Consolidated Summary of State Reporting Requirements for the Safe Drinking Water Information System (SDWIS)

United States
Environmental Protection
Agency
Office of Water
4604
EPA812-B-95-001
November 1995
-------
-------
UNITED STATES ENVIRONMENTAL PROTECTION AGENCY
| 401 M Street, S.W..
" Washington, D.C. 20460
2 8 [996

It is a pleasure to transmit the first version of the Consolidated Summary of State
Reporting Requirements for the Safe Drinking Water Information System (SDWIS) to you. This
document is identical to the one that was originally sent to you by Cynthia Dougherty in
December, 1995 as an advanced copy for your use, The format of loose leaf pages with punched
holes was chosen so that, in the future, this document could be easily updated by sending only
replacement pages.

This document was created for several reasons. First, it is meant to satisfy the need that
was expressed on several occasions, especially by the States, for a single, concise reference where
anyone could go to find all of the SDWIS reporting requirements under the Public Water Supply
Supervision program. To keep it concise, this document does not contain any of the technical
details on reporting, but focuses on the "what" to report.

Second, this document was created with the future in mind, where, with a single reference,
one can capture all of the reporting requirements for the drinking water program. It is the Data
Sharing Committee's (DSC) recommendation that this document be used in this way, for
example, by reference in State/EPA Environmental Performance Partnership Agreements.

Third, this document will serve as a resource for both the DSC and the Data Quality Team
and possibly other groups that will be dealing with drinking water reporting issues. As the
recommendations of the DSC become implemented, any changes to the reporting requirements
will be reflected in updates to this document., In this way, this document will always contain the
most up-to-date summary of the current reporting requirements.

Thank you to everyone that provided comments on the drafts of this document. Your
input helped us to produce what we believe is a quality document. It is our hope that this
document will serve the purposes mentioned above and that it will be useful to you.
Sincerely,
Tom Poleck, Chairman
For the Data Sharing Committee
-------
-------
CONSOLIDATED SUMMARY OF STATE
REPORTING REQUIREMENTS FOR THE
SAFE DRINKING WATER INFORMATION SYSTEM (SDWIS)
CONTRACT NO. 68-C2-0113
WORK ASSIGNMENT NO. 3-36
Prepared for:

United States Environmental Protection Agency
Office of Ground Water and Drinking Water
401 M Street, S.W.
Washington, D.C. 20460
Work Assignment Manager:

Mr. Thomas Poleck

Prepared by:

The Cadmus Group, Inc.
and the
PWSS Data Sharing Committee

RELEASE NO. 1
-------
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
-------
-------
CONTENTS

PREAMBLE vi

INTRODUCTION AND BACKGROUND 1

PART I. CONSOLIDATED SUMMARY OF CURRENT REPORTING REQUIREMENTS 2

PART II. RULE SPECIFIC REPORTING REQUIREMENTS 19

1. TOTAL COLIFORM RULE TCR-1
BACKGROUND TCR-1
FRDS/SDWIS REPORTING REQUIREMENTS TCR-1
A. State Decisions TCR-1
B. Violations TCR-1
C. Public Notification TCR-2
D. Enforcement Actions TCR-2
DOCUMENT SOURCES TCR-4

2. SURFACE WATER TREATMENT RULE SWTR-1
BACKGROUND SWTR-1
FRDS/SDWIS REPORTING REQUIREMENTS SWTR-1
A. State Decisions SWTR-1
B. Source Records SWTR-3
C. Violations SWTR-5
D. Public Notification SWTR-7
E. Enforcement Actions SWTR-7
DOCUMENT SOURCES SWTR-7

3. LEAD AND COPPER RULE LCR-1
BACKGROUND LCR-1
FRDS/SDWIS REPORTING REQUIREMENTS LCR-1
A. State Decisions/Milestones LCR-1
B. Sample Data .... LCR-3
C. Violations LCR-4
D. Public Notification LCR-6
E. Enforcement Actions LCR-6
F. Return to Compliance LCR-6
DOCUMENT SOURCES LCR-9

4. PHASE I, II, IIB, AND V RULES PHASE-1
BACKGROUND PHASE-1
FRDS/SDWIS REPORTING REQUIREMENTS PHASE-1
A. State Decisions PHASE-1
B. Violations PHASE-3

DATE: November, 1995 RELEASE NO. 1
-------
C. Return to Compliance PHASE-7
D. Public Notification PHASE-7
E. Enforcement Actions • • PHASE-8
DOCUMENT SOURCES • PHASE-8

5. UNREGULATED CONTAMINANTS UCM-1
BACKGROUND UCM-1
FRDS/SDWIS REPORTING REQUIREMENTS UCM-2
A. State Decisions UCM-2
B. Sample Records •. UCM-2
C. Violations UCM-5
D. Return to Compliance UCM-5
E. Public Notification UCM-7
F. Enforcement Actions UCM-7
DOCUMENT SOURCES UCM-8

6. REPORTING VARIANCE/EXEMPTION INFORMATION V/E-1
BACKGROUND V/E-1
FRDS/SDWIS REPORTING REQUIREMENTS V/E-1
A. State Decisions - Reporting Variances and Exemptions V/E-1
B. Violations V/E-4
C. Public Notification V/E-4
DOCUMENT SOURCES V/E-6

7. REPORTING ENFORCEMENT INFORMATION ENF-1
BACKGROUND ENF-1
FRDS/SDWIS REPORTING REQUIREMENTS ENF-1
A. Linking Enforcement Actions to Violations ENF-3
B. Return to Compliance ENF-3
DOCUMENT SOURCES ENF-5

8. MISCELLANEOUS REPORTING MISC-1
BACKGROUND MISC-1
FRDS/SDWIS REPORTING REQUIREMENTS MISC-1
A. State Decisions MISC-1
B. Violations - MISC-1
C. Public Notification MISC-3
D. Enforcement Actions MISC-3
DOCUMENT SOURCES MISC-4
DATE: November, 1995 RELEASE NO. 1
-------
TABLES

Table SUM-1: Grand Summary of Current Reporting Requirements ; 5
Table TCR-1: FRDS C1105 (TCR Violation Type Codes) /SDWIS VIOLATION, TFRVTYPE_CODE
TCR-1
Table TCR-2: Required Reporting Elements for TCR Violations '. TCR-3
Table SWTR-1: Required Reporting Elements Associated with Filtration Requirement (FR) Determinations
SWTR-2
Table SWTR-2: FRDS C3019 Codes (Reason Filtration is Required)/SDWIS MILESTONE_EVENT,
REASON_CODE SWTR-3
Table SWTR-3: Required Reporting Elements for Treatment Applied at the Source or Plant SWTR-3
Table SWTR-4: Additional Required Reporting Elements for PWSs Determined to Have GUDI Sources
SWTR-5
Table SWTR-5: Required Reporting Elements for SWTR Violations SWTR-6
Table LCR-1: Required Reporting Elements Associated with LCR Milestones LCR-1
Table LCR-2: FRDS C805 Codes (PWS Milestone Codes)/SDWIS MILESTONE_EVENT, TYPE_CODE
LCR-2
Table LCR-3: Required Reporting Elements Associated with Lead Sample Data LCR-3
Table LCR-4: LCR Violation Codes/Default Values LCR-4
Table LCR-5: Required Reporting Elements for LCR Violations LCR-5
Table LCR-6: Definition of Compliance Achieved by LCR Violation Type LCR-7
Table PHASE-1: Summary of Monitoring Requirements for the Phase I, II, IB, and V Rules .. PHASE-2
Table PHASE-2: Required Reporting Elements for Phase I, E, IIB, and V Rule Violations .... PHASE-3
Table PHASE-3: Phase I, II, IIB, and V Rule Contaminant Codes PHASE-6
Table UCM-1: Required Reporting Elements for Unregulated Sample Data UCM-2
Table UCM-2: FRDS C2107 (Sample Contaminant Codes/UEQ/SDWTS SAMPLE_ANALYTICAL_RESULT,
TFRCNTMN_CODE - (Non-discretionary Monitoring) UCM-4
Table UCM-3: FRDS C2107 (Sample Contaminant Codes/UEQ/SDWIS SAMPLE_ANALYTICALJIESULTJ
TFRCNTMN_CODE (Discretionary Monitoring) UCM-5
Table UCM-4: Required Reporting Elements for UCM Violations UCM-6
Table V/E-1: Required Reporting for Variances/Exemptions ; .. V/E-1
Table V/E-2: Variance/Exemption Contaminant Codes V/E-3
Table V/E-3: Variance/Exemption Status Codes V/E-4
Table V/E-4: Variance/Exemption Treatment Codes V/E-5
Table ENF-1: Required Reporting Elements for Enforcement Actions ENF-1
Table ENF-2: FRDS C1205 Codes (Federal Enforcement Follow-up Action Codes) ENF-2
Table ENF-3: FRDS C1205 Codes (State Enforcement Follow-up Action Codes) ENF-2
Table ENF-4: Database Elements for Linking Violations and Enforcement Actions ENF-4
Table MISC-1: Required Reporting Elements for TTHM and Radionuclide Violations MISC-2
Table MISC-2: Contaminant Codes for TTHMs and Radionuclides MISC-3
DATE: November, 1995
RELEASE NO. 1
in
-------
APPENDICES

APPENDIX A: COMPLETE LIST OF REFERENCES •.'.• A-l
APPENDKB: SDWIS/FEDCONTACTS B-l
DATE: November, 1995 RELEASE NO. 1
iv
-------
PREAMBLE

This document provides guidance to the States on reporting required data to the Federal version of the Safe
Drinking Water Information System (SDWIS/FED). The Public Water System Supervision (PWSS) Data Sharing
Committee (DSC) oversaw the development of this document through a contract with The Cadmus Group, Inc.
While the purpose of the DSC is to review the data needs of the U.S. EPA and to recommend changes to State
reporting requirements, all of the current requirements discussed in this document have not been reviewed to date.
Issuance of this document, therefore, does not constitute a reaffirmation of all current reporting requirements for
SDWIS/FED. This document simply summarizes the current requirements which will remain in effect until they
are reviewed and possibly changed by the DSC and the Office of Ground Water and Drinking Water at a later date.

This document does not contain all of the detail behind "how" to report the required data, but focuses more on the
"what" to report. See the references listed in this document for the details behind how to report. Any questions
regarding the use of this document, and/or its contents, should be directed to the persons identified in Appendix A.
DATE: November, 1995 RELEASE NO. 1
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995
RELEASE NO. 1
VI
-------
INTRODUCTION AND BACKGROUND

The current PWSS Program reporting requirements originiated in the late 1980's in response to the promulgation
of various National Primary Drinking Water Regulations (NPDWR) following the 1986 ammendments to the Safe
Drinking Water Act. At that time, the U.S. EPA developed a national database management system, called the
Federal Reporting Data System (FRDS), to maintain basic inventory, violation, enforcement, and variance/-
exemption data, that were needed for Federal oversight of the State PWSS programs. The original reporting
requirements were documented in two guidance documents, Water Supply Guidance V-l and Water Supply
Guidance V-2, as well as in the FRDS user documentation.

Over time as new regulations became effective, the reporting requirements were expanded and modified. Typi-
cally, a separate reporting guidance document was developed for each new regulation. Some of these new
regulations contained features and subsequent reporting requirements, specifically on treatment techniques, that
could not be readily accommodated by FRDS. These factors, to name only a couple, contributed to the relatively
complicated, rule specific, and separately referenced reporting requirements that currently exist.

This document was produced in response to requests that were made by many States to have all of the current
reporting requirements consolidated into a single reference document, and should serve as a general reference for
all currently required SDWIS/FED reporting.

This document was also developed for the following purposes:

o to serve as a technical reference listing both FRDS data elements and the associated SDWIS attributes for
reporting data to SDWIS/FED, and should also be useful for the retrieval of information,
o to serve as a baseline reference document for the Data Sharing Committee that lists all of the current
requirements, and
o to serve as a technical reference document to be used by the Data Quality Team for the numerous data
quality initiatives that they are pursuing.

The remainder of this document is divided into two main parts. Part I is an overall summary of the current
reporting requirements presented in a single table. Part II provides a more detailed summary of the reporting
requirements presented in separate sections for each drinking water rule.
DATE: November, 1995 RELEASE NO. 1
-------
PART I. CONSOLIDATED SUMMARY OF CURRENT REPORTING REQUIREMENTS

Table SUM-1 summarizes all of the current reporting requirements in both FRDS and SDWIS terminology Table
SUM-1 also lists whether a particular data element/attribute is required for a specific drinking water rule, such as
the Total Coliform Rule (TCR), or the Surface Water Treatment Rule (SWTR).

The current reporting requirements are composed of two types of requirements; registration and grant eligibility.
Registration requirements are those data elements that are either operationally required by FRDS to process the
data on a public water system, or are programmatically required by the U.S. EPA to define each PWS or to meet
some basic program need. These two types of registration requirements can also be conditionally required
depending on the data being reported.

In some cases, conditionally required data elements must only be reported to meet the operational requirements of
the FRDS data system. For example, C301 (PWS-AD-ID) is the identification number (secondary qualifier after
the PWSID) for the C300 (Other Address) FRDS database record, and needs to be reported if other address data
are reported. Other address information is not a current reporting requirement, so the appearance of C301 in
Table SUM-1 occurs only for completeness sake, not because it should be considered a current reporting require-
ment.

The same concept is true for latitude/longitude data (C415 and C417), and cadastral data (C418, C419, C421,
C423, and C425). Although the reporting of latitude/longitude data has been a U.S. EPA requirement under the
1991 EPA Locational Data Policy, this requirement has yet to be officially implemented as a FRDS or
SDWIS/FED reporting requirement by the Office of Ground Water and Drinking Water. The "conditional"
designation of these particular data elements suggests that, if these optional data are reported, then both latitude
and longitude must be reported. Latitude and longitude data are currently under consideration as new reporting
requirements for SDWIS/FED.

Grant elibility requirements are those data elements that define a PWS for PWSS State grant allottment purposes.
Each year, FRDS, now SDWIS/FED, is used to determine the percentage of the total national PWSS grant
allocation that will go to each State. Only systems that contain valid data for all of the grant elibility data elements
are considered in this calculation.

A few reporting requirements summarized in this document were not clearly described by any of the available
reference documents. These uncertain requirements were researched by consulting with senior OGWDW and
contractor personnel that were involved with the development of the original reporting requirements. Clarifica-
tions to those reporting requirements are provided below.

Currently to have a PWS inventory registered into FRDS/SDWIS-FED, at least one source record needs to
be reported along with all of the other required inventory data elements. Although only one source is
needed to register a PWS inventory in SDWIS/FED, the intent of this reporting requirement was always to
have all sources of water reported for each PWS. This document therefore clarifies this requirement by
stating that all active sources of-water should be reported for each PWS.

FRDS data element C411 (PWS-SE-SELLER-ID) is required to be reported for all consecutive PWSs.
Although a general characteristic of inventory, this data element is specifically needed under the SWTR.
In SDWIS/FED, these data are represented by the relationship between WATERJSYSTEMSs via the
WATERJPURCHASE entity type.

DATE: November, 1995 ' RELEASE NO. 1
-------
Although not specifically listed as a FRDS reporting requirement, C1280 Enforcement-Violation Link
records are required reporting to FRDS/SDWIS-FED. These data are needed to link follow-up actions to
violations. See Table ENF-4 in Section 7 for a description of the data needed to properly link follow-up
actions to violations. The proper linkage of follow-up actions to violations would have a single action
linked to multiple violations (e.g., a single notice of violation record linked to several synthetic organic
chemical (SOC) monitoring/reporting (M/R) violations if a single notice was sent in response to a failure
to monitor for al of the regulated SOCs). In this case, separate follow-up actions should not be reported
for each, separately reported, SOC M/R violation.
DATE: November, 1995 RELEASE NO. 1
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995 RELEASE NO. 1
-------
g
O"
be
o

I
U
<—
o
CS

E
O
«
H

«
to
'cn
g
3
(i
g
H"
g
**

S
u
D
£
a
td *".
cn ea
PM «

g
cn

B
cn
5 g
g S
-

lit
ts Rf ° _,
. A |-1|
llt-i
z e-oa
Ed
Q
D PWS STATE TYPE_CODE
WATER_SYSTEM
D PWS FEDERAL TYPE_CO1
WATER SYSTEM
TYPE CODE
POPULATION SERVED

£
s|
O ^

o
z
o

o
Z
BJ
>-

ACTIVITY STATUS CODE
WATER SYSTEM

£
h

P
c.
Ss
5 £
o
Z

o
Z

l{s|B^5
•«• fLfr =•?« 1. 1 1.
4-fJ || t| j
| i 1 1 i^l f 2 1
Z E S .a e-s «
-------
n
o
42
a
o*
CXO
o
^
C3
•a
I
I
CO

£
p
(X
M
5
£«
•fi
S
5
§
K

i
«
j

^>
w ,
^c £
H C
Pk «

«
1
|
H
CO
. H
tv MS
a w
2 S3
CD *3
O1
p, 00
O £
ll
So
§1

C*3
p
J3
SDVVISATTRIB
ENTITY
1«
2^ kf
§^
OJ
ii
V
O

o
2

2
0

CO
[j5
>*

NAME
LEGAL ENTITY
NAME
WATER SYSTEM

Cd
^;
s
-1
o £
£
o
2

o
2

2
0

c/5
P«5
>H

ADDRESS CITY NAME
LEGAL ENTITY

fc
t?
1
CO
t-2!
O ^
z
o
2

o
Z

o
z

CO
w

STATE FIPS CODE
LEGAL ENTITY

1
%
H
CO
o» °?
0
o
2

0
^

o
0

CO
w
>•

ADDRESS ZIP CODE
LEGAL ENTITY

cu
Si
ta
H
CO
O a.
s-
o
2

0
j2

£
£

CO
w
><

«s

I
p
r^
v.
COUNT
SERVICE_CONNECTION_

. CO
00
OH CJ
W W
sil
O eu O
*

0
^

Z
0

-2.^
t.'go | |

0 § fe CO ^'<*H
3 8 o ^ 5 e
"e "E. 2 O *•• ®
3 3-2^11
ll
Q '5
^ CO 9
||
fa cu
Q Q
O O
s s
w w
START DAY
/\NNUAL_OPERATING_P
START MONTH
ANNUAL_OPERATING_P

S
|Q
«ll
I-H S a
o SS
*
o
2

o
K

*
Q

•2 -M ^ ^S 2

"(3 *S nS . *£? O*
c o fe t» S **-"
3 8 5 ^ 1 e
*O — ^ £_) ^^ O „;
6 Vigils
la
CO JS
* i"i
« u
si
Q O
O 0

w w
END DAY
ANNUAL_OPERATING_P
END MONTH
ANNUAL_OPERATING_P
a
ci
§
§
w
o i£
O
LU
C/3
LU
LT
O)
CD
03
.a
I
o
ili
i
-------

o
to
03
£
s
i
§

w"".
2 5
PH M
BJ
>
.
&
u
H
•ii
. PI
z i
is
O1

z£
Oz
p
pa
S25
8£
. « «

SDWIS ATTRIBUTE
ENTITY
H H
§ §
O z
li
8S
NM W
NH CQ
CO g
i§
„ ,,,,
'

'
^
*•

_,v-
- •='

''
"

** SA
-<;
"S. -S
' $-^
' i?

• ?~
:-l
kt
^ X S
I/-;"-- %,
.

-• v
_.

•
•"
^

x ••••

6 .4, O c
o "o J3 Js 4) M o
n fi-iilllil
T! l^1 8 S ^ s 's :
Z "3 v§ 1 B. e E o.^

1
•^
STATE ASGN IDENTIFICATIO1
NUMBER
LEGAL ENTITY

O
p
sg
3£

'
,

••

* f
'
~. *. \. \

- v "
"*?
* ""
5
i

fg N
1"
J7
y
- '
v.\

"-"£; -
%
•• •> ••

-
o

CO
w
>-

O
Z

*— t

«^
STATE ASGN IDENT NUMBEI
WATER SYSTEM FACILITY

Q
BJ
CO
o
Z
o

S
>"

o
Z

TYPE CODE
WATER SYSTEM FACILITY

w
CL.
H
Q
0:
t
W
Of
w
- CO
SS
si
o
Z
o
Z

o
Z

W
^l

o
Z

Q
12

WATER TYPE CODE
WATER PURCHASE
WATER TYPE CODE
WATER SYSTEM FACILITY

w
Q
O
O3
il
O
Z
1

o
Z

lii
u t> J3
2 1 °
o
Z

Q
Z

Represented by relationship betweer
WATER SYSTEMS via
WATER PURCHASE entity type

Q
•«J
W
CO
w
=s
si
0
Z

S •'•
1
* '
o
Z

o
Z

LAT DEGREES NUM
WATER SYSTEM FACILITY

w
1
^
w
S S

- 53
S- ™
*= S "9
§
-------
c
o
1
1
2J
CO
•o
GO
3>
2

V*
s
S
1

^
B
g

u>
•S H
5s

«
k
g
C/3
AS

li
o 5
, S
(2
.a

I
o

lii

I
-------
I
s
O"
o

. '
!
; |
' I
i 1

•TJ
w

•

•"
• V -

%'•

'
/•
'
-
o
Z

O
g ill Hi
*

o
Z

c8 5 5 3
*3 oo a> *o -ti •— u

S O II 05 *^ ^
"w ^ m « $8 £ ^
M g » § 8 t2 *S
oi E 0 "3 &.._ S
H
1 O i I
z 3 z z
5 < O O
STATE ASGN IDENTIFICATI
NUMBER
TREATMENT OBJ PROCESS
STATE ASGN IDENTIFICATI
NUMBER
MILESTONE EVENT
STATE ASGN IDENTIFICATI
NUMBER
DEVIATION

£
§
^>
H
5
op
§1
o
Z

*•

*
CO
PJ
*

0
Z ' •

o
Z

o
CO
w
5

1 =>

*1* MS ^ [Ij ^ ^ Z ^
tr;WU3Q 213 OTZ
^d^S'S-S.'o'O
OS i i
H
s
o
^
TINTRPRO CODE
TREATMENT OBJ PROCESS
TYPE CODE
MILESTONE EVENT
TYPE CODE
DEVIATION
6
%
§
f*|
w
H
UJ
CO
S oS O
O

111
LLJ
DC
LO

kJ*
CD

LLJ

Q
-------
o
cr
S?
o
t
ca

E
CO
•o

1
O
CA

K
0
u.
w
a

i
i

§
P
«
y

~ >
is
s3 S
Pk •"
£
£

1
CO
£g

•5 w
5 K
OP
a
REGISTRATION
REQUIREMENTS

SOWS ATTRIBUTE
ENTITY

Hi M
& iC
gl
§5
U Pi
s w
Q S
§ g
^4

+ •

,, .

,«
1

g
•?
li
1
!

PI
i
Z
STATE ASGN IDENTIFICATIO
NUMBER
WATER SYSTEM GEO AREA
ASGMT"

Q
<;
— w
o fe
O S
-
'•?• N
s s'
€ '"

•k ^ s '
•, -X, ^ :
*rf-
^•AV •
•V JVS *, ;
/s^j
v- •* ' :
-
.> ^V, S1
^sv V
••:. ?
VM&V

- **s%
\ '"^
xo*
"tf:"
i
>H;
_v O V ^
^ <. ''•• '-^
-^s ^ 4
,*v SS A
•f ' ^ -^
* ~~'i ^
i ' '
ii^ ^ <'>S'
;" c
- s' "
U f
f s X
;%s «, "
; s^
'^""'
0

3
A C600 record iden-
tifying the PWS as a
wholesaler of water
must be reported when
the population served
= 0
i 2S
z 9
STATE ASGN IDENTIFICATIO
NUMBER
WATER SYSTEM SERVICE Al
ASGMT"

w
°?
o M

OP-
o

o
Z

.§

o
z

o
^i
S
TINSAT CLASS CODE
WATER SYSTEM SERVICE Al
ASGMT

1
1
t>
w
m "P
§ &
0^
0

o
Z

4
Used for NTNCWSs
andTNCWSsonly.to
identify the primary
type of area they serve

w
CO
VO :>
U Si
O

UJ
V)
in
O)
O)
5
o
-------
o
er
UD
B
O
O.
CS

« •%
co oa
11

05
£
CO

H
* W
H g

S 3
01
z£
0 c^
PI
A t3
»a —
3

SDWIS ATTRIBUTE
ENTITY
Hg
§§
o 2
SM ®
fe ^
8«
M W .
ob *s
a, Z

'••

'
•.
_.
"• *• ^
.., ^
*••*
s1.
«
s.
s^

/^^
L /

: > '
i ^'"
L I'
; J
; .(^
! 1*
:-
;v -
'-
% ^
:--
f "•*

s
•"
*

" ',
•• ,

o
Z

Z .

O
2

1. .

o § "°" §
" fi^i
lilli

S51
STATE ASGN IDENTIFICATK
NUMBER
VISIT

Q
fi
g
s»
OB<

^
-
'
••
1

g
o
^ T
1
&
i

' -
-
«

%
'
o

CO
w

o
Z

§ S'
D GENERATED ID SOURCE
MILESTONE EVENT
STATE ASGN IDENTIFICATK
NUMBER
MILESTONE EVENT

a
M
pr
P.
3
s
ii
o Eu
o
Z

CO
Ed

Q
Z

o
Z

C-l

ACTUAL DATE
MILESTONE EVENT

E—1
^
w
Z
8
2
^
ii
u £
o
Z

0
Z

o
Z

TYPE CODE
MILESTONE EVENT
O3
0
8
(i
Z

u;
e
s»
UOn
o
Z

0
Z

o
Z

.*•

MEASURE
MILESTONE EVENT
^
J
£
K
Z

£
r
12 CO
o S
: ;
•
:

-
^

e
s

1
"S
' S
"
, '

-
- "

'•

CO
s

CO
W • '

CO ' .
^

CO
*

o
z

CO '

w Q |
1 8, §'
FEDERAL FISCAL YEAR NU
VIOLATION
D GENERATED ID SOURCE
VIOLATION
STATE ASGN IDENTIFICATI
NUMBER
VIOLATION

-S
= 3
0 >
O
in
G>
O)
03
JD

I
O

lii

i
-------
o
I
bl
I

I
03
E
en
•o
I

«
O
REMENTSF
H
S

g
p

04
^

PHASE I,
II/1IB.V

S
(A

tfi
frSte
Si!
§ j|
§3
a
_ en
IS
r* «~
||
5 »

w
S
SDWISATTRIB
ENTITY
1 FRDS-II COMPONENT
NUMBER AND NAME

M ^
•§ «? «?
f2^^
csBB
S-ss „ A.W
O »-• •-« H S CS
Hflll

O ttl
T^ o 55

1
tn

TFRCNTMN CODE
VIOLATION"
C1103
VIO-CONTAMINANT

vo
10

r-
o
o
i
o

TT
vcT
en
oo
^
1
cs

TFRVTYPE CODE
VIOLATION
C1105
VIO-TYPE

a
•*"

CO
s

s
2
s
COMPLIANCE PERIOD
VIOLATION
IC1107
VIO-COMP-
PERIOD-BEGIN-DATE
-s
c <^
.a -n *a *n
° '§ n o
_ &_< a
0202
I'UH 2
M *** M
3 IS I

Cl 109 is not
required if
Cllll is re-
ported

•si
E g
£1

"o
.a IS -a .0
§1 = 1
0202

w
§
COMPLIANCE PERIOD
VIOLATION
C1109
VIO-COMP-PERIOD-END-
DATE
•s

.a ^ .a ,,
S '3 2 ?
0202
1«M 2
.a ^ .a
0 20 I

^ "
.a is -a
Hill
O 2*0 a

11
i i
z1"!

^
.s ig .a ^
o §"3 2

o
Z

•»

Cllll
VIO-COMP-PERIOD-
MONTHS

o
Z

& AS
•O 0 ^>
•8^8-
l-o IS
l2S-2«8

o
Z

*•

AWARE DATE
j VIOLATION
»C1115
VIO-AWARE-DATE

0
Z

1
ANALYSIS RESULT_ME
VIOLATION
DC1123
VIO-ANALYSIS-RESULT

.§

o
Z

0
'z

1
VIOLATED MCL MEAS
VIOLATION
DC1125
VIO-MCL-VIOLATED

;§

.§

O
Z,

ON
•e 2
g-02
S*" S o
O

*U O

Z '

8-3 5
iJ3
0 '3 o

^S-gS
8||'"3|*0j
Ills I.

0
2

1
§
1 REQUIRED SAMPLE Ml
VIOLATION
BC1127
VIO-SAMPLES-REQUIRED

0
2

E
SAMPLE TAKEN QUAN
VIOLATION
C1129
VIO-SAMPLES-TAKEN
loo

0
z

1
Q
MAJOR VIOLATIONJN
CODE
VIOLATION
IC1131
VIO-MAJOR-VIOLATION-
FLAG
-------
g
o
I
I
I
O

I
CA
03
'§

0
In
1
E|
K
P
§

(
1
1
i
|
c
e
E
;

c
c

1
^
c
{
I

fi
p
a
a

«>.
CO B
S t
PH i-l

k
B!
ji
4 g
S £jj
X M
a P
1
017WJL8 Al 1 KlBU.lt,
ENTITY
? a

5 §
2 O
1 Z
32
i W
g§
4 z

°£ 3 -o o g1
I 1 ? 2 "§••§
5| 2 §* 1 | g

o
Z
1

o
Z

*
Represented by a relationship between
VIOLATION and
WATER_SYSTEM_FACILITY

Q
3
m 05
= 6
U£

> ""
^
-

-
- s
'JS
* 1*^
% §
1
;!
•••*•
,
*•

^
f

CO
w

CO
•*"

CO
>.
CO

o
z

«
FEDERAL FISCAL YEAR NUMBER
ENFORCEMENT ACTION
D GENERATED ID SOURCE CODE
ENFORCEMENT ACTION
STATE ASGN IDENTIFICATION
NUMBER
ENFORCEMENT ACTION

- &
° £
0«

CO
>

CO
*
CO
w

o
z

«
DATE
ENFORCEMENT ACTION

£
<
Q
z
8
J
§ z
O w

CO
W

a
•*

CO
^
CO
w

o
z

ts
The three position FRDS-II FOLLOW-
UP-ACTION code is represented as three
separate columns in SDWIS as follows:
FRDS Position SDWIS Column
1. TFREFUA AT CODE
2. TFREFUA FT CODE
3. TTREFUA SC CODE
Z
O
5
•5
£•<
£
Q
~g
° jg
O H
o
z
LU

LU
LU
DC
-------
I
g,

1
o

£
ra
CO
•a
co
a>

K
O
1/J
»!*
rl
S
B

S
1

—
|s"
g§

1
1
|i
§3
01
aE
§1
11
3 c>
Ed Ed
«2

B
S3*.
SDWSATTR
ENTIT
II COMPONENT
JER AND NAME
Q g

E "•

o
*»*
*s
s

I
-

g
S

1
,
0

g
g

i
«
0

g
CO
[i]

CO
Id

CO
pa
g
o

w
B'

g
CO
0

CO
g

CO
w

CO
Ed
g
0

1
CO
U)

•g
CO
0

I 2
cUii
g || | | a
oo -i I"" | '•§
.C4 «-L is "ei t> —
o a §• S i§ '?
g
i^
^•y
Represented by a relations
VIOLATION and ENFO
MENT ACTION
C-VIO-ID
z

o §

§
B
DATE BEGIN
ENF VIOLATION CRI
I
w
1
S

c? li
0^

DATE END
ENF VIOLATION CRI
Q
[i
|

?? li
0 §

I
S
DATE BEGIN
ENF VIOLATION CRI
C-PERIOD-BEGIN
"Z

?? ti
0§

1
H
TFRVTYPE CODE
ENF VIOLATION CRI
a
i
g
OS »-
S £5
0^

§
B
TFRCNTMN CODE
ENF VIOLATION CRI
<-CONTAMINANT
g
*— ' t-
?S ti
36
in
05
CD
-------
1

I
60

I
O
O

w
O
I
VI
es

K
O
(K
03
a
a
Z
P
ex
S

s
p

OS
s

« t>
co B3
PL, M

£
.
o:
u
H
g|
H 5
Jr g
is
01
0 Zl
P w
-< t3
2 ptf

SDWIS ATTRIBUTE
ENTITY
H
&3
FRDS-IICOMPON
NUMBER AND NA

'"
,

' '

f f'

'
'

•• •"*»
*J
ja
•u
w
E* s
•
- ^

\ "'
'

"
'•

GO
>

O
z

D GENERATED ID SOURCE CODE
SAMPLE
STATE ASGN IDENTIFICATION
NUMBER
SAMPLE

§
S|
0 CO

o
z

"8 f ^
? 1?
•B-i ;

o
^

w
COMPLIANCE PERIOD BEGIN DAT
SAMPLE

103
MPLE-BEGIN-DATI
OS
.a. ii
lllll
• II lilt
(23 l-S 8 a
2

B "c
i 0

o
z

COMPLIANCE PERIOD END DATE
SAMPLE

105
MPLE-END-DATE
OS

CO
^

o
Z

o
^4

TFRCNTMN CODE
SAMPLE ANALYTICAL RESULT
H
5
107
MPLE-CONTAMIN;
Oco

CO
w
>>:

o
Z

DETECTION LIMIT CODE
SAMPLE ANALYTICAL RESULT

Z
109
MPLE-RESULT-SIG
cs <
O co

^^
•a ^
S 1 ^
>-H D< O

O
Z

o
'^

MEASURE
SAMPLE_ANALYTICAL_RESULT

111
MPLE-ANALYSIS-
SULT
cs •< W
O co OS

(0
^

o
Z

o
t(^t

UNIT OF MEASURE CODE
SAMPLE ANALYTICAL RESULT

112
MPLE-RESULT-UM
OS

CO
^

o
Z

o
J^

TFRSTOP METH CODE
SAMPLE

113
MPLE-ANALYSIS-
:THOD
02s

m
><

O '

o
^

SOURCE TYPE CODE
SAMPLE

S
115
MPLE-SOURCE-TY
CJ «

£|vo
sl?
£ g..S

O
£

•7

o
Z

Represented by a relationship between
SAMPLE and
WATER SYSTEM FACILITY.

119
MPLE-SE-ID
0 m
§
LLJ
OC
in
O)
O)
-------
I
g-
&
1

I
•o
c

2
e>
GO

o
1ENTSFI
P

P
^
^
W Q
£§
I
S>
6
H

CO
ti g
CM £j
g S
OP
a
K §
II

M
!•<•
SDWISATTR1BU
ENTITY

f-td
FRDS-riCOMPONEN
NUMBER AND NAM

IJ,
111

COMPOSITE QUANTITY
SAMPLE
Q
e
C2125
SAMPL&QTY-COMPOSr

>
o
2
S

§
8,
w
O.

- v
Vs
v ; " \
-, /!
-.•• ""
k ^

;^j:
'-%
™= -
•^ ™V
3-- *!
- a-
-- ^ ,
v^ s
1 ^^
''S
"^i"
if
;f:l}
•F -vT1*
0* <^ cO*
^ IXir^ N^'
s "* ^
vx %-X ^
i 's \
^ ws •• is
; V \ s** v
•.%, ^v

2
»
^
CO
w

tt s
0 0 §
li III
0

S O z1 Q
•s o ft o
es i ° i
S w p w

«' § " §
1 S> 1 Sih
,1 Q S Q Z
^ «• a o'£
% § 21 §«
i'S 1 S«l li
cs<; Z<; WCQ< i^co
Sp-< w i-S H^t-i w u
ll SI III SI

sa
* s

2
8 '

TFRCNTMN CODE
DEVIATION

fc
.*
[
§"
SB.
O >

2
CO
W

1
B&
I

TYPE CODE
DEVIATION
TYPE CODE
MILESTONE EVENT

C3005
VE-RECORD-TYPE

*
«

!|i
1^1
*^ *3 Vt
0

o
z

EFFECTIVE DATE
DEVIATION
ACTUAL DATE
MILESTONE EVENT

C3007
VE-EFFECTIVE-DATE

CO
>«
CO

o
z

1 EXPIRATION DATE
DEVIATION

C3009
VK-F.XPIRATION-DATE

o
Z

STATUS CODE
DEVIATION
STATUS CODE
MILESTONE EVENT

C3011
VE-STATUS-CODE

C/3
uu

DC
in
en
05
0}
XI

I
o

lii
-------
en
4)

1
H

ee
o
In
1/1
i
i
p
a
S

a
a
|

co g"
PH B

Q£

H
CO
is
U D
a
50
Oz
2 £3
IP
s ^
tt

td
H
S
SDWISATTW
ENTITY
o z
FRDS-II COMP
NUMBER AND
o
z
1

z
o
z

TJ-

S
%
MODIFIED MCL MEAS
DEVIATION

C3013
VE-MOD-MCL
O
z
CO
>

„.

TINTRPRO CODE
DEVIATION

»C3017
VE-ALT-PROCESS
.&
^
^
2 ""
*
o
Z

"3-

REASON CODE
DEVIATION

1C3019
VE-REASON-CODE

REASON CODE
MILESTONE EVENT

'
- .
:

'
.
'

ff * ',
:
•
•"
,

•
;
-.-.-. f •
•
1 :
1 !
&
1 ^
I i
^
| i
' * '•", i

' i

•"

,,,,,,,
„
--
o

£
0

S3
"E,^.
o
Z
o
Z

BJ
W
i g
o I

5 1
o S
STATE ASGN IDENTIF
NUMBER
DEVIATION SCHEDULI
STATE ASGN SCHEDU
MILESTONE EVENT

C3101
VE-SCHEDULE-ID

-
•t
. •'
' f
S
IS
?
5
w
S
i"
"U

••

.
o
Z
o
Z

o
Z

^i
td O
" ^tf
-2 §«"^ S2
!§ § "•§ w
§8^9
z-S'-Sfe

•s
Not Convert

C4001
SDD-ID
<
LU

U
in
Oi
o
g
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995 RELEASE NO. 1
18
-------
PART II. RULE SPECIFIC REPORTING REQUIREMENTS

" • The following sections contain the specific; reporting requirements for the major National Primary Drinking
Water Regulation rule packages that have Keen promulgated to date.
DATE: November, 1995 RELEASE NO. 1
19
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November. 1995 ~ ' RELEASE N°" 1
-------
1. TOTAL COLIFORM RULE
BACKGROUND

The Total Coliform Rule (TCR) became effective on December 30, 1990, and updated bacteriological
monitoring for PWSs. The number of samples to be collected and analyzed is based on population served by
the system. The State may permit any system serving < 1,000 persons to sample less frequently than monthly
if the system uses protected ground water, has no history of total coliform contamination, and a sanitary
survey shows the system is free of sanitary defects.

Any samples that test positive for total coliform (TC+) must be analyzed for fecal coliform (FC) or E. coli
(i.e., must be speciated). In addition, repeat samples must be collected within 24 hours (longer with State
permission). For systems collecting < 5 samples per month, monitoring the next month increases to 5
samples per month following a positive result.
FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions

None are required to be reported.

B. Violations
Under the TCR, a PWS could incur 2 types of MCL violations and 5 types of M/R violations (as
shown in Table TCR-1). Table TCR-2 lists the data elements that must be reported for each TCR
Table TCR-1: FRDS C1105 (TCR Violation Type Codes) /SDWIS VIOLATION, TFRVTYPE_-
CODE
Violation Type
MCL, Acute
MCL, Monthly
M/R, Major Routine
M/R, Minor Routine
M/R, Major Repeat
M/R, Minor Repeat
Description
FC+ or E. coli positive (EC+) repeat or TC+ or EC+ repeat following a FC+ routine
For systems collecting:
> 40 samples - more than 5% are TC+
< 40 samples - > 1 sample TC+ (repeat or routine)
Note: Also applies to systems on quarterly and annual monitoring schedules.
No samples collected for compliance period
Some but not all samples collected for compliance period
No follow-up samples collected after a TC+ sample or no speciation
Some but not all follow-up samples collected or speciated for compliance period
Code
21
22
23
24
25
26
DATE: November, 1995
RELEASE NO. 1
TCR-1
-------
Violation Type
Description
Code
Mflfc, Sanitary Survey
Fails to have a sanitary survey conducted at the required frequency:

CWS: by 6/29/94 and a min. of lx/5 yrs, thereafter
NCWS: by 6/29/99 and a min. of Ix/lOyrs, thereafter , •

Note: Only necessary to PWSs collecting < 5 samples, or these systems must
collect 5 samples.
28
C. Public Notification

Any system that incurs a TCR violation is subject to public notification (PN) requirements contained
in §141.32. Mandatory health effects language in §§141.32(e)(l 1) or (12) must be included in PN
materials when a system incurs a "22" (monthly MCL) or "21" (acute MCL) violation, respectively.
Failure to meet PN delivery and content requirements, result in a PN violation. Information for the
data elements listed in Table TCR-2 must be reported for violations of § 141.32 requirements.
Additionally, the following values must be specified: Cl 103 = 3100 and Cl 105 = 06.
D. Enforcement Actions

Any formal enforcement actions taken to address a violation must be reported to FRDS/SDWIS.
EPA also encourages the reporting of informal enforcement responses, since the vast majority of
these violations are resolved through informal actions. Enforcement actions are reported in the
FRDS C1200, ENFORCEMENT-DATA record, and the SDWIS/FED ENFORCEMENT_ACTION
Entity. In addition, enforcement actions must be linked to the violations which they address.
Enforcement linking is achieved in the FRDS C1280 record, ENF-VIOLATIONS. For more detail
on which enforcement actions must be reported to FRDS/SDWIS and the linking of enforcement
actions to violations, refer to Section 7, entitled, Reporting Enforcement Information.
DATE: November, 1995
RELEASE NO. 1
TCR-2
-------
Table TCR-2: Required Reporting Elements for TCR Violations
FRDS
Element
No./Name
C1101:
VIO-ID
C1103:
VIO-CON-
TAM
C1105:
VIO-TYPE
C1107:
VIO-
COMP-
PERIOD-
BEG1N
DATE
C1109:
VIO-
COMP-
PERIOD-
ENDDATE
Cllll:
VIO-
COMP-
PERIOD-
MONTHS
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
VIOLATIONS
D GENERATED_ID_SOURCE_CODE
VIOLATIONS
STATE -
ASGN IDENTIFICATION_NUMBER
VIOLATIONS
TFRCNTMN CODE
VIOLATION
TFRVTYPE_CODE
VIOLATION
COMPLIANCE PERIOD BEGIN_DATE
VIOLATION
COMPLIANCE PERIOD END DATE
VIOLATION
Not converted; can be determined from Cl 107
and Cl 109
Definition
Code used to
identify the
violation
Contaminant
ID for the
violation
The type of
violation
Date compli-
ance period
begins
Date compli-
ance period
ends
Duration of
compliance
period in
months
Code Values/
Reporting Format
yynnnnn, where
yy = Fed FY in which
state became aware of
violation
nnnnn = assigned by
State or generated by
FRDS/SDWIS
3100
Refer to Table TCR-1
mmddyy
mmddyy
3 digits, ranging from
001 - 120, depending
on violation type
Other .
When the VIO-ID
is generated by
FRDS, the first
position contains
the letter
"V"
Not reported for
sanitary survey
M/R ("28")
FRDS/SDWIS-
EED will value
C1131 VIO-
MAJOR-VIOLA-
TION-FLAGfor
violations "23" -
"26". Also see
Note!.

Optional, if
Cllll is reported
Optional, if
Cl 109 is report-
ed. Also see Note
2.
Note 1: If multiple TCR M/R violations (i.e., types "23" - "26") are incurred by a PWS during the same compliance period, the
state is only required to report one, in the following order of importance:

1st- "25", Major Repeat M/R
2nd- "23", Major Routine M/R
3rd- "26", Minor Repeat M/R
4th- "24", Minor Routine M/R

A sanitary survey ("28") violation should always be reported even if it occurs in the same compliance period as the other
DATE: November, 1995
RELEASE NO.
TCR-3
-------
TCRM/R violation types orMCL violation(s). Similarly, an MCL violation should always be reported, and if both a
monthly ("22") and acute MCL violation ("21") occur during the same compliance period, both should be reported.

Note 2: a,) For violation types 21 - 26, Cl 111 would =

"001" for monthly monitoring
"003" for quarterly monitoring
"012" for annual monitoring

b.) For violation type 28, Cl 111 would -

"042" for CWSs or "102" for NCWSs which did not have sanitary survey by 6/29/94 or 6/29/99, respectively
(i.e., 42 or 102 months from TCR effective date of 1/1/91)

"060" for CWSs and "120" for NCWSs which did not have repeat sanitary survey within 5 or 10 years of last
survey, respectively (or number of months representing frequency with which states require sanitary surveys)

Note 3: A system is considered to have returned to compliance for a "28" violation when it begins collecting 5 or more
samples/month or has had a sanitary survey.

DOCUMENT SOURCES

Primary Source: Total Coliform Ruk ;'TCR) Implementation Manual, Appendix D - FRDS
Reporting,
March 1991

Secondary Sources:
Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994
(original release: EPA 812-B-93-003, January 1993)

June 1994 memorandum, entitled, "Requirement for Public Water System which Takes Fewer than
Five Total Coliform Samples per Month to Undergo a Sanitary Survey

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 RELEASE NO. 1
TCR-4
-------
2. SURFACE WATER TREATMENT RULE
BACKGROUND

The Surface Water Treatment Rule (SWTR), promulgated June 1989, established criteria under which
filtration is required for public water systems (PWSs) supplied by surface water (sw) sources or ground water
under the direct influence (GUDI) of sw. This regulation also establishes treatment techniques (TT) in lieu of
maximum contaminant levels (MCL) for Giardia lamblia. viruses, heterotrophic plate count, bacteria,
Legionella. and turbidity. Systems using exclusively ground water (gw) sources that are not GUDI are
excluded from regulation under SWTR.

Under the SWTR, systems initially fall into one of three categories, the first of which can include filtering
systems with inadequate filtration:
• Filtered
• Unfiltered, required to filter
• Unfiltered, successfully avoiding filtration

The SWTR reporting requirements are based primarily on these three categories (i.e., reporting associated
with the requirement to filter, source information, and violations). A system's filtration status can change
over time. For example, an unfiltered system that is successfully avoiding filtration may be triggered into
filtration and temporarily be categorized as "unfiltered, required to filter". Unfiltered systems that are
required to filter have a maximum of 18 months to install filtration. Once filtration is in place, these systems
become filtered systems. Any changes in the filtration status of a system must be reported to FRDS/SDWIS-
FED. The filtration status is recorded in the FRDS C480, Source record. Refer to Tables SWTR-3 and
SWTR-4 for information on how to report this requirement.
FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions

1. Filtration Requirements

• States were initially required to identify by December 1991 the sw systems that must install
filtration and to report the date the system was informed of the requirement to install
filtration and any reason(s) for this requirement.

• The Filtration Requirement Determination is recorded in the C3000 record [i.e., Variance-
Exemption-Data record]. Refer to Tables SWTR-1 & SWTR-2 for details on how to report
this determination.

• The Filtration Requirement Determination is also required to be reported for any system
that:

was successfully avoiding filtration but subsequently has been triggered into the
filtration requirement, and
have been determined to have GUDI source(s) that require filtration
DATE: November, 1995 RELEASE NO. 1
SWTR-1
-------
• The Filtration Requirement Determination is not required to be reported for system with
filtration in place prior to 12/91

2. GUDI Systems

• States must determine whether each gw or purchased gw source is GUDI by:

6/94 for CWSs
6/99 for NTNCWSs

• GUDI determinations are/were due to FRDS/SDWIS-FED by 9/94 for CWSs and 9/99 for
NTNCWSs

• Within 6 months of the GUDI determination, systems must begin meeting unfiltered M/R
requirements, or State-determined requirements

• Within 18 months of the GUDI determination, State must decide which GUDI systems must
filter

• Refer to Tables SWTR-3 and SWTR-4 for reporting of GUDI determinations
Table SWTR-1:
Required Reporting Elements Associated with Filtration Requirement (FR)
Determinations
FRDS Element
No./Namc
C3001: VE-ID
C300S: VE-
RECORD-
TYPE
C3007: VE-
EFFECTTVE-
DATE
C3019: VE-
REASON-
CODE
SDWIS Attributes
Entity
FEDERAL FISCAL YEAR NUMBER
DEVIATION
STATE -
ASGN IDENTIFICATION NUMBER
DEVIATION
D GENERATED ID SOURCE CODE
MILESTONE EVENT
TYPE CODE
MILESTONE_EVENT
ACTUAL DATE
MDLESTONE_EVENT
REASON_CODE
MILESTONE_EVENT
Definition
ID for the filtration
requirement record
Value that repre-
sents if C3000 is a
variance, exemp-
tion, or "other
event"
Date PWS was
informed of require-
ment to filter
Code(s) that repre-
sent why State
required filtration
Code Values/
Reporting Format
yynnnnn, where
yy = Fed FY in which PWS was in-
formed of filtration requirement
nnnnn = assigned by State or generat-
ed by FRDS
"FR" - Filtration Requirement Re-
cord
mmddyy
Refer to Table SWTR-2 below for
codes
DATE: November, 1995
SWTR-2
RELEASE NO. 1
-------
Table SWTR-2:
FKDS C3019 Codes (Reason Filtration is Required)/SDWIS
MILESTONE_EVENT, REASON_CODE
===
C3019
<~W1«»
==
21
22
31
32
' 33
34
oc
1 !^=^=
Description
=======================
Source Water Coliform
Source Water Turbidity
Failure to Meet Daily CT
Residual Disinfectant < 0.2 mg/1
Residual Disinfectant Concentration Not Detected
Lack of Redundant Disinfection Components
Watershed Control is Inadequate

C3019
Code
36
37
41
42
1 43
51
52
"
Description
On-site Inspection Warrants Filtration
Waterborne Disease Outbreak
Violation of TCR MCL, Monthly/Acute
Violation of TTHMMCL
Violation of Turbidity MCL
PWS Opts to Install Filtration
State Requires Filtration (independent of SWTR)

Note: All codes that apply must be reported.
B. Source Records

States must report the type of treatment applied to each sw or GUDI source (including purchased sources).
Table SWTR-3 contains the information that is required to be reported either by source or at the treatment
plant level. This information was due to FRDS for sw sources by March 1992 and forCWS.usingGUDI by
September 1994 For NTNCWSs using GUDI, these data will be due by September 1999. Table SWTR-4
lists the additional data elements that are required.for GUDI systems. These reporting requirements (or any
under SWTR) do not apply if a system uses solely ground water.

Table SWTR-3: Required Reporting Elements for Treatment Applied at the Source or Plant
==============
FRDS Ele-
ment
No./Name
=========
C401: PWS-
SE-ID
C481: PWS-
SE-TREAT-
MENT-1D
——=—=============================
SDWIS Attributes
Entities
'
STATE ASGN IDENT_CD
WATER SYSTEM FACILITY
STATE -
ASGN IDENTIFICATION NUMBER
TREATMENT OBJ PROCESS ASGMT
STATE -
ASGN IDENTIFICATION_NUMBER
MILESTONE EVENT
STATE -
ASGN rbENTMCATIONJNUMBER
DEVIATION
===============
Definition
===============
The source or
plant ID
IDs specific
treatment at a
source
Code Values/
Reporting Format
3 digits
2 digits
Other
Each source
of a PWS has
a unique
C401and
C48 lvalue,
which may be
generated by
FRDS/-
SDWIS
DATE: November, 1995
SWTR-3
RELEASE NO. 1
-------
FRDS Ele-
ment
No./Name
C483: PWS-
SE-TREAT-
MENT-OB-
JECTTVE

C485: PWS-
SE-TREAT-
MENT-PRO-
CESS

SDWIS Attributes
Entities

PRIMARY T-
REATMENT INDICATOR CODE
TREATMENT_OBJ_PROCESS_ASGMT

TREATMENT OBJ PROCESS_ASGMT
TINTRPRO_CODE

Definition

IDs specific
objective to be
obtained
through treat-
ment

IDs a specific
treatment pro-
cess used at a
source or plant

Code Values/
Reporting Format

"P" - Particulate
Removal

"N"- No treatment
at source

"348" -Filtered

"349"-Unfiltered,
successfully avoid-
ing
"350"-Unfiltered,
required to filter

"996"-SWTR,
seller's responsibility

"351" -Not subject
toSWTR

Other

Other treat-
ment codes
maybe
applicable
[See Table
IDO5 of the
Data Element
Dictionary
(DED)-
version2.12]
Other objec-
tives may
apply (See
Table IDO4-
DED2.12)
A C483 code
of "P" cannot
be paired
with a C485
code of
"349", "350",
"996", or
"351".
Also refer to
Notes 1-4,
below this
table.
Note 1: P348 docs not need to be reported if other filtration treatment codes have already been reported for the source or treatment
plant (i.e., C483/C485 codes: P341, P342, P344 -P347).

Note 2: For N350 systems (unfiltered, required to filter), State also must report Filtration Determination Requirement information
indicated in Tables SWTR-1 and SWTR-2.

Note 3: Code N996 is applicable to purchased systems, where the seller is responsible for the filtration requirements.

Note 4: Code N351 is used for systems that have both sw and gw sources, where at least one gw source is not intermixed with sw.
This code only should be reported for each source or treatment plant using or treating solely gw. This is different than a PWS that has
only gw sources and no sw sources; for these system no SWTR reporting requirements apply.
DATE: November, 1995
RELEASE NO.
SWTR-4
-------
Table SWTR-4:
Additional Required Reporting Elements for PWSs Determined to Have
GUDI Sources
FRDS
Element
No./Name
C405:
PWS-SE-
RECORD-
TYPE
C407:
PWS-SE-
CODE
C411:
PWS-SE-
SELLER-ID
SDWIS Attributes
Entities
TYPE CODE
WATER_SYSTEM_FACILITY
WATER TYPE CODE
WATER_PURCHASE
Represented by relationship
between 2 WATER SYSTEMS
via the WATER_PURCHASE
entity type
Definition
Code value that repre-
sents whether all data
elements in C400 data
record correspond to
source or treatment
plant
Code that represents the
source type
Seller's PWS ID
Code Values/
Reporting Format
"P"- Plant/ Facility •
Record .
"S" - Source Record
"Y"- GUDI, non-pur-
chased
"Z"- GUDI, purchased
ssxxxxxxx, where:
ss = 2-digit State abbre-
viation &
xxxxxxx = seller's ID
Other
Only required if in-
serting a new source
record. State has
option of reporting
by plant or at source
level
This code can only
be reported at the
source level.
Only specified if
source is purchased
Note: FRDS/SDWIS-FED will automatically change the Primary Source (Cl 19) from a "G" to a "Y" or from a "W" to a "Z", if a
system has:
1. no permanent sw or purchased sw source, but had a permanent GUDI source, or
2. has a temporary GUDI source and has no temporary sw sources or permanent gw sources.
c.
Violations
To simplify reporting under the SWTR, multiple monitoring violations were aggregated into 2 types of M/R
violations and multiple treatment technique violations into 1 type. Reporting of violations is done at the PWS
level. All other SWTR reporting is done at the source or treatment plant level, except where a system has an
unfiltered and filtered source. Violations at both of these sources would be reported. The reporting
requirements for SWTR violations are explained in Table SWTR-5.
DATE: November, 1995
RELEASE NO. 1
SWTR-5
-------
Table SWTR-5:
Required Reporting Elements for SWTR Violadmts
FRDS Element
No./Name
C1101:VIO-ID
C1105: VIO-
TYPE
C1107: VIO-
COMP-PERIOD-
BEGINDATE
C1127: VIO-
SAMPLES-RE-
OUIRED
C1129: VIO-
SAMPLES-
TAKEN
C1131: VIO-
MAJOR-VIO-
LATION-FLAG
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
VIOLATION
D GENERATED ID SOURCE CODE
VIOLATION
STATE ASGN IDENTmCATION NUMBER ..
VIOLATION
TFRVTYPE CODE
VIOLATION
COMPLIANCE PERIOD BEGIN .DATE
VIOLATION
REQUIRED SAMPLE NUMBER
VIOLATION
SAMPLE TAKEN QUANTITY
VIOLATION
MAJOR VIOLATION INDICATOR CODE
VIOLATION
Code Values/
Reporting Format
yynnnnn, where
yy = Fed FY in which
state became aware of
violation
nnnnn = assigned by
State or generated by
FRDS/SDWIS
"31" -M/R for
Unfiltered PWSs
(both avoiding and
required to filter)
"36" -M/R for
Filtered PWSs
"41" - Treatment
technique (TT) vio-
lation
(See Note 1 below
end of table)
mmddyy
4-digit integer
4-digit integer
"Y" = Major
"N"= Minor
Other

A PWS could incur
more than one 31,36,
or 41 violation per
month. Only one of
each type should be
reported each month
(major M/R should be
reported over minor
M/R). An M/R and
TT violation occurring
in the same month
should both be re-
ported.
1st day of month in
which violation occurs
Applies to "31" &
"36" violations only
Cl 127 and Cl 129 are
only required if Cl 131
is not reported
Applies to "31" &
"36" violations only,
optional if Cl 127 &
Cl 129 are reported
(Also see Note 2
below)
Note 1: The "old" turbidity requirements under Sections 141.13 and 141.22 apply to those few systems for which a requirement to
filter decision was made prior to 12/30/91, but which have not yet installed filtration. For these systems, Cl 103, VIO-
CONTAMINANT - "0100" and Cl 105 = "02" for an MCL violation or "03" for M/R violations.

Note 2: Major violation ~ takes < 10% of required samples per compliance period

Minor violation - takes > 90% of all required samples, but less than 100%

Where, required samples for:
DATE: November, 1995
RELEASE NO. 1
SWTR-6
-------
\3nfiltered systems = source water coliform, source water turbidity, CT value determination, and entry point and
distribution system disinfection residual monitoring

Filtered systems = finished water turbidity, and entry point and distribution system disinfection residual monitoring '

Note 3: The Contaminant Code (ERDS Cl 103) for the violation, is not reported for any SWTR violation, but is reported for related
public notification violations as discussed in paragraph D below.

Note 4: The Cl 111, Duration of Compliance Period in months, is not required because all SWTR violations are 1 month in
duration.

D. Public Notification

Section 141.32 requires that public notification (PN) be delivered whenever a system incurs an MCL,
M/R, or TT violation. For the SWTR, PN is required when a system incurs an M/R ("31" or "36") or
TT violation ("41"). Mandatory health effects language, contained in Section 142.15(e)(10), must be
included in PN materials delivered for those filtered systems that violate the treatment requirements
for filtration and disinfection (i.e., incur a "41" violation). Failure to meet the PN content and
delivery requirements must be reported to FRDS/SDWIS. The FRDS Cl 103, contaminant code, for
SWTR PN violations = 0200. The FRDS Cl 105, violation type code, for PN is "06".

E. Enforcement Actions

Formal enforcement actions taken to address SWTR violations must be reported to FRDS/SDWIS,
regardless of whether EPA or the State undertakes the action. The Regions are responsible for
reporting all EPA formal actions. EPA also encourages the reporting of informal enforcement
actions taken in response to SWTR violations, although such reporting is not required.

The FRDS C1200 ENFORCEMENT-DATA record and SDWIS/FED ENFORCEMENT_ACTION
Entity are used to report enforcement action information. See Table ENF-1 in Section 7 entitled,
Reporting Enforcement Information, for a description of the C1200 data elements for which
information must be provided and a list of formal and other enforcement actions which are required
to be reported to FRDS/SDWIS. In addition, these enforcement actions must be linked to the
violations that they address. For more detailed information regarding this linking, see Section 7,
Reporting Enforcement Information.

DOCUMENT SOURCES

Primary Source: Detailed FRDS Reporting Guidance for the SWT and TC Rules (including
Appendix D, March 1991

Secondary Sources:
Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994
(original release: EPA 812-B-93-003, January 1993)

Modifications to the FRDS Reporting Requirements for the SWT Rule, January 1992
FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 RELEASE NO. 1
SWTR-7
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995 RELEASE NO. 1
SWTR-8
-------
3. LEAD AND COPPER RULE
BACKGROUND
The Lead and Copper Rule (LCR), which was promulgated on June 7, 1991, established treatment technique
(TT) requirements when lead and/or copper exceed certain levels referred to as action levels. An exceedance
occurs when more than 10 percent of the samples collected are greater than the action level of 15 parts per
billion (ppb) for lead or 1.3 parts per million (ppm) for copper. Unlike other drinking water regulations,
exceeding the lead and/or copper action level is not a violation. Instead, this exceedance triggers one or more
of the following TT requirements: public education, corrosion .control treatment, source water treatment, and
lead service line replacement.

Lead and copper results are expressed as the 90th percentile level, which is the 90th highest sample result.
For a system collecting 10 samples, this would be the 9th highest lead or copper sample result obtained
during a monitoring period. 90th percentile values are calculated using all valid samples collected during a
compliance period.

The LCR reporting requirements are based primarily on reporting information about various milestones
associated with the LCR and violations of LCR requirements. These requirements are described in more
detail below.
FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions/Milestones

Section 142.15 of the LCR contains state reporting requirements. Most of these requirements
represent LCR milestone events that are tracked in the FRDS C800 PWS-MILESTONE-EVENT
record and the SDWIS/FED MILESTONE_EVENT Entity. Some of these milestones denote state
decisions associated with the LCR [e.g., systems for which the state has designated or approved
optimal water quality parameters (WQPs)]. These state decisions are considered under the LCR to
be federally enforceable. Table LCR-1 below contains a description of the milestone data that must
be reported to FRDS/SDWIS-FED.
Table LCR-1: Required Reporting Elements Associated with LCR Milestones
FRDS Element
No./Name
C801: PWS-MILE-
STONE-ID
C803: PWS-MELE-
STONE-DATE
SDWIS Attributes
Entities
D GENERATED ID SOURCE CODE
MILESTONE EVENT
STATE -
ASGN roENTmCATIONJNUMBER
MILESTONE EVENT
ACTUAL DATE
MILESTONE_EVENT
Definition
Alphanumeric value
used to uniquely
identify a specific
milestone
Date associated with
the milestone occur- .
rence
Code Values/
Reporting Format
nnnn
See Note 1 on the
next page
mmddyy
See Note 2
DATE: November, 1995
LCR-1
RELEASE NO. 1
-------
FRDS Element
No^Nsmc
C805: PWS-MDLE-
STONE-CODE
C81S: PWS-MILE-
STONE-VALUE
SDWIS Attributes
Entities
TYPE CODE
MILESTONEJiVENT
MEASURE
MILESTONEJEVENT
Definition
Code that represents a
specific milestone
occurrence
See Note 3 on the next
page
Code Values/
Reporting Format
Refer to Table LCR-2 .
for a list of valid
codes '
Numerical value with
a maximum of 7
whole digits and 8
digits after the deci-
mal
NOTE 1:

NOTE 2:

NOTES:
NOTE 4:

NOTES:
When the PWS-MELESTONE-ID is generated by FRDS, the first position contains the letter M.

For action level cxceedances, the milestdnE-date is the last day of the monitoring period. For all other milestone
events, the milestone date is the actual date of the event.
Data must be provided for the PWS-MILESTONE-VALUE for three LCR milestones. When the lead action
level exceedance milestone is reported, the 90th percentile sample value must be recorded in the PWS-
MILESTONE-VALUE data element. When the copper 90th percentile value is exceeded, the sample value must
be recorded n the PWS-MILESTONE-VALUE data element. The PWS-MILESTONE-VALUE is also used to
record an accelerated state-specified line replacement rate when the lead service line replacement milestone is
reported.

States have the option of reporting comments associated with a milestone in the C813 record, PWS-
MELESTONE-COMMENT.

Among other LCR requirements, the § 142.15 requirements are currently being evaluated by an EPA/State work
group charged with identifying improvements in the rule's implementation. Consequently, these requirements
may be modified at a later date.
Table LCR-2: FRDS C805 Codes (PWS Milestone Codes)/SDWIS MILESTONE_EVENT, TYPE-
CODE
C805
CU90
PB90
CCSR
CCSC
OTDE

Description
Conner action level exceedance
Lead action level exceedance
Designates systems required to conduct a corrosion
control treatment study
Designates systems that have completed a corrosion
control treatment study
Indicates systems for which the state has designated or
approved optimal corrosion control treatment (OCCT)
C805
Code
OTIN
WQPS
STDE
STIN
MPLS
Description
Indicates systems that have installed OCCT
Indicates systems for which the state has designated
or approved optimal water quality parameters
Indicates systems for which the state has designated
or approved source water treatment (SOWT)
Indicates systems that have installed SOWT
Indicates systems for which the state has designated
or approved maximum permissible levels for lead
and copper in source water
Denotes systems required to conduct lead service line replacement
DATE: November, 1995
LCR-2
RELEASE NO. 1
-------
B.
Sample Data
Section 142.15 requires the reporting of 90th percentile lead values for all large systems, and for
those medium and small systems that exceed the lead action level. Ninetieth percentile lead sample
data are to be reported to EPA using the C2100 database record (SAMPLE-DATA). FRDS/SDWIS-
FED will automatically generate the C800 PWS-MILESTONE-EVENT record for those lead
ninetieth percentile values that exceed the action level. However, if the state chooses to provide data
for the C800 record, FRDS/SDWIS-FED will not duplicate information in the FRDS C800 database
record or the SDWIS MILESTONE_EVENT Entity. Ninetieth percentile copper values are only
required to be reported when the copper action level is exceeded. Copper 90th percentile values that
exceed the action level are reported to the FRDS C800 milestone record and not to the FRDS C2100
database record. Table LCR-3 below provides a description of the data elements, contained in the
C2100 database record, that are required when any lead 90th percentile data are reported (i.e.,
exceedances or non-exceedances of the action level).
Table LCR-3: Required Reporting Elements Associated with Lead Sample Data
FRDS Element
No /NHHIC
C2101: SAM-
PLE-ID
C2103: SAM-
PLE-BEGIN-
DATE
C2105:
SAMPLE-END-
DATE
C2107:
SAMPLE-CON-
TAMINANT-
CODE
C2111:
SAMPLE-ANAL-
YSIS-RESULT
SDWIS Attributes
Entities
D GENERATED_ID_SOURCE_CODE
SAMPLE
STATE ASGN IDENTMCATION_NUMBER
SAMPLE
COMPLIANCE PERIOD_BEGIN_DATE
.SAMPLE
COMPLIANCE PERIOD END_DATE
SAMPLE
TFRCNTMN CODE
SAMPLE_ANALYTICAL_RESULT
MEASURE
SAMPLE_ANALYTICAL_RESULT
. Definition
Numeric value used to
uniquely identify a
specific sampling oc-
currence for lead
Date associated with
the first day of the
monitoring period in
which lead 90th per-
centile data was ac-
quired
Date associated with
the last day of the
monitoring period in
which lead 90th per-
centile data was ac-
quired
Code indicating the
contaminant for which
sample data has been
reported
Value representing
90th percentile lead
value
Code Values/
Reporting Format
nnnnn
mmddyy
mmddyy
PB90
Numerical value with
maximum of 7 whole
digits and 8 digits
after the decimal,
expressed in mg/1
NOTE: The SAMPLE-ID may be assigned by the state or generated by FRDS/SDWIS-FED. When the SAMPLE-ID is generated by
FRDS/SDWIS-FED, the first position contains the letter S.
DATE: November, 1995
RELEASE NO.
LCR-3
-------
Violations

Under the LCR, violations are categorized as either monitoring and reporting (M/R) violations or TT
violations. There are 15 types of LCR violations, six of which are M/R violations and the remaining
nine are TT violations. See Table LCR-4 for an itemized list of these violations and their
corresponding FRDS/SDWIS-FED codes. For a detailed description of LCR violations, see the
discussion beginning on page 21 of the "Lead and Copper Rule, Definitions and Federal Reporting
for Milestones, Violations, and SNCs," May 1992.

Table LCR-4 also contains the data elements for .which FRDS/SDWIS-FED will provide default
values, as well as the default values listed for each violation type. FRDS/SDWIS-FED can generate
these values based on information about a violation or partial information with which it is supplied.
For example, a value of 6 months is automatically provided for the FRDS Cl 111 data element when
an initial lead and copper tap monitoring and reporting violation is reported. FRDS/SDWIS-FED
will also perform range checks of compliance date information to ensure that violations are reported
for the appropriate time frame.
Table LCR-4: LCR Violation Codes/Default Values
Violation
Code
51
52
53
54
55
56
57
58
59
60
61
62
63
64

Violation
Description
Initial Lead and Copper Tap M/R
Follow-up or Routine Lead and Copper Tap M/R
Initial WQP M/R
Follow-up or Routine Entry Point WQP M/R
Follow-up or Routine Tap WQP M/R
Initial, Follow-up, or Routine Source Water M/R
OCCT Study/Recommendation
OCCT Installation/Demonstration
WQP Entry Point Noncompliance
WQP Tap Noncompliance
SOWT Recommendation
SOWT Installation
MPL Noncompliance
Lead Service Line Replacement

Data Element/Default Value
C1103
5000
5000
5000
5000
5000
5000
5000
5000
5000
5000
5000
5000
C1109
6 months later than Cl 107
None
6 months later than Cl 107
3 months later than Cl 107
Cllll
6 months

6 months
3 months
None
None
None
24 months later than Cl 107
3 months later than Cl 107
None
6 months later than Cl 107
24 months later than Cl 107

24 months
3 months

6 months
24 months
No default values are provided for this violation type
5000
5000
12 months later than Cl 107
12 months
None
DATE: November, 1995
RELEASE NO. 1
LCR-4
-------
Table LCR-5: Required Reporting Elements for LCR Violations
FRDS Element
No./Name
C1101:VIO_ID
C1103:
VIO-CONTAMI-
NANT
C1105:
VIO-TYPE
C1107: VIO-
COMP-PERI-
OD-BEGBSF
DATE
C1109: VIO-
COMP-PERI-
OD-END-DATE
Cllll: VIO-
COMP-PERI-
OD-MONTHS
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
VIOLATION
D GENERATED ID SOURCE CODE
VIOLATION
STATE -
ASGN IDENTIFICATION NUMBER
VIOLATION
TFRCNTMN CODE
VIOLATION
TFRVTYPE CODE
VIOLATION
COMPLIANCE PERIOD BEGIN DATE
VIOLATION
COMPLIANCE PERIOD END DATE
VIOLATION
Not converted; can be determined from
C1107andC1109
Definition
Value used to
uniquely identify
a specific
violation
Code used to
denote the con-
taminant for
which a violation
has been
incurred
Code used to
denote type of
LCR violation
Date compliance
period begins
Date compliance
period ends
Value denoting
the number of
calendar months
in a compliance
period in which a
PWShas
incurred a viola-
tion
Code Values/
Reporting Format
yynnnnn, where
yy = Fed FY in
which state became
aware of violation
nnnnn = assigned
by State or generated
byFRDS/SDWIS
5000 for all viola-
tions except "63."
See Note 1 below.
See Table LCR-4 for
a list of valid codes
mmddyy
mmddyy
3-digit integer
Other
When the VIO-
ID is generated
by FRDS, the
first position
contains the
letter V

See Note 2
below
NOTE 1: The VIO-CONTAMINANT code of 5000 is automatically generated by FRDS/SDWIS-FED for most LCR
violations, except MPL and public notification noncompliance. For MPL noncompliance a 1030 value for lead
and a 1022 value for copper should be specified by the state for the VIO-CONTAMINANT data element. For
public notification noncompliance, the 5000 value must be provided by the state.

NOTE 2: FRDS/SDWIS-FED will automatically generate a value for Cl 109 (SDWIS: COMPLIANCE_-
PERIOD_END_DATE), and Cl 111 for many LCR violations based on other information provided. See Table
LCR-4 for a list of LCR violations for which FRDS/SDWIS-FED generates these values. When FRDS/SDWIS-
FED does not generate these values, only Cl 109 or Cl 111 is required to be reported because FRDS/SDWIS-
FED will generate the corresponding value.
DATE: November, 1995
RELEASE NO. 1
LCR-5
-------
D. Public Notification

Any system that incurs an LCR violation is subject to public notification requirements, which are
codified in § 141.32. Information for the data elements listed in Table LCR-5 must be reported for
violations of § 141.32 requirements. Additionally, the following values must be specified: Cl 103 =
5000 and Cl 105 = 06.
E. Enforcement Actions

M/R and TT violations of LCR requirements must be reported as described in Table LCR-5. In
addition, any formal enforcement actions taken to address these violations must be reported to
FRDS/SDWIS, regardless of whether EPA or the State undertakes the action. EPA also encourages
the reporting of informal enforcement actions taken in response to LCR violations, although such
reporting is not required.

The C1200 ENFORCEMENT-DATA record is used to report enforcement action information. See
Table ENF-1 in Section 7, Reporting Enforcement Information, for a description of the C1200 data
elements for which information must be provided and a list of formal and other enforcement actions
which are required to be reported to FRDS/SDWIS.

When enforcement actions that address LCR violations are reported to FRDS, they must be linked or
associated with the violations they address. As with all other enforcement actions addressing
NPDWR violations, there are three ways to link enforcement actions to violations. For more detailed
information regarding this linking, see Section 7, Reporting Enforcement Information.

F. Return to Compliance

Information indicating that a water system is no longer incurring an LCR violation [or has returned to
compliance (RTC)] must be reported to EPA. RTC is reported as "compliance achieved" and is
among those enforcement actions that are required to be reported to FRDS/SDWIS. Compliance
achieved is also recorded in the C1200 ENFORCEMENT-DATA record. For a definition of RTC
for each of the 15 LCR violations, see Table LCR-6, or pages 19 and 20 of the "Lead and Copper
Rule, Definitions and Federal Reporting for Milestones, Violations, and SNCs", May 1992.
Although reporting of RTC is required for all LCR violations, it is especially important that it be
reported for initial lead and copper tap water M/R violations. The significant noncomplier definition
for this violation is tied to the length of time the system is out of compliance.
DATE: November, 1995 RELEASE NO.
LCR-6
-------
Table LCR-6: Definition of Compliance Achieved by LCR Violation Type
Violation Type
Initial Pb andCu Tap
JWXR(SeeNote2)
Follow-up Pb and Cu
TapM/R
Routine Pb and Cu Tap
M/R
Initial Tap & Entry
Point WQP M/R
Follow-up Entry Point
WQP M/R
Routine Entry Point
WQP M/R
Follow-up Tap WQP
M/R
Routine Tap WQP Mm
Initial Source Water
Mm
Follow-up Source
Water M/R
Routine Source Water
Mm
OCCT Study/ Recom-
mendation
' Definition of Compliance Achieved
System meets M/R requirements, during subsequent compliance period(s), for each 6-month
compliance period in which samples were not properly collected [§§ 141.86(aXd)(l)], analyzed [§
141.89(a)], or for which required information was not reported to the State [§ 141.90(a)].
System meets M/R requirements, during subsequent compliance period(s), for each 6-month
compliance period in which samples were not properly collected [§ 141.86(aXc) and (d)(2)],
analyzed [§ 141.89(a)], or for which required information was not reported to the State [§
141.90(a)].
System meets M/R requirements, during one subsequent compliance period, for one 6-, 12-, or 36-
month compliance period (whichever was in effect at the time of the violation) that includes proper
sample collection [§§ 141.86(aXc) and (d)(3) or (4)], analysis [§141.89(a)], and reporting to the
State [§ 141.90(a)l.
System meets M/R requirements, during subsequent compliance period(s), for each 6-month
compliance period in which samples were not properly collected [§§ 141 .87(a)(l),(2) & (b)],
analyzed [§ 141 .89(a)], or for which required information was not reported to the State [§
141.90(a)].
System meets M/R requirements, during subsequent compliance period(s), for any of the four
quarters in which samples were not properly collected [§§ 141 .87(a)(l),(2) & (c)], analyzed [§
141.89(a)], or for which required information was not reported to the State [§ 141.90(a)].
System meets M/R requirements, during one subsequent quarter, that includes proper sample
collection [§§ 141.87(aXl),(2),(d) and (e)], analysis [§ 141.89(a)], and reporting to the State [§
141.90(a)].
System meets M/R requirements, during subsequent compliance period(s), for each 6-month
compliance period in which samples were not properly collected [§§ 141.87(aXl),(2) and (c)],
analyzed [§ 14 1 -89(a)], or for which required information was not reported to the State [§
141.90(a)].
System meets M/R requirements, during a subsequent compliance period, for one 6- or 12-month
compliance period (whichever is in effect at the time of the violation) that includes proper sample
collection [§§ 141.87(aXl),(2), (d) and (e)], analysis [§ 141. 89(a)], and reporting to the State [§
141.90(a)].
System meets M/R requirements, during a subsequent compliance period, for the 6-month
compliance period in which samples were not properly collected [§§ 141 .88(a)(l) & (2) and (b)],
analyzed [§ 141.89(a)], or for which required information was not reported to the State [§
141.90(b)].
System meets M/R requirements, during a subsequent compliance period, for each 6-month
compliance period in which samples were not properly collected [§§ 141.88(aXl) & (2) and (c>
(e)], analyzed [§141 .89(a)], or for which required information was not reported to the State [§
141.90(b)1.
System meets M/R requirements, during a subsequent compliance period, for one 1-, 3-, or 9-year
compliance period (whichever is in effect at the time of the violation) that includes proper sample
collection [§§ 141.88(a)(l) & (2) and (d) or (e)], analysis [§ 141.89(a)], and reporting to the State
[§141.90(b)l.
System submits, during a subsequent compliance period, the OCCT recommendation [§§
141 .82(a) & 141 .90(c)(2)], completes and submits the OCCT study to the State [§§ 141 .82(c) &
141 .90(c)(3)], and provides any additional information to the State that is needed to make an
OCCT decision FS 141.82(dY2YI.
DATE: November, 1995
RELEASE NO. 1
LCR-7
-------
Violation Type
OCCT Installa-
tion/Demonstration
Entry Point WQP
Noncompliancc
Tap WQP Noncompli-
ancc
SOWT Recommenda-
tion
SOWT Installation
Source Water MPL
Noncompliance
Lead Service Line
Replacement
Public Education
.•••'•' Definition of Compliance Achieved : ;\ ;:';:«• •;:*"^i,;;v';<::
System properly installs and operates treatment [§ 14 1 .82(e)], submits certification of proper ' .
installation and operation [§ 141.90(oX4)], or demonstrates that OCCT already is in place [§§
141.81(bXlX3) an'd 141.90(cXDl.
System meets State designated or approved WQP values or ranges for one subsequent quarter [§
141.82(g)].
System meets State designated or approved WQP values or ranges for one subsequent 6-month
compliance period f§ 141.82(g)].
System submits SOWT recommendation to the State [§§ 141.83(aXl) & (bXl) and 141.90(d)(l)].
System properly installs and operates SOWT [§§ 141.83(bX3) & (5)] and/or submits certification
of proper installation and deration [§ 141.90(d)(2)].
System meets State designs 3d or approved MPL values, during a subsequent compliance period,
for one 1-, 3-, or 9-year compliance period (whichever is in effect at the time of the violation) [§
141.83(bX5)].
System meets the 7% replacement rate (or higher if required by the State) by any one or a
combination of:
• demonstrates replaced lines under its limited control [§ 141.84(e)and 141.90(eX4)]
• replaces entire line [§§141 .84(a) & (b)]
• shows the lead service line contributes < 15 ppb of lead [§ 141 .84(c), and
Reports all required information to the State [§ 141.90(e)].
System delivers one round of public education [§§ 141.85(a)-(c)], and submits a letter to the State
that demonstrates measures taken to meet these public education requirements [§ 141.90(f)].
NOTE 1: The actions needed to achieve compliance are not meant to replace other activities that are required to be
conducted under the rule for that time frame nor are they meant to indicate that a violation did not occur for the
system. Instead, they indicate that this violation no longer continues and should no longer be reported for the
system. Should the system again fail to meet subsequent requirements of the rule, another violation must be
reported.

NOTE 2: The violations in italics can result in a system reaching significant noncompliance status.
DATE: November, 1995
RELEASE NO. 1
LCR-8
-------
DOCUMENT SOURCES

Primary Source: •

Lead and Copper Rule, Definitions and Federal Reporting for Milestones, Violations', and SNCs,
May 1992.

Secondary Sources:

Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994
(original release: EPA 812-B-93-003, January 1993).

March 23,1993, memorandum from Abraham Siegel regarding Corrections to "Lead and Copper
Rule, Definitions and Federal Reporting for Milestones, Violations, and SNCs."

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 RELEASE NO. 1
LCR-9
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995 RELEASE NO.
LCR-10
-------
4. PHASE I, II, Iffi, AND V RULES
BACKGROUND
The Phase I, II, IIB, and V rules establish monitoring and reporting (M/R) and maximum contaminant level
(MCL) or treatment technique (TT) requirements for 66 chemicals contaminants in drinking water. These
regulations also establish M/R requirements for unregulated contaminants (refer to the summary on
Unregulated Contaminants). In general, the requirements of the phase rules apply to CWSs and NTNCWSs,
with two exceptions. First, the M/R and MCL requirements for nitrate and nitrate requirements also apply to
TNCWSs. Second, the fluoride requirements apply only to CWSs. Monitoring under the phase rules is
conducted at each entry point to the the distribution system and must be representative of well(s) or source
water after treatment, hi addition, compositing of up to 5 samples is allowed. The table on the next page
indicates the effective date, number of regulated contaminants, and monitoring requirements for each of the
phase rules.

Initial monitoring for the Phase I volatile organic chemicals (VOCs) was required to be completed by 12/88
for systems serving > 10,000 persons, by 12/89 for systems serving 3,300 - 10,000 persons, and by 12/91 for
systems serving < 3,300 persons. The Phase II rule promulgated the standardized monitoring framework
(SMF). The SMF standardized monitoring requirements within contaminant groups and synchronized
monitoring schedules across three contaminant groups: VOCs (including the Phase I VOCs), inorganic
chemicals (lOCs), and synthetic contaminants (SOCs). The SMF incorporates contaminants regulated under
all the phase rules. However, the monitoring requirements for asbestos, nitrate, and nitrite are different from
other Phase II and V lOCs because of their unusual characteristics.

The SMF establishes a 9-year "compliance cycle" which is comprised of three, 3-year "compliance periods".
The first period is 1993 -1995. During this compliance period, Phase II and IIB initial monitoring for all
systems and Phase V initial monitoring for systems serving > 150 service connections must be completed.
The second period spans from 1996 - 1998, during which systems serving < 150 service connections must
complete initial Phase V monitoring. The third period begins in 1999 and ends in 2001. States may specify
the year within the period that monitoring is required, hi addition, the SMF allows for waivers of contami-
nants other than nitrate and nitrite.
FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions

Previous sampling results can be used to satisify initial monitoring requirements ("grandfathering"
data) for Phase II/IIB (with the exception of nitrate and nitrite) or for repeat monitoring requirements
for Phase V. This provision has restrictions regarding how old the data can be. In addition, states
may grant waivers to reduce the frequency of monitoring for contaminants which had not been used
in the water supply area (i.e., use waiver) or if a source was not susceptible to contaminants based on
a vulnerability assessment and prior sampling results (i.e., susceptibility waiver). Waivers may
apply to the entire system or may be limited to certain sampling points. Waivers are not allowed for
nitrate and nitrite. Waiver decisions are not required to be reported to FRDS/SDWIS-FED.
DATE: November, 1995 RELEASE NO. 1
PHASE-1
-------
Table PHASE-1: Summary of Monitoring Requirements for the Phase I, II, IIB, and V Rules
Rule/Effective Date
No. of Contami-
nants
Monitoring Requirements w/o Waivers
Phase I

Effective: 1/9/89
8VOCs
Initial
sw: 4 consecutive quarterly samples
gw: 1 sample

Repeat
sw: quarterly, if no detects, can reduce to annual
gw: annual; if no detects for 3 years, can reduce to triennial

If detects, then monitor quarterly until reliably and consistently (R&C)
MCL (see note below for definition of R&C below the MCL)
below
Phase II/IIB

Effective: 1/30/91
9 IOCS,
10 VOCs, &
ISSOCs

total = 34

Note: SOCs exclude
3 aldicarbs for which
the MCLs were
stayed; part of cur-
rent unregulated list
VOCs/SOCs
Initial - sw & gw: 4 consecutive quarterly samples

VOC Repeat - sw & gw: quarterly if detects; annual if no detects +
gw goes to triennial if 3 consecutive yrs w/o detects

SOC Repeat - sw & gw: if detects, monitor quarterly
sw & gw: if no detects + > 3,300 persons, monitor 2x/3 years
if no detects + < 3,300 persons, monitor lx/3 years

IQCs (excluding asbestos, nitrate, and nitrite)
Initial - sw: annual; gw: triennial

Repeat - Same as initial, unless results are > MCL, system goes on quarter-
ly monitoring until R&C below MCL

IQCs - Asbestos
Initial - 1 sample

Repeat - if initial is:
< MCL, monitor during 1st 3 years of next 9-year cycle
> MCL, monitor, quarterly until R&C below MCL

Nitrate (No waivers allowed)
CWSs/NTNCWSs: sw - quarterly, gw - annually
reduce from quarterly to annuai if 4 consecutive quarters < 1/2 MCL
increase from annual to quarterly if> 1/2 MCL

TNCWSs: annual monitoring

Nitrite (No waivers allowed)
Initial - all systems: annual monitoring

Repeat - all systems:
< 1/2 MCL, repeat monitoring is at state discretion
> 1/2 MCL, quarterly until R&C below MCL, then annual
Phase V

Effective: 7/17/92
5 IOCS,
3 VOCs, &
ISSOCs

total = 23
Monitoring frequency is the same as for Phase II/IIB (excluding asbestos, nitrate, or
nitrite).
NOTE: Reliably and consistently below the MCL for sw =- 2 consecutive quarters below the MCL; for gw = 4 consecutive quarters below the
MCL.
DATE: November, 1995
RELEASE NO. 1
PHASE-2
-------
B.
Violations
Violations may be reported by system or by sampling point. If reporting by system, only one
violation type for a given contaminant during the same monitoring period is reported to
FRDS/SDWIS (major to be reported over minor violation), regardless if the violation occurs at
multiple sampling points. However, if reporting by sampling point and the same violation occurs at
multiple sampling points for the same contaminant for the same monitoring period, the state would
report all violations. This is different than a situation in which a system incurs different types of
violations or the same violation for different contaminants; in this situation all violations should be
reported regardless of whether reporting is done by system or sampling point. FRDS/SDWIS will
accept state violations (e.g., more frequent monitoring, confirmation samples for contaminants other
than nitrate and nitrite). However, reporting of state violations could result in a system's incorrectly
being determined to be a significant noncomplier (SNC). The table below indicates the required
reporting elements for a violation.
Table PHASE-2: Required Reporting Elements for Phase I, II, IIB, and V Rule Violations
FRDS Ele-
ment
No./Name
CHOI: VIO-
ID
C1103: VIO-
CONTAMI-
NANT
C1105: VIO-
TYPE
C1107: VIO-
COMP-PERI-
OD-BEGIN-
DATE
C1109: VIO-
COMP-PERI-
OD-END-
DATE
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
VIOLATION
D GENERATED ID SOURCE CODE
VIOLATION
STATE -
ASGN H)ENTMCATION_NUMBER
VIOLATION
TFRCNTMN CODE
VIOLATION
TFRVTYPE CODE
VIOLATION
COMPLIANCE PERIOD BEGIN DATE
VIOLATION
COMPLIANCE PERIOD END DATE
VIOLATION
Definition
Code used to
identify the
violation
Contaminant
ID for the
violation
The type of
violation
Date monitor-
ing period
begins
Date monitor-
ing period ends
Code Values/
Reporting Format
yynnnnn, where yy =
Fed FY in which state
became aware of
violation
nnnnn = can be
assigned by State or
generated by FRDS/-
SDWIS
Refer to Table
PHASE-3
"01" - single sample
MCL
"02" - average MCL
"03"- regular M/R
"04" - confirmation
M/R
"07" - TT violation
mmddyy
mmddyy
Other

See Note 1 at
the end of this
table
See Note 2 at
the end of this
table

May report
C1111,VIO-
COMP-PERI-
OD-
MONTHS
instead (See
Note 3 at the
end of table)
DATE: November, 1995
PHASE-3
RELEASE NO. 1
-------
FRDS Ele-
ment
No /Name
C1I11: VIO-
COMP-PERI-
OD-MONTHS
C1115:VIO-
AWARE-
DATE
C1123:VIO-
ANALYSIS
RESULT
C1131: VIO-
MAJOR-VIO-
LATION-
FLAG
C1143: VIO-
SE-ID
SDWIS Attributes
Entities
Not converted; can be determined from Cl 107
and Cl 109
AWARE DATE
VIOLATION
ANALYSIS RESULT MEASURE
VIOLATION
MAJOR VIOLATION_INDICATOR_CODE
VIOLATION
Represented by a relationship between VIOLA-
TION and WATER_SYSTEM_FACILITY
Definition
Period of time
in which
monitoring
was required
(in months)
Date state
became aware
of MCL vio-
lation
Analytical
result(s) that
caused the
]••/.'„':". violation
Indicates
whether vio-
lation is major
or minor M/R
violation
Source/entity
ID at which
the violation
was incurred
Code Values/
Reporting Format
3 digits number
between "001 " &
"108", depending on
monitoring frequency
mmddyy
maximum of 7 digits
to the right of the
decimal and 8 digits to
the left
"Y"- Major
"N"- Minor
3-digit number btwn
"001" & "949" - if
reporting by sampling
point
"000" - if reporting
by system
Other
May report
C1109,VIO-
COMP-PERI-
OD-END-
DATE instead
(See Note 3 at
the end of
table)
Applies to
"01"&"02
violations only
Applies to
"01"&"02
violations only
(See Note 4
below)
May report
C1129.VIO-
SAMPLES-.
TAKEN
instead (Sss
Note 5 beiw)

NOTE 1: Violations can no longer be reported using group contaminant codes. EPA plans to replace group contaminant
codes with individual violations for contaminants represented by a group contaminant code. For example, 2 VO8
which was used to report violations for the Phase I VOCs will be replaced with 8 individual M/R violations.

NOTE 2: Cl 105, violation type is defined as follows:

• "01", single sample MCL applies to systems monitoring on annual or less frequent basis.
• • "02", average MCL occurs when the average of the initial and confirmation sample exceeds the MCL,
or when the system is monitoring more frequently than once per year and the running annual average
exceeds the MCL.
• "03", regular M/R - failure to conduct initial, any repeat sampling, or to accurately report an analytical
result.
• "04", confirmation M/R applies to nitrate and nitrate only (for Federal violations) and occurs when
system exceeds nitrate and does not collect the required confirmation sample or does not report it
within required period of time. If a system fails to collect or report this required confirmation sample,
the state would still report the MCL exceedance to FRDS/SDWIS-FED based solely on the initial
monitoring results and this system would incur both an "01" and "04" violation.
• "07", treatment technique violation applies only to those systems using acrylamide and epichlorohydrin
as part of their treatment. This violation results from failure to certify annually that these chemicals are
being used as directed by the manufacturer or distributor.
DATE: November, 1995
RELEASE NO. 1
PHASE-4
-------
NOTE 3: Cl 111 equals "001" for confirmation sample M/R violations for nitrate, nitrite, and other State-required
confirmation sampling ("04"); "003" for quarterly sampling; "012" for annual monitoring; "036" for triennial
monitoring; "072" for monitoring every 6 years; and "108" for monitoring every 9 years.

NOTE 4: For single samples, the value reported for Cl 123, VIO-ANALYSIS-RESULT, would be the regular sample .
causing the violation. For nitrate/nitrite or for other contaminants where a confirmation sample was required,'
Cl 123 would equal the average of the initial and confirmation sample. If the confirmation sample were not
taken, Cl 123 would equal the initial sample result (system would also incur an "04" violation, confirmation
M/R). For systems monitoring less frequently than annually, Cl 123 would equal the running annual average.

NOTE 5: A major M/R = failure to collect any samples. A minor M/R = some but not all samples collected.
DATE: November, 1995 RELEASE NO. 1
PHASE-5
-------
Table PHASE-3: Phase I, II, IIB, and V Rule Contaminant Codes
Code
Description '
Inorganic Contaminants (lOCs)
Phase II/IIB
1010
1015
1020
102S
1035
1038
1040
1041
1045
1094

1024
1036
1074
1075
1085

Fluoride

Total Nitrate/Nitrite
Nitrate
Nitrite

Phase V

Nickel (Sec Note 1)

Thallium
Volatile Organic Contaminants (VOCs)
Phase I
2969
2976
2977
2980
2981
2982
2984
2990

2380
tvDichlorobcnzcne (1,3-Dichlorobenzene)
Vinyl chloride
1.1-Dichlorocthylcne (Dichloroethane)

Carbon tctrachloride (Tetrachloromethane)
Trichloroethylcne (TCE)

Phase II/IIB

cis-1 2-DicWorocthvlcnc
Code
Description
VOCs: Phase II/IIB (Continued)
2955
2968
2979
2983
2987
2989
2991
2992
2996

2378
2964
2985
Xylenes (total)
o-Dichlorobenzene
trans- 1 ,2-Dichloroethylene
1 ,2-Dichloropropane
Tetrachloroethylene
Monochlorobenzene (Chlorobenzene)
Toluene
Ethylbenzene
Styrene
Phase V
1 ,2,4-Trichlorobenzene
Dicbloromethane
1 , 1 ,2-Trichloroethane
Synthetic Organic Contaminants (SOCs)
2010
2046
2015
2020
2050
2051
2065
2067
2105
2110
2326
2383
2931
2946

2959
Lindane
Carbofuran
Methoxychlor
Toxaphene
Atrazine
Alachlor
Heptachlor
Heptachlor Epoxide
2,4-D
2,4,5-TP (Silvex)
Pentachlorophenol
Polychlorinated biphenyls (PCBs)
l,2-Dibromo-3-cWoropropane (DBCP)
Ethylene dibromide (EDB)

Chlorodane
Note: Arsenic (contaminant code 1005) is not regulated under the phase rules; however, EPA recommends that this contaminant
be incorporated into the SMF because its monitoring frequency of once every 3 years is similar to other chemicals in the
SMF.
DATE: November, 1995
RELEASE NO. 1
PHASE-6
-------
Note 1: The MCL for Nickel was remanded (June 29,1995 Federal Register, p.33928), therefore MCL violations are not currently
possible; monitoring requirements still apply.
Table PHASE-3 (Continued): Phase I,'II, IIB, and V Rule Contaminant Codes
Code
Description
SOCs (Continued)
PhaseV
2005
2031
2032
2033
2034
2035
2036
2306
Endrin
Dalapon
Diquat
Endothall
Glyphosate (Round-up)
Di(2-ethylhexyl)adipate
Oxamyl (Vydate)
Benzopyrene
Code
Description
SOCs (Continued)

2037
2039
2040
2041
2042
2063
2274

Phase II/IIB
Simazine
Di(2-ethylhexyl)phthalate
Picloram'
Dinoseb
Hexachlorocyclopentadiene
2,3,7,8-TCDD (Dioxin)
Hexachlorobenzene (HCB)

C. Return to Compliance

When a federal violation is incurred, it must be reported to FRDS/SDWIS. Further, states must
inform EPA when violations have been addressed and a system has returned to compliance (RTC).
RTC is defined for MCL, M/R and TT violations for the Phase rules below:

• MCL violation - subsequent monitoring shows system is below the MCL
• M/R violation - system is reporting in accordance with requirements
• TT violation - system submits required certification for acrylamide or epichlorohydrin.

RTC is reported to FRDS as "compliance achieved". Compliance achieved is represented by SOX
when RTC is reported by the State or BOX when reported by EPA. The SOX or BOX must be
linked to the violation that it resolved. Refer to Section 7, entitled, Reporting Enforcement
Information for details on how to report compliance achieved and the linking of enforcement actions
to violations.
D. Public Notification

Public notification (PN) is required when a system incurs an MCL, M/R, or TT violation.
Mandatory health effects language for chemicals is outlined in Section 141.32 (e) for MCL violations
of the Phase rules. This language must be published in the newspapers within 14 days and notice to
consumers within 45 days. Nitrate and nitrate MCL violations have an additional requirement of
electronic notification within 72 hours. Monitoring violations require notification in newspapers
within 3 months and every 3 months thereafter until the violation ceases. NTNCWSs have the option
of hand delivery or posting instead of newspapers and mailings. Failure to meet the PN requirements
must be reported. The Cl 105, violation type code, for PN is "06".
DATE: November, 1995
RELEASE NO. 1
PHASE-7
-------
E. Enforcement Actions

Formal enforcement actions takentto address violations of the Phase I, II, IIB, or V rules must be
reported to FRDS/SDWIS, regardless of whether C?A or the State undertakes the action. EPA also
encourages the reporting of informal enforcement a:. ,3ns taken in response to violations, although
such reporting is not required.

The C1200 ENFORCEMENT-DATA record is used to report enforcement action information. See
Table ENF-1 in Section 7, Reporting Enforcement Infonr-fion, for a description of the C1200 data
elements for which information must be provided and a lit "formal and other enforcement actions
which can be reported to FRDS/SDWIS. In addition, these enforcement actions must be linked to the
violations that they address. For more detailed information regarding this linking, see Section 7,
Reporting Enforcement Information.

DOCUMENT SOURCES

Primary Sources:

Phase II Implementation Guidance for FRDS, December 1991.

Secondary Sources:

Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994;
(original release: EPA 812-B-93-003, January 1993).

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.

Consolidated Rule Summary for the Chemical Phases, May 1994.
DATE: November, 1995 RELEASE NO. 1
PHASE-8
-------
5. UNREGULATED CONTAMINANTS
BACKGROUND
Monitoring and reporting (M/R) of unregulated contaminants is required under Section 1445 of the SDWA.
The purpose of unregulated contaminant monitoring (UCM) is to assist EPA in determining the occurrence of
unregulated contaminants in drinking water and whether future regulation is warranted. M/R requirements
were included for specific unregulated contaminants under the Phase I and II regulations, and continued under
Phase V.

The M/R requirements listed below apply to CWSs and NTNCWSs serving > 150 service connections and
only for those contaminants for which a waiver has not been granted. Unregulated contaminant monitoring
does not apply to TNCWSs. CWSs and NTNCWSs serving < 150 service connections are not required to
self monitor, but are required to send a letter to the State indicating they are available for monitoring. This
letter was due to the State by 1/1/91 for Phase I and by 1/1/94 for Phase II contaminants.

The 48 unregulated contaminants, remaining after the promulgation of Phase V are listed in Tables UCM-2
and UCM-3. At least one round of results is needed from non-discretionary contaminants (listed in Table
UCM-2); the remaining 14 are at State discretion (see Table UCM-3).
Rule/Effective
Date
No. of Contaminants
Monitoring Requirements w/o Waivers
Phase I

Effective: 1/9/89
51 (15 were discretionary)

(Refer to Group 3 contaminants in Table 2a
& Group 4 in Table 2b)
Surface Water: 4 consecutive quarterly samples/source

Ground water: 1 sample/entry point

Initial due end of 1988,1989, or 1991 based on population

Repeat due every 5 years thereafter
Phase H

Effective: 1/30/91
added 30 contaminants + 3 aldicarbs
(MCLs for 3 aldicarbs were stayed)

total = 84

(Refer to Groups 1 & 2 in Table 2a)
4 consecutive quarterly samples/sampling point (except sulfate =
1 sample/sampling point)

Initial due 12/31/95

Repeat due every 5 years thereafter
Phase V
Effective: 7/17/92
Regulated 36 of previously unregulated
contaminants
Current total = 48
No new unregulated contaminants or requirements were added with
Phase V; schedule established under Phase I & II applies.
NOTE: Sampling point for ground water = entry point representative of each well after treatment. Sampling point for surface water
= site in distribution system representative of each source, or an entry point after treatment.
DATE: November, 1995
RELEASE NO. 1
UCM-1
-------
FRDS/SDWIS REPORTING REQUIREMENTS

•A. State Decisions

After the initial round of M/R for Phase I, States were encouraged to grant waivers for contaminants
which had not been used in the water supply area (i.e., use waiver) or if a source was not susceptible
to contaminants based on a vulnerability assessment and prior sampling results (i.e., susceptibility
waiver). Systems are not required to test for contaminants for whicha Statejwaiver has been granted.
A waiver may be granted for an entire system or for one or more sampling points. Waiver decisions
are not required to be reported to FRDS.

B. Sample Records

Samr-mg results are required to be reported to the C2100 record, SAMPLE-DATA. The specific
sample elements to be reported are presented in Table UCM-1.
Table UCM-1: Required Reporting Elements for Unregulated Sample Data
FRDS Element
No./Name
C2101: SAM-
PLE-ID
C2105: SAM-
PLE-END-
DATE
C2107: SAM-
PLE-CON-
TAMINANT
C2109: SAM-
PLE-RESULT-
SIGN
SDWIS Attributes
Entities
D GENERATED ID SOURCE CODE
SAMPLE
STATE ASGN IDENTIFICATION NUMBER
SAMPLE
COMPLIANCE PERIOD END DATE
SAMPLE
TERCNTMN CODE
SAMPLE_ANALYTICAL_RESULT
DETECTION LIMIT CODE
SAMPLE_ANALYTICAL_RESULT
Definition
Code used to
identify sam-
ple
Date sample
was collected
The unregu-
lated contami-
nant being
analyzed
Indicates
whether
result was
below method
detection limit
(MDL)or
was detected
Code Values/
Reporting For-
mat
5 digits specified
by State
mm/dd/yy
Refer to Tables
UCM-2 &UCM-
3 for 4-digit code
"<" means was
not detected
"=" means ex-
actly equal to
value reported
Other
Can be generat-
ed by FRDS/-
SDWIS
The date of
sample collec-
tion is used
instead of the
end date for un-
regulated con-
taminants
Certain con-
taminants share
a common
analytical
method, as
shown in
Tables UCM-2
&UCM-3
Non-detects are
reported as < 0,
where;
"<" is C2109
& "0" is
C2111
DATE: November, 1995
UCM-2
RELEASE NO. 1
-------
FRDS Element
No./Name .
C2111: SAM-
PLE-ANALY-
SIS-RESULT
C2112: SAM-
PLE-RESULT-
UM
C2113: SAM-
PLE-ANALY-
SIS-
METHOD
C2115: SAM-
PLE-SOURCE-
TYPE
C2119: SAM-
PLE-SE-ID
C2125: SAM-
PLE- QUANTI-
TY-COMPOS-
ITED
C2137: SAM-
PLE-TYPE
SDWIS Attributes
Entities
MEASURE
SAMPLE_ANALYTTCAL_RESULT
UNIT OF MEASURE CODE
SAMPLE_ANALYTICAL_RESULT
TFRSTOP METH_CODE
SAMPLE
SOURCE TYPE CODE
SAMPLE
Represented by a relationship between SAMPLE
and WATER_SYSTEM_FAOLITY
COMPOSITE QUANTITY
SAMPLE
TYPE_CODE
Definition
Laboratory
results for a
sample
Units of mea-
surement for
the analytical
result
EPA method
used to anal-
ysis the
sample
The source
type repre-
sented by the
sample
Unique ID
no. for each
sampling
point
No. of sam-
pling sites
included in
composite
sample
The water
type repre-
sented by the
sample.
Code Values/
Reporting For-
mat
Max. of 7 digits to
left of decimal
and 8 to right
"1" - micrograms
per liter (ug/1)
"2" - milligrams
per liter (mg/1)
3 digits to left of
decimal and max.
of 2 to right. See
Tables UCM-2&
UCM-3.
"1"- surface
water (sw) or
purchased sw
"2"-GUDIor
purchased GUDI
"3" - ground
water (gw) or
purchased gw
3 digits, estab-
lished by PWS
Integer number
between 2 and 5
"F"- Finished
water
"R"- Raw water
Other
In some cases,
may use UEC
method of
reporting (see
Tables UCM-2
and UCM-3)
ug/1 is preferred
unit of measure
Same method
must be used to
report using
UEC.
If composited,
sample consists
of any sw.it is
coded as "1"
Will be man-
datory reporting
req't. starting
1996. Must be
used for all
unregulated
monitoring at
this sampling
point.
Only required
if sample is
composited
"R" is only re-
ported for
PWSs using all
gw without
treatment
Tables UCM-2 and UCM-3 list the non-discretionary and discretionary unregulated contaminants,
respectively and their corresponding contaminant codes, hi addition, Unregulated Expansion Codes (UEC),
and corresponding EPA analytical methods are also listed in these tables, where applicable.

A UEC is used to report results below the laboratory method detection limit (MDL) (i.e., non-detects) for a
group of contaminants using the same analytical method. It cannot be used if any of the contaminants in the
DATE: November, 1995
RELEASE NO. 1
UCM-3
-------
group are measured using a method other than the one indicated for that contaminant group in Table UCM-2
or UCM-3, or if one or more of the contaminants in the group have been waived from monitoring. It can be
used if one or more contaminants in a particular group are above the lab MDL. For each of the contaminants
above the MDL, the data elements in Table UCM-1 must be reported and the actual analytical result must be
reported for C2111 (SAMPLE-ANALYSIS-RESULT) instead of the UEC.

Table UCM-2: FRDS C2107 (Sample Contaminant Codes/UEQ/SDWIS
SAMPLE_ANALYTICAL_RESULT, TFRCNTMN_CODE - (Non-discretionary
Monitoring)
Unregulated Contaminant and Associated Code
EPA Method*
UEC
Group 1 10 Phase II Organics & 3 Alidcarbs
Aldrin
Dieldrin
Mclribuzin
Dicamba
Carbaryl
3-Hydroxycarbofuran
Mcthomyl
2356
2070
2595
2440
2021
2066
2022
Butachlor
Metolachlor
Propachlor

Aldicarb
Aldicarb Sulfoxide
Aldicarb Sulfone
2076
2045
2077

2047
2043
2044
525.1
515.1
531.1
11++
N/A
12++
GROUP 2 1 Phase n Inorganic
Sulfatc
1055

375.2
N/A
GROUP 3 20 Phase I Volatile Organics
Bromobcnzcnc
o-ChlorotoIucnc
p-Chlorotoluenc
m-Dichlorobcnzene
Bromodichloromcthanc
Bromoform
Bromomcthanc
Chlorodibromomcthanc
Chloroc thane
Chloroform
2993
2965
2966
2967
2943
2942
2214
2944
2216
2941
Chloromethane
Dibromomethane
1,1-Dichloroethane
1 3-Dichloropropane
2,2-Dichloropropane
1,1-Dichloropropene
1 3-Diohloropropene
1,1,1 ,2-Tetrachloroethane
1 ,1 ,2,2-Tetrachloroethane
1,2,3-Trichloropropane
2210
2408
2978
2412
2416
2410
2413
2986
2988
2414
502.1,
502.2,
524.1, or
524.2 can
be used w/
UEC 3+++,
if same
method used
for all 20
contaminants
3+++
NOTE: Other methods have been approved for some of these contaminants; however, Tables UCM-2 and UCM-3 only indicate the
method which allows the use of UEC.
DATE: November, 1995
RELEASE NO. 1
UCM-4
-------
Table UCM-3: FRDS C2107 (Sample Contaminant Codes/UEC)/SDWIS SAMPLE_-
ANALYTICAL_RESULT, TFRCNTMN_CODE (Discretionary Monitoring)
Unregulated Contaminant and Associated Code
EPA Method*
UEC
GROUP 4 14 Phase I State-Discretion
n-Butylbenzene 2422
sec-Butylbenzene 2428
tert-Butylbenzene 2426
Hexachlorobutadiene 2246
Isopropylbenzene 2994
p-Isopropyltoluene 2030
1,2,3-Trichlorobenzene 2420
1 ,2,4-Trimethylbenzene
1 ,3,5-Trimethylbenzene
Bromochloromethane
Dichlorodifluoromethane
Fluorotrichloromethane
Naphthalene
n-Propylbenzene
2418
2424
2430
2212
2218
2248
2998
502.2

4+++

* The UEC method of reporting is limited to these EPA analytical methods.
Violations

Violations may be reported by sampling point or by system. If violations occur at multiple sampling
points for the same contaminant for the same monitoring period, the State would report all violations
if reporting by sampling point, but only 1 violation if reporting by system (major to be reported over
minor violation). The table on the next page indicates the required reporting elements for a violation.
D. Return to Compliance

A return to compliance (RTC) should be reported when a system is in compliance with its M/R
requirements. Compliance achieved is represented by SOX when RTC is reported by the State or
BOX when reported by EPA. The SOX or BOX must be linked to the violation that it resolved.
Refer to Enforcement and Variance/Exemption Sections for details on how to report compliance
achieved and the linking of enforcement actions to violations.
DATE: November, 1995
RELEASE NO. 1
UCM-5
-------
Table UCM-4: Required Reporting Elements for UCM Violations
FRDS Element
No./Namc
CHOI: VIO-ID

' C1103: VIO-
. CONTAMt-
I NANT
C1105: VIO-
TYPE
C1107: VIO-
COMP-PERI-
OD-BEGIN-
DATE
C1109: VIO-
COMP-PERI-
OD-END-DATE

Cllll: VIO-
COMP-PERI-
OD-MONTHS
C1131: V10-
MAJOR-VIO-
LATION-FLAG

SDWIS Attributes
Entities
FEDERAL FISCAL_YEAR_NUMBER
VIOLATION
D GENERATED_ID_SOURCE_CODE
VIOLATION
STATE ASGN IDENTMCATIONJNUMBER
VIOLATION
TERCNTMN_CODE
VIOLATION
TFRVTYPE_CODE
VIOLATION
COMPLIANCE PERIOD BEGIN_DATE
VIOLATION
COMPLIANCE_PERIOD_END_DATE
VIOLATION

Not converted; can be determined from Cl 107 and
C1109
MAJOR VIOLATION_INDICATOR_CODE
VIOLATION

Definition
Code used
to identify
the violation

Contami-
nant ID for
the violation
The type of
violation
Date moni-
toring
period
begins
Date moni-
toring
period ends

Period of
time in
which
monitoring
was re-
quired (in
months)
Major viola-
tion
designation

Code Values/
Reporting For-
mat
yynnnnn, where
yy = Fed FY in
which state be-
came aware of
violation
nnnnn = as-
signed by State
or can be gener-
ated by FRDS-
/SDWIS
Refer back to
Tables UCM-2
&UCM-3
"03" - regular
M/R
mmddyy
mmddyy

3 digits number
btwn "003" &
"060", depend-
ing on monitor-
ing frequency
"Y"- Major
"N"- Minor

Other •

See Note 1
below this
table
See Note 2
below this
table

May report
Cllll,
VIO-
COMP-
PERIOD-
MONTHS
instead
May report
C1109,
VIO-
COMP-
PERIOD-
END-
DATE
instead
May report
C1129,
VIO-SAM-
PLES-
TAKEN
instead (See
Note 3 be-
low')
DATE: November, 1995
UCM-6
RELEASE NO. 1
-------
FRDS Element
No./Name .

C1143: VIO-SE-
ID

SDWIS Attributes
Entities

Represented by a relationship between VIOLATION
and WATER_SYSTEM_FACILITY.

Definition

Source/-
entity ID at
which the
violation
was in-
curred

Code Values/
Reporting For-
mat
3-digit number
btwn"001"&
"949" - if
reporting by
sampling point

"000" - if
reporting by
system
Other

NOTE 1: Violations can no longer be reported using group contaminant codes. EPA plans to replace group contaminant
codes with individual violations for contaminants represented by a group contaminant code. For example, 2U36
which was used to report 36 original unregulated Phase I violations will be replaced with 36 individual M/R
violations.

NOTE 2: A regular M/R = failure to conduct initial, any repeat sampling, or accurately report an analytical result.
Confirmation samples for unregulated contaminants is not Federally required. Therefore, failure to collect a
confirmation sample (i.e., "04") is a State violation only and should not be reported to FRDS/SDWIS.

NOTE 3: A major M/R = failure to collect any samples. A minor M/R = some but not all samples collected.
E. Public Notification

Special public notification (PN) requirements, contained in Section 141.35, apply to 20 unregulated
VOCs. These contaminants are listed in Table UCM-2 as Group 3 contaminants. In particular
systems are required to notify the persons they serve of the availability of sampling results for these
unregulated contaminants. Failure to meet the delivery requirements of this notice constitutes a PN
violation. This violation is reported similarly to other violations. The Cl 105, violation type code,
for PN is "06". (Refer back to Table UCM-4 for details on how to report violations to
FRDS/SDWIS-FED.
F. Enforcement Actions

Any formal enforcement actions that are taken to address M/R violations for unregulated
contaminants must be reported to FRDS/SDWIS. EPA also encourages the reporting of informal
enforcement actions taken in response to violations, although such reporting is not required.

The C1200 ENFORCEMENT-DATA record and the ENFORCEMENT_ACTION SDWIS Entity
are used to report enforcement action information. See Table ENF-1 in Section 7, Reporting
Enforcement Information, for a description of the C1200 data elements for which information must
be provided and a list of formal and other enforcement actions which are required to be reported to
FRDS/SDWIS. hi addition, these enforcement actions must be linked to the violations that they
address. For more detailed information regarding this linking, also refer to the Reporting Enforce-
ment Information Section.
DATE: November, 1995
RELEASE NO. 1
UCM-7
-------
DOCUMENT SOURCES

Primary Sources:

State Reporting Guidance for Unregulated Contaminant Monitoring, EPA 812-B-94-:001, March
1994.

Phase II Implementation Guidance for FRDS, December 1991.

Secondary Sources:

Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994;
(original release: EPA 812-B-93-003, January 1993).
, •
FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 RELEASE NO. 1
UCM-8
-------
6. REPORTING VARIANCE/EXEMPTION INFORMATION
BACKGROUND

The primacy agent, State or EPA, may grant a public water system (PWS) a variance or exemption from
National Primary Drinking Water Regulation (NPDWR) requirements, provided it does not result in an
unreasonable risk to health. As provided by Section 1415 of the Safe Drinking Water Act (SDWA), a
variance may be granted to a PWS when its raw water characteristics render it unable to meet NPDWR
requirements such as a maximum contaminant level. However, before it may be granted, these systems must
first install the applicable best available technology or treatment technique. Section 1416 of the SDWA
provides for the issuance of exemptions to PWSs that are unable to comply with NPDWR requirements due
to compelling factors, which may include economic considerations.

The variance or exemption issued by the State or EPA must contain a schedule for compliance (including
increments of progress) and may contain requirements for additional control measures to be applied for the
duration of the variance/exemption. The FRDS C3100 data base record (VE-SCHEDULE) and the SDWIS
DEVIATION SCHEDULE Entity are used to record information about variance/exemption schedules.

FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions - Reporting Variances and Exemptions

The FRDS C3000 VARIANCE-EXEMPTION-DATA record and the SDWIS DEVIATION
SCHEDULE Entity are used to report information that characterizes variances, exemptions, or other
related data. Table V/E-1 below contains a description of the FRDS C3000 data elements and
SDWIS DEVIATION attributes for which information must be provided. Valid code values for data
elements that must be provided are listed in Tables V/E-2, V/E-3, and V/E-4. In particular: Table
V/E-2 lists contaminant codes for which a variance or exemption may be granted; Table V/E-3 lists
codes for activities related to the status of variances and exemptions; and Table V/E-4 lists treatment
codes for which variances and exemptions may be granted.

Table V/E-1: Required Reporting for Variances/Exemptions
FRDS Element
No./Name
C3001: VE-ID
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
DEVIATION
D GENERATED ID SOURCE CODE
DEVIATION
STATE -
ASGN IDENTIFICATION NUMBER
DEVIATION
D GENERATED ID SOURCE CODE
MILESTONE EVENT
Definition
Value used to
uniquely identify
a specific
variance, ex-
emption, or other
related data
Code Values/
Reporting Format
yynnnnn, where yy =
Federal fiscal year in
which variance,
exemption, or other
related data was
reported.
nnnnn = assigned by
State or generated by
SDWIS/FED
Other
When the
VE-ID is
generated
by SDWIS,
the first
position
contains the
letter X
DATE: November, 1995
V/E-1
RELEASE NO. 1
-------
FRDS Element
No,/Name ,
C3003: VE-
CONTAMI-
NANT
C?' r. VE-RE-
CC..J-TYPE
C3007: VE-EF-
FECTTVE-DATE
C3009: VE-EX-
PIRATION-
DATE
C3011: VE-
STATUS-CODE
C3013: VE-
MOD-MCL
C3017: VE-
ALT-PROCESS
SDWIS Attributes
Entities
TFRCNTMN CODE
DEVIATION
TYPE CODE
DEVIATION
EFFECTIVE DATE
DEVIATION
EXPIRATION DATE
DEVIATION
STATUS CODE
DEVIATION
MODIFIED MCL MEASURE
DEVIATION
TTNTRPRO CODE
DEVIATION
Definition
Code used to
denote the con-
taminant for
which a variance
or exemption has
been granted
Code used to
represent whet-
her the VARI-
ANCE-EX- .
EMPTION- '
DATA record is
a variance or ex-
emption
Date on which
variance or ex-
emption has or
will become
effective
Date on which
variance or ex-
emption has or
will expire
Code used to
denote current
status of variance
or exemption
Value used to
represent a modi-
fied MCL that
has been ap-
proved as a
condition of a
variance or ex-
emption
Value used to
represent an
alternative treat-
ment process that
has been ap-
proved as a
condition of a
variance or ex-
emption
Code Values/
Reporting Format
See Table V/E-2 for
a list of valid codes
"VA" - Variance
"EX" - Exemption
mmddyy
mmddyy
See Table V/E-3 for
a list of valid codes
Numerical value
with a maximum of
7 whole digits and 8
digits after the
decimal
See Table V/E-4 for
a list of valid treat-
ment codes
Other

Must be
less than
C3009
Must be
greater than
C3007

Must be
specified
when a
value is pro-
vided for
C3015
(VE-
TREAT-
MENT-
PROCESS)
NOTE: Some of the data elements contained in the C3000 record are used to record information about systems that are required to
install filtration pursuant to the Surface Water Treatment Rule (SWTR). For more information, see Section 2 on SWTR
reporting.
DATE: November, 1995
RELEASE NO. 1
V/E-2
-------
Table V/E-2: Variance/Exemption Contaminant Codes
Code
0100
1005
1010
1015
1020
1024
1025
1035
1036
1040
1041
1045
1074
1075
1085
1094
2005
2010
2015
2020
2031
2032
2033
2034
2035
2036
2037
2039
2040
2041
2042
2046
2050
2051
2063
2065
Description •
Turbidity
Arsenic
Barium
Cadmium
Chromium
Cyanide
Fluoride
Mercury
Nickel
Nitrate
Nitrite
Selenium
Antimony, Total
Beryllium, Total
Thallium, Total
Asbestos
Endrin
BHC-gamma (Lindane)
Methoxychlor
Toxaphene
Dalapon
Diquat
Endothall
Glyphosate
Di(2-ethylhexyJ) Adipate
Oxamyl (Vydate)
Simazinc
Di(2-ethylhexyl) Phthalate
Picloram
Dinoseb
Hexachlorocyclopentadiene
Carbofuran
Atrazine
Alachlor (Lasso)
2,3,7,8 - TCDD (Dioxin)
Heptachior
Code
2067
2105
2110
2274
2306
2326
2378
2380
2383
2931
2946
2950
2955
2959
2964
2968
2969
2976
2977
2979
2980
2981
2982
2983
2984
2985
2987
2989
2990
2991
2992
2996
4000
4010
4100
5000
Description
Heptachlor Epoxide
2,4-D
2,4,5-TP (Silvex)
Hexachlorobenzene (HCB)
Benzo(A)Pyrene
Pentachlorophenol
1 ,2,4-Trichlorobenzene
cis-l,2-Dichloroethylene
Total Polychlorinated Biphenyls (PCB)
l,2-Dibromo-3-Chloropropane (DBCP)
Ethylene Dibromide (EDB)
TTHM
Xylenes, Total
Chlordane
Methylene Chloride (Dichloromethane)
o-Dichlorobenzene
p-Dichlorobenzene
Vinyl Chloride
1 , 1 -Dichloroethylene
trans-l,2-Dichloroethylene
1,2-Dichloroethane
1 , 1 , 1 -Trichloroethane
Carbon Tetrachloride
1,2-Dichloropropane
Trichloroethylene
1,1,2-Trichloroethane
Tetrachloroethylene
Monochlorbbenzene (Chlorobenzene)
Benzene
Toluene
Ethylbenzene
Styrene
Gross Alpha, Excluding Radon & Uranium
Combined Radium (-226 & -228)
Gross Beta Particle Activity
Lead/Copper
DATE: November, 1995
V/E-3
RELEASE NO. 1
-------
Table V/E-3: Variance/Exemption Status Codes
Code
A
B
C
E
G
I
K
M
O
Q
Description
Interest Expressed
Completed. PWS in Compliance
Application Received
State Proposes to Deny
State Proposes to Grant
Hearing Scheduled on Proposal
Hearing Held on Proposal
Compliance Schedule Prescribed
Hearing Scheduled on Compliance Schedule
Hearing Held on Compliance Schedule
Code
R
S
T
U
V
W
X
Y
Z
Description
Additional Information Desired
Request Granted
Request Denied
State Sets Monitoring Requirements
EPA Sets Monitoring Requirements
Notification Given to Public
Other
Notification Given to EPA
Pending Deletion

B. Violations

Failure to meet the schedule established by a variance or exemption is a violation and must be
reported to FRDS/SDWIS. A variance or exemption violation has a FRDS Cl 105, VIO-TYPE value
of "08". The reporting of this violation is similar to that of other violation types. For a more detailed
discussion regarding the reporting of violations, refer to the violation section of any of the rule-
specific summary sheets.

C. Public Notification

Public notification (PN) is initially required when a system is granted a variance or exemption, as
outlined in Section 141.32(a). Additional PN is required if a system violates the schedule outlined
for the variance or exemption (i.e., an "08" violation). Sections 141.32(b) outline the PN
requirements associated with a variance or exemption violation. Failure to deliver the PN
requirements in accordance with these sections, results in a PN violation which must be reported to
FRDS/SDWIS. The FRDS Cl 105, violation type code, for PN is "06".
DATE: November, 1995
RELEASE NO. 1
V/E-4
-------
Table V/E-4: Variance/Exemption Treatment Codes
Code
121
125
141
143
145
147
149
160
180
190
200
220
240
300
320
341
449
455
460
500
520
541
543
560
580
600
620
Description
Activated Carbon, Granular
Activated Carbon, Powdered
Aeration, Cascade
Aeration, Diffused
Aeration, Packed Tower
Aeration, Slat Tray
Aeration, Spray
Algae Control
Bone Char
Brominization (Special Use)
Chloramines
Chlorine Dioxide
Coagulation
Distillation
Electrodialysis
Filtration, Cartridge
Inhibitor, Silicate
Iodine
Ion Exchange
Lime - Soda Ash Addition
Microscreening
Ozonation, Post
Ozonation, Pre
Permanganate
Peroxide
Rapid Mix
Reducing Agents
Code
342
343
344
345
346
347
360
380
401
403
421
423
441
443
445
447
623
625
627
640
660
680
700
720
740
741
742
Description
Filtration, Diatomaceous Earth
Filtration, Greensand
Filtration, Pressure Sand
Filtration, Rapid Sand
Filtration, Slow Sand
Filtration, Ultrafiltration
Flocculation
Fluoridation
Gaseous Chlorination, Post
Gaseous Chlorination, Pre
Hypochlorination, Post
Hypochlorination, Pre
Inhibitor, Bimetallic Phosphate
Inhibitor, Hexametaphosphate
Inhibitor, Orthophosphate
Inhibitor, Polyphosphate
Reducing Agent, Sodium Bisulfate
Reducing Agent, Sodium Sulfite .
Reducing Agent, Sulfur Dioxide
Reverse Osmosis
Sedimentation
Sequestration
Sludge Treatment
Ultraviolet Radiation
pH Adjustment
pH Adjustment, Post
pH Adjustment, Pre
DATE: November, 1995
V/E-5
RELEASE NO. 1
-------
DOCUMENT SOURCES

Primary Source:

Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994
(original release: EPA 812-B-93-003, January 1993).

Secondary Source:

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November. 1995 RELEASE NO. 1
V/E-6
-------
7. REPORTING ENFORCEMENT INFORMATION
BACKGROUND

Effective October, 1, 1990, all State and Federal formal enforcement actions were required to be reported to
FRDS. Enforcement data is stored in the FRDS C1200 ENFORCEMENT-DATA record. Table ENF-1
below contains a description of the data elements for which information must be provided. Tables ENF-2
and ENF-3 contain a list of formal Federal and State enforcement actions, respectively, and other actions that
must be reported to FRDS/SDWIS-FED. EPA also encourages the reporting of informal enforcement
actions, although such reporting is not required.

FRDS/SDWIS REPORTING REQUIREMENTS

Table ENF-1: Required Reporting Elements for Enforcement Actions
FRDS Element
No./Name
C1201: ENF-ID

C1203:
ENF-ACTION-
DATE
C1205:
ENF-FOLLOW-
UP-ACTION

SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
ENFORCEMENT_ACTION
D GENERATED ID SOURCE CODE
ENFORCEMENT_ACTION
STATE -
ASGN IDENTIFICATION NUMBER
ENFORCEMENT_ACTION
DATE
ENFORCEMENT_ACTION
Represented as three separate columns as fol-
lows:
FRDS Position SDWIS Column
1 TFREFUA AT CODE
2 TFREFUA FT CODE
3 TFREFUA SC CODE

Definition
Value used to
uniquely identi-
fy a specific
action

Date on which
enforcement
action was
taken
Code used to
represent an
enforcement
action taken by
the State, EPA
Region, or EPA
Headquarters

Code Values/
Reporting Format
yynnnnn, where:
yy = Fed FY in which
enforcement action
nnnnn = assigned by
State or generated by
FRDS/SDWIS

mmddyy
3-digit code, where;
Position 1:
"E"- EPA or Federal
action
"S" - State action
Position 2:
"F"- Formal action
"I" - Informal Action
"O"- Other Action
Position 3:
A valid enforcement
follow-up code that
indicates the specific
action taken
Other
When
the
ENF-ID
erated
by
FRDS,
the first
position
contains
the letter
E

Tables
ENF-2
and
ENF-3
contain
a list of
valid
C1205
codes

DATE: November, 1995
ENF-1
RELEASE NO. 1
-------
Table ENF-2: FRDS C1205 Codes (Federal Enforcement Follow-up Action Codes)

Formal Notice of Violation Issued
Bilateral Compliance Agreement Signed
ProDOsed Administrative Order Issued •_
Final Administrative Order Issued J
1431 (Emergency) Order
Complaint for Penalty Issued __
Complaint for Penalty Consent Order/Decree w/penalry
Complaint for Penalty Default Judgment
Civil Case Referred to Department of Justice
Civil Case Filed
Civil Case Concluded
Criminal Case Referred to Department of Justice
Criminal Case Filed
Criminal Case Concluded
Compliance Achieved
Variance/Exemption Issued
No Additional Formal Action Needed

Code
EFJ
EFK
EF!
EFL
EF/
EF<
EF-
EF=
EF9
EFQ
EF%
EF&
EFV
EFW
EOX
EOY
EO+
EO6
Table ENF-3: FRDS C1205 Codes (State Enforcement Follow-up Action Codes)
Enforcement Action Description
Formal Notice of Violation Issued
Bilateral Compliance Agreement Signed
Administrative Order (w/o penalty) Issued
Administrative Order (w/ penally) Issued
Administrative Penalty Assessed
Civil Case Referred to Attorney General
Civil Case Filed
Civil Case Concluded
Code
SFJ
SFK
SFL
SFO
SFM
SF9
SFQ
SF%
DATE: November, 1995
RELEASE NO. 1
ENF-2
-------
Table ENF-3 (Continued): FRDS C1205 Codes (State Enforcement Follow-up Action Codes)
Enforcement Action Description
Criminal Case Referred to Attorney General
Criminal Case Filed
Criminal Case Concluded
Compliance Achieved
Variance/Exemption Issued
No Additional Formal Action Needed
Intentional No-action
Code
SF&
SFV
SFW
SOX
SOY
SO+
SO6
A. Linking Enforcement Actions to Violations

Enforcement actions reported to FRDS/SDWIS-FED should be linked or associated with the
violations they address. The FRDS C1280, ENF-VIOLATIONS and the SDWIS ENF_VIO-
LATION_CRITERION Entity and the relationship between ENFORCEMENT_ACTION AND
VIOLATION are used to link enforcements and violations. Table ENF-4 below show the data
elements that must be populated to achieve this linking. These data elements are automatically
populated when one of the three methods for reporting violation linking data, described below, are
used.

Violations and enforcement actions can be linked three ways; however, only one Unking method can
be used at a time. The first method is to associate an enforcement action with a violation's begin and
end dates (C1107 and C1109). Another linking method consists of associating the enforcement
action with corresponding violation IDs (C 1101). The last method consists of linking the
enforcement action to a contaminant code (Cl 103), violation types (Cl 105), and compliance period
begin dates (Cl 107). The unking codes for these three methods, respectively, are X5000, Y5000,
and Z5000. An enforcement action that is not (or cannot be) linked to a violation is termed an
"orphan" enforcement action. An example of an "orphan" enforcement action is an enforcement
response that addresses state violations exclusively (e.g., cross-connection).
B. Return to Compliance

Information indicating that a water system has returned to compliance (RTC) must be reported to
EPA for violations of the Phase I, II, IIB, and V Rules, the Lead and Copper Rule, and the total
trihalomethane standard. RTC is reported to FRDS as "compliance achieved". Compliance achieved
is represented by SOX when reported by the State or EOX when reported by EPA. The SOX or
BOX must be linked to the violation that it resolved. The FRDS C1200 ENFORCEMENT-DATA
record and the SDWIS ENFORCEMENT_ACTION Entity (refer back to Table 1) are used to report
this information. Additionally, SOX or EOX must be linked with the associated violation using one
of the methods described in Section A above.
DATE: November, 1995 RELEASE NO. 1
ENF-3
-------
Table ENF-4: Database Elements for Linking Violations and Enforcement Actions
FRDS Element
NoJNamc
C1281
ENF-L1NK-VIO-
rn
AJLj/

C1283
ENF-LINK-
RANGE-BEGIN

C1285
ENF-UNK-
RANGE-END

C1287
ENF-LINK-
PERIOD-BEGIN

CI289
ENF-LINK-VIO-
TYPE

C1291
ENF-LINK-
CON-
TAMINANT
SDWIS Attributes

Represented by a relationship
between VIOLATION and EN-
FORCEMENT_ACTION

DATE BEGIN
ENF_VIOLATION_CRrrERION

DATE END
ENFJV1OIATION_CRITERION

DATE BEGIN
ENF_VIOLATION_CRITERION

TFRVTYPE CODE
ENF_VIOLATION_CRrrER[ON

TFRCNTMN CODE
ENF_VIOLATION_CRrrERION

Definition

ID that represents a
specific violation that is
related to unique
enforcement action

Start of period covered
by violation(s) which are
associated w/ enforce-
ment action
End of monitoring period
covered by violations)
which are associated w/
enforcement action
Start of monitoring
period in which a vio-
lation that is related to
the enforcement action
was incurred
Violation type of a
violation that is related to
the enforcement action

ID number of a con-
taminant for a violation
that is related to the
enforcement action
Code Values/
Reporting
Format
yynnnnn, where:
yy = FedFYin
which enforcement
action was taken
nnnnn = reported
by state or gener-
ated by FRDS/S-
DWIS

mmddyy

2-digits = C1105,
VIO-TYPE

4 -digits

Other •

When gener-
ated, first
position is
the letter
"V"

Used when
linking w/
theYSOOO
method
Must also
specify
C1203 &
C1205
Applies to
X5000
linking
method
Applies to
Z5000
linking
method

Applies to
Z5000
linking
method
Applies to
Z5000
linking
method
Note: Through the normal course of its operation, FRDS/SDWIS populates C1280 record data elements including C1293 (ENF-
LJNK-TYPE). C1293 represents the method used to relate violations to enforcement actions. Where:

"X" - link is by Associated Violation Date Range (i.e., X5000 transaction)
11Y" - link is by Associated Violation ID (i.e., Y5000 transaction)
"Z" - link is by Associated Violation Contaminant (i.e., Z5000 transaction)

C1293 records are represented in SDWIS in the Entity/attribute, ENF-VIOLATION-CRrTERION/TYPE CODE.
DATE: November, 1995
RELEASE NO. 1
ENF-4
-------
DOCUMENT SOURCES

Primary Source: •

November 13,1990, memorandum from Connie Bosma regarding Reporting Enforcement Actions
and "Compliance Achieved" to FRDS.

Secondary Sources:

Release 2.12 - Federal Reporting Data System (FRDS-II) Data Element Dictionary, March 1994
(original release: EPA 812-B-93-003, January 1993).

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 RELEASE NO. 1
ENF-5
-------
[THIS PAGE INTENTIONALLY LEFT BLANK]
DATE: November, 1995 RELEASE NO. 1
ENF-6
-------
8. MISCELLANEOUS REPORTING
BACKGROUND
This section contains the reporting requirements for the Total Trihalomethanes (TTHM) and the
Radionuclides. Both of these contaminant groups were part of the National Interim Primary Drinking Water
Regulations. The original requirements are still in effect today, although regulations have already been
proposed that would replace these requirements. Until new regulations are promulgated, the current reporting
requirements will continue for SDWIS/FED.

Monitoring requirements for TTHMs apply to community water systems .(CWS) that serve > 10,000 people
and that add a disinfectant (oxidant) to their drinking water. Systems are required to take a minimum of 4
samples per treatment plant on a quarterly basis. All monitoring results are averaged and reported quarterly.
Under certain circumstances and with the permission of the State, monitoring may be reduced to 1
sample/quarter. In addition, systems utilizing only ground water, with the permission of the State, may
submit a single sample for maximum TTHM potential per year.
Monitoring requirements for the radionuclides apply to all CWSs. Systems must monitor for gross alpha
particle activity for four consecutive quarters. Results are reported as an annual average. If a gross alpha
result is > 5 pCi/1, the same or equivalent sample must be tested for radium-226. If the radium-226 result is
> 3 pCi/1, the sample must be tested for radium-228. An MCL violation occurs when the combined radium-
226 and radium-228 result > 5 pCi/1. Systems repeat monitoring every 4 years.

Monitoring requirements for man-made radionuclides (beta particle and photon radioactivity) apply to CWSs
that serve > 100,000 people. Systems monitor quarterly for gross beta particle activity as well as Tritium and
Stontium-90. hi some circumstances, monitoring for Iodine-131, Stontium-89, and Cesium-134 also apply.
The MCL for beta particle activity from man-made radionuclides shall not produce an annual total body dose
> 4 millirem/year. Systems repeat monitoring every 4 years.
FRDS/SDWIS REPORTING REQUIREMENTS

A. State Decisions

None are required to be reported.

B. Violations

Under the original TTHM and radionuclide regulations, violations are categorized as either
monitoring/reporting (M/R) or maximum contaminant level (MCL) violations. Violations are to be
reported by system only. Table MISC-1 presents the required reporting elements for violations. The
contaminant codes for reporting TTHM and radionuclide violations are presented in Table MISC-2.
DATE: November, 1995 RELEASE NO. 1
MISC-1
-------
Table MISC-1: Required Reporting Elements for TTHM and Radionuclide Violations
FRDS Element
No./Name
C1101: VIO-ID
C1103: VIO-
CONTAMI-
NANT
C1105: VIO-
TYPE
C1107: VIO-
COMP-PERI-
OD-BEGIN-
DATE
C1109: VIO-
COMP-PERI-
OD-END-DATE
Cllll: VIO-
COMP-PERI-
OD-MONTHS
C1115:VIO-
AWARE-DATE
C1123: VIO-
ANALYSIS-RE-
SULT
SDWIS Attributes
Entities
FEDERAL FISCAL YEAR NUMBER
VIOLATION
D GENERATED ID SOURCE_CODE
VIOLATION
STATE -
ASGN IDENTIFICATION NUMBER
VIOLATION
TFRCNTMN CODE
VIOLATION
TFRVTYPE CODE
VIOLATION
COMPLIANCE PERIOD BEGIN DATE
VIOLATION
COMPLIANCE PERIOD END DATE
VIOLATION
Not converted; can be determined from Cl 107
and CI 109
AWARE DATE
VIOLATION
ANALYSIS RESULT MEASURE
VIOLATION
• Definition
Code used to
identify the
violation
Contaminant
ID for the
violation
The type of
violation
Date moni-
toring period
begins
Date moni-
toring period
ends
Period of
time in which
monitoring
was required
(in months)
Date state
became
aware of
MCL vio-
lation
Analytical
result(s) that
caused the
MCL viola-
tion
Code Values/
Reporting Format
yynnnnn, where yy
= Fed FY in which
state became aware
of violation
nnnnn = can be
assigned by State or
generated by FRDS-
/SDWIS
Refer to Table
MfSC-2
"01" - single sample
MCL
"02" -average MCL
"03"- regular M/R
mmddyy
mmddyy
3 digits number
between "001" &
"048", depending
on monitoring fre-
quency
mmddyy
Maximum of 7 digits
to the right of the
decimal and 8 digits
to the left
Other

See Note 1 at
the end of this
table

May report
Cllll.VIO-
COMP-PERI-
OD-
MONTHS
instead (See
Note 2 at the
end of table)
May report
C1109.VIO-
COMP-PERI-
OD-END-
DATE instead
(See Note 2 at
the end of ta-
ble)
Applies to
"01"&"02
violations only
Applies to
"01" & "02"
violations only
(See Note 3
below)
DATE: November, 1995
MISC-2
RELEASE NO. 1
-------
FRDS Element
No./Name
C1131: VIO-
MAJOR-VIO-
LATION-FLAG

SDWIS Attributes
Entities
MAJOR VIOLATION INDICATOR CODE
VIOLATION

Definition
Indicates
whether
violation is
major or
minor M/R.
violation
Code Values/
Reporting Format
"Y"= Major
"N"- Minor

Other
May report
C1129.VIO-
SAMPLES-
TAKEN
instead (See
Note 4 below)
NOTE 1: Cl 105, violation type is defined as follows: •

• "01", single sample MCL applies to systems monitoring on annual or less frequent basis.
• "02", average MCL occurs when the average of the initial and confirmation sample exceeds the MCL,
or when the system is monitoring more frequently than once per year and the running annual average
exceeds the MCL.
• "03", regular M/R = failure to conduct initial, any repeat sampling, or to accurately report an analytical
result.

NOTE 2: Cl 111 equals "003" for quarterly sampling; "012" for annual monitoring; and "048" for monitoring every 4
years.

NOTE 3: For single samples, the value reported for Cl 123, VIO-ANALYSIS-RESULT, would be the regular sample
causing the violation. For systems monitoring less frequently than annually, Cl 123 would equal the running
annual average.

NOTE 4: A major M/R = failure to collect any samples. A minor M/R = some but not all samples collected.
Table MISC-2: Contaminant Codes for TTHMs and Radionuclides
Code
2950
4000
Description
Total Trihalomethanes
Gross Alpha, excluding radon and uranium
Code
4010
4101
Description
Combined Radiums (-226 & -228)
Man-Made Beta Particle and Photon Emitters
C. Public Notification

Public notification (PN) is required when a system incurs an MCL, or M/R violation. Mandatory
language of the PN is outlined in Section 141.32(d). This language must be published in the
newspapers within 14 days and notice to consumers within 45 days. Monitoring violations require
notification in newspapers within 3 months and every 3 months thereafter until the violation ceases.
Failure to meet the PN requirements must be reported as a violation to SDWIS/FED. The violation
type code (FRFDS Cl 105 or SDWIS TFRVTYPE_CODE), for PN is "06".
D. Enforcement Actions
DATE: November, 1995
RELEASE NO. 1
MISC-3
-------
Formal enforcement actions taken to address violations must be reported to FRDS/SDWIS,
regardless of whether EPA or the State undertakes the action. EPA also encourages the reporting of
informal enforcement actions taken in response to violations, although such reporting is not required.

The FRDS C1200 ENFORCEMENT-DATA record is used to report enforcement action
information. See Table ENF-1 in Section 7, Reporting Enforcement Information, for a description of
the C1200 data elements for which information must be provided and a list of formal and other
enforcement actions which can be reported to FRDS/SDWIS. In addition, these enforcement actions
must be linked to the violations that they address. For more detailed information regarding this
linking, see Section 7, Reporting Enforcement Information.
DOCUMENT SOURCES

Primary Sources:

Release 2.12 - Federal Reporting Data System (FRDS-H) Data Element Dictionary, March 1994;
(original release: EPA 812-B-93-003, January 1993).

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 version.
DATE: November, 1995 " ~~ " RELEASE NO. 1
MISC-4
-------
APPENDIX A. COMPLETE LIST OF REFERENCES

NOTE * Indicates the primary document where the reporting requirements are presented.

GENERAL REPORTING

* July 9, 1984 memorandum from Victor J. Kimm, "Guidance for Public Water System Supervision
Program Reporting Requirements, WSG #V-1".

* June 19,1987 memorandum from Michael B. Cook, "Public Water Supervision Revised Reporting
Requirements -- Water Supply Guidance V-2".

* FRDS-H Data Element Dictionary, Release 2.12 (March 1,1994), original release: EPA 812-B-93-
003, January 1993.

FRDS to SDWIS/FED Data Conversion Mapping, May 1995 Version.

November 30, 1990 memorandum from Connie Bosma, "Reporting Enforcement Actions and
'Compliance Achieved1 to FRDS".

TOTAL COLIFORM RULE

* Total Coliform Rule Implementation Manual (Including Appendix D). Final March 8, 1990 (This
date was corrected to be March 8,1991).

June 1, 1994 memorandum from Robert Blanco, "Requirement for a PWS Which Takes Fewer Than
5 Total Coliform Samples Per Month To Undergo a Sanitary Survey".

April 3,1992 memorandum from Betsy Devlin, "TCR FRDS Reporting Issue - Monthly and Acute
MCL Violations".

SURFACE WATER TREATMENT RULE

* Surface Water Treatment Rule Implementation Manual (Including Appendix D). Final March 8,
1990 (This data was corrected to be March 8, 1991).

January 22, 1992 memorandum from Jeff Sexton, "Modifications to the FRDS Reporting
Requirements for the SWT Rule".

August 13, 1992 memorandum from Brian Mass, "Reporting Filtration Decisions to FRDS".

February 28, 1991 memorandum from Connie Bosma, "Final SNC Definition for the SWTR".

February 21,1992 memorandum from Robert Blanco, "Guidance on the Enforcement of the SWTR".
DATE: November, 1995 RELEASE NO. 1
A-l
-------
PHASE I
The reporting guidance for this rule was made obsolete with the issuance of the Phase II/IIB
reporting guidance. • .
PHASE n AND IIB
Phase II Implementation Guidance, Federal Reporting Data System (FRDS) Reporting, December
19,1991 (Distributed with a January 2, 1992 cover memorandum from Connie Bosma with a note
that the guidance is final and to disregard the "Draft Final" notation in the upper right hand corner of
each page).

Draft Consolidated Summary of Phases II/IIB/V
LEAD AND COPPER RULE

* Lead and Copper Rule Definitions and Federal Reporting for Milestones, Violations, and SNCs.
May 1992. (Distributed June 1,1992 with a cover memorandum from Robert J. Blanco).

March 3,1993 memorandum from Abraham I. Siegel, "Corrections to 'Lead and Copper Rule
Definitions and Federal Reporting for Milestones, Violations, and SNCs'."

March 23,1993 memorandum from Abraham I. Siegel, "Clarification of How to Report Lead 90th
Percentile Sample Data to FRDS When the PWS Has Completed its Monitoring Late".
UNREGULATED CONTAMINANT MONITORING

* "State Reporting Guidance for Unregulated Contaminant Monitoring", (EPA 812-B-94-001), March
1994.
DATE: November, 1995 RELEASE NO. 1
A-2
-------
APPENDIX B: SDWIS/FED CONTACTS
LOCATION
U.S. EPA
Headquarters
SDWIS User
Support
Region 1
Region 2
Region 3
Region 4
Region 5
Region 6
Region 7
Region 8
Region 9
Region 10
OFFICE ADDRESS
U.S.EPA
Office of Ground Water and Drinking Water
401 M Street, S.W.
Washington D.C., 20460
Science Application International Corp.
Suite 300
200 North Glebe Road
Arlington, VA 22203
U.S. EPA, Region 1
John F. Kennedy Federal Building
One Congress Street
Boston, MA 02203
U.S. EPA, Region 2
Jacob K. Javitz Federal Building
26 Federal Plaza
New York, NY 10278
U.S. EPA, Region 3
841 Chestnut Building
Philadelphia, PA 19107
U.S. EPA, Region 4
345 Courtland Street, N.E.
Atlanta, GA 30365
U.S. EPA, Region 5
77 W.Jackson Blvd.
Chicago, IL 60604
U.S. EPA, Region 6
1445 Ross Ave.
Suite 1200
Dallas, TX 75202-2733
U.S. EPA, Region 7
726 Minnesota Ave.
Kansas City, KS 66101
U.S. EPA, Region 8
999 18th Street
Suite 500
Denver, CO 80202-2405
U.S. EPA, Region 9
75 Hawthorne Street
San Francisco, CA 94105
U.S. EPA, Region 10
1200 Sixth Ave.
Seattle, WA 98101
CONTACT
Abe Seigel
(202) 260-2804
(703) 908-2460
Kathy Lynch
(617) 565-3618
Bill Jutis
(212)264-4753
Charlotte Dennis
(215)597-2460
Claduia Darnell
(404) 347-2913
Tom Poleck Kris Werbach
(312)886-2407 (312)886-6527
Fran Haertel Mark McCasland
(214)655-8090 (214)655-8088
Darlene Schowengerdt
(913)551-7474
Rich Gomez
(303)293-1409
Richard Lamport
(415)744-1854
Jane Schuster Craig Paulson
(206) 553-1096 (206) 553-4350
DATE: November, 1995
B-l
RELEASE NO. 1
-------
-------