Cgi.
IT
United States
Environmental Protection
Office of Water
(WH-550B)
March 1990
Federal Reporting
Data System (FRDS-1I)
Data Entry Instructions
en
cr>
_
UJ
HEADQUARTERS LIBRARY
ENVIRONMENTAL PROTECTION AGENCY
WASHINGTON, D.C. 20460
-------
-------
FRDS-II. Data Entry Instructions - Release 1.0
Federal Reporting Data System (FRDS-II)
Data Entry Instructions
Release Log
Notes All change notices/descriptions that relate to the FRDS-II
Data Entry Instructions should be filed immediately following
the release log.
Change
Notice
Release
Number
1 .00
~-
. __._
Effective
Date
10/01/89
.
.....
Description of Release
Initial Release of Production Documentation
Effective Date: 10/0 1/89
Release Number: 1. 0 Page:
-------
FRDS DATA ENTRY INSTRUCTIONS
TABLE OF CONTENTS
CHAPTER TITLE PAGE
General Information
Introduction 1
I Forms Description 2
II Data Transfer File 25
III Position Concept... 31
IV Data Base Registration Requirement 33
V Data Element Removal vs. Data Base Record
Deletion 36
VI Record Identification and Maximum
Occurances 38
VII General Coding Instructions 15
Detail Information
VIII Detailed Coding Instructions 50
Data Capture Form A
Section Al - System Address 51
Section A2 - Public Water System
Characteristics 55
Section A3 - Other Address(es) 62
Data Capture Form B
Section B1 - Source / Entity Data 67
Section B2 - Treatment Data 76
Data Capture Form C
Section C1 - Geographic Areas Served 81
Section C2 - Service Areas 85
Section C3 - On-Site Visits...: 88
Effective Dates 10/01/89 Release Numbers 1 . 0 . Page: j,
-------
FRDS DATA ENTRY INSTRUCTIONS
TABLE OF CONTENTS
CHAPTER TITLE PAGE
VIII (cont.) Data Capture Form D
Section D1 - Violation Data 92
Data Capture Form E
Section E1 - Enforcement Data 99
Data Capture Form F
Section F1 - Variances, Exemptions
£ Other Related Data 106
Section F2 - VE Schedule 111
Data Capture Form G
Section G1 - State Discretionary Data...116
IX Record Deletion Form 120
Appendixes
Appendix A - Examples of Data Capture
Form / Data Transfer File A-1
Appendix B - Edit/Update B-1
Appendix C - Anytoun, USA, Coded
Source/Entity Examples C-1
Appendix D - Data Base Registration/Grant
Eligibility At-A-Glance D-1
Effective Dates 10/01/89 Release Number: t . 0 Page: i, jj.
-------
FRDS DATA ENTRY INSTRUCTIONS
TABLE OF CONTENTS
Figures
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
Figure
1 (Section A1 DBR Relationship)
2 (Section A2 DBR Relationship)
3 (Section A3 DBR Relationship ).-....
W (Section B1 DBR Relationship)
5 (Section B2 DBR Relationship)
6 (Section C1 DBR Relationship)
7 (Section C2 DBR Relationship)
8 (Section C3 DBR Relationship)
9 (Section Dl DBR Relationship)
10 (Section El DBR Relationship)....
11 (Section F1 DBR Relationship)...,
12 (Section F2 DBR Relationship)..,.
13 (Section G1 DBR Relationship)....
1 <4 ( FORM A )
15 (TOWNSHIP/RANGE)
16 (FORM B)
17 (FORM C)
18 (FORM D)
19 (FORM E)
20 (FORM F)
21 (FORM G)
22 (RECORD DELETION FORM)
5
6
7
9
10
13
m
15
17
19
21
22
24
66
72
80
91
98
. ... 105
....115
....119
. ... 122
Effective Date: 10/0 1/89
Release Number 1.0
Page =
-------
FRDS-II DATA ENTRY INSTRUCTIONS
INTRODUCTION
The FRDS-II Data Capture Forms are designed to assist the FRDS-II
System users in their data collection efforts. It should be noted
that these forms are intended for data collection only and not for
direct input to the FRDS-II System, which uill be accomplished via
the FRDS-II Data Transfer Format. It is hoped that the way in
uhich data is presented on these forms uill assist the user in the
transition to the FRDS-II Data Transfer Format.
These data entry instructions are meant to be as comprehensive as
possible. However, there are issues related to FRDS-II data that
are programmatic in nature, and these issues are not generally
discussed here. A more comprehensive and detailed discussion of
'programmatic versus technical issues, definitions of data elements,
table references, and glossary may be found in the Federal
Reporting Data System Data Element Dictionary.
This document is arranged into two major parts. The first part
(consisting of Chapters I through VII) contains general information
that pertains to all Data Capture Forms and to the FRDS-II System
as a uhole. The second part (Chapters VIII and IX) contains all of
the detailed information that pertains to each individual Data
Capture Form.
Effective Date: 10x01/89
Release Number: 1.0
Page :
-------
FRDS-II DATA ENTRY INSTRUCTIONS
GENERAL INFORMATION
CHAPTER I
FORMS DESCRIPTION
Effective Date: 10/01/89
Release Number:
Page
-------
FRDS-II DATA ENTRY INSTRUCTIONS
GENERAL INFORMATION
FORMS DESCRIPTION
There are eight different FRDS-II Data Capture Forms (Forms A - G
and a Record Deletion Form). The following is an overview of forms
A - G, their sections. and the information contained therein. The
Record Deletion form is discussed in Chapter IX, "Record Deletion
Form."
o FORM A
Section A1 - SYSTEM ADDRESS (See Figure 1)
This section is used to enter facility name and address
information for a public water system. Where multiple
facilities exist for a public water system at different
locations, this section should be used to enter address
information for the system as a whole. The following
data may be entered via this section:
DATA ELEMENT" *
C131
C133
C135
C137
C139
cmi
C143
FORM REFERENCE NAME
- SYSTEM NAME
- ADDRESS LINE 1
- ADDRESS LINE 2
- CITY
- STATE
- ZIP CODE + 4
- TELEPHONE (AREA CODE £ NUMBER)
Section A2 - PUBLIC WATER SYSTEM CHARACTERISTICS (See Figure 2)
This section is used to enter data related to the various
physical characteristics of the public uater system. The
following data may be entered via this section1
DATA ELEMENT f
C105
C107
C11 1
C1 13
C1 17
C121
C123
C125
C127
cm?
C1S9
C161
C163
C165
FORM REFERENCE NAME
PWS TYPE
ACTIVITY FLAG
SYSTEM BEGIN (YR C MO)
DEACTIVATION DATE (YR £ MO)
RETAIL POPULATION SERVED
PERCENT SURFACE
PERCENT GROUND
PERCENT PURCHASED SURFACE
PERCENT PURCHASED GROUND
RETAIL SERVICE CONNECTIONS
NON-COMMUNITY SEASON BEGIN (MO C DAY)
NON-COMMUNITY SEASON END (MO £ DAY.)
OWNER TYPE
REGULATING ENTITY
Effective Date
10/01/89
.Release Number
1-0
Page
-------
FORMS DESCRIPTIOH
Section A3 - OTHER ADDRESS(ES) (See Figure 3)
This section is used to enter additional address infor-
mation, such as an ouner;address or related facility
addresses. The following data may be entered via this
sections
DATA ELEMENT #
C301
C303
C305
C307
C309
C311
C313
C315
FORM REFERENCE NAME
ADDRESS ID
ADDRESS TYPE
ADDRESSEE NAME
ADDRESS LINE 1
ADDRESS LINE 2
CITY
STATE
ZIP CODE + 4
Effective Dates 10/0 I/89
Release Number: 1.0
Page'
-------
31.
> SS-.₯S-H
;*SK*\ ,--t\ r 't^g
..?*:.:: is! , (»:.;.:₯::::.
li
Eifective Date: 10/01/89
Release Number: j. o
-------
w
>:-W:"iW
Q
«/>
UJ
ca
+ *
!-
4*
'.
i ~~-
Jli
O I
II
-
MM
-
IE
-
i :
M
f
44
H
4-
1:
vw
II
-------
O
u
CD
= Q
O
UL.
LU
oc
Q_
u
i-|i..ji |-*|-?||
iiHii
Effective Date
10/0 1/89
-------
-------
O
DC
O
O
uu
LU
CO
<
CO
u.
UJ
Q.
<
u
I
Q
-------
O
QC
O
u
CO
<
CO
£*
<£
= Q to
o
LU
o:
a.
O
UI
-sf.fi
.-S-"
3*1-1:
-------
FORMS DESCRIPTION
FORM C . .
Section C1 ' - GEOGRAPHIC AREAS SERVED (See Figure 6)
'This section is used to' enter data that identifies geo-
graphic areas or jurisdictions served by a public water
system. All data elements within a single geographic
areas served record should be valued uith related data,
which describe a single geographic area. For example,
if city "X" is in county "A", they both should be in-
cluded in the same geographic areas served -record.
Conversely, if city "X" is outside of county "A", they
each should be included in a separate record. The
FRDS-II Data Base has one geographic areas served record
for each geographic area served that has been reported
to EPA. The following data may be entered via this
section:
DATA ELEMENT t
C501
C503
CSOS
C507
CS09
C513
CS15
Section C2
FORM REFEREMCE NAME
- GA ID
- ADMIN REGION
- ADMIN DISTRICT
- FEDERAL CONGRESS DISTRICT
- F/S COUNTY
- CITY
- INDIAN RESERVATION
SERVICE AREAS (See Figure 7)
This section is used to enter data that characterizes
the type of area served by the public water system. The
FRDS-II Data Base has one record for each type of area
served that is reported to EPA and must have one service
area designated as primary for non-transient, non-
community and non-community public water systems. The
following data may be entered via this section:
DATA ELEMENT *
C601
C603
C605
FORM REFERENCE NAME
- SERV ID
- TYPE/CAT
- PRIMARY SERVICE FLAG
Effective Date= 10/01x89
Release Number- 1.0
Page =
-------
FORMS DESCRIPTION
Section C3 - ON-SITE VISITS (See Figure 8)
This section is used to enter data that is related to
on-site visits made to a public uater system. The
FRDS-II Data Base has one on-site visit record for each
on-site visit (such as a sanitary survey), that has
been reported to EPA. The following data may be entered
via this section1
DATA ELEMENT *
C701
C703
C70S
FORM REFERENCE NAME
- VISIT ID
- VISIT DATE (MO, DAY, £ YR)
- VISIT REASON
Effective Date: 10/01/89
Release Number: 1 .0 Page: ]_£
-------
Q
Q£
O
o
CO
<
CQ
CO h- Q
~_Q -. z:
A^^<
fP^-aZi
a.
<
O
Effective Date
Figure 6
10/01/ag . Release Number'. 1
Page :
-------
Q
QC
O
o
to
<
CO
0.
<
O
to
z<
O "j
^O
y>
-iP
-jfiti
jte
* *"*' +
: .;sf|*:
; ' JllL
--Ifi-
S-p g". 1
TT^ "^~~^ ''^U:
5f "*£$ i- .»»- 1L
5 5 * ; '"g>7^n
, ||;|
.5«f:.fJ
9
*
lirl"*'^
sii-^: '
::. J-B:
-S-
iiH
-I*h
I. 1
1
» A*
ill1
*.
> '
«
IF
g:lc-
*iil:
IS|: I!.
5.-rI;.:t.|
"*I^:J
itii
H-
3 _
I-
£0
v. O
> n
oO
is 2
a a
0.0
J-
\ -
. -. -
;;"!'.-.- 1|E'''
:^::-:-:::-::'-:'>'f:''-l?T:';;:;.-:-'-':;:;:::/?v1;:':':''':':':':':'-^^::'"'^ '-'''- .^t::
;|
: 1
-ilii
13 3 3 3 3 3
'- 3 3 B 3 3 3i
Effective Date
Figure 7
10/01/89 Release Number
Pages
-------
0*
O
O
LU
co
<
GQ
<
5
= Q
QC
O
u.
LU
O£
Q_
<
U
z>
O LU
55
B
III
<
oO 1
33
^fijisiii
;;.₯₯: SBs.^
ill
11
'. ,-', ' '.', -'-^M :
' 3 3 3 3 3 3i
^xmm?m jjmjj^jm
1111111111 iilllllli
gSiiiiiiiiilills § i;s ?sii^*s:
ft|ftw^;:;;:;:;:ss!::*s;:?sft*s;₯; si i%s mssmm
~~i
Effective Date
Figure .8
10/01/89 Release Number:
Page: 15
-------
FORMS DESCRIPTION
FORH D
Section D1" - VIOLATION DATA (See Figure 9)
This section is used to enter data that characterizes
a violation of a primary drinking uater regulation
issued to a public uater system by a State or Federal
agency. The FRDS-II Data Base has one violation record
for each violation that has been reported to EPA. The
following data may be entered via this section:
DATA ELEMENT t FORM REFERENCE NAME
C1101 - VIOLATION ID (FY £ -ID NUMBER)
C1103 - CONTAMINANT
C1105 - VIOLATION TYPE
C1107 - COMPLIANCE PERIOD BEGIN (MO, DAY, £ YR)
C1109 - COMPLIANCE PERIOD END (MO, DAY, £ YR)
C1111 - COMPLIANCE PERIOD DURATION
C1115 - AWARENESS DATE (MO, DAY, £ YR)
C1121 - ANALYSIS METHOD
C1123 - ANALYSIS RESULT
C1 125 - MCL VIOLATED
C1127 - NUM SAMPLES REQUIRED
C1129 - NUM SAMPLES TAKEN
C1131 - MAJOR VIOLATION
C1 143 - SE ID
Effective Date: 10/01/89 Release Number: 1.0 Page: 16
-------
Q
QC
O
o
LU
CO
Q_f=
gs
ac
a.
<
a
Effective. Date
Figure 9 -
10/01 /f? ' Release Number: 1t0:j Page?
-------
FORMS DESCRIPTION
o FORM E
Section E1- - ENFORCEMENT DATA (See Figure 10)
This section is used to enter data that characterises an
enforcement action taken against a public water system
by a State or Federal agency. The FRDS-II Data Base has
one enforcement record for each enforcement action that
has been reported to EPA. The following data may be
entered via this section:
DAT.A ELEMENT *
C1201
C1203
C120S
XSOOO
YSOOO
Z5000
FORM REFERENCE NAME
ENFORCEMENT ID (FY £ ID NUMBER)
ENFORCEMENT DATE (MO, DAY, £ YR)
- FOLLOW-UP ACTION
- ASSOCIATED VIOLATION RANGE
BEGIN (MO DAY YR)
END (MO DAY YR)
- ASSOCIATED VIOLATION IDS
VIOLATION ID 1 (FY £ ID NUMBER)
VIOLATION ID 2 (FY £ ID NUMBER)
VIOLATION ID 3
-------
o
OC
O
O
CO
g
Effective Date:
Figure 10
10/01/89 Release Number
Page '
-------
FORMS DESCRIPTION
FORM F
Section F1 ' - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA (See
Figure 11)
This section is used to enter data that characterises a
variance or exemption that is pending for, or has been
granted to, a public water system. The FRDS-II Data Base
has one variance or exemption record for each variance
or exemption that has been reported to EPA. The
following data may be entered via this section:
DATA ELEMENT #
:C3001
C3003
C3005
C3007
C3009
C301 1
C3013
C3015
C3017
C3019
Section F2
FORM REFERENCE NAME
- VE ID CFY £ ID NUMBER)
- CONTAMINANT
- RECORD TYPE
- EFFECTIVE DATE (MO,
- EXPIRATION DATE (MO
- STATUS CODE
- MODIFIED MCL
- TREATMENT PROCESS
- ALTERNATE PROCESS
- REASON
VE SCHEDULE (See Figure 12)
DAY, fi YR)
DAY, £ YR)
This section is used to enter data that characterises a
schedule of events and/or actions that are related to a
variance or exemption that is pending for, or has been
granted to, a public uater system. The FRDS-II Data-
Base has one schedule record for each event or action
which is related to a variance or exemption that has
been reported to EPA. The following data may be entered
via this form:
DATA ELEMENT t
C3001
C3101
C3103
. C3105
C3107
FORM REFERENCE NAME
- VE ID (FY £ ID NUMBER)
- SCHEDULE ID
- ACTION
- SCHEDULED DATE (MO, DAY, £. YR)
- ACCOMPLISHED DATE (MO, DAY, £ YR)
Effective Date
10/01/89
Release Numbers t..._0_
Page
29
-------
o
o
CO
<
CQ
QC
O
O
<
Q
LU
5§
LU
"»s:
i/>
LU
o
<
oc
<
R
liH
1-
gU.
2 E
i- «
0.
co
I
D
j;
5
Effective Date
Figure 1 1
10/01/89 Release Number: j.0 Pages
-------
o
o
U4
CO
<
CO
So.
uO
a ca
Q.Q
Cfi
J-
i
i-
ai~
335
1-33331
0 0
*
I e B
J h
frft'"
₯
S i
f.
3
3331
333i
an
*
2 e
Effective Date
Figure 12
10/01/89 Release Number ' 1 . 0
Pages ZJL
-------
FORMS DESCRIPTION
FORM G
Section G1 - STATE DISCRETIONARY DATA (See Figure 13J
This section is used to enter data that characterises a
specific set of values defined at the discretion of the
State. The FRDS-II Data Ease has one discretionary
record for each single set of State specific data values
that has been reported to EPA for a public water system.
The following data may be entered via this section:
DATA ELEMENT *
CM001
CU003
C400S
C4007
C4009
FORM REFERENCE NAME
- SDD ID
- STATE DISCRETIONARY DATA NAME
- STATE DISCRETIONARY VALUE
- 2UANTITY
- DATE (MO, DAY, £ YR)
Effective Date:
10/01/89
Release Number.: 1 . 0
Page: 23
-------
o
QC
Q
O
CO
<
CD
LL. Q£
O
I
CO
i-
«
>. o
u>u-
i_ O
S5
5S.
* «
uU
Is
3 ra
Q.O
1
I
H
1-
<»l ^
2
i X
5 -
I =
IS
2 _
VI
I I _
I I
2 i
S i
o »
Effective Date
Figure 13
10/01/89 Release Kumber: 1.0
Page: 2J£
-------
FRDS-II DATA ENTRY INSTRUCTIONS
CHAPTER II
DATA TRANSFER FILE
Effective Date: \Q/Q1/a 9 Release Number: 1 . 0 Pages 25
-------
DATA TRANSFER FILE
The Data Transfer File Format, which may be used at the onset of
FRDS-II availability, is the only format (except as noted belou)
by which, the Revised Reporting Requirement (RRR) data can be
entered into the FRDS-II Data Base. Consequently, this is the
EPA preferred format for use by States to input their FRDS-II
data. However, States that will not initially have the
capability to use the Data Transfer File Format, will be able to
submit update transactions in the FRDS 1.5 format that they
currently use. There will be a phase-in period during .which
inventory data in the FRDS 1.5 format will be accepted into the
FRDS-II System. Refer to the latest approved FRDS-II
implementation schedule for phase-in deadlines.
EXCEPT FOR THE AWARENESS DATE IN THE REVISED CARD 45, IT SHOULD
BE EMPHASIZED THAT THE FRDS 1.5 TRANSACTION FORMAT DOES NOT
ALLOW FOR THE INPUT OF REVISED REPORTING REQUIREMENT DATA.
After the phase-in period, public water systems uill be counted
for grant allocation purposes ONLY if all of the data items
required for that purpose are supplied. After this time, the
capability for accepting transactions in the FRDS 1.5 format will
not be available. Action data (i.e., violations, enforcements,
variances and exemptions) is an exception to the phase-in period,
and will have to be reported using the Data Transfer File Format
at an earlier time in the implementation schedule. Again, see
the latest approved FRDS-II implementation schedule for the
phase-in deadline for action data.
Effective Date? 10/01/89 Release Number: 1.0 . Pages ,3_6
-------
DATA TRANSFER FILE
In those cases uhere multiple records (i.e., Form Sections) may
be input to FRDS-II. secondary data address qualifiers are
required to be included with each record. These are needed to
uniquely identify the specific record being processed. These
secondary data address qualifiers are shown in the "Sualifier 2
and the "2ualifier 3" columns in the list below. *
DATA ADDRESS 2UALIFIERS
SECTION PRIMARY
ID SECTION NAME . QUALIFIER
A1
A2
A3
B1
B2
D1
E1
F1
F2
« i .
SYSTEM ADDRESS
PWS CHARACTERISTICS
OTHER ADDRESSES
SOURCE / ENTITY DATA
TREATMENT DATA
GEOGRAPHIC AREAS SERVED
SERVICE AREAS
ON-SITE VISITS
VIOLATION DATA
ENFORCEMENT DATA
VARIANCES £ EXEMPTIONS
. V £ E SCHEDULE
STBTIP nT«trDFTTnwa n v HIT;
*PMS-ID
*PWS-ID
*PMS-ID
*PUS-ID
*PWS-ID
*PWS-ID
*PWS-ID
*PUS-ID
*PUS-ID
*PMS-ID
*PUS-ID
*PWS-ID
l*PU«!-Tn
SECON
1 2UALIFIER 2
N/A
N/A
*ADDRESS-ID
* SE-ID
* SE-ID
* GA-ID
* SERV-ID
* VISIT-ID
"VIOLATION-ID
* ENF-ID
* VE-ID
* VE-ID
* SDD-ID
DARY
QUALIFIER 3
N/A
N/A
N/A
N/A
*TREATMENT-ID
N/A
N/A
N/A
N/A
N/A
N/A
*SCHED-ID
N/A
**NOTE' The data element numbers for the qualifiers listed
above, are not valid data element .numbers for use in
the data element number area-(positions 27-31) in the
DTF record. Specifically, these data element numbers
are C101, C301, C401, C481, CS01, C601, C701, C1101,
C120-1, C3001, C3101, and CU001.
Effective Date-' 10/0 1/89
Release Number 1 . 0
Page: 27
-------
DATA TRANSFER FILE
Secondary data address qualifiers are always required to permit
FRDS-II to -uniquely identify a specific record in those cases
where multiple records for a PWS can exist (e.g., multiple
sources). In such cases, the secondary data address qualifiers
serve as essential "group codes", permitting the automatic
grouping of all related Data Transfer File records during
processing. This needs to be done to ensure that the data from
multiple Form-IDs -for any PWS would not be inadvertently mixed.
The group code can also be used to communicate to the FRDS-II
Computer System that the user .wants FRDS to automatically
generate the associated ID and post it to the data base.
In these cases, the group code is prefixed with a "G" and
it is referred to as a "Group Generation Code" (GGC). By design,
GGCs are not retained in the data base but serve in a temporary
capacity only: grouping related data together and triggering
the automatic generation of sequential ID numbers.
I.n those cases where the user decides to assign his or her own
ID codes, and the secondary data address (i.e., ID) already
exists in the data base, the record being inserted will be re-
jected as having a duplicate ID. However, since the GGC numbers
are not stored in the data base, such an error under the GGC con-
cept is not possible. The drawback to these system generated IDs
is that the user does not have immediate access to them for
subsequent updating purposes. However, after each update in the
Effective Date' 10/01/89 Release Number: 1.0 Page:
-------
DATA TRANSFER FILE
FRDS-II System, a report showing all IDs generated during that
update, will be available to the user.
With the exception of the X5000, Y5000, and ZSOOO enforcement
transactions, one Data Transfer record is required for
each data value (i.e., data element) to be entered into the
FRDS-II System. For example, when adding a System Address
up to seven Data Transfer records may be necessary, since
seven data elements are possible. Each Data Transfer record
would contain the appropriate data value along uith the Section
ID, Data Address Cualifier(s), (see page 27 for the list of valid
qualifiers) Action Code, Data Element Humber and Batch Date.
Each Data Transfer File record is 80 characters in length and
has the following format:
Definition Positions
Form ID 1-2
Qualifier 1 3-11
Sualifier 2 . 12 - 18
Cualifier 3 19 - 25
Action Code 26
Data Element Mumber 27 - 31
Data Value 32 - .71
Reserved for FRDS-II use 72 - , 74
Batch Date 75-80
1 1 DATA ADDRESS 2UALIFIERS I I DATA I II I
I FORM I IACT. IELEM.I I FRDS I BATCH I
ID I 2UAL 1 I QUAL 2 I fiUAL 3 I CODE INUM. I DATA VALUE I USE I DATE I
I I I I I I I I -_\
1-2 3-11 12-18 19-25 26 27-31 '32-71 72-74 75-80
Effective Date: 10/01/89 Release Number: j_._0 - Page: 29
-------
DATA TRANSFER.FILE .
The X5000, Y5000, and ZSOOO transactions are the only cases where
the Data Transfer File Data Value (pps 32 - 71) uill contain
multiple data elements. These data elements are BEGIN and END
dates in the ASSOCIATED VIOLATION RANGE (XSOOO), VIOLATION IDS 1
through U in the ASSOCIATED VIOLATION IDS (Y5000), and
(violation) TYPE, CONTAMINANT (type) , and (violation) BEGIN DATE
in the ASSOCIATED VIOLATION CONTAMINANT GROUPS (ZSOOO). When
used, these data elements must be contiguous in the Data Transfer
File Data Value (i.e., without any intervening spaces).
In addition, there is a maximum number of occurances for these
data elements that can occur in the Data Value Field. The
maximum number is shown as follous:
ASSOCIATED VIOLATION RANGE (XSOOO) - A maximum of one begin date
and one END date may be used
in the Data Value Field.
ASSOCIATED VIOLATION IDS (Y5000) - A maximum of four VIOLATION
IDS may be used in the Data
Value Field.
ASSOCIATED VIOLATION CONTAMINANT - A maximum of three groups,
GROUPS (ZSOOO) each consisting of TYPE,
CONTAMINANT, and BEGIN DATE
may be used in the Data
Value Field.
See Appendix A for examples of hou the Data Transfer File Format
records are related to encoded Data Capture Forms.
Effective Date: 10/01/89 Release Number: 1 . 0 Page= 30
-------
FRDS-II DATA ENTRY INSTRUCTIONS
CHAPTER III
POSITION CONCEPT
Effective Date: 10/0 t/89 Release Numbers 1.0 Pages 31
-------
POSITIOH CONCEPT
Throughout this document, you uill see the term "POSITION" (e.g.,
"POSITIONS "1-3 must contain", etc.). In order to avoid any
possible confusion or misinterpretation, the following examples
are given1
o "POSITION 1", (or "FIRST POSITION") means LEFT-MOST
o "POSITIONS 1 - 3" means position 1 is LEFT-MOST .
and position 3 is the RIGHT-MOST.
Effective Date: 10/01/89 Release Number: 1.0 Page: 32
-------
FRDS-II DATA ENTRY INSTRUCTIONS
CHAPTER IV
DATA BASE REGISTRATION REQUIREMENT
Effective Date: jj)/0 1/89 Release Number 1 . 0 Page: 3!
-------
DATA BASE REGISTRATION REeUIREPIENT
The term "Registration Requirement" is used to characterise and
delineate uh'ich FRDS-II data elements are necessary in order for
a public water system, or some other event related to that public
water system (e.g.. Violation, Exemption, etc.), to get "recorded1
into the FRDS-II Data Base. The "Reason Codes" and definitions
on the next page are offered as an explanation of the rationale
used in identifying uhy a specific data element is needed by
FRDS-II for the public water system to become registered.
*
Effective Date: 10/0 1/jj> Release Number* 1 .0 Page: 3Ji
-------
Registration
Requirement
Federal Reporting Data System
Data Base Registration Requirements
Definitions
Definition
OPERATIONALLY REQUIRED
The FRDS-II computer system cannot process data related to a
public uater system without a value for'this data element.
Examples1- * PWS-ID to insert a new public uater system,
* PWS-SE-RECORD-TYPE to insert a new source or
entity
PROGRAflHATICALLY REQUIRED
Based upon programmatic need, EPA has determined that a value
aluays must be reported for this data element for public
uater system inventory. violation, enforcement. or
variance/exemption data to be inserted into the FRDS-II Data
Base .
Examples: * PUS-TYPE to insert a neu public uater system,
* PWS-SE-CODE to insert a neu source or entity,
* VIO-TYPE to insert a neu violation,
* ENF-ACTION-DATE to insert a neu enforcement,
* VE-STATUS-CODE to insert a neu variance/exemption
OPERATIONALLY REQUIRED - CONDITIONALLY
Under certain circumstances, the FRDS-II computer
cannot process data related to a public water system
a value for this data element.
system
without
Examples'
* VIO-ID if inserting a neu violation,
* ENF-ID if inserting a neu enforcement,
* VE-ID if inserting a neu variance/exemption
PROGRAMMATICALLY REQUIRED - CONDITIONALLY
Based upon programmatic need. EPA has determined that, under
certain circumstances, a value must be reported for this data
element for public uater system inventory, violation,
enforcement, or variance/exemption data to be inserted into
the FRDS-II Data Base.
Examples:
* PWS-DEACT-YYHM if inserting an inactive PWS,
* VIO-CONTAMINANT if inserting an MCL or M/R
violation
Effective Date*
10/0 1/89
Release Number' 1 .0
Page! 2J|
-------
FRDS-II DATA ENTRY IHSTRUCTIONS
CHAPTER V*
DATA ELEMENT REMOVAL VS. DATA BASE RECORD DELETION
Effective Date: 10/01/89 Release Number' 1 . Q Page: 36
-------
DATA ELEMENT REMOVAL VS. DATA BASE RECORD DELETION
The difference between data element removal and Data Base Record
CDBR) deletion is an important concept in the FRDS-II System.
When a DBR is deleted, all values contained in that DBR and the
DBR itself are removed. When a data .element is removed, only
its value is blanked out (initialised to nulls) in the DBR; other
data elements in that specified DBR remain unchanged.
DBR deletion is accomplished only through the use of the ACTION
CODE "D". Data element value removal, houever, is accomplished
by entering an ACTION CODE of "M" .(i.e., Modify) and a dollar
sign (*) in the first (left-most) position of the data element
value to be removed.
Effective Date.: 10/01/89 Release Number: 1,0 Page= £7
-------
FRDS-II DATA ENTRY INSTRUCTIONS
CHAPTER VI
RECORD IDENTIFICATION
Effective Date: 10/01/89 Release Number 1.Q Pages 38
-------
RECORD IDENTIFICATION
Except for sections A1 and A2 (which use the PWS ID), all section
types on the FRDS-II Data Capture Forms have a unique record ID
(i.e., secondary data address qualifiers). These IDs are used in
FRDS-II to specifically identify Data Base Records (DBRs) in the
data base so that the various transaction types (insert, delete,
and modify) can be performed. For most record types, the user
has the option of assigning his or her oun record ID, or allowing
the FRDS-II System to generate a unique record ID. Exceptions to
this are the SYSTEM ADDRESS and PUBLIC WATER SYSTEM CHARACTER-
ISTICS (Sections AT and A2, respectively), which use the PWS ID
for a record ID, and must always be assigned by the user.
It should be noted here, that in some cases there is a difference
in the length of the record ID, between what is defined in the
Federal Reporting Data System Data Element Dictionary and what is
shown on the FRDS-II Data Capture Forms. This is to allow room
for the "Group Generation Code" (GGC), which signals the FRDS-II
Computer System to Generate the record ID. The actual length of
the record IDs in the FRDS-II Data Base are as defined in the
FRDS-II Data Element Dictionary. It should also be noted that
the FRDS-II System makes a special allowance for the use of the
GGC in IDs that are defined as numeric. No other alphabetic
characters are accepted in these IDs. The FRDS-II System will
not allow a mixture of user assigned IDs and GGCs in an update
for a given record type, within a given PWS. For example, if two
source records for the same PWS are to be posted to the data base
in the same update, BOTH SE IDs must be user assigned, or BOTH
must use the GGC. A further discussion of "Group Generation
Codes" may be found in Chapter II - "Data Transfer File".
The following is a list of each record ID and the rules for
their assignment or generation.
ADDRESS ID - (OTHER ADDRESS(ES))
If the user wants to assign the ADDRESS ID...
o position 1 must be greater than or
equal to 1 and less than or equal to 9. '
o position 2 of the ID must be blank.
If the user wants the FRDS-II computer system
to generate an ADDRESS ID...
o position 1 of the ID must contain the
letter "G".
o position 2 must be greater than or
equal to 1 and less than or equal to 9.
NOTE: When ADDRESS ID is assigned by the user, a maximum of 9
address records may be entered in any single update for
a given PWS. When ADDRESS ID is computer generated, a
maximum of 9 address records may be entered in any
single update for a given PWS.
Effective Dates 10/01/89
Release Number: 1.0
Pages 39
-------
RECORD IDENTIFICATION
SE ID - (SOURCE / ENTITY DATA)
If the user wants to assign the SE ID...
o positions 1 - 3 must be greater than or
equal to 001 and less than, or equal to 949.
If the user uan.ts the FRDS-II computer system
to generate the SE ID... ' ' .
o position 1 of the ID must contain the
letter "G"
o positions 2-3 must be greater than or
equal to 01 and less than or equal to 99.
NOTE: when SE ID is assigned by the user, a maximum of 200'
source entity records may be entered in any single
update for a given PUS. . When SE ID is computer
generated, a maximum of 99 source entity records may be
entered in any single update for a given PWS. SE IDs
950 through 999 are reserved for EPA ODW use.
TREATMENT ID - (TREATMENT DATA)
If the user uants to assign the TREATMENT ID...
o positions 1 - 2 must be greater than or
equal to 01 and less than or equal to 99.
o position 3 must contain a blank.
If the user uants to have the FRDS-II computer
system generate the TREATMENT ID...
o position 1 must contain the letter "G".
o positions 2-3 must be greater than or
equal to 01 and less than or equal to 99.
NOTE: When TREATMENT ID is assigned by the user, a maximum of
40 treatment records may be entered in any single
update for a given SOURCE. When TREATMENT ID is
computer generated, a maximum of 40 treatment records
may be entered in any single update for a given SOURCE.
Effective Date: 10/01/89
Release Number:
Page: t»g
-------
RECORD IDENTIFICATION
GA ID - (GEOGRAPHIC AREAS SERVED)
If the user wants to assign the GA ID...
o position 1 - 2 must be greater than or
equal to 01 and less than or equal to 39.
If the user wants to have the FRDS-II computer
system generate the GA ID....
o position 1 must contain the letter "G".
o position 2 must be greater than or
equal to 1 and less than or equal to 9.
HOT£: When GA ID is assigned by the user, a maximum of HO
geographic areas served records may be entered in any
single update for a given PUS. When GA ID is computer
generated, a maximum of 9 geographic areas served
records may be entered in any single update for a given
PWS. GA IDs 90 through 99 are reserved for EPA ODW
use .
SERV ID - (SERVICE AREAS).
If the user wants to assign the SERV ID..
o position 1 - 2 must be greater than or
equal to 01 and less than or equal to 99.
If the user wants to have the FRDS-II computer
system generate the SERV ID...
o position 1 must contain the letter "G".
o position 2 must be greater than or
equal to 1 and less, than or equal to 9 .
NOTE: When SERV ID is assigned by the user, a maximum of 40
service area records may be entered in any single
update for a given PUS. When SERV ID is computer
generated, a maximum of 9 service area records may be
entered in any single update for a given PWS.
Effective Date:
10/0 1/89
Release Number 1.0
Page :
-------
"RECORD IDENTIFICATION
VISIT ID - (ON-SITE VISITS)
If the user wants to assign the VISIT ID...
o position 1 - 2 must be greater than or
equal to 01 and less than.or equal .to 99. .
If the user uants to have the FRDS-II computer
system generate the VISIT ID...
o position 1 must contain the letter "G".
o position 2 must be greater than or
equal to 1 and less than or equal to 9.
NOTE: VISIT ID uill ALWAYS be generated by the FRDS-II
Computer System. A maximum of 9 on-site visit records
may be entered in any-single updata for a given PWS.
VIOLATION ID - (VIOLATION DATA]
If the user uants to assign the VIOLATION ID...
o positions 1-2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o positions 3-7 must be greater than or
equal to 00001 and less than or equal to 99999.
If the user uants the FRDS-II Computer System to generate the
VIOLATION ID. . .
o positions 1 - 2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o position 3 must contain the letter "G".
o positions <4 - 7 must be greater than or
equal to 0001 and less than or equal to 9-999. .
NOTEs When the VIOLATION ID is assigned by the user, a
maximum of 300 violation records may be entered in any
single update for a given PUS. When the VIOLATION ID
is computer generated, a maximum of 300 violation
records may be entered in any single update for a given
PWS and position 3 of the generated ID uill contain a
II y H
Effective Date: 10/0^/89 Release Number 1 . 0 Page:
-------
RECORD IDENTIFICATION
ENFORCEMENT ID - (ENFORCEMENT DATA)
If the'user wants to assign the ENFORCEMENT ID...
o positions 1 - 2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o positions 3-7 must be greater than or
equal to 00001 and less than or equal to 99999.
If the user wants the FRDS-II Computer Sys.tem to generate the
ENFORCEMENT ID...
o positions 1 - 2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o position 3 must contain the letter "G".
o positions 4-7 must be greater than or
equal to 0001 and less than or equal to 9999.
NOTE: when ENFORCEMENT ID is assigned by .the user, a maximum
of 300 enforcement records may be entered in any single
update for a given PWS. When ENFORCEMENT ID is
computer generated, a maximum of 300 enforcement
records may be entered in any single update for a given
PUS and position 3 of the generated ID will contain an
VS ID - (VARIANCES, EXEMPTIONS C OTHER RELATED DATA)
If the user wants to assign the VE ID...
o positions 1 - 2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o positions 3-7 must be greater than or
equal to 00001 and less than or equal to 99999.
If the user wants the FRDS-II Computer'System to generate the
VE ID...
o positions 1 - 2 must be greater than or
equal to 78 and less than or equal to the current
federal fiscal year.
o position 3 must contain the letter "G".
o positions 4-7 must be greater than or
equal to 0001 and less than or equal to 9999.
NOTE: when VE ID is assigned by the user, a maximum of 50
variances, exemptions £ other related data records may
be entered in any single update for a given PWS. When
VE ID is computer generated, a maximum of SO variances,
exemptions £ other related data records may be entered
in any single update for a given PWS and position 3 of
the generated ID will contain an "X".
Effective Date:
10/01/89
Release Number:
Page
ii
-------
RECORD IDENTIFICATION
SCHEDULE ID - (VE SCHEDULE)
If the user wants to assign the SCHEDULE ID...
o positions. 1-2 must be greater than or
equal to 01 and less than or equal to 99.
If the user wants the FRDS-II Computer System to generate the
SCHEDULE ID...
o position 1 must contains the letter "G".
o position 2 must be greater than or
equal to 1 and less than or equal to. 9.
NOTE' When SCHEDULE ID is assigned by the user, a maximum of
50 schedule records may be entered in any single update
for a given variance and exemption record. When
SCHEDULE ID is computer generated, a maximum of 9
schedule records may be entered in any single update
for a given variance and exemption record.
SDD ID - (STATE DISCRETIONARY DATA)
If the user uants to assign the SDD ID...
o positions 1 - 3 must be greater than or
equal to 001 and less than or equal to 999.
If the user wants the FRDS-II computer system
to generate the SDD ID...
o position 1 of the ID must contain the
letter "G"
o positions 2-3 must be greater than or
equal to 01 and less than or.equal to 99.
NOTE: When SDD ID is assigned by the user, a maximum of 100
State discretionary records may be entered in any
single update for a given PWS. When SDD ID is computer
generated, a maximum of 99 State discretionary records
may be entered in any single update for a given PWS.
Effective Date: 10/01/89 Release Number: 1.0 Page:
-------
FRDS-II DATA ENTRY IMSTRUCTIOHS
CHAPTER VII
GENERAL CODING INSTRUCTIONS
Effective Date: 10/0 1/89 Release Number: 1.0 Page'
-------
GENERAL CODIMG INSTRUCTIONS
Throughout the FRDS-II Data capture forms, there are many areas
where dates may be entered. Additionally, there are three
different formats in which these dates are represented. These
formats include:
YR HO (Year and Month)
MO DAY Cttonth and Day)
no DAY YR (Month, Day and Year)
When dates are entered, the applicable month, day or year should
be left-justified and sero-filled. The examples shown below
demonstrate the correct and the incorrect methods of entering
the date of narch 7, 1988.
CORRECT INCORRECT
YR MO 8803 883
HO DAY 0307 307
no DAY YR 030788 3 788
There are many sections in the FRDS-II Data Capture Forms
that allou for multiple iterations of the same data types to be
entered in a single section. For example. Section C3 (ON-SITE
VISITS) contains six iterations of.the same data types. This allows
the user to enter up to six on-site visits on that single form.
If the user uants to enter more than six on-site visits for any
single update, he or she would have to use a second or third
form, as needs dictate.
Similarly, there are forms that have two or more iterations of
the same section. For example. Section D1 is repeated twice
on Form D. This enables the user to enter two violations for
a single update on one form. If the user wants to enter more
than two violations for any single update, he or she must use
additional forms as appropriate.
There is a third case where two sections are repeated twice on
the same form (Section B1 - SOURCE/ENTITY DATA and SECTION B2 -
TREATMENT DATA). Under normal circumstances, the user would fill
in SOURCE / ENTITY DATA and possibly two or three iterations
of TREATMENT DATA. However, it is possible for the user to enter
a single source entity and up to ten iterations of treatment data
on a single form. This would be accomplished by filling in the
SOURCE/ENTITY DATA section at the top of the form and then filling
in the TREATMENT DATA in both of the B2 Sections, with the SE ID
in all ten occurances being filled in identically to the SE ID in
Section B1. If more than ten iterations of TREATMENT DATA are
needed, additional forms would be necessary. The same methodology
would apply to VARIANCES, EXEMPTIONS C OTHER RELATED DATA and
VE SCHEDULE data (Data Capture Form F).
Effective Date' 10/01/89 Release Number: 1 . 0 Page: t46
-------
I
GENERAL CODING INSTRUCTIONS
All Data Captuze Forms have several items in common. These
include, PWS ID, ACTION CODE, BATCH DATE, and SECTION TYPE.
se of these items is as follows:
PWS ID - This is an alphanumeric value that is used to uniquely
(C10U identify ,a public water system. PWS ID is always
prefixed with a valid United States Postal Service (USPS)
abbreviation or EPA Region code which is then followed by
a 7-character identifier that is unique for each PWS
within that State or Region. The following rules apply
when specifying PWS ID-
o Positions 1 - 2 must be a valid USPS State code or
for Indian Lands, an EPA Region code from 01 through
10 should be used where applicable.
o Positions 3-9 must be unique for each PWS within
a State
o Positions 3-9 may contain alphanumeric characters
A - Z or 0 - 9.
o Positions 3-9 must not contain any special
characters (i.e., other than A - Z or 0 - 9).
(ACTION CODE -
This is an alphabetic value that determines the
action that the FRDS-II Computer System will take
with the specified data. ACTION CODES must always
be specified and must be one of the following
values =
ACTION
CODE
D (DELETE) =
This ACTION CODE causes an entire Data Base
Record (DBR) to be deleted from the FRDS-II
Data Base. In order for a DBR to be
deleted, it must exist in the data base.
When a violation record is deleted, all
RELATED enforcement records will also be
deleted. However, enforcement records
related to other violations as well, will
NOT be deleted.
Effective Date=
10/01/89
Release' Number ! 1 . 0
Page: T7
-------
GENERAL CODING INSTRUCTIONS
ACTION
CODE
I (INSERT) »
M (MODIFY) »
This ACTION CODE causes a new DBR
to be inserted into the FRDS-II Data
Base. DBRs with duplicate record IDs are
not allowed in the FRDS-II Data Base. If
a record being added has a record ID that
already exists in the data base, it will
not be inserted into the data base.
This ACTION CODE causes the current value of a
data element in an already existing DBR to be
modified. Modifying the current value
includes the removal (blanking out) of an
existing data value. This can be accomplished
by entering a dollar sign ($) in the first
position (left-most) of the data element to be
.removed. Some data elements in the FRDS-II
Data Base may not be removed. Refer to the
Data Element Registration Tables (that follow
the data entry instructions for each record
type) to see if removal is allowed. Also, see
Chapter V, "DATA ELEMENT REMOVAL VS. DATA BASE
RECORD DELETION."
BATCH DATE
This may be any valid calendar date that the user
desires. Some consideration should be given to the
date that is entered in BATCH DATE, since it is used
to "time sequence" events that take place during an
update of the FRDS-II Data Base. "Time sequencing"
determines the order of processing of duplicate
transaction types (e.g., two violation transactions
with the sane PUS ID and the same VIOLATION ID), by
posting the transaction uith the most recent BATCH
DATE last. In other words, the transaction with the
earlier BATCH DATE will be "overlaid" by the
transaction with the most recent (later) BATCH DATE.
When inserting a PWS in performing a traditional
update (updates that are not total replace), all
"registration requirement" data elements for the PWS
must be submitted with the sane Batch Date. Data
elements that are not required for data base regis-
tion may contain any Batch Date the user so desires..
Note' When transactions are submitted as a "total
replace", BATCH DATE is disregarded by the
FRDS-II Computer System.
Effective Date
10/01/89
Release Number: 1.0
Page :
-------
GENERAL CODING INSTRUCTIONS
I
ECIMALS
When entering numbers into data elements that are
defined as decimal, the user should be auare of the
following constraints^
o Decimal numbers MUST contain the decimal point.
o The maxiaum number of positions (as determined
by the rules for the data element involved) in
the integer portion or the decimal portion of
the number being entered, cannot be exceeded.
o A whole number may be entered uithout the decimal
point, as long as it does not exceed the length
of the defined integer portion of the number.
Decimal data elements that do not meet the above
criteria, uill be rejected by the FRDS-II System.
EXAMPLE: Consider the decimal data element REACH
tllLES, which is defined as 9(4).9(2) - (a four
position integer and a two position decimal).
INPUT
1234.56
1
1 . 1
1234
1234S6
0.01
0.001
12345 . 6
RESULT
1234.56
0001.00
0001 . 10
1234.00
ILLEGAL
0000.01
ILLEGAL
ILLEGAL
SECTION TYPE - This is the letter/number combination (i.e. A1,
A2, etc.) that appears in the boxes on the left
hand side of the data capture forms. It is used
to identify SECTION TYPE on the FRDS-II Data
Capture forms. SECTION TYPE is also used to
relate sections on the data capture forms to
Data Base Records (DBRs) in the FRDS-II Data
Base. This data is always required in order to
ensure proper data placement or deletion.
Effective Date' 10/0 1/89
Release Numbers 1.0
Page: 49
-------
FRDS-II DATA ENTRY INSTRUCTIONS
CHAPTER VIII
DETAILED CODING INSTRUCTIONS
Effective Date: 10/01/89 Release Number: t.0 Page: 50
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM A
SECTION A1 - SYSTEM ADDRESS
Effective Date: 03/05/88
Release Number' 0.0!
Page
-------
SECTION A1 - SYSTEM ADDRESS
(See Figure 14)
This section is used to enter facility name and address
information for a public uater system. Where multiple
facilities exist for a public water system at different
locations, this section should be used to enter address
information for the system as axwhole. The following
data may be entered via this section1
SYSTEM NAME
(C131)
CITY
(C137)
STATE
(C139)
Enter the name of the public water system. Up to
30 positions may be specified and any combination
of alphabetic, numeric or special characters is
allowed. SYSTEM NAME can be the formal, legal or
common name that is used most generally in referring
to the public water system.
ADDRESS LINE 1
CC133)
Enter address data (generally other than street
address) such as the name of a responsible person or
agency, or information applicable to the primary
facility location of the public uater system. If
this data is unknown or does not exist for the public
water system, do not provide this data.
ADDRESS LINE 2
(C135)
Enter address data such as the street address, rural
route and/or box designation, etc., that is
applicable to the primary facility location of.the
public uater system. If a street address or rural
route and/or box number does not exist for the public
uater system, do not provide this data.
Enter the city name that is applicable to the primary
facility location of the public water system.
Enter the United States Postal Service (USPS) State
abbreviation that is applicable to the primary
facility location of the public water system. The
State code must be a valid 2-character USPS State
abbreviation as found in SECTION VI, Table ID02, in
the Federal Reporting Data System Data Element
Dictionary.
Effective Date: 03/05/8.8
Release Number:
Page: <5J.
-------
SECTION A1 - SYSTEM ADDRESS
ZIP CODE + 4
Iccmn
Enter the ZIP CODE -m that is applicable to the
primary facility location of the public water system
If the +4 portion of the sip code is unknown, leave
that portion blank.
TELEPHONE NUMBER (AREA CODE £ NUMBER)
(C143)
Enter the telephone number of the public water
system. TELEPHONE NUMBER identifies the area code
and phone number which is applicable to the primary
facility of or the principal contact person for
the public water system. If the AREA CODE is
unknown, the 7-digit phone number may be entered
by itself.
Effective Date
03/05/88
Release Number: 0.0 3
Page :
-------
SECTION A1 - SYSTEM ADDRESS
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
Ci31
C133
C135
C137
C139
C141
C143
FORM REFERENCE NAME
:======================:
SYSTEM NAME
ADDRESS LINE 1
ADDRESS LINE 2
CITY
STATS ' .
ZIP CODE + 4
TELEPHONE
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR
A.
A
A
A
A
A
-A
~ L. . .
L ' Y '
' L Y
L
L
.L
L Y
Y
Y
Y
Y*
Y
Y
Y
Y
Y
Y
Y
At least
LEG.END
the 5-digit sip code is required for grant eligibility.
A/N/D
JUST
SIN
ZERO FILL
REG. CODE
GRANT ELIG.-
CBR
A
L
Y
Y
1
2
3
U
Y
C
Y
N
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
SKIP IF NONE OR NOT APPLICABLE
ENTER PRECEDING ZEROS OR ZERO FILL.
REMAINING DECIMAL PLACES
OPERATIONALLY REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
CANNOT BE REMOVED
Effective Date:
03/05/88
Release Number
Page: .- 51
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM A
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
Effective Date: 10/0 1/.8_& Release Number : 1 . 0 Page
-------
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
(See Figure 14)
This section is used to enter data related to the
various physical characteristics of the public water
sys-tem. The following data may be entered via this
section:
PMS TYPE
(C10S)
Enter a 'C1 if the public water system is a
community system, an *M' if a non-community system,
or a 'P' if a non-transient non-community system.
A community water system is a public water system
that has at least 15 service connections used by
year-round residents or regularly serves at least
25 year-round residents.
A non-community water system is a public water system
that does not meet the requirements to be a community
or a non-transient water system.
A non-transient non-community water system (HTNCWS)
is a public water system that is not a community
water system and that, serves regularly at least 25
service connections used by year-round residents or
regularly serves at least 25 of the same persons over
6 months per year.
ACTIVITY FLAG
(C107)
Enter an 'A' if the public water system is active or
an 'I' if the water system is inactive. If an 'I'
is entered for an inactive PUS, DEACTIVATIOH DATE
must also.be specified.
SYSTEM BEGIN (YR C MO)
(C1.1 1 )
Enter the year and month the public water system
initiated operation. If the date the PWS initiated
operation is not known, enter the "best estimate"
of when operation began. For example, January, 1987
would be entered as 8701.
DEACTIVATION DATE (YR £ MO)
(C113)
Enter the year and month that the system was
deactivated. For example, January, 1987 would be
entered as 8701. DEACTIVATION DATE must be specified
if ACTIVITY FLAG is an 'I1 (inactive).
Effective Date: 10/01/89
Release Number: 1.0
Page: 56
-------
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
RETAIL POPULATION SERVED
C1 17)
- Enter the number of retail customers served by the
public uater system. If the public uater system has
large seasonal fluctuations in the number of retail
customers served, enter the average number of
customers served. When RETAIL POPULATION SERVED is
specified, the following rules apply!
o Must be numeric
o Must be greater than or equal to. 00000001
o Should be greater than or equal to 25 if C1<47,
RETAIL SERVICE CONNECTIONS, is less than 15
NOTE: RETAIL POPULATION SERVED can be zero if no
retail population is served and a service
area characteristic (see Data Capture Form C,
Section C2) identifies the PWS as a wholesaler
of water.
PERCENT SURFACE
(C121)
Enter the annual average percentage of water obtained
from non-purchased, permanently available surface
uater sources. The total of this percentage along
uith PERCENT GROUND, PERCENT PURCHASED SURFACE, and
PERCENT PURCHASED GROUND should be equal to 100.
If the public water system has only one source
of uater, or if all sources are of the same type,
this data does not have to be specified. When
PERCENT SURFACE is specified, the follouing rules
apply:
o Must be numeric
o Must be greater than or equal to zero
o Should be less than or equal to 100
o Must not contain a percent sign (M) or
decimal point (.)
Effective Date:
10/01/89
Release Number: 1.0
Page :
-------
I
SECTIOK A2 - PUBLIC MATER SYSTEM CHARACTERISTICS
PERCENT GROUND
(C123)
Enter the annual average percentage of uater obtained
from non-purchased, permanently available ground
water sources. The total of this percentage along
with PERCENT SURFACE; PERCENT PURCHASED SURFACE and
PERCENT PURCHASED GROUND should be equal to 100.
If the public uater system has only one source
of uater, or if all sources -are of the same type,
this data does not have to be specified. When
PERCENT GROUND is specified, the following rules
apply:
o Must be numeric
o Must be greater than or equal to aero
'o Should be less than or equal to 100
o Must not contain a percent sign (X) or
decimal point (.)
PERCENT PURCHASED SURFACE
CC125)
Enter the annual average percentage of uater
obtained from purchased, permanently available
surface uater sources. The total of this percentage
along uith PERCENT SURFACE; PERCENT GROUND; and
PERCENT PURCHASED GROUND should be equal to 100.
If the public uater system has only one source
of uater, or if all sources are of the same type,
this data does not have to be specified. When
PERCENT PURCHASED SURFACE is specified, the follouing
rules apply:
o Must be numeric
o Must be greater than or equal to zero
o Should be less than or equal to 100
o Must not contain a percent sign C/J) or
decimal point (.)
Effective Date'- 10/0 I/89
Release Number: 1 . Q._
Page: 58
-------
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
PERCENT PURCHASED GROUND
(C127)
Enter the annual average percentage of uater
obtained from purchased, permanently available
ground uater sources. The total of this percentage
along with PERCENT SURFACE; PERCENT GROUND; PERCENT
PURCHASED SURFACE should be equal to 100.
If the public uater system has only one source
of uater* or if all sources are of the same type,
this data does not have to be specified. When
PERCENT PURCHASED GROUND is specified, the following
rules apply:
o Must be numeric
o Must be greater than or equal to zero
o Should be less than or equal to 100
o Must not contain a percent sign (J£) or
decimal point (.)
OWNER TYPE
(C163)
Enter the code value that identifies the type of
ouner of a public uater system. Valid ouner type
codes may be found in SECTION VI, Table 0163, in the
Federal Reporting Data System Data Element
Dictionary ' '
REGULATING ENTITY
(C165)
Enter the code value that represents whether a public
uater system is regulated by Federal, State, both
Federal and State, or neither Federal nor State
drinking uater regulations. Valid codes are as
follows:
»F" =
" S " =
"B" =
"N" =
Regulated by Federal regulations
Regulated by State regulations
Regulated by both Federal and State
regulations
Not State or Federally regulated
RETAIL SERVICE CONNECTIONS
(C147)
Enter the number of retail service connections that a
public uater system had in the most recent year.
When this data element is specified, the following
rules apply:
o Must be numeric
o Should be greater than or equal to 15 if C117,
RETAIL POPULATION SERVED is less than 25
Effective Date: 10/01/89
Release Number* 1.0
59
-------
r
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
PWS SEASOH BEGIN (MO £ DAY)
(C1S9)
. Enter the month and day a non-community or
Non-Transient Non-Community Water System's (NTNCWS)
season of operation normally begins. For example,
October 9th would be entered as 1009. If a community
public water system/ do not provide .this- data.
** See note belou.
PWS SEASON END (MO fi DAY)
(C161) .
Enter the month and day a non-community or
Non-Transient Non-Community Water System's (NTNCWS)
season of operation normally ends. For example.
October 9th uould be entered as 1009. If a
community public water system, do not provide this
data. . , '
** See note below
** NOTE! in order for a non-community Public Mater
System to be considered grant eligible,
the period of time covered by the season
begin and season end dates must be a minimum
of sixty days. The same rule applies to a
non-transient non-community Public Water
System, ex-cept that the minimum period of
time to be covered is 180 days.
Effective Date: 10/01/89
Release Number 1 . 0
Page1 60
-------
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
DATA .ELEMENT REGISTRATION TABLE
DATA
ELEMENT
C10S
C107
C111
C113
C117
C121
C123
C125
C127
C147
C159
C161
3
C165
«
FORM REFERENCE NAME
= = = = = = = = = = = = = = = = = = == = = = = = =
PWS TYPE
ACTIVITY FLAG
SYSTEM BEGIN
DEACTIVATION DATE
RETAIL POPULATION SERVED
PERCENT SURFACE
PERCENT GROUND
PERCENT PURCHASED SURFACE
PERCENT PURCHASED GROUND
RETAIL SERVICE CONNECTIONS
PWS SEASON BEGIN
PWS SEASON END
.
OWNER TYPE
REGULATING ENTITY
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG . CBR
= = = = = = = = = ssa = = = = = = = = = = = = = sss
A
A
N
N
N
N
N
N
N
N
N
N
A
A
N/A 2
N/A 2
L *
L Y Y «+
L 2
L Y
L Y
L Y
L Y
L 2
L Y Y
L Y Y
N/A
N/A
Y N
Y N
Y
Y
Y N
Y
*
Y
*
Y N
C Y
C Y
Y Y
Y Y
LEGEND:
A/N/D -
JUST -
SIN -
ZERO FILL -
REG. CODE -
GRANT ELIG.-
CBR
A = ALPHANUMERIC, N = NUMERIC, D = DECIMAL
L = LEFT 'JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
Y = SKIP IF NONE OR NOT APPLICABLE
Y = ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
1 = OPERATIONALLY REQUIRED
2 = PROGRAMMATICALLY REQUIRED
3 = OPERATIONALLY REQUIRED, CONDITIONALLY
4 * PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
Y = DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
C = DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N =. CANNOT BE REMOVED
Effective Date:
10/01/89
Release Number: 1 . 0 . Page:
-------
FRDS-II DATA EKTRY INSTRUCTIONS
DATA CAPTURE FORM A
SECTION A3 - OTHER ADDRESS(ES)
Effective Dates 10/01/89 Release Numbers 1.Q Page' 62
-------
SECTIOM A3 - OTHER ADDRESSCES)
(See Figure 14)
This section is used to enter additional address infor-
mation' such as an ounez address or related facility
addresses. The following data may be entered via this
section:
ADDRESS ID
(C301 )
ADDRESS TYPE
Enter a numeric value that uill uniquely identify
an owner address, treatment facility address, or
other address related to the public uater system.
ADDRESS ID must be valued in order for a new address
record to be inserted into the FRDS-II Data Base.
Note' See Chapter VI, "Record Identification and
Maximum Occurances" for user assignment and
automatic generation of this ID.
Enter the code value that identifies the type of
addressee or facility of a public uater system. The
address type codes are contained in SECTIOM VI, Table
0303 in the Federal Reporting Data System Data
Element Dictionary. ADDRESS TYPE must be valued in
order for a neu address record to be inserted into
the FRDS-II Data Base.
ADDRESSEE MAHE
(C305)
ADDRESS LIKE
(C307)
Enter the name of an addressee or facility of a
public uater system. Any combination of alphabetic
numeric, or special characters is allowed.
Enter the first line of an address applicable to a
public uater system addressee or facility. This can
be used for the name of a responsible person or
agency, or it can be an additional address line
applicable to the location of a public uater system
addressee or facility.
ADDRESS LIKE 2
CC309)
Enter the second line of an address applicable to
a public water system addressee or facility.
ADDRESS LINE 2 is the street, rural route and box
designation, etc. that is applicable to the location
of a public uater system addressee or facility.
Effective Date: 10/01/89
Release Mumber: 1.0
Page: 63.
-------
SECTION A3 - OTHER ADDRESS(ES)
CITY
(C311
STATE
(C313)
ZIP CODE
CC315)
Entez the city in which a public water system
addressee or facility is located.
Enter the U. S. Postal Service State abbreviation
in which a public water system addressee or facility
is located.
Enter the U. S. Postal Service ZIP code in which a
public uater system addressee or facility is located.
If the + 1 portion of .the ZIP CODE + t» is unknown,
leave that portion blank. At least the 5-digit
portion of ZIP CODE + 4 must be valued in order for a
new address record to be inserted into the FRDS-II
Data Base.
Effective Date: 10/01/89
Release Number: 1 .j) Page= 6J
-------
SECTION A3 - OTHER ADDRESS(ES)
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
FORM REFERENCE NAME
: = = = = = = = = s:sasss = = s = = = sssss = = = s =
C301 ADDRESS ID
C303 ADDRESS TYPE
C305 ADDRESSEE NAME
C307 ADDRESS LINE 1
C309 ADDRESS LINE 2
C311 CITY
C313 STATE
C31S ZIP CODE + 4 *
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR
:=== asss sssxss sssss
3 N
Y
Y
Y
Y
Y
Y
Y
N
A
A
A
A
- A
A
A
L
N/A
L
L
L
L
L
L
Y
Y
* Provide 9-digit sip code if known - 5-digit sip code is acceptable
LEGEND:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE
GRANT ELIG.-
CBR
A
L
Y
Y
C
Y
N
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
SKIP IF NONE OR NOT APPLICABLE
ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
OPERATIONALLY.REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY RE2UIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
RE2UIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS RE2UIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY RE2UIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
CAN BE REMOVED (i:e., * IN LEFT-MOST POSITION)
CANNOT BE REMOVED
Effective Date: _l_0_/.O.t/89
Release Number:
Page: 6 5
-------
v>
oae
Public Water System
Data Capture Form A
PWS 10
Sut* i
I I I I I I
4CTKWCOOE
I I
u
BATCH DATE
no o»r nt
I I I I I I I
(CIO,,
SYSTEM ADDRESS
SYSTEM NAVE
1 ! 1 1 1 ! 1 1 1 1 1 ! 1 ! 1 t 1 ! 1 ! ! f 1 1 1 1 1 1 1 "l
IC131)
AOOACS9UNE1 ' "
1 1 1 1 I 1 I f 1 f 1 1 1 1 1 1 1 1 1 1 1 ! 1 1 1 1 ! I 1 1
AOOHEUUNE2
1 ! 1 !! 1 1 1 1 ! 1 1 ! 1 1 1 I 1 1 1 1 1 1 1 I 1 1 1 1 1
CfTY STATE ZPCOCC +4
1 ! I 1 I I 1 ! 1 ! ! 1 I I t 1 III 1 1 1 1 1 1 1 I 1
(C1371 . IC13B! (CM1)
ADEACCOE KUUBER
i 1 1 1 1 !- 1 1- 1 ! 1
(C143)
|
|
|
J
,
|A2
SOUSCi
PUBLIC WA TER SYSTEM CHARACTERISTICS
PW3 ACT.VTY SYSTEM BEGIN DEACTIVAnONOATE BETAl POPULATCN SERVED
1 TYPE C.CCMtUKTr f"M Yfl MO YH UO
UH.MKKOUUMTT I 1 «.»CTIW 1 1 1 1 1 1 1 1 1 1 Illlllll
r.*cm.tai**na 1 II.MCTM 1, i.,.1. 1III1II Illl! 1 1 I
,CIOS) W"COM«j»mr ,C107) (CIIII. [CH3> (C)17)
PERCENT PERCENT , PtRC£NTI»U HOUSED PERCENT PURCHASED
SURFACE OaOUNO SURFACE QROUNO
EWIERIiniSO I I I + | I I | + I I I + | I | | = 100%
.GUI) |C123) (C1»l 1C127)
NGN COMMUNITY SEASON
OWNER REGULATING - BEGIN £NO
TYPE ENTITY HETAJ. SEflVCE CONNtCTOiS UO DAY. UO DAV
it ii 1 1 .11 1 1 1 1 Mill 1 i I i 1
(C1UI jClSSI (CUT) (CIKfl (CHI)
J
.
[Ja]
OTHER ADDRESS(ES)
|Q TYPE ADDRESSEE NAME
1 ! 1 1 1 1 I 1 1 1 1 ( ! 1 1 i ! ! 1 ] ! 1 I 1 1 1 [ 1 1 1 1 1 1 1 1
(C3011 (C3OJI iCaJSI
AOOHESS LINE 1
1 1 1 1 1 1 1 1 1 1 1 1 I 1 1 I 1 1 1 1 1 1 1 1 1 1 1 1 1 1
(C307)
ADORESS LINE 2
l_l J t ! 1 I 1 1 1 1 ! t I 1 1 ! I 1 1 I 1 1 1 1 1 1 1 1 1
(C309)
CITY " STATE ZPCOOC +«
1 ! 1 1 1 ! 1 I 1 1 I 1 1 1 1 1 Ml 1'! 1 I 1 1 III
icani iC3i3i tciisi
J
J
J
J
Figure 14
Effective Date: 10/Q. 1 /89 Release Number: 1.0 .
2 6 6
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM B
SECTION B1 - SOURCE / ENTITY DATA
Effective Date: 10/01/89 Release .Number = 1 .0 . Pages 67
-------
SE ID
(CHOI)
NAME
(C
-------
SECTION B1 - SOURCE / ENTITY DATA
SE CODE
(C407)
Enter the code that describes the type of source
water, entry point or plant. Valid SE CODEs may
be found in SECTION VI, Table 0407, in the FRDS-II
Data Element Dictionary.
SE CODE is used in conjunction uith C405 (SE RECORD
TYPE) and must be a valid combination thereof. Valid
combinations may be found in SECTION VI, Table
ID10, in the FRDS-II Data Element Dictionary.
AVAILABILITY
(C409)
SELLER PWS ID
(C411)
Enter the code value that represents the
circumstances under which a source of water
utilized by, or an entity related to, a public
water system is used or operated. Examples of
valid codes may be found in SECTION VI, Table 0409,
in the Federal Reporting Data System Data Element
Dictionary.
Enter the State-prefixed PWS ID of the public
water system from whom water is purchased. SELLER
PWS ID is valid only for purchased sources of water
(i.e., where SE RECORD TYPE is an "S" and SE CODE is
"P" or "M").
Effective Date:
10/0 1/89
Release Number: 1.0
Pages 6J.
-------
SECTION B1 - SOURCE / ENTITY DATA
LATITUDE (DEC, HIN, £ SEC)
(cm 5) *
Enter the degrees, minutes, and seconds of LATITUDE
for the location of the entity being reported.
LATITUDE is required when inserting a Source / Entity
record, if LONGITUDE is specified.
Valid min/raax latitudes may be found in Sec.tion VI,
Table 0509 (TIPS County Codes) and 0427 (Hydrologic
Unit Codes) in the Federal Reporting Data System
Data Element Dictionary.
When blanking out (initialising to nulls) LATITUDE
by using a dollar sign ($) in the left-most position,
LONGITUDE will also be blanked out (initialised to
nulls).
LONGITUDE (DEC, WIN, £ SEC)
(cm 7) -' .
Enter the degrees, minutes, and seconds of LONGITUDE
for the location of the entity being reported.
LONGITUDE is required uhen inserting a Source /
Entity record, if LATITUDE is specified.
Valid min/raax longitudes may be found in Section VI,
Table 0509 (TIPS County Codes) and 0427 (Hydrologic
Unit Codes) in the Federal Reporting Data System
Data Clement Dictionary.
Uhen blanking out (initializing to nulls) LONGITUDE
by using a dollar sign (*) in the left-most position,
LATITUDE will also be blanked out (initialized to
nulls ) .
Effective Date:. 10/01/89 Release Number- 1 ,0 Pages 70
-------
SECTION B1 - SOURCE / ENTITY DATA
TOWNSHIP / RANGE
C419, C421, C423, C425)
Enter the TOWNSHIP / RANGE data for the location
of the entity being reported. When TOWNSHIP /
RANGE data is specified, the following rules apply:
TOWNSHIP / RANGE data is used to describe an area
of land and is made up of four separate data
elements. None of these four data elements is
meaningful by itself, but when all are used, they
will define an area of one quarter square mile.
(See figure 15 on the following page.) The four
data elements are described as follows:
TOWNSHIP (C419) - Positions 1 - 3 is a number that
represents the location of a TOWNSHIP in relation-
ship to a known base line. Position 4 is the dir-
ection ("Nn for North, or "S" for South) from a known
base line. Rules for entering TOWNSHIP are as
follows:
o Positions 1-3 must be numeric
o Positions 1 - 3 must be greater than or equal to
001
o Position 4 must be ...
"N" (i.e., the township is north of the base
line) or
"Sn (i.e., the.,, township is south of the base
line)
RANGE (C421) - Positions 1 - 3 is a number that
represents the location of a RANGE in relationship
to a known Principal Meridian. Position 4 is the
direction (ȣ"* for East or "W" for West) from a known
Principal Meridian. The rules for entering RANGE
are as follows:
o Positions
3 must be numeric
o Positions 1 - 3 must be greater than or equal to
001
o Position 4 must be ...
"E" (i.e., the range is east of the Principal
Meridian) or
"W" (i.e., the range is west of the Principal
Meridian)
Effective Date: 10/01/89
Release Number 1:0
Page :
-------
TOWNSHIP GRID
NORTH
wesTt
j
i
|
*
3
T 25.
R 3W
BA
2
._ <
Q
xUJ ' i ' : '
^»^ intlMl Poinf
I !
i
' 1 i ;
SOOTH
TOWMSH«> 1 SOUTH. KAMOI1 WEST
T
IS
1*
M
31
1
(T
M
79
17
«
*
' .
71
18
33
1
10
U
ZJ
J7
J4
2
tl
SEC.
14
V
\
u
1
U
y
.24
a
V
SECTION 1«
J__ g-^%%%% i
Effective Date:
Figure 15
10/01/a 9 Release Number:
Page: 72
-------
SECTION B1 - SOURCE / ENTITY DATA
SECTION (C123) - This is a numeric value that rep-
resents one of the 36 sections of a township. The
36 sections are numbered in.a aigsag fashion,
beginning with section 01 in the northeast corner
of a township and ending with section 36 in the
southeast corner of the township. SECTION must
be entered under the following rules:
o must be numeric
o must be greater than or equal to 01 and
less than or equal to 36.
2UARTER SECTION (CU25) - This an alphabetic value
that represents a particular quadrant of a section.
The four quadrants are identified as follows:
o "NW* (i.e., the northwest quadrant of the section)
o "ME" (i.e., the northeast quadrant of the section)
o "SU" (i.e., the southwest quadrant of the section)
o "SE" (i.e., the southeast quadrant of the section)
When blanking out (initialising to nulls) TOWNSHIP/
RANGE data the following rules apply1
o A dollar sign ($) in the left-most position of
TOWNSHIP or RANGE will cause all TOWNSHIP/
RANGE data to be blanked out.
o A dollar sign ($) in the left-most position of
SECTION will cause SECTION and BUARTER SECTION
to be blanked out.
o A dollar sign (S) in the left-most position of
2UARTER SECTION will cause only QUARTER SECTION
to be blanked out.
RIVER REACH
(C427)
Enter the value that identifies the hydrologic unit
code and, if appropriate, the segment number for the
location of the source or entity being reported.
For a complete description of RIVER REACH, see the
Federal Reporting Data System Data Element Dictionary.
Valid hydrologic unit codes are found in SECTION VI,
Table 0427, in the Federal Reporting Data System Data
Element Dictionary.
Effective Date: 10/01/89 Release Number: 1.0 Page:
-------
SECTION B1 - SOURCE / ENTITY DATA
ON REACH - .
CCH29)
Enter the value that represents whether a source of
uater is "on" or "off" a defined river reach.
'If the source of water is on a defined river reach
enter a "Y". If the source of water is off a
defined river reach, enter an "N". ON REACH is
required when RIVER REACH or REACH MILES has
been specified. For a complete discussion of
ON REACH, see the Federal Reporting Data System
Data Element Dictionary, under C427,
PWS-SE-RIVER-REACH-NUM, and C429, PWS-SE-ON-REACH.
REACH MILES
(CH31) ''..
Enter the numeric value that defines an enact location
in miles, of a surface source intake in relationship
to the downstream end of the river reach, if the
source is "on" a defined river reach.
o The integer portion cannot exceed H positions
o The decimal portion cannot exceed 2 positions
o Must be numeric
o Must be greater than or equal to zero
The rules for entering decimal .numbers into the
FRDS-II System, are discussed in Chapter VII.
"GENERAL CODING INSTRUCTIONS."
Effective Date: 10/0 1/89 Release Number: 1.0 Page: 7<4
-------
SECTION B1 - SOURCE / ENTITY DATA
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
ELEM
=51^
FORM REFERENCE NAME
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG . GBR
CH01
C403
C40S
C407
C409
C41 1
C<415
C417
C419
C<421
C423
B,5-
C427
C429
C431
SE ID
NAME
SE RECORD TYPE
SE CODE
AVAILABILITY
SELLER PUS ID
LATITUDE
LONGITUDE
TOWNSHIP
RANGE
SECTION
QUARTER SECTION
RIVER REACH
ON REACH
REACH MILES
N
A
A
A
A
A
N
N
A
A
N
A
A
A
D
L
L
N/A
N/A
N/A
L
L
L
L
L
L
L
L
N/A
A
SIwB, s; = = is
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM B
SECTION B2 - TREATMENT DATA
Effective Date= 10/01/89 Release Number: 1.0^ Page:
-------
SE ID
SECTIOH B2 - TREATMENT DATA
(See Figure 16)
This section should be used to enter data that identifies
treatment objectives and processes that are applied to a
unique source of uater used by a public uater system.
At least one treatment data record must be specified for
each source of uater used by a public system. A complete
treatment record consists -o£ the TREATMENT OBJECTIVE
and the TREATMENT PROCESS. The following data .may be
entered via this section:
For both SE ID and TREATMENT ID below, see
Chapter VI, " Record Identification and
Maximum Occurances" for user assignment and
automatic generation of this ID. Also, see
Appendix C, "Anytoun USA, Public Mater
System", for examples of Source/ Treatment
relationships.
Enter the SE ID that identifies the source of uater
to uhich this treatment data is to be applied. In
order to be registered into the FRDS-II system
every source must have a treatment objective and
treatment process specified.
TREATMENT ID
(C<48 1)
Enter a numeric value that uill uniquely identify
the specific treatment to be applied to a source
of uater.
TREATMENT
(C483)
OBJECTIVE
Enter the code value that identifies the objective
to be attained through treatment of a source of
uater. The code value specified must be a valid
treatment objective code as found in SECTION VI,
Table IDOS, in the Federal Reporting Data System
Data Element Dictionary. It should be noted that
a valid treatment objective is "no treatment" and
if applicable, TREATMENT OBJECTIVE should be coded
as such (i.e., TREATMENT OBJECTIVE code of "N" and
TREATMENT PROCESS code of "000").
TREATMENT OBJECTIVE is used in conjunction uith
C485 (TREATMENT PROCESS) and must be a valid
combination thereof. Valid combinations may be
found in SECTION VI. Table ID03, in the FRDS-II *
Data Element Dictionary.
Effective D.ate =
10/01/89
Release Number: 1.0
Page :
77
-------
SECTION B2 - TREATMENT DATA
TREATMENT PROCESS
CC485)
Enter the code value that identifies the treatment
process to be applied to a source of water. The code
value specified must be .a valid treatment process
code as found in SECTION VI, Table ID01, in the
Federal Reporting Data Systems-Data E-lement Diction-
ary. It should be'noted that a valid treatment
process is "no treatment" and if applicable, should
be coded as such. (i.e., TREATMENT OBJECTIVE code of
"N" and a TREATMENT PROCESS code of "000").
TREATMENT PROCESS is used in conjunction with C183
(TREATMENT OBJECTIVE) and must be a valid combination
thereof. Valid combinations may be found in SECTION
VI, Table ID03, in the FRDS-II -Data Element
Dictionary.
Effective Dates 10/01/89 Release Number: 1_. 0 Page: 7J
-------
DATA
ELEMENT
i:
SECTION B2 - TREATMENT DATA
DATA ELEMENT REGISTRATION TABLE
ZERO REG. GRANT
FORM REFERENCE NAME A/N/D JUST SIN FILL CODE ELIG. CBR
C401 SE ID
C481 TREATMENT ID
Ct83 TREATMENT OBJECTIVE
C<*85 TREATMENT PROCESS
N L
N L
A N/A
N L
Y
V
Y -
C
C
N
N
Y
Y
LEGEND:
A/N/D
JUST
SIN
ZERO FILL
REG. CODE
GRANT ELIG.-
CBR
Effective Date:
A
L
Y
Y
1
2
3
4
Y
C
Y
N
10/0 1/89
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
SKIP IF NONE OR NOT APPLICABLE
ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
OPERATIONALLY REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
CAN BE REMOVED (i.e., $ IN LEFT-MOST POSITION)
CANNOT BE REMOVED
Release Number: 1.0
Page '
-------
Public Water System
Data Capture Form B
Sat.
1 1 i
PW3 ID
ONtun
III!
M>
t 1 1
CTOK
ACTION CODE
u
BATCH DATE
MO otr r*
I i M I i I
3E 10
|B1|l ! 1 I
SOURCE / ENTITY DATA SE
RECORD
NAME TYPE
1 1 ! 1 ! ! 1 1 1 1 1 1 1 1 I 1 1 1 1 1 t 1 1 1 1
IC401) iCMMI
5ELLEAPWSO 3ATA LATtTUOE
STATE 0 NUMBER ORCW .^j UN
1 I 1 1 M M M 1 1 M 1 1 1
IC4I1)
C*»J1 iC*1SI
. TOWNSHPN* . "ANGE L"* SEC ' «StC HVDRCtCGIC
1 1 I 1 M 1 1 M 1 I 1 i i i i i
.C41»l
|B2| =E
I
LL
LL
LL
LL
i«m
,c*»u ,0*11) *«jsi icun
1 0051
LONGITUDE
SEC 3EO *»« SEC
1 1 1 1 1 1 Ml
C4t71
SiVtR REACH ON
UNIT COW SEG HUM REACH
1 1 1 1 1 1 1 I_I 1
,C*J») !&1
TREATMENT DATA
DJAIXUNT "nEATVftr TREAT
O o OBJECTIVE =POC
1 II II 1
1 1 1
1 II
1 1 1
1 1 1
,C«1|
U LL
U LL
U LL
U LL
SE
COOS AVAILABUTV
u y
REACH UtES
1 1 1 ! 1 1
jn
KENT
ESS
u
u
JJ
u
1 '(
SE 10
SOURCE / ENTITY DA TA «
RECORD
NAME nrPE
1 1 I 1 1 1 1 1 ! 1 ! ! 1 1 1 1 1 1 1 1 1 1 M 1
SELLEHPVWIO CATA LATfTUOE
STATE O NUMBER ORCIN QJQ UM
M 1 M M M 1 1 1 M 1
LONGmjOE
5£C EEC MN SEC
1 i 1 1 1 1
iC411| (C4IJ) tC4)S) 1C4I7)
TOWNSHIP RANGE niVEHHE*CH ON
TOWNSHIP N/3 RANGE LW SEC 1-'«S£C HYOROLOCC UNfT CODE SEG HIM REACH
M 1 I 1 I I l 1 l 1 l 1 i i i i i i i i i i i 1 1 i 1
.C4t»»
|B2| *
1
u
LL
LL
LL
(001)
,C4ai> i£+23) t O*2 if .O427)
TREATMENT Dt
0 TnEATttENT
1 II
1 1 1
1 II
1 II
1 1 1
(C4*l)
|[>«9) |CX
\TA
TTIEATMEXT EAT
OBJECTIVE PRCX
U LL
U LL
U LL
U LL
U LL
(C-U3I (C«5j
SE
CODE AVAILABIITY
U LJ
(CJO« 1C409)
REACH MILES
1 1 1 i-l 1 1
1311
WENT
:ESS
JJ
JJ
JJ
JJ
_LJ '
r
Effective Dates 10/01/89
Fig.ure 16
Release Number:
Page" 80
-------
I
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM C
SECTION Cl - GEOGRAPHIC AREAS SERVED
Effective Date: 10/01/89
Release Number: 1 . 0
Page! 81
-------
SECTION C1 - GEOGRAPHIC AREAS SERVED
(See Figure 17)
This section is used to enter data that identifies geo-
graphic areas or jurisdictions served by a public water
system. All data elements uithin a single geographic
areas served record should be valued with related data
elements, uhich describe a single geographic area. For
example, if city "X" is in county "A", they both should
be specified in the same geographic areas served record.
Conversely, if city "X" is outside of county "A", they
each should be specified in a separate record. The
FRDS-II Data Base has one geographic areas served record
for each geographic area served that has been reported
to EPA. The following data may be entered via this
section:
GA ID
(CS01)
Enter a GA ID that will uniquely identify a specific
geographic area served.
Note: see Chapter VI, "Record Identification and
Maximum Occurances" for user assignment and
automatic generation of this ID.
ADMIN REGION
(C503)
Enter the code value that represents the State
administrative region, if any, that is being
served by a public water system in whole or in
part.
ADHIN DISTRICT
(C505)
Enter the code value that represents the State
administrative district, if any, that is being
served by a public water system in whole or in
part.
FEDERAL CONGRESS DISTRICT
(C507)
Enter the code value that represents the Federal
congressional district, that is being served by a
public water system in whole or in part. When
specified. FEDERAL CONGRESS DISTRICT must be a valid
Federal congressional district code for the State
as found in SECTION VI, Table 0507, in the Federal
Reporting Data System Data Element Dictionary.
Effective Date: 10/01/89 Release Number: 1.0 Page: 82
-------
SECTION C1 - GEOGRAPHIC AREAS SERVED
STATE COUNTY CODE
KC508)
Enter the State county code as applicable to the
State. When specifying only the STATE COUNTY CODE,
a one-for-one STATE COUNTY CODE to FIPS COUNTY CODE
conversion table must be provided by the user.
FIPS COUNTY CODE . .
(C509)
Enter the FIPS COUNTY CODE as applicable to the
State. Valid FIPS COUNTY CODES may be found in
SECTION VI. Table 0509 in the Federal Reporting Data
System Data Element Dictionary.
When the primacy agent specifies only the STATE
COUNTY COD.E, the FRDS-II System uill use the STATE
COUNTY CODE to FIPS COUNTY CODE table for county code
conversion and uill store BOTH the STATE COUNTY CODE
and FIPS COUNTY CODE in the FRDS-II Data Base. If
the primacy agent specifies only the FIPS COUNTY
CODE, ONLY the FIPS county code will be stored in the
FRDS-II Data Base '.
CITY
(C513)
Enter the city, community, or jurisdiction that is
being served by the public uater system, in whole or
in part.
INDIAN RESERVATION
CCSIS)
Enter the code value that represents the Indian
reservation or Alaska remote village, if any, being
served by a public water system in whole or in part
When specified, this data element must be a valid
Indian reservation or Alaska remote village code as
defined in SECTION VI, Table ID01 in the Federal
Reporting Data System Data Element Dictionary.
Effective Date: 10/01x89 Release Number: 1.0 Page: S3
-------
DAT A
ELEMENT
NUM.
SECTION C1 - GEOGRAPHIC AREAS SERVED
DATA ELEMENT REGISTRATION TABLE
FORM REFERENCE NAME
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG. GBR
C501 GA ID
CS03. ADMIN REGION
C505 ADMIN DISTRICT
C507 FEDERAL CONGRESS DISTRICT
C508 STATE COUNTY CODE
CS09 FIPS COUNTY CODE
C513 CITY
C515 INDIAN RESERVATION
N
A
A
.A
A
A
A
A
L
L
L
L
L
L
L
L
Y
Y
Y
Y
Y
Y
c
c
N
Y
Y
Y
Y
Y
Y
Y
LEG-END:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE
GRANT ELIG.-
CBR
A = ALPHANUMERIC, N = NUMERIC, D - DECIMAL
L = LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
Y = SKIP IF NONE OR NOT APPLICABLE
Y = ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
1 = OPERATIONALLY REQUIRED
2 = PROGRAMMATICALLY REQUIRED
3 = OPERATIONALLY REQUIRED. CONDITIONALLY
H = PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
Y = DATA ELEMENT IS REQUIRED FOR A PMS TO BE
CONSIDERED "GRANT ELIGIBLE"
C = DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N = CANNOT BE REMOVED
Effective Dates
10/01/89
Release Number-
Page' &j±
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM C
SECTIOH C2 - SERVICE AREAS
Effective Date: 10/01/89 Release Number: 1 . 0 Page1 SJJ
-------
SERV ID
(C601)
TYPE/CAT
CC603)
SECTION C2 - SERVICE AREAS
(See Figure 17)
This section is used to enter data that characterizes the
type of area served by the public uater system. The
FRDS-II Data Base has one record for each type of area
served that is reported to EPA. Non-transient
non-community and non-community water systems must have
one, and only one, service area designated as primary.
The following data may be entered via this section:
Enter a SERV ID that will uniquely identify a
specific service area.
Note: see Chapter VI, "Record Identification and
Maximum Occurances" for user assignment and
automatic generation of this ID.
Enter the code value that characterizes the type of
area serviced by the public uater system. It is
likely that a public uater system uill have several
types of service areas* so the FRDS-II system uill
allow many repetitions of this record for each public
uater system in the data base. When specified,
position 1 of the TYPE/CAT must be one of the
follouing codes '
"R"
nmn
"S"
"0"
(a residential area) or
(a transient area) or
(a semi-residential area)
(other than above)
or
and position 2 must be a valid service area
sub-category code that is applicable to the major
service area types as defined in SECTION VI, Table
0603 in the Federal Reporting Data System Data
Element Dictionary.
PRIMARY SERVICE FLAG
(C605)
Enter a "Yn if the service area is the primary (i.e.,
most prevalent) type of area served by the PWS. This
data element must be valued for non-community and
non-transient non-community public uater systems.
It is important to note that only one area served by
a public uater system can be designated as the
primary type.
Effective Date' 10/0 1/89
Release Number: 1.0
Page: 86
-------
DATA
PENT
= = =
SECTION C2 - SERVICE AREAS
DATA ELEMENT REGISTRATION TABLE
FORM REFERENCE NAME
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR
C601 SERV ID
C603 TYPE/CAT
C605 PRIMARY SERVICE FLAG
N L
A L
A N/A
N
Y Y
C* Y
A/N/D
JUST
SIN
ZERO FILL
REG. CODE -
NOT APPLICABLE
ZEROS OR ZERO FILL
* Requires that each non-community or non-transient non-community
public water system must identify one and only one of its service
areas as primary.
LEG-END:
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
SKIP IF NONE OR
ENTER PRECEDING
REMAINING DECIMAL PLACES
OPERATIONALLY REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
C = DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N = CANNOT BE REMOVED
A
L
Y
Y
1
2
3
4
GRANT ELIG.- Y =
CBR
Effective Date:
10/01/89
Release Number:
1 . 0
Page :
-------
FRDS-II DATA ENTR* INSTRUCTIONS
DATA CAPTURE FORM C
SECTION C3 - ON-SITE VISITS
Effective Date: 10/01/89 Release Number: 1.0 Page: 88
-------
SECTION C3 - OK-SITE VISITS
(See Figure 17) '
This section is used to enter data that is related to
on-site visits made to a public water system. The
FRDS-II Data 'Base has one on-site visit' record for each
on-site visit (such as a sanitary survey), that has
been reported to EPA. The following data may be entered
via this section:
VISIT ID
(C701)
VISIT ID will ALWAYS be generated by the FRDS-II
Computer System.
Notes See Chapter VI, "Record Identification and
Maximum Occurances".
VISIT DATE (MO, DAY, £ YR)
(C703)
Enter the calendar date on uhich a visit uas made to
a public uater system. When specified, VISIT DATE
must be a valid calendar date and must be in the
form "MMDDYY" where'
MM = Calendar Month
DD = Calendar Day
YY * Calendar Year
ISIT REASON
Enter the code value that represents the reason that
a visit uas raade to a public uater system. When
specified, .enter the appropriate code into position
1 of the VISIT REASON as follous:
i v
2
Class I Survey -(i.e..
Class II Survey (i.e
sanitary survey)
sanitary survey)
other than a
Position 2 is valid for Class II surveys. See
SECTION VI, Table 0705 in the Federal Reporting Data
System Data Element Dictionary for valid on-site
visit reason codes. Position Z must be blank if a
Class I Survey is specified.
Effective Date
10/01X89
Release Number: 1 .-Q
Page: §&
-------
SECTION C3 - ON-S1TE VISITS
DATA ELEMENT REGISTRATION TABLE
FORM REFERENCE NAME
DATA
ELEMENT
'IM.
C701 VISIT ID
C703 VISIT DATE
C70S VISIT REASON
. ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG . CBR
N L
N L
A L
Y
Y
:aaaa aas
N
Y
Y
LEGEND:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE -
GRANT ELIG.-
CBR
A = ALPHANUMERIC, N = NUMERIC, D = DECIMAL
L a LEFT JUSTIFY, R - RIGHT JUSTIFY, A = ALIGN
Y a SKIP IF NONE OR NOT APPLICABLE
Y » ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
1 = OPERATIONALLY REQUIRED
2 = PROGRAMMATICALLY REQUIRED
3 - OPERATIONALLY REQUIRED, CONDITIONALLY
t = PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
Y = DATA ELEMENT IS REQUIRED FOR A PUS TO BE
CONSIDERED "GRANT ELIGIBLE"
C = DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PMS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N = CANNOT BE REMOVED
Effective Date: TO/01/89
Release Number: 1.0
Page: 90
-------
Public Water System
Data Capture Form C
"- ' ***" PWSO ACTION t
Stm DNwnMr
1 1 1 1 1 1 1 1 1 1 ||
(CtOIJ
fci"| GEOGRAPr
FEDERAL
AOMIN ADMM CONGRESS STATE FIPS
GAD REGION DISTRICT DISTRICT COUNTY COUNTY
1 1 II 1 II 1 1 I 1 1 1 III 1
1 ' II 1 II 1 1 1 1 1 1 III 1
ill i i i i 1 II! 1
i i ii i 1 1 i i i i i 1 Ml 1
(CSOl) (C503) (CMS) JCM7) (Cgg, (Cm)
IC2I SERVICE AREAS
PRIMARY
SERV SERVICE
ID TYPE/ CAT FLAG
|ll III II
III III II
III III II
III III II
III III II
III III II
(ceoi) (can (COB)
DOC
IK
1
1
1
1
* BATCH DATE
i 7 i T i 7 i
/-hM« w.Mortiy 1 1 i 1 1 1 1
1 AREAS SERVED
CITY ' INDIAN
RESERVATION
1 II II
1 II 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 II
jCStS) (CS15)
IC3I ON-SITE VISITS
VISIT VISIT DATE VISIT
ID MO DAY YR REASON
1 I 1 1 1 1 II 1 LJ_J
MI I I i I I 1 LU
Ml 1 Mill U_J
1 i 1 1 Mill LLJ
til | | 1 1 1 i LLJ
i i i 1 II 1 1 1 LLJ.
(C701) (C70J) f07"*!
Figure 17
Effective Date= 10/01/89 Release Number:
1.0 Page! £1
-------
FRDS-rll DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM D
SECTION D1 - VIOLATION DATA
Effective Date: j0/01/eq Release Number*. 1.0 Pages ,92
-------
SECTIOM D1 - VIOLATION DATA
(See Figure 18)
This section is used to en.ter data that characterizes
a violation of a primary drinking uater regulation
issued to a public uater system by a State or Federal
agency. The FRDS-II Data Base has one violation record
for each violation that has been reported to EPA. The
following data may be entered via this sections
VIOLATION ID
(C1101)
CONTAMINANT
(C1103)
-------
SECTIOM D1 - VIOLATION DATA
COMPLIANCE PERIOD BEGIN (WO, DAY, £ YR)
(C1107) , . :- . .',
Enter the calendar date of the beginning of the
compliance period for which the public uater system
was in violation of a primary drinking uater
regulation. COMPLIANCE PERIOD BEGIN is required
for all violations.
COMPLIANCE PERIOD END (MO, DAY, £ YR>
CC1109)
Enter the calendar date of the end of a compliance
period in which a public uater system was in
violation of a primary drinking uater regulation.
COMPLIANCE PERIOD END is required uhen inserting a
violation record, when COMPLIANCE PERIOD DURATION
is not specified.
COMPLIANCE PERIOD DURATION
CC1111)
Enter the number of calendar months of the compliance
period during which a public uater system uas in
violation of a primary drinking regulation.
COMPLIANCE PERIOD DURATION is required uhen inserting
a violation record and uhen COMPLIANCE PERIOD END is
not specified.. This data element should not be input
uhen COMPLIANCE PERIOD END is specified.
AWARENESS DATE (MO, DAY, £ YR)
(C1115)
Enter the calendar date that the primacy agent
became auare of this violation.
NUM SAMPLES RE2UIRED
(C.1127)
Enter the number of samples for monitoring and
reporting violations that uere required to be
collected, analyzed, and reported by a public uater
system for a specific compliance period. If not
a monitoring or reporting violation, do not provide
this data.
SE ID
(C1143)
Enter the SE ID of the source, plant or entity for
uhich, the violation uas entered.
Effective Date: 10/01/89
Release Number: 1.0
Page: r 9
-------
SECTION D1 - VIOLATION DATA
NUM SAMPLES TAKEN
(C1129) '
Enter the number of samples for monitoring and
reporting violations that were actually collected,
analyzed, and reported by a public water system for a
specific compliance period. If not a monitoring ox
reporting violation, do not provide this data.
MAJOR VIOLATION
(C1131)
Enter a "₯" if a major monitoring or reporting
violation. A major violation is one where no
samples were taken during a compliance period.
Enter an "K" if a minor violation.
If not a monitoring or reporting violation, leave
blank. MAJOR VIOLATION does not apply to check
sampling violations.
ANALYSIS METHOD
CC1121)
Enter the code value that represents the analysis
method used to obtain an analytical result uhich
led to the issuance of the MCL violation for a
public water system. ANALYSIS METHOD must not
be specified for monitoring and reporting violations.
Hhen specified, this data element must be a valid
analysis method code as described in SECTION VI,
Table 1121, in the Federal Reporting Data System
Data Element Dictionary.
Effective Date: 10/01/89
Release Number: 1.0
Page: 95
-------
SECTION D1 - VIOLATION DATA
ANALYSIS RESULT .
CC1123) '
Enter the numeric value that represents the result
obtained from a single analysis, or the average
result obtained from multiple analyses, that led
. . to the issuance of the MCL violation for a public
water system. ANALYSIS RESULT is required for
inserting a violation record for MCL violations
of other than BACTI or turbidity. When specified,
ANALYSIS RESULT must be entered under the following
rules s .
o Must be specified for MCL violations, other
than BACTI or turbidity.
o The integer portion cannot exceed 7 positions
o The decimal portion cannot exceed 8 positions
o Must be numeric
o Must be greater than or equal to zero
The rules for entering decimal numbers into the
FRDS-II System, are discussed in Chapter VII,
"GENERAL CODING INSTRUCTIONS."
MCL VIOLATED
(C1125)
Enter the numeric value that represents the maximum
contaminant level uhich was exceeded that led to the
issuance of an MCL violation for a public water
system. MCL VIOLATED is required for inserting
a violation record only if the primacy agent has a
different MCL than in the Federal regulations. When
specified, MCL VIOLATED must be entered under the
following rules:
o Must be specified for MCL violations, other
than BACTI or turbidity.
o The integer portion cannot exceed 7 positions
o The decimal portion cannot exceed 8 positions
o Must be numeric
o Must be greater than or equal to zero
The rules for entering decimal numbers into the
FRDS-II System, are discussed in Chapter VII,
"GENERAL CODING INSTRUCTIONS."
Effective Date: 10/01/89
Release Number: "L 0
Page' 96
-------
SECTION D1 - VIOLATION DATA
DATA ELEMENT REGISTRATION TABLE
DATA
FORM REFERENCE NAME
C1101
C1103
C110S
C1107
C1109
C1111
C1143
cms
C1127
C1129
C1131
C1125
VIOLATION ID
CONTAMINANT
VIOLATION TYPE
COMPLIANCE PERIOD BEGIN
COMPLIANCE PERIOD END
COMPLIANCE PERIOD DURATION
SE ID
AWARENESS DATE
NUM SAMPLES REQUIRED
NUM SAMPLES TAKEN
MAJOR VIOLATION
ANALYSIS METHOD
ANALYSIS RESULT
MCL VIOLATED
ZERO REG. GRANT.
A/N/D JUST SIN FILL CODE ELIG . CBR
sssss ms
=as= =a = ss
A
A
A
N
N
N
N
N
N
N
A
A
D
D
L
L Y
L
L
L
L '
L
L
L Y
L -Y
N/A Y
L Y
A Y
A Y
Y 3
4
2
Y 2
Y 4
-------
Public Water System
Data Capture Form D
. PWS.D' .
SUM . tO Hunt*,
I I I I I I ) |
(C101)
ACTION cone
u
BATCH DATE
no MY ni
I I I I I I I
|"pi"| VIOLATION DATA
!»»»**.« VIOLATION COMPLIANCE P
ff IZlBER CONTAM.NANT TYPE ^
1 1 1 1 1 1 I I ! I i I I I I | | |
ERUOiEON
Y YR
I I I
(C1101) (C1103) (C1IOS) IC1107)
COMPLIANCE PERIOD END
MO DAY YR
I 111 I I I
(CI109)
OR
COMPLIANCE PERIOD
DURATION
II I I
(01111)
MONITORMO AND REPORTING VIOLATIONS
_ AWARENESS DATE , NUW
aeD »c
MO DAY YR **
I I 1 I i 1 i I i 1 L
SAMPLES
QUIRED
I
(C1143) (C111S) (CIIZ7)
NUMSAMf
TAKE*
I |
(C11Z9J
ILES .
_l OR
MAJOR
VIOLATION
UY.YES
N.NO
(C1131)
OR
MAXIMUM CONTAUNANT LEVEL VIOLATIONS
ANALYSIS
METHOD ANALYSIS RESULT
1 II MUM IN
(C1121) (C1123)
I I I I I I I
puss)
MCI, VIOLATED
M.I II
1 1 || 1
|
^
1
VIOLATION ID
FY iO NUMBER
I I I I I I
(C1101)
SEID
1111
(CI143)
CONTAMINANT
VIOLATION DATA
VIOLATION COMPLIANCE PERIOD BEGN
TVP6 MO DAY YR
I ! I I I I I I I I II I I I
(C1103) (C110S) (C1107)
COMPLIANCE PERIOD END
MO DAY YR
II I I I I I
(C11091
AWARENESS DATE
MO DAY YH
I i i i I I I
(01115)
MONITORING AND REPORTING VIOLATIONS
NUM SAMPLES
REQUIRED
III
(C1127)
NUM SAMPLES MAJOR
TAKEN VIOLATION
I | OR |J
tcn^ "»«
Y.-YES
N-NO
OR
MAXIMUM CONTAMINANT LEVEL VIOLATIONS
ANALYSIS
METHOD
i i LL
;
ANALYSIS RESULT
I LI I I I I I I I I II
MCL VIOLATED
.1 1 Mil
ccii2T) tcnsaj (01125)
Figure 18
Effective Date* 10/01/89 Release Number: 1.0 Pages 9S
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM E
SECTION E1 - ENFORCEMENT DATA
Effective Date: 10/01/89
Release Number: 1 . 0
Page: 99
-------
SECTION El,- ENFORCEMENT DATA
(See Figure 19)
This section is used to enter data that characterizes an
enforcement action taken against a public water system
by a State or Federal agency. The FRDS-II Data Base has
one enforcement record for each enforcement action that
has been reported to EPA. The following data may be
entered via this section2
ENFORCEMENT ID (FY £ ID NUMBER)
(C1201)
Enter an ENFORCEMENT ID that will uniquely identify
a specific enforcement action taken by a State or
Federal agency against a public water system.
Positions 1-2 contain the Federal fiscal year (FY)
in which the enforcement action was issued. Fiscal
year must always be specified, must always be greater
than 71, must always be equal to or less than the
current Federal fiscal year and must always be
numeric.
Positions 3-7 contain an ID NUMBER, which must be
unique for each enforcement action for the PUS for
the Federal fiscal year.
Note: see Chapter VI, "Record Identification and
Maximum Occurances" for user assignment and
automatic generation of this ID.
FOLLOW-UP ACTION
(C120S)
Enter the code value that represents the enforcement
action that was taken by a State or Federal agency
against a public water system. When specified,
position 1 must be one of the following codes:
«F» s formal action
"I" = informal action
"E" * administrative order issued by EPA (For
EPA use only.)
"0" = other than above
When specified, positions 2-3 must be a valid
enforcement follow-up sub-category code that is
applicable to the major follow-up action types.
These may be found in SECTION VI, Table ID09, in the
Federal Reporting Data System Data Element
Dictionary. Position 3 is reserved for future use.
ENFORCEMENT DATE (MO, DAY, £ YR)
(C1203)
Enter the calendar date on which an enforcement
action was taken by a State or Federal agency
against a public water system.
Effective Dates 10/01/89
Release Number: 1.0
Pages 1Qd
-------
SECTION El - ENFORCEMENT DATA
When inserting an enforcement record into the FRDS-II Data Base, it
should be related to a violation record or records. Three methods
have been provided to the user to relate enforcement actions to
violation records. The three methods are (1) ASSOCIATED VIOLATION
RANGE (X5000); (2) ASSOCIATED VIOLATION IDS (YSOOO); and (3)
ASSOCIATED VIOLATION CONTAMINANT GROUPS (Z5000). When relating an
enforcement record to a violation record,.the FRDS-II System builds
a "Link Record" to the violation record specified by the user,
through the use of one or more of the aforementioned methods. The
rules for entering violation data for any of these methods may be
found in the instructions for DATA CAPTURE FORM D (VIOLATION DATA).
When updating enforcement actions, the "M" (Modify) action code
uould normally be used to modify the following data elements:
C1203 - ENF-ACTION-DATE
C120S - ENF-FOLLOW-UP-ACTION
However, the "Modify" action code can also be used to establish
additional Violation "Link Records." Once an enforcement record
has been posted to the FRDS-II Data Base, the user may use the
"Modify" action code to establish additional "Link Records"
to specified violation records. So, the user may link enforcements
to violation records two ways: (1) When adding an enforcement
record to the FRDS-II Data Base by the use of an "Insert" trans-
action (Action code of "I"); or (2) By modifying an existing
enforcement record in the FRDS-II Data Base by the use of a
"Modify" transaction (Action code of "M").
If an enforcement action is applied erroneously to certain
violation records, it can only be corrected by first deleting the
enforcement action (with an action code of "D") and re-inserting
(with an action code of "I") the enforcement action with the proper
violations identified by the X5000, YSOOO or ZSOOO update methods.
It is important for the user to realize that when an enforcement
action is deleted from the FRDS-II Data Base, ALL links to
violations for that enforcement are also deleted.
ASSOCIATED VIOLATION RANGE (BEGIN (MO, DAY £ YR)
(X5000) and END (MO, DAY £ YR))
Enter the beginning and ending dates that represent the
violations that occurred within a specific time period, to
which the enforcement actions are to be applied. If either
the beginning date or the ending date for the violation
record compliance period falls within the range of dates
specified, the enforcement action will be applied to that
violation. If the end date in the ASSOCIATED VIOLATION
RANGE is left blank, then the ENFORCEMENT DATE (C1203) will
be used as the end date in the ASSOCIATED VIOLATION RANGE.
In all cases, the beginning and ending dates in the
ASSOCIATED VIOLATION RANGE must be equal to or less than
the ENFORCEMENT DATE (C1203).
Effective Dates 10/01/89 Release Number' 1 .0 Pages 10.1
-------
SECTION E1 - ENFORCEMENT DATA
ASSOCIATED VIOLATION RANGE ( CONT . )
CX5000) . .
For example, if a violation record had a compliance period
begin date of 06/15/87 and a compliance period end date of
07/15/87, the following ASSOCIATED VIOLATION RANGES would
cause an enforcement action to be applied:
o BEGIN 05/15/87 - END 06/15/87 (Compliance period begin
date in violation falls within the specified range)
o BEGIN 07/15/87 - END 08/15/87 (Compliance period end
date in violation falls within the specified range)
Only a single ASSOCIATED VIOLATION RANGE will be accepted
in the same update for a given enforcement action.
If the beginning or ending date in the violation record
does not match the range of dates specified, a link will
not be established to the violation. However, the
enforcement action will be accepted.
ASSOCIATED VIOLATION IDS (FY £ ID NUMBER)
(Y5000)
Enter the specific violation ID(s) to which the enforcement
action is related. When the enforcement action is posted
to the data base, a link will be established between the
enforcement record and each violation record specified by
the violation ID. When a specified violation ID is not
found in the data base, the link will not be established;
however, the enforcement action will be accepted.
If the user wishes to enter more ASSOCIATED VIOLATION IDS
than are provided on the form for the same enforcement
action, an additional form or forms may be used. Except
for the ASSOCIATED VIOLATION ID data, all other information
on the form (i.e., PWS ID, ACTION CODE, BATCH DATE,
ENFORCEMENT ID, FOLLOW-UP ACTION, and ENFORCEMENT DATE)
would be the same.
Effective Date: 10/01/89 Release Numbers 1 .0 Page: f.1Q2
-------
SECTION E1 - ENFORCEMEHT DATA
ASSOCIATED VIOLATION CONTAMINANT. GROUPS (TYPE, CONTAMINANT,
(Z5000) ...''' COMPLIANCE PERIOD BEGIN
DATE CMO, DAY E YR))
Enter the ASSOCIATED CONTAMINANT GROUP data, which consists
of Violation Type, Contaminant Code and Compliance Period
Begin Date, of violations that relate to this enforcement.
If the violation record data exactly matches the specified
ASSOCIATED CONTAMINANT GROUP, a link will be established
between the enforcement record and the violation record.
If an exact match does not take place, no link will be
established, however, the enforcement action will be
accepted.
If the user wishes to enter more ASSOCIATED VIOLATION
CONTAMINANT GROUPS than are provided on the form for the
same enforcement action, an additional form or forms may be
used. Except for the ASSOCIATED VIOLATION CONTAMINANT
GROUPS, all other information on the form (i.e., PMS ID,
ACTION CODE, BATCH DATE, ENFORCEMENT ID, FOLLOW-UP ACTION,
and ENFORCEMENT DATE) would be the same.
NOTE! see Chapter II - "Data Transfer File" for further
information on XSOOO, Y5000, and Z5000 enforcement
processing.
Effective Date: 10/01/89
Release Number* 1.0
Page-' 103
-------
SECTION E1 - ENFORCEMENT DATA
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
FORM REFERENCE NAME
= = = = = = = = = = = = = = - = = = = =
ZERO REG.. GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR
C1201 ENFORCEMENT ID
C1203 ENFORCEMENT DATE
C120S FOLLOW-UP ACTION
A' L
N L
A L
. 3
Y 2
2
N
N
N
LEGEND-
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE -
A
L
Y
Y
1
2
3
4
GRANT ELIG.- Y
C
CBR
Y
N
======================================
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
SKIP IF NONE OR NOT APPLICABLE
ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
OPERATIONALLY REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
CAN BE REMOVED (i.e., * IK LEFT-MOST POSITION)
CANNOT BE REMOVED
Effective Dates 10/01/89
Release Number: 1.0
Page:
-------
Public Water System
Data Capture Form E
ACTION cooe
(C101)
u ..
kmul u -Madly
BATCH DATE
no Mr in
I I I I I I I
P1
Cl
ENFORCEMENT D
FY ID NUMB
I I I I I
(C1201)
VIOLATION O1
FY IDNUMBE
1 ! 1 I f 1
(Y5000)
TYPE CONTAMMAN1
III 1
(23000)
ENFORCEMENT ID
FY . IDNUMI
Mill
(C1201)
VIOLATION ID 1
FY IDNUMBE
1)1)11
(YSOOO)
TYPE CONTAMINAN
III 1
(Z5000)
FfJFnPnFMFfJT DA TA
ASS
FCUOWUP ENFORCEMENTOATE BEGIN
ER ACTION MO DAY YR MO DAY
LJJ 1 1 1 1 1 1 1 1 1 + MM
(CUDS) (C19B3)
(XSOOO)
ASSOCIATED VIOLATION IDS
VIOLATION 10 2 VIOLATION ID J
R FY 0 NUMBER FY ID NUMBER
1 1 1 1 1 ! 1 1 1 1 1 1 11
OR
ASSOCIATED VIOLATION CONTAMINANT GROUPS
COMPLIANCE PERIOD COMPLIANCE PERIOD
BEGIN DATE BEGIN DATE
T. MO DAY YR , TYPE CONTAMINANT , MO DAY YR , .TYPE
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
ASS
FOLLOW-UP ENFORCEMENTOATE BEGIN
ER ACTON MO DAY YR Mo DAY
L_U 1 I 1 1 1 1 1 1 1 1 + | | | |
tciaos) (Ci2m
(X5000)
ASSOCIATED VOLATCN IDS
VDLATION ID 2 VIOLATION ID 3
R FY D NUMBER FY ID NUMBER
1 1 1 1 1 1 I 1 I 1 1 1 f 1
OR
ASSOCIATED VIOLATION CONTAMINANT GROUPS
COMPLIANCE PERIOD COMPLIANCE PERIOD
BEGIN DATE BEGIN DATE
T, MO DAY YH , TYPE CONTAMINANT . MO DAY YR , .TYPE
1 I 1 1 1 1 1 1 1 1 1 1 II
iCCIATED VIOLATION RANGE
END
YR M0 DAY YR
MM Mill
OR
VIOLATION O 4
FY ID NUMBER
j 1 1 1 1 ! 1
COMPLIANCE PERIOD
BEGIN DATE
CONTAMINANT. MO DAY YR
1 1 1 1 1
OCIATED VOLATION RANGE
END
YR M0 DAY YR
MM Mill
OR
VIOLATION D4
FY ID NUMBER
J 1 1 1 1 1 1 1
COMPLIANCE PERIOD
BEGM DATE
CONTAMINANT| MO DAY YR
1 I 1 1 1
Figure 19
Effective Dates 10/01/89 . Release Numbers
Pages
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORK F
SECTION F1 - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA
Effective Dates 10/01/89 Release Numbers j, 0 Page' . ,10.6.
-------
SECTION F1 - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA
(See Figure 20)
This section is used to enter data that characterizes a
variance or exemption that is pending for, or has been
granted to, a public water system. The FRDS-II Data Base
has one variance or exemption record for each variance
or exemption that has been reported to EPA. The
following data may be entered via this sections
VS ID (FY £ ID NUMBER)
(C3001)
Enter a VE ID that will uniquely identify a specific
variance or exemption that is pending for, or that
has been granted to, a public water system by a
primacy agent under the following rules.
Positions 1 - 2 contain the fiscal year (FY) in
which the variance or exemption was reported
to EPA. Uhen adding, deleting or modifying a
variance or exemption record, fiscal year must
always be specified, must always be equal to or
less than the current fiscal year, must be numeric,
and cannot be less than 78.
Notes see Chapter VI, "Record Identification" for
user assignment and automatic generation of
this ID.
CONTAMINANT
(C3003)
RECORD TYPE
(C3005)
EFFECTIVE DATE
(C3007)
Enter the code value that represents a contaminant
for which a variance or exemption is pending, or
that has been granted to, a public uater system by a
primacy agent. This data element must be a valid
contaminant code or a valid contaminant group code as
found in SECTION VI, Table ID06, in the Federal
Reporting Data System Data Element Dictionary.
Enter the code value that represents whether this is
a variance, exemption, turbidity waiver, filtration
exclusion, or other record. Valid RECORD TYPE codes
may be found in SECTION VI, Table 3005, in the
Federal Reporting Data System (FRDS-II) Data Element
Dictionary.
(MO, DAY, £ YR)
Enter the calendar date on which the variance or
exemption that has been granted to a public water
system by a primacy agent became, or will become,
effective. When specified, EFFECTIVE DATE must
be less than C3009, EXPIRATION DATE.
Effective Date: 10x01/89
Release Number: 1.0
Page: 107
-------
SECTION F1 - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA
EXPIRATION DATE (MO, DAY, £ YR) :
(C3009) . '
Enter the calendar date on which a variance or
exemption that was granted to a public water system
expired, or uill expire. When specified, EXPIRATION
DATE must be after the EFFECTIVE DATE.
STATUS CODE
CC3011)
Enter the code value that describes the current
status of a variance or exemption that is pending
for, or has been granted to, a public water system
by a primacy agent. When specified, STATUS CODE
must be a valid variance or exemption status
code as described in SECTION VI, Table 3011 in
the Federal Reporting Data System Data Element
Dictionary.
MODIFIED MCL
(C3013)
Enter the numeric value that represents the modified
maximum contaminant level that has been approved as
a condition to a variance or an exemption granted to
a public water system by a primacy agent.
When specified, MODIFIED MCL must be entered under
.the following rules:
o The integer portion cannot exceed 7 positions
o The decimal portion cannot exceed 8 positions
o Must be numeric
o Must be greater than or equal to zero
o A decimal point may or may not appear
o A decimal point must be specified if a
fractional amount is intended.
TREATMENT PROCESS
CC3015)
Enter the code value that represents the treatment
process for which a variance or exemption is being
granted to a public water system by a primacy agent.
When specified, this TREATMENT PROCESS must be a
valid treatment process code as described in SECTION
VI, Table ID04, in the Federal Reporting Data System
Data Element Dictionary.
Effective Date* 10/01/89
Release Number:
Page; ro_8
-------
SECTION F1 - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA
ALTERNATE PROCESS
CC3017) . '
Enter the code value that represents the alternate
process for uhich a variance or exemption is being
granted to a public water system by a primacy agent.
When specified, this data element must be a valid
treatment process code as described in SECTION VI.
Table ID04, in the Federal Reporting Data System Data
Element Dictionary.
REASON
(C3019)
Enter the code value that represents the reason for
uhich a variance or exemption has been granted to a
public water system by a primacy agent. When
specified, this data element must be a valid
reason code as described in SECTION VI, Table 3019,
in the Federal Reporting Data System Data Element
Dictionary.
Effective Dates 10/01/89
Release Number: 1.0
Pages 109
-------
SECTION F1 - VARIAKCES. EXEMPTIONS C OTHER RELATED DATA
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
FORM REFERENCE NAME
ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR'
C3001 VE ID
C3003 CONTAMINANT
C300S RECORD TYPE
C3007 EFFECTIVE DATE
C3009 EXPIRATION DATE
C3011 STATUS CODE
C3013 MODIFIED MCL
C3015 TREATMENT PROCESS
C3017 ALTERNATE PROCESS
C3019 REASON
A
A
A
N
N
A
D
N
N
N
L
L
L .
L
L
N/A
A
L
L
L
Y 3
2
2
Y ' 4
-Y <*
2
Y Y H
Y
Y <*
Y
N
N
N
Y
Y
N
Y
Y
Y
Y
LEGEND:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE -
GRANT ELIG.- Y
C
CBR
A * ALPHANUMERIC, N * NUMERIC, D = DECIMAL
L = LEFT JUSTIFY. R = RIGHT JUSTIFY, A = ALIGN
Y = SKIP IF NONE OR NOT APPLICABLE
Y = ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
1 = OPERATIONALLY REQUIRED
2 = PROGRAMMATICALLY REgUIRED
3 = OPERATIONALLY REQUIRED, CONDITIONALLY
H PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PUS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N = CANNOT BE REMOVED
Effective Date: 10/01/89
Release Number: 1.0
Page: 110
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM F
SECTION F2 - VE SCHEDULE
Effective Dates 10/01/89
Release Number 1 .10
Page-' 1 1 1
-------
SECTION F2 - VE SCHEDULE
(See Figure 20)
This section is used to enter data that characterizes a
schedule of events and/or actions that are related to a
variance or exemption that is pending for, or has been
granted to, a public water system. The FRDS-II Data Base
has one schedule record for each event or action which is
related to a variance or exemption that has been reported
to EPA. The following data may be entered via this form:
VE ID (FY 6 ID NUMBER)
(C3001)
Enter the VE ID for the variance or exemption record
to which the VE SCHEDULE will be applied. This data
element is required. A VE SCHEDULE record cannot
be added to the FRDS-II Data Base unless a variance
or exemption record to which it can be applied
already exists.
Notes see Chapter VI, "Record Identification" for
user assignment and automatic,generation of
this ID.
SCHEDULE ID
CC3101)
ACTION
(C3103)
Enter a numeric value that will uniquely identify
a specific event or action that is related to a
variance or exemption that is pending for* or has
been granted to, a public water system.
Notes See Chapter VI, "Record Identification" for
user assignment and automatic generation of
this ID.
Enter the code value that represents an event or
action that is to be taken by the State (or was
taken by the State) relating to a variance or an
exemption that is pending for, or has been granted
to, a public water system. This data element is
required when modifying the current value. When
specified, ACTION must be a valid variance or
exemption schedule action as described in SECTION
VI, Table 3103, in the Federal Reporting Data System
Data Element Dictionary.
Effective Dates 10/01/89
Release Number 1.0
Pages 112
-------
SECTION F2 - VE SCHEDULE
SCHEDULED DATE (MO, DAY, £ YR>
(C3105)
Enter the calendar date on which an event oz action
relating to a variance oz an exemption that is
pending for, oz has been gzanted to, a public uatez
system is scheduled (oz was scheduled) to occuz.
ACCOMPLISHED DATE (110, DAY, G YR)
(C3107)
Entez the calendaz date on which an event oz action
zelating to a vaziance oz an exemption that is
pending for, oz has been gzanted to, a public uatez
system MAS accomplished, if completed.
Effective Date: 10/01/89 Release Number: 1.0 Page: 113
-------
SECTIOH F2 - VE SCHEDULE
DATA ELEMENT REGISTRATION TABLE
DATA
ELEMENT
in.
FORM REFERENCE NAME
ZERO REG..GRANT
A/N/D JUST SIN FILL CODE ELIG. CBR
C3001 VE ID
C3101 SCHEDULE ID
C3103 ACTION
C3105 SCHEDULED DATE
C3107 ACCOMPLISHED DATE
A
N
A
N
N
-'L
L
L
L
, L
Y
Y
Y
Y 3
Y 3
Y '
Y
N
N
Y
Y
Y
LEGEND:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE -
GRANT ELIG.- Y *
C =
CBR
A = ALPHANUMERIC, N = NUMERIC, D = DECIMAL
L = LEFT JUSTIFY, R = RIGHT JUSTIFY, A = ALIGN
Y = SKIP IF NONE OR NOT APPLICABLE
Y = ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
1 = OPERATIONALLY REQUIRED
2 = PROGRAMMATICALLY REQUIRED
3 * OPERATIONALLY REQUIRED, CONDITIONALLY
H = PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PWS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
Y = CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
N = CANNOT BE REMOVED
Effective Date* 10/01/89
Release Number: 1.0
Pages 11H
-------
Public Water System
Data Capture Form F
PWS O
But* IDNuntar
I I I I I I I I I
(C101)
U
U .Had*,
BATCH DATE
i 7 i T i
["FT
IT
IC3001)
STATUS
CODE
U
IC3011J
p2"
1
FV
1 1
1 1
1 1
1 1
VARIANCES, EXEMPTIONS & OTHER RELATED DATA
VED ,^,.MM, , RECORD EFFECTIVE DATE EXPIRATION DATE
, ID NUMBER CONTAMNANT TYPE MO DAY YR MO . DAY YR
1 1 1 1 I 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
(C3003)
MOOFIEDMCL
1 1 1 M 1 1
(0013)
I
I VED
ID NUMBER
I I 1 I t I
1 1 1 1 1 1
1 I 1 t 1 1
1 1 1 1 1 1
(03001)
I.M 1 1
SCHEDULE '
ID
1 1 1
1 I 1
1 . 1
1 1 1
(C3101)
(C3QOS) (C3007) (C3909)
TREATMENT ALTERNATE
PROCESS PROCESS
Mill 1 i
(C3B1S)
VE SCHEDULE
1 1 1
(CW17)
1
ACTION SCHEDULED DATE
i i . MO . DAY
Il| fill
III I'!'
111 1 1 1 1
III I'''
(C310J) (C310S)
*R ' .
1 1 1
1 t 1
I 1 1
1 1 1
1
1
1
1
1
|
REASON
1 1 1
(C301B)
ACCOMPLISHED DATE
MO
|
|
|
|
(C3107)
|
|
|
|
DAY . YH .
|
|
|
|
1 1 1
1 1 1
1 1 1
1 1 1
^_ ^ VARIANCES, EXEMPTIONS & OTHER RELATED DATA
| F1 |
^~^ VEB RECORD . EFFECTIVE DATE EWIRAT1OHOATE
FY . DNUMBEH CONTAMWAKT TYPE . MO . DAY _ YH MO . DAY . YH
| 1 1 1 1 1 1 1 1 1 1 1 1 1 1
I I i h i i I M I i I i I
(C3001) (C3003) (C3005) (C3D07) (C3009)
STATUS
CODE MOOFIEOMCL
M I I I I I I M.I I M I I I
(C3011) (C3013)
TREATMENT ALTERNATE _.__
PROCESS PROCESS REASON
I | | | I I I I I I I I i
ICX1 5) (C3017) (C30I8)
r^l VE SCHEDULE
J VEO SCHEDULE
FV ID NUMBER ID ACTON
1 I 1 . 1 1 1 1 III ll|
1 1 1 1 1 1 1 1 III III
1 1 1 1 . . . 1 III III
1 . 1 i t . . 1 Ml Ml
(C3001) (C3101) (C310S)
SCHEDULED DATE ACCOMPLISHED DATE
MO . DAY YR MO , DAY YH
| t | 1 | I I | 1 | 1 | 1 1
M 1 i 1 i I M 1 ' I ' i
1 1 1 1 1 f 1 1 1 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1
(C3105) (C3107)
Effective Date:
Figure 20
10x01/89 Release Number:
Pages _ _i_j5
-------
FRDS-II DATA ENTRY INSTRUCTIONS
DATA CAPTURE FORM G
SECTION G1 - STATE'DISCRETIONARY DATA
Effective Dates 10/01/89 Release Number: 1.0 Pages 116
-------
SECTION G1 - STATE DISCRETIONARY DATA
(See Figure 21)
This section is used to enter data that characterizes a
specific set of values defined at the discretion of the
State. The FRDS-II Data Base has one discretionary
record for each single set of State specific data values
that has been reported to EPA for a public water system.
The following data may be entered via this section'
SDD ID
CCH001)
Enter a numeric value that will uniquely identify
a specific State discretionary data item applicable
to a public water system.
STATE DISCRETIONARY DATA NAME
(C4003)
Enter the alphanumeric value that describes the
data entered in the other data elements in the
STATE DISCRETIONARY RECORD, For example, "Sanitary
Engineer" or "Wholesale Population".
STATE DISCRETIONARY VALUE
(C4005)
The user may enter any alphanumeric value desired
in STATE DISCRETIONARY VALUE. For example, the
sanitary engineer, "John Jones".
STATE DISCRETIONARY QUANTITY
(C4007)
The user may enter any numeric value desired
in STATE DISCRETIONARY QUANTITY under the following
rules;
When specified...
o The integer portion cannot exceed 7 positions
o The decimal portion cannot exceed 8 positions
o Must be numeric
o A decimal point may or may not appear
o A decimal point must be specified if a
fractional amount is intended
For example, the wholesale population quantity
could be entered here.
DATE (MO, DAY, £ YR)
CC4009)
The user may enter any valid date desired. However,
the year portion of the date must -.be graeter than
77.
Effective Date: 10/01/89 Release Number: jt0 Page: 117
-------
SECTION G1 - STATE DISCRETIONARY DATA
DATA. ELEMENT REGISTRATION TABLE
DATA
ELEMENT ,
'M. FORM REFERENCE NAME
ssss sssseassssssassssess.sssss
. ZERO REG. GRANT
A/N/D JUST SIN FILL CODE ELIG . CBR
sssss sass ass ssss ssss'sssss ass
C«*001 SDD ID ,N L
» *"
CH003 STATE DISCRETIONARY DATA
NAME A L
STATE DISCRETIONARY VALUE A L
CH007 STATE DISCRETIONARY
QUANTITY D A
C«I009 DATE N L
Y
Y
Y
Y
N
Y
Y
Y
Y-
LEGEND:
A/N/D
JUST
SIN
ZERO FILL -
REG. CODE -
GRANT ELIG.-
CBR
A
L
Y
Y
1
2
3
Y *
C =
Y =
N *
ALPHANUMERIC, N = NUMERIC, D = DECIMAL
LEFT JUSTIFY,. R = RIGHT JUSTIFY, A « ALIGN
SKIP IF NONE OR NOT APPLICABLE
ENTER PRECEDING ZEROS OR ZERO FILL
REMAINING DECIMAL PLACES
OPERATIONALLY REQUIRED
PROGRAMMATICALLY REQUIRED
OPERATIONALLY REQUIRED, CONDITIONALLY
PROGRAMMATICALLY REQUIRED, CONDITIONALLY
(SEE CHAPTER IV, "DATA BASE REGISTRATION
REQUIREMENT", FOR FURTHER EXPLANATION)
DATA ELEMENT IS REQUIRED FOR A PUS TO BE
CONSIDERED "GRANT ELIGIBLE"
DATA ELEMENT IS CONDITIONALLY REQUIRED FOR A
PWS TO BE CONSIDERED "GRANT ELIGIBLE"
CAN BE REMOVED (i.e., * IN LEFT-MOST POSITION)
CANNOT BE REMOVED
Effective Date: 10/01/89
Release Number 1.0
Page: 118
-------
Public Water System
Data Capture Form G
PW5O
SUM
tONuntw
I I f I I I I I I I
ACTION CODE
f.fcMM U-UoOf
u
BATCH DATE
no a»r m
I I I I I I I
, 1
1 1 soon
1 1 1 II 1 1 1 1
(C400I) (C4003)
LL M '
1 1 1
(C4007)
STA TE DISCRETIONARY DA TA
STATE DISCRETIONARY DATA NAME
1 1 1 1 1 1 1 II 1 1 1 1 1 I "l 1 1 1
STATE DISCRETIONARY VALUE
1 M 1 1 1 1 1 1 1 M 1 1 M M 1
QUANTITY
J 1 1 1 1 M 1
1 M II 1
M 1 1 1 1
DATE
MO DAY YB
1 i 1 1 1 1 1
(C4009)
^__^
[Gil
i__l scoc
1 1 1 II 1 1 1 1
(0*001) (C400J)
I I I I I
|L*is)
1 1 1
(C4007)
573 TE DISCRETIONARY DATA
STATE DISCRETIONARY DATA NAME
1 1 1 1 1 1 1 1 1 M 1 MM 1 1 !
STATE DISCRETIONARV VALUE
M 1 M 1 M M II II II M 1
QUANTITY
J 1 1 1 1 1 1 1
1 1 1 ! 1 1
M M i 1
DATE
MO DAY YB
1 1 1 1 M 1
(C4009)
^._^
rGll
1 1 SCO ID '
1 M II 1 M 1
104001) (C4009)
Ul 1 1
1 1 1
(C4007)
STA TE DISCRETIONARY DA TA
STATE DISCRETIONARY DATA NAME
1 1 1 1 1 1 1 M M 1 1 II M M
STATE DISCRETIONARY VALUE
QUANTITY
.1 1 1 1 1 1 I 1
M 1 1 1 1
1 1 M 1 1
DATE
MO DAY YR
1 1 M 1 1 1
-------
PRDS-II DATA ENTRY INSTRUCTIONS
RECORD DELETION FORM
Effective Dates 1Q/01/8 ft Release Numbers 1 . o Page: _j2 j)
-------
RECORD DELETION FORM
(See Figure 22)
The RECORD DELETION FORM is available for the purpose of deleting
an ENTIRE Data Base Record (DBR) from the FRDS-II Data Base.
Note that the fora section names that are listed on the right
side of the form identify all DBR types that can be deleted.
Although public water system DBRs can be deactivated, they
cannot be deleted.
The DBR deletion process cannot violate the rules of
FRDS-II record registration (e.g., each public water system
DBR must have at least one source DBR).
Along with each section type is the necessary identification
data that must be specified in order to delete the appropriate
DBR. If an attempt is made to delete the last source DBR,
that transaction will be rejected uith an appropriate error
message.
In all cases, the PUS ID must be specified. Additionally,
at least one other record ID must be specified to uniquely
identify the DBR to be deleted. For example, to delete
a treatment DBR, the Source Entity ID (SE ID) must be specified
along with the Treatment ID. This is because each treatment
DBR is related to a particular Source Entity DBR.
The same methodology is used for VE Schedule record deletion
since the Schedule Record is related to a particular VE DBR
(Variances, Exemptions, and Other Related Data).
Effective Date: jQ/Q1/89 Release Numbers 1.0 Page: 121
-------
FRDS - II RECORD DELETION FORM
RECORD TO BE DELETED
Batch Date
*> wr .
I (III
QUALIFIER 1
QUALIFIER 2
ADDRESS
10
PWS ID
SIM DNumbir
I I I I I I I I I I I II
(C101) (C301)
PWS ID SE
_ SIM ONurtxr . O
[5T1I.I I i i i i i i I I I I I
PWS ID
sw ' ONMrtxr o
I I i I I I I I I I I I I I
PWS ID
(0481)
GA
D
|j|
i LJJ
(C101) (CJ01)
PWS ID sew
1 7 1 1 1 r 1 1 1 1 1 1 1
(Cioi) . (MOD
PWS ID VBIT
SIM OMuirtar K>
I I I I I I I I I I I I i
QUAURER 3
ACTION CODS
DATA BAgE
RECORD
TREATMENT
. 10
(CM1)
PWS ID VKWTIOND
SIM DNuntw FV DNUMBER
I I I I I I I I I I I I I I I I II
(0101) (CIIBt)
PWS ID
*"* OHuatut rw
I I . I I I I I I I I I I I I
ENFORCEMENT D
FV 10 NUMBER
PWS ID
SIM
(C1201)
Ff
VED
IOMMBER
I I I I I I ( ( I i I I I I I I I I
(Cioi) [taooi)
PWS ID
lONunter py IO NUMBER
SCHSO
ID
(03101)
I'l I I ! I I I I I I I I I I I II | | |
(C101) (C3001)
PWS ID oo
U I i i i"Ti i ILLJU
(C300) ADDRESS
0 I (C400) SOORCBEMTTTY
D(C460)TREAniBIT
(CSOO) GEOGRAPHIC AREAS
SERVED
(CSOO) SERVICE AREA
(C700)ON-SITE VISIT
(C1100) VIOLATION
(C1200) ENFORCEMENT
_ J (C3000) VARIANCES, EXEMPTIONS
D 4 OTHER REUTED DATA
(C3100)VE SCHEDULE
(C4001)
(C4000) STATE DISCRETIONARY
I P I DATA
Figure 22
Effective Dates 10/01/89 . Release Number:
1 .0 Pages 12J8
-------
FRDS-II DATA ENTR* INSTRUCTIONS
APPENDIX A
EXAMPLES OF DATA CAPTURE FORM / DATA TRANSFER FILE
Effective Dates 10/01/89 Release Numbers 1.0 Page: Al
-------
DATA CAPTURE FORM A
EXAMPLE 1
The objective of the Data Capture Form A on page A3 is to insert into
FRDS-II the facility name and address information for a Public Mater
System in Rhode Island with the ID number RI1S83811.
SECTION Al - SYSTEM ADDRESS
This information indicates that John Jones is the
person responsible for the PUS Lippitt Estates Assn,
located at Park View Terrace in Cumberland, RI 02864.
He can be reached, by phone, at (401)333-0829.
SECTION A2 - PUBLIC WATER SYSTEM CHARACTERISTICS
This information indicates that PUS RI1S83811 is an
Active, Community PUS (see page 56 for definition) which
commenced operation on or about June 1977 and serves 350
retail customers. .
One hundred percent of the water is obtained from
purchased, permanently available surface water sources.
It is privately owned and regulated by both Federal and
State regulations and has 86 Retail Service Connections.
SECTION A3 - OTHER ADDRESSES
This information indicates that the Lippitt Estates
Association is the System Owner/Responsible Party for
RI1583811, and can be reached at 60 Beach Rd in
Cumberland, RI 02864.
The user has assigned the Address ID (C301).
Effective Date: 10/01/89
Release Number: 1.0
Page* A21T.
-------
(C181)
Public Water System
Data Capture Form A
ACTION CODE
BATCH DATS
/I/I
(01MJ
SYSTEM ADDRESS
'i i4iStSiA/i i. i i i i i i i i I
ADDRESS UNE1
iTiOiNiCiSi i i i ii i i l l l l l l l l l l l l I
(CIS*
ADORES81ME2
IPiAiRiKi iViligiWi iTiSiftiftiAiCi*/! t i i i i i i i i i i i I
(C1W
CITY
lCiUiHiBtCi*iU/»iff/ibi i i
(CIST)
STATE
ZPCODE
t i
-M
i i i I
(C13t)
(C141)
TEUPHONE
AREA CODE NUMBER
ICMJ)
Pt/BL/C WA7EH SYSTEM CHARACTERISTICS
Pri% C^QOMUUMfV
(Cios>
ACIIVIIV
FLAO
(C107)
SYSTEM BEBJN DEACDVATDN DATE
YR MO VR MO
Il|1|0l6l | | | | | _
(C1111 (C113J (CtM)
BETA*. POPULATBN SERVED
I I I I I
PEHCENT
OROUNO
PERCENTPURCHASED PERCENT PURCHASED
SURFACE <»««w /"I***. QRPIJM> ___,
III I + I I I I + l/|0 1^1 + I I I I = 100%
PWl (C123) (CMS) (C«n
NCN COMMUNITY SEASON
OWNER REQUUTWO BEQM END
TYPE ENTITY RETAL SERVICE CONNECTIONS MO DAY MO DAY
Iflfcl I I I I I I I I I I I I I I I I
CC1«S> (CM71 (CtS» «='!)
OTHEf? ADDRESS(ES)
pg
l?i
ADDRESSEE NAME
i i i
IC301} (C30S) (C3DS1
AOORESSLME1
I I I I I I I I I I I I I I I I I I I I I |_L I I I I I I I I
(C307)
AOORESSUNE2
(cam
(0311)
i. i i i Kin
(C3t3)
i T
(C315)
Effective Date: TO/OJ/89
Release Number' 1.0
Page :
-------
Sample Data Transfer File Records - FORM A
1-2 3-11
1RI1583811 I
I I .
A11RI1583811 i
A1IRX1583811 I
A1 IRI1583811 I
A1 IRI1583811I
A1IRI1583811I
M IRI1583811 I
A2IRI15S3811 I
i I
A2IRI1583811 1
A2IRI1583811 I
A2IRI158381 1 I
t -._______ i .
A2IRI1583811 I
I _ I .
A2IRI1583811I
I - i .
12-18 19-25 26 27-31 32-71
I IHC131 ILIPPITT ESTATES ASSN
I _ | | _
1 H1C133 I JOHN JONES
~ I I I - - - - :
1 IHC135 (PARK VIEW TERRACE
I IIIC137 [CUMBERLAND
1 UIC139 IRI
1 IIIC141 (02864
I IIIC143 14013330829
i || | » «.«»-«....»....«.«. v«.«.«**i««»«.«
! IIIC105 1C
_______ i ___ i i i
1 IIIC107 IA
I IIIC111 I7706
I la *
'
1 IIIC117 1350
t II '
I II1C125 1100
__ i _______ i i i __ ___ _________
1 IHC163 12
1 i L _ 1 J
1
75-801
10415871
10415871
i
10415871
10415871
1
10415871
A
10415871
- 1
10415871
1
10415871
10415871
1
10415871
10415871
_ t ____ ... t
10415871
i i
10415871
- I - 1
Effective Date: 10/01/89 Release Number: 1.0 Page: A4
-------
A2IRI1583811I
i_________ j.
IIIC165 IB
I-I 1
0115871
2IRI1583811I
IIIC147 |86
10415871
A3IRI158381111
IIIC303 |0
I-I I
10415871
A3IRI1583811 I 1 I
__, | |
UIC305 ILIPPITT ESTATES ASSOCIATION 10415871
| _ | | | 1
A3IRI1583811! 1
I 1-
II1C309 160 BEACH ROAD
|_| j
10415871
I 1
A3IRI1583811 I 1 I
II1C311 I CUMBERLAND
,j-| 1
10415871
| 1
A3IRI1583811I 1 I
__! , ,
IIIC313 IRI
I-I I
10415871
1 1
3lRI1583811
1IIC315 I02864
I-I I
10415871
Effective Dates 10/01/89 Release Number: 1.0 Pages AS
-------
DATA CAPTURE FORM A
' . EXAMPLE 2
ihe objective of the Data Capture Form A on page A7 is to Modify Public
Water System Characteristics information already existing in FRDS-II.
Also note that different Batch Dates have been used to time sequence
the transactions on the Data Transfer File; FRDS-II will automatically
sort and process these transactions in ascending sequence thus allowing
multiple Batch Dates to be submitted at the same time.
SECTION A2 - PUBLIC MATER SYSTEM CHARACTERISTICS -
.This modification indicates that RI1583811 became inactive
on August 8. (Note: On the Sample Data Transfer File
Records - FORM A, column 26 nou has an M for modifying
Data Elements C107 and C113.)
RECORD DELETION FORM
t
SECTION A3 - OTHER ADDRESS(ES) . :
The example on Page A8 shouts how to delete a C300 (Other
Address) Data Base Record (DBR) from FRDS-II. Note that
all values previously reported for this address record
will be removed with this single command.
Effective Date: 10/01/89 Release Number: 1.0 Page' - A6
-------
Public Water System
Data Capture Form A
PW90
SUM
BATCH DATE
(C101)
IA1I I I I I I I I I I I
(CW1I
1 1 1 1 1 1 1 1 1 1
(Cl**
I 1 1 1 1 1 1 1 1 1
(C13S)
OTY
1 1 1 1 1 1 1 1 1 1
(C1S7»
TELEPHONE
AREA CODE NUMBER
1 I 1 1 1 1 1 1 1 1
(M43)
SYSTEM ADDRESS
SYSTEM' NAME
1 1 1 1 1 1 1 1 1 1
ADDRESS LNEI
1 1 1 1 1 1 1 1 1 1
ADDRESS UNE2
1 1 1 1 1 1 1 1 1 1
STATE
1 1 1 1 1 1 III
(C1M!
J
1 1 1 1 1 I 1 1 1 1 1
1 1 1 1 1 1 1 1 1 1 1
1 1 1 f | 1 1 1 1 1 1
OPCODE +*
1 1 1 I 1 1 1 1 1 1
(Ct4l»
PUBLIC WATER SYSTEM CHARACTERISTICS
Acnvnv
SYSTEM BEQM DEACTTVATONOATE
RETAL POPULATION SERVED
PERCENT
SURFACE
SOURCE WATER UTUZCD i I I I + I
r.-jss, I " M i lS*iWfri I i i i i i i i l
IU> (C113) (CUT)
PERCENT PURCHASED PERCENT PURCHASED
SURFACE GROUND
I +1 i i I + I i i I = 100%
PERCENT
(MOUND
1C1Z3)
(C12S)
OWNER REGULATING
TYPE ENTITY
RETAl SERVICE CONNECT
(C1S5) (CM7»
(CfSO)
OTHER ADDRESSfES)
LUU Li
(C301) (G30Q)
i i i i i i \ i i i i i i i i i ' i i i i i i i i i i I
ADDRESS UNE1
I I I I I I I I I I I I
(C307)
I ! i 1 I
I I I I I I I I I I I I I I I I I
AOORESSLME2
I I I I I I I I I I
I I I I I I I I
I I I I I
(C30B)
(C311)
CITY STATE
I I I 1 I I I I I I I I I
(catai
ZPCOOE +«
I I I I | I I 1 I I
(C315)
Effective Dates 10/01/89
Release Number: 1.0 Page: A7
-------
FRDS - II RECORD DELETION FORM
RECORD TO BE DELETED
Batch Data
no o»r m
I I I I I I
QUALIFIER 1
PWS ID
QUALIFIERS
ADDRESS
10
\LU
PWS ID *
SM* DNunter 10
I I » I I I I I I I I II I
(C101) (Cttl)
se
PWS ID
Sum DNunfcw _,
I I I I I I 1 I I 111 I 1
PWS ID «
SUM DNunfcv , ,
I I I I I I I I I I I I I
. . (CS01)
PWS ID
saw
I I I I I
I I I
I
icaot)
PWS ID
ID
VBIT
D
QUALIFIER 3
ACTION CODE
DATA BASE
RECORD
TREATMENT
. "0 .
ic«tn
ENFOWBIEHrD
FV IONUMBER
I I I I I I I I I I
VE SCHEDULE
(C4001I
(C4000) STATE DISCRETIONARY
I DATA
Effective Dates 10/01/89
Release Number« 1 -0 Page.s h&
-------
Sample Data Transfer File Records - FORM A
1-2 3-11 12-18 19-25 26 27-31
-I 1-
A2IRI1583811 I
32-71
75-80
081388
IMIC107 II
A2IRI1583811I
I 1
|nlC113 18808
I-I [
10813881
A3 IR11583811 I 1
DIC300
1081688
Effective Date: 10/01/89 Release Number' 1_, 0 Pages A9
-------
DATA CAPTURE FORM B
EXAMPLE 1
The objective of the Data Capture Form B on page A11 is to Insert data
that identifies sources of water that are utilized by the Public Hater
System and to specify the treatments applied. The user has requested
FRDS-II to generate both the SE IDs, and the TREATMENT IDs for this
Public Water System's sources and treatments.
SECTION B1 - SOURCE/ENTITY DATA
This section requires us to enter Source/Entity data for a
.Public Mater System, in this case RI1583811. Me have
requested FRDS-II to generate the SE ID for the Cumberland
River which is a Surface water source (S), with an
availability of (P) designating that it is a Permanently
available source. (Note: The Data Entry Instructions
refer you to the appropriate tables in Section VI of the
Data Element Dictionary). This section permits us.to
enter Latitude and Longitude of 415700, 0712500
respectively and a Hydrologic Unit Code of 01090003001 and
the fact that it is located 10.3 miles On Reach.
SECTION B2 - TREATMENT DATA
The Treatment Objectives of D, I, 0 and P represents
Disinfection, Inorganics Removal, Organics Removal and
Particulate Removal respectively. The associated treat-
ment processes identify: chlorine Dioxide (220);
Activated Alumina (100); Flocculation (360); Sedimentation
(660); and Coagulation (240).
EXAMPLE 2
SECTION 81 £ B2- SOURCE/ENTITY S TREATMENT DATA
This entry will Insert Source/Entity and Treatment data
for a second source of water for PUS RI1583S11, named Well
1. It requests FRDS-II to generate both the SE and
TREATMENT IDs. Treatment Objective B indicates
Disinfection By-products Control. Treatment Process 121
represents Activated Carbon, Granular while a second
Treatment Process (220) identifies the use of Chlorine
Dioxide (see Treatment Processes by Treatment Objective
tables in Section VI of the Data Element Dictionary.)
Effective Dates 10/01/89
Release Number* 1.0
Page! A10
-------
Public Water System
Data Capture Form B
4CTUN
BATCH CUTE
Imlmta M .
SOURCE /ENTITY DATA
i£iOi /i
IC401I (CM*
RECORD ^
TYPE coce AVAlASLTTr
SELLER PWaO
STATS O NUMBER
(C41S)
Ml M I I I I I 0T/ 1^71001
TOWMMPMAWE
. TOWNSWPH* . RAMOS BW SEC . 1«BEC
I I I M I I Ml I I I
|C41« (C4»| (C4M) («a5r
(C40S)
DEO . MM SEC
(C409I
PJVEH REACH
REACH UtCS
(C427)
(CM*) (C41I)
SED
TREATMENT DATA
rr
/I
TBEATVSNT
OBJECTIVE
ISiOI/l
6PISI
Iftoifl
I&IOI5T
(C4D1)
101
10]
10
TREATUEKT
PROCESS
I2I2IOJ
l/jojol
134101
(CMS)
SOURCE /ENTITY DATA
NAME
I/I 1 1 1 1 1 1 1 1 1 1 1 1 1
|C«1)
STATS
(C40S)
CODE AVAUIBUTY
lC| l£l
(CMOS) («W| (C409)
O NUMBER
I I M M 1 I I I
LATITUDE
060 MW SEC
LOMOmjOB
DM MN SEC
(C411J
(C41S)
RIVER REACH
. TOWMMPN* . RANK EM SEC . 1'«SEC.
M I M I M M I I I
(C41f) (C421) IC4J31 (CMS)
REACH MUS
,
1 1 1 |4|-|/I 1
(CUT)
(040)
TREATMENT DATA
16-10121
TREATUBIT
TREATMENT
OBJECTIVE
TH6ATMKKT
PROCESS
MM
MM
MM
MM U
LLU U
I I M U
Mil
mj
(Cttll
(C4M)
(CMS)
Effective Dates 10/0
Release Number: _]__.p Pages A1 1
-------
Sample Data Transfer File Records - FORM B
1-2
_ I
i
-I
B1I
B1I
B1|
_ i
B1|
B1|
"11
i
i
B1I
B1i
i
B2|
I
B2I
B2I
B2I
l
3-11
RI1583811
RI158381 1
RI1583811
RI1583811
RI1583811
RI1583811
RI1583811
RI1S83811
RI1583811
*
RI1583811
RI1583811
RI1583811
RI1583811
I
I
1
1
1
1
I
I
1
1
t
1
1
1
I
1
60
GO
GO
GO
GO
GO
GO
GO
GO
GO
GO
GO
GO
2-18
1
1
1
1
1
1
1
1
1
1
1
1
1
19-25
I.
I
I
I
I
I
[
1
1
| ___
1
IG01
IG01
IG02
IG02
. i
26
II
II
II
II
II
II
II
II
II
11
_ i
i
11
11
II
_ i _
27-31
IC403
1C405
1C407
IC409
(cms
IC417
IC427
IC429
IC431
IC483
_
IC4S5
IC483
IC485
i
32-71
(CUMBERLAND RIVER
IS
IS
IP
1115700
1712500
101090003001
IY
110.3
ID
. _
1220
11
<
1 100
I
1
1
1
1
1
1
I
1
1
1
1
1
1
1
75-80
041587
041587
041587
041587
041587
041587
041587
041587
041587
041587
041587
041587
041587
|
I
I
4
.(
I
I
I
i
1
1
t
1
J
1
1
Effective Date: 10/01/89 Release Number: 1.0 Page' A12
-------
B2IRI1583811
2IRI1583811
B2IRI1583811
B2IRI1583811
B2IRI1583811
B21RI1583811
B1 IRI1583811
B1 IRI1583811
B1 IRI1583811
B1 IRI1583811
B1 I RI 15838 11
B1 [RI1583811
B1 IRI1583811
B1 IRI1583811
I __
1
IG01
IG01
IG01
IG01
IG01
IG01
IG02
IG02
| _
IG02
IG02
IG02
IG02
IG02
IG02
IG03
IG03
IG04
IG04
IG05
IG05
I
I
I
I
I
I
I
I
HIC483
_ |
IIIC485
IIIC483
IIIC485
IIIC483
IIIC485
IIIC403
IIIC405
IIIC407
UIC409
IIIC415
IIIC417
IHC427
IIIC429
1 I
10
1360
i «»
10
1660
IP
1 240
IWELL 1
IS
IG
IP
1415740
10712519
101090003003
IN
10415871
i
10415871
10415871
.________(___ 1
10415871
10415871
10415871
10415871
10415871
1«. ... 1
1
10415871
10415871
10415871
10415871
10415871
I i
10415871
_ | ___ |
i
Effective Dates 10/01/89 Release Number* 1.0 Pages R13
-------
B1IRI1583811IG02 I
I
UIC431 15.7
I-I -I
10115871
B2IRI1583811IG02 |G01
1_ _ I .._ I ,
I I
111C483 IB
1-1 I-
10415871
B2UI158381 1 IG02 1601 UIC485 I220
10415871
B2IRI1583811IG02 |G02 UIC483 IB
10415871
I 1
B2IRI15838111G02 IG02 UIC485 M21
10415871
I 1
Effective Dates 10/01/89 .Release Numbers 1 .0 Pages
-------
DATA CAPTURE FORM B
EXAMPLE 3
e objective of the section on Page A16 is to submit Source/Entity
/ata and Treatment Data with a user supplied SE ID, and TREATMENT ID.
SECTION B1 - SOURCE/ENTITY DATA
This entry will insert a Source record for a Permanently
Available, Purchased, Surface Source, the Town of
Cumberland. Note that the seller PWS-ID number is
provided to show from whom the water is being purchased.
SECTION B2 - TREATMENT DATA
The Treatment Objective of N represents No Treatment At
Source, while the Treatment Process Code of 997 indicates
that the Treatment was applied at the Plant. Note that
if a Treatment Objective of N is reported, NO OTHER Treat-
ment Objective may be reported for that Source record.
EXAMPLE
SECTION B1 - SOURCE/ENTITY DATA
This entry will insert the required Plant record (The
Jackson Treatment Plant) that was referred to in the
"Treatment Applied at Plant" Treatment record in Example 3
above. Note that at least one Plant (SE Record Type P)
record with Treatment Objectives other than N, must be
provided whenever a Source record specifies a Treatment
Objective of N.
SECTION 82 - TREATMENT DATA
Treatment Objectives F, D and C, (Iron Removal, Disinfection and
Corrosion Control respectively) are shown, identifying the related
TREATMENT PROCESSES: Aeration, Spray (149); Filtration, Slow Sand
(346)! Hypochlorination, Pre (423); and pH Adjustment (740)).
Effective Dates 10/01/89
Release Number:
Pages A15
-------
Public Water System
Data Capture Form B
BATCH DATE
(CtBII
i-mtn u -
SOURCE / ENTITY DATA ^
f*~m** ** ** H*ME f , TWS
|B1| iQiQi /| |T|0|U|A/| \C\f\ iCUirtifiitfufi^iJiAJiA i i i i i i |S|
(C401I (C40J)
SEUJBIPWBD
STATE D NUMBER
twin
TOWMMPMNOE
. TOWMSMPN* . RANGE EAW . SEC . "MSEC .
1 1 1 1 1 1 1 1 1 1 1 1 1
(C41t| (Cttll (C4t3) («IS
(CMS)
LATITUDE IONOITUOE
DEO MM SEC OEO MM SEC
(C4tS) (Ml 7)
SIVCT REACH _O"
HYDRCLCOC UNIT CODE SEONUU REACH
1 1 1 1 ! 1 1 1 1 1 i 1 I 1 1
(M27) om>(4« .RMNOE EWT .
1 M 1 M I 1 1
(C41«
(M17)
RIVER REACH «
HVOMOUXIBUNITCaOE SEONUH REACH
J I I I I I I I t I I I ILJ
(GOT) (C42W
flEACHMUB
I I I I 1*1 I 1
(Mil)
TREATMENT DATA
S6D
TREATUEMT
OBJECTIVE
TflEATHENT
IDDI2J
Bffl
i n i
(UD1)
(Ctti)
[Dl
|0]
l£l
IC4UI
1/£I2I
IfgBl
M$|
I I I
{C4UI
Effective Date* 10/01/89
Release Number: 1 . 0
Page: fi16
-------
Sample Data Transfer File Records - FORM B
m2 3-11 12-18' 19-25 26 27-31 32-71
i i i it i ______ _ __ _
i * \ " | _»*- __ i | __ _ i __.
B1 IRI1583811 1001 | IIIC403 I TOWN OF CUMBERLAND
_ I | j _ | j
B1 IRI1S8381 1 I 001 [ I1IC405 IS
. | | | - | I !>
B1 IRI1S8381 1 1001 | IIIC407 IP
I | I - I 1
B1 IRI158381 1 1001 I IUC409 IP
1 j |_j |
B1 IRI158381 1 1001 [ lltC411 IRI1647530
1 1 1 - 1 1
B1 IRI158381 1 1001 | UIC415 1415700
I j l_| I
it
l [RI158381 1 I 001 | IHC417 1712500
-I I- I I -I I-
B2IRI1583811 1001 101 UIC483 IN
| j_ . |_| I
B2IRI1583811 1001 101 UIC485 I997
1 1 1-1 1
B1 1RI1583811 1002 1 |I|C403 1 JACKSON TREATMENT PLANT
, | I |_| |_ .
B1 IRI1583811 1002 1 IHC405 IP
1 1 . - | - | i
B1 IRI1583811 1002 1 HIC407 IT
1 1 1 1 _ | 1
« _ ,
'75-801
_ 1 ______ 1
10415871
1 1
10415871
.___ i _ __- |
10415871
, i __ i
10415871
._«.._ | _- i
10415871
. i i
10415871
i _ i
1041587!
1 1
1041587!
__ i - i
10415871
._ i _ i
10415871
i 1
10415871
I . i
I 04 15871
1 1
Effective Date: 10/01/89 Release Number' 1-0 Page' fl17
-------
B1IRI1583811 1002 ;l ' IIIC409, |P
10415871
- 1 i 1 , ! - 1 1
B1 I RI 15838 11 1002 1 UIC415 1415700
B1 IRI1583811 I002 1 |I|C417 10712500
I I I - | --- | ~-
B2IRI153381 1 1002 101 IHC483 IF
i i i t i i
B2 IRI1583811 1 002 101 UIC485 1149
1 1 1 II1
B2IRI15S3811 1002 102 UIC483 ID
1 1 1 1 1 t
B2IRI158381 1 1 002 102 UIC485 1346
u2!RI158381 1 1 002 103 IHC483 |D
B2IRI1583811 1002 103 UIC485 1423
1 1 \ 111
B2IRI1583811 1002 104 UIC483 1C
B2IRI1583811 1002 104 UIC485 1740
i i t i _ i i
. , ,
10415871
{]
|041587f
_ I _^ - t
10415871
I041587J
10415871
___ i t
10415871
/
10415871
10415871
_ _ i _ i
1041587!
t i
10415871
1 1
Effective Date' 10/01/89 Release Numbers 1.0 Pages - &18
-------
DATA CAPTURE FORM B
EXAMPLE 5
Jhe objective of the example on Page A20 is to remove the Latitude and
-ongitude information. This is done as a modify using the * in the
first position of either the Latitude(C415) or Longitude(C417). In
this example ue have blanked out (initialized to nulls) Latitude.
Longitude will be blanked out automatically (i.e., initialized to
nulls) by the system. It is not necessary for the user to do both.
RECORD DELETIOM FORM
SECTION B2 - TREATMENT DATA
The example on Page A21 shows how to delete a C<*80
(Treatment Data) Data Base Record (DBR) from FRDS-II.
Note that all values previously reported for this
treatment data record will be removed with this single
command.
Effective Date: 10/01/89
Release Number: 1,0
Page: ft19
-------
Public Water System
Data Capture Form B
n*»»
ACIIOHOOOE
BATCH MTC
1 f S6°
(C401I
SEUJ
STATE
1 1 1
SOURCE /ENTITY DATA SE
RECORD
NAME ' TWE J
1 I 1 1 | I | ! 1 1 1 1 1 1 1 1 1 ! 1 1 1 1
(C«J|
=flPW3K>
O NUMBER
1 1 1 1
Mil)
TOWMMPRANOE
lTT"| iTiTiTi
(C41t)
[B2| "
L
LL
LL
LL
LL
«cww
(C421) IC42D (642D
(C40S)
IATITUOE LONBITUOE
5EQ MM SEC OEO ' MN SEC
l$ I I I I I I I I I I I |
FWER REACH ON
HYDROLOQJC UNIT CODE SEQNUM REACH
I I I I I I I I I I If | L
SE
CODE AVALMUTV
U LJ
REMMMLE8
! 1 I'l II
(CUT) {GIN) (GUI)
TREATMENT DATA
JJ LLT 77 l""
U U
JJ LL
JJ LL
U LL
(win
JJ U LL
JJ " U LL
JJ U LL
JJ U LL
(C«» (CMS)
MEHT
£SS
JJ
JJ
JJ
JJ
l 4
1
SED
|Bl|i 1 1 1
(C*i>
sai
STATE
1 1 1 1
ITT"
(C4I«)
[F2J *
L
LL
LL
LL
LL
(C40t|
SOURCE /ENTITY DATA x
RECORD
NAME TYPE
1 11111)11 1 1 1 1 I 1 1 1 1 1 1 1 1 1 1 1
.ERPHWD
0 NUMBER
! 1 11 1
TOWNanPRANOE
« RMOE &W SEC . 1MBCC
1 1 1 1 1 1 1 1 1
(Ctt1) . {C4&B) {C439)
7f
D !»
«MII
(CMS)
LATITUDE LONOirUOE
CCQ MM SEC OEO MH SEC
1 1 1 1 1 II 1 II 1 II 1 1
(C41S) (C417)
RNERREACM _QN
MYDROtoacunrrcooe SEONUM RUGH
I I I l l l I I I I I 1 1 | L
se
COOS AVAKABUTV
u y
REACH MIES
Ill-Ill
(C427) (04») (C43I)
r£A7M£AnrD4T4
nCHT TREATMENT TREATMENT
B OBJECTIVE PflOCEW
JJ U LLLJ
U U LL
_U U LL
JJ U LL
JJ U LL
(C4MI {COS!
u
u
u
u
4
Effective Dates 10/01/89
Release Number* 1 . 0
Page'
-------
FRDS - II RECORD DELETION FORM
Batch Date
RECORD TO BE DELETED
QUALIFIER1
PWS ID
QUAURER 2
SUM
I
I I i I
PWS ID *
^_^ SIM OHaitm O
[JTIl i I i i i , t t I i I 1 1
PWS ID
SUM
/i/l \0\o \2 \
(CW1)
(C*01»
»-
PWS ID
Saw DNuntar . ,
I I I I I I I I I I I I I
SERV
D
-------
Sample Data Transfer File Records - FORK B
1-2 3-11 12-18 19-25 26 27-31
__ | | _...: J ._ , . J ;__
32-71
75-8
81IRI15838111001 I
IMIC415 |$
I-I 1
I080888!
B2IRI1583811I002 I04 |D|C480 I
10816881
I- J
10415871
! 1
1041587!
I 1
Effective Date: 08/30/89 Release Kurober: 1.0 Page: A22
-------
DATA CAPTURE FORM C
EXAMPLE 1
he objective .of the example on Page A21 is to Insert Geographic Areas
Served, Information.
SECTION C1 - GEOGRAPHIC AREAS SERVED
The user has requested FRDS-II to generate the GA ID
in this example. He/she has Inserted new information ,
on Administrative Region 01, Federal Congressional
District 01, FIPS County Code 007, and the City
of Cumberland being served by this PUS.
SECTION C2 - SERVICE AREAS
FRDS-II uill generate SESV ID for this Service Area, uith
a TYPE/CAT of R2 (Mobile Home Park), another Service Area
uith a TYPE/CAT of T2 (Service Station) and one uith S2
(Institution). Note prefixes R = Residential, T =
Transient, and S - Semi-residential. Also, since the
Primary Service Flag need only be reported for Non-
Community and Non-Transient, Non-Community Mater Systems
(i.e., PWS-TYPE of N or P) and this is a Community Water
System, the Primary Service Flag need not be reported for
this PUS.
SECTION C3 - ON-SITE VISITS
FRDS-II will automatically generate the VISIT ID in this
example. This section uill create a Visit record in
FRDS-II uith a Visit Date of March 28, 1987, and a Visit
Reason 1, indicating a Sanitary Survey uas the reason for
the visitation.
Effective Dates 10/01/89
Release Number: 1.0
Page'
-------
Public Water System
Data Capture Form C
WL1
. Acmmcace UTCHMW ^
» iDNura* tu Mr
1*^ ''Til,, i 1 ' ' ' ~j_j_£J l^J i-mm « .**»» . I 0 [7 | / I Jrl 1 71
(C101I
[H] GEOGRAPHIC AREAS SERVED
FEDERAL . "
ADUM AOMM CONGRESS STATE FIPS CITY INDIAN
QAD REGION DISTRICT DISTRICT COUNTY COUNTY ' RESERVATION
|6i/llOi/ll i I \0\l\ \ | P|0|7||C|U|M|8|e^!t|A|^6t 1 1 I
1 Ml 1 III 1 1 I 1 1 II l|
i i n nil II II
I II I
I II I
I i II i I I 1 II 1 1 II 1 ! I Ml 1 1 1 ! 1 1 1 1 1 1 1 1 1 1
(csoi) (cm) (csos) icsmi tcsoo (cscw (csi3) (Csnt
IC2I SERVICE AREAS
__, PRIMARY
SE"* SERVICE
D TYPE/ CAT PLAO
l£i 2l |T|2j LJ
LLJ LLJ LJ
LLJ LLJ LJ
LLJ LLJ LJ
<«01| (CMO) (CMS)
i
I03 I ON-SITE VISITS
VISIT VISITOATE VISIT
ID MO DAY Yfl REASON
III I I M M LLJ
Ml | I M M LLJ
I i I | |l|ll LLJ
till f M I I LLJ
Ml | I | M M LM
(C701) (C703) (C7W
Effective Date: 10/01/89
Release Number: 1.0 Page
-------
Sample Data Transfer File Records - FORM C
2 3-11 12-18 19-25 26 27-31
I _ 1 __ : | :_ | _ | : j ...
iIRI15838111G1 I UIC503 101
32-71
75-80 I
101*15871
i r
C1IRI1583811IG1
I
UIC507 101
I-I 1
10415871
C1IRI1583811IG1
IHC509 I007
I-I I
0415871
C1IRI1583811|G1
--! I
IIIC513 I CUMBERLAND
1041587!
I 1
C21RI1583811IG1 I
I
IHC603 |R2
I-I 1
10415871
C2IRI1583811IG2 I
I-
IIIC603 IT2
l-l 1
10415871
I 1
IRI1583811IG3 I
I.. '_-_,.. I ....... 1
I I
IIIC603 IS2
l-l I
10415871
. i ______i
C3IRI1583811161
I I
I
IIIC703 1032886
l-l I
10415871
, i______i
C3IRI1583811161
I. i
IIIC705 11
l-l 1-
0415871
Effective Date: 10/01/89 Release Number: j. 0 Page:
-------
DATA CAPTURE FORM C
; ' ' : EXAMPLE 2 ...
The objective of the form on Page A27 is to Insert Geographic Areas
Served information along uith Service Areas and On-Sight Visits data as
in Example 1 of Data Capture Form C. However, in this example, the user
submits the GA ID, SERV ID and VISIT ID instead,of them being generated
by the system. . -
The user has entered a State County Code rather than the FIPS County
Code. However, he/she had previously submitted the requisite State
County Code to FIPS' County Code conversion table to the FRDS DBA, thus
enabling FRDS-II to store both code values in the data base.
Effective Dates 10/.OL1./A1. Release Number: j . Q Page? _J,26
-------
Public Water System
Data Capture Form C
Acrumcax
(C101)
ill
/
itf a
GEOGRAPHIC AREAS SERVED
AOMM AOMM CONGRESS STATE FIP9
Q*O REGION DISTRICT DISTRICT COUNTY COUNTY
CITY
LJLJLLJLU I i I I I I I L
LULU LLJ I i I I I I II I I II
LULLJ I i l LU 1
(MOD (CSM» (CMS) (C907)
1 1 1 1 1 1
(CM) (CS131
INDIAN
RESERVATION
|0L/ll£l2JLj_I lDi/l Plflfel I I I pUJlHIdgUKUtldlfl i I I I I i I M I
II
1 1
(CMS)
II II
SERVICE AREAS
SERV
ID
(Cni)
TYPE/ CAT
LLJ LJLJ
PRIMARY
SERVICE
FLAG
U
LJ
LJ
\C3\ ON-SITE VISITS
VISIT VISITOATE
IO UO DAY YR
III 1 1 1 1 1
Ml Mill
Ml Mill
Ml | 1 1 1 1
M 1 Mill
fCTOT) (C7Q3)
I |
| |'
I |
| |
I |
VISIT
REASON
I/U
LU
LU
LU
LU
LU
(C70S)
Effective Date: 10/01/89
Release Numbers 1.0 Page
-------
Sample Data Transfer File Records - FORM C
-2 3-11 12-18
__ I ______ 1 1
C1IRI1583811I01 1
1 1 | .
C1IRI1583811I01 1
| I 1 ,
C1 [RI158381 1 101 |
I 1 _ t .
C1 IRI158381 1 101 |
1_ 1 j.
C2IR1 15838 11 101 I
-1 | i.
C2IRI1583811 101 I
i i t.
02IRI1583811 102 |
-i i i.
C2IRI1583811 103 I
_i i _ i.
C3IRI1583811 101 I
_ i _ i i .
C3IRI158381 1 161 }
i i i .
19-25 26 27-31 32-71
IIIC503 I02
IHCS07 101
IIIC508 I006
I - | .-,
UIC513 I CUMBERLAND
IIIC603 !R2
IIIC603 |Y
IHC603 lT2
IIIC603 |S2
IIIC703 I032887
I I
IIIC705 11
i - i - . i
~P
75-801
__ |
10(415871
1
10415871
1
10415871
1
10415871
1
10415871
1
10415871
1
1
1041587!
1
10415871
1
1041587!
1
10415871
i i
Effective Date: I_Q_XQ 1 /8f Release Number: 1.0 Pages IL28
-------
DATA CAPTURE FORM D
EXAMPLE 1
The objective of the form on Page A30 is to Insert Violation Data for
RI1S83811. In this example, the user has provided the Violation ID
Number and contaminant information related to a monitoring violation
(Violation Type 03).
SECTION D1 - VIOLATION DATA
Violation 8600006 is a Regular Monitoring Violation (T ype
03) for Coliform Microbiological Contamination
(Contaminant 3000). This is a Major Violation since no
required samples were taken. The Compliance Period Begin
Date (i.e., Violation Date) was October 15, 1985, with a
compliance period of one month.
DATA CAPTURE FORM D
EXAMPLE 2
SECTION D1 - VIOLATION DATA
Violation 8600007 is also a Regular Monitoring Violation
for Coliform. It is a Major Violation with a compliance
period of one month.
Note: The two examples on this page are almost identical.
.The purpose is to demonstrate the collection of data for
tuo violations, uith the same batch date, for the same
Public Mater System on the same Data Capture Form.
Effective Date: 10/01/89
Release Number: 1.0
Page: A29
-------
Public Water System
Data Capture Form D
iftTri \ i£i S, 'D£gr, / , /I ITI , - 10"
(Mil .
[pi"! VIOLATION DATA
VIOLATION 0 VIOLATION COMPLIANCE PERIOD BEQN
ICMWJ (C1103) (C1106) (C1W7)
COMPLIANCE PERIOD END
MO DAY YR
Mill 1
(CUM)
BATCH MTS ^i
(/ \ / X^l ^|*7|
OR
"pST
(C11U)
MOMTORMQ AND REPORTMQ VOLATXM3
>: AWARENESS DATE NUM SAMPLES
SEK) "^ w*»»= RFfllHRFn
i i i iTiTiTi MM
(C1143) (0111$) iCtlST)
i r i o«
(C112W
.y. Y.Y6S
LLJ M*"0
OR"
UAXMUMCONTAMMANT LEVEL VIOLATIONS
ANALYSIS
METHOO ANM.VSB RESULT
1 M 1 M.M 1 Mill
MCLVK
M M M.I
ILATED
1
1 M 1 1
(C1121) (C1123) (CtlJS)
__
[pT| VIOLATION DATA
VBLAtJOND VIOLATION C9MPLUNCE PERIOD BEGM
\8fay)\0\o\o\~)i fL\o\Q \6\ \fy3\ I/ 1/ l^l/ l^i$i
(B«01) ' (C110S) (C110S) (CtWT)
COMPLUNOE PEROO END
MO DAY VR
1 1 M 1 1
IC1KN)
OR
Id 101 /I
MONrrORMO AND REPORTMa VOLATIONS
SED AWARENESS DATE REQUIRED
MM I'l'lTlTl MM
(Ctt43) (C111S) (C1127)
NUM SAMPLES
TAKEN
II 1 OB
(C1129I
MAJOR
VIOLATION
.y. Y.YES
IN N.NO
OR
MAXMUU CONTAMINANT LEVEL VIOLATIONS
ANALYSIS
METHOO ANALYSIS RESULT
1 M 1 1 1 1 1 Mil III
MCLVDLATED
Mill I.I 1 1
1 1 1 II
(01121) 101123) (C112S)
Effective Date? ^0/01/.8_S Release Numbers 1.0 Page* ft3J.
-------
Sample Data Tzansiez File Records - FORM D
3-11
12-18 19-25 26 27-31
______( _ | _ | |
IRI158381118600006 I U1C1103I3000
32-71
75-80
1041587
D1IRI 158381 11 86000061
| |
II1C1105103
1
10415871
D1IRI1S8381118600006
1 1 C11 07 I 1 0 1585
10415871
I 1
D1IRI158381118600006 I
__ f | |
IIIC11111001
I-I I
10415871
I 1
D1IRI1583811I86000061
, | j
II1C1131IY
I-I I-
10415871
I !
D11RI15S3811I8600007I
__j | ]
Hid 1031 3000
I-I I
1041587!
i 1
IRI1583811I8600007I
| i ' |
UIC1105I03
,|_i _..___ i
i i i
10415871
,| 1
D1IR1 158381 1186000 07
I
UIC1107I 110185
I I 1 .___ __,.
I I 1
10415871
| j
D1IRI1 58381 118600 0071
IC1111I001
10415871
| 1
D1IRI158381118600007
__ | |
IIIC1131I Y
I-I I-
10415871
Effective Dates 10/01/89 Release Number: 1.0 Pages A31
-------
DATA CAPTURE FORM D
EXAMPLE 3
fhe objective of the example on Page A33 is to Insert Violation data
for Public Water System RI1583811.
SECTION D1 - VIOLATION DATA ... - .
Violation 8700231, for Arsenic, type 02 (MCL, Average) has a
Compliance Period Begin date of July 01, 1986. The Awareness
Date was March IS, 1987. "
The Analysis Method 101 (Atomic Absorption) used resulted
in an Analysis Result of .06. The MCL Violated was
'.05.
Effective Date: 10/01/89
Release Number: 1 .0
Page
-------
Public Water System
Data Capture Form D
Ufcl
m *»**«* BATCH DATs
Stt» IDNwrfev ^^
|^ I^J^ 1 W ,J I v I ^7 | O \f\fu 1^^^ 1 i .^^^ » I^^^UL. 1 ^7 T* 1 f I ^j| 1 A 1 f \
(C101>
["5TI VIOLATION DATA
py ID NUUBCR W "^ ^"
|5|7|0i0l^)3iyi |/|0[OL5l |0|i| Idl7l«l/lfl6l
(CHOI) (C1109) (C110S) (01107)
COMPLIANCE PERIOD END """oURSS^''100
HO Mr YR ' OR
iiiii i I0i3 id
UOMTORMQ AMD REPORTMa VIOLATIONS
SEO REQUIRED
HO DAY YR "^^
|0|0|/J I<5|3|/^l71 Mil
(C1143) (C1115) (C11J7)
CAM SAMPLES MAJOR
TAKEN VBUflBN
|| || V.VES
| OR LJ »»»
(C1129) «"wi
OR
ANALYSa
METHOD ANALYSB RESULT Ma VIOLATED
\l\0\l\ I I 1 1 M 1 I.IOI6I 1 II 1 1 1 1 1 1 1 1 .I^I6T 1 1 1 1 1
(C1I21) (C11ZD (CtlzS)
fpT[ VIOLATION DATA
_._._ VIOLATION COMPLIANCE PEBOOBBJW
VIOLAMON il fYWtiMIMlMT TYPE
FY 03 NUMBER «-««.««. r« MO DAY YR
ill III 1 ! 1 1 1 1 1 1 1 1 1 III
(C1101) (C1103) (C1106) (C1107)
Dcamnn OOMPUANCE PERIOD
COMnJNMCE PKIW*J erao OURATK1N
MO DAY YR OR
IIIII I I I I I
MONmMNO AND REPORTMB WOLAnONS
SEE) AWARENESS DATE REQUIRED
i i iTiTiTi INI
(C1143) (C1115) (01127)
NIM SAMPLES JfSSL
TAKEN VQATION
|| || V.YES
1 OR LJ M-"°
(CI12»
OR
MAXWUMCONTAUMANT LEVEL VIOLATIONS
ANALYSIS
METHOD ANALYSIS RESULT Ma VIOLATED
1 1 1 1 1 1 1 1 1 I.I 1 1 1 II 1 1 1 1 1 1 1 1 .1 M III 1
(C11Z1) (C1123) ^,,25,
Effective Date: 10/01/89 Release Number: 1.0 Page* A33
-------
Sample Data Transfer File Records - FORM D
1-2 3-11 12-18 :
1 I RI158381 1 18700231 I
D1 IRI158381 1 18700231 I
D1 IRI1583811I8700231I
i ____ ____ i _____ i
D1 IRI1583811 18700231 I
D1 I RI158381 1 18700231 1
D1 IRI1583811 18700231 I
D1 IRI1583811 18700231 I
_ i _ _______ i __ i
01 I RI158381 1 18700231 I
I_ t i
D1 IRI1583811 18700231 I
1 1 i .
19-25 26
II
II
II
II
II
II
-
II
II
II
-_; _ i _
27-31 . 32-71 75-80
IC1103M005 1041587
IC1105I02 10415871
1C1107I070186 (041587!
i _ i _ _ __ _ ___ i
IC1111I036 10415871
IC1143I001 1041587
IC1 1 151031587 ~- 1041587
i _ __ | __ |
IC1121I101 1041587!
i _ | _____ __ __.. __ __., _ ___ | «_ ___ |
IC1123I.06 10415871
i __ i __ _ ___ __ ______ _____ i __ ___
i i i
IC1125I.05 10415871
I i _ I I
Effective Date* 10/01/89 Release Number: 1.0 Page: A34
-------
DATA CAPTURE FORM D
EXAMPLE 4
The objective of the example on Page A36 is to Modify violation data
for Violation 8600006, for PUS RI1583811.
SECTION D1 - VIOLATION DATA
The Compliance Period Begin date was erroneously inserted
as October 15, 1985. In this modify ue are changing the
Compliance Period Begin date to October 1, 1985.
RECORD DELETION FORM
SECTION D1 - VIOLATION DATA
The example on Page A37 shous hou to delete a C1100
(Violation Data) Data Base Record (DBR) from FRDS-II,
Note that all values previously reported for this
violation record and all linkages to its related
enforcement actions uill be removed uith this single
command.
Effective Date: UD/01/89
Release Number: 1.0
Page:
-------
Public Water System
Data Capture Form D
PWS ID
ACTKMCOOf
BATCH MIX
>| 'I
l
001)
["DI~| VIOLATION DATA
VIOLATION COMPLIANCE PERIOD BEGM
VIOLATION ID CONTAMINANT TYPE MO DAY YR
(C110H (CUM) [CUM) (CtlOT)
OOMPUANCE PERIOD END OURATION
MO DAY YR OR
I I I I I i I MM
(C11W «»'»>
MONITORMa AND REPOHTMa VIOLATIONS
AWARENESS DATE NUM SAMPLES
SEO ""* REQUIRED
MO B»T in
MM 1 M I 1 i 1 MM
(C1143) (C111S) <«"«»
HUM SAMPLES MAJOR
TAKEN VKJLATBN
II || Y.YE8
| OH LJ N-HO
(C1129)
OR
MAXMUMOONTAMMANT LEVEL VIOLATIONS
ANALYSIS
METHOD ANALYSIS RESULT
1 III 1 I.I 1 II
MCL VIOLATED
I I ! I I I.I I Mill
(C1121) (01123) (C11ZS)
II
, p
[pi"! VIOLATION DATA
u«»-n~.« VIOUTON COMPLIANCE PEHI008EOW
FY """DUMBER CONTAMWANT IYPE « DAY YR
1 I 1 I ill II 1 1 M 1 1 1 III
(C1101) (C1103) (C110S) (C1107)
COMPLIANCE PEROO END """oURATof SI°O
MO DAY YR OR
I i I i I I I MM
(C1109) |t"1"
MONITORINQ AND REPORTWO VIOLATONS
SEIO AWAHENCSS DATE ^acniwKn^
MO DAY VR HB*"
I I I i I i i i I Mil
[C1M3I (C111S) (C11ZT)
UUSAUPLCS MAJOR
TAtffiN WHATON
II II V.YES
I OH LJ "-NO
(C1128) * "
OR
MAXUUUOONTAMMANT LEVEL VIOLATIONS
ANALYSIS
METHOD . ANALYSIS RESULT
1 1 1 1 1 1 1 M ' III
MCL VIOLATED
1 II
(C11Z1) (C11231 (CI125)
Effective Dates JJ>/01/89 Release Numbers 1^0 Pages ft3Q
-------
S3S38SS FRDS-II RECORD DELETION FORM
RECORD TO BE DELETED
Batch Date
QUAURER 1 QUALIFIER 2
PWS ID ADORESS
SM« ONlfffcv
I I I I I I I I I I I I I
1C101I (C301)
PWS ID SE
KM* DNurtMC 10
| , i i , , , , , | I II I
I04"1)
QUALIFIER 3
ACTION CODE
DATA BASE
RECORD
(0101)
SUM
PWS ID
,
t
J I II I
(C101) (C40t»
PWS ID »
SIM DNURter .... |
I I I I I I I I I I I I I
(Ciet)
PWS ID
SUM ONuntm
I I I I I I I I I I
TREATMENT
10
|C4tl)
S6RV
O
(C101)
SOtt
PWS ID
(C«01)
VB(T
« TREATMENT
| n| (CSOO) GEOGRAPHIC AREAS
I ul SERVED
Q I (CSOO) SERVICE AREA
(C7DO)OW«ITEVISrr
Dl (C1100) VIOLATION
(C1200)ENFORCEMENT
(C3000) VARIANCES, EXEMPTIONS
| D| ft OTHER RELATED DATA
(C3100)VESCHiOULE
(cwoo
(C4000) STATE (NSCRETIONARY
I P I DATA
Effective Dates 10/01/89
Release Number: 1.0 Pages A37
-------
Sample Data Transfer File Records - FORK D
1-2 3-11 12-18 19-25 26 27-31.
-». I ^^mmmm.mmmmmmmmmm I «*«,»,«»^.il*,,,*, -I wmwm^mmmmmmm I *» I m» mm mm mm mm. I _ ^. *,«__.
D1IRI1S8381118600006I IMIC1107 I 100185
32-71
75-
I
1081388}
i ___ i
i i
D1IR11583811 I 8600006! IDIC1100I
10816881
I I
Effective Date: 10/01/89 Release Number: j.0 Pages ft38
-------
DATA CAPTURE FORM E
EXAMPLE 1
The objective of both examples on page AUO is to Insert Enforcement
Data for PUS RI1583811. Data for two Enforcement IDs for one PUS has
been collected on one Data Capture Form, with the same Batch Date.
SECTION E - EHFORCEMENT DATA
The ID for this Enforcement (8600001) has been assigned by
the user. The Follou-up Action that was taken and is being
reported (FG) is a Formal Action, State Issued Public
notification. The date on which the Enforcement Action was
taken by the state against PUS RI1583811, was March 1,
1986. The Associated Violation ID (entered in Y5000) for
this enforcement (i.e., the violation for which the
enforcement action was taken) is 8600006.
EXAMPLE 2
SECTIOK E1 - ENFORCEMENT DATA
Enforcement 8600002, against Violation 8600007, was also ;
Formal Action, State Issued Public Notification. The date
the enforcement action was taken was April 1, 1986.
Effective Dates 10/01/89
Release Number: 1.0
Page: A39
-------
Public Water System
Data Capture Form E
PWSJD
ACTION CODE
BATCH DATE
(C101I
E1
ENFORCEMEM
-------
Sample Data Transfer File Records - FORM E
2 3-11 12-18 19-25 26 27-31
I i ______ j. i _______ i _ i _____ i __.
1IRI1S8381118600001 I 111C1205 IFG
32-71
75-80
[041587
. i___
E1IRI1S8381118600001 I
I
UIC1203I030186
I-I I
1041587
E1 I R11-5838 11 18600001 I
I
IIIY5000I8600006
I-I I
10415871
I 1
E1IRI1583811186000021
IIIC1205IFG
I-I I
10415871
E1 IRI1S83811 I8600002 I
I
IHC1203I040184
I-I I
10415871
E1[RI1583811186000021
IllY5000I8600007
I-I I
10415871
Effective Dates 10/01/89 Release Number: 1.0 Page' A41
-------
DATA CAPTURE FORM E
- ' EXAMPLE 3
The objective .of th'e example on page A43 is to show that whenever an.
Associated Violation Range (X5000) is employed to establish a linkup
with applicable violation records, the violation end date need hot be
specified: the system will always use the ENFORCEMENT DATE submitted
as the ASSOCIATED VIOLATION RANGE End Date whenever the end date is not
specified.
SECTION E1 - ENFORCEMENT DATA
The user wishes to apply this formal Follow-up Action, F2
(Civil Action Filed) to all violations occurring within
the violation range of July 1, 1986 and June. 30, 1987.
.Since the end date was not specified, the system will
assume the end date to be the same as the enforcement
date. ...
Effective Date: 10/01/89
Release Number' 1.0
Page' A12
-------
Public Water System
Data Capture Form E
BATCH DATE
(C1011
ENFORCEMENT DATA
ENFORCEMENT D
NUMBER
FOLLOW4JP
ACTION
ENFORCEMENT DATE
MO DAY YH
ASSOCIATED VOLATION RANGE
BEGIN
MO DAY YR
END
MO DAY yB
i i 1 i 1 i 1
OR
ASSOCIATED VIOLATION OS
VOLATBN01
FY 0 NUMBER
1 1 1
1 1 1 1 1
WOLATON02
ONUMBER
VWLATONOJ
FY IONUMBEH
WJLATCNO4
IONUMBEH
1 1 1 1
1 1 1 1 1 1 1 1 1
1 J
(YSOOO)
OR
ASSOCIATED VIOLATION CONTAMMANT GROUPS
COMPLIANCE PERIOD
BEQMOATE
TYPE CONTAMMANT , MO DAY YR
COMPLIANCE PERIOD
BEOMOATE
TYPE . CONTAMMANT , M O . DAY
COMPLIANCE PERCO
BEGMOATE
TYPE CONTAMINANT . MO DAY YR
iirt wninmmi . MU OUT . "1 - ITre GGNrAMMJUVT . MO OAT TH . | I Tre MmiJUIIWni i
I I I I I ill I I I I I I I I I I I M I I I I I I i III I I
(HOW
ENFORCEMENT 0
FY D NUMBER
FOU.OW4JP
ACTON
ENFORCEMENT DATE
MO QAV YR
_ r T . «* iiijniiibn r^r* *w ^ *f *^-' "
I I I I I I I » I I I I M M I I I +
*risrt« ^B^^_^^_^to^ -j-
[C1»1)
(CMOS
ASSOCIATED VOLATION RANGE
BEGIN
MO DAY
YR
U0
END
DAY
yR
11 i 1111 11 i 1111
txMW1
OR
ASSOCIATED VOLATION OS
VIOLATION Ol
FY 0 NUMBER
III)
iiil
VOLATION D 2
FY ONUMBER
1 1 1 1 1 1 1 1
FY
| |
ID NUMBER
i 1 1 1
V
_U UJ
K&ATIONO4
0 NUMBER
1 1 1 1 1
(YSOOO>
OR
ASSOCIATED VOLATCN CONTAMINANT GROUPS
COMPLIANCE PERIOD
BEQMOATE
TYPE OONTAMNANT . MO DAY YR
COMPLIANCE PERIOD
BEONDATE
TYP6 . CONTAMINANT. MO . DAY . YR
COMPLIANCE PEHOD
BEQMOATE
TYPE CONTAMMANT .MO DAY YH
-= uuniwinOTi - MV OUT . TN , ITF6 CONTAMMANT . MO DAY . YR . . IT»* CONTAMHANI . MU U«T . TH .
I I I i I I Tl I I I ! I I I I I I I II I I I I I I I I I III I I I I I I
(ZSOOO)
Effective Date ' 10/0 1x89
Release Number' 1.0 Page'
-------
Sample Data Transfer File Records - FORM E
1-2 3-11 12-18 19-25 26 27-31
32-71
7S-80
I
.1 IRI1583811I8600003I
UIC1203I063087
I-I I
081587
E1IRI1583811I8600003I
IICl205lFfi
1081587
E1IR1158381118600003! 111X5000I 070186
10815871
I 1
Effective Date: 10/01/89 Release Numbers 1T0 Page'
-------
DATA CAPTURE FORM E
EXAMPLE M
he objective of the example on Page A.U6 is to add an Associated
iolation Range (i.e., to apply this Enforcement Action against all
/iolations reported against this PUS whose compliance period began
sometime within the date range specified) to an existing Enforcement.
fhis is done as Modify Action.
SECTION E1 - ENFORCEMENT DATA
Me are modifying Enforcement 8600002 for PUS RI583811, to
establish linkages to all the violations that were
reported against this PUS that had violation dates in the
Range of October 1, 1986 - September 30, 1987.
.Note: Since no violation for this PUS falls into this date
range, (Violation ID 8600006 Compliance Period ended
September 30, 1986) this transaction will NOT create a
link to any existing violation.
Effective Date' 10/01/89
Release Number' JL...O..,
Page
-------
Public Water System
Data Capture Form E
prae
SM* _ IDNWMMT
ACTION CQOE
BATCH DATE
(C101)
C4
Cl
ENFORCEMENT 0
FY IDNUMBEI
\S |»|5|0 & |
(CWOn
VIOLATION D1
FY ID NUMBER
I I I I I I
(W000>
TYPE CONTAUMANT
I I I I
(Z30001
C4
Cl
ENFORCEMENT D
FY DNUUBI
III !
ICW01)
VIOLATIONDt
FY IONUMBE
1 1 1 1 1 1
(YSOOO)
TYPE CONTAMMA*
III)
(ZSOOOI
ENFORCEMENT DATA
FOLLOW4JP ENFORCEMENT DATE
1 ACTION MO DAY YR ' uo
0J-2J 1 1 II 1 1 1 1 1 + Hl<
(C120S) (C1ZW
ixsooc.
. . ASSOCIATED VOLATION IDS
VXXATXJNOZ VIOLATION ID 3
FY 10 NUMBER FY IDNUMS
I 1 1 1 1 I 1 1 1 1 I 1
OR
ASSOCIATED VOLATION CONTAM»4ANT GROUPS
COMPLIANCE PERIOD COMPLIANCE P6HOD
BEGIN DATE BSQWOATE
, MO .DAY YR , TYPE CONTAMINANT . MO DAY YR ,
1 1 1 1 1 1 1 1 1 1 I.I 1 1 1 1 1
FMFDflf*FMPMT HA TA
FCUOWMJP ENFOHCEMENTDATE
ER ACTON MO DAY VR M(
I_L_I i ii IIIIMI+ I_L
(ci!os) (ctaa)
(XSOOO)
ASSOCIATED VDLATON OS
VDLATON D 2 VIOLATION 10 3
R FY ID NUMBER FY ONUU
1 1 i 1 1 1 1 1 1 1 1 1 1
OR
ASSOCIATED VIOLATION CONTAMINANT GROUPS
COMPLIANCE PEROD ' COMPLIANCE PEROD
BEGIN DATE BEGIN DATE
IT. MO DAY YR . TYPE CONTAMMANT . MO DAY YR ,
1 1 1 I 1 1 1 1 1 II I 1 1 ll
ASSOCIATED VDUTKJN RANGE
BEGIN END
OAY YR MO °*Y Y«
OR
ER " DNUMBEH
III i 1 1 1 III
COMPLIANCE PEROO
BEOMDATE
. TYPE . CONTAMINANT . MO DAY YR
1 i 1 i i i 1 I Mil'
i
ASSOCIATED VDLATDN RANGE
BEGIN END
1 DAY YR MO DAV VR
1 1 1 1 1 1 I 1 II 1
OR
VIOLATION 04
BEA ^ "DNUMBER
, i 1 M i t i 1
COMPLIANCE PEROD
BEGIN DATE
. TYPE . CONTAMWANT , MO OAY . Y« .
1 1 1 1 1 1 1 1 1 1 1
Effective Dates 10/01/89 Release Number: 1,0 Pages ftjf.fi
-------
DATA CAPTURE FORM E
EXAMPLE 5-6
The objective of the example on page A48 is to show hou to Modify
enforcement related data already in FRDS-II. The first example
(Example 5) changes the existing Enforcement Date. The next example
(Example 6) adds tuo more Associated Violation IDs to those already
existing for this Enforcement.
EXAMPLE 5
SECTION E1 - ENFORCEMENT DATA
The Enforcement Date for 8600001 of PUS RI1583811 uas
erroneously inserted as March 1, 1986. In this Modify
example, ue are changing the date to June 15 > 1986.
EXAMPLE 6
SECTION E1 - ENFORCEMENT DATA
Two additional violations are to be associated with the
Enforcement Action 8600002 for PUS RI1583811. Violation
IDs 8600008 and 8600009 uere unintentionally omitted in
the original submission; they are.entered as Modify
transactions to correct this oversight.
RECORD DELETION FORM
SECTION E1 - ENFORCEMENT DATA
The example on Page A49 shows hou to delete a C1200
(Enforcement Data) Data Base Record (DBR) from FRDS-II.
Note that all values previously reported for this
enforcement record and all linkages to its related
violations will be removed with this single command.
Effective Dates 10/01/89
Release Number: 1.0
Page:
-------
Public Water System
Data Capture Form E
PWSO
ACTION cooe
BATCH DATE
(C101)
f«M*f U mUoOY
E1
FY
ENFORCEMENT DA TA
ENFORCEMENT O FOLLOW-UP ENFORCEMENT DATE
ID NUMBER ACTON MO DAY VR
ASSOCIATED VOLATON RANGE
. BEGIN END
MO DAY YR M0 DAY YR
1 1 1 1 1 1 1 1 1 1 1
1X88001 OR
ASSOCIATED VOLATON OS
FY
n
VOLATON01 VOLATON 10 Z V«
!O NUMBER py O NUMBER PY
"TEL. - ^TS-BER
1 1 1 1 1 1 1 1 i 1 1 1 1
OR
ASSOCIATED VOLATON CONTAMINANT CROUPS
Tl
COMPLIANCE PEROD COMPLIANCE
BEGMOATE BEGIN 0
PE CONTAMMANT , MO DAY YR . TYPE CONTAMMANT . MO DAY
1 in 1 i h 1 i 1 1 i 1 i i i 1 i i
PEROO COMPLIANCE PEROD
ATE BEGIN DATE
YR , * TYPE CONTAMINANT , tl O DAY YR ,
1 1 1 1 1 1 1 1 1 ! 1 1
iZSODO)
Effective Dates 10/01/JS9 Release Number: 1 . 0^ Page'-
-------
FRDS - II RECORD DELETION FORM
Batch Date
A3|
[eT
~B2\
"cTI
iT
iCJOtl
Sia>
| 1
(C101)
Sun
| |
(C10I)
sw>
| |
QUALIFIER 1 QUALIFIER 2
PWS ID ADDRESS
ID
l i i i Ti i 1 M t
(001)
PWS ID SE
ONwrtw ID
I I I I I I I I I I
PWS ID
lONwrtMr 10
1 ! I I I I I I I |
PWS ID
lONUfTMT . .
1 1 I 1 1 1 1 1 1 1 1
_.....____ DATA BASE
QUAUHEai HE«MP.
ACTION CODE "-»"
F"Q I (C300) ADDRESS
j~Q~j (C400) SOURCE/ENTITY
TREATMENT
| | 1 D |(C4SO) TREATMENT
[n 1 (CSOO) GEOGRAPHIC AREAS .
1 Ul SERVED
(CtOI)
I I
PWS ID
ON
I I I I I I I I
icwt)
(Clou
PWS ID
ON
I I I I I I I I
vair
LU
PWS ID
SUM lON
I I I I I ! I I I I
icwt)
PWS ID
(CI01)
PWS ID
S>w ONw
I I I I t i I I I I
IC101)
PWS ID
SM* IDNuB*»
I I I I I I I I I I
(cion
PWS ID
(C701)
VKXATXmO
FY D NUMBER
I I I I I I II
(CllOt)
ENFORCEMENT ID
FV ID NUMBER
\P\L\A\t3\o\d\l\
(C12D1)
VEO
FV DNUMBER
I I I I I I II
(C3001)
VEO
FV IONUMBER
I I | I I I I I
(C3D01)
SCO
10
SCH6O
(C3101I
s
I
.'
. .
0 I (C800) SERVICE AREA
QJ (C700) ON-SITE VISIT
(C1100) VTOLftTION
D| (C1200) ENFORCEMENT
_ I (C3000) VARIANCES, EXEMPTIONS
D I & OTHER RELATED DATA
I I I ID I (C310°)VESCHEOULE
(CMOtl
(C4000) STATE DISCRETIONARY
I DATA
Effective Dates 1Q/Q1/89
Release Number' 1.0 Page: A19
-------
Sample Data Transfer File Records - FORM E
1-2 3-11 12-18 19-25 26 27-31
~ I I.~- |
E1IRI158381118600002I
32-71
75-8
."j
1060188"
I I
IMIXSOOOI100186093087
I I _____'i _-._____' -
E1IRI158381118600001 I
IMIC12031061586
10818881
I 1
£11RI1583811186000021
I MlY5000186000088600009
10818881
1 I
E1IRI158381118600001 I
DIC1200I
I082088I
Effective Date: 10/01/89 Release Number: 1. 0 Pages JV&P,
-------
DATA CAPTURE FORM F
EXAMPLE 1
he objective of the example on Page A52 is to shou how to Insert
Variance, Exemption and Other Related Data for PUS RI1583811. A VE
Schedule is also included in Example 2. In all cases the user has
assigned his/her oun IDs.
SECTION F1 - VARIANCES,EXEMPTIONS £ OTHER RELATED DATA
The user has supplied the VE ID of 8600001 to identify an
Exception that was granted for Nitrite (Contaminant 1010)
for PWS RI15S3811.
This exemption became effective on January 1,
1987 and will expire on December 3, 1988.
DATA CAPTURE FORM F
EXAMPLE 2
SECTION F1 - VARIANCES, EXEMPTIONS £ OTHER RELATED DATA
The user has expressed an interest in an Other exemption
(Status A) for Arsenic (Contaminant 1005) by specifying a
Record Type of OT (Other), a modified MCL value of . 1 and
an Alternate Process of 360 (Flocculation). He/she has
supplied the. VE ID of 8600701 for this record. The
reason for the variance being requested (007) is due to
Facility Construction that is Pending.
This exemption became effective on August 31, 1980 and
will expire on December 31, 1988.
SECTION F2 - VE SCHEDULE
For the VE-ID 8600701, the user has identified a schedule
that calls for the Treatment System Design (Scheduled
Action Code 007) to be completed by November 30, 1987.
Effective Date' 10/01/89
Release Number: 1.0
Page' Aji|
-------
Public Water System
Data Capture Form F
PWS O
SUM
ID Nino*
ACTtONCOIX
/.MM M.M00*
(ClOt)
III
BATCH MTf
VARIANCES, EXEMPTIONS & OTHER RELATED DATA
*""" VED RECORD EFFECTIVE DATE EXPIRATION DATE
FY . 10 NUMBER CCMTAUMANT TYPE MO DAY YR MO DAY J^R
(C3001) (CXOO) (CMOS) (C3007)
S£Sf «co«Dyo. T«|SS^T
II 1 M 1 1 1 1 I.I 1 1 1 1 1 1 1 1 I i i I
(CM11) (C3013) (C3018)
["F2"| VE SCHEDULE
"^^" VE ID SCHEDULE
FY ID NUMBER 10 ACTION SCHEDULED DATE
t 1 1 1 1 1 1 . MO , DAY YH
1 1 1 1 1 1 1 | ||| 1)1 | 1 1 I 1 1
111 Ill III 1 1 | 1 1 1
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
1 1 1 1 1 t f 1 ||| III | 1 | 1 1 1
toMci) (dim) (cairn (Otosi
(C3000I
ALTERNATE
PROCESS
1 i i 1 L
(C3017) (C
REASON
1 1 1
Ml«|
ACCOMPLISHED DATE
I |",°iT i 7 i
f I i f '
f fill
i | i I i
(C31B7)
1 ' I
1 ' 1
1 > I
VARIANCES, EXEMPTIONS & OTHER RELATED DATA
..._,...,
COMTAMHANT
RECORD
TYPE
(0001)
STATUS
CODE
U L
EFFECTIVE DATE
MO,. DAY . _YH
EXPIRATION DATE
MO . OAY YB
(C3003)
...._,__ .._
MODIFIED MCL
(C300T)
(C300B)
\.\4\a\o\o\<)(d\db\
(C3013)
TREATMENT
PROCESS
I I I I
(0015)
ALTERNATE
PROCESS
REASON
(CM17)
tcaoifl)
FY
VED
ID NUMBER
SCHEDULE
l^/l
VE SCHEDULE
ACTON SCHEOULEDDATE
1 1 1 1
(C3001)
(C3101)
(C31B3)
I t I 1 I I I
I I I I I I I
I I I I I t i
(C3105)
ACCOMPUSHEOOATE
. MO , DAY . YR
I i |T | i
i . l i l i
I . I i l i
i i l i l i
(C3107)
Effective Date: 1Q/Q1/89
Release Number' 1.0
Pages A52
-------
Sample Data Transfer File Records - FORM F
1-2 3-11 12-18 19-25 26 27-31
| 1 | _ , , ____.
RI158381118600001 I 111C3003t1040
32-71
75-80
1041587
I
F1IR1158381118600001 I |I|C3005|EX
__ | | | | _ | |
10415871
F1IRI158381118600001 I
IIC3007I010187
t-l 1
10415871
F1IRI1583811186000011
IIIC3009I123187
I-I I
10415871
I 1
F1IR1158381118600701 I 111C3003I 1005
041587!
F1IRI158381118600701 I
IHC3005IOT
I-I 1
10415871
F1IRI158381118600701 I
I
IHC3007I083180
I-I I
10415871
H 1
F1IRI15S381118600701 I
UIC3009I 123187
I-I I
I041S87I
I 1
F1IRI158381118600701 I
I
IIC30131.40000000
1041587
I
F1IRI1583811E8600701I
IHC3017I 360
l-l I
1041587!
F1IRI158381118600701 I
| ___|
IIIC3019I007
l-l 1^
10415871
F2IRI158381118600701101
11[C3103 I 28
l-l I
10415871
F21RX1583811I8600701101
IIIC3105I113087
l-l 1
10415871
Effective Date: 10/01/8.9. Release Mumber: 1 .0 Pages fl53
-------
DATA CAPTURE FORM-G
EXAMPLES 1-3 -.
The objective of the examples on this data capture form is to-provide
some indication as to how a primacy agency can store pertinent data,
concerning a specific PUS. for which no data element has been assigned
in FRDS-II. The State Discretionary Data (SOD) entered on FORK G
follows a "Parameter - Value" method of storing such data. It is
essentially the user's "file drawer" in which he/she can store values
for named data items. It is the user's responsibility to assign SDD
names (or codes) that are meaningful to him/her so that subsequent
retrieval of this data will also be meaningful.
EXAMPLE 1
SECTION G1 -. STATE DISCRETIONARY DATA . . .
The user wants to identify the Sanitary Engineer who is
currently responsible for PWS RI1S83811. C1003 is the
named data item (or parameter) Sanitary Engineer, while
the alphanumeric value stored in State Discretionary
Value (C4005) is the name of the Sanitary Engineer -, John
Smith.
EXAMPLE 2
SECTION G1 - STATE DISCRETIONARY DATA
The user wants to record the wholesale population served
for the same PWS. Since this is a numeric field, he/she
enters the named value in C4007 (CUANTITY) instead of
CH005 as above. (This would permit the possibility of ,
future computation on this field which could not be done
if CHOOS were.used to store the value).
EXAMPLE 3
SECTION G1 - STATE DISCRETIONARY DATA
In this example, the user wishes to record the fact that
on May 30, 1987, PUMP-1 was replaced at the PWS. Since
this is a Date value, it is entered in CH009 (DATE). The
SDD NAME chosen to identify this value is* Pump-1
Replacement Date.
Effective Date: 10/01/89
Release Number: 1t.0_
Page: A51
-------
Public Water System
Data Capture Form G
PWS a
ACTION core
IDNvnbv
BATCH DATE
jCIOI)
Foil
1 1 soon
\Q\$/\ \s\h\\
(CM01) (CU03)
gldj
*'
1 1
(C400T)
|G1 I
1 1 SHOD
P-IO laJ ItoJMl
(C4001) (C4001»
UJ
1 1 1
(C4007)
STATE DISCRETIONARY DATA
STATE DISCRETIONARY DATA HADE
*)) (ITIAItfiyi l£ld6l/l/UI£l£f*| 1 1
STATE DISCRETIONARY VALUE
HWl [SIM/in/*fl 1 M 1 1 1 1 1 1
QUANTITY
II I.I 1 1 1 1 i 1 1 1
STA TE DISCRETIONARY DA TA
STATE DISCRETIONARY DATA NAUE
Oluei*lAlLl*l IPIol/'lult Irtl7!/!o !/of 1
STATE DISCRETIONARY VALUE
II 1 1 1 1 1 1 1 1 M 1 1 II I 1
QUANTITY
I/I&10U i I i I I I I I
1 1 1 1 1 1 1
Mill 1 1
DATE
HO DAY Vfl
1 1 1 1 1 1 1
(C40O9)
Mill 1 1
1 1 1 1 1 1 1
DATE
UO DAY Yd
1 1 1 1 i 1 1
\T\ fcifliry
STATE DISCRETIONARY VALUE
II 1 1 1 1 I 1 1 1 1 1 1 1 1 1 1
QUANTITY
II I.I 1 1 1 1 1 1 1 1
Mill 1 1
1 1 1 1 1 1 1
DATE
MO OAY YR
lamaidifiTl
(C4009) '
__.
1 ^"^ 1
L»_J SOOD
1 iLu
(C4001) (C4003)
Lu
(Lilw&j
1 !
(C4007)
STA TE DISCRETIONARY DA TA
STATE DISCRETIONARY DATA NAflE
1 1 M 1 1 1 1 1 1 1 1 1 1 1 1 1
STATE DISCRETIONARY VALUE
1 1 1 1 1 II 1 1 1 1 1 1 II 1 1
QUANTITY
M I.I M II M 1 1
Mill 1 1
M M 1 1 1
SATE
MO OAY Vfl
1 1 1 1 1 i I
Effective Date' 10/01/89
Release Number: 1.0 Page: A55
-------
Sample Data Transfer File Records - FORM G
1-2 3-11 12-18 19-25 26 27-31 . 32-71
31IRI1583811IG01 I 111C4003I SANITARY ENGINEER.
7S-8
|
1081587
G1 IRI1583811IG01 |
| | |
IIIC4005IJOHN SMITH
10815871
G1[RI15S3811IG02 I
UIC4003IWHOLESALE POPULATION
10815871
1 1
61IRI15838111602 i
IIIC4007I150
l-.l 1
10815871
G1IRI1S83811IG03 I
I _________ I ______ I
| _____|
UIC4003I.P.UKP-1 REPLACEMENT DATE
10815871
I 1
G1IRI15838111602 I
IItC(t009l053087
I-I I
10815871
I 1
Effective Date: 10/01/89 Release Number: 1.0 Page: ASS
-------
FRDS-II Edit/Update Processing
January 9, 1989
Effective Dates 10/01/ag Release Humbers 1.0 Pages B1
-------
FRDS- II Edit/Update Processing
The FRDS II Edit program. accepts data in the FRDS II Data Transfer File
-format (DTF) , and validates that the data adheres to the rules defined
the Data Element Dictionary and Data Entry Instructions. Data that
is determined to adequately meet the specifications is passed to the
FRDS-II Update program via the FRDS-II Edited Data File. All rejected
data is recorded in the FRDS-II Edit Error File for processing by the
FRDS-II Error program. Each anomaly detected by the Edit program is
identified within the FRDS-II Edit Error File* unless it is Execution
Fatal to the Edit program. The reason for abnormal terminations and/or
pertinent execution statistics are printed on the Edit Control Totals
report. .
Inputs to the FRDS-II Edit Process
o FRDS-II Data Transfer File
The FRDS-II Data Transfer File (DTF), as defined in the Data Entry
Instructions, contains a single FRDS-II data base item within each
record. The qualifiers required to identify which data base record
is to be effected by the DTF record, a code identifying the effect
desired and a field identifying the data item, also reside in each
DTF record. The FRDS-II Edit program expects to receive the Data
Transfer File in the following sequence »
f Batch Number (major)
t Qualifier 1 (PUS-ID)
* Qualifier 2
f Form ID
f Qualifier 3
f Action Code
t Data Element Kumber (minor)
Refer to the attached Data Transfer File format and Chapter II in
this document for a detailed description of this file.
o FRDS-II Data Element Dictionary Data Base
The FRDS-II Edit program accesses the application's automated Data
Element Dictionary Data base indirectly, for many of the processing
requitments. This information includes the Data Type, Data Item
Format, and code validation tables. This information is obtained
indirectly and is retained internally in the memory space of the
Edit program for the entire duration of execution, precluding the
need for continual access of the FRDS-II Data Element Dictionary
Data Base.
o FRDS-II Data Base
Many of the validations required to verify the integrity of the
input transactions necessitate reviewing the current status of the
FRDS-II Data Base. The FRDS-II Edit program accesses the data base
only to the minimal extent necessary to ensure the correctness of
the data within the DTF Record.
Effective Dates 10/01/89 Release Numbers _1_,_0. Pages
-------
FRDS- II Edit/Update Processing
uts from the FRDS-II Edit Process
FRDS-II Edited Data File
All transactions read from the FRDS-II Data Transfer File and deemed
acceptable for processing by the FRDS-II Update program are written
to the Edited Data File. The record format of this file is also
in the Data Transfer File Format.
o FRDSr-il Edit Error File
Those transactions read from the FRDS-II Data Transfer File and
determined to be unacceptable for application to the FRDS-II Data
Base, are written to the Edit Error File. The format of this file
is the same as the DTF, except that each record in the Edit Error
File that was determined to contain an anomaly is flagged with an
embedded error code. The exact location of the error code is
documented in the attached FRDS-II Edit Error File format specifica-
tion. The brief description of each error condition with the
associated error code* is documented in the attached FRDS-II Edit
Error Conditions.
o FRDS-II Edit Control Totals
The Edit program maintains and prints various counts of DTF records
processed, which facilitates manual quality assurance of the
program's execution. During processing, certain erroneous
situations may be encountered that are sufficiently severe that
continued processing is impossible. If this is the case, the Edit
program records the problem on the Edit Controls Totals Report, then
terminates processing.
Effective Dates 10/01/89
Release Number * 1 . 0
Page:
-------
FRDS- II Edit/Update Processing
DATA TRANSFER FILE
FORMAT SPECIFICATION
Each Data Transfer File zecozd is 80 characters in length and
has the following formats . ..
Definition Positions
Fozn ID 1-2
Cualifiez 1 , 3 - 11
Qualifier 2 - 12-18
Cualifier 3 19-25
Action Code 26
Data Element Number 27-31
Data Value 32 - 71
Resezved for FRDS-II use 72 - 74
Batch Date 75 - 80
I DATA ADDRESS QUALIFIERS I I DATA I
FORM I lACT. IELEM.I DATA
I I I
I FRDS I BATCH I
I ID ! fiUAL 1 I CUAL 2 I CUAL 3 I CODE I NUM. I VALUE I USE I DATE!
I I | I I I I I I 1
1-2 3-11 12-18 19-25 26 27-31 32-71 72-7*» 7S-80
Effective Dates 10/01/89
Release Number1 1.0
Page
B&
-------
FRDS- II Edit/Update Processing
EDIT ERROR FILE
FORMAT SPECIFICATION
Each Edit Exzoz File Record is in the same 80-character format as
the Data Transfer File Format and is defined as follous:
Definition
Form ID
Qualifier 1
Qualifier 2
Qualifier 3
Action Code
Data Element Number
Data Value
t Error Code
Batch Date
I DATA ADDRESS QUALIFIERS I
FORM I I ACT.
ID I QUAL 1 I QUAL 2 I QUAL 3 1 CODE
1 1 1 1
.Positions
1
3
12
19
26
27
32
72
75
(DATA t
IELEM. I
I NUM. 1
1 1
- 2
- 11
- 18
- 25
- 31
- 71
- 7«*
- SO
DATA
VALUE
I II
I ERROR I BATCH I
(CODE I DATE I
I I I
1-2
3-11
12-18
19-25
26
27-31
32-71
72-74 75-80
Effective Date ' 10/01/89
Release Number: 1,0
Page'
B£
-------
------- |