United States .'Office of Water ' EPA 812-B-93-003
Environmental Protection (WH-550) January 1993
Agency
vVEPA Federal Reporting Data
System (FRDS-II) Data
Element Dictionary
Printed On'ftdoybJed'Paper
-------
SDC-0055-031-LN-2003
January 31, 1993
FEDERAL REPORTING DATA SYSTEM (FRDS-II)
DATA ELEMENT DICTIONARY
CONTRACT NO. 68-W1-0055
DELIVERY ORDER NO. 0055-031
Prepared for:
United States Environmental Protection Agency
Office of Ground Water and Drinking Water
401 M Street, SW.
Washington, D.C. 20460
Delivery Order Project Officer: Abraham I. Siegel
Prepared by:
EPA Systems Development Center
(A Contractor Operated Facility)
Science Applications International Corporation
200 North Glebe Road, Suite 300
Arlington, VA 22203
-------
SXS, SYSTEM 2000, are re&iS^red trademarks of SAS Institute Inc., Gary, NC, USA.
-------
FRDS-E DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Preface
This document, the Federal Reporting Data System (FRDSrll) Data Element Dictionary
.(D.E.D), contains comprehensive information about, and related to, each data element
maintained in the Federal Reporting Data System (FRDS-II) SYSTEM 2000™ Data Base.
The current release of the D.E.D is always noted in the Release Log which immediately
follows this preface. Pages within this document having the same release number always
represent information taken from a common version of the data source. Pages containing
different release numbers, however, may contain incompatibilities since they reflect
information taken at varying points in time from versions of the data source which may be
dissimilar.
Drinking water programmatic information contained in the D.E.D includes:
• Descriptions, edit criteria and/or acceptable values, and related comments for each
data base record and data element.
• What must be specified in order to insert, modify, or delete public water system
inventory, violation, enforcement action, milestone, variance and exemption and other
related data, and sample data and records into the FRDS-II Data Base (i.e.,
registration requirements).
• What must be specified for a public water system to be considered grant eligible.
• The source(s) of all FRDS-II data.
Technical information contained in the D.E.D includes:
• Data element numbers and names.
• Records and families to which the data elements belong.
• The data capture form identification, data qualifier(s), and the maximum length of
data that may be entered via the FRDS-II data transfer file.
• Data characteristics, including data type, picture, access, and data category.
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Other information of general interest contained in the D.E.D includes:
• A data base structure chart and the definition of the FRDS-n Data Base..
• Data element number-name cross-reference lists.
• Lists of acceptable codes and values.
• A reference section.
• A glossary of technical and drinking water programmatic terms.
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
Federal Reporting Data System (FRDS-II)
Data Element Dictionary
Release Log
Note: All change notices/descriptions that relate to the FRDS-n Data Element Dictionary should be
filed immediately following the Release Log.
Release
Number
1.00
2.00
Effective
Date
10/01/89
1/31/93
Description of Release
Initial Release of Production Documentation
Revised Release of Production Documentation
_
Effective Date: 1/31/93
Release: 2.00
-------
FRDS il DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
Change Notice
Release 2.00 of the Federal Reporting Data System (FRDS-n) Data Element Dictionary is
intended to be a full replacement for the Release 1.00 version of this documentation. Some
sections, however, are not being replaced due to factors discussed below. In those cases,
where ihe user feels the previous information is still of value to him/her, he/she can insert
those sections in the new document, as the original section references I through vm have
been retained in Release 2.00.
Section I. FRDS-II Data Base Definition is a total replacement.
Section II. Data Element Descriptions a total replacement.
Section III. Quick Reference is a total replacement.
Section IV. This Section contains FRDS 1.5 to FRDS-II Comparison Tables which are.
considered to be of limited value at this time and, consequently, has not been
included in this document.
Section V. This Section contains FRDS 1.5 to FRDS-II Conversion Rules which are
considered to be.of limited value at this time and, consequently, has not been
included in this document.
Section VI. Lists of Acceptable Code Values with Associated Descriptions has been
regenerated and, for the most part are included in this change release. Due to
the large volume of essentially unchanged pages involved with Table C427
(Hydrological Unit Codes) and C509 (FIPS County Codes), however, these
Tables have not been totally replaced. Section VI page numbers VI-122
through Vl-384 have been retained for the former while VI-512 through VI-
638 have been retained for the latter. In several instances, substantive changes
in the CS09 Table have necessitated the inclusion of these changed pages in
this Section.
Section VII. The References Section has been replaced by a list of documents readily
available from EPA Regional and/or Headquarters offices. Users are urged to
use these references in lieu of those found in Release 1.00, since much of the
older reference material has been outdated and may no longer be valid.
Section VIII. The Glossary is a total replacement.
Effective Date: 1/31/93
Release: 2.00
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31, 1993
Contents
Section I FRDS-n Data Base Definition 1-1
A. Data Base Structure Chart 1-2
B. Data Base Definition 1-3
Section n Data Element Descriptions n-1
Introduction n-1
CO STATErSUMMARY H-8
C100 PWS-SUMMARY H-20
C300 PWS-ADDRESS-DATA n-60
C400 PYVS-SOURCE-ENTTTY-INFO H-69
C480 PWS-SE-TREATMENT-DATA 11-88
C500 PWS-GEOGRAPfflC-AREAS-SERVED ' O-92
C600 PWS-SERVICE-AREAS n-103
C700 PWS-ON-SITE-VISITS n-io?
C800 PWS-MILESTONE-EVENTS H-lll
C900 PWS-fflSTORY H-119
C1000 NON-COMPLIANCE-DATA 11-124
C1100 VIOLATION-DATA H-126
C1180 VIO-ENFORCEMENTS . . . : H-145
C1200 ENFORCEMENT-DATA D-149
C1280 ENF-VIOLATIONS D-158
C1300 NCP-CNTL-NODE D-166
C1350 NON-COMPLIANCE-PROFILE 11-167
C2000 SAMPLE-DATA-CONTROL-NODE 11-177
C2100 SAMPLE-DATA H-178
C3000 VARIANCE-EXEMPTION-DATA ' H-185
C3100 VE-SCHEDULE H-203
C4000 STATE-DISCRETIONARY-DATA H-208
C4050 DBA-DATA . . . ; 11-214
Section HI Quick Reference ni-1
A. Data Base Structure Chart III-2
B. Comprehensive Data Element Table ni-3
C. Name to Number Cross Reference III-8
D. Data Element Requirements ID-10
Effective Date: 1/31/93 Release: 2.00 i
-------
FRDS-n DATA ELEMENT DICTIONARY SDC4Q55-031-LN-2003
January 31. 1993
Section IV FRDS 1.5 Versus FRDS-n Comparison Tables IV-1
Section V FRDS 1.5 to FRDS-n Conversion Rules V-l
Section VI Lists of Acceptable Code Values with Associated Descriptions VI-1
Section VII References VH-1
Section VIII Glossary of Technical and Drinking Water Programmatic Terms .... VIII-1
Effective Date: 1/31/93 Release: 2.00 ii
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section I
FRDS-II Data Base Definition
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section I FRDS-II Data Base Definition
This section of the FRDS-II Data Element Dictionary includes:
• FRDS-n Structure Chart as of December 31, 1992
• FRDS-II Data Base Definition
The FRDS-II Structure Chart
Chart IA on page 1-2 depicts the data base architecture of FRDS-n under the SYSTEM
2000™ (S2K) Data Base Management System (DBMS). The FRDS-n Data Base is a
hierarchically arranged set of records that contain information relating to the Public Water
Supply Supervision (PWSS) Program. In-depth information about the data base structure is
included in Section VIII, Glossary of Technical and Drinking Water Programmatic Terms,
under Data Base, Data Base Family, and Data Base Record.
Each block on the structure chart represents a data base record, labeled with its number,
family, name, and prefix.
Users will also receive a revised FRDS-n Structure Chart (Release 2.10) which includes
detailed information concerning this structure. The top portion of each block on the detailed
chart contains the data base record number and name, the data capture form ID associated
with the record's data, and its data base family. Below the data base record name and
number are the data elements contained within each data base record.
In the expanded chart, each data element contains the following attributes:
• Data Element Number
• Data Element Name
• Data Type
• Maximum Length
• Data Base Registration Requirement (if any)
• Grant Eligibility Requirement (if any)
• Whether Generated/Not Generated by the FRDS-H System
Effective Date: 1/31/93 Release: 2.00 Page: I - 1
-------
I A. FRDS-II Structure Chart
B!
R1
P.
I
Federal Reporting Data System (FRDS-II)
Structure Chart
December 1. 1992
UnM
GEOGRAPHIC
ARCAS
stRviD
PWSOA-
SERVICE
ARIAS
PWSSEKV
CtOO 6
HISTORY
C1200 •
INFORCEMINT
DATA
JHf-
CI2M I
UNK TO
VIOLATION
CNF-IINK
C4000 II
STATf
DISCRETION
ARV DATA
SOD-
C4060 IJ
DBA DAI A
UOtNO
n
K>
-------
FRDS-O DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
FRDS-II Data Base Definition
The FRDS-II Data Base Definition is a detailed description of the structure of the FRDS-II
Data Base. It lists, in table form, each data element by:
• Number and Name.
• Whether the data element is KEY (by default, left blank) or NON-KEY (a term
applicable when formulating SYSTEM 2000 locate statements).
• Data Type.
Describes the SYSTEM 2000 data type for the data element being described. Valid
SYSTEM 2000 data types are: CHARACTER, DATE, TEXT, INTEGER, and
DECIMAL.
• Picture.
Describes the length and format of the data element being described. The letter or
number outside the parentheses indicates the format (X = alphanumeric, 9 =
numeric) and the number inside the parentheses represents the length. The Data Base
definition contains the optimum size for all character (alphanumeric) fields.
Through an overflow capability, System 2000 accommodates maximum sized fields in
excess of the size shown in the definition. In FRDS-0, all CHARACTER, X(4),
fields can accommodate up to 40 characters of input data.
• Record Identification Number.
Section n, FRDS-II Data Element Description Notes, provides detailed descriptions of the
data in the Data Base Definition.
Effective Date: 1/31/93 Release: 2.00 Page: I - 3
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-20C
January 31, 199j
Section 1 B.
0* STATE-SUMMARY
1* ST-REGION-CODE
3* ST-STATE-CODE
4* ST-IND-RES-CODE
5* ST-PRIMACY-FLAG
7* ST-ANY-DATA-LAST-UPDATE
9* ST-INV-LAST-UPDATE
13* ST-VIO-LAST-UPDATE
15* ST-ENF-LAST-UPDATE
29* ST-SAMPLE-LAST-UPDATE
17* ST-VE-LAST-UPDATE
19* ST-RECON-FLAG
100* PWS-SUMMARY
101* PWS-ID
102* PWS-GRANT-ELIGIBLE
103* PWS-STATUS
105* PWS-TYPE
107* PWS-ACTIV1TY-FLAG
109* PWS-HI STORY-FLAG
111* PWS-SYSTEM-BEGIN-YYMM
113* PWS-DEACT-YYMM
115* PWS-POP-CATEGORY
117* PWS-RETAIL-POP-SERVED
119* PWS-PRIMARY-SOURCE
121* PWS-PCT-SURFACE
123* PWS-PCT-GROUND
125* PWS-PCT-PUR-SURFACE
127* PWS-PCT-PUR-GROUND
129* PWS-TREATMENT-CLASS
131* PWS-SYSTEM-NAME
133* PWS-SYSTEM-ADDR-LINE-1
135* PWS-SYSTEM-ADDR-LINE-2
137* PWS-SYSTEM-CITY
139* PWS-SYSTEM-STATE
141* PWS-SYSTEM-ZIP
143* PWS-PHONE
145* PWS-METERS
147* PWS-SERVICE-CONNECTIONS
149* PHS-AVG-OAILY-PROD
151* PWS-TOT-DESIGN-CAPACITY
153* PWS-TOT-EMERGENCY-PROD
155* PHS-TOT-STORAGE-CAPACZTY
157* PWS-MAX-DAILY-PROD
159* PWS-SEASON-BEGIN-MMOD
161* PWS-SEASON-END-MMDD
163* PWS-OWNER-TYPE
165* PWS-REGULATING-ENTITY
167* PWS-INV-LAST-UPDATE
168* PWS-INSERT-DATE
169* PWS-ANY-DATA-LAST-UPDATE
171* PWS-RECON-FLAG
173* PWS-FYNN-TRACKER
Data Base Definition
( SR
( INT 9(2)
( CHAR X(2)
( CHAR X(7)
( CHAR X(l)
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY DATE
( CHAR X(l)
( SR
( CHAR X(9)
CHAR X(l)
CHAR X(3)
CHAR X(l)
CHAR X(l)
CHAR X(l)
(NON-KEY INT 9(4)
(NON-KEY INT 9(4)
( CHAR X(l)
(NON-KEY INT 9(8)
( CHAR X(l)
(NON-KEY INT 9(3)
(NON-KEY INT 9(3)
(NON-KEY INT 9(3)
(NON-KEY INT 9(3)
( CHAR X(l)
(NON-KEY CHAR X(30)
(NON-KEY CHAR X(4)
(NON-KEY CHAR X(30)
( CHAR X(15)
(NON-KEY CHAR X(2)
( CHAR X(5)
(NON-KEY CHAR X(10)
(NON-KEY INT 9(7)
( INT 9(7)
(NON-KEY INT 9(10)
(NON-KEY INT 9(10)
(NON-KEY INT 9(10)
(NON-KEY INT 9(10)
(NON-KEY INT 9(10)
(NON-KEY INT 9(4)
(NON-KEY INT 9(4)
( CHAR X(l)
(NON-KEY CHAR X(l)
( DATE
(NON-KEY DATE
( DATE
( CHAR X(l)
(NON-KEY CHAR X(60)
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN-
•IN.
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
):
):
):
):
):
):
):
:
:
•
•
:
•
):
100):
100):
100).:
100.) :.
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
100):
Effective Date: 1/31/93
Release: 2.00
Page: I -
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
Section 1 B. Data Base Definition (continued)
300*
301*
303*
305*
307*
309*
311*
313*
315*
400*
401*
403*
405*
407*
409*
411*
413*
415*
417*
418*
419*
421*
423*
425*
426*
427*
429*
431*
480*
481*
483*
485*
500*
501*
503*
505*
507*
508*
509*
511*
513*
515*
517*
600*
601*
603*
605*
PWS-ADDRESS-DATA
PWS-AD-ID
PWS-AD-TYPE
PWS-AD-NAME
PWS-AD-ADDR-LINE-1
PWS-AD-ADDR-LINE-2
PWS-AD-CITY
PWS-AD-STATE
PWS-AD-ZIP
PWS-SOURCE-ENTITY-INFO
PWS-SE-ID
PWS-SE-NAME
PWS-SE-RECORD-TYPE
PWS-SE-CODE
PWS-SE-AVAILABILITY
PWS-SE-SELLER-PWS-ID
PWS-SE-DATA-ORIGIN
PWS-SE-LATITUDE
PWS-SE-LONGITUDE
PWS-SE-MERIDIAN-NAHE
PWS-SE-TOWNSHIP
PWS-SE-RANGE
PWS-SE-SECTION
PWS-SE-QTR-SECTION
PWS-SE-QTR-QTR-SECTION
PWS-SE-RIVER-REACH-NUM
PWS-SE-ON-REACH
PWS-SE-REACH-MILES
PWS-SE-TREATMENT-DATA
PWS-SE-TREATMENT-ID
PWS-SE-TREATHENT-OBJECTIVE
PWS-SE-TREATMENT-PROCESS
PWS-GEOGRAPHIC-AREAS-SERVED
PWS-GA-ID
PWS-GA-ADMIN-REGION
PWS-GA-ADKIN-DIST
PWS-GA-CONGRESSIONAL-DIST
PWS-GA-STATE-COUNTY-CODE
PWS-GA-FIPS-COUNTY-CODE
PWS-GA-MSA-CODE
PWS-GA-CITY-SERVED
PWS-GA-IND-RES-CODE
PWS-GA-DATA-ORIGIN
PWS-SERVICE-AREAS
PWS-SERV-ID
PWS-SERV-CATEGORY
PWS-SERV-PRIMARY-FLAG
(
(NON-KEY
(
(NON-KEY
(NON-KEY
(NON-KEY
(
(NON-KEY
(
{
(NON-KEY
(NON-KEY
(
(
(NON-KEY
•(NON-KEY
(NON-KEY
(
(
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(
(NON-KEY
(NON-KEY
(
(NON-KEY
(
(
(
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(NON-KEY
(
(
(
(NON-KEY
(
(NON-KEY
(
(
SR
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
SR
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
INT
INT
CHAR
CHAR
CHAR
INT
CHAR
CHAR
CHAR
CHAR
DEC
SR
INT
CHAR
INT
SR
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
SR
INT
CHAR
CHAR
9(1)
X(l)
X(30)
X(4)
X(30)
X(15)
X(2)
X(5)
9(3)
X(15)
X(l)
X(l)
X(l)
X(9)
X(l)
9(6)
9(7)
X(4)
X(4)
X(4)
9(2)
X(2)
X(2)
X(8)
X(l)
9(4). 9(2)
9(2)
X(D
9(3)
9(2)
X(2)
X(2)
X(2)
X(3)
X(3)
X(4)
X(15)
X(5)
X(l)
9(2)
X(2)
X(l)
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
IN
100):
300):
300):
300):
300):
300):
300):
300):
300):
100):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
400):
480):
460):
480):
100):
500):
500):
500):
500):
500):
500 )»
500):
500):
500):
500):
100):
600):
600):
600):
Effective Date: 1/31/93
Release: 2.00
Page: 1-5
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-200
January 31, 1993
Section 1 B. Data Base
700* PWS-ON-SITE-VISITS
701* PWS-VISIT-ID
703* PWS-VISIT-DATE
705* PHS-VXSIT-REASON
800* PWS-MILESTONES-EVENTS
801* PWS-MILESTONE-ID
803* PWS-MILESTONE-DATE
805* PWS-MILESTONE-CODE
809* PWS-MILESTONE-ORIGIN
811* PWS-MILESTONE-ZNSERT-DATE
813* PWS-MILESTONE-COMMENT
815* PWS-MZLESTONE-VALUE
900* PWS-HZSTORY
901* PWS-HIST-CHANGED-ITEM
903* PWS-HIST-CHANGE-DATE
905* PWS-HIST-OLD-VALUE
907* PWS-HIST-NEW-VALUE
1000* NON-COMPLIANCE-DATA
1001* NCD-RECON-FLAG
1100* VIOLATION-DATA
1101* VIO-ID
1103* VIO-CONTAMINANT
1105* VIO-TYPE
1107* VIO-COMP-PERIOD-BEGIN-DATE
1109* VIO-COMP-PERIOD-END-DATE
1111* VIO-COMP-PERIOD-MONTHS
1115* VIO-AWARE-DATE
1117* VIO-INSERT-DATE
1121* VIO-ANALYSIS-METHOD
1123* VIO-ANALYSIS-RESULT
1125* VIO-MCL-VIOLATED
1127* VIO-SAMPLES-REQUIRED
1129* VIO-SAMPLES-TAKEN
1131* VIO-MAJOR-VIOLATION-FLAG
1133* VIO-LAST-UPDATE
1135* VIO-FY
1137* VIO-DATA-ORIGIN
1143* VIO-SE-ID
.1180* VIO-ENFORCEMENTS
1181* VIO-LINK-ENF-ID
1183* VIO-LINK-ENF-DATE
.U85 * VIO-LINK-FOLLOW-UP-ACTION
Definition (continued)
( SR
(NON-KEY INT 9(2)
(NON-KEY DATE
( CHAR X(2)
( SR
(NON-KEY CHAR X(4)
(NON-KEY DATE
( CHAR X(4)
(NON-KEY CHAR X(l)
(NON-KEY DATE
(NON-KEY CHAR X(4)
(NON-KEY DEC 9 (7). 9 (8)
( SR
( CHAR X(4)
(NON-KEY DATE
(NON-KEY CHAR X(20)
(NON-KEY CHAR X(20)
( SR
( CHAR X(l)
( SR
(NON-KEY CHAR X(7)
( CHAR X(4)
( CHAR X(2)
( DATE
( DATE
(NON-KEY INT 9(3)
( DATE
( DATE
(NON-KEY CHAR X(3)
(NON-KEY DEC 9(7). 9(8)
(NON-KEY DEC 9(7). 9(8)
(NON-KEY INT 9(3)
(NON-KEY INT 9(3)
( CHAR X(l)
( DATE
( INT 9(2)
(NON-KEY CHAR X(l)
(NON-KEY INT 9(3)
( SR
(NON-KEY CHAR X(7)
(NON-KEY DATE
( CHAR X(3)
IN 100):
IN 700):
IN 700):
IN 700):
IN 100):
IN 800):
IN 800 ) :
IN 800):
IN 800):
IN 800):
IN 800):
IN 800):
IN 100):
IN 900):
IN 900):
IN 900):
IN.. ;900):
IN.. -100):
IN* 10.00):
IN 1000):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100) :
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1100):
IN 1180):
IN 1180):
IN 1180):
Effective Date: 1/31/93
Release: 2.00
Page: I -
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
Section 1 B. Data Base
1200* ENFORCEMENT-DATA
1201* ENF-ID
1203* ENF-ACTZON-DATE
1205* ENF-FQLLOW-UP-ACTION
1207* ENF-LAST-UPDATE
1209* ENF-FY
1211* ENF-DATA-ORIGIN
1213* ENF-ZNSERT-DATE
1215* ENF-COMMENT
1280* ENF-VZOLATZONS
1281* ENF-LINK-VZO-ZD
1283* ENF-LZNK-RANGE-BEGZN
1285* ENF-LZNK-RANGE-END
1287* ENF-LZNK-PERZOO-BEGZN
1289* ENF-LZNK-VZO-TYPE
1291* ENF-LZNK-CONTAMZNANT
1293* ENF-LINK-TYPE
1300* NCP-CNTL-NODE
1350* NON-COMPLIANCE-PROFILE
1351* NCP-HZNDOW-BEGZN-YYMM
1353* NCP-WINDOW-MONTHS
1355* NCP-WINDOW-PURPOSE
1357* NCP-CONTAMZNANT
1359* NCP-MCL-VIOLATIONS
1361* NCP-MCL-DURATZON
1363* NCP-MON-VIOLATIONS
1365* NCP-MON-DURATION
1367* NCP-ENF-ACTZONS
2000* SAMPLE-DATA-CNTL-NODE
2100* SAMPLE-DATA
2101* SAMPLE-ZD
2103* SAMPLE-BEG ZN-DATE
2105* SAMPLE-END-DATE
2107* SAMPLE-CONTAMINANT
2111* SAMPLE-ANALYSIS-RESULT
2117* SAMPLE-FY
2119* SAMPLE-SE-ZD
3000* VARIANCE-EXEMPTION-DATA
3001* VE-ID
3003* VE-CONTAMINANT
3005* VE-RECORD-TYPE
3007* VE-EFFECTZVE-DATE
3009* VE-EXPIRATION-DATE
3011* VE-STATOS-OODE
3013* VE-MOD-MCL
3015* VE-TREATMENT-PROCESS
3017* VE-ALT-PROCESS
3019* VE-REASON-CODE
Definition (continued)
( SR
(NON-KEY CHAR X(7)
DATE
CHAR X(3)
DATE
ZNT 9(2)
CHAR X(l)
(NON-KEY DATE
(NON-KEY CHAR X(4)
( SR
(NON-KEY CHAR X(7)
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY CHAR X(2)
(NON-KEY CHAR X(4)
( CHAR X(l)
( SR
( SR
( ZNT 9(4)
(NON-KEY ZNT 9(3)
(NON-KEY CHAR X(4)
( CHAR X(4)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
( SR
( SR
(NON-KEY CHAR X(5)
(NON-KEY DATE
(NON-KEY DATE
( CHAR X(4)
(NON-KEY DEC 9(7). 9(8)
( ZNT 9(2)
(NON-KEY ZNT 9(3)
( SR
(NON-KEY CHAR X(7)
(NON-KEY CHAR X(4)
( CHAR X(2)
(NON-KEY DATE
(NON-KEY DATE
(NON-KEY CHAR X(l)
(NON-KEY DEC 9(7). 9(8)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
(NON-KEY ZNT 9(3)
ZN 1000):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1200):
ZN 1280):
ZN 1280):
ZN 1280):
ZN 1280):
ZN 1280):
ZN 1280):
ZN 1280):
ZN 1000):
ZN 1300):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 1350):
ZN 100):
ZN 2000):
ZN 2100):
ZN 2100):
ZN 2100):
ZN 2100):
ZN 2100):
ZN 2100):
ZN 2100):
ZN 100):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
ZN 3000):
Effective Date: 1/31/93
Release: 2.00
Page: 1-7
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-20C
January 31, 1993
Section 1 B. Data
3021* VE-LAST-UPDATE
3023* VE-FY
3025* VE-DATA-ORIGIN
3027* VE-VUL-FLAG
3029* VE-ALT-MON-FREQ
3031* VE-SE-ID
3033* VE- INSERT-DATE
3100* VE-SCHEDULE
3101* VE-SCHED-ZD
3103* VE-SCHED-ACTION
3105* VE-SCHED-DATE
3107* VE-SCHED-ACCOMP-DATE
4000* STATE-DISCRETIONARY-DATA
4001* SDD-ID
4003* SDD-NAME
4005* SDD-VALUE
4007* SDD-QUANTZTY
4009* SDD-DATE
4050* DBA-DATA
4051* DBA-NAME
4053* DBA-VALUE
4055* DBA-DATE
4057* DBA-COMMENT
4059* DBA-ID
4061* DBA-SNC-CRITERIA
Base Definition (continued)
( DATE
( INT 9(2)
(NON-KEY CHAR X(l)
(NON-KEY CHAR X(l)
(NON-KEY INT 9(3)
(NON-KEY INT 9(3)
(NON-KEY DATE
( SR
(NON-KEY INT 9(2)
(NON-KEY CHAR X(2)
(NON-KEY DATE
(NON-KEY DATE
( SR
(NON-KEY INT 9(3)
( CHAR X(4)
(NON-KEY CHAR X(4)
(NON-KEY DEC 9(7). 9(8)
(NON-KEY DATE
( SR
( CHAR X(15)
( CHAR X(4)
( DATE
(NON-KEY CHAR X(4)
(NON-KEY INT 9(3)
(NON-KEY CHAR X(4)
IN 3000):
IN 3000):
IN 3000):
IN 3000):
IN 3000):
IN 3000):
IN 3000):
IN 3000):
IN 3100):
IN 3100):
IN 3100):
IN 3100) :
IN 100):
IN 4000):
IN 4000):
IN 4000):
IN .4000):
IN. 4000) :
IN 100):
IN 4050):
'IN. 4050):
IN 4050):
IN 4050):
IN 4050):
IN 4050):
Effective Date: 1/31/93
Release: 2.00
Page: I-
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section II
Data Element Descriptions
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Section II Data Element Descriptions
Introduction
Section n contains detailed descriptions of the FRDS-H Data Base Records (schema records)
and data elements in the FRDS-II Data Base. These descriptions are presented on pages
entitled, "FRDS-H Data Element Description".
This introduction is intended to provide a description of the terms used on these pages.
Sample pages, II-3 and D-4, have each term annotated as NOTE 1, NOTE 2, etc. An
explanation of these notes follows (pages H-5 through H-8). When the "FRDS-n Data
Element Description" pages are used to describe Data Base Records, there will be some
differences in format. These differences will be identified where applicable.
It should be noted that there are certain terms used on these pages (e.g., "Data Base
Family"), that usually are not of concern to most staff personnel actually performing data
entry. However, there is general terminology used throughout Section n that DOES apply to
both data entry and end users alike. When used in the "Description", "Edit
Criteria/Acceptable Values" and "Comments" portions of the Data Element Description
pages, the following terms have particular significance:
MUST: When the term "must" (i.e., "must be specified" or "must be valued") is used in
conjunction with a particular data element, it implies that an omitted or incorrect data
element will cause rejection by the FRDS-II System. Rejection of the data element in
question would always be the case and that, in turn, could cause the rejection of an entire
Data Base Record.
SHOULD: When the term "should" (i.e., "should be specified" or "should be valued") is
used in conjunction with a particular data element, it implies that while a data element is
desirable for inclusion into the FRDS-II Data Base, its validity is not checked and no action
is taken for its omission.
WILL AUTOMATICALLY BE: When the phrase "will automatically be" is used in
conjunction with a particular data element, it implies that the FRDS-II System will determine
certain, data values during its normal course of operation. The value of other existing data
elements or events are considered when determining such data element values. An example
of an automatically valued data element is C115 (PWS-POP-CATEGORY), which is based
upon the value of C117 (PWS-RETAIL-POP-SERVED).
For additional information and definitions, see Section vm, "Glossary of Technical and
Drinking Water Programmatic Terms."
Effective Date: 1/31/93 Release: 2.00 Page: n - 1
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-200
January 31, 1993
FRDS-II Data Base Record Description • Number: NOTE 1
Name: NOTE 2
Description:
NOTE 3
• Data Characteristics:
Data Type: RECORD Data Base Family: NOTE 8
Parent Record: NOTE 7
Record Contents:
NOTE 16
Comments:
NOTE 17
NOTE 18
Effective Date.- NOTE 19
Release Number: NOTE 20 Page: NOTE 21
Effective Date: I/31/93
Release: 2.00
Page: II -
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
FRDS-n Data Element Description Number: NOTE 1
Name: NOTE 2
Description:
NOTE 3
Source:
Data Characteristics
FRDS-ll Data Transfer File
Form ID: NOTE 4
Data Qualifien: NOTES
Maximum Length: NOTE 6
Data Base Record:
Data Base Family:
Data Category:
Data Type:
Picture:
NOTE 7
NOTE 8
NOTE 9
NOTE 1O
NOTE 11
Registration Requirement: NOTE 12
Grant Requirement: NOTE 13
Access: NOTE 14
Code Table ID: NOTE IS
• Edit Criteria:
Must be specified when ... NOTE is
When specified, ...
[E ]
NOTE 16A
• Comments:
NOTE 17
!
! NOTE 18
Effective Date: NOTE 19
Release Number: NOTE 20
Page: NOTE 21
Effective Date: 1/31/93
Release: 2.00
Page: n - 3
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-200
January 31, 1993
FRDS-II Data Element Description Notes
NOTE 1: (Number)
A number assigned to a FRDS-II Data Element or Data Base Record.
NOTE 2: (Name)
The name assigned to a FRDS-n Data Element or Data Base Record.
NOTE 3: (Description)
A narrative that describes the FRDS-II Data Element or Data Base Record.
NOTE 4: (FRDS-n Transfer File, Form ID)
A field in the FRDS-II Data Transfer File Record used for the Form ID of the
FRDS-II Data Capture Form that contains the data element being described. (Not
applicable for Data Base Records.)
NOTE 5: (FRDS-n Transfer File, Data Qualifiers)
The name(s) of the FRDS-II Data Base Record IDs necessary in the FRDS-II Data
Transfer File Record, to uniquely identify the Data Base Record containing the
described data element. (Not applicable for Data Base Records.)
NOTE 6: (FRDS-II Transfer File, Maximum Length)
The maximum number of positions allowed in the FRDS-II Data Transfer File record
for the data element being described. In some cases, this may be larger than the
picture size as described in NOTE 11. If this is the case and the data type is <
CHARACTER, FRDS-II will accommodate the larger size. (Not applicable for Data
Base Records.)
NOTE 7: (Data Base Record/Parent Record)
The SYSTEM 2000 component number and name of the FRDS-II Data Base Record
in which the data element being described resides. For Data Base Records, this
descriptor contains the number and name of the immediate structural ancestor Data
Base Record.
Effective Date: 1/31/93 Release: 2.00 Page: II - 4
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
NOTE 8: (Data Base Family)
A number that indicates the set of FRDS-II Data Base Records the data element
being described belongs to. This information is useful to the FRDS-II user when
requesting certain types of reports or formulating complex queries.
NOTE 9: (Data Category)
A 2-digit code used to classify a data element. See Section VII, "References" in the
FRDS-n Data Element Dictionary for specific Category Code definitions. (Not
applicable for Data Base Records.)
NOTE 10: (Data Type)
Describes the SYSTEM 2000 data type for the data element being described. Valid
SYSTEM 2000 data types are: CHARACTER, DATE, TEXT, INTEGER, and
DECIMAL. DATE is stored in MMDDYY format and when used for retrieval,
should be entered without slashes. For example, June 20, 1988 should be entered
062088. For Data Base Records, the data type will contain RECORD. See Section
VIII - "Glossary of Technical and Drinking Water Programmatic Terms".
NOTE 11: (Picture)
Describes the length and format of the data element being described. The letter or
number outside the parentheses indicates the format (X=alphanumeric, 9=numeric)
and the number inside the parentheses represents the length. The following examples
are given:
• An alphanumeric data element of 30 characters would be represented as X(30).
• A 5-digit whole number would be represented as 9(5).
• A 7-digit number with 2 decimal places would be represented as 9(5).9(2).
• A DATE would be represented as 9(6) in the format of MMDDYY.
In FRDS-II, any alphanumeric field that is defined as over four positions in length can
accommodate up to 40 characters of input data. See Section VIII - "Glossary of Technical
and Drinking Water Programmatic Terms." (Not applicable for Data Base Records.)
Effective Date: 1/31/93 Release: 2.00 Page: II - 5
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-200
January 31, 1993
NOTE 12: (Registration Requirement)
A number that indicates one of four types of data entry requirements associated with
the FRDS-II System. See Section VIII - "Glossary of Technical and Drinking Water
Programmatic Terms".
NOTE 13: (Grant Requirement)
Indicates whether the data element or Data Base Record being described is required
for the PWS to be included in the calculation of the State's Drinking Water Grant.
There are three values that appear here. They are as follows:
YES The data must always be provided.
COND Data COULD be required, depending upon how another data element is
valued. An example of this would be; C411 (PWS-SE-SELLER-PWS-ID) is
required when a source of water is a purchased source.
NO This data element is not considered in the calculation of the State's Drinking
Water Grant.
NOTE 14: (Access)
Used to indicate whether the data element being described is a data base key or
non-key item. Key items are those items for which SYSTEM 2000 will build and
maintain indexes. SYSTEM 2000 makes use of those indexes to access appropriate
Data Base Records for the user. An item for which an index is created is called a
KEY item, implying that it provides easy access to the Data Base Records containing
its values. When an item is declared NON-KEY, values for that item are not
indexed although they can be used when accessing data in conjunction with KEY
items. (Not applicable for Data Base Records.)
NOTE 15: (Code Table ID)
Section VI contains comprehensive lists (i.e., tables) of acceptable code values along
with each code's description and other related comments, as appropriate, for each of
the FRDS-II data elements that have code values.
Effective Date: 1/31/93 Release: 2.00 Page: II -
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
NOTE 16: (Edit Criteria/Acceptable Values/Record Contents)
This is used to specify the actual acceptable values and/or the name of a table that
contains-the acceptable values, for the data element being described. Record
Contents is used to list all data elements that are contained in the Data Base Record
being described.
NOTE 16A: (Edit/Update Error Codes)
The three-character error code that would appear on the FRDS-II Edit/Update Error
Report when the edit criteria rules have been violated. For detailed information on
edit/update error codes, see Data Correction: The Trouble Shooter's Guide, which
is Appendix B of the FRDS-H Data Entry Instructions, Release 2.00.
NOTE 17: (Comments)
Contains any comments pertinent to the data element or Data Base Record being
described.
NOTE 18: (Vertical Bar)
Users will note that a vertical bar may appear in the left margin of some pages.
This bar is used to identify the location of changes which were made since the prior
release of the FRDS-II Data Element Dictionary.
NOTE 19: (Effective Date)
The date that this page of the FRDS-H Data Element Dictionary, became effective.
NOTE 20: (Release Number)
The number of the release of this section of the FRDS-H Data Element Dictionary.
NOTE 21: (Page)
The page number.
Effective Date: 1/31/93 Release: 2.00 Page: II - 7
-------
FRDS-II Data Base Record Description Number- CO
Name: STATE-SUMMARY
• Description
A SYSTEM 2000 data base record Identification number and name.
The CO. STATE-SUMMARY, data base record contains data elements that identity and characterize an Individual State's Inventory, violation.
enforcement action, sample, and variance/exemption/other data.
The FRDS-II Data Base has one STATE-SUMMARY data base record lor each d the fallowing governmental jurisdictions:
the 50 United Slates
the District of Columbia
the U.S. Possessions (American Samoa. Guam, the Northern Mariana Islands. Palau. the
Commonwealth of Puerto Rico, and the U.S. Virgin Islands)
the Freely Associated States (Federated States of Micronesia, and the Marshall Islands)
8 EPA regions in which the region has primacy over Indian reservations
Additionally, the FRDS-II Data Base may have one STATE-SUMMARY data base record tor each Indian reservation that has been granted
primary enforcement responsibility.
• Data Characteristics
Data Type. RECORD Data Base Family. All Parent Record.
• Record Contents
This data base record contains the following data elements-
Cl ST-REGION-CODE • C13 ST-VIO-LAST-UPDATE
C3 ST-STATE-CODE .. CIS ST-ENF-LAST-UPDATE
C4 ST-IND-RES-CODE • C17 ST-VE-LAST-UPDATE
C5 ST-PRIMACY-FLAG * C19 ST-RECON-FLAG
C7 ST-ANY-DATA-LAST-UPDATE . C29 ST-SAMPLE-LAST-UPDATE
C9 ST-INV-LAST-UPDATE
• Comments
Each data element name contained within the STATE-SUMMARY data base record is prefaced with ... ST-
Effective Date 1/31133 Release Number. 2.00 Page. H-8
-------
FRDS-tl Data Element Description
Name: ST-REGION-CODE
Number
• Description
A computed code value that represents one of the 10 EPA regional offices In which public water systems are located.
The term computed, as used here, implies that this code value is not reported by the State. ST-REGION-CODE Is assigned by the PROS
Data Base Administrator.
.Source
• Data Characteristics
FRDS-II Data Transfer File
' DBA SUPPLIED ***
Data Base Record: CO STATE-SUMMARY
Data Base Family:
Data Category:
Data Type: INTEGER
Picture: 9(2)
ALL
10
Registration Requirement: •
Grant Requirement NO
Access: KEY
Code Table ID: 0001
• Acceptable Values
see Section VI; Table 0001):
Entries from the EPA Region Coi
•Or - Boston. EPA Region I (CT ME MA NH Rl VT)
•02- - New York, EPA Region II (NJ NY PR VI)
TO'- Philadelphia. EPA Region III (DC DE MD PA VA WV)
•04' - Atlanta. EPA Region IV (AL FL GA KY MS NC SC TN)
•05' - Chicago. EPA Region V • (IL IN Ml MN OH Wl)
W - Dallas. EPA Region VI (ARLANMOKTX)
•07- • Kansas City. EPA Region VII (IA KS MO NE)
•08' - Denver. EPA Region VIII (CO MT ND SO UT WY)
•09-• San Francisco. EPA Region IX (AS AZ CA FM GU HI MH MP NV PW)
•10-- Seattle, EPA Region X (AKIDORWA)
•* Comments
ST-REGION-CODE Is valued wtth Arabic numerals (01. 02 10) to Identify the EPA regions In the FRDS-tl Data Base, and not Roman
numerals (I. II X).
Effective Date. 1/31/93
Release Number. 2.00
Page: JI_-§.
-------
FRDS-II Data Element Description
Number C3
Name: ST-STATE-CODE
• Description
A computed code value that represents a State. EPA region, or Indian reservation, and that describes a governmental jurisdiction In which
public water systems are located. Included are:
the 50 United States
the District of Columbia
the U.S. Possessions (American Samoa. Guam, the Northern Mariana Islands. Palau. the
Commonwealth of Puerto Rico, and the U.S. virgin Islands)
the Freely Associated States (Federated States of Micronesia, and the Marshall Islands)
B EPA regions In which the region has primacy over Indian reservations
Each governmental jurisdiction other than the 50 United States (i.e.. the District of Columbia, the U.S. Possessions, the Freely Associated
States. Indian reservations, and the EPA regions performing direct implementation) is. referred to as a State, by convention and definition.
Public water systems located on an Indian reservation are identified as if they are located within an EPA region (i.e.. 02.04.... 10), and not
within a specific State. Additionally, tor public water systems located on an Indian reservation that has been granted primary enforcement
responsibility, data element C4. ST-IND-RES-CODE. identifies the reservation.
Since EPA regions I (Boston) and III (Philadelphia) do not have any federally administered Indian reservations within their jurisdictions.
ST-STATE-CODE should never be valued with a 01 or 03.
The term computed, as used here, implies that this code value is not reported by the State. ST-STATE-CODE is assigned by the FRDS Data
Base Administrator.
• Source
FRDS-II Data Transfer File
' DBA SUPPLIED'
• Data Characteristics
Data Base Record: CO STATE-SUMMARY
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: X(2)
ALL
10
Registration Requirement: _;
Grant Requirement: NO
Access: KEY
Code Table ID: 0003
• Acceptable Values
Entries from the FIPS PUB 5-2. Alphabetic State Codes and Selected EPA Region Codes (see Section VI; Table 0003)
• Comments
ST-STATE-CODE is valued with Arabic numerals (02.04 10) to identify the 8 EPA regions, and not Roman numerals (II. IV X).
Effective Date 1/31/93
Release Number: 200
Page:
-------
FRDS-II Data Element Description
Name: ST-IND-RES-COPE
Number: C4
• Description
A computed code value tat identities an Indian reservation which has been granted primary enforcement
risibility.
The term computed, as used here, implies that this code value is not reputed by the State. ST-IND-RES-CODE Is assigned by the FRDS
Data Base Administrator.
• Source
FRDS-II Data Transfer Fiu
••• DBA SUPPLIED •••
e Data Characteristics
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Category: JO
Data Type: CHARACTER
Picture: X(71
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
KEY
ID01
• Acceptable Values
Entries from the FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes (see Section VI; Table ID01)
• Comments
This data element is valued only when an Indian reservation has been granted primary enforcement r
isibility.
Effective Date. 1/31/93
Rel
Number. 200
Page: 11-11
-------
FRDS-II Data Element Description
Number CS
Description
Name: ST-PBIMACY-FIAG
A computed code value that represents whether an EPA region (identified In C1, ST-REGION-CODE), State (IdenttRed In C3.
ST-STATE-CODE), or Indian reservation (identified in C4. ST-IND-RES-CODE) has been granted primary enforcement responsibility for public
water systems.
The term computed, as used here, fmplfes that (his code value k not reported by the State. ST-PfllMACY-FLAG fe assigned by ihe PROS
Data Base Admintslrator.
Source
• Data Characteristics
FRDS-II Data Transfer File
*•• DBA SUPPLIED *"
Data Base Record: 00 STATE-SUMMARY
Data Base Family: ALL
Data Category: 10
Data Type: CHARACTER
Picture: XM)
Registration Requirement •
Grant Requirement: NO
Access:
Code Table ID:
KEY
0005
Acceptable Values
Entries from the Primacy Flag Codes (see Section VI; Table 0005):
•Np - Native Entity has Primacy ........................ (Indian Tribe/Reservation}
•R' • EPA Region has Primacy
•S1 - State Agency has Primacy
• Comments
None
Effective Date
Release Number: g.OO
Page: 11-12
-------
FRDS-tl Data Element Description Number
Name: ST-ANY-DATA-LAST-UPDATE
Description
A computed value that represents the most recent calendar date on which an update was posted to any inventory, violation, enforcement
action, sample, or varlance/exempBon/other data In the FRDS-tl Data Base for a State.
This date applies to any update posted to any data element (
C100 PWS-SUMMARY
C300 PWS-ADDRESS-DATA
PWS-SOURCE-ENTrrY-INFO
PWS-SE-TREATMENT-DATA
•ds:
C400
C480
CSOO
C600
C700
C800
PWS=GEOGRAPHIC-AREAS-SERVED
PWS-SERVICE-AREAS
PWS-ON-SITE-VtSITS
PWS-MILESTONES-EVENTS
C1100 VIOLATION-DATA
C11BO VIO-ENFORCEMENTS
mtained in any of the following data base reo
• C1200 ENFORCEMENT-DATA
• C1280 ENF-V10LATIONS
• C2100 SAMPLE-DATA
• C3000 VARIANCE-EXEMPTION-DATA
• C3100 VE-SCHEDULE
• C4000 STATE-DISCRETIONARY-DATA
The term update, as used here, includes any additions, modifications, or deletions made to any Inventory, violation, enforcement action.
sample, or variance/exemption/olher data in the FRDS-II Data Base.
The term computed, as used here. Implies that this date Is not reported by the State. ST-ANY-DATA-LAST-UPDATE is determined automatically
by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: 00 STATE-SUMMARY
Data Base Family: ALL
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement _;
Grant Requirement NO
Code Table. ID:
NON-KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1-2;
day, in position 3 • A\ and
year, in position 5 - 6
• Comments
This date is changed tor State reported updates only (i.e., updates submitted via DTF transactions).
Other dates of last update are maintained in the following data elements:
C9 ST-INV-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
C15 ST-ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-INV-LAST-UPDATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1133 VIO-LAST4JPDATE
C1207 ENF-LAST-UPDATE
C3021 VE-LAST-UPDATE
Ettective Dale J/31/93
Release Number. 200
Page: 11-13
-------
FRDS-II Data Element Description
Number. 09
Name. ST-INV-LAST-UPDATE
• Description
A computed value that represents the most recent calendar date on which an update was posted to any Inventory data In the FRDS-II Data
Base for a State.
This date applies to any update posted to any data element contained in any of fte following data base records:
C100 PWS-SUMMARY
C300 PWS-ADDRESS-DATA
C400 PWS-SOUPCE-ENT1TY-INFO
C460 PWS-SE-TREATMENT.DATA
C500 PWS-GEOGRAPHIC-AREAS-SERVEO
C600 PWS-SERVICE-AREAS
C700 PW&ON-SITE-VISrrS
C600 PW&MILESTONES-EVENTS
C4000 STATE-DISCRETIONARY-DATA
The term update, as used here. Includes any additions, modifications, or deletions made to any Inventory data In the FRDS-II Data Base.
The term computed, as used here, implies that this date is not reported by the State. ST-INV-LAST-UPDATE Is determined automatically by
the FRDS-H computer system during As normal course of operation.
Source
FRDS-II Data Transfer File
•** GENERATED DATA ITEM *•*
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day. In position 3-4; and
year, in position 5 - 6
• Data Characteristics
Data Base Record: 00 STATE-SUMMARY
Data Base Family:
Data Category:
Data Type: DATE
Picture: MMDDYY
ALL
60
Registration Requirement ^
Grant Requirement: NO
Access: NON-KEY
Code Table ID: N/A
• Comments
This date is changed for State reported updates only (i.e.. updates submitted via DTP transactions).
Other dates of last update'are maintained in the following data elements:
C7 ST-ANY-DATA-LAST-UPDATE
C13 ST-V)O-LAST-UPDATE
C15 ST-ENF-LAST-UPDATE
C1T ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-INV-LAST4JPDATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1133 V1O-LAST-UPDATE
C1207 ENF-LAST-UPDATE
C3021 VE-LAST-UPDATE
Effective Dale 1/31/93
Release Number: 2.00
Page: II • 14
-------
FRDS-II Data Element Description
Name: ST-VIO-LAST-UPDATE
Number C13
• Description
A computed value that represents the most recent calendar date on which an update was posted to any violation data m the FRDS-II Data
Base tor a State.
This data applies to any update posted to any data element contained In any of the tallowing data base records:
• C1100 VIOLATION-DATA
• C1180 VIO-ENFORCEMENTS
The.term update, as used here, includes any additions, modifications, or deletions made to any violation data In the FRDS-II Data Base.
The term computed, as used here, implies that this date is not reported by the State. ST-VIO-LAST-UPDATE Is determined automatically by
the FRDS-II computer system during Its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement: •
Grant Requirement NO .
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month. In position 1 - 2|
day, in position 3 • 4; and
year. In position 5 - 6
• Comments
This date is changed for State reported updates only (i.e.. updates submitted via DTF transactions).
OthBT dotes of Issi update BTB mdintsJnod In tho following dots 6l6fH6ntsi
C7 ST-ANY-DATA-LAST-UPDATE • C167 PWS-INV-LAST-UPDATE
C9 ST-INV-LAST-UPDATE • C169 PWS-ANY-DATA-LAST-UPDATE
CIS ST-ENF-LAST-UPDATE • C1133 VIO-LAST-UPDATE
C17 ST-VE-LAST-UPDATE • C1207 ENF-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE • C3021 VE-LAST-UPDATE
Effective Date 1/31/93
Release Number: 2.00
Page: II -1
-------
FRDS-II Data Element Description
Name: ST-ENF-LAST-UPDATE
Number C1S
• Description
A computed value that represents the most recent calendar date on which an update was posted to any enforcement action data In the
FRDS-II Data Base for a State.
This date applies to any update posted to any data element contained in any of the following data base records:
• C1200 ENFORCEMENT-DATA
• C1280 ENF-VIOLATIONS
The term update, as used here, includes any additions, modifications, or deletions made to any enforcement action data In the FRDS-II Data
The term computed, as used here. Implies that this date is not reported by the State. ST-ENF-LAST-UPDATE is determined automatically
by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
*** GENERATED DATA ITEM •••
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
A six digit numeric calendar date, comprised of.
month, in position 1 - 2;
day. in position 3 - 4; and
year, in position 5 - 6
e Comments
This date is changed for State reported updates only (i.e.. updates submitted via DTP transactions).
Other dates of last update are maintained in the following data elements:
C7 ST-ANY-DATA-LAST-UPDATE
C9 ST-INV-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-1NV-LAST-UPDATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1133 VIO-LAST-UPDATE
C1207 ENF-LAST-UPDATE
C3021 VE-iAST-UPDATE
Effective Date- 1/31/93
Release Number: 200
Page: 11-16
-------
FRDS-II Data Element Description
Name: ST-VE-LAST-UPDATE
Number C17
• Description
A computed value that represents the most recent calendar date on which an update was posted to any variance, exemption, or other event
in the FRDS-II Data Base tor a State.
This date applies to any update posted to any data element contained in any of the following data base records:
• C3000 VARIANCE-EXEMPTION-DATA
• C3100 VE-SCHEDULE
The term update, as used here. Includes any additions, modifications, or deletions made to any variance, exemption, or other event in the
FRDS-II Data Base. '
The term computed, as used here, implies that this date Is not reported by the State. ST-VE-LAST-UPDATE is determined automatically by
the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
1 GENERATED DATA ITEM ••
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Category: 60
Data Type: DATE
Picture: MMDDYY
RdQistr&tion Requirement!
Grant Requirement
NO
Code Table ID:
NON-KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day, in position 3 - 4; and
year, in position 5-6
• Comments
This date Is changed for State reported updates only (i.e., updates submitted via DTP transactions).
Other dates of last update are maintained in the following data elements:
C7 ST-ANY-DATA-LAST-UPDATE • C167
C9 ST-INV-LAST-UPDATE • C169
C13 ST-VIO-LAST-UPDATE • C1133
CIS ST-ENF-LAST-UPDATE • C1207
C29 ST-SAMPLE-LAST-UPDATE • C3021
PWS-INV-LAST-UPDATE
PWS-ANY-DATA-LAST-UPDATE
VIO-LAST-UPDATE
ENF-LAST-UPDATE
VE-LASl-UPDATE
Effective Date 1/31/93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Name: ST-RECON-FLAG
Number. C19
sltates
• Description
A computed code value thai represents whether or not an update has been performed to the FRDS-II Data Base lor a State which r
the recalculation ol any of the various data elements whose values are maintained (i.e.. computed) by the FRDS-II computer system.
The term computed, as used here, implies that this code value is not reported by the State. ST-RECON-FLAG is determined automatically
by the FRDS-II computer system during its normal course of operation.
• Source
FRDS-II Data Transter File
••• GENERATED DATA ITEM •••
• Data Characteristics
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Cateoory: 10
Data Type: CHARACTER
Picture: X(1)
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
KEY
0019
e Acceptable Values
Entries from the State Reconciliation Flag Codes (see Section VI; Table 0019):
•IT • Reconciliation NOT Needed for State
•Y1 • Reconciliation Needed for State
e Comments
Other reconciliation flags are maintained in the following data elements:
• C171 PWS-RECON-FLAG
• C1001 NCD-REGON-FLAG
Effective Date. 1/31/93
Release Number: 200
Page: 11-18
-------
FRDS-II Data Element Description Number. C29
Name: ST-SAMPLE-LAST-UPDATE __
• Description
A computed value that represents the most recent calendar date on which an update was posted to any sample data in the FRDS-II Data
Base for a State.
This date applies to any update posted to any data element contained in the following data base record:
• C2100 SAMPLE-DATA
The farm update, as used here, includes any additions, modifications, or deletions made to any sample data in the FRDS-II Data Base.
The term computed, as used here, implies that this date is not reported by the State. ST-SAMPLE-LAST-UPDATE is determined automatically
by the FRDS-II computer system during Its normal course of operation.
• Source
FRDS-II Data Transfer File
' GENERATED DATA ITEM '
e Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 • 2i
day. In position 3 - 4; and
year, in position 5 - 6
e Data Characteristics
Data Base Record: CO STATE-SUMMARY
Data Base Family: ALL
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
e Comments
This date Is changed for State reported updates only (i.e.. updates submitted via DTP transactions).
Other dates of last update are maintained in the following data elements:
C7 STANY-DATA-LAST-UPDATE • C167 PWS-INV-LAST-UPDATE
C9 ST-INV-LAST-UPDATE • C169 PWS-ANY-DATA-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE • C1133 VIO-LAST-UPDATE
C15 ST-ENF-LAST-UPDATE • C1207 ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE • C3021 VE-LAST-UPDATE
Effective Date. 1/31/93
Release Number: 2.00
-------
FRDS-II Data Base Record Description
Name: PWS-SUMMARY
Number C100
• Description
A SYSTEM 2000 data base record Identification number and name.
The C100, PWS-SUMMARY. data base record contains data elements that serve to Identify and characterize a public water system's Inventory
data. Additional inventory data is stored in the following data base records:
• C300 PWS-ADDRESS-DATA • C600 PWS-SERVICE-AREAS
• C400 PWS-SOURCE-ENTrTY-INFO • C700 PWS-ON-SITE-VISrrS
• C480 PWS-SE-TREATMENT-DATA • CSOO PWS-MILESTONES-EVENTS
• CSOO PWS-GEOGRAPHIC-AREAS-SERVED • C4000 STATE-DISCRETIONARY-DATA
The FRDS-II Data Base has one PWS-SUMMARY data base record for each public water system that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: ALL Parent Record: CO STATE-SUMMARY
• Record Contents
This data base record contains the following data elements:
C101 PWS-ID
C102 PWS-GRANT-EUGIBLE
C103 PWS-STATUS
C105 PWS-TYPE
C107 PWS-ACTIVITY-FLAG
C109 PWS-HISTORY-FLAG
C111 PWS-SYSTEM-BEGIN-YYMM
C113 PWS-DEACT-YYMM
C115 PWS-POP-CATEGORY
C117 PWS-RETAIL-POP-SERVED
C119 PWS-PRIMARY-SOURCE
C121 PWS-PCT-SURFACE
C123 PWS-PCT-GROUND
C125 PWS-PCT-PUR-SURFACE
C127 PWS-PCT-PUR-GROUND
C129 PWS-TREATMENT-CLASS
C131 PWS-SYSTEM-NAME
C133 PWS-SYSTEM-ADDR-UNE-1
C135 PWS-SYSTEM-ADDR-L1NE-2
C137 PWS-SYSTEM-CITY
C139 PWS-SYSTEM-STATE
C141 PWS-SYSTEM-ZIP
C143 PWS-PHONE
C145 PWS-METERS
C147 PWS-SERV1CE-CONNECTIONS
C149 PWS-AVG-DAILY-PROD
C151 PWS-TOT-DESIGN-CAPACITY
C153 PWS-TOT-EMERGENCY-PROD
C155 PWS-TOT-STORAGE-CAPACITY
C157 PWS-MAX-DAILY-PROD
C159 PWS-SEASON-BEGIN-MMOD
C161 PWS-SEASON-END-MMDD
C163 PWS-OWNER-TYPE
C165 PWS-REGULATING-ENTITY
C167 PWS-INV-LAST-UPDATE
C168 PWS-INSERT-DATE
C169 PWS-ANY-DATA-LAST-UPDATE
C171 PWS-RECON-FLAG
C173 PWS-FYNN-TRACKEH
• Comments
Each data element name contained within the PWS-SUMMARY data base record is prefaced with ... PWS-
At present, there are approximately 345.000 public water systems in the FRDS-II Data Base. Of these. 225.000 public water systems comprise
the Current inventory.
Effective Dale
Release Number 200
Page.
-------
FRDS-II Data Element Description
Name: PWS-ID
Number. C101
• Description
An alphanumeric value used to uniquely identify a public water system.
A public water system identification code is unique within a State.
PWS-ID is of the form: ss xxxxxxx (space Inserted for clarity only)
When: ss = the FIPS Pub 5-2 State abbreviation In which a public water system is located, or the region number of the EPA region
responsible for an Indian reservation
xxxxxxx = a public water system identification code assigned by the State
• Source
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length: 9
e Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base FamHy: ALL
Data Category: .21
Data Type: CHARACTER
Picture: X®
Registration Requirement J
Grant Requirement YES
Access: KEY
Code Table ID: N/A
• Edit Criteria
Must always be specified
When specified:
position 1 • 2 must be equal to the value specified in the State code (C3. ST-STATE-CODE)
position 3 - 9 must be alphabetic and/or numeric (i.e.. contain only V through •ff. and/or 'A' through T)
position 3-9 must not contain any special characters (e.g., T,'.'. '•'. etc.)
must not exist in the FRDS-II data base when inserting an inventory record
must exist in the FRDS-II data base when Inserting any record except an Inventory record
must exist in the FRDS-II data base when modifying and inventory record
Each new inventory record must include values tor those data elements within the PWS summary record (C100, PWS-SUMMARY) that are
identified as Registration Requirement data elements (see 'Data Characteristics' on his page) [ERR]
Additionally, each new inventory record must include at least one
PWS-SE-RECORD-TYPE of'S1) |EBA]
source record (C400, PWS-SOURCE-EfflTTY.|NFO with C405,
• Comments
PWS-tD is a critical identification number within the FRDS-II Data Base. As such, once a PWS ID has been assigned to a public water system,
It should never be used to refer to any other public water system within the State.
If a State determines, however, that It Is necessary to renumber their public water systems. It is imperative that a one-tor-one conversion list
be supplied to the FRDS Data Base Administrator prior to reporting any existing public water system that has been assigned a new
Identification number.
PWS-ID must be valued for a new public water system to be inserted into the FRDS-II Data Base.
Additionally, it is required for a public water system to be grant eligible.
Effective Date 1/31/93
Release Number. 2.00
Page: ll-2j_
-------
FRDS-II Data Element Description
Name: PWS-GRANT-ELIGIBLE
Number C102
• Description
A computed code value that represents whether or not a public water system will be counted in the computation of a State's grant allocation.
In FRDS-II, certain data elements must have a specific value for a public water system to be counted when the State's grant allocation Is
computed. It any of these data elements are not valued or the data element does not contain the specific value required, the public water
system will not be counted for grant allocation purposes. See Section III.. B.. for a complete list of these data elements.
The term computed, as used here. Implies that this code value is not reported by the State. PWS-GRANT-EUGIBLE is determined
automatically by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
"• GENERATED DATA ITEM "•
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: 10
Data Type: CHARACTER
Picture: XM)
Registration Reauirement: -
Grant Reauirement NO
Access: KEY
Code Table ID: 0102
• Acceptable Values
Entries from the Grant Eligibility Codes (see Section VI; Table 0102):
•N1 - PWS NOT Grant Eligible
•Y1 - PWS Grant Eligible
• Comments
This data element will be valued with the letter T tor a public water system that is 'Grant Eligible1 (I.e., a system that will be counted when
the State's grant allocation is computed). Refer to Section III. 8. for a list of all data elements that affect the grant eligibility determination.
Effective Date. 1/31/93
Release Number: 200
Page: II-22
-------
FRDS-II Data Element Description
Name: PWS-STATUS
Number C103
• Description
A computed code value that represents Whether a public water system is:
• A Community. Non-transient Non-community, or Transient Non-community public water system;
• Active or Inactive; and
• InJhe Current or Historical inventory.
The term computed, as used here. Implies that this code value is not reported by the State. PWS-STATUS is determined automatically by
the FRDS-II computer system during Its normal course of operation.
PWS-STATUS is of the form: xyz (spaces inserted for daily only)
Where: x = a code value that represents Community (C). Non-transient Non-community (P). or Transient Norwommunlty (N)
y«a code value that represents Active (A) or Inactive (I)
z » a code value that represents Current (C) or Historical (H)
• Source
FRDS-II Data Transfer File
••* GENERATED DATA ITEM •••
• Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: XO)
ALL
10
Registration Requirement ^
Grant Requirement ~
Access:
Code Table ID:
NO
KEY
0103
• Acceptable Values
Entries from the PWS Status Codes (see Section VI; Table 0103):
•CAC' - CWS. Active. Current (Community PWSs)
•CAM1 - CWS. Active. Historical (Community PWSs)
•CIC- - CWS. Inactive. Current (Community PWSs)
•CIH' • CWS. Inactive, Historical (Community PWSs)
•NAC1 - TNCWS, Active. Current (Transient Non-community PWSs)
•NAH' • TNCWS. Active. Historical (Transient Non-community PWSs)
•NIC- - TNCWS. Inactive. Current (Transient Non-community PWSs)
•NIH- - TNCWS. Inactive. Historical (Transient Norvcommunity PWSs)
•PAC1 - NTNCWS, Active. Current (Non-transierH Noircommunfty PWSs)
•PAH' - NTNCWS. Active. Historical (Non-transient Nocvcommunlty PWSs)
•PIC' - NTNCWS, Inactive. Current (Non-transient Non-community PWSs)
•PIH1 • NTNCWS. Inactive. Historical • (Non-transient Norxxsmmunity PWSs)
• Comments
The data elements that are
• C105 PWS-TYPE
• C107 PWS-ACTIVTTY-FLAG
• C109 PWS-HISTORY-FLAG
nsidered In the computation of this code value are as follows:
Effective Date 1/31/93
Release Number. 2.00
Page: 11-23
-------
FRDS-II Data Element Description Number. C10S
Name: PWS-TYPE
• Description
A code value that indicates whether a public water system is a Community, a Non-transient Non-community, or a Transient Non-community
public water system.
A Community water system means a public water system which serves at least 15 service connections used by year-round residents or
regularly serves at least 25 year-round residents.
A Non-community water system means a public water system that is not a Community water system. Non-community water systems are
'divided into Non-transient and Transient categories. A Non-transient Non-community water system means a public water system that is not
-a Community water system and that regularly serves at least 25 of the same persons over 6 months per year. A Transient Non-community
water system means a public water system that does not fulfill the requirements to be either a Community or a Non-transient Non-community
public water system.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL Registration Requirement ,2,
Data Category: 10 Grant Requirement YES
Data Type: CHARACTER Access: KEY
Picture: X{1] Code Table ID: 0105
• Edit Criteria
Must be specified when-
• inserting an inventory record
• modifying the current value
When specified:
• must be one of the PWS Type Codes (see Section VI; Table 0105):
•C1 - Community PWS (CWS)
•N* - Transient Non-community PWS (TNCWS)
•P1 - Non-transient Non-community PWS (NTNCWS)
• Comments
PWS-TYPE is used in the computation of data element C103. PWS-STATUS.
When a Non-transient Non-community or a Transient Non-community public water system is changed to a Community public water system,
data elements C159. PWS-SEASON-BEGIN-MMDD. and C161. PWS-SEASON-END-MMDD will automatically be initialized to a -null- value.
PWS-TYPE must be valued for a new public water system to be inserted into the FRDS-II Data Base.
Additionally, it is required for a public water system to be grant eligible.
Effective Date. 1/31/93 Release Number:
-------
FRDS-II Data Element Description Number: C107
Name: PWS-ACTrvrTY.FLAG .
• Description
A code value that represents whether a public water system Is Active or Inactive.
The term Active refers to a public water system that is producing water on a regular basis (obtaining, treating, pumping, storing, or
dtetnbuting).
The term Inactive refers to a public water system that Is not an Active public water system. Such systems have discontinued operation.
A public water system that has closed permanently is an obvious example of a system that would be an Inactive system.
A public water system that has dosed temporarily, but for a substantial period of time, could be designated as Inactive by the State, but not
necessarily so. This decision depends upon State specific policy regarding such systems.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL Registration Requirement 2
Data Category: JO Grant Requirement YES
Data Type: CHARACTER Access: KEY
Picture: X(1) Code Table ID: 0107
• Edit Criteria
Must be specified when:
• inserting an inventory record
• modifying the current value
When specified:
• must be one of the PWS Activity Rag Codes (see Section VI; Table 0107):
•A' - Active PWS
V • Inactive PWS
When deactivating a PWS. the date of deactivation (C113, PWS-DEACT-YYMM) must be specified [E9A]
• Comments
PWS-ACnvTTY-FLAG Is used in the computation of data element C103. PWS-STATUS.
It PWS-ACTTVITY-FLAG indicates that the public water system is Inactive, data element C113, PWS-OEACT-YYMM. Identifies the data on which
the system became Inactive.
When an Inactive public water system is changed to an Active public water system, data element C113. PWS-DEACT-YYMM, will automatically
be initialized to a -null, value.
PWS-ACnvTTY-FLAG must be valued for e new public water system to be inserted Into the FRDS-II Data Base. Additionally, a public water
system must be Active (PWS-ACTrvTTY-FLAG = W) to be grant eligible.
Eflectve Date 1/31/93 Release Number: 2.00 Page: II-25
-------
FRDS-II Data Element Description
Name: PWS-HISTORY-FLAG
Number C109
• Description
A computed code value that represents whether a public water system is In the Current or Historical inventory.
tory
The definition of Current inventory is influenced by whether or not a State submitted a Total Replacement1 to its public water system In
in the most recent repotting period.
If a State submitted a Total Replacement.' the term Current inventory refers to those public water systems which were reported In that most
recent period. Those public water systems that existed in the Current inventory prior to the update, for which a replacement was not
'submitted, would become part of the Historical inventory.
If a State submitted 'updates only* to Its inventory in the most recent reporting period. Current inventory refers to those public water systems
that existed in the Current inventory prior to the update, plus any new public water systems which were reported in that most recent period.
The term Historical inventory refers to those public water systems that were in the Current inventory at one time, but were assigned to the
Historical inventory during the conversion from FRDS 1.5 to FRDS-II. were assigned to the Historical inventory by explicit action of the FRDS
Data Base Administrator, or were assigned to the Historical inventory as a result of Total Replacement1 update processing as described
above, and. consequently, are no longer part of the Current inventory.
A public water system that has been Inactive for a substantial period of time may be assigned to the Historical Inventory, at the discretion
of the FRDS Data Base Administrator.
Any update input by the State for a public water system in the Historical inventory will cause the system to be transferred to the Current
Inventory.
The term computed, as used here, implies that this code value is not reported by the State. PWS-HISTORY-FLAG is determined automatically
by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: JO
Data Type: CHARACTER
Picture: Xm
Registration Requirement _;
Grant Requirement NO
Access: KEY
Code Table ID: 0109
• Acceptable Values
Entries from the History Flag Codes (see Section VI; Table 0109):
*C* - Current Inventory
•H1 - Historical Inventory
• Comments
PWS-HISTORY-FLAG is used in the computation of data element C103. PWS-STATUS.
A public water system must be in the Current inventory (PWS-HISTORY-FLAG = *C') to be grant eligible.
Effective Date 1/31/93
Release Number: 2.00
Page: II-26
-------
FRDS-II Data Element Description Number: Cm
Name: PWS-SYSTEM-BEGIN-YYMM
• Description
A numeric value that represents Ihe calendar year and month In which a public water system initiated operation.
If the calendar date on which a public water system initiated operation Is not known. PWS-SYSTEM-BEGIN-YYMM identifies the 'best estimate'
of when the system initiated operation.
PWS-SYSTEM-BEGIN-YYMM is of the form: yymm (space Inserted tor clarity only)
Where: yy = 9w calendar year in which a public water system initiated operation
mm = the month of the year in which a public water system initiated operation
• Source
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length: 4
e Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: .61
Data Type: INTEGER
Picture: 9(41
Registration Requirement: ^
Grant Requirement: NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be a four digit numeric calendar date, comprised of:
. year, in position 1 - 2; and
. month. In position 3 - 4
e Comments
None
Effective Date 1/31/93
Release Number: 2.00
Page: 11-27
-------
FRDS-II Data Element Description
Name: PWS-DEACT-YYMM
Number C113
• Description
A numeric value that represents the calendar year and month in which a public water system was deactivated.
The term deactivated refers to a public water system that has discontinued operation.
A public water system that has closed permanently is an obvious example of a system that would be deactivated by the State.
A public water system that has closed temporarily, but for a substantial period of time, could be deactivated by the State, but not necessarily
•so. This decision depends upon State specific policy regarding such systems.
PWS-DEACT-YYMM is of the form: yymm (space inserted for darity only)
Where: yy = the calendar year in which a public water system was deactivated
mm = the month of the year in which a public water system was deactivated
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers:
Maximum Length:
PWS-ID
4
Data Base Record: C100
Data Base Family: ALL
Data Cateaorv: 61
Data Tvoe: INTEGER
Picture: 9(4)
PWS-SUMMARY
Registration Requirement
Grant Requirement
Access:
Code Table ID:
4
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• inserting an inventory record for an inactive PWS [E9A]
• modifying the current value
Must not be specified when inserting an inventory record for an active PWS (i.e.. C107. PWS-ACTIVITY-FLAG or 'A1) [EXI]
When specified-
• must be a four digit numeric calendar date, comprised of:
. year, in position 1 - 2. and
. month, in position 3 • 4
• must be before the current calendar date [EEA]
• must be greater than the PWS operation begin date (C111. PWS-SYSTEM-BEGIN-YYMM) [EGD]
• Comments
PWS-DEACT-YYMM is not applicable to Active water systems.
Data element C107, PWS-ACTIVITY-FLAG. identifies whether the public water system is Active or Inactive.
When an Inactive public water system is changed to an Active public water system, data element C113. PWS-DEACT-YYMM. will automatically
be initialized to a -null- value.
PWS-DEACT-YYMM must be valued for a Inactive public water systems.
Effective Date 1/31/93
Release Number. 200
Page: Jl
-------
FRDS-II Data Element Description
Name. PWS-POP.CATEGORY
Number C115
• Description
A computed code value that represents the specific population range into which the population served by a public water system falls,
The farm computed, as used here, implies that this code value Is not reported by the State. PWS-POP-CATEGORY Is determined
automatically by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM '
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: 10
Data Type: CHARACTER
Picture. X/,1)
Registration Reauirement -
Grant Requirement NO
Access: KEY
Code Table ID: 0115
• Acceptable Values
Entries from the Population Category Codes (see Section VI; Table 0115):
•A' - Under 101 persons served
•B1 - 101 • 500 persons served
•C' - 501- 1,000 persons served
•D- - 1,001 - 2,500 persons served
T • 2,501 - 3.300 persons served
•P • 3,301 - 5,000 persons served
•G* - 5,001 - 10,000 persons served
•H1 - 10,001 - 50.000 persons served
V • 50.001 - 75.000 persons served
•J' - 75,001 • 100.000 persons served
•K1 - Over 100.000 persons served
•. Comments
The data element that is considered in the computation of this code value is C117, PWS-RETAIL-POP-SERVED.
Effective Date- 1/31/93
Release Number. 2.00
Page: 11-29
-------
FRDS-II Data Element Description
Number C117
Name: PWS-RETAIL-POP-SERVED
• Description
A numeric value that represents the number of retail customers served by a public water system.
In public water systems where large seasonal fluctuations in population occur. PWS-RETAIL-POP-SERVED represents the average number
of persons served.
'• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .A2
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: 30
Data Type: INTEGER
Picture: 9(8)
Registration Requirement
Grant Requirement
AOOBSS!
Code Table ID:
YES
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• inserting an inventory record
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• must be less than 20000000 (20 million) [EEM]
• must be greater than zero when the Public Water System is not a wholesaler of water (i.e., no occurrence of C603.
PWS-SERV-CATEGORY is 'O2') [EGC]
• should be greater than or equal to 25 when the number of service connections (C147. PWS-SERVICE-CONNECTIONS) is less than
15
• Comments
Approximately 15% of the nation's population is served by 85% of the public water systems. Inversely. 85% of the nation's population to served
by 15% of the public water systems
PWS-RETAIL-POP-SERVED is used In the computation of data element C115. PWS-POP-CATEGORY.
PWS-RETAIL-POP-SERVED must be valued for a new public water system to be inserted Into the FRDS-II Data Base. Additionally, a public
water system must serve 25 or more persons, or have 15 or more service connections to be grant eligible (unless they are Identified as
•wholesalers of water*).
Effective Date. 1/31/93
Release Number:
Page: II-30
-------
FRDS-II Data Element Description Number C119
Name: PWS-PRIMARY-SOURCE
• Description
A computed code value that represents whether a public water system is a surface water system, a ground water system, a purchased surface
water system, or a purchased ground water system.
Determination of primary source is based upon two factors. The type of the source and the availability of the source (e.g.. used on a
permanent, seasonal. Interim, emergency basis).
A specific hierarchy is followed in calculating the primary source. It is as follows:
1) Initially, only permanently available sources are examined;
2) If a non-purchased'surtace source is encountered, the public water system is considered to be a surface water system, and the.
determination process is complete;
3) If a purchased surface source is encountered, the public water system Is considered to be a purchased surface water system, and
the determination process is complete;
4) If a non-purchased ground water (UDI) source is encountered, the public water system is considered to be a ground water (UDI).
system, and the determination process Is complete;
5) If a purchased ground water (UDI) source Is encountered, the public water system is considered to be a purchased ground water
(UDI) system, and the determination process Is complete;
6) If a non-purchased ground water source is encountered, the public water system Is considered to be a ground water system, and
the determination process is complete;
7) If a purchased ground water source Is encountered, the public water system is considered to be a purchased ground water system,
and the determination process is complete;
8) If there are no permanently available sources, all sources are treated equally, regardless of their individual availability, and steps 2
through 7 are repeated.
The term computed, as used here, implies that this code value is not reported by the State. PWS-PRIMARY-SOURCE Is determined
automatically by the FRDS-II computer system during its normal course of operation.
• Source • Data Characteristics
FRDS-II Data Transfer File
•** GENERATED DATA ITEM •••
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Cateaorv: 10
Data Type: CHARACTER
Picture: X(1)
Registration Requirement: •
Grant Reauirement NO
Access: KEY
Code Table ID: 0119
• Acceptable Values
Entries from the Primary Source Type Codes (see Section VI; Table 0119):
*G' - Groundwater. Non-purchased
•P* • Surface, Purchased
•S' • Surface, Non-purchased
"W • Groundwater. Purchased
•V - Groundwater (UDI). Non-Purchased
*Z* - Groundwater (UDI). Purchase
• .Comments
The data elements that are considered in the computation of this code value are as follows:
• C405 PWS-SE-RECORD-TYPE
• C407 PWS-SE-CODE
• C409 PWS-SE-AVAILABILJTY
Effective Date. 1/31/93 Release Number: 2.00 Page: 11-31
-------
FRDS-ll Data Element Description
Name: PWS-PCT-SURFACE
Number C121
• Description
A numeric value that represents the percentage of water delivered to the public that Is obtained from non-purchased surface wale
used by a public water system.
urces
PWS-PCT-SURFACE is calculated by dividing the quantity of water obtained from all sources into the quantity of water obtained from only
non-purchased-surface water sources, multiplying the result by 100. and rounding the percentage obtained to the nearest whole percent
• Source
• Data Characteristics
FRDS-ll Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length.
A2
PWS-ID
-2
Data Base Record: ClOQ PWS-SUMMARY
Data Base Family: ALL
Data Category: 30
Data Type:
Picture:
INTEGER
9(3)
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an Integer number
• must be between zero and 100. inclusive JEICJ
• the sum of the following data elements should be less than or equal to 100:
. C121 PWS-PCT-SURFACE
. C123 PWS-PCT-GROUND
. C125 PWS-PCT-PUR-SURFACE
. C127 PWS-PCT-PUR-GROUND
• Comments
Often, the total quantity of water obtained from all sources and toe total quantity of water obtained from only non-purchased, surface water
sources is unknown. In such cases. PWS-PCT-SURFACE Identifies a percentage which reflects a relative order of magnitude fl.e., plus or
minus 5%) rather than a precise percentage.
Related percentages should be maintained in the following data elements:
• C123 PWS-PCT-GROUND
• C125 PWS-PCT-PUR-SURFACE
• C127 PWS-PCT-PUR-GROUND
Effective Date 1/31/93
Release Number: 2.00
Page: II- 32
-------
FRDS-ll Data Element Description
Name: PWS-PCT-GROUND
Number C123
• Description
A numeric value that represents the percentage of water delivered to the public that Is obtained from non-purchased ground water sources
used by a public water system.
. PWS-PCT-GROUND Is calculated by dividing the quantity of water obtained from all sources into the quantity of water obtained from only
non-purchased ground water sources, multiplying the result by 100, and rounding the percentage obtained to the nearest whole percent
• Source
• Data Characteristics
FRDS-ll
Form ID:
Data Qualifiers:
Maximum Length
Data Transfer File
-*2_
PWS-ID
_
= J
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: JO
Data Type: INTEGER
Picture: 9(31
NO
Regulation Requirement
Gram Requirement
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an Integer number
• must be between zero and 100, inclusive [EIC]
• the sum of the following data elements should be less than or equal to 100:
. C121 PWS-PCT-SURFACE
. C123 PWS-PCT-GROUND
. C125 PWS-PCT-PUR-SURFACE
. C1Z7 PWS-PCT-PUR-GROUND
• Comments
Often, the total quantity of water obtained from all sources and the total quantity of water obtained from only non-purchased ground water
sources is unknown. In such cases, PWS-PCT-GROUND identifies a percentage which reflects a relative order of magnitude (i.e.', plus or
minus 5%) rather than a precise percentage.
Related percentages should be maintained In the following data elements:
• C121 PWS-PCT-SURFACE
• C125 PWS-PCT-PUR-SURFACE
• C127 PWS-PCT-PUR-GROUND
Effective Date 1/31/93
Release Number 2.00
Page: II-33
-------
FRDS-II Data Element Description
Name: PWS-PCT-PUR-SURFACE
Number.
• Description
A numeric value that represents the percentage of water delivered to the public that Is obtained from purchased surface water sources used
by a public water system.
PWS-PCT-PUR-SURFACE is calculated by dividing the quantity of water obtained from all sources Into the quantity of water obtained from
only purchased surface water sources, multiplying the result by 100. and rounding the percentage obtained to the nearest whole percent
'• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
.A2_
PWS-ID
3
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category:
Data Type: INTEGER
Picture: 9(3)
Registration Requirement •
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must be between zero and 100. inclusive (EIC]
• the sum of the following data elements should be less than or equal to 100:
. C121 PWS-PCT-SURFACE
. C123 PWS-PCT-GROUND
. C125 PWS-PCT-PUR-SURFACE
. C127 PWS-PCT-PUR-GROUND
• Comments
Often, the tola! quantity of water obtained from all sources and the total quantity of water obtained from only purchased surface water sources
Is unknown. In such cases. PWS-PCT-PUR-SURFACE identifies a percentage which reflects a relative order of magnitude (i.e., plus or minus
5%) rather than a precise percentage.
Related percentages should be maintained in the following data elements:
• C121 PWS-PCT-SURFACE
• C123 PWS-PCT-GROUND
• C127 PWS-PCT-PUR-GROUND
Effective Date 1/31/93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Name: PWS-PCT-PURX5ROUND
Number C127
• Description
A numeric vialue thai represents the percentage of water delivered to the public that is obtained from purchased ground water sources used
by a public water system.
PWS-PCT-PUR-GROUND Is calculated by dividing the quantity of water obtained from all sources Into the quantity of water obtained from
only purchased ground water sources, multiplying the result by 100. and rounding the percentage obtained to the nearest whole percent
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: 30
Data Type: INTEGER
Picture: 9f3)
Registration Requirement ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the currant value
When specified:
• must be an integer number
• must be between zero and 100. inclusive [EICJ
• the sum of the following data elements should be less than or equal to 100:
. C121 PWS-PCT-SURFACE
. C123 PWS-PCT-GROUND
. C12S PWS-PCT-PUR-SURFACE
. C127 PWS-PCT-PUR-GROUND
• Comments
Often, the total quantity of water obtained from all sources and (he total quantity of water obtained from only purchased ground water sources
Is unknown. In such cases, PWS-PCT-PUR-GROUND identifies a percentage which reflects a relative order of magnitude (I.e.. plus or minus
5%) rather than a precise percentage.
Related percentages should be maintained In the following data elements:
• C121 PWS-PCT-SURFACE
• C123 PWS-PCT-GROUND
• C125 PWS-PCT-PUR-SURFACE
Effective Date 1/3T/93
Release Number 2.00
Page: 11-35
-------
FRDS-II Data Element Description
Name: PWS-TREATMENT-CLASS
Number C129
• Description
A computed code value that represents whether a public water system's source water is treated, untreated, or mixed (treated and untreated).
Treated Implies that all source water is subjected to treatment
Untreated implies (hat no source water is subjected to treatment
Mixed Implies that multiple sources of water are in use with at least one source of water that Is subjected to treatment and at least one source
of water that is not subjected to treatment.
The term computed, as used here. Implies that this code value Is not reported by the State. PWS-TREATMENT-CLASS Is determined
automatically by the FRDS-II computer system during Its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
"• GENERATED DATA ITEM ••
Data Base Record: C100 PWS-SUMMARY
Data Base FarnUv: ALL
Data Category: 10
Data Type: CHARACTER
Picture: Xm
Registration mquiremer
Grant Requirement
Access:
Code Table ID:
NO
KEY
0129
• Acceptable Values
Entries from the Treatment Class Codes (see Section VI; Table 0129):
•M' - Mixed Treated/Untreated (Some sources have treatment applied but not all)
•N1 - No Treatments Reported .(No sources have any treatments reported)
T - Treated (All sources have treatment applied)
•U1 - Untreated (No sources have treatment applied)
• Comments
The data elements that are considered when this code value is computed are as follows:
• C405 PWS-SE-RECORD-TYPE
• C407 PWS-SE-CODE
. C483 PWS-SE-TREATMENT-OBJECTIVE
. C485 PWS-SE-TREATMENT-PROCESS
Effective Date.
Release Number.
Page: 11-36
-------
FRDS-H Data Element Description Number C131
Name: PWS-SYSTEM-NAME ___
• Description
An alphanumeric value that represents the name of a public water system.
The system name can be the formal, legal, or common name that is used most generally in referring to a public water system
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .A1
Data Qualifiers: PWS-ID
Maximum Length: 40
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: J>1
Data Type: CHARACTER
Picture: XQ01
Registration Requirement ^^_^^_^^_
Grant Requirement YES
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-SYSTEM-NAME identifies the name by which the
system, &s ft whota, is gdnsrdlly known.
PWS-SYSTEM-NAME must be valued for a public water system to be grant eligible.
Effective Date 1/31/93
Release Number: 2.00
Page: II-37
-------
FRDS-II Data Element Description Number C133
Name: PWS-SYSTEM-ADDR-UNE-1
• Description
An alphanumeric value that represents the first line of an address applicable to a public water system.
PWS-SYSTEM-ADDR-UNE-1 can be the name of a responsible person or agency, or It can be an address line applicable to the actual physical
location of a public water system.
• Source
FRDS-II Data Transfer File
Form ID: .A1
Data Qualifiers: PWS-1D
Maximum Length: _40_
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base Familv: ALL
Data Cateaorv: 01
Data Type: CHARACTER
Picture: XM
Registration Requirement
Grant Requirement:
ACOQBfi*
Code Table ID:
.
NO
NON-KEY
N/A
• Comments
Where multiple facilities exist tor a public water system at different physical locations, PWS-SYSTEM-ADDR-UNE-1 Identifies the responsible
person, agency, or address information that is applicable to the location of the primary facility of the system.
This address line should be specified only as needed. If a responsible person or agency Is unavailable and the i
a single line. C135. PWS-SYSTEM-ADDR-UNE-2 is used.
Other parts of the system address are maintained in the following data elements:
• C135 PWS-SYSTEM-ADDR-UNE-2
• C137 PWS-SYSTEM-CITY
• • C139 PWS-SYSTEM-STATE
• C141 PWS-SYSTEM-ZIP
iddress
sis of
Effective Date 1/31/93
Release Number: 2.00
Page: II-
-------
FRDS-II Data Element Description Number. C13S
Name: PWS-SYSTEM-ADDR-UNE-2
• Description
An alphanumeric value that represents the second line of an address applicable to a public water system.
PWS-SYSTEM-ADDR-UNE-2 is the street address, rural route, etc.. that is applicable to the actual physical location of a public water system
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .A]
Data Qualifiers: PWS-ID
Maximum Length: 40
Data Base Record: C100 PWS-SUMMARY
Data Base Family ALL
Data Cateoorv: 01
Data Type: CHARACTER
Picture: X(30)
Grant Requirement
Access:
Code Table ID:
•
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
e Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-SYSTEM-ADDR-UNE-2 Identifies the address
Information that Is applicable to the location of the primary facility of the system.
Since this value should represent the actual, physical location of the public water system, post office box and other non-locational
designations should not be used.
Other parts of the system address are maintained In the following data elements:
• C133 PWS-SYSTEM-ADDR-UNE-1
• C137 PWS-SYSTEM-CITY
• C139 PWS-SYSTEM-STATE
• C141 PWS-SYSTEM-ZIP
Effective Date: 1/31/93
Release Number: 2.00
Page: 11-39
-------
FRDS-II Data Element Description
Name: PWS-SYSTEM-CrTY
Number C137
• Description
An alphanumeric value that represents the city in which a public water system is physically located.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: A1
Data Qualifiers: PWS-ID
Maximum Length: 40
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: . .01
Data Type: CHARACTER
Picture: X(15)
Registration Requirement *
Grant Requirement YES
Access: KEY
Code Table ID: N/A
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
e Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-SYSTEM-CITY identifies the city which is applicable
to the physical location of the primary facility of the system.
Other parts of the system address are maintained in the following data elements:
• C133 PWS-SYSTEM-ADDR-LINE-1
• C135 PWS-SYSTEM-ADDR-UNE-2
• C139 PWS-SYSTEM-STATE
• C141 PWS-SYSTEM-ZIP
PWS-SYSTEM-CITY must be valued for a public water system to be grant eligible.
Effective Date 1/31/93
Release Number 2.00
Page: II-40
-------
FRDS-II Data Element Description
Name: PWS-SYSTEM-STATE
Number. C139
• Description
A code value that represents the U.S. Postal Service (USPS) State abbreviation in which a public water system to physically located.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
A1
PWS-ID
£
Data Base Record: C100 PWS-SUMMARY
Data Base Famllv: ALL
Data Cateaorv: 10
Data Type: CHARACTER
Picture: Xffil
Grant Requirement
Access:
Code Table ID:
YES
NON-KEY
ID02
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the USPS Postal State Codes (see Section VI; Table ID02)
• should be the same as position 1 - 2 of C101. PWS-ID. (unless the system is under EPA regional primacy)
Additionally, within an address, the State code and position 1 of the USPS ZIP Code must agree [E9B]
e Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-SYSTEM-STATE identifies the USPS
abbreviation which Is applicable to the physical location of the primary facility of the system.
OlhGf ports of ths system oddress BTB irutint&fnsd In 1h6 following dflt& slsntonts*
• C133 PWS-SYSTEM-ADDR-UNE-1
• C13S PWS-SYSTEM-ADDR-UNE-2
• C137 PWS-SYSTEM.CrTY
• C141 PWS-SYSTEM-ZIP
PWS-SYSTEM-STATE must be valued tor a public water system to be grant eligible.
Effective Date 1/31/93
Release Number 2.00
Page: 11-41
-------
FRDS-II Data Element Description
Name: PWS-SYSTEM-ZIP
Number C141
• Description
An alphanumeric value that represents the U.S. Postal Service (USPS) ZIP code In which a public water system Is physically located.
PWS-SYSTEM-ZIP is of the form: zzzzzeeee (space Inserted tor dartty only)
Where:
the ZIP code
the ZIP+4 optional ZIP code extension
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .A1
Date Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Date Category: 70
Date Type: CHARACTER
Picture: X(5)
Registration Requirement j
Grant Requirement YES
Access: KEY
Code Table ID: N/A
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be a 5 or 9 digit integer number
• must be greater than zero
Additionally, within an address, the State code and position 1 of the USPS ZIP Code must agree [EBB]
e Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-SYSTEM-ZIP Identifies the ZIP code which is
applicable to the physical location of the primary facility of the system.
Other parts of the system address are maintained in the following date elements:
• C133 PWS-SYSTEM-ADDR-LINE-1
• C135 PWS-SYSTEM-ADDR-UNE-2
• C137 PWS-SYSTEM-CITY
• C139 PWS-SYSTEM-STATE
PWS-SYSTEM-ZIP must be valued for a public water system to be grant eligible.
Effective Date. 1/31/93
Release Number:
Page: 11-42
-------
FRDS-II Data Element Description
Name: PWS-PHONE
Number C143
• Description
An alphanumeric value that represents the telephone number of a public water system or the system's primaiy contact
PWS-PHONE is of the town: aaaeeennnn (spaces inserted for clarity only)
aaa B the telephone area code
eee = the telephone exchange
nnnn • the telephone number
• Source
e Data Characteristics
FRDS-II Data Transfer I
Form ID: .A1
Data Qualifiers: PWS-ID
Maximum Length: 10
Data Base Record: C100 PWS-SUMMARY
Data Base Familv: ALL
Data Cateoorv: 71
Data Type: CHARACTER
Picture: X(10)
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• !•>•»•Jflurl
specrneu.
must be an alphanumeric value
positions 1 through 3 (i.e.. area code) should be valid for the system state (i.e.. C139. PWS-SYSTEM-STATE) If a a
number is specified
nplete telephone
• .Comments
Where multiple facilities exist for a public water system at different physical locations. PWS-PHONE identifies the telephone number which •
Is applicable to the primary facility of. or the principal contact for, the system.
Effective Date. 1/31/93
Release Number 2.00
Page: 11-43
-------
FRDS-II Data Element Description
Name: PWS-METERS
Number C145
• Description
A numeric value that represents the number of water meters that a public water system had attached to Its retail service connections in the
most recent year.
• Source *" NOT ON INPUT FORM •••
• Data Characteristics
FRDS-H Data Transfer File
Form ID: A2
Data Qualifiers: PWS-IP
Maximum Length: 7
Data Base Record: C100
Data Base Familv: ALL
Data Category: 30
DataTwe: INTEGER
Picture: 9m
PWS-SUMMARY
RBQIStTBtlOn ROQUlrBIDO
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• should be less than or equal to the number of service connections (C147. PWS-SERVICE-CONNECTtONS)
• Comments
Although this data is maintained in the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form for Its input
Updates to this data can be made only through the submission of new or corrected values via the FRDS-II Data Transfer File (DTP) format
Effective Date 1/31/93
Release Number. 200
Page:
-------
FRDS-II Data Element Description Number C147
Name: PWS-SERVICE-CONNECTIONS
• Description
A numeric value that represents the number of retail service connections that a public water system had in the most recent year.
In general, a service connection to the point at which the water distribution system pipe connects to a water meter in a building, home, or
the like. This explanation to not completely comprehensive, however, since water meters are not always utilized. The following example best
Illustrates this factor.
• An apartment building that pays a single water bill for all of its residents (regardless of the number of residents) is said to have a single
• A duplex, whose 2 residents each pay thetr own water bill, is said to have 2 service connections
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: .A2
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL Registration Requirement: _2_
Data Category: JO Grant Requirement YES
Data Type: INTEGER Access: KEY
Picture: 9(7) Code Table ID: N/A
• Edit Criteria
Must be specified when:
• Inserting an inventory record
• modifying the current value
UA«MM fiw^tuj^Kmtt
wnen specrneo.
• must be an integer number
• must not be a negative number [EGA]
• must be greater than zero when the Public Water System is not a wholesaler of water ("'••-. no occurrence of C603,
PWS-SERV-CATEGORY to 'O3f) [EGCJ
• should be greater than or equal to the number of meters (C14S. PWS-METERS)
• should be greater than or equal to 15 when the retail population served (C117. PWS-RETAIL-POP-SERVED) to less than 25 (unless
the PWS to a wholesaler of water)
•' Comments
Generally speaking, there are approximately 3.5 persons served per each retail service connection.
PWS-SERVICE-CONNECTIONS must be valued for a new public water system to be inserted Into the FRDS-II Data Base. Additionally, a
public water system must have 15 or more service connections, or serve 25 or more persons to be grant eligible (unless they are identified
as "wholesalers of water*).
Effective Date 1/31/93 Release Number ^00 Page: II - 45
-------
FRDS-II Data Element Description
Name: PWS.AVG-DAILY.PROD
Number C149
• Description
A numeric value that represents the average daily quantity of water that was produced by a public water system in the most recent year.
The unit of measurement for PWS-AVG-DA1LY-PROD is gallons per day.
PWS-AVG-DAILY-PROD is calculated by adding together the total gallons of water produced In a year by each treatment or pumping faddy.
and dividing that sum by the total number of days that at least one treatment or pumping facility was in operation.
• Source "• NOT ON INPUT FORM
e Data Characteristics
FRDS-ll Data Transfer File
Form ID: .A2
Data Qualifiers: PWS-IP
Maximum Length: 10
Data Base Record: CfOO
Data Base Family: ALL
Date Category: 30
Data Type: INTEGER
Picture: 9(10)
PWS-SUMMARY
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• should be less than or equal to C157. PWS-MAX-DAILY-PROD
• Comments
Although this data is maintained in the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form for Its Input
Updates to this data can be made only through the submission of new or corrected values via the FflDS-JI Data Transfer File (DTF) formal
Other capacity information is maintained in the following data elements:
• C1S1 PWS-TOT-DESIGN-CAPACITY
• C153 PWS-TOT-EMERGENCY-PROD
• C155 PWS-TOT-STORAGE-CAPACITY
• C157 PWS-MAX-DAILY-PROD
Treatment and pumping facilities are also known in FRDS-II as entities.
Effective Date. 1/31/93
Release Number: 2.00
Page1
-------
FRDS-II Data Element Description Number C151
Name: PWS-TOT-DESIGN-CAPACITY
• Description
A numeric value that represents the total quantity of water that a public water system was designed and approved to produce.
The unit of measurement tor RVVS-TOT-OESIGN-CAPACITY is gallons per day.
PWS-TOT-DESIGN-CAPACITY is calculated by adding together the approved design capacity of each treatment or pumping facility.
• Source
NOT ON INPUT FORM '
e Data Characteristics
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length: 10
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: JO
Data Type: INTEGER
Picture: 9(10)
Registration Requirement *
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
e Comments
Although this data is maintained in the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form forte input
Updates to this data can be made only through the submission of new or corrected values via the FRDS-II Data Transfer Rle (DTP) formal
nts:
Other capacity information Is maintained in the following data derm
* C149 PWS-AVG-DAILY-PROD
. • C153 PWS-TOT-EMERGENCY-PROD
• C155 PWS-TOT-STORAGE-CAPACrTY
• C1S7 PWS-MAX-DAILY-PROD
Treatment and pumping facilities are also known In FRDS-II as entitles.
Effective Date 1/31/93
Release Number: 2.00
Page: 11-47
-------
FRDS-II Data Element Description Number C153
Name: PWS-TOT-EMERGENCY-PROD
• Description
A numeric value that represents the total quantity of water that can be produced by a public water system using emergency power generation
equipment under Ms control.
The unit of measurement for PWS-TOT-EMERGENCY-PROD is gallons per day.
PWS-TOT-EMERGENCY-PROD is calculated by adding together the emergency power production capacity of each treatment or pumping
facility.
• Source
NOT ON INPUT FORM '
• Data Characteristics
FRDS-II Data Transfer File
Form ID: J£
Data Qualifiers: PWS-ID
Maximum Length: JO
Data Base Record: C100 PWS-SUMMARY
Data Base Family
Data Category:
Data Type: INTEGER
Picture: 9(10)
ALL
30
Registration Requirement: ^^^^_^^^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when-
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• should be less than or equal to the maximum daily production (C157. PWS-MAX-DAILY-PROD)
• Comments
Although this data Is maintained In the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form for Its Input
Updates to this data can be made only through the submission of new or corrected values via the FRDS-II Data Transfer Flle.(DTF) formal
Other capacity information is maintained in the following data elements:
• C149 PWS-AVG-DAILY-PROD
• C151 PWS-TOT-DESIGN-CAPACITY
• C155 PWS-TOT-STORAGE-CAPACITY
• C157 PWS-MAX-DAILY-PROD
Treatment and pumping facilities are also known in FRDS-II as entities.
Effective Date- 1/31/93
Release Number. 2.00
Page: Jl
-------
FRDS-II Data Element Description Number C155
Name: PWS-TOT-STORAGE-CAPACITY
• Description
A numeric value that represents the total quantity of water that can be stored by a public water system.
The unit of measurement for PWS-TOT-STORAGE-CAPACITY is gallons.
PWS-TOT-STORAGE-CAPACrTY is calculated by adding together the storage capacity of each water storage facility.
• Source ••• NOT ON INPUT FORM •••
• Data Characteristics
FRDS-II Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length: JO
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: JO
Data Type: INTEGER
Picture: 9(1ffl
Registration Requbomont
Grant Requirement
Access:
Code Table ID:
NON-KEY
N/A
• Edrt Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• Comments
Although this data is maintained In the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form for its Input
Updates to this data can be made only through the submission of new or corrected values via the FRDS-II Data Transfer File (DTP) format
Other capacity Information is maintained in the following data elements:
• C149 PWS-AVG-DAILY-PROD
. . C151 PWS-TOT-DESIGN-CAPACITY
• C153 PWS-TOT-EMERGENCY-PROD
• C1S7 PWS-MAX-DAILY-PROD
Water storage facilities are also known in FRDS-II as entities.
EttectrveDate 1/31/93
Release Number 2.00
-------
FRDS-II Data Element Description
Name: PWS-MAX-DAILY-PROD
Number C157
• Description
A numeric value lhat represents the maximum daily quantity of water that can be produced by a public water system.
The unit of measurement for PWS-MAX-DAILY-PROD is gallons per day.
PWS-MAX-DAILY-PROD is calculated by adding together the maximum daily production capacity of each treatment or pumping facility.
• Source
NOT ON INPUT FORM *••
e Data Characteristics
FRDS-II Data Transfer File
Form ID: .A2
Data Qualifiers: PWS-ID
Maximum Length: 10
Data Base Record: C100 PWS-SUMMARY
Data Base Family:
Data Category:
Data Type: INTEGER
Picture: 9(10)
ALL
30
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must not be a negative number [EGA]
• should be greater than or equal to the average daily production (C149. PWS-AVG-DAILY-PROD)
• should be greater than or equal to the total emergency production (C153. PWS-TOT-EMERGENCY-PROD)
e Comments
Although this data is maintained In the FRDS-II Data Base, no provision has been made on any FRDS-II data capture form for Us Input
Updates to this data can be made only through the submission of new or corrected values via the FRDS-II Data Transfer File (DTP) formal
Other capacity information is maintained in the following data elements:
• C149 PWS-AVG-DAILY-PROD
• C151 PWS-TOT-DESIGN-CAPACITY
• C153 PWS-TOT-EMERGENCY-PROD
• C155 PWS-TOT-STORAGE-CAPACITY
Treatment and pumping facilities are also known in FRDS-II as entities.
Effective Date: 1/31/93
Release Number: 2.00
Page:
-------
FHDS-II Data Element Description Number
Name: PWS-SEASON-BEGIN-MMDD
• Description
A numeric value that represents the calendar month and day on which a Non-transient Non-community or a Transient Norvcommunity public
water system's season of operation commences.
PWS-SEASON-BEGIN-MMDDisoftheform: mmdd (space Inserted tor clarity only)
Where: mm = the calendar month In which a Non-transient Non-community or a Transient Non-community public water system commences
operation
dd ° the day of the month on which a Non-transient Non-community or a Transient Non-community public water system commences
• Source
• Data Characteristics
FRDS-II Data Transfer File
FOrm ID: A2
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL Registration Requirement ^
Data Category: .62 Grant Requirement COND
Data Type: INTEGER Access: NON-KEY
Picture: 9(4) Code Table ID: N/A
• Edit Criteria
Must bs spocffiod whsni
• modifying Ih6 current v&luo
• not presently valued and the season end date (C161, PWS-SEASON-END-MMDD) has been specified
Must not be specified when Inserting or modifying a community water system (i.e.. C105. PWS-TYPE or fC") (EXE]
When specified:
• must be a four digit numeric calendar date, comprised of.
. month. In position 1 • 2i and
. day of the month, in position 3-4
• Comments
PWS-SEASON-BEGIN-MMDD is not applicable to Community water systems.
The ending date of a Norvcommunity system's season is maintained in data element C161. PWS-SEASON-END-MMDD.
When e Non-transient Non-community or a Transient Non-community public water system to changed to a Community public water system,
PWS-SEASON-BEGIN-MMDD will automatically be initialized to a -null- value.
A Non-community (Non-transient and transient) public water system must operate for a minimum period of time (as defined by the season
begin and end dates) to be grant eligible. The minimum period of time Is:
• 60 days for a Transient Non-community public water system; or
• 180 days for a Non-transient Non-community public water system.
Effective Date 1/31/93
Re)
Number: 2.00
Page: 11-51
-------
FRDS-II Data Element Description Number. C161
Name: PWS-SEASON-END-MMDD
• Description
A numeric value that represents the calendar month and day on which a Non-transient Norvcommunity or a Transient Norvcommurtty public
water system's season of operation ceases.
PWS-SEASON-END-MMDDisoftheform: mmdd (space Inserted for darity only)
Where: mm * the calendar month in which a Non-transient Non-community or a Transient Nornwrnmunlty public water system ceases
operation
dd = the day of the month on which a Non-transient Non-community or a Transient Non-community public water system
operation
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: .A2
Data Qualifiers: PWS-ID
Maximum Length: _4_
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL Registration Requirement
Data Category: 62 Grant Requirement COND
Data Type: INTEGER ' Access: NON-KEY
Picture: 9(4) Code Table ID: N/A
Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the season begin date (C159. PWS-SEASON-BEGIN-MMDD) has been specified
Must not be specified when inserting or modifying a community water system (i.e.. C105. PWS-TYPE or 'CT [EXE]
When specified:
• must be a four digit numeric calendar date, comprised of.
. month, in position 1 - 2. and
. day of the month, in position 3 - 4
e Comments
PWS-SEASON-END-MMDD is not applicable to Community water systems.
The beginning date of a Non-community system's season is maintained in data element C159. PWS-SEASON-BEGIN-MMDD.
When a Non-transient Non-community or a Transient Non-community public water system Is changed to a Community public! water system.
PWS-SEASON-END-MMDD will automatically be initialized to a -null- value.
A Non-community (Non-transient and transient) public water system must operate for a minimum period of time (as defined by the season
begin and end dates) to be grant eligible. The minimum period of time is
• 60 days for a Transient Non-community public water system; or
• 180 days for a Non-transient Non-community public water system.
Effective Date 1/31/93 Release Number: 2.00 Page.
-------
FRDS-II Data Element Description
Name: PWS-OWNER-TYPE
Numbsr
• Description
A code value that identifies the type of owner of a public water system.
Examples of PWS-OWNER-TYPE Include owner's such as a city, a county, a State, the Federal government, an Investor, a licensed public
utility, etc.
• Source
FRDSm Data Transfer File
Form ID: A2
Data Qualifiers: PWS-ID
Maximum Length:
e Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: 10
Data Type: CHARACTER
Picture: XH1
Registration Requirement:
Grant Requirement
Access:
Code Table ID: 0163
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the PWS Owner Type Codes (see Section VI; Table 0163):
•+• - Not Reported by State .(>' may not be used on any FRDS-H input transaction. It was
assigned by the FRDS-II computer system during the conversion of
data from FRDS 1.5 to FRDS-II.)
•V - Federal Government
•2-' • Private (SuMwisions. InvestedJrusts. Cooperatives, WaterAsscdations.eteO
•3* - State Government
•4* - Local Government v. (Authorities. Commissions, Districts, Municipalities. Cities, Towns,
Counties, etc.)
- Mixed Public/Private
•51
•ff
- Native American (Indian Tribes & Reservations. Alaska Remote Villages)
e Comments
None
Effective Date 1/31/93
Release Number. 2.00
Page: II-S3
-------
FRDS-II Data Element Description
Number
Name: PWS-REGULATING-ENTITY
• Description
A code value that represents whether a public water system is regulated by Federal. State, both Federal and State, or neither Federal nor
Slate drinking water regulations.
• Source
Data Characteristics
FRDS-II Data Transfer File
Form ID: J&
Data Qualifiers: PWS-ID
Maximum Length:
Data Base Record: C100 PWS-SUMMARY
Data Base Family: ALL
Data Category: .10
Data Type: CHARACTER
Picture: XM»
Registration Requirement -
Grant Requirement: NO
Access: NON-KEY
Code Table ID: 0165
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Regulating Entity Codes (see Section VI; Table 0165):
•B' - Both State & Federal Governments
•P - Federal Government Only
•N1 - Neither State nor Federal Govt.
*S* - State Government Only
• Comments
None
Effective Date. 1/31/93
Release Number: 200
Page: 11-54
-------
FRDS-II Data Element Description
Number C167
Name: PWS-INV.LAST-UPDATE
• Description
A computed value that represents the calendar date on which a public water system was initially posted to the FRDS-II Data Base or when
a subsequent State-supplied Inventory modification was made.
ds
TWs date applies to any update posted to any data element contained in any of the following data base
C100 PWS-SUMMARY
C300 PWS-ADDRESS-DATA
. C400 PWS-SOURCE-ENTJTWNFO
C480 PWS-SE-TREATMENT-DATA
' C500 PWS-GEOGRAPHIC-AREAS-SERVED
C600 PWS-SERV1CE-AREAS
C700 PWS-ON-SrTE-VISITS
C800 PWS-MILESTONES-EVENTS
C4000 STATE-DISCRETIONARY-DATA
The term update, as used here. Includes any additions, modifications, or deletions made to any inventory data In the FRDS-II Data
thte public water system.
for
The term computed, as used here. Implies that this date Is not reported by the State. PWS-INV-LAST-UPDATE Is determined automatically
by the FRDS-II computer system during Its normal course of operation when a new public water system Is Inserted into the FRDS-II Data Base
or when any Inventory data Is subsequently modified.
• Source
• Data Characteristics
FRDS-II Data Transfer File
"•• GENERATED DATA TTEM •••
Data Base Record: C100 PWS-SUMMARY
Data Base Family:
Data Category:
Data Type: DATE
Picture: MMDDYY
ALL
60
Registration Requirement ^
Grant Requirement
Access:
Code Table ID:
NO
KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of.
montti, In position 1-2;
day. m position 3 • 4; and
year. In position 5 - 6
e Comments
This data Is changed for State
sported updates only (i.e., updates submitted via DTP transactions).
Other last update dates are maintained in the folio
C7 ST-ANY-DATA-LAST-UPDATE
C9 SMNV-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
C1S ST-ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
ring data
C29 ST-SAMPLE-LAST-UPDATE
C169 PW&ANY-DATA-LAST-UPDATE
C1133 VIO-LAST-UPDATE
C1207 ENF-LAST-UPDATE
C3021 VE-LAST-UPDATE '
Effective Date- 1/31/93
Release Number 2.00
Page: 11-55
-------
FRDS-II Data Element Description
Name: PWS-INSERT-DATE
Number C168
• Description
A computed value that represents the calendar date on which a public water system was Initially posted to the FRDS-II Data Base.
The term computed, as used here. Implies that this date is not reported by the State. PWS-INSERT-DATE Is dete
ally by
the FRDS-II computer system during Its normal course of operation when a new public water system Is Inserted Into the FRDS-II Data Base.
Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM •"
Date Base Record: C100
Date Base Family: ALL
Date Category: 60
Date TVDB: DATE
Picture: MMDDYY
PWS-SUMMARY
Registration Requiremer
Grant Requirement
Access:
Code Table ID:
£
NO
NON-KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, In position 1 - 2;
day. in position 3 - 4; and
year, in position 5 - 6
• Comments
This date is valued tor State reported data only (i.e., date submitted via DTP transactions).
Other insert dates are maintained in the following date elements:
• C811 PWS-MILESTONE-INSERT-DATE
• C1117 VIO-INSERT-DATE
C1213 ENF-INSERT-DATE
C3033 VE-INSERT-DATE
Effective Date: 1731/93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Number C189
Name: PWS-ANY-DATA-LAST-UPDATE
• Description
A computed value that represents the most recent calendar date on which an update was posted to any Inventory, violation, entoroement
action, sample, or variance/exemption/bther data in the FRDS-II Data Base for this public water system.
Thte date applies to any update posted to any data eler
C100 PWS-SUMMARY
C300 PWS-ADDRESS-DATA
. C400 PWS-SOURCE-ENTITY-INFO
C480 PWS-SE-TREATMENT-DATA
C500 PWS-GEOGRAPHIC-AREAS-SERVED
C600 PWS-SERV1CE-AREAS
C700 PWS-ON-SITE-VISrrS
C800 PWS-MILESTONES-EVENTS
C1100 VIOLATION-DATA
C1180 V1O-ENFORCEMENTS
into
ntained In any of (he following data base records:
• C1200 ENFORCEMENT-DATA
• C1280 ENF-VIOLATIONS
• C2100 SAMPLE-DATA
• C3000 VARIANCE-EXEMPTION-DATA
• C3100 VE-SCHEDULE
• C4000 STATE-DISCREDONARY-DATA
The term update, as used here, includes any additions, modifications, or deletions made to any inventory, violation, enforc
sample, or variance/exemption/other data In the FRDS-II Data Base for this public water system.
mt action.
The term computed, as used here, implies that this date Is not reported by the State. PWS-ANY-DATA-LAST-UPDATE Is determined
automatically by die FRDS-II computer system during Its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM '
Data Base Record: C100 PWS-SUMMARY
Data Base Famflv: ALL
Data Category: jjfj
Data Tvoe: DATE
Picture: MMDDYY
mgtstraoon Hequiremer
Grant Requirement
Access:
Code Table ID:
it -
NO
KEY
N/A
• Acceptable Values
A six digit numeric calendar data, comprised of:
month, in position 1 - 2;
day, In position 3 - 4; and
year, in position 5-6
• Comments
This date to changed for State reported updates only (i e.. updates submitted via DTP transactions).
Other dates of last update are maintained in the following data elements:
C7 ST-ANY-DATA-LAST-UPDATE
C9 ST-INV-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
C1S ST-ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-INV-LAST-UPDATE
C1133 VIO-LAST-UPDATE
C1207 ENF-LAST-UPDATE
C3021 VE-LAST-UPDATE
Effective Date 1/31/93
Release Number. 2.00
Page: Jl
-------
FRDS-N Data Element Description
Name: PWS-RECON-FLAG
Number C171
• Description
A computed code value that represents whether or not an update has been performed to the FRDS-1I Data Base for a public water system
which necessitates the recalculation of any of the various data elements whose values are maintained (La-, computed) by the FRDS-II
computer system.
The term computed, as used here. Implies that this code value Is not reported by the State.
PWS-RECON-FLAG is determined automatically by the FRDS-tl computer system during its normal course of operation.
• Source
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
• Data Characteristics
Data Base Record: C100 PWS-SUMMARY
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: XM)
10
RegBlration Requirement •
Grant Requirement NO
Access:
Code Table ID:
KEY
0171
• Acceptable Values
Entries from the PWS Reconciliation Flag.Codes (see Section VI; Table 0171):
•N1 - Reconciliation NOT Needed for PWS
-V - Reconciliation Needed for PWS
• Comments
Other reconciliation flags are maintained in the following data elements:
• C19 ST-RECON-FLAG
• C1001 NCD-RECON-FLAG
Effective Date: 1/31/93
Release Number: 200
Page:
-------
FRDS-II Data Element Description
Name: PWS-FYNN-TRACKER
Number C173
• Description
A computed value that represents the Federal fiscal year(s) hi which the associated public*
submitted.
PWS-FYNN-TRACKER is of the format >FYxxFYzz...FYnn>. where lof, W, and Yin' represer
system was reported to EPA (Note: only the most recent 15 Federal fiscal years are saved).
Btersystt
t Federal i
i included in the Slate's inventory
al years In which the public water
Each subsequent Federal fiscal year in which the public water system is reported Is corxatenated to the other Federal fiscal years in this data
element In descending order. For example. If a public water system is first reported in FY88. then in the next five consecutive Federal fiscal
years. PWS-FYNN-TRACKER would contain:
FY88FY89FY90FY91FY92
If the public water system Is reported again in Federal fiscal year 93. PWS-FYNN-TRACKER would be updated to contain:
FY88FY89FY90FY91FY92FY93
The term computed, as used here. Implies that this date Is not reported by the State. PWS-FYNN-TRACKER Is determined automatically by
the FRDS-II computer system during Its normal course of operation whenever a public water system is included In a State's inventory
submittal.
e Source
e Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM
Data Base Record: ClOO PWS-SUMMARY
Data Base Family: ALL
Data Category: J)l
Data Type: CHARACTER
Picture: X(60)
Registration Requirement ^
Grant Requirement: NO
Access: NON-KEY
Code Table ID: N/A
e Acceptable Vajues
An alphanumeric value
• Comments
This date element is the means by which a user can determine the specific Federal fiscal year(s) in which the public water system was
reported to EPA
Effective Date: 1/31/93
Release Number: 2.00
Page: 11-59
-------
FRDS-II Data Base Record Description Number C300
Name: PWS-ADDRESS-DATA .
• Description
A SYSTEM 2000 data base record identification number and name.
The C300. PWS-ADDRESS-DATA. data base record contains data elements that are related to a public water system's addressees and/or
facilities.
It is important to note that the term, -public water system's addressees' exdudes the system nanw ami address, which is rnalntalned In data
elements C131 through C141.
-The FRDS-II Data Base has one PWS-ADDRESS-DATA data base record for each addressee and facility related to a public water system that
has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: J Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C301 PWS-AD-ID • C309 PWS-AD-ADDR-UNE-2
• C303 PWS-AD-TYPE . C311 PWS-AD-CITY
• C305 PWS-AD-NAME • C313 PWS-AD-STATE
• C307 PWS-AD-ADDR-LINE-1 • C315 PWS-AD-ZIP
• Comments
Each data element name contained within the PWS-ADDRESS-DATA data base record is prefaced with: PWS-AD- At least one of the above
data elements other than C301 must be valued to have this data base record accepted by FRDS-II.
Effective Date- 1/31/93 Release Number: 200 Page: II-60
-------
FRDS-II Data Element Description
Name: PWS-AD-ID
Number C301
• Description
A numeric value used to uniquely Identify a specific addressee of. or a facility related to. a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
A3
PWS-ID
PWS-AD-ID
J
Data Base Record: C300 PWS-ADDRESS-DATA
Data Base Family: J
Data Category: 20
Data Type: INTEGER
Picture: 9(1)
NO
Registration Requirement
Grant Requirement
Access:
Code Table ID: N/A
NON-KEY
• Edit Criteria .
Must be specified when:
• Inserting, modifying or deleting an address record
Wnen specified:
• position i must be 'G' or numeric
• position 1 must not be 'G* In when modifying or deleting an address record
• and position 11s •G*:
. position 2 must be numeric
. position 3 - 7 must be blank
• and position 1 is not 'GV
. position 1 must be numeric
. position 2 - 7 must be blank
. the ID must exist in the FRDS-II data base tor the PWS. when modifying or deleting an address record
. the ID must not exist in the FRDS-II data base for the PWS, when inserting an address record
Each new address record must include values for those data elements within the address record (C300. PWS-ADDRESS-DATA) that are
Identified as Registration Requirement data elements (see 'Data Characteristics' on this page) [ERR]
Additionally, at least one address data element (i.e.. C305, PWS-AD-NAME; C307. PWS-AD-ADDR-UNE-1; C309. PWS-AD-ADDR-UNE-2; C311.
PWS-AD-CITY; C313. PWS-AD-STATE; or C315. PWS-AD-ZIP) must be valued [E6F]
• Comments
N desired, the user can have the FRDS-II computer system generate a PWS-AD-ID number by specifying a Group Generation Code (GGC)
when a new address data base record is to be inserted into the data base. This is accomplished by substituting the GGC for an actual ID
(I.e. Gn. where ... the letter 'G' tells FRDS-II to generate the ID and the "n1 is an arbitrary number assigned to all related C300,
PWS-ADDRESS-DATA. data elements so that their logical grouping wBI remain Intact).
PWS-AD-ID must be valued for a new PWS-ADDRESS-DATA data base record to be inserted Into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number: 2.00
Page: II-61
-------
FRDS-II Data Element Description
Name: .PWS-AD-TYPE
Number. C303
• Description
A code value that represents the type of addressee or facility of a public water system.
Examples of PWS-AD-TYPE include addressee's such as an owner, a treatment facility operator, a primary point of contact, etc.
Other examples of PWS-AD-TYPE include facilities (entities) such as a treatment facility, a pumping facility, a water storage facility, etc.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form 10: .A3
Data Qualifiers: PWS-ID
PWS-AD-ID
Maximum Length:
Data Base Record: C300
Data Base Family: 1
Data Category: 10
Data Type: CHARACTER
Picture: X(l)
PWS-ADDRESS-DATA
NO
Registration Requirement
Grant Requirement
Access:
Code Table ID: , 0303
KEY
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Addressee Type Codes (see Section VI; Table 0303):
•D1 - Distribution Facility
•£• - Employee
V - Laboratory
•M1 -- Mailing
•O' - System Owner/Responsible Party
•P' - Pumping Facility
•R' • Operator
•S* - Storage Facility
T - Water Treatment Plant/Facility
V • Vendor
•X1 - Other
• Comments
If a new PWS-ADDRESS-DATA record Is Inserted into the FRDS-II Data Base and PWS-AD-TYPE is not supplied by the State. PWS-AD-TYPE
will be assigned a value of TC (i.e., Other).
Effective Date: 1/31/93
Release Number: 2.00
Page: II-62
-------
FRDS-II Data Element Description
Name: PWS-AD-NAME
Number. C30S
• Description
An alphanumeric value that represents the name of an addressee or facility associated with a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
A3
PWS-ID
PWS-AD-IO
JS_
Data Base Record: C300 WS-ADDRESS-DATA
Data Base Family:
Data Category.
Data Type: CHARACTER
Picture: X(30)
1
01
Registration Rectulrement -
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Effective Date. 1/31/93
Release Number 2.00
Page: 11-63
-------
FRDS-II Data Element Description
Name: PWS-AD-ADDR-LINE-1
Number C307
• Description
An alphanumeric value that represents the first line of an address applicable to a public water system addi
PWS-AD-ADDR-LINE-1 can be the name of a responsible person or agency, or It can be an additional address line applicable to the location
of a public water system addressee or facility.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .A3
Data Qualifiers: PWS-ID
PWS-AD-ID
Maximum Length:
Data Base Record: C300 PWS-ADDRESS-DATA
Data Base Family: J
Data Category: 01
Data Type: CHARACTER
Picture: XM)
Registration Requiremer
Grant Requirement:
Access:
Code Table ID:
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
This address line should be specified only as needed.
a single line. C309. PWS-AD-ADDR-UNE-2 is used.
If a responsible person or agency Is unavailable and the street address consists of
Other addressee or facility related address data elements are maintained in the following data elements:
• C309 PWS-AD-ADDR-UNE-2
• C311 PWS-AD-CrrY
• C313 PWS-AD-STATE
• C315 PWS-AD-ZIP
Effective Date: 1/31/93
Release Number: 2.00
Page: Jl
-------
FRDS-II Data Element Description
Name: PWS-AD-ADDR-UNE-2
Number
• Description
An alphanumeric value that represents the second line of an address applicable to a public water system add
or facility.
PWS-AD-ADDR-UNE-2 is the street address, rural route and box designation, etc.. that is applicable to the location of a public water syste
addressee or facility.
• -Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: A3
Data Qualifiers: PWS-ID
PWS-AD-ID
Maximum Length:
Data Base Record: C300 PWS-ADDRESS-DATA
Data Base Famllv: 1
Data Cateoorv: 01
Data Type: CHARACTER
Picture: X(30)
mgisraoon mquramer
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying ihe current value
When specified:
• must be an alphanumeric value
• Comments
Other add
• C307
• C311
• C313
or facility related address data elements are maintained In the following data elements:
PWS-AD-ADDR-LINE-1
PWSAD-CITY
PWS-AD-STATE
• C315 PWS-AD-ZIP
Effective Date. 1/31/93
Release Number: 2.00
Page: II-65
-------
FRDS-II Data Element Description
Name: PWS-AD-CITY
Number C311
• Description
An alphanumeric value that represents the city in which a public water system addressee or facility is located.
e Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: .A3
Data Qualifiers: PWS-ID
PWS-AD-ID
Maximum Length: 40
Data Base Record: C300 PWS-ADDRESS-DATA
Data Base Family: J
Data Category: J)l
Data Type: CHARACTER
Picture: X(1S)
Registration Requirement: •
Grant Requirement NO
KEY
Code Table ID:
N/A
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Other addressee or facility related address data elements are maintained in the following data elements:
• C307 PWS-AD-ADDR-UNE-1
• C309 PWS-AD-ADDR-UNE-2
• C313 PWS-AD-STATE
• C315 PWS-AD-ZIP
Effective Date 1/31/93
Release Number. 200
Page:
-------
FRDS-II Data Element Description
Name: PWS-AP-STATE
Number C313
• Description
A cod* value that represents the U.S. Postal Service (USPS) State abbreviation in which a public water system addressee or facility is located.
• Source
• Data Characteristics
FRDS-II
Focrn IDi
Data Qualifiers:
Maximum LiMiytli
Data Transfer File
*»
PWS-ID
PWS-AD-ID
: 2
• Edit Criteria
Must be soacffiad when:
Data Base Record: C300
Data Base Family: J
Data Category: JO
Data Type: CHARACTER
Picture: Xf21
PWS-ADDRESS-DATA
Registration Requirement
Grant Requirement: NO
Access: NON-KEY
Code Table ID: ID02
• modifying the current value
UUfc»AM ttt-n*t^Rt*f4
wnen spocniOQ.
• must be one of the USPS Postal State Codes (see Section VI; Table ID02)
Additionally, within an address, the State code and position 1 of the USPS ZIP Code must agree [E9B]
• Comments
Other addressee or facility related addr
• C307 PWS-AD-ADDR-UNE-1
• C309 PWS-AD-ADDR-UNE-2
• C311 PWS-AD-CrTY
• C315 PWS-AD-ZIP
data elements ere maintained in the following data elc
Hits:
Effective Date 1/31/93
Release Number: 2.00
Page: 11-67
-------
FRDS-ll Data Element Description
Name: PWS-AD-2IP
Number C31S
• Description
An alphanumeric value (hat represents the U.S. Postal Service (USPS) ZIP code In which a public water system addressee or facility IB
located.
PWS-AD-ZIP is of the form:
(space inserted for clarity only)
Where:
= the ZIP code
B the ZIP+4 optional ZIP code extension
• Source
FRDS-ll Data Transfer File
Form ID: A3
Data Qualifiers: PWS-ID
PWS-AD-ID
Maximum Length: _9_
e Data Characteristics
Data Base Record: C300 PWS-ADDRESS-DATA
Data Base Family: J
Data Category: .TO
Data Type: CHARACTER
Picture: X(5)
Registration Requirement ^
Grant Requirement NO
Access. KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be e 5 or 9 digit integer number
• must be greater than zero
Additionally, within an address, the State code end position 1 of the USPS ZIP Code must agree [E9BJ
• Comments
Other addressee or facility related address data elements are maintained in the following data elements:
• C307 PWS-AD-ADDR-LINE-1
• C309 PWS-AD-ADDR-LINE-2
• C311 PWS-AD-CiTY
• C313 PWS-AD-STATE
Ettective Date- 1/31/93
Release Number 200
Page.
-------
FRDS-II Data Base Record Description
Number C400
Name: PWS-SOURCE-ENTnY-INFO
• Description
A SYSTEM 2000 data bi
d Identification number and name.
The C400. PWS-SOURCE-ENTITY-INFO, data base record contains data elements that characterize a source of water that to utilized by. or
an entity that to related to. a public water system.
fitry points, treatment
An entity can be any location or facility related to the public water system. Such entities include distribution systt
plants, pumping facilities, water storage facilities, and the like.
The FRDS-II Data Base has one PWS-SOURCE-ENTTTY-INFO data base record for each source of water utilized by. or entity related to. a
public water system that has been reported to EPA.
In order for the FRDS-II computer system to permit the storage of a public water system (i.e., data base legtetiatton). at toast one
PWS-SOURCE-ENTTTY-INFO data base record MUST be inserted into the data base whh data element C405. PWS-SE-RECORD-TYPE..
Indicating a source of water (i.e., "S").
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
C401 PWS-SE-ID
C403 PWS-SE-NAME
C405 PWS-SE-RECORD-TYPE
C407 PWS-SE-CODE
C409 PWS-SE-AVAILABILITY
C411 PWS-SE-SELLER-PWS-ID
C413 PWS-SE-DATA-ORIGIN
C415 PWS-SE-LATITUDE
C417 PWS-SE-LONGITUDE
C418 PWS-SE-MERIDIAN-NAME
C419 PWS-SE-TOWNSHIP
C421 PWS-SE-RANGE
C423 PWS-SE-SECTION
C425 PWS-SE-QTR-SECTION
C426 PWS-SE-QTR-QTR-SECTION
C427 PWS-SE-RIVER-REACH.NUM
C429 PWS-SE-ON-REACH
C431 PWS-SE-REACH-MILES
• Comments
Each data element name contained within the PWS-SOURCE-ENTITY-INFO data base record to prefaced with ... PWS-SE-
Etfecbve Date 1/31/93
Release Number 2.00
Page: II- 89
-------
FRDS-II Data Element Description Number.
Name: PWS-SE-ID
• Description
A numeric value used to uniquely identity a specific source of water that is utilized by. or an entity (e.g.. an entry point a treatment plant
or other related facility) that is related to. a public water system.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: B1 '
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: • j3
Data Base Record: C400 PWS-SOURCE-ENTnY-INFO
Data Base Family: J Registration Requirement J_
Data Category: 20 ' Grant Requirement NO
Data Type: INTEGER Access: NON-KEY
Picture: 9(3) Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting, modifying or deleting a source or entity record
• inserting, modifying or deleting a treatment record
When specified:
• position 1 must be 'G' or position 1 - 3 must be numeric
• position 1 must not be 'G' when modifying or deleting a source or entity record, or a treatment record
• and position 1 is 'G':
. position 2 - 3 must be numeric
. position 2 • 3 must be greater than zero
. position 4 • 7 must be blank
• and position 1 is not 'GV
. position 1 - 3 must be numeric
. position 1 - 3 must be between 1 through 949. inclusive
. position 4 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a source or entity record, or treatment record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a source or entity record
. the ID must exist in the FRDS-II data base for the PWS or the source or entity record, also, must be specified, when Inserting a
treatment record
Each new source or entity record must include values for those data elements within the source or entity record (C400.
PWS-SOURCE-ENTITY-INFO) that are identified as Registration Requirement data elements (see 'Data Characteristics' on this page) (ERR]
Additionally, each new inventory record must include at least one source record (C400. PWS-SOURCE-ENTTTY-INFO with C405.
PWS-SE-RECORD-TYPE of 'S1) (E8A]
• Comments
If desired, the user can have the FRDS-II computer system generate a PWS-SE-ID number by specifying a Group Generation Code (GGC)
when a new source/entity data base record is to be inserted into the data base. This Is accomplished by substituting the GGC for an actual
ID (Le.. Gnn where ... the letter 'G' tells FRDS-II to generate the ID and the VuT is an arbitrary number assigned to all related C400.
PWS-SOURCE-ENTrTY-INFO. data elements so that their logical grouping will remain intact).
Other source/entity IDs are maintained in the following data elements:
• C1143 VlO-SE-ID
• C2119 SAMPLE-SE-ID
• C3031 VE-SE-ID
PWS-SE-ID must be valued for a new PWS-SOURCE-ENTrTY-INFO data base recot! to be inserted Into the FRDS-II Data Base.
Effective Date 1/31/93 Release Number: 200 Pege:
-------
FRDS-II Data Element Description
Number C403
Name: PWS-SE-NAME
• Description
An alphanumeric value that represents either the name of a source of water or the name of an entity (e.g.. name of an entry point, treatment
plant, or other facility) related to a public water system.
• Source
FRDS-II Data Transfer File
Form ID: B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: .40
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Data Characteristics
Data Base Record: C400 PWS-SOURCE-ENTTTY.tNFO
Data Base Family: .2
Data Category: .01
Data Type: CHARACTER
Picture: X(15) Code Table ID:
Grant Requirement
NO
NON-KEY
N/A
e Comments
A source of water for a public water system can be any ocean, river, stream, spring, lake, reservoir, Infiltration gallery, cistern, ground water
well, another public water system, etc. from which water Is obtained for ultimate processing and distribution.
An entity for a public water system can be any entry point or plarrt/facfllty related or associated with a public water system.
Data element C405. PWS-SE-RECORD-TYPE, Identifies whether this data element contains the name of a source of water of. or the name
of an entity rotated to, a public water system.
Effective Date 1/31/93
Release Number 2.00
Page: 11-71
-------
FRDS-ll Data Element Description Number 0405
Name: PWS-SE-RECORD-TYPE
• Description
A code value that represents whether all other data elements contained In the 0400. PWS-SOURCE-ENTITY-INFO. data base record an
related to a source of water, or to another type of entity (e.g., an entry point, a treatment plant, or other related tacflity) tor a public water
system
In order tor the FRDS-ll computer system to permit the storage of a public water system (i.e.. data base registration), at least one
PWS-SOURCE-ENTITY-INFO data base record MUST be Inserted into the data base with data element C405. PWS-SE-RECORD-TYPE.
Indicating a source of water (i.e.. "S").
• Source
• Data Characteristics
FRDS-ll
Form ID:
Data Qualifiers:
Maximum Length
Data Transfer File
B1
PWS-ID
PWS-SE-ID
: J
• Edit Criteria
Data Base Record: C400 PWS-SOURCE-ENTrTY-INFO
Data Base Family: 2
Data Category: 10
Data Type: CHARACTER
Picture: XfU
Registration Requ
Grant Requiremer
Code Table ID:
rement 1
it NO
KEY
0405
Must be specified when:
• inserting a inventory record
• inserting a source or entity record
When specified
• must be one of the Source/Entity Record Type Codes (see Section VI; Table 0405):
•£' - Entry Point Record (Surface or Qroundwater. and Permanent or Non-permanent)
•P1 • Plant/Facility Record (Treatment Plant, Storage. Pumping, and Distribution Facilities, Weil
Head. Intake, etc.)
•S' - Source Record .(Surface. Groundwater. Purchased Source)
Valid combinations of source/entity record types (C40S. PWS-SE-RECORD-TYPE) and source/entity codes (C407, PWS-SE-CODE) are found
in Table ID10
Every public water system must include at least one source record (i.e., C405. PWS-SE-RECORD-TYPE of •&) [ESC]
• Comments
A source of water tor a public water system can be any ocean, river, stream, spring, lake, reservoir, Infiltration gallery, cistern, ground water
well, another public water system, etc. from which water is obtained for ultimate processing and distribution.
PWS-SE-RECORD-TYPE cannot be modified. If a change Is required, the C400 data base record must be deleted and reinserted.
PWS-SE-RECORD-TYPE must be valued for a new PWS-SOURCE-ENTITY-INFO data base record to be inserted Into the FRDS-ll Data Base.
Etlectve Date: 1/31/93
Release Number: 2.00
Page: II-72
-------
FRDS-II Data Element Description Number C407
Name: PWS-SE-CODE .
• Description
A code value that represents the type of source water that Is utilized by, or the type of entity that is related to. a public water system. That
Is:
• For a source of water, whether the water Is obtained from a surface source, groundwater source, groundwater under the direct
Influence (UDI) of surface water source, purchased surface source, purchased groundwater source, or purchased groundwater UD1
source: or
• For an entity, a classification of the type of entry point, or the type of plant or facility.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: Bl
Data Qualifiers: PWS-ID
PWS-SE-tD
Maximum Length: J
Data Base Record: C400 PWS-SOURCE-ENTTTY.INFO
Data Base Family: J Registration Requin
Data Category: JO Grant Requirement NO
Data Type: CHARACTER Access: KEY
Picture: Xm Code Table ID: ID10
• Edit Criteria
Must be specified when:
• Inserting an Inventory record
• inserting a source or entity record
• modifying the current value
When specified:
• must be one of (he Combined Source/Entity Record Type and Source/Entry Point/Plant Type Codes (see Section VI; Table ID10):
•EA" • Surface, Permanent
*EB* • Surface. Non-permanent
•EC* - Groundwater, Permanent
•ED* - Groundwater. Non-permanent
•PH1 - Well Head
•PI* • Intake
•PM' - Pumping Facility
•PO' - Other Plant or Facility
•PR' • Storage Facility
•FT - Treatment Plant
•SG* - Groundwater. Non-purchased
•SP' • Surface, Purchased
•SS1 - Surface. Non-purchased
•SW - Groundwater. Purchased
•SV - Groundwater (UDI). Non-Purchased
•ST • Groundwater (UDI). Purchased
Valid combinations of source/entity record types (C405. PWS-SE-RECORD-TYPE) and source/entity codes (C407. PWS-SE-CODE) are found
in Table ID10.
e. Comments
A source of water for a public water system can be any ocean, river, stream, spring, lake, reservoir. Infiltration gallery, cistern, ground water
well, another public water system, etc. from which water Is obtained for ultimate processing and distribution.
When a purchased source of water Is changed to a non-purchased source, data element C411, PWS-SE-SELLER-ID, will automatically be
Initialized to a -null, value. PWS-SE-CODE must be valued for a new PWS-SOURCE-ENTITY-INFO data base record to be Inserted Into the
FRDS-II Data Base.
Effective Date 1/31/93 Release Number. 2.00 Page: 11-73
-------
FRDS-II Data Element Description
Name: PWS-SE-AVAILABILITV
Number. C409
• Description
A 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 PWS-SE-AVAILABIUTY Include availabilities such as permanently, seasonally, for emergencies only, etc.
• Source
FRDS-II Data Transfer File
Form ID: _B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length:
• Data Characteristics
Data Base Record: C400 PWS-SOURCE-ENTrTiMNFO
Data Base Family: .2
Data Category: 10
Data Type: CHARACTER
Picture XM) Code Table 10:
Registration Requirement ^
Grant Requirement ~
NO
NON-KEY
0409
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Source Availability Codes (see Section VI; Table 0409):
'£' • Emergency Utilization
T - Interim Utilization
•O' - Other Utilization
*P* - Permanent Utilization
•S1 . Seasonal Utilization
• Comments
None
Effective Date 1/31/93
Release Number: 2.00
-------
FRDS-H Data Element Description Number. C411
Name: PWS-SE-SELLEB-PWS-ID
• Description
An alphanumeric value that represents the Identification number of a public water system from whom raw or treated water Is purchased for
processing and distribution.
PWS-SE-SELLER-PWS-IDisofthefOfrn: ss xxxxxxx (space Inserted tor darity only)
Where: ss a the FIPS Pub 5-2 State abbreviation In which a public water system is located, or the region 'number of the EPA region
responsible tor an Indian reservation
xxxxxxx o the public water system identification of the seller of water
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _B1
Data Qualifiers: PWS-IP
PWS-SE-ID
Maximum Length: 9
Data Base Record: C400
Data Base Family: J
Data Category: j!1
Data Type: CHARACTER
Picture: X(9)
PWS-SOURCE-ENTITY-INFO
NO
Registration Requirement
Grant Requirement
Code Table ID: 0003
NON-KEY
• Edit Criteria
Must be specified when:
• modifying the current value
Must only be specified when inserting or modifying a purchased water source (i.e., C405. PWS-SE-RECORD-TYPE of'S1 and C407.
PWS-SE-CODE of -P' or VT) [EYC]
When specified:
• position 1 - 2 must be a valid FIPS Pub 5-1 State code
• the PWS ID should exist in the FRDS-II Data Base
• .Comments
PWS-SE-SELLER-PWS-tD Is applicable to each source of water that Is purchased.
Data element C407. PWS-SE-CODE. identifies whether or not the source of water In question is purchased.
When a purchased source of water is changed to a non-purchased source of water, data element C411. PWS-SE-SELLER-IQ, will
automatically be Initialized to a -null-value.
Effective Date. jy3i/93
Release Number: 2.00
Page: 11-75
-------
FRDS-II Data Element Description
Name: PWS-SE-DATA-OR1GIN
Number C413
• Description
A code value that represents the source or origin of the various values that are maintained In the C400. PWS-SCHJRCE-ENTTTY-1NFO. data
base record.
Examples of PWS-SE-DATA-ORIGIN include sources or origins such as State reported, reported by an EPA region, generated by the FRDS-II
computer system during Its normal course of operation, etc.
• Source
• Data Characteristics
FRDS-H Data Transfer File
' GENERATED DATA ITEM •••
Data Base Record: C400 PWS-SOURCE-ENnTY-INFO
Data Base Famf
Data Category:
Data Type:
Picture:
v: 2
10
CHARACTER
xm
Registration Requirem
Grant Requirement
Access:
Code Table ID:
ent •
NO
NON-KEY
ID07
• Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table ID07):
•H1 - Headquarters (EPA) supplied data (EPA Use Only)
•Rp - Region (EPA) supplied data (EPA Use Only)
•S1 . State supplied data
• Comments
This value ts not input directly by the State. Rather. It is conveyed to Production Control at the time the data is to be processed. Production
Control then communicates to FRDS-II the correct value to assign to this data element
Other data origins are maintained in the following data elements:
• C51' PWS-GA-DATA-ORIGIN
• C809 PWS-MILESTONE-ORIGIN
• C1137 VIO-DATA-ORIG1N
This value cannot be modified.
C1211 ENF-DATA-ORIGIN
C3025 VE-DATA-ORIGIN
Effective Date 1/31/93
Release Number: 2.00
Page: _M
-------
FRDS-II Data Element Description Number. C41S
Name: PWS-SE-LATTTUDE
• Description
A numeric value that represents one of two spherical coordinates that identify the exact physical location of a source of water that is utilized
by. or an entity that to related to. a public water system.
Latitude uses the earth's equator as Its latitudinal origin.
PWS-SE-LATTnjDEisoftheform: dd mm ss (spaces inserted for clarity only)
Where: dd » the degrees of the latitude
' mm = the minutes of the latitude
ss • the seconds of the latitude
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: J31
Data Qualifiers: PWS-ID
PWS-SE-ID
Msximum Longthi 6
Data Base Record: C400 PWS-SOURCE-ENTrTY-INFO
Data Base Family: J Registration Requirement J_
Data Category: 72 Grant Requirement NO
Data Type: INTEGER Access: KEY
Picture: 9(6) Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the longitude (C417. PWS-SE-LONGITUDE) has been specified [E9F]
When specified:
• must be a six digit integer number, comprised of:
. degrees, in position 1 • 2;
. minutes, in position 3 • 4; and
. seconds, in position 5*6
• degrees must be within 00 through 59. inclusive
• minutes must be within 00 through 59. inclusive
• seconds must be within 00 through 59. Inclusive
For Primacies within the continental U.S.. the latitude must be between 23 degrees. 27 minutes and 50 degrees. 0 minutes
•- Comments
PWS-SE-LATTTUDE Is not meaningful by itself. To be meaningful. PWS-SE-LATTTUDE must be considered In conjunction with data element
C417. PWS-SE-LONGITUDE.
Whenever the value for this data element is removed for a public water system, the corresponding longitude (data element C417) will
automatically be initialized to a -null- value
PWS-SE-LATTrUDE must be valued when data element C417. PWS-SE-LONGITUDE. is valued.
EflecDve Date 1/31/93 Release Number: 200 Page: 11-77
-------
FRDS-II Data Element Description
Name: .PWS-SE-LONGITUDE
Number C417
• Description
A numeric value that represents one of two spherical coordinates that Identity the exact physical location of a source of water that is utilized
by. or an entity that is related to. a public water system.
Longitude uses the prime meridian (Greenwich. England) as Its longitudinal origin.
PWS-SE-LONGITUDE is of the form: ddd mm ss (spaces inserted for clarity only)
Where: ddd = the degrees of the longitude
mm B the minutes of the longitude
ss «B the seconds of the longitude
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: 7
Data Base Record: C400 PWS-SOURCE-ENTrTY-INFO
Data Base Family: .2
Data Category: 73
Data Type: INTEGER
Picture: 9(7)
Registration Requirement _4
Grant Requirement NO
Access: KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the latitude (C415. PWS-SE-LATTTUDE) has been specified [E9F]
•t
When specified:
• must be a seven digit integer number, comprised of:
. degrees, in position 1 • 3;
. minutes, in position 4 - 5| and
. seconds, in position 6 - 7
• degrees must be within 000 through 180. Inclusive
• minutes must be within 00 through 59, inclusive
• seconds must be within 00 through 59. Inclusive
For Primacies within the continental U.S.. the longitude must be between 65 degrees. 0 minutes and 125 degrees. 0 minutes longitude
• Comments
PWS-SE-LONGITUDE is not meaningful by Itself. To be meaningful. PWS-SE-LONGITUDE must be considered in conjunction with data
element C415, PWS-SE-LATITUDE.
Whenever the value for this data element Is removed for a public water system, the corresponding latitude (data element C415) wiD
automatically be initialized to a -null- value.
PWS-SE-LONGITUDE must be valued when data element C415. PWS-SE-LATITUDE. is valued.
Effective Date 1/31/93
Release Number. 2.00
Page: II-7B
-------
FRDS-H Data Element Description
Number C41B
Name: PWS-SE-MERIDIAN-NAME
• Description
An alphanumeric value that represents the name of a North-South line from which an exact measuremert of longitude may be made hi order
to locale a specific Township. When coupled with the associated Baseline, It identifies the starting point from which Township. Range.
Section. Quarter-Section, and Quarter-Quarter Section may be used to pinpoint the location of a source or entity.
Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
PWS-SE-ID
J«_
Data Base Record: C400 PWS-SOURCE-ENTTTY-INFO
Data Base Family: 2
Data Cateoorv: 01
Data Type: CHARACTER
Picture: ' XI4)
Registration Requirement 4
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Continents
Meridian name is of particular Importance when more than one Principal Meridian exists within the State. If more than one Principal Meridian
extets for the State, this data element should be valued.
Effective Date 1/31/93
Release Number: 2.00
Pege: II • 79
-------
FRDS-II Data Element Description Number C419
Name: PWS-SE-TOWNSHIP
• Description
An alphanumeric value that represents the physical location of an area of land (i.e.. a township) In relationship to a Known Base line.
PWS-SE-TOWNSHIP In conjunction with data element C421. PWS-SE-RANGE. identifies the township In which a source of water utilized by.
or an entity related to, a public water system is located.
PWS-SE-TOWNSHIP is of the form: tit d (space inserted for darity only)
Where: ttt = a number which represents the physical location of a township in relationship to a known Base line
d = the direction (N for North, or S for South) from a known Base line
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: .81
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: .4
Data Base Record: C400 PW^SOURCE-ENTTTY-INFO
Data Base Famfly: J Registration Requirement
Data Category: 74 Grant Requirement: NO
Data Type: CHARACTER Access: NON-KEY
Picture: X(4) Code Table ID: N/A
Edit Criteria
Must be specified when:
modifying the current value
not presently valued and a Range (C421. PWS-SE-RANGE) has been specified [E9G]
not presently valued and a section (i.e.. C423. PWS-SE-SECTION) has been specified
not presently valued and a quarter section (i.e.. C425, PWS-SE-QTR-SECTION) has been specified
not presently valued and a quarter-quarter section (i.e.. C426. PWS-SE-QTR-QTR-SECTION) has been specified
When specified-
• position 1 - 3 must be numeric
• position 1 - 3 must be greater than 000
• position 4 must be:
. 'N1 (i.e., the township is north of the base line) or
. *S' (i.e.. the township is south of the base line)
Additionally, a valid Range (C421. PWS-SE-RANGE) must also be provided
• Comments
PWS-SE-TOWNSHIP in conjunction with data element C421. PWS-SE-RANGE. identifies a 36 square mile area (i.e.. approximately 23.040
PWS-SE-TOWNSHIP is not meaningful by itself. To be meaningful and precise. PWS-SE-TOWNSHIP should be considered In conjunction
with the following data elements:
• C421 PWS-SE-RANGE
• C423 PWS-SE-SECTION
• C425 PWS-SE-QTR-SECTtON
• C426 PWS-SE-QTR-QTR-SECTION
Together, data elements C419. PWS-SE-TOWNSHIP; C421. PWS-SE-RANGE: C423. PWS-SE-SECTION; C425. PWS-SE-QTR-SECTION; and
C426. PWS-SE-QTR-QTR-SECTION. are part of the rectangular survey system which is presently maintained by the U.S. Department of the
Interior. Bureau of Land Management
Whenever the value for this data element is removed for a public water system, the corresponding range (C421). section (C423). quarter
section (C425). and quarter-quarter section (C426) will automatically be initialized to a -null- value.
PWS-SE-TOWNSHIP must be valued when the range, section, quarter section, or quarter-quarter section Is valued.
Effective Date- 1/31/93 Release Number 2.00 Page: II-80
-------
FRDS-II Data Element Description Number C421
Name: PWS-SE-RANGE
• Description
An alphanumeric value that represents the physical location of an area of land (i.e.. a township) In relationship to a known Principal meridian.
PWS-SE-RANGE m conjunction with data element C419. PWS-SE-TOWNSHIP, identifies the township in which a source of water utilized by.
or an entity related to. a public water system Is located.
PWS-SE-RANGE Is of the form: ttt d (space inserted for dartty only)
Where: ttt = a number which represents the physical location of a township In relationship to a known Principal meridian
d = the direction (E tor East, or W for West) from a known Principal meridian
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: 4
Data Base Record: C400 PWS-SOURCE-ENTrrY-INFO
Data Base Family: J Registration Requirement
Data Category: 75 Grant Requirement NO
Data Type: CHARACTER Access: NON-KEY
Picture: X(4) Code Table ID: N/A
• Edit Criteria
Must be specified when:
modifying the current value
not presently valued and a Township (C419. PWS-SE-TOWNSHIP) has been specified [E9Q]
not presently valued and a section (i.e.. C423. PWS-SE-SECTION) has been specified
not presently valued and a quarter section (Le.. C425. PWS-SE-QTR-SECTION) has been specified
not presently valued and a quarter-quarter section 0-e.. C426, PWS-SE-QTR-QTR-SECTION) has been specified
Wnon specified:
• position 1-3 must be numeric
• position 1 - 3 must be greater than 000
• position 4 must be.
. '£• (i.e.. the township Is east of the base tine) or
. -W (i.e., the township Is west of the base line)
Additionally, a valid Township (C419. PWS-SE-TOWNSHIP) must also be provided
• Comments
PWS-SE-RANGE In conjunction with data element C419. PWS-SE-TOWNSHIP, identifies a 36 square milearea (I.e.. approximately 23,040
acres).
PWS-SE-RANGE is not meaningful by Itself. To be meaningful and precise. PWS-SE-RANGE should be considered in conjunction with the
following data elements:
• C419 PWS-SE-TOWNSHIP
• C423 PWS-SE-SECTION
• C425 PWS-SE-QTR-SECTION
• C426 PWS-SE-QTR-QTR-SECTION
Together, data elements C419, PWS-SE-TOWNSHIP; C421. PWS-SE-RANGE: C423, PWS-SE-SECTION; C425. PWS-SE-QTR-SECTION; end
C426. PWS-SE-QTR-QTR-SECTION, are part of the rectangular survey system which Is presently maintained by Ihe U.S. Department of the
Interior. Bureau of Land Management
Whenever the value for this data element is removed for a public water system, the corresponding township (C419), section (C423). quarter
section (C425). and quarter-quarter section (C426) will automatically be initialized to a -null- value.
PWS-SE-RANGE must be valued when Ihe township, section, quarter section, or quarter-quarter section I valued.
Effective Date 1/31/93 Release Number 2.00 Pege: 11-81
-------
FRDS-II Data Element Description
Name: .PWS-SE-SECTION
Number C423
• Description
A numeric value that represents one of 36 sections of the township In which a source of water utilized by. or an entity related to. a public
water system Is located.
The 36 sections are numbered In a zigzag fashion beginning with 01 In the northeast comer of a township, and ending with a 36 In the
southeast comer of a township.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: 2_
C400 PWS-SOURCE.ENTTTY.INFO
Data Base Family: 2
Data Category:
Data Type: INTEGER
Picture: 9(2)
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and a Quarter Section (C425. PWS-SE-QTR-SECT10N) has been specified
• not presently valued and a quarter-quarter section (i.e.. C426. PWS-SE-QTR-QTR-SECTION) has been specified •
When specified:
• must be numeric
• must be within 01 through 36. inclusive
Additionally, a valid Township (C419. PWS-SE-TOWNSHIP) and Range (C421. PWS-SE-RANGE). must also be provided [EUKJ
• Comments
PWS-SE-SECTION identifies a 1 square mile area (i.e., 640 acres) within a specific township defined by data elements C419,
PWS-SE-TOWNSHIP. and C421. PWS-SE-RANGE.
PWS-SE-SECTION Is not meaningful by Itself. To be meaningful and precise.
PWS-SE-SECTION should be considered in conjunction with the following data elements:
• C419 PWS-SE-TOWNSHIP
• C421 PWS-SE-RANGE
• C425 PWS-SE-OTR-SECTION
• C426 PWS-SE-QTR-QTR-SECTION
Together, data elements C419, PWS-SE-TOWNSHIP; C421. PWS-SE-RANGE; C423. PWS-SE-SECTION; C425. PWS-SE-OTR-SECTION; and
C426. PWS-SE-QTR-QTR-SECTION. are part of the rectangular survey system which Is presently maintained by the U.S. Department of the
Interior, Bureau of Land Management
Whenever the value for this data element is removed for a public water system, the corresponding quarter section (C425). and quarter-quarter
section (C426) will automatically be initialized to a -null- value.
PWS-SE-SECTION must be valued when the quarter section, or quarter-quarter section is valued.
Effective Date. 1/31/93
Release Number. 200
Page: I1-B2
-------
FRDS-II Data Element Description
Name: PWS-SE-QTR-SECTION
Number. C425
• Description
An alphanumeric value that represents one of 4 quadrants of the section in which a source of water utilized by. or an entity related to. a public
water system is located.
The four quadrants are identified as NW (Northwest). NE (Northeast). SW (Southwest), and SE (Southeast).
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: B1
Data Qualifiers: PWS-ID
PWS-SE-ID
Msximum LfinQthi
Data Base Record: C400 PWS-SOURCE-ENnTY-INFO
Data Base Family: J
Data Category: 10
Data Type: CHARACTER
Picture: X(2)
Registration Requirement _4_
Grant Requirement
Access: NON-KEY
Code Table ID: ID11
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and a Quarter Quarter Section (C426. PWS-SE-QTR-QTR-SECTION) has been specified
When specified:
• must be one of the Township/Range Quarter Section and Quarter-Quarter Section Codes (see Section VI; Table ID11):
•NE- - Northeast Quarter
•NW - Northwest Quarter
•SE" - Southeast Quarter
•SW - Southwest Quarter
Additionally, a valid Township (C419. PWS-SE-TOWNSHIP), Range (C421. PWS-SE-RANGE) and Section (C423. PWS-SE-SECTION) must
also be provided [EUL]
e Comments
PWS-SE-QTR-SECTION identifies a 160 acre quadrant within a specific section defined by data element C423. PWS-SE-SECTION.
PWS-SE-QTR-SECTION is not meaningful by Itself. To be meaningful and precise. PWS-SE-QTR-SECTION should be considered in
conjunction with the following data elements:
• C419 PWS-SE-TOWNSHIP
• C421 PWS-SE-RANGE
• C423 PWS-SE-SECTION
• C426 PWS-SE-QTR-QTR-SECTION
Together, data elements C419. PWS-SE-TOWNSHIP; C421. PWS-SE-RANGE; C423. PWS-SE-SECTION; C42S. PWS-SE-QTR-SECTION; and
C426, PWS-SE-QTR-QTR-SECTION. are part of the rectangular survey system which to presently maintained by the U.S. Department of the
Interior. Bureau of Land Management
Whenever the value for this data element is removed for a public water system, the corresponding quarter-quarter section (C426) will
automatically be initialized to a -null- value.
PWS-SE-QTR-SECTION must be valued when the quarter-quarter section is valued.
Effective Date 1/31/93
Release Number: 2.00
Page: II-B3
-------
FRDS-II Data Element Description Number C426
Name: PWS-SE-QTR-QTR.SECTION
• Description
An alphanumeric value that represents one of 4 quadrants of the quarter-section In which a source of water utilized by, or an entity related
to. a public water system is located.
The four quadrants are Identified as NW (Northwest). NE (Northeast). SW (Southwest), and SE (Southeast).
• Source
• Data Characteristics'
FRDS-II Data Transfer File
Form ID: Bt .
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length:
Data Base Record: C400 PWS-SOURCE-ENTrfY-INFO
10
Data Base Famfly:
Data Category:
Data Type: CHARACTER
Picture: Xf2)
Registration Requirement ^
Grant Requirement NO
Code Table ID:
NON-KEY
ID11
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Township/Range Quarter Section and Quarter-Quarter Section Codes (see Section VI; Table ID11):
•NE1 • Northeast Quarter
•NW • Northwest Quarter
•SE* - Southeast Quarter
•SW1 - Southwest Quarter
Additionally, a valid Township (C419. PWS-SE-TOWNSH1P). Range (C421. PWS-SE-RANGE). Section (C423. PWS-SE-SECTION) and Quarter
Section (C425. PWS-SE-QTR-SECTION) must also be provided |EUM]
• Comments
PWS-SE-QTR-QTR-SECTION Identifies a 40 acre quadrant within a specific quarter-section defined by data element C42S.
PWS-SE-QTR-SECTION.
PWS-SE-QTR-QTR-SECTION is not meaningful by Itself. To be meaningful and precise. PWS-SE-QTR-QTR-SECT10N should be considered
In conjunction with the following data elements:
• C419 PWS-SE-TOWNSHIP
• C421 PWS-SE-RANGE
• C423 PWS-SE-SECTION
• C425 PWS-SE-QTR-SECTION
Together, data elements C419. PWS-SE-TOWNSHIP; C421. PWS-SE-RANGE; C423, PWS-SE-SECTION: C42S. PWS-SE-QTR-SECTION: and
C426, PWS-SE-QTR-QTR-SECTION. are part of the rectangular survey system which is presently maintained by the U.S. Department of the
Interior, Bureau of Land Management.
Effective Date: 1731/93
Release Number: 200
Page: Jl
-------
FRDS-II Data Element Description Number C4Z7
Name: PWS-SE-RIVER-REACH-NUM .
• Description
A code value that identifies a linear section of a stream, lake, reservoir, estuary, wide river, shoreline, etc.. of the continental United States
that to associated with a source of water utilized by a public water system.
The river reach (as It is known) provides a hydrologic framework for organizing and analyzing water resources and water quality data.
PWS-SE-HIVER-REACH-NUMteofthetorm: hhhhhhhhsss (space Inserted for clarity only)
Where: hhhhhhhh = the U.S. Geological Survey's Hydrologic Unit Code
* sss B the U.S. EPA Storet system's Hydrologic Unit Code extension (the segment)
end hhhhhhhh te of the form: rrppaacc (spaces inserted for clarity only)
Where: rr = a U.S. Water Resources Council (WRC) region
rr pp B a WRC planning subregion
rr pp aa = an accounting unit of the National Water Data Network
rr pp aa cc B a cataloging unit of the USGS Catalog of Information on Water Data
Each part of the river reach number (e.g., rr, pp) delineates a hydrologic drainage basin that defines (from left to righQ a progressively smaller
basin size. The water resources region (i.e.. rr) being the largest area, and the river reach (i.e.. rr pp aa cc sss) being the smallest area.
When coupled with C431, PWS-SE-REACH-MILES, a specific physical location along a river reach can be established.
Acceptable Hydrologic unit codes are defined in Federal Information Processing Standard Publication (PIPS PUB) 103. which te entitled.
•Codes for the Identification of Hydrologic Units In the United States and the Caribbean Outlying Areas.' This FIPS PUB te also known as.
•Geological Survey Circular 878-A.1
Acceptable river reach codes are defined by the U.S. EPA's STORET Office tor use In their Water Quality System Reach File.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: .81
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length:
Data Base Record: C400 PWS-SOURCE-ENTrTY-INFO
Data Base Family: .2 Registration Requirement ^_
Data Category: JO Grant Requirement NO
Data Type: CHARACTER Access: KEY
Picture: Xffi) Code Table ID: 0427
• Edit Criteria
Must be specified when.
• modifying the current value
When specified:
• position 1 - 8 must be one of the FIPS PUB 103, Hydrologic Unit Codes (see Section VI; Table 0427)
• position 9-11 must be either blank or numeric [EA9J
•. Comments
Data element C429. PWS-SE-ON-REACH, Identifies whether a source of water is 'on' or 'off a river reach.
Data element C431, PWS-SE-REACH-MILES, defines an exact physical location of a surface source Intake hi relationship to the downstream
end of a river reach.
Effective Date. 1/31/93 Release Number 200 Page: 11-85
-------
FRDS-II Data Element Description
Name: PWS-SE-ON-REACH
Number C429
• Description
A code value that represents whether a source of water utilized by a public water system Is •on* or 'off a defined river reach.
•On' Implies that a surface source Intake Is located on a defined river reach. "Off implies that the source of water (or surface source Intake)
Is not located on a defined river reach, but instead. Is located within the area drained by the river reach.
If a surface source Make Is 'on1 the river reach, the number of reach miles (C431.PWS-SE.REACH^ILES) defines an exact physical location
of the intake. Reach miles are measured from the downstream end of the river reach.
• Source
• Data Characteristics
Form ID:
Data Qualifiers:
FRDS-II Data Transfer File
PWS-ID
PWS-SE-ID
Maximum Length: _1_
Data Base Record: C400 PWS.SOURCE.EHnTY.INFO
Data Base Family
Data Category:
Data Type: CHARACTER
Picture: X£l)
10
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: 0429
• Edit Criteria
Must be specified when:
• modifying the current value
Should be specified when:
• not presently valued and a river reach number (I.e.. PWS-SE-RIVER-REACH-NUM) has been specified
• not presently valued and the river reach miles (i.e.. PWS-SE-REACH-MILESJ has been specified
When specified:
• must be one of the On Reach Flag Codes (see Section VI; Table 0429):
•N* • Intake NOT on defined River Reach
•Y1 - Intake on defined River Reach
• Comments
Data element C427, PWS-SE-RIVER-REACH-NUM. Identifies the river reach number that is associated with a source of water.
Data element C431, PWS-SE-REACH-MILES. defines an exact physical location of a surface source intake in relationship to the downstream
end of a river reach.
Effective Date 1/31/93
Release Number. 2.00
Page: 11-86
-------
FRDS-II Data Etement Description
Name: PWS-SE-REACH-MILES
Number C431
• Description
A numeric value that defines an exact physical location of a surface source intake in relationship to the downstream end of the river reach.
given that the source is 'on' a defined river reach.
A source of water utilized by a public water system can be either 'on1 or 'off the river reach (C429, PWS-SE-ON-REACH).
•On1 Implies that a surface source Intake is located on a defined river reach. "OTP Implies that the source of water (or surface source Intake)
Is not located on a defined river reach, but Instead. Is located within the area drained by the river reach.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: JJ1
Data Qualifiers: PWS-ID
PWS-SE-ID
Maximum Length: 6
Data Base Record: C400 PWS-SOURCE-ENT1TY-INFO
Data Base Family:
Data Category:
Data Type: DECIMAL
Picture: 9(4).9ta
41
NO
Registration Requirement
Grant Requirement
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
Should be specified when:
• not presently valued and a River Reach number (C427, PWS-SE-RIVER-REACH-NUM) has been specified
• not presently valued and an On-Reach (C429. PWS-SE-ON-REACH) has been specified
When specified:
must be a numeric real number
whole portion cannot exceed four digits
decimal portion cannot exceed two digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount is intended
must not be a negative number (EGA]
• Comments
Data element C4Z7. PWS-SE-RIVER-REACH-NUM. identifies the river reach number that Is associated with a source of water.
Data element C429. PWS-SE-ON-REACH. identifies whether a source of water is 'on' or trf* a river reach.
Effective Date. V31/93
Release Number 2.00
Page: 11-87
-------
FRDS-II Data Base Record Description
Number. C480
Name: PWS-SE-TREATMENT-DATA
• Description
A SYSTEM 2000 data base record Identification number and name.
The C480. PWS-SE-TREATMENT-DATA, data base record contains data elements that Identify a treatment that has been applied to a unique
source of water or whether treatment has been applied elsewhere.
The FRDS-II Data Base has one PWS-SE-TREATMENT-DATA data base record (or each treatment mat has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C400 PWS-SOURCE-ENTmMNFO
• Record Contents
This data base record contains the following data elements:
• C481 PWS-SE-TREATMENT-ID
• C483 PWS-SE-TREATMENT-OBJECTIVE
• C485 PWS-SE-TREATMENT-PROCESS
• Comments
Each data element name contained within the PWS-SE-TREATMENT-DATA data base record is prefaced with... PWS-SE-TREATMENT-
When a C4SO. PWS-SE-TREATMENT-DATA. data base record indicates that a source of water is treated at the plant, several additional steps
should be followed. These steps are as follows:
(1) A C400, PWS-SOURCE-ENTITY-INFO. data base record should be inserted Into the data base with
data element C405, PWS-SE-RECORD-TYPE, indicating a plant data base record; and
(2) One or more C460. PWS-SE-TREATMENT-DATA. data base records should be inserted tor the plant
data base record indicating the actual treatments) applied.
Effective Date: 1/31/93
Release Number: 2.00
Page: II-88
-------
FRDS-II Data Element Description
Name: PWS-SE-TREATMENT-ID
Number. C481
• Description
A numeric value used to uniquely identify a specific treatment applied to a source of water for a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: J2
Data Qualifiers: PWS-ID
PWS-SE-ID
TREATMENT-ID
Maximum Length:
Data Base Record: C480
Data Base Family 2
Data Category 20
DataTvoe: INTEGER
Picture: 9(2)
PWS-SE-TREATMENT-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
3
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a treatment record
When specified:
• must not have a 'G* in position 1 when modifying or deleting a treatment record
• and position 1 is a "G1:
. position 2*3 must be numeric
. position 2 • 3 must be greater than zero
. position 4 - 7 must be blank
• and position 1 te not a 'G':
. position 1-2 must t>6 numeric
. position 1 • 2 must be greater than zero
. position 3-7 must be blank
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a treatment r
. the ID must not exist in the FRDS-II data base for the PWS. when Inserting a treatment record
Each new treatment record must Include values for those data elements within the treatment record (C480. PWS-SE-TREATMENT-DATA) that
are Identified as Registration Requirement data elements (see 'Data Characteristics' on this page) [ERR]
Additionally, a source or entity record must be inserted when inserting a treatment record for a new Public Water System [E6H]
• Comments
If desired, the user can have the FRDS-II computer system generate a PWS-SE-TREATMENT-ID number by specifying e Group Generation
Code (GGC) when a new treatment data base record is to be inserted Into the data base. This Is accomplished by substituting the GGC for
an actual ID (i.e. Gn. where... the letter 'G1 tells FRDS-II to generate the ID and the tf Is an arbitrary number assigned to all related C4BO.
PWS-SE-TREATMENT. data elements so that their logical grouping will remain intact).
Effective Date 1/31/93
Rel
Number 2.00
Page:
-------
FRDS-II Data Element Description Number. C483
Name: PWS-SE-THEATMENT-OBJECTIVE
• Description
A code value that Identifies a specific objective to be attained through treatment of a source of water (or a public water system.
Examples of PWS-SE-TREATMENT-OBJECTIVE include objectives such as disinfection, paniculate removal, corrosion control, softening, etc.
-• Source
.• Data Characteristics
FRDS-II Data Transfer File
Form ID: J2
Data Qualifiers: PWS-ID
PWS-SE-ID.
Maximum Length:
TREATMENT-ID
Data Base Record: C480 PWS-SE-TREATMENT-DATA
Data Base Family: 2
Data Category: _io
Data Type: CHARACTER Access:
Picture: Xm Code Table ID:
Registration Requirement _3_
Grant Requirement
NO
KEY
ID05
• Edit Criteria
Must be specified when:
• inserting a treatment record
• modifying the current value
Must not be specified when inserting or modifying an entry point record (i.e.. C405. PWS-SE-RECORD-TYPE of '£•) [EXAJ
When specified:
• must be one of the Treatment Objective Codes (see Section VI; Table 1005):
•A' • Additional Treatment Elsewhere
*B' - Disinfection By-products Control
•C1 • Corrosion Control
•D1 • Disinfection
•E' • Dechlorination
'F' • Iron Removal
•I1 - Inorganics Removal
*M' - Manganese Removal
•N" - No Treatment at Source
*O* - Organics Removal
•P' - Paniculate Removal
•R1 - Radionudides Removal
•S1 - Softening (Hardness Removal)
T • Taste / Odor Control
•X1 - Treatment Unknown (Converted FRDS 1.5) ("X1 may not be used on any FRDS-II Input)
•Y* - Treated (Converted FRDS 1.5) p" may not be used on any FRDS-II input)
•Z* - Other
Valid combinations of Treatment Objectives (C483. PWS-SE-TREATMENT-OBJECTIVE) and Treatment Processes (C485.
PWS-SE-TREATMENT-PROCESS) are found in the Combined Treatment Objective and Treatment Process Codes (see Section VI; Table ID03)
e Comments
Data element C485. PWS-SE-TREATMENT-PROCESS, identifies the specific treatment process that fulfills the treatment objective identified
in this data element.
If no treatment is applied to a source of water, or additional treatment is applied elsewhere (e.g.. by a seller, at a treatment plant or entry
point), it should be so noted.
PWS-SE-TREATMENT-OBJECTIVE must be valued for a new
PWS-SE-TREATMENT-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date- 1/31/93
Release Number 200
Page: 11-90
-------
FRDS-II Data Element Description Number C48S
Name: PWS-SE-TREATMENT-PRQCESS
• Description
A code value that identities a specific treatment process that is utilized for a source of water tor a public water system.
Examples of PWS-SE-TREATMENT-PROCESS Include processes such as chlorination. filtration, fluortdalion. pH adjustment
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: B2
Data Qualifiers: PWS-ID
PWS-SE-ID
TREATMENT-ID
Maximum Length:
Data Base Record: C4BO PWS-SE-TREATMENT-DATA
Data Base Family: J
Data Category: 10
Data Type: INTEGER
Picture: 9(3)
Registration Requirement ^__^
Grant Requirement NO
Access: KEY
Code Table ID: ID03
• Edit Criteria
Must be specified when:
• Inserting a treatment record
• modifying the current value
Must not be specified when inserting or modifying an entry point record (i.e., C405. PWS-SE-RECORD-TYPE of '£*) [EXA]
When specified:
• must be one of the Treatment Process Codes (see Section VI; Table ID04)
Valid combinations of Treatment Objectives (C483, PWS-SE-TREATMENT-OBJECTIVE) and Treatment Processes (C485,
PWS-SE-TREATMENT-PROCESS) are found in the Combined Treatment Objective and Treatment Process Codes (see Section VI; Table 1003)
e Comments
Data element C483, PWS-SE-TREATMENT-OBJECTIVE, identifies the specific treatment objective that is to be attained by the application of
the treatment process identified in this data element
H no treatment is applied to a source of water, or additional treatment is applied elsewhere (e.g.. by a seller, at a treatment plant-or entry
point), It should be so noted.
Other treatment process codes are maintained In the following data elements:
• C3015 VE-TREATMENT-PROCESS
• C3017 VE-ALT-PROCESS
PWS-SE-TREATMENT-PROCESS must be valued for a new PWS-SE-TREATMENT-DATA data base record to be inserted Into the FRDS-II
DataBase.
Effeojve Date 1/31/93
Release Number: 200
Page: 11-91
-------
FRDS-ll Data Base Record Description Number C500
Name: PWS-GEOGRAPHIC-AREAS-SERVED
• Description
A SYSTEM 2000 data base record identification number and name.
The C500. PWS-GEOGRAPHIC-AREAS-SERVED. data base record contains data elements that identify a geographic area or jurisdiction
served by a public water system.
It is assumed that all data elements within a single PWS-GEOGRAPHIC-AREAS-SERVED data base record are valued with related data which
describe a single geographic area. Completely separate geographic areas served are maintained in separate
PWS-GEOGRAPHIC-AREAS-SERVEO data base records.
i served that has been
'The FRDS-ll Data Base has one PWS-GEOGRAPHIC-AREAS-SERVED data base record for each geographic
reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C501 PWS-GA-ID
• C503 PWS-GA-ADMIN-REGION
• C505 PWS-GA-ADMIN-DIST
• C507 PWS-GA-CONGRESSIONAL-DIST
• C50B PWS-GA-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
CS13 PWS-GA-CITY-SERVEO
C515 PWS-GA-IND-RES-CODE
C517 PWS-GA-DATA-ORIGIN
• Comments
Each data element name contained within the PWS-GEOGRAPHIC-AREAS-SERVED data base record is prefaced with... PWS-GA-
At least one of the above data elements other than C501 and CS17 must be valued to have this data base record accepted by- FRDS-ll.
Effective Date. 1/31/93
Release Number. 2.00
Page: 11-92
-------
FRDS-II Data Element Description Number C501
Name: PWS-GA-ID _^___
• Description
A numeric value used to uniquely identity a specific geographic area served by a public water system.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: C1
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length: 2
Data Base Record: CSOO PWS-GEOGRAPHIC-AREAS-SERVED
Data Base Family: j» Registration Requirement J_
Data Category: 20 Grant Requirement NO
Data Type: INTEGER Access: NON-KEY
Picture: 9(2) . Code Table ID: N/A
• Edit Criteria
Must be specified when*
• Inserting, modifying or deleting a geographic area served record
When specified:
• position 1 must be 'G' or position 1 - 2 must be numeric
• position 1 must not be 'G1 when modifying or deleting a geographic area served record
• and position 1 is 'GV '
. position 2 must be numeric
. position 2 must be greater than zero
. position 3 - 7 must be blank
• and position 1 is not 'GV
. position 1 - 2 must be numeric
. position 1 - 2 must be between 1 and 89. inclusive
. position 3 - 7 must be blank
. the ID must exist in trie FRDS-II data base for the PWS. when modifying or deleting a geographic area served record
.. the ID must not exist in the FRDS-II data base tor the PWS. when inserting a geographic area served record
Each new geographic area served record must Include values for those data elements within the geographic area served record (CSOO.
PWS-GEOGRAPHIC-AREAS-SERVED) that are identified as Registration Requirement data elements (see 'Data Characteristics' on this page)
[ERR]
Additionally, at least one geographic area served data element (i.e.. C503. PWS-GA-ADMIN-REGION; C505. PWS-GA-ADMIN-DIST; C507.
PWS-GA-CONGRESSIONAL-DIST; C508. PWS-GA-STATE-COUNTY-CODE; C509. PWS-GA-FIPS-COUNTY-CODE; C513.
PWS-GA-CITY-SERVED. or C515. PWS-GA-IND-RES-CODE) must be valued [E6J]
• Comments
If desired, the user can have the FRDS-II computer system generate a PWS-GA-ID number by specifying a Group Generation Code (GGC)
when a new geographic areas served data base record is to be inserted into the data base. This is accomplished by substituting the GGC
for an actual ID (i e. Gn. where... the letter 'G1 tells FRDS-II to generate the ID and the 'n1 te an arbitrary number assigned to all related CSOO.
PWS-GEOGRAPHIC-AREAS-SERVED, data elements so that their logical grouping will remain intact).
PWS-GA-IDs 90 through 99 are reserved for use by the FRDS-II computer system.
PWS-GA-ID must be valued for a new PWS-GEOGRAPHIC-AREAS-SERVED data base record to be Inserted into the FRDS-II Date Base.
Effective Date 1/31/93 Release Number. 2.00 Page: "-93
-------
FRDS-II Data Element Description
Name: PWS-GA-ADMIN-REGION
Number C503
• Description
An alphanumeric value that represents a State administrative region, It any. that Is being served by a public water system In whole or In part.
State administrative regions. H any. are unique to a given State, and are Independently determined by that State.
e Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .C1
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length: 2
Data Base Record: C500
Data Base Family: 3
Data Category: 02
Data Type: CHARACTER
Picture: X(2)
PWS-GEOGRAPHIC-AREAS-SERVED
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Other data elements contained within the C500, PWS-GEOGRAPHIC-AREAS-SERVED. data base record'represent a variety of different
geographic or jurisdicfional means of identifying the area served by a public water system. These data elements are as follows:
CSOS PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C508 PWS-GA-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CITY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date: 1/31/93
Release Number: 2.00
Page: 11-94
-------
FRDS-II Data Element Description
Name: PWS-GA-ADMIN-DIST
Number C50S
• Description
An alphanumeric value that represents a State administrative district, if any. that is being served by a public water system m whole or In pat
State administrative districts. If any. are unique to a given State, and are independently determined by that State.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
PWS-GA-ID
-2
Data Base Record: C500
Data Base Family: J
Data Category: 02
Data Type: CHARACTER
Picture: Xf2)
PWS-GEOGRAPHIC-AREAS.SERVED
Registration Requirement
Grant Requirement:
Access: NON-KEY
Code Table ID: N/A
NO
e Edit Criteria
Must be specified when:
• modifying the current value
uukAM j-i-i iioiHnii
wnen specmea.
• must be an alphanumeric value
e Comments
Other data elements contained within the C500. PWS-GEOGRAPHIC-AREAS-SERVED. data base record represent a variety of different
geographic or jurisdictional means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C507 PWS-GA-CONGRESSIONAL-DIST
C508 FWS-GA.STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CrrY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date. 1/31/93
Release Number. 2.00
Page: _H
-------
FRDS-II Data Element Description Number C8BT
Name: PWS-GA-CONGRESSIONAL-DIST
• Description
A code value (hat represents a Federal congressional district that is being served by public water system in whole or in part
Congressional districts are unique to a given State, and to each session of Congress.
Non-voting delegates to Congress are represented by a W in PWS-GA-CONGRESSIONAL-DIST.
No Representative to Congress is represented by a -99- in PWS-GA-CONGRESSIONAL-D1STRICT.
M Large delegates (only one Representative) to Congress are represented by a -OO1 (double zero) In PWS-GA-CONGRESSIONAL-DIST.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _C1
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length:
Data Base Record: CSOO PWS-GEOGRAPHIC-AREAS-SERVED
JO
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: X(2> _
NO
Registration Requirement
Grant Requirement
Access: NON-KEY
Code Table ID: 0507
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the FIPS PUB 9. Federal Congressional District Codes (100th Congress) (see Section VI; Table 0507)
e Comments
Other data elements contained within the CSOO. PWS-GEOGRAPHIC-AREAS-SERVED. data base record represent a variety of different
geographic or jurisdictional means of Identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C50B PWS-GA-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CITY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date: 1/31/93
Release Number: 200
Page: 11-96
-------
FRDS-II Data Element Description Number. C508
Name: PWS-GA-STATE-COUNTY-CODE
• Description
A code value that represents a county, or county equivalent, that is being served by a public water system In whole or In part.
PWS-GA-STATE-COUNTY-CODE is a State specific county code, where Federal Information Processing Standard (FIPS) codes are not used
by a State. A State may report either FIPS county codes, or county codes which are assigned by that State. If the county codes reported
by a State are not identified as FIPS codes, a one-tor-one State county code to FIPS county code conversion list MUST be provided.
A county is considered to be the first order subdivision1 of each State regardless of Its local designation (e.g. county, parish, borough, etc.).
All of the following are. considered to be county equivalents:
the census areas and boroughs of Alaska
the District of Columbia
tho psrishss of LouisJ&ns
the independent cities of the States of Maryland. Missouri. Nevada, and Virginia
that part of Yellowstone National Park located in Montana
the munkapios of the Commonwealth of Puerto Rico
the Islands of the U.S. Virgin Islands
the districts/islands of American Samoa
the States of the Federated States of Micronesia
the island of Guam
the munldpalilies/telands/atolls of the Marshall Islands
the municipalities of the Northern Mariana Islands
the States of the Republic of Palau
the Islands of the U.S. Minor Outlying Islands
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: C1
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length: .3
Data Base Record: C500 PWS-GEOGRAPHIC-AREAS-SERVED
Data Base Family: j| Registration Requirement
Data Category: _15 Grant Requirement NO
Data Type: CHARACTER Access: NON-KEY
Picture. X{3) Code Table ID: 0508
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the State-specific County Codes (see Section VI; Table 0508)
e Comments
If the State reports a non-FIPS county code. FRDS-II stores the reported value herein and wDI automaticalty determine the equivalent FIPS
county code and store it In data element C509. PWS-GA-FIPS-COUNTY-CODE.
Acceptable FIPS county codes are defined In Federal Information Processing Standard Publication (FIPS PUB) 6-4. which is entitled. •Counties
and Equivalent Entities of the United States, Its Possessions, and Associated Areas.'
Other data elements contained within the C500. PWS-GEOGRAPHIC-AREAS-SERVED. data base record represent a variety of different
geographic or jurisdictional means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CITY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date 1/31/93 Release Number 2.00 P*9* "-97
-------
FRDS-II Data Element Description
Number C509
Name: PWS-GA.FIPS-COUNTY-CODE
• Description
A code value that represents a county, or county equivalent, that Is being served by a public water system In whole or In part.
PWS-GA-FIPS-COUNTY-CODE is a Federal Information Processing Standard (FIPS) county code. A State may report either FIPS county
codes, or county codes which are assigned by that State. If the county codes reported by a State are not Identified as FIPS codes, a
one-tor-one State county code to FIPS county code conversion list MUST be provided.
A county is considered to be the first order subdivision' of each State regardless of its local designation (e.g. county, parish, borough, etc.).
All of the following are considered to be county equivalents:
the census areas and boroughs of Alaska
the District of Columbia
the parishes of Louisiana
the independent cities of the Slates of Maryland. Missouri. Nevada, and Virginia
that part of Yellowstone National Park located in Montana
the munidpios of the Commonwealth.of Puerto Rico
the Islands of the U.S. Virgin Islands
the districts/islands of American Samoa
the States of the Federated States of Micronesia
the Island of Guam
the municipalities/islands/atolls of the Marshall Islands
the municipalities of the Northern Mariana Islands
the States of the Republic of Palau
the islands of the U.S. Minor Outlying Islands
• Source
• Data Characteristics
Form ID:
Data Qualifiers:
FRDS-II Data Transfer File
PWS-ID
PWS-GA-ID
Maximum Length: 3
Data Base Record: C500
Data Base Family: j3
Data Category: 10
Data Type: CHARACTER
Picture: X(31
PWS-GEOGRAPHIC-AREAS-SERVED
Registration Requirement
Grant Requirement
NO
Code Table ID:
NON-KEY
0509
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the FIPS PUB 6-3. County Codes (see Section VI; Table 0509)
• Comments
If the State reports a non-FIPS county code. FRDS-II stores the reported value in data element C508. PWS-GA-STATE-COUNTY-CODE. and
will automatically determine the equivalent FIPS county code and store It herein.
Acceptable FIPS county codes are defined in Federal Information Processing Standard Publication (FIPS PUB) 6-4. which is entitled. •Counties
end Equivalent Entities of the United States. Its Possessions, and Associated Areas.'
Other data elements contained within the C500. PWS-GEOGRAPHIC-AREAS-SERVED. data base record represent a variety of different
geographic or jurisdiction^ means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C508 PWS-GA-STATE-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CITY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date. 1/31/93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Name: PWS-GA-MSA-CODE
Number
• Description
A computed code value that represents a metropolitan statistical area (MSA), or primary metropolitan statistical area (PMSA), that is being
served by a public water system In whole or hi part
The term computed, as used here, implies that this code value is not reported by the Slate. PWS-GA-MSA-CODE is determined automatically
by the FRDS-II computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM •••
Data Base Record: CSOO PWS-GEOGRAPHIC-AREAS-SERVED
Data Base Family: J
Data Category: 10
Data Type: CHARACTER
Picture: XM)
Registration Requirement _;
Grant Requirement NO
Access:
Code Table ID:
KEY
0511
• Acceptable Values
Entries from the FIPS PUB 8-5. Metropolitan Statistical Area (MSA) Codes, with PMSAs. NECMAs, & CMSAs (see Section VI; Table 0511)
• Comments
Other data elements contained within the C500. PWS-GEOGRAPHIC-AREAS-SERVED, data base record represent a variety of different
geographic or jurisdictionaJ means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C50B PWSX3A-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C513 PWS-GA-CtTY-SERVED
C515 PWS-GA-IND-RES-CODE
Effective Date 1/31/93
Release Number 2.00
Page: 11-99
-------
FRDS-II Data Element Description
Name: PWS-GA-CITY-SERVED
Number CS13
• Description
An alphanumeric value that represents a city, community, or jurisdiction that is being served by a public water system in whole or In part
Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C1
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length: 40
Data Base Record: C500
Data Base Family: 3
Data Category: JJ1
Data Type: CHARACTER
Picture: XfiSl
PWS-GEOGRAPHIC-AREAS-SERVED
Registration Requirement •
Grant Requirement NO
Access: KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Other data elements contained within the CSOO. PWS-GEOGRAPHIC-AREAS-SERVED. data base record represent a variety of different
geographic or jurisdictonal means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C508 PWS-GA-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C515 PWS-GA-IND-RES-CODE
Effective Date
Release Number: 200
Page:
-------
FRDS-II Data Element Description
Name: .PWS-GA-IND-RES-CODE
Number CS15
• Description
A code value that represents an Indian reservation or Alaska remote village, if any. being served by a public water system In whole or In part.
Acceptable PWS-GA-IND-RES-CODE Indian reservation and Alaska remote village codes are defined In the Federal Information Processing
Standards Publication (PIPS Pub) 55-2. entitled, 'Guideline - Codes for Named Populated Places. Primary County Divisions, and other
Locabonal Entities of the United States and Outlying Areas.'
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: £2
Data Qualifiers: PWS-ID
PWS-GA-ID
Maximum Length:
Data Base Record: C500
Data Base Family: _3
Data Category: 1D
Data Type: CHARACTER
Picture: X(S)
PVYS-GEOGRAPHIC-AREAS-SERVED
Registration Requirement: *
Grant Requirement NO
Access: KEY
Code Table ID: 1DQ1
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Alaska Remote Village Codes (see Section VI; Table ID01)
• Comments
Other data elements contained within the C500. PWS-GEOGRAPHIC-AREAS-SERVED, data base record represent a variety of different
geographic or jurisdictional means of identifying the area served by a public water system. These data elements are as follows:
C503 PWS-GA-ADMIN-REGION
C505 PWS-GA-ADMIN-DIST
C507 PWS-GA-CONGRESSIONAL-DIST
C508 PWS-GA-STATE-COUNTY-CODE
C509 PWS-GA-FIPS-COUNTY-CODE
C511 PWS-GA-MSA-CODE
C513 PWS-GA-CrrY-SERVED
EKective Date JQ1/93
Release Number. 200
Page: II-1
-------
FRDS-II Data Element Description
Name: PWS-GA-DATA-ORIGIN
Number CS17
• Description
A code value that represents the source or origin of the various values that are maintained in the C500. PWS-GEOGRAPHIC-AREAS-SERVED.
Gst& boss record.
Examples of PWS-GA-DATA-ORIGIN include sources or origins such as State reported, reported by an EPA region, generated by the FRDS-II
computer system during its normal course of operation, etc.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM •••
Data Base Record: C500 PWS-GEOGRAPHIC-AREAS-SERVED
Data Base Family: 3
Data Category: • 10
Data Type: CHARACTER
Picture: XfD
Registration Requirement
Grant Requirement
Code Table ID:
.
NO
NON-KEY
ID07
• Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table ID07):
•H1 • Headquarters (EPA) supplied data (EPA Use Only)
•R1 • Region (EPA) supplied data (EPA Use Only)
•S* - State supplied data
• Comments
This value is not input directly by the State. Rather. It is conveyed to Production Control at the time the data Is to be processed. Production
Control then communicates to FRDS-II the correct value to assign to this data element
Other data origins are maintained in the following data elements:
• C413 PWS-SE-DATA-ORIGIN
• C809 PWS-MILESTONE-ORIGIN
• C1137 VIO-DATA-ORIGIN
This value cannot be modified.
C1211 ENF-DATA-ORIGIN
C302S VE-DATA-ORIGIN
Effective Date. 1/31/93
Release Number 200
Page: 11-102
-------
FRDS-II Data Base Record Description
Name: PWS-SERV1CE-AREAS
Number: C600
• Description
A SYSTEM 2000 data base record Identification number and name.
The C600. PWS-SERVICE-AREAS, data base record contains data elements that characterize a service area of a public water system.'
The FRDS-II Data Base has one PWS-SERVICE-AREAS data base record for each type of area served that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: _4_
Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C601 PWS-SERV-ID
• C603 PWS-SERV-CATEGORY
C605 PWS-SERV-PRIMARY-FLAG
• Comments
Each data element name contained within the PWS-SERVICE-AREAS data base record is prefaced with: PWS-SERV- At least one of the above
data elements other than C601 must be valued to have this data base record accepted by FRDS-II.
Effective Date: 1/31/93
Release Number. 2.00
Page: 11-103
-------
FRDS-II Data Element Description
Name: PWS-SERV-ID
Number C601
• Description
A numeric value used to uniquely Identify a specific type of area being served by a public water system. In whole or in part.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C2
Data Qualifiers: PWS-ID
PWS-SERV-ID
Maximum Length: 2
Data Base Record: C600
D&t& B&so Fsntily* 4
Data Category: 20
Data Tvoe: INTEGER
Picture: 9(2)
PWS-SERVICE-AREAS
^^ Registration Requirement:
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a service area record
When specified:
• position 1 must be "G1 or position 1 - 2 must be numeric
• position 1 must not be 'G1 when modifying or deleting a service area record
• and position 1 is 'G':
. position 2 must be numeric
. position 2 must be greater than zero
. position 3 - 7 must be blank
• and position 1 is not 'Gf:
. position 1 - 2 must be numeric
. position 1 - 2 must be greater than zero
. position 3 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a service area record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a service area record
Each new service area record must include values for those data elements within the service area record (C600. PWS-SERVICE-AREAS) that
are Identified as Registration Requirement data elements (see 'Data Characteristics' on this page) [ERR]
• Comments
If desired, the user can have the FRDS-II computer system generate a PWS-SERV-ID number by specifying a Group Generatioh Code (GGC)
when a new service area data base record is to be inserted into the data base. This is accomplished by substituting the GGC for an actual
ID 0 e. Gn. where ... the letter 'G' tells FRDS-II to generate the ID and the If is an arbitrary number assigned to all related C600,
PWS-SERVICE-AREAS. data elements so that their logical grouping will remain intact).
PWS-SERV-ID must be valued for a new PWS-SERVICE-AREAS data base record to be Inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number: 200
Page:
-------
FHDS-II Data Element Description
Name: PWS-SERV-CATEGORY
Number
• Description
A code value that represents a primary type of area being served by a public water system In whole or In part
PWS-SERV-CATEGORY te of the form: xy {space Inserted tor darity only)
Where: x = a category identifying the area being served (e.g., residential, transient)
y = a sub-category of the category (e.g., mobile home park (a sub-category of a residential service area), campground (a
sub-category of a transient service area), etc.)
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID.'
Data Qualifiers:
Mdxinujm Lsngthi
_C2_
PWS-ID
PWS-SERV-ID
J
• Edit Criteria
Data Base Record. C600
Data Base Family: J
Data Category: 10
Data Type: CHARACTER
Picture: X(2)
PWS-SERV1CE-AREAS
Registration Requirement ^3^^^
Gram Requirement : NO
Access: KEY
Code Table ID: 0603
Must be specified when.
• Inserting a service area record
• modifying the current value
When specified:
• must be one of the Service Area Category Codes (see Section VI. Table 0803):
•Of - Interstate Carrier (Other)
•02- . Wholesaler (Sells Water) (Other)
•O9- - Other Area (Other)
•RV . Residential Area (Residential)
•R2" . Mobile Home Park (Residential)
•R9* • Other Residential Area (Residential)
•SV • School (Semi-residential)
•S? - Institution (Semi-residential)
•S31 - Medical Facility (Semi-residential)
•S4' - Industrial/Agricultural (Semi-residential)
•S5* - Day Care Center (Semi-residential)
•S9- - Other Semi-residential Area (Semi-residential)
TV - Recreation Area (Transient)
T21 - Service Station (Transient)
T3' - Summer Camp (Transient)
T41 - Restaurant (Transient)
T51 - Highway Rest Area (Transient)
T61 - Hotel/Motel (Transtent)
T9* • Other Transient Area (Transient)
• Comments
PWS-SERV-CATEGORY must be valued for a new PWS-SERVICE-AREAS data base record to be inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number 2.00
Page: II-IPS
-------
Description
FRDS-ll Data Element Description Number. C605
Name: mS-SERV-PRIMARY-FLAG
A code value that Indicates whether or not an area served by a public water system is the primary type of area served by that public
system.
It Is Important to note that only one area served by a public water system can be designated as the primary type.
• Source
• Data Characteristics
FRDS-ll Data Transfer Frle
Form ID: C2
Data Qualifiers: PWS-ID
PWS-SERV-ID
Maximum Length: J_
Data Base Record: C600 PWS-SERVICE-AREAS
Data Base Family: 4
Data Category: 10
Data Type: CHARACTER
Picture: X(D
Registration Reauirernent 4
Grant Requirement: NO
Access: KEY
Code Table ID: 0605
e Edit Criteria
Must be specified when:
• modifying the current value
• Inserting a new non-transient non-community or a non-community public water system
• should be designated for one and only one area served by the public water system
When specified.
• must be one of the Primary Service Area Hag Codes (see Section VI; Table 0605):
•N1 • Non-Primary Service Area (Secondary Service Area)
•Y" • Primary Service Area
• Comments
One, and only one, PWS-SERV-PRIMARY-FLAG should be valued with the letter V (i.e., service area is the primary one) among all
PWS-SERVICE-AREAS data base records In the FRDS-ll Data Base tor this public water system. •
Effective Date 1/31/93
Release Number. 200
Page: 11-106
-------
FRDS-II Data Base Record Description
Name: PWS-ON-SITE-VISITS
Number C700
• Description
A SYSTEM 2000 data base record identification number and name.
The C700, PWS-ON-SITE-VISITS. data base record contains data elements that are related to an on-stte visit made to a public water system.
The FRDS-II Data Base has one PWS-ON-SITE-VISITS data base record for each on-ste visit that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: _5_
Parent Record: ClOO PWS-SUMMARY
• Record Contents
This data base
CTOI PWS-VISIT-ID
C703 PWS-VISIT-DATE
the following data elements:
C705 PWS-VISIT-REASON
e Comments
Each data element name contained within the PWS-ON-SITE-VISITS data base record is prefaced with: PWS-VISIT- Both C703 and C705 data
elements must be valued to have this data base record accepted by FRDS-II.
Note that PWS-ON-SITE-VISITS data base records will NOT be deleted If a Total Replace1 of Inventory submitted and a previously submitted
visit data base record is omitted.
Effective Date 1/31/93
Release Number: 200
Page: II -107
-------
FRDS-II Data Element Description
Name: PWS-VlsrMD
Number. C701
• Description
A numeric value used to uniquely identity a specific ort-site visit made to a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C3
Data Qualifiers: PWS-ID
PWS-VISIT-ID
Maximum Length.
Data Base Record: C700
Data Base Family:
Data Category: 20
Data Type: INTEGER
Picture:
pws-ON-srrE-visrrs
9(2}
Registration Requirement 3
Grant Requirement NO
Access:
Code Table ID:
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• inserting, modifying or deleting an on-site visit record
When specified:
• position 1 must be *G* or position 1 - 2 must be numeric
• position 1 must not be "G" when modifying or deleting a on-site visit record
• and position 1 is 'G':
. position 2 must be numeric
. position 2 must be greater than zero
. position 3 - 7 must be blank
• and position 1 is not 'GV
. position 1 - 2 must be numeric
. position 1 - 2 must be greater than zero
. position 3 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS, when modifying or deleting a on-site visit record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a on-site visit record
Each new on-site visit record must include values tor those data elements within the on-site visit record (C700. PWS-ON-SITE-VISrrS) that
are identified as Registration Requirement data elements (see 'Data Characteristics1 on this page) [ERR]
Additionally, at least one on-site visit data element (i.e.. C703. PWS-VIS1T-DATE or C705. PWS-vlSIT-REASON) must be valued
• Comments
If desired, the user can have the FRDS-II computer system generate a PWS-VISIT.ID number by specifying a Group Generation Code (GGC)
when a new on-site visit data base record is to be inserted into the data base. This is accomplished by substituting the GGC tor an actual
ID (i.e. Gn. where ... the letter 'G1 tells FRDS-II to generate the ID and the V Is an arbitrary number assigned to all 'related C700
PWS-ON-SITE-VISITS, data elements so lhat their logical grouping will remain intact).
In a Total Replace* environment FRDS-II will automatically convert any user assigned visit ID to a GGC. This Is necessary since
PWS-ON-SITE-VISIT data base records are only inserted and duplicate IDs could easily become a problem. The use of GGCs guarantees
unique PWS-VISIT-IDs for States totally replacing their Inventory each quarter.
PWS-VISIT-ID must be valued for a new PWS-ON-SITE-VISITS data base record to b» inserted Into the FRDS-II Data Base.
Effective Date
Release Number. 200
Page:
-------
FRDS-tl Data Element Description
Name: PWS-V1SIT-DATE
Number C7TJ3
• Description
A value that represents the calendar date on which a visit was made to a public water system.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: C3
Data Qualifiers: PWS-1D
PWS-VISIT-ID
Maximum Length:
Data Base Record: C700 PWS-ON-SITE-VlsrrS
Data Base Fami
Data Category:
Data Type:
Picture: •
v: 5
60
DATE
MMDDYY
Registration Requlremei
Grant Requirement
Code Table ID:
NO
NON-KEY :
N/A
e Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and C705, PWS-VISIT-REASON. has been specified [E9L]
When specified.
• must be a six digit numeric calendar date, comprised of:
. month, in position 1 - 2|
. day. In position 3 - 4; and
. year, in position 5 • 6
• must be before the current calendar date [EEA]
e Comments
Data element C705. PWS-VISIT-REASON, Identifies the reason for which a visit was made on this date.
Effective Date 1/31/93
Release Number 200
Page: 11-109
-------
FRDS-II Data Element Description
Name: PWS-V1SIT-REASON
Number C705
• Description
A code value that represents the reason for which a visit was made to a public water system.
PWS-V1SIT-REASON is of the form: xy (space Inserted for clarity only)
Where: x = class of visit (i.e.. class 1 or 2 survey)
y = sub-category (e.g.. regularly scheduled, complaint investigation, emergency, spill)
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C3
Data Qualifiers: PWS-ID
PWS-VISIT.ID
Maximum Length: 2
Data Base Record: C700 PWS-ON-SITE-VISrTS
Data Base Family: .5
Data Category: 10
Data Type: CHARACTER
Picture: X(2)
Registration Requirement: •
Grant Requirement: NO
Access: KEY
Code Table ID: 0705
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and C703. PWS-VISIT-DATE. has been specified [E9LJ
When specified:
• must be one of the On-site Visit Reason Codes (see Section VI; Table 0705):
•1 • - Sanitary Survey
•2A' - Training
•2C' - Laboratory Certification
*2E* - Emergency Assistance
•2G' • Engineering Determination/Advice
•21' • Investigation (Complaint/Violation/etc.)
•2L* • Laboratory Inspection
*2M' - Informal System Inspection
•2O' - Other
•2P' - Permit (Qualification/Review/Compliance)
•2R1 - Regularly Scheduled
•2S' - Sample Collection
•2T- - Technical Assistance (Non-specific)
•2V - Variance/Exemption/Other Compliance
•2V • Schedule Related
• Comments
Data element C703, PWS-V1SIT-DATE. identifies the date on which this visit was made.
Effective Date: 1/31/93
Release Number.
Page:
-------
FRDS-II Data Base Record Description Number C800
Name: PWS-MILESTONES-EVENTS
• Description
A SYSTEM 2000 data base record identification number and name.
The C800. PWS-MILESTONES-EVENTS. data base record contains data elements that are related to events concerning the Lead and Copper
Rule.
The FRDS-II Data Base has one PWS-MILESTONES-EVENTS data base record for each milestone that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C801 PWS-MILESTONE-ID
• C803 PWS-MILESTONE-DATE
• C805 PWS-MILESTONE-CODE
• C809 PWS-MILESTONE-ORIGIN
C811 PWS-MILESTONE-INSERT-DATE
C813 PWS-MILESTONE-COMMENT
C815 PWS-MILESTONE-VALUE
• Comments
Each data element name contained within the PWS-MILESTONES-EVENTS data base record is prefaced with ... PWS-MILESTONE-
Note that PWS-MILESTONES-EVENTS data base records will NOT be deleted If a Total Replace* of Inventory is submitted and a previously
submitted milestone data base record Is omitted.
Effective Date. 1/31/93
Release Number 2.00
Page:
-------
FRDS-II Data Element Description
Name: PWS-MILESTONE-ID
Number C801
• Description
An alphanumeric value used to uniquely Identify a specific milestone for a public water system.
MILESTONE-ID is of the form: nnnn
Where: nnnn • a milestone identification number assigned by the State or generated by the FRDS-II computer system (the first position
consists of the letter "M1 If the ID was generated)
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
C4
PWS-ID
MILESTONE-ID
A _
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Family: 13
Data Category: 25
Datatype: CHARACTER
Picture: XM)
Registration Requirement 3
Grant Reauirement NO ,.,_
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a milestone record [E4V]
When specified:
• position 1 must be 'G* or "M", or position 1 - 4 must be numeric
• position 1 must not be 'W when inserting a milestone record [E2U]
• position 1 must not be 'G* when modifying or deleting a milestone record f.E2W]
• and position 1 is "G* or 'M':
. position 2 • 4 must be numeric |E3H]
. position 2 - 4 must be greater than zero
. position 5 - 7 must be blank
• and position 1 is neither 'G' nor 'M':
. position 1 - 4 must be numeric
. position 1 • 4 must be greater than zero
. position 5 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS, when modifying or deleting a milestone record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a milestone record
• and position 1 is 'MV
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a milestone record
Each new milestone record must include values for those data elements within the milestone record (C600. PWS-MILESTONE-EVENTS) that
are identified as Registration Requirement data elements (see 'Data Characteristics1 on this page) [ERR]
• Comments
If desired, (he user can have the FRDS-II computer system generate a MILESTONE-ID number by specifying a Group Generation Code (GGC)
when a new milestone data base record is to be inserted into the data base. This is accomplished by substituting the GGC for an actual ID
(i.e, Gnnn where ... the letter *G* tells FRDS-II to generate the ID and the 'nnn1 is an arbitrary number assigned to all related CBOd.
PWS-MILESTONES-EVENTS. data elements so that their logical grouping will remain IntacQ.
PWS-MILESTONE-ID must be valued for a new PWS-MILESTONES-EVENTS data base record to be inserted Into the FRDS-II Data Base.
Effective Date- 1/31/93
Release Number: 2.00
Page: II • 112
-------
PBDS.II Data Element Description
Number C803
Name: PWS-MILESTONE-DATE
• Description
A value that represents the calendar date associated with a certain milestone
renc
i tor a public water system.
The exact nature of the date contained in PWS-MILESTONE-DATE is dependent upon the type of milestone that was reported by the State.
For example, tor action level exceedances. the date reported is the last day of the monitoring period in which the exceedance was
encountered. In comparison, for treatment designation/installation events, the date reported is either the data the State made the optimal
corrosion control treatment (OCCT) or source water treatment (SOWT) designation, or the date the State received proof of the installation
of OCCT or SOWT. as applicable.
.-
Complete details regarding the exact nature of this date as It relates to the type of milestone is contained hi Chapter VI. Definitions and
Federal Reporting for Milestones. Violations, and SNCs. of the Lead and Copper Implementation Guidance.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C4
Data Qualifiers: PWS-ID
MILESTONE-ID
Maximum Length: _6_
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Family:
Data Category:
Data Type: DATE
Picture: MMDDYY
13
60
Registration Requirement:
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
• Edit Criteria
Must be specified when:
• Inserting a milestc
ice record
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month. In position 1 - 2;
. day. In position 3 - 4; and
year, in position 5-6
• Must be after June 30.1991 (06/30/91) [EHZ]
• Must be the same as. or before the current calendar date [EQW]
• Comments
Data element C805. PWS-MILESTONE-CODE. identifies the specific milestone to which this date applies.
PWS-MILESTONE-DATE must be valued for a new PWS-MILESTONES-EVENTS data base record to be Inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number 2.00
Page: 11-113
-------
FRDS-II Data Element Description
Name: PWS-MILESTONE-CODE
Number: C805
• Description
A code value that represents a specific milestone occurrence tor a public water system.
Examples of PWS-MILESTONE-CODE Include milestones such as 90th percentile lead and copper action exceedances. corrosion control
studies required/completed, treatment designated/approved/installed. Water Quality Parameters (WQP) designated/approved. Maximum
Permissible Levels (MPLs) designated/approved, and Lead Service Line Replacement (LSLR) designations.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C4
Data Qualifiers: PWS-ID
MILESTONE-ID
Maximum Length:
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Family: 13
Data Category: 10
Data Type: CHARACTER
Picture: X(4)
Registration Requirement:
Grant Requirement
Access:
Code Table ID:
2
NO
KEY
0805
• Edit Criteria
Must be specified when:
• Inserting a milestone occurrence record
• modifying the current value
When specified:
• must be one of the Pb/Cu Milestone Event Codes (see Section VI; Table 0805):
•CCSR* - Corrosion Control Study Required
•CSSC' • Corrosion Control Study Completed
•CU901 • Copper Action Level Exceedance
•LSLR1 • Lead Service Line Replacement Required
•MPLS* • Max. Permissible Levels in Source Water
•OTDE' • OCCT Treatment Designated or Approved
•OTIN' - OCCT Treatment Installed
•PB901 - Lead 90th Action Level Exceedance
•STDE* - SOWT Designated or Approved
•STIN1 • SOWT Treatment Installed
•WOPS' - Water Quality Parameters
• Comments
PWS-MILESTONE-CODE must be valued tor a new PWS-MILESTONES-EVENTS data oase record to be inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number. 2.00
Page: 11-114
-------
FRDS-II Data Element Description
Name: PWS-MILESTONE-ORIGIN
Number C809
• Description
A code value that represents the source or origin of the various values that are maintained in the C800. PWS-MILESTONES-EVENTS, data
base record.
Examples of PWS-MILESTONE-ORIGIN Include sources or origins such as State reported, reported by an EPA region, generated by the
FRDS-II computer system during Its normal course of operation, etc.
• Source
e Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Family: 13
Data Category: 10
Data Type: CHARACTER
Picture: X(1)
Registration Requirem
Grant Requirement
AppBSfi'
Code Table ID:
ent -
NO
NON-KEY
ID07
e Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table ID07):
•H1 - Headquarters (EPA) supplied data (EPA Use Only)
•R* • Region (EPA) supplied data (EPA Use Only)
•S" - State supplied data
e Comments
This value is not input directly by the State. Rather. It is conveyed to Production Control at the time the data is to be processed. Production
Control then communicates to FRDS-II the correct value to assign to this data element
Other data origins are maintained in the following data elements:
.. C413 PWS-SE-DATA-ORIGIN
* • C517 PWS-GA-DATA-ORIGIN
• C1137 VIO-DATA-ORIGIN
This v&Iu6 c&nnot bs nxxJifiod.
C1211 ENF-DATA-ORIGIN
C3025 VE-DATA-ORIGIN
Effective Date 1/31/93
Release Number. 2.00
-------
FRDS-II Data Element Description Number C811
Name: PWS-MILESTONE-INSERT.DATE
• Description
A computed value that represents the calendar date on which a milestone data bi
J was initially posted to the FRDS-II Data Base.
The term computed, as used here, implies that this date Is not reported by the State.
PWS-MILESTONE-INSERT-DATE is determined automatically by the FRDS-II computer system during Ms normal course of operation when
a new milestone data base record is initially inserted into the FRDS-II Data Base.
• Source
• Data Characteristics
FRDS-II Data Transfer File
••* GENERATED DATA ITEM •*•
Data Base Record: CBOO
Data Base Family: 13
Data Catepory: 60
Data Tvoe: DATE
Picture: MMDDYY
PWS-MILESTONE-EVENTS
Registration Requirement
Grant Requirement
^fcrrnf «r
Code Table ID:
.
NO
NON-KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day. in position 3 - A; and
year, in position 5 - 6
• Comments
This date is valued for State reported data only (i.e.. data submitted via DTP transactions).
Other insert dates are maintained in the following data elements:
• C168 PWS-INSERT-DATE • C1213
• C1117 VIO-INSERT-DATE . C3033
ENF-INSERT-DATE
VE-INSERT-DATE
Effective Dale 1/31/93
Release Number: 2.00
Page: 11-116
-------
FRDS-II Data Element Description
Number C813
Name: PWS-MILESTONE-COMMENT
• Description
An alphanumeric value that represents any description, characteristic, or attribute that the State or EPA region wants to record for the
associated milestone data base record.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C4
Data Qualifiers: PWS-ID
MILESTONE-ID
Maximum Length: 40
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Family: 13
Data Category: • J>1
Data Type: CHARACTER
Picture. XM)
Registration Requirement *
Grant Requirement NO
Code Table ID:
NON-KEY
N/A
e Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Only one comment Is allowed per milestone data base record.
Other comments are maintained in the following data elements:
• C1215 ENF-COMMENT
• C4057 DBA-COMMENT
Effective Date 1/31/93
Release Number: 2.00
Page. II-117
-------
FRDS-II Data Element Description
Name: PWS-MILESTONE-VALUE
Number C81S
• Description
A numeric value that represents the 90th percentile lead or copper level exceedance. or Lead Service Line Replacement (LSLR) rates when
reporting lead and copper milestones.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: C4
Data Qualifiers: PWS-ID
MILESTONE-ID
Maximum Length:
Data Base Record: C800 PWS-MILESTONE-EVENTS
Data Base Familv: 13
Data Cateoorv: 41
Data Tvoe: DECIMAL
Picture: 9(7).9(B)
Registration Requirement
Grant Requirement
Access:
Code Table ID:
4
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• inserting a milestone record with a milestone code (C805. PWS-MILESTONE-CODE) indicating a Lead 90th Action Level Exceedance
(i.e.. 'PB901). Copper Action Level Exceedance (i.e.. CU90) or Lead Service Line Replacement (i.e.. 'LSLR1) [E7F]
Must not be specified when inserting or modifying a sample record, unless the milestone code (CB05. PWS-MILESTONE-CODE) indicates
Lead 90th Action Level Exceedance (i.e., 'PB90'). Copper Action Level Exceedance (i.e.. 'CU9T/) or Lead Service Line Replacement (i.e..
•LSLR') [EXH]
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount is intended
must be greater than or equal to 1.35 when the milestone code (C805, PWS-MILESTONE-CODE) indicates Copper Action Level
Exceedance (i.e.. 'CU90') [EEL]
must be greater than or equal to .0155 when the milestone code (C805. PWS-MILESTONE-CODE) indicates Lead 90th Action Level
Exceedance (i.e.. *PB90') [EEJ]
must be less than or equal to 1.00 when the milestone code (CB05. PWS-MILESTONE-CODE) Indicates Lead Service Line
Replacement Required (i.e.. 'LSLR*) [EEK]
• Comments
PWS-MILESTONE-VALUE must be specified for a new PWS-MILESTONES-EVENTS data base record to be inserted into the FRDS-II Data
Base for the following types of milestones:
• Lead action level exceedance
• Copper action level exceedance
• Lead Service Line Replacement (LSLR) rate
Effective Date. 1/31/93
Release Number: 200
Page: II-118
-------
FRDS-II Data Base Record Description Number C900
Name: PWS-HISTORY
• Description
A SYSTEM 2000 date base record Identification number and name.
The C900, PWS-HISTORY, data base record contains data elements that are related to changes made to a public water system's inventory
data In FRDS-II.
The FRDS-II Data Base has one PWS-HISTORY data base record tor each change In value made to a select list of inventory data elements.
Inventory data elements are those that have PWS- as part of their data element name prefix.
• Data Characteristics
Data Type: RECORD Data Base Family: J Parent;Record: - ClOO PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C901 PWS-HtST-CHANGED-ITEM • C905 PWS-HIST-OLD-VALUE
• C903 PWS-HIST-CHANGE-DATE • C907 PWS-HIST-NEW-VALUE
• Comments
Each data element name contained within the PWS-HISTORY data base record is prefaced with: PWS-HIST- Refer to Section III.. Quick
Reference (sub-section B.) for a list of data elements for which historical information is kept
Effective Date, j/31/93 Release Number: 2.00 Pege: II -119
-------
FRDS-II Data Element Description
Number. C901
Name: PWS-HIST-CHANGED-ITEM
• Description
An alphanumeric value that represents a selected Inventory data element component number whose value was updated. Inventory data
elements are those that have PWS- as part of their data element name prefix.
• Source
• Data Characteristics
FRDS-II Data Transfer File
•*• GENERATED DATA ITEM •*•
Data Base Record: C900 PWS-HISTORY
Data Base Faml
Data Category:
Data Type:
Picture:
v: 6
02
CHARACTER
X(4)
Registration Requirem
Grant Requirement
Access:
Code Table ID:
ent •
NO
KEY
N/A
• Acceptable Values
An alphanumeric value representing an Inventory (i.e.. PWS-) data element number. Including the *C' prefix
Historical tracking is automatically done by FRDS-II tor the following data elements:
C100 PWS-SUMMARY (whenever a 'Current1 system becomes •Historical')
C103 PWS-STATUS
C113 PWS-DEACT-YYMM
C115 PWS-POP-CATEGORY
C119 PWS-PRIMARY-SOURCE
C129 PWS-TREATMENT-CLASS
C131 PWS-SYSTEM-NAME
C147 PWS-SERV1CE-CONNECTIONS
• Comments
Data element C903. PWS-HIST-CHANGE-DATE, identifies a date on which a data element's value was updated.
Data element C905. PWS-HIST-OLD-VALUE. identifies the contents of a data element prior to Its update.
Data element C907, PWS-HIST-NEW-VALUE, identifies the contents of a data element subsequent to its update.
Historical information is maintained for a select list of inventory data elements only.
Effective Date 1/31/93
Release Number:
Page: 11-120
-------
FRDS-II Data Element Description Number C903
Name: PWS-HIST-CHANGE-DATE
• Description
A value that represents the calendar date on which a selected inventory data element's value was updated.
Whenever a public water system becomes 'Historical,' this value will automatically be set to the date on which FRDS-II detected It was no
longer part of the 'Current1 inventory.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM •••
Data Base Record: C900
Data Base Family: .6
Data Category: 60
Data Type: DATE
Picture: * MMDDYY
PWS-HISTORY
Registration Requirement -
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month. In position 1 • 2j
day, In position 3 - 4; and
year. In position 5 - 6
• Comments
Data element C901, PWS-HIST-CHANGED-ITEM, Identifies an Inventory data element component number whose value was updated.
Data element C905, PWS-HIST-OLD-VALUE. identifies the contents of a data element prior to Its update.
Data element C907, PWS-HIST-NEW-VALUE. Identifies the contents of a data element subsequent to Its update.
Historical information is maintained for a select list of Inventory data elements only.
Effective Date. 1/31/93
Release Number. 2.00
Page: II -121
-------
FRDS-II Data Element Description
Name: PWS-HIST-OLD-VALUE
Number C905
• Description
An alphanumeric value that represents the contents of a selected Inventory data element prior to Its update.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM '
Data Base Record: C900 ' PWS-HISTORY
Data Base Family: 6
Data Category: 01
Data Type: CHARACTER
Picture: X(20)
Registration Requirement •
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An alphanumeric value
The original value (i.e.. before the update) of the data element being documented in the history record
When a PWS becomes 'historical*, this value will automatically be set to the literal. 'HISTORICAL-PWS'
• Comments
Data element C901. PWS-HIST-CHANGED-ITEM, identifies an inventory data element component number whose value was updated.
Data element C903. PWS-HIST-CHANGE-DATE. identifies a date on which a data element's value was updated.
Data element C907. PWS-HIST-NEW-VALUE. identifies the contents of a data element subsequent to Its update.
Historical information is maintained for a select list of inventory data elements only.
Effective Date 1/31/93
Release Number: 2.00
Page: II -122
-------
FRDS'll Data Element Description
Name: PWS-HIST-NEW-VALUE
Number. C907
• Description
An alphanumeric value that represents the contents of a selected Inventory data element subsequent to its update (i.e.. the new value).
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM •*•
Data Base Record: C900 PWS-HISTORY
Data Base Family: 6
Data Category: J>1
Data Type: CHARACTER
Picture: X(2TO
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
e Acceptable Values
An alphanumeric value
The new value P.O.. following the update) of the data element being documented in the history record
When a historical PWS becomes •current', this value will automatically be set to the literal. "WAS MADE CURRENT*
e Comments
Data element C901. PWS-HIST-CHANGED-ITEM. identifies an inventory data element component number whose value was updated.
Data element C903. PWS-HIST-CHANGE-DATE. identifies a date on which a data element's value was updated.
Data element C905. PWS-HIST-OLD-VALUE. identifies the contents of a data element prior to Its update.
Historical information is maintained for a select list of inventory data elements only.
Effective Date 1/31/93
Release Number:
Page: II • 123
-------
FRDS-II Data Base Record Description Number C1000
Name: NON-COMPLIANCE-DATA
• Description
A SYSTEM 2000 data base record identification name and number.
The C1000. NON-COMPLIANCE-DATA, data base record contains a single data element. It is included In the FRDS-II Data Base solely tor
the purpose of efficiently processing violation, enforcement action, and non-compliance profile data.
The FRDS-II Data Base has one NON-COMPLIANCE-DATA data base record tor each public water system that has at least one violation or
enforcement action.
• Data Characteristics
Data Type: RECORD Data Base Family: 7-9 Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements.
• C1001 NCD-RECON-FLAG
• Comments
None
Eflective Date 1/31/93 Release Number. 200 Page: II • t24
-------
FRDS-II Data Element Description
Name: NCD-RECON-FLAG
Number. C1001
• Description
A computed code value that represents whether or not an update has been performed to the FRDS-II Data Base which necessitates the
verification and/or determination of appropriate violation and enforcement linkages or the regeneration of non-compliance profile data base
records.
The term computed, as used here, implies that this code value Is not reported by the State. NCD-RECON-FLAG is det
by the FRDS-II computer system during Its normal course of operation.
ined auto
tfcally
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM
Data Base Record: C1000 NON-COMPUANCE-DATA
Data Base Family: 7-9 Registration Requirement
Data Category: 10 Grant Requirement
Data Type: CHARACTER Access:
Picture: Xm Code Table ID:
.
NO
KEY
1001
Acceptable Values
•compliance
Data Reconciliation Flag Codes (see Section VI; Table 1001)-
EntnBS from Ih6 Norn
•NULL1 • Reconciliation NOT Needed for NCP/LINK (NULL implies no Data Base value)
T • NCP Reconciliation Needed
•2* - NCP and LINK Reconciliation Needed
• Comments
Other reconciliation flags are maintained in the following data elements:
• C19 ST-RECON-FLAG
• C171 PWS-RECON-FLAG
EtlecDve Daw 1/31/93
Release Number: 2.00
Page: II -125
-------
FRDS-II Data Base Record Description
Name: VIOLATION-DATA
Number. C1100
• Description
A SYSTEM 2000 data base record identification name and number.
The C1100. VIOLATION-DATA, data base record contains data elements that characterize a violation of a primary drinking water regulation
Incurred by a public water system.
The FRDS-II Data Base has one VIOLATION-DATA data base record for each violation that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: CtOOO NON-COMPLIANCE-DATA
• Record Contents
This data base record contains the following data elements:
C1101 VIO-ID
C1103 VIO-CONTAMINANT
C1105 VIO-TYPE
C1107 VIO-COMP-PERIOD-BEGIN-DATE
C1109 VIO-COMP-PERIOD-END-DATE
C1111 VIO-COMP-PERIOD-MONTHS
C1115 VlO-AWARE-DATE
C1117 VIO-INSERT-DATE
C1121 V1O-ANALYSIS-METHOD
C1123 VIO-ANALYSIS-RESULT
C1125 VIO-MCL-VIOLATED
C1127 VIO-SAMPLES-REQUIRED
C1129 VIO-SAMPLES-TAKEN
C1131 VIO-MAJOR-VIOLATION-FLAG
C1133 V1O-LAST-UPDATE
C1135 VIO-FY
C1137 VIO-DATA-OR1GIN
C1143 VIO-SE-ID
• Comments
Each data element i
ntained within the VIOLATION-DATA data base record is prefaced with... VIO-
Eflectwe Date- 1/31/93
Release Number: 2.00
Page: Jl -126
-------
FRDS-II Data Element Description Number
Name: VIO-ID
Description
An alphanumeric value used to uniquely identify a specific violation of a primary drinking water regulation Incurred by a public water system.
R Is unique for each public water system within the Federal fiscal year In which the State became aware of the violation.
VIO-ID is of the form: yy nnnnn (space Inserted for clarity only)
Where: yy o the Federal fiscal year In which the State became aware of the violation
nnnnn = a violation identification number assigned by the State or generated by the FRDS-II computer system (the first position
consists of the letter "V If the ID was generated)
• Source • Data Characteristics
FRDS-II Data Transfer File
FOrm ID: D1
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length: 7
Data Base Record: C1100 VIOLATION-DATA
Data Base Family: .7 Registration Requirement:
Data Category: 22 Grant Requirement NO
Datatype: CHARACTER Access: NON-KEY
Picture: Xf7> Code Table ID: N/A
• Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a violation record
When specified:
position 1 - 2 must be the Federal fiscal year of the violation
position 1 - 2 must be greater than 77 and less than or equal to the current Federal fiscal year
position 1 - 2 must be greater than 88 and less than or equal to the current Federal fiscal year, for SWTR violations Q.e.. C1105.
VIO-TYPE te -3V. -361 or '411)
position 3 must be *G' or V, or position 3-7 must be numeric
position 3 must not be V when Inserting a violation record
position 3 must not be 'G1 when modifying or deleting a violation record
and position 3 te 'G' or V:
. position 4-7 must be numeric
. position 4 - 7 must be greater than zero
• and position 11s neither 'G' nor V:
. position 1 - 7 must be numeric
. position 1 - 7 must be greater than zero
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a violation record
. the ID must not exist in the FRDS-II data base for the PWS, when inserting a violation record
• and position 11s V:
. the ID must exist in the FRDS-II data base tor the PWS, when modifying or deleting a violation record.
Each new violation record must include values for those data elements within the violation record (C1100. VIO-VIOLATION) that are Identified
as Registration Requirement data elements (see 'Data Characteristics' on this page) [ERR]
• Comments
H desired, the user can have the FRDS-tl computer system generate a VIO-ID number by specifying a Group Generation Code (GGC) when
a new violation data base record Is to be Inserted into the data base is accomplished by Inserting the GGC In positions 3 • 7 of the VIO-ID.
Another violation ID is maintained in data element C1281. ENF-UNK-VIO-ID.
VIO-ID must be valued for a new VIOLATION-DATA data base record to be inserted Into the FRDS-II Data Base.
Effective Date: 1/31/93 Release Number 200 Page: II-127
-------
FRDS-II Data Element Description Number. C1103
Name: VIO-CONTAMINANT
• Description
A code value that represents an Identification number of a contaminant for which a public water system has Incurred a violation of a primary
drinking water regulation.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: _D1
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length: 4
Data Base Record: C1100 VIOLATION-DATA
Data Base Family: _7 Registration Requin
Data Category: JO Grant Requirement NO
Data Type: CHARACTER Access: KEY
Picture: X(41 Code Table ID: ID06
• Edit Criteria
Must be specified when:
• modifying the current value .
• Inserting a violation for certain MCL or Monitoring violations (i.e.. C1105. VIO-TYPE Is *01> through W or *2r through "261) IE81Q
• Inserting a violation for MPL Non-Compliance violations (i.e.. C1105. VIO-TYPE Is W) [E8V]
Must not be specified when inserting or modifying a Sanitary Survey or SWTR violation (i.e.. C1105. VIO-TYPE of •28'. •31*. *36> or Ml*) (EXQ]
When specified-
• must be one of the Contaminant Identification Codes (see Section VI; Table ID06)
• Position 3 of the violation ID must be 'G' when a wild-card violation contaminant code (i.e.. a contaminant code containing an
asterisk) is specified [E3X]
• must not be a wild-card violation contaminant code (i.e.. a contaminant code containing an asterisk) unless the submitted data Is
for a new violation [E8S]
• must not be a wild-card violation contaminant code (i.e., a contaminant code containing an asterisk) unless the submitted data Is
for a Monitoring and Reporting violation (i.e.. C1103, VIO-CONTAMINANT is W or W) [EBQ]
• must not be a wild-card contaminant group of 0***. 3*** or 4*** (these are not defined as wild-cards)
• must only be a wild-card contaminant group (i.e.. 1*** or 2"*) to indicate a predefined list of contaminants for which a Federal
monitoring requirement exists
• must not be a volatile organic chemical group code (i.e.. position 2 of C1103 is 'U1 or V) unless the violation type is Monitoring and
Reporting or a Notification violation (i.e.. C1105, VIO-TYPE Is TJ3' through W) [GBR]
• must not be a wild-card contaminant group (i.e.. 1 ••" or 2***) nor a volatile organic chemical group code (i.e.. position 2 of C1103
•U' or -V) when the compliance period begin date (i.e., C1107. VIO-COMP-PERIOD-BEGIN-DATE) Is after December 31.1992
• must be M022* or '1030' when the violation type (C1105. VIO-TYPE) indicates an MPL Non-Compliance violation (i.e.. •63") [EORJ
• must be •3100* when the violation type (C1105. VIO-TYPE) indicates a TCR violation (i.e.. "21' through I26>) [EOS]
• must only be *3100> when the violation type (C1105. VIO-TYPE) Is -05'. "Off or -21' through >26> [EQUJ
• must be '50001 when the violation type (Cl 105. VIO-TYPE) indicates a Lead or Copper violation other than MPL Non-Compliance
(i.e., '5V through '621. '64' or >651) [EQO]
• must only be •5000' when the violation type (C1105. VIO-TYPE) indicates a Lead or Copper violation other than MPL Non-Compliance
(i.e.. -Si' through "ST. W or •&•) [EOT]
• Comments
Data element C1105, VIO-TYPE. identifies a type of violation incurred by a public water system.
For violations which were incurred prior to 1/1/93.1*** may be reported for a failure to monitor any of the 10 National Interim Primary Drinking
Water Regulation inorganics. Likewise. 2*" may be reported for a failure to monitor ANY of the 6 National Interim Primary Drinking Water
Regulation organics. In both cases, the FRDS-II computer system generates 10 discrete violations for 1"* and 6 discrete violations for 2***.
Other contaminant Identification numbers are maintained In the following data elements:
• C1291 ENF-LINK-CONTAMINANT
• C1357 NCP-CONTAMINANT
• C2107 SAMPLE-CONTAMINANT
• C3003 VE-CONTAMINANT
This data element must be valued for a new Maximum Contaminant Level (MCL) or Monitoring & Reporting (M&R) violation (types 01 through
04, and 21 through 26) to be inserted into the FRDS-II Data Base.
This data element must be valued for a Maximum Permissible Level (MPL) non-compliance violation (type 63) to be inserted Into the FRDS-II
Data Base.
Effective Date 1/31/93 Release Number: 200 Page: II-128
-------
FRDS-H Data Etement Description Number CliOS
Name: VIO-TYPE
Description
A code value mat represents the type of violation that was incurred by a public water system.
Examples of VIO-TYPE include types such as average MCL, regular monitoring, public notification requirements, etc.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: Dt
Data Qualifiers: PWS-ID
•VIO-ID
Maximum Length: 2
Data Base Record: C1100 VIOLATION-DATA
Data Base Family: .7 Registration Requirement .2
Data Category: 10 Grant Requirement NO
Datatype: CHARACTER Access: . KEY
Picture: X(2> Code Table ID: IPOS
• Edit Criteria
Must be specified when:
» inserting a violation record
• modifying the current value
• Inserting a violation tor certain MCL or Monitoring violations (i.e.. C1105. VIO-TYPE is
-------
FRDS-II Data Element Description Number. C1107
Name: VIO-COMP-PERIOD-BEGIN-DATE
• Description
A value that represents the calendar date of the beginning of a monitoring period in which a public water system was determined to be in
violation of a primary drinking water regulation.
Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: D1
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length: 6
Data Base Record: C1100
Data Base Family: 2
Data Category: JO
Data Type: DATE
Picture: MMPDYY
VIOLATION-DATA
Registration Requirement: _2
Grant Requirement NO
Access: KEY
Code Table ID: N/A
e Edit Criteria
Must be specified when:
• Inserting a violation record
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, In position 1-2;
. day. in position 3 - 4; and
. year, in position 5 - 6
• Must be the same as, or before the current calendar date [EQW]
• must be before the compliance period end date (C1109. VIO-COMP-PERIOD-END-DATE). when the end date has been specified
[EER]
• must not be after the violation awareness date (C1115. VIO-AWARE-DATE) for MCL violations (i.e., C1105. VIO-TYPE is <01*. "Of.
•21* or '22) [E9PJ
• must be after September 30.1989 (09/30/89) when the violation type (C1105. VIO-TYPE) Indicates a Surface Water Treatment Rule
(SWTR) violation (i.e.. "SV. *36' or M11) [ElA)
• must be after June 30,1992 (06/30/92) when the violation type (C1105. VIO-TYPE) indicates a Notification violation (I.e.. W or W)
and the violation contaminant code indicates a Lead and Copper violation (i.e.. C1103, VIO-CONTAMINANT Is '50000 [EIB]
e Comments
Data element Cl 109. VIO-COMP-PERIOD-END-DATE. identifies the ending calendar date of the monitoring period.
Data element C1111. VIO-COMP-PERIOD-MONTHS, identifies the duration (in calendar months) of the monitoring period.
Another period begin date is maintained in C1287, ENF-LINK-PERIOD-BEGIN.
VIO-COMP-PERIOD-BEGIN-DATE must be valued tor a new VIOLATION-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number:
Page: 11-130
-------
FHDS-tl Data Element Description Number C1109
Name: yiO-COMP-PERIOD-END-DATE
• Description
A value that represents the calendar date of the end of a mentoring period in which a public water system was in violation of a primary
drinking water regulation.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: Dl
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length: 6
Data Base Record: C1100
Data Base Family: 7
Data Category: 60
Data Tvoe: DATE
Picture: MMDDYY
VIOLATION-DATA
Registration Requirement:
Grant Requirement
Access:
.• Code Table ID:
4
NO
KEY
N/A
• Edit Criteria
Must be specified when:
• Inserting certain violations (i.e.. C1105, VIO-TYPE is W through -28'. "S3f. '55' through "ST. W. «' or -65} and the violation
duration (Cl 111. VIO-COMP-PERIODMONTHS) is not specified {E9QJ
• modifying the current value
Should not be specified when the violation duration (C1111, V10-COMP-PERIOD-MONTHS) Is specified
When specified:
• must be a six digit numeric calendar date, comprised of.
. month. In position 1 • 2; day. in position 3-4; and year, in position 5-6
• must be before the current calendar date, unless the violation type (C1105. VIO-TYPE) is W. VOT or '41* (EEB]
• must be after June 30.1991 (06/30/91) when the violation type (C1105. VIO-TYPE) Is '5V through -651) [EHY]
• the violation duration must be between t and 12 months, when the vtolaticfj type (C1105. VIO-TYPE) is 121> through •28'[EHCJ .
• the violation duration must be between 1 and 60 months. Inclusive, when the violation type (C1105. VIO-TYPE) Indicates a Regular -:
Montoring violation (i.e., •OS1) and the contaminant code (Cl 103. VIO-CONTAMINANT) indicates a volatile organic chemical group
code (i.e.. position 2 of Cl 103 is 'U1 or V) [EHD]
• the violation duration must be between 1 and 120 months, inclusive, when the violation type (C1105. VIO-TYPE) indicates an MCL.
Monitoring, Notification or Sanitary Survey violation (i.e., •0V through "OS1 or W) [EHF]
• the violation duration must be 1 month when the violation type (Cl 105. VIO-TYPE) is -31'. *36- or '4V [EHK]
• must be greater than the compliance period begin date (Cl 107. VIO-COMP-PEHIOD:BEGIN-DATE) |EGM]
• the violation duration must be 3 months when the violation type (C1105. VIO-TYPE) indicates a Follow-up & Routine E.P. WQP M&R
or a WOP Entry Point Non-Compliance violation (i.e., *54' or '590 [EHM]
• the violation duration must be 6 months when the violation type (C1105, VIO-TYPE) Indicates an Initial Tap Sampling for Pb and Cu.
Initial Water Quality Parameter WQP M&R. or SOWT Recommendation violation (i.e.. 'ST. '53' or -61-) [EHN]
• the violation duration must be 12 months when the violation type (C1105, VIO-TYPE) indicates an LSLR violation (I.e., "641) [EHO]
• the violation duration must be 24 months when the violation type (C1105. VIO-TYPE) Is *58' or tSf (EHP]
• the violation duration must be either 6 or 12 months when the violation type (Cl 105. VIO-TYPE) Indicates a Follow-up & Routine Tap
WQP M&R. WQP Tap Non-Compliance or Public Education violation (i.e.. '55'. <<60> or -65^ (EHR]
• the violation duration must be either 6 or 18 months when the violation type (C1105. VIO-TYPE) is 'ST1 [EHS]
• the violation duration must be 6,12 or 36 months when the violation type (C1105. VIO-TYPE) is >52> |EHT]
• the violation duration must be 6.12.36 or 108 months when the violation type (C1105. VIO-TYPE) Is '56' [EHU]
• the violation duration must be 12.36 or 108 months when the violation type (Cl 105. VIO-TYPE) Is -631 [EHVJ
• must not be after the violation awareness date (C1115. VIO-AWARE-DATE) tor non-MCL violations (I.e.. C1105. VIO-TYPE Is •OS-
through •06', '23' through *26>. *31' •36' or '51* through '651) [E9R]
• the number of months between the compliance period begin date (C1107, VIO-COMP-PERIOD-BEQIN-DATE) and the compliance
period end date (C1109. VIO-COMP-PERIOD-END-DATE) must agree with the violation duration (C1111,
VIO-COMP-PERIOD-MONTHS) when all three are specified (E9OJ
Additionally, If a compliance period end date and the violation duration are both specified and they are Inconsistent in relation to the
compliance period begin date, the worst case scenario will be assumed.
e Comments
Data element Cl 107. VIO-COMP-PERIOD-BEGIN-DATE, identifies the beginning calendar date of the monitoring period.
Data element C1111. VIO-COMP-PERIOD-MONTHS, identifies the duration (in calendar months) of the monitoring period.
If the monitoring period duration (I.e.. C1111. VIO-COMP-PERIOD-MONTHS) Is not reported by the State, this data element must be valued
for a new violation to be inserted into the FRDS-II Data Base for violation types 01 through 28.52. 55 through 57.60.63. and 65.
If this value is not input directly. FRDS-II will assign a value based upon the period of time defined by VIO-COMP-PERIOD-BEGIN-DATE and
VIO-COMP-PERIOD-MONTHS for violation types 01 through 28, 52.55 through 57,60.63. and 65.
If this value is not input directly. FRDS-II will assign a value of 1 month after the VIO-COMP-PERIOD-BEGIN-DATE for violation types 31.36.
and 41
Effective Date 1/31/93 Release Number. 2.00 Page:
-------
FRDS-ll Data Element Description
Number C1111
Name: VJO-COMP-PERIOD-MONTHS
• Description
A numeric value that represents the number of calendar months in a monitoring period during which a public
of a primary drinking water regulation.
• Source • Data Characteristics
syste
i In violation
Form ID:
Data Qualifiers:
FRDS-II Data Transfer File
PWS-ID
VIO-ID
Maximum Length: 3
Data Base Record: C1100
Data Base Family: 7
Data Category: 30
DataTvoe: INTEGER
Picture: 9(3)
VIOLATION-DATA
Registration Reauirement 4
Grant Requirement NO
Access: NON-KEV
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting certain violations (I.e.. Ci 105. VIO-TYPE is -or through -28'. '521. -55' through 'ST. •60>. <63> or *6S>) and the compliance
period end date (C1109. VIO-COMP-PERIOD-END-DATE) is not specified [E9OJ
• modifying the current value
Should not be specified when the compliance period end date (C1109. VIO-COMP-PERIOD-END-DATE) b specified
When specified:
• must be an integer number
• the violation duration must be between 1 and 12 months, when the violation type (C1105. VIO-TYPE) is "21' through *26I [EHC]
• the violation duration must be between 1 and 60 months, inclusive, when the violation type (C1105. VIO-TYPE) Indicates a Regular
Monitoring violation (i.e.. TO') and the contaminant code (C1103, VIO-CONTAMINANT) indicates a volatile organic chemical group
code (i.e.. position 2 of Ci 103 is 'U1 or V) [EHDJ
• the violation duration must be between 1 and 120 months, inclusive, when the violation type (Ci 105. VIO-TYPE) indicates an MCL.
Monitoring, Notification or Sanitary Survey violation (i.e.. '01' through "OS1 or "28") [EHF]
• the violation duration must be 1 month when the violation type (C1105. VIO-TYPE) Indicates an Surface Water Treatment Rule (SWTR)
violation (i.e.. -31'. '36' or Mr) [EHK]
• the violation duration must be 3 months when the violation type (C1105. VIO-TYPE) Indicates a Follow-up & Routine E.P. WOP M&R
or a WOP Entry Point Non-Compliance violation (i.e.. '54' or '59') [EHM]
• the violation duration must be 6 months when the violation type (C1105. VIO-TYPE) Indicates an Initial Tap Sampling for Pb and Cu.
Initial Water Quality Parameter WQP M&R. or SOWT Recommendation violation (i.e.. '51'. '53' or '61 •) [EHN]
• the violation duration must be 12 months when the violation type (C1105. VIO-TYPE) indicates an LSLR violation (i.e.. •&«•) [EHO]
• the violation duration must be 24 months when the violation type (C1105. VIO-TYPE) indicates an OCCT Installation/Demonstration
or SOWT Installation violation (i.e., 'SB1 or '621) tEHPJ
• the violation duration must be either 6 or 12 months when the violation type (Ci 105. VIO-TYPE) Indicates a Follow-up & Routine Tap
WQP M&R, WQP Tap Non-Compliance or Public Education violation (i.e.. '55'. *60* or >65>) [EHR]
• the violation duration must be either 6 or 18 months when the violation type (C1105. VIO-TYPE) Indicates a OCCT Study
Recommendation violation (i.e.. '571) [EHS]
• the violation duration must be 6.12 or 36 months when the violation type (C1105. VIO-TYPE) indicates a Follow-up and Routine Tap
Sampling violation (i.e. '521) [EHT]
• the violation duration must be 6,12. 36 or 108 months when the violation type (C1105. VIO-TYPE) indicates an Initial. Follow-up, or
Routine SOWT M&R violation (i.e.. >56>) [EHUJ
• the violation duration must be 12,36 or 108 months when the violation type (C1105. VIO-TYPE) is *63* (EHV)
• the number ol months between the compliance period begin date (C1107. VIO-COMP-PERIOD-BEGIN-DATE) and the compliance
period end date (C1109. VIO-COMP-PERIOD-END-DATE) must agree with the violation duration (C1111.
V1O-COMP-PERIOD-MONTHS) when all three are specified [E9O]
Additionally, if a compliance period end date and the violation duration are both specified and they are Inconsistent in relation to the
compliance period begin date, the worst case scenario will be assumed
• Comments
Data element C1107. VIO-COMP-PERIOD-BEGIN-DATE. identifies the beginning calendar date of a monitoring period.
Data element Ci 109. VIO-COMP-PERIOD-END-DATE. identifies the ending calendar date of a monitoring period.
If the ending date of the monitoring period (i.e.. C1109. VIO-COMP-PERIOD-END-DATE) is not reported by the State, this data element must
be valued for a new violation to be inserted into the FRDS-II Data Base for violation types 01 through 28, 52,55 through 57.60.63. and 65.
if this value is not input directly. FRDS-II will assign a value based upon the period of time defined by VIO-COMP-PERIOD-BEGIN-DATE and
VIO-COMP-PERIOD-END-DATE for violation types 01 through 28. 52. 55 through 57.60.63. and 65.
If this value is not input directly. FRDS-II will assign a value of 1 for violation types 31. 36. and 41.
Effective Date 1/31/93
Release Number. 200
Page: 11-132
-------
FRDS-II Data Element Description
Name: VIO-AWARE-DATE
Number C1115
• Description
A value that represents the calendar date on which the State became aware of the existence of a violation of a primary drinking water
regulation by a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Mdxirnum Longthi
D1
PWS-ID
VIO-ID
_8
Data Base Record: C1100
Data Base'Family: _7
Data Category: JjO
Data Type: DATE
Picture: MMDDYY
VIOLATION-DATA
Registration Requirement 4
Grant Requirement NO
KEY
Code Table ID:
N/A
• Edit Criteria
Must be specified when:
• Inserting a violation for an MCL violation (i.e., C1105. VIO-TYPE of "OV or -Of) for Inorganic. Organic and Radiological Contaminants
(i.e.. C1103. VIO-CONTAMINANT of Mnnn'. •ftmn1 and '4nnn'. respectively) [E7N]
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of.
. month, in position 1-2;
. day. in position 3 • 4; and
. year, in position 5-6
• must be before the current calendar date, unless the violation type (C1105. VIO-TYPE) indicates a monitoring and reporting violation
(i.e.. -or. -O? or '411) [EEB]
• must not be before the compliance period begin date (C1107. VIO-COMP-PERIOD-BEGIN-DATE) for MCL violations fi.e.. C1105.
VIO-TYPE is -Or. -021. "211 or -221) [E9PJ
• must not be before the compliance period end date (C1109. VIO-COMP-PERIOD-END-DATE) tor non-MCL violations (i.e.. C1105.
VIO-TYPE Is -03' through -OS1. -23' through •26', -31' '36' or '5V through -65-) [E9RJ
• Comments
Data element C1103, VIO-CONTAMINANT. Identifies the contaminant for which a public water system Incurred a violation.
This data element must be valued for a new MCL violation (types 01 and 02) other than Bacfl or Turbidity contaminants to be Inserted into
the FRDS-II Data Base.
Effective Date 1/31/93
Release Number. 2.00
Page:
-------
FRDS-II Data Element Description
Name: VIO-INSERT-DATE
Number C111
• Description
A computed value that represents the calendar date on which a violation data base record was Initially posted to the FRDS-II Data
The term computed, as used here. Implies that this date is not reported by the State.
VIO-INSERT-DATE te determined automatically by the FRDS-II computer system during Its normal course of operation when a new violation
data base record Is initially inserted into the FRDS-II Data Base.
• Source
• Data Characteristics
FRDS-II Data Transfer File
1 GENERATED DATA ITEM •••
Data Base Record: C1100 VIOLATION-DATA
Data Base Family:
Data Category:
Data Type: DATE
Picture: MMDDYY
60
Registration Requirement •
Grant Requirement NO
Access: KEY
Code Table ID: N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day. in position 3 - 4; and
year, in position 5 • 6
e Comments
This date is valued for State reported data only (i.e.. data submitted via DTF transactions).
Other insert dates are maintained in the following data elements:
• C16S PWS-INSERT-DATE
• C811 PWS-MILESTONE-INSERT-DATE
C1213 ENF-INSERT-DATE
C3033 VE-INSERT-DATE*
Effective Date- 1/31/93
Release Number. 2.00
Page: 11-134
-------
FRDS-II Data Element Description
Number C1121
Name: VIO-ANALYSIS-METHOD
• Description
A code value that represents the analysis technique or method lhat was used to obtain an analytical result which led to the Identification of
an MCL violation for a public water system.
• Source
FRDS-II Data Transfer File
Form ID: J31
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length:
• Data Characteristics
Data Base Record: C1100 VIOLATION-DATA
Data Base Family: 2
Data Category: 10
Data Type: CHARACTER
Picture: XO1
Registration Requirement _;
Grant Requirement NO
Code Table ID:
NON-KEY
1121
• Edit Criteria
Must be specified when*
• modifying the current value
Must only be specified when Inserting or modifying a Simple MCL or Average MCL violation (I.e.. C1105. VIO-TYPE of W or TJ21) [EYA]
Should be specified when inserting or modifying a Simple MCL or Average MCL violation (i.e.. C1105. VIO-TYPE of "OV or "020
When specified:
• must be one of the Analysis Method Codes (see Section VI; Table 1121)
• Comments
VIO-ANALYSIS-METHOD Is applicable only to MCL violations.
Data element C1103. VIO-CONTAMINANT. Identifies the contaminant for which a public water system Incurred a violation.
Data element C1123, VIO-ANALYSIS-RESULT. Identifies the analytical result which led to an MCL violation.
Effective Date 1/31/93
Release Number: 2.00
Page: 11-135
-------
FRDS-II Data Element Description
Name: VIO-ANALYSIS-RESULT
Number C11
• Description
A numeric value that represents the result obtained from a single analysis, or the average result obtained from multiple analyses, that led to
the identification of an MCL violation for a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _D1
Data Qualifiers: PWS-ID ''
VIO-ID
Maximum Length: 15
Data Base Record: C1100
Data Base Family: 7
Data Category: .41
Data Type: DECIMAL
Picture: 9(71.9(8)
VIOLATION-DATA
Registration Requirement 4
Grant Requirement NO
Access: NON-KEY
Code Table ID:
N/A
• Edit Criteria
Must be specified when:
• Inserting a violation for an MCL violation (i.e.. C1105. VIO-TYPE of "OV or -02-) for Inorganic. Organic and Radiological Contaminants
(i.e., C1103. VIO-CONTAMINANT of 'Innn'. -2nnn' and '4nnn'. respectively) [E7PJ
• modifying the current value
Must only be specified when inserting or modifying a Simple MCL or Average MCL violation (i.e.. C1105. VIO-TYPE of 101f or '020 [EVA]
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount.te intended
must not be a negative number (EGA]
• Comments
VIO-ANALYSIS-RESULT is applicable only to MCL violations.
Data element C1103. VIO-CONTAMINANT. (dentines the contaminant tor which a public water system Incurred a violation.
This data element must be valued for a new MCL violation (types 01 and 02) other than Bacti or Turbidity contaminants to be inserted into
the FRDS-II Data Base.
Effective Date" 1/3 V93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Name: VIP-MCL-VIOLATED
Number. C112S
Description
A numeric value that repn
public water system
ints the maximum contaminant level which was exceeded that led to the identification of an MCL violation tor a
• Source
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
D1
PWS-ID
VIO-ID
• Edit Criteria
e Data Characteristics
Data Base Record: C1100
Data Base Family: 7
Data Category: 41
Data Tvoe: DECIMAL
Picture: 9(7).9(8)
VIOLATION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
4
NO
NON-KEY
N/A
Must be specified when:
• inserting a violation record for an Simple MCL or Average MCL violation where the Maximum Contaminant Level violated is other than
the Federal MCL
• modifying the current value
Must only be specified when inserting or modifying a Simple MCL or Average MCL violation (i.e.. C1105. VIO-TYPE of W or -021) [EYA]
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount Is Intended
must not be a negative number [EGA]
• Comments
VIO-MCL-VIOLATED is applicable only to MCL violations.
Data element C1103. VIO-CONTAMINANT. Identifies the contaminant for which a public water system Incurred a violation.
Data element C1123. VIO-ANALYSIS-RESULT, identifies the analytical result which led to an MCL violation.
For MCL violations in which the maximum contaminant level differs from the Federal regulation, this data element must be valued for anew
violation to be inserted Into the FRDS-II Data Base.
Effective Date. 1/31/93
Release Number: 200
Page: II • 137
-------
FRDS-II Data Element Description
Name: VIO-SAMPLES-REQUIRED
Number C1127
• Description
A numeric value that represents the number of samples that were required to be collected, analyzed, and reported by a public water system
for a specific monitoring period.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
VIO-ID
_3
Data Base Record: C1100
Data Base Family: 7
Data Category: 30
Data Type: INTEGER
Picture: 9(3)
VIOLATION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
—
NO
NON-KEY
N/A
e Edit Criteria
Must be specified when:
• Inserting a SWTR Monitoring violation (i.e.. C1105. VIO-TYPE is
VIO-MAJOR-VIOLATION-FLAG) is not specified [E9MJ
• modifying the current value
•31* or •36') and the major violation flag (C1131.
Must not be specified when:
Inserting or modifying a MCL violation (i.e.. C1105. VIO-TYPE of -01' or -021) [EXB]
Inserting or modifying a Notification violation (i.e.. C1105. VIO-TYPE of TO* or •Off) [EXL]
Inserting or modifying a TCR violation (i.e., C1105. VIO-TYPE ot "2V. "221 or •28') [EXM]
Inserting or modifying a Treatment Technique violation (i.e.. C1105, VIO-TYPE of *4V) [EXN]
Inserting or modifying a Lead or Copper violation (i.e.. Cl 105. VIO-TYPE of '5V through •eS') [EXD]
Should only be specified for Regular Monitoring (i.e.. C1105. VIO-TYPE of TO*) violations or SWTR Monitoring (i.e.. C1105. VIO-TYPE ot *31*
or "36') violations
When specified:
• must be an integer number
• must be greater than zero [EGG]
For SWTR Monitoring violations, when all three data elements are specified, the percentage difference between the number of samples
required (C1127. VIO-SAMPLES-REQUIRED) and the number of samples taken (C1129. VIO-SAMPLES-TAKEN) must agree with the major
violation flag (C1131. VIO-MAJOR-VIOLATION-FLAG) [E7J]
e Comments
Data element C1103. VIO-CONTAMINANT. Identifies the contaminant for which a public water system Incurred a violation.
Data element Cl 129. VIO-SAMPLES-TAKEN. identifies the number of samples that were actually collected, analyzed, and reported.
Effective Date: 1/31/93
Release Number 200
Page: II • 138
-------
FRDS-II Data Element Description
Name: VIP-SAMPLES-TAKEN
Number C1129
• Description
A numeric value that represents the number of samples that were actually collected, analyzed, and reported by a public water system tor
a specific monitoring period.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: Dl
Data Qualifiers: PWS-ID
V1O-ID
Maximum Length:
Data Base Record: C1100
Data Base Family: .7
Data Category: 30
Data Type: INTEGER
Picture: 9(3)
VIOLATION-DATA
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID:
N/A
• EdN Criteria
Must be specified when:
• Inserting a Regular Monitoring violation (Le.. C1105. VIO-TYPE Is •03') and the major violation flag (C1131,
VIO-MAJOR-VIOLATION-FLA3) is not specified IE9T]
• Inserting a SWTR Monitoring violation (i.e.. C1105. VIO-TYPE is -31' or "36") and the major violation flag (C1131.
VIO-MAJOR-VIOLATION-FLAG) is not specified [E9M]
• modifying the current value
Must not be specified when:
• Inserting or modifying a MCL violation (I.e.. C1105. VIO-TYPE of -Of or -OST) [EXB]
• Inserting or modifying a Notification violation (i.e.. C1105. VIO-TYPE of US' or TO1) [EXL]
• inserting or modifying a TCR violation (I.e., C1105, VIO-TYPE of W. "22* or <28<) [EXMJ
• Inserting or modifying a Lead or Copper violation (Le.. C1105. VIO-TYPE of •sr through •65') [EXD]
cord when the major violation flag (C1131. VIO-MAJCR-VIOLATION-FLAG)
Should not be specified when Inserting or modifying a violatio
is valued
When specified.
• must be an Integer number
• must not be a negative number [EGA]
• must be less than the number of samples required (C1127, VIO-SAMPLES-REQUIRED), when both items are submitted [EEQ
For SWTR Monitoring violations, when all three data elements are specified, the percentage difference between the number of samples
required (C1127, VIO-SAMPLES-REQUIRED) and the number of samples taken (C1129. VIO-SAMPLES-TAKEN) must agree with the major
violation flag (C1131. VIO-MAJOR-VIOLATION-FLAG) [E7J]
Additionally, for Monitoring violations (i.e.. C1105. VIO-TYPE is '03* or W). when the number of samples taken (C1129,
VIO-SAMPLES-TAKEN) and the major violation flag (C1131. VIO-MAJOR-VIOLATION-FLAG) both have been specified, and an inconsistency
exists, the worst case scenario will be assumed [E9Y]
• Comments
VIO-SAMPLES-TAKEN Is applicable only to monitoring or reporting violations.
Data element C1103. VIO-CONTAMINANT, Identifies the contaminant for which a public water system incurred a violation.
Data element C1127, VIO-SAMPLES-REQUIRED. Identifies the number of samples that wen required to be collected, analyzed, and reported.
For monitoring or reporting violations for which the major violation flag (i.e.. C1131. VIO-MAJOR-VIOLATION-FLAG) is not reported by the
State, this data element must be valued for a new violation to be inserted into the FRDS-II Data Base for violation type 03.
If this value is not input directly. FRDS-II will assign a value, as follows:
• zero for violation types 03 and 04 when data element C1131. VIO-MAJOR-VIOLATION-FLAG. Is equal to T
• 001 for violation types 03 and 04 when data element C1131. VIO-MAJOR-VIOLATION-FLAG. Is equal to 'N1
Effective Date J/31/93
Release Number: 200
Page:
-------
FRDS-II Data Element Description Number. C1131
Name: VIO^AJOR-VIOLATION-FLAG
• Description
A code value that Indicates the severity of an M&R violation, major or minor. The major versus minor designation does not apply to a sanitary
survey M&R violation.
The definition of what constitutes a major vs. minor M&R violation varies, dependent upon the rule in question. Refer to the terms "Major
Violation1 and 'Minor Violation1 in the Glossary in Section VIII of the Data Element Dictionary for comprehensive definitions.
• Source e Data Characteristics
FRDS-II Data Transfer File
Form ID: Dl
Data Qualifiers: • PWS-ID
VIO-IP
Maximum Length: J
Data Base Record: C1100 VIOLATION-DATA
Data Base Family: J Registration Requirement
Data Category: JO Grant Requirement NO
Data Type: CHARACTER Access: KEY
Picture: XM) Code Table ID: 1131
• Edit Criteria
Must be specified when:
• modifying the current value
• inserting a Regular Monitoring violation (i.e.. C1105. VIO-TYPE Is TW) and the number of samples taken (C1129.
VIO-SAMPLES-TAKEN) is not specified [E9T]
• inserting a SWTR Monitoring violation (i.e.. C1105. VIO-TYPE is *31' or >36') and the number of samples required (C1127,
VIO-SAMPLES-REQUIRED) or the number of samples taken (C1129. VIO-SAMPLES-TAKEN) is not specified [E9M]
• inserting or modifying a Treatment Technique violation (i.e.. Cl 105. VIO-TYPE of '41 •) [EXNJ
Must not be specified when:
• inserting or modifying a MCL violation (i.e.. C1105. VIO-TYPE of "Or or "020 [EXBJ
• inserting or modifying a Lead or Copper violation (i.e., Cl 105. VIO-TYPE of '5V through 165') [EXD]
Should not be specified when inserting or modifying a violation record for Regular Monitoring (C1105 of "031) or SWTR Monitoring (CT105
of 'SV or •36') violations when the number of samples taken (Cl 129. VIO-SAMPLES-TAKEN) is valued
When specified:
• must be one of the Major/Minor Violation Flag Codes (see Section VI; Table 1131):
•N' - Minor Monitoring Violation
•V - Major Monitoring Violation
For SWTR Monitoring violations, when all three data elements are specified, the percentage difference between the number of samples
required (C1127. VIO-SAMPLES-REQUIRED) and the number of samples taken (C1129. VIO-SAMPLES-TAKEN) must agree with the major
violation flag (C1131. VIO-MAJOR-VIOLATION-FLAG) [E7J]
For TCR Routine Monitoring violations, the major violation flag (C1131. VIO-MAJOR-VIOLATION-FLAG) must agree with the violation type
(C1105. VIO-TYPE) [E7M]
Additionally, for Monitoring violations (i.e.. Cl 105. VIO-TYPE is '03' or W). when the number of samples taken (C1129.
VIO-SAMPLES-TAKEN) and the major violation flag (Cl 131. VIO-MAJOR-VIOLATION-FLAG) both have been specified, and an inconsistency
exists, the worst case scenario will be assumed [E9Y1
• Comments
VIO-MAJOR-VIOLATION-FLAG is applicable only to monitoring or reporting violations.
Data element C1103, VIO-CONTAMINANT, identifies the contaminant for which a public water system Incurred a violation.
Data element Cl 127. VIO-SAMPLES-REQUIRED. identifies the number of samples that were required to be collected, analyzed, and reported.
Data element Cl 129, VIO-SAMPLES-TAKEN. identifies the number of samples that were actually collected, analyzed, and reported.
For monitoring or reporting violations for which the samples taken (i.e.. Cl 129, VIO-SAMPLES-TAKEN) is not reported by the State, this data
element must be valued for a new violation to be inserted into the FRDS-II Data Base for violation type 03.
If this value is not input directly, FRDS-II will assign a value, as follows:
• T for violation types 03 and 04 when data element Cl 129. VIO-SAMPLES-TAKEN. is equal to zero
• 'N' for violation types 03 and 04 when data element C1129. VIO-SAMPLES-TAKEN. Is greater than zero
• •Y1 for violation types 23 and 25
• 'N1 for violation types 24 and 26
• V tor violation types 31 and 36 when data element Cl 129. VIO-SAMPLES-TAKEN, is less than 90% of the value stored in data
element C1127, VIO-SAMPLES-REOUIRED
• 'N1 tor violation types 31 and 36 when data element Cl 129, VIO-SAMPLES-TAKEN, is greater than or equal to 90% of the value stored
in data element C1127. VIO-SAMPLES-REQUIRED
Effective Date. 1/31/93 Release Number 200
-------
FRDS-II Data Element Description
Name: VIO-LAST-UPDATE
Number C1133
• Description
A computed value that represents the calendar date on which a violation was initially posted to the FRDS-II Data Base or when a subsequent
State-supplied violation modification was made.
The term computed, as used here, Implies that this date is not reported by the State.
VIO-LAST-UPDATE to determined automatically by the FRDS-II computer system during Its normal course of operation whenever a violation
data base record to inserted Into the FRDS-II Data Base or when It to subsequently modified.
• Source
Data Characteristics
FRDS-II Data Transfer File
•*• GENERATED DATA ITEM '
Data Base Record: C1100
Data Base Family: 7
Data Cateoorv: 60
Data Tvoe: DATE
Picture: MMDDYY
VIOLATION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1-2;
day, in position 3 - 4; and
year, in position 5 - 6
e Comments
This date is changed for State reported updates only (i.e.. updates submitted via DTP transactions).
Other last update dates are maintained the following data elements:
C7 ST-ANY-DATA-LAST-UPDATE
C9 ST-INV-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
CIS ST-ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-INV-LAST-UPDATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1207 ENF-LAST4JPDATE
C3021 VE-LAST-UPDATE
Effective Date. 1/31/93
Release Number 2.00
Page: II - 141
-------
FRDS-II Data Element Description
Name: VIO-FY
Number C1135
• Description
A computed numeric value that represents the Federal fiscal year In which the State became aware of the violation.
The term computed, as used here. Implies that this value Is not reported by the State. VIO-FY Is detei
computer system during Its normal course of operation.
nined automatically by the FFtDS-ll
• Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C1100
Data Base Family: 7
Data Category: 31
Data Tvoe: INTEGER
Picture: 9(2)
VIOLATION-DATA
Registration Requirement
Grant Reguirement
Access:
Code Table ID:
.
"KEY
N/A
• Acceptable Values
An integer number
The Federal fiscal year in the range 80 to the current fiscal year (90 to present for SWTR violations}. Inclusive
• Comments
Other Federal fiscal year's are maintained In the following data elements:
• C1209 ENF-FY
• C2117 SAMPLE-FY
• C3023 VE-FY
Effective Date. 1/31/93
Release Number: 2JX)
Page: II -142
-------
FRDS-ll Data Element Description
Name: VIO-DATA-ORIGIN
Number C1137
• Description
A code value that represents the source or origin of the various values that are maintained in the C1100. VIOLATION-DATA, data base record.
Examples of VIO-DATA-ORIGIN Include sources or origins such as State reported, reported by an EPA region, generated by the FRDS-ll
computer system during Its normal course of operation, etc.
• Source
• Data Characteristics
FRDS-H Data Transfer File
••* GENERATED DATA ITEM •••
DataBase Record:
Data Base Family:
Data Category:
C1100 VIOLATION-DATA
10
Data Type:
Picture:
CHARACTER
xm
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
ID07
• Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table ID07):
•H' - Headquarters (EPA) supplied data (EPA Use Only)
•R1 - Region (EPA) supplied data (EPA Use Only)
•S1 - State supplied data
• Comments
This value Is not input directly by the State. Rather, it is conveyed to Production Control at the time the data is to be processed. Production
Control then communicates to FRDS-ll the correct value to assign to this data element
Other data origins are maintained in the following data elements:
• C413 PWS-SE-DATA-ORIGIN
• CS17 PWS-GA-DATA-ORIGIN
* • CB09 PWS-MILESTONE-ORIGIN
This value cannot be modified.
C1211 ENF-DATAORIGIN
C3Q25 VE-DATA-ORIGIN
Etlectwe Date. 1/31/93
Release Number. 2.00
Page: 11-143
-------
FRDS-11 Data Element Description
Name: VIO-SE-ID
Number C1143
• Description
A numeric value used to uniquely identify a specific source of water that Is utilized by. or an entity (e.g.. an entry point, a treatment plant.
or other related facility) that is related to. a public water system.
Violations are Incurred by a public water system, not by specific sources or entry points. However, this data element offers the opportunity
to designate a specific source/entity at which the violation was incurred.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: J)l
Data Qualifiers: PWS-ID
VIO-ID
Maximum Length:
Data Base Record: C1100
Data Base Family: 7
Data Category: 31
Data Tvoe: INTEGER
Picture: 9(3)
VIOLATION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
•
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
Must not be specified when inserting or modifying a Lead or Copper violation (i.e.. C1105. VIO-TYPE of '5V through "GST) [EXD]
When specified:
• must be an integer number
• must be less than or equal to 949 [EEH]
• Comments
For Chem/Rad violations, a VIO-SE-ID equal to zero means that the violation is •system* specific. A VIO-SE-ID greater than zero means that
the violation is 'sampling point" specific.
Other source/entity IDs are maintained in the following data elements:
• C401 PWS-SE-ID
• C2119 SAMPLE-SE-ID
• C3031 VE-SE-ID
Effective Date. 1/31/93
Release Number: 2.00
Page: 11-144
-------
FRDS-11 Data Base Record Description Number C11BO
Name: VIO-ENFORCEMENTS
• Description
A SYSTEM 2000 data base record identification name and number.
The C1 ISO. VIO-ENFORCEMENTS. data base record contains data elements that Identify enforcement actions that are related to violations
incurred by a public water system.
The FRDS-II Data Base has one VIO-ENFORCEMENTS data base record for each enforcement action that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: .7 Parent Record: C1100 VIOLATION-DATA
• Record Contents
This data base record contains the following data elements:
• C1181 VIO-UNK-ENF-ID • C1185 VIO-LJNK-FOLLOW4JP-ACTION
• C1183 VIO-LJNK-ENF-DATE
• Comments
Each data element name contained within the VIO-ENFORCEMENTS data base record is prefaced with: VIO-UNK-
Ertectve Date. 1/31/93 Release Number 2.00 Pege: 11-145
-------
FRDS-II Data Element Description
Name: VIO-LINK-ENF-ID
Number C1181
• Description
A computed alphanumeric value that represents a specific
nfo
nt action that Is related to a unique violation.
VIO-UNK-ENF-ID is of the form: yy nnnnn (space inserted tor dartty only)
Where, yy = the Federal fiscal year in which the enforcement action was taken by the State
nnnnn = an enforcement action identification number assigned by the State or generated by tie FRDS-II computer system flhe fat
position consists ol the letter 'E1 if the ID was generated)
The term computed, as used here. Implies that this ID is not reported by the State. VIO-UNK-ENF-ID is determined automatically by the
FRDS-II computer system when the State inserts a new enforcement action into the FRDS-II Data Base.
• Source
• Data'Characteristics
FRDS-II Data Transfer File
••* GENERATED DATA ITEM **•
Data Base Record: C1180 VIO-ENFORCEMENTS
Data Base Family: 7 Registration Requirement •
Data Category: 23 Grant Requirement NO
DataTvoe CHARACTER Access: NON-KEY
Picture: Xm Code Table ID: N/A
• Acceptable Values
An alphanumeric value representing an Enforcement ID (see C1201, ENF-ID)
• Comments
Since multiple enforcement actions can relate to a single violation, the FRDS-II computer system determines what specific enforcement
action(s) are related to each unique violation.
Another enforcement action ID is maintained in data element C1201. ENF-ID.
Effective Date 1/31/93
Release Number:
Page:
-------
FRDS-II Data Element Description
Name: VIO-LINK-ENF-DATE
Number C1183
• Description
A computed value that represents the calendar date on which an enforcement action was taken by the State against a public water system.
The term computed, as used here. Implies that This value Is not reported by the State. VIO-UNK-ENF-DATE is determined automatically by
the FRDS-II computer system during Its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C1180
Data Base Family: 7
Data Category: 60
Data Tyoe: DATE
Picture: MMDDYY
VIO-ENFORCEMENTS
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
N/A
-
• Acceptable Values
A six digit numeric calendar date, comprised of.
month. In position 1 - 2;
day, in position 3 - 4; and
year. In position 5 - 6
• Comments
Another enforcement date is maintained In C1203. ENF-ACTION-DATE.
Effective Date 1/31/93
Release Number: 2.00
Page.
•147
-------
FRDS-ll Data Element Description
Number C118S
• Description
A computed value that represents the enforcer
Name: VIP-LINK-FOLLOW-UP-ACTION
nt action that was taken by the State against a public water system.
The term computed, as used here. Implies that this value is not reported by the State. vIO-UNK-FOLLOW-UP-ACTION Is determined
automatically by the FRDS-ll computer system during Its normal course of operation.
• Source
• Data Characteristics
FRDS-ll Data Transfer File
' GENERATED DATA ITEM *••
Data Base Record: C11BO VIO-ENFORCEMENTS
Data Base Family: _7
Data Category: 10
Data Type: CHARACTER
Picture: XJ3J
Registration Requirement. ^
Grant Requirement
Access:
Code Table 10:
NO
KEY
1009
• Acceptable Values
Entries from the Enforcement Follow-up Action Codes (see Section VI; Table ID09):
• Comments
Another tollow-up action is maintained in C1205. ENF-FOLLOW-UP-ACTION.
Effective Dale 1/31/93^
Release Number: 200
-------
FRDS-II Data Base Record Description
Name: ENFORCEMENT-DATA
Number C1200
• Description
A SYSTEM 2000 data base record Identification name and number.
The C1200. ENFORCEMENT-DATA, data base record contains data elements that characterize an enforcement acton taken by the State
against a public water system in response to a violation.
The FRDS-II Data Base has one ENFORCEMENT-DATA data base record for each enforcement action that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C1000 NON-COMPLIANCE-DATA
• Record Contents
This data base record contains the following data elements:
• C1201 ENF-ID
• C1203 ENF-ACTION-DATE
• C1205 ENF-FOLLOW-UP-ACT1ON
• C1207 ENF-LAST-UPDATE
C1209 ENF-FY
C1211 ENF-DATA-ORIGIN
C1213 ENF-INSERT-DATE
C1215 ENF-COMMENT
• Comments
Each data element name contained within the EN=ORCEMENT-DATA data base record Is prefaced with: ENF-
Effective Date 1/31/93
Release Number.
00
Page: H -149
-------
Description
FRDS-II Data Element Description Number C1201
Name: ENF-ID
An alphanumeric value used to uniquely identify a specific enforcement action taken by the State against a public water system. It is unique
for each public water system within the Federal fiscal year In which the enforcement action was taken by the State.
ENF-ID is of the form: yy nnnnn (space inserted for clarity only)
Where: yy = the Federal fiscal year in which the enforcement action was taken by the State
nnnnn = an enforcement action identification number assigned by the State or generated by the FRDS-II computer system (the first
position consists of the letter *E* if the ID was generated)
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: El
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length: 7
Data Base Record: C1200 ENFORCEMENT-DATA
Data Base Family: J Registration Requirement
Data Category: 23 Grant Requirement NO
Data Type: CHARACTER Access: NON-KEY
Picture: XfT) Code Table ID: N/A
Edit Criteria
Must be specified when:
• inserting, modifying or deleting an enforcement action record
When specified:
• position 1 - 2 must be the Federal fiscal year of the enforcement action
• position 1 - 2 must be greater than 77 and less than or-equal to the current Federal fiscal year
• position 3 must be 'G1 or '£'. or position 3 - 7 must be numeric
• position 3 must not be 'E1 when inserting a enforcement action record
• position 3 must not be 'G1 when modifying or deleting a enforcement action record
• and position 3 is 'G' or •£':
. position 4-7 must be numeric
. position 4-7 must be greater than zero
• and position 1 is neither 'G1 nor •£':
. position 1 - 7 must be numeric
. position 1 - 7 must be greater than zero
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a enforcement action record
. the ID must not exist in the FRDS-II data base tor the PWS, when inserting a enforcement action record
• and position 1 is '£':
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a enforcement action record
Each new enforcement action record must include values tor those data elements within the enforcement action record (C1200.
ENFORCEMENT-DATA) that are identified as Registration Requirement data elements (see 'Data Characteristics1 on this page) [ERR]
• Comments
If desired, the user can have the FRDS-II computer system generate an ENF-ID number by specifying a Group Generation Code (GGC) when
a new enforcement action data base record is to be inserted into the base. This Is accomplished by inserting the GGC In positions 3-7 of
the ENF-ID.
Another enforcement action ID is maintained In data element C1181. VIO-UNK-ENF-ID.
ENF-ID must be valued tor a new ENFORCEMENT-DATA data base record to be inserted into the FRDS-II Data Base.
Eflecbve Date. 1/31/93 Release Number: 2.00 Page:
-------
FRDS-II Data Element Description
Name: ENF-ACTION-DATE
Number C1203
• Description
A value that represents the calendar date on which an enforcement action was taken by the State against a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
El
PWS-ID
ENF-ID
£
Data Base Record: C1200
Data Base Family: J
Data Category: 60
Data Type: DATE
Picture: MMDDYY
ENFORCEMENT-DATA
Registration Requirement 2
Grant Requirement •• NO
Access: KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting an enforcement action record
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1-2,
. day, in position 3 - 4; and
. year. In position 5 - 6
• must be before the current calendar date [EEA]
• Comments
Another enforcement date is maintained In C1183, VIO-LINK-ENF-DATE.
ENF-ACTION-DATE must be valued for a new ENFORCEMENT-DATA data base record to be Inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number: 2.00
Page: II -151
-------
FRDS-II Data Element Description
Number C1205
Name: ENF-FOLLOW-UP-ACTION
• Description
A code value that represents an enforcement action that was taken by the State against a public water system.
• Source
• Data Characteristics
Form 10:
Data Qualifiers:
FRDS-II Data Transfer File
ENF-ID
Maximum Length: 3
Data Base Record: C1200 ENFORCEMENT-DATA
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: XO) Code Table ID:
B
10
Registration Requirement _2
Grant Requirement NO
KEY
ID09
• Edit Criteria
Must be specified when:
• inserting an enforcement action record
• modifying the current value
When specified:
• must be one of the Enforcement Follow-up Action Codes (see Section VI; Table IDQ9)
• Position 1 must be'S' when the data te submitted by the State [EFH]
e Comments
Another follow-up action is maintained in C1185, VIO-UNK-FOLLOW-UP-ACTION.
ENF-FOLLOW-UP-ACTION must be valued tor a new ENFORCEMENT-DATA data base record to be inserted into the FRDS-II Data Base*
Effective Date- 1/31/93
Release Number: 200
Page:
-------
FRDS-II Data Element Description
Name: ENF-LAST-UPDATE
Number C1207
• Description
A computed value that represents the calendar date on which an enforcement action was initially posted to the FRDS-II Data Base or when
a subsequent State-supplied enforcement action modification was made.
The term computed, as used here, implies that this date is not reported by the State.
the FRDS-II computer system during its normal course of operation when an enforceme
Data Base or when It Is subsequently modified.
ENF-LAST-UPDATE is determined automatically by
t action data base record Is Inserted Into the FRDS-II
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM '
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1-2;
day, In position 3 - 4; and
year, in position 5 - 6
Data Base Record: C1200
Data Base Family: 8
Date Category: 60
DataTvoe: DATE
Picture: MMDDYY
ENFORCEMENT-DATA
Grant Requirement
£f**f*fr'
Code Table ID:
NO
KEY
N/A
• Comments
This date is changed for State reported updates only (i.e.. updates submitted via DTP transactions).
Other last update dates are maintained in the following data elements:
.. C7 ST-ANY-DATA-LAST-UPDATE
• C9 ST-INV-LAST-UPDATE
• C13 ST-VIO-LAST-UPDATE
• CIS ST-ENF-LAST-UPDATE
• C17 ST-VE-LAST-UPDATE
C29 ST-SAMPLE-LAST-UPDATE
C167 PWS-INV-LAST-UPDATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1133 V1O-LAST-UPDATE
C3021 VE-LAST-UPDATE
Effective Date- 1/31/93
Release Number: 2.00
Page:
-------
FRDS-II Data Element Description
Name: ENF-FY
Number C1209
• Description
A computed numeric value that represents the Federal fiscal year in which the enforcement action was taken by the State.
The term computed, as used here. Implies that this value is not reported by the State. ENF-FY is determined automatically by the FRDS-II
computer system during its normal course of operation.
• Source
e Data Characteristics
FRDS-II Data Transfer File
••* GENERATED DATA ITEM •••
Data Base Record: C1200
Data Base Family. 8
Data Category: 31
DataTvoe: INTEGER
Picture: 9(2)
ENFORCEMENT-DATA
Registration Requirement
Grant Requirement:
Access:
Code Table ID:
.
NO
KEY
N/A
• Acceptable Values
An integer number
The Federal fiscal year in the range 80 to the current fiscal year, inclusive
• Comments
Other Federal fiscal year's are maintained in the following data elements:
• C1135 VIO-FY
• C2117 SAMPLE-FY
• C3023 VE-FY
Effective Date. 1/31/93
Release Number: 2.00^
Page'
-------
FRDS-II Data Element Description
Name: ENF-DATA-ORIGIN
Number
• Description
A code value that represents the source or origin of the various values that are maintained In the C1200. ENFORCEMENT-DATA, data base
record.
Examples of ENF-DATA-ORIGIN Include sources or origins such as State reported, reported by an EPA region, generated by the FRDS-II
computer system during Its normal course of operation, etc.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM <
Data Base Record: C1200 ENFORCEMENT-DATA
Data Base Family: £
Data Category: _10
Data Type: CHARACTER
Picture: XM) Code Table ID:
Registration Requirement _;
Grant Requirement NO
KEY
1007
• Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table (DOT):
•H- - Headquarters (EPA) supplied data (EPA Use Only)
•R- - Region (EPA) supplied data (EPA Use Only)
•S- . State supplied data
• Comments
This value is not input directly by the State. Rather, it is conveyed to Production Control at the time the data is to be processed. Production
Control then communicates to FRDS-II the correct value to assign to this data element
Other data origins are maintained in the following data elements:
.• C413 PWS-SE-DATA-ORIGIN
' • C517 PWS-GA-DATA-ORIGIN
• C809 PWS-MILESTONE-ORIGIN
This value cannot be modified.
C1137 VIO-DATA-ORIGIN
C3025 VE-DATA-ORIGIN
Effective Date. 1/31/93
Release Number:
Page: II-155
-------
Description
FRDS-II Data Element Description
Name: ENF-INSERT-DATE
Number C1213
A computed value that represents the calendar date on which an enforcement action data base record was Initially posted to the FRDS-II
DataBase.
The term computed, as used here. Implies that this date is not reported by the State. ENF-INSERT-DATE is determined automatically by the
FRDS-II computer system during Its normal course of operation when a new enforcement action data base record is initially inserted into the
FRDS-II Data Base.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day, in position 3 • 4. and
year, in position 5-6
Data Base Record: '01200
Data Base Family:
Data Category: 60
Data Type:
Picture:
ENFORCEMENT-DATA
DATE
MMDDYY
Registration Requirement ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Comments
This date is valued for State reported data only (i.e.. data submitted via DTF transactions).
Other Insert dates are maintained in the following data elements:
• C168 PWS-INSERT-DATE
• C811 PWS-MILESTONE-INSERT-DATE
C1117 VJO-INSERT-DATE
C3033 VE-INSERT-DATE"
Effective Date 1/31/93
Release Number. 2.00
-------
FRDS-II Data Element Description
Name: ENF-COMMENT
Number C1215
• Description
An alphanumeric value that represents any description, characteristic, or attribute that the State or EPA region wants to record tor I
associated enforcement action data base record.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: Jl
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length: 40
Data Base Record: C1200 ENFORCEMENT-DATA
Data Base Family: 8 Registration Requirement
Data Cateoorv: 01 Grant Requirement
Data Type: CHARACTER Access:
Picture: ' X(4) Code Table ID:
.
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
Only one comment is allowed per enforcement action data base record.
Other comments are maintained in the following data elements:
• CB13 PWS-MILESTONE-COMMENT
• C4057 DBA-COMMENT
Effective Date 1/31/93
Release Number: 200
Page: II. 157
-------
FRDS-II Data Base Record Description
Name: ENF-VIQLATIONS
Number C1280
• Description
A SYSTEM 2000 data base record Identification name and number.
The C12BO. ENF-VIOLATIONS. data base record contains data elements that identify a violation that is associated with a unique enforcement
action taken by the State against a public water system.
The FRDS-II Data Base has one ENF-VIOLATIONS data base record for each violation that is related to a unique enforcement action.
• Data Characteristics
Data Type: RECORD Data Base Family: B_
Parent Record: C1200 ENFORCEMENT-DATA
• Record Contents
This data base record contains the following data elements:
• C1281 ENF-UNK-VIO-ID
• C1283 ENF-LINK-RANGE-BEGIN
• C12B5 ENF-LINK-RANGE-END
• C12B7 ENF-LINK-PERIOD-BEGIN
C1289 ENF-LINK-VIO-TYPE
C1291 ENF-UNK-CONTAMINANT
C1293 ENF-UNK-TYPE
• Comments
Each data element name contained within the ENF-VIOLATIONS data base record is prefaced with: ENF-UNK-
Eflective Date. 1/31/93
Release Number: 200
Page:
-------
FRDS-II Data Element Description
Name: ENF-LINK-VIO-ID
Number C1281
• Description
A computed alphanumeric value that represent a specific violation that is related to a unique enforcement action.
ENF-UNK-VIO-ID Is of the form: yy nnnnn (space nserted for clarity only)
Where: yy = the Federal fiscal year In which the State became aware of the violation
nnnnn = a violation Identification number assigned by the State or generated by the FRDS-II computer system (the first position
consists of the letter VH the ID was generated)
The term computed, as used here. Implies that this ID Is not reported by the State. ENF-LINK-VIO-ID is determined automatically by the
FRDS-II computer system when the State inserts a new violation data base record Into Ihe FRDS-II Data Base.
Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: E1
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length:
Data Base Record: C1280 ENF-VIOLATIONS
Data Base Family: 8 Registration Requirement
Data Category: 22 Grant Requirement
Data Type: CHARACTER Access:
Picture: XfT) Code Table ID:
.
NO
NON-KEY
N/A
e Edit Criteria
Must bo spBCffiod whom
• Inserting a violation link record with a •YSOOO1
When specified:
• must be an alphanumeric value
• Position 1 through 2 must be between "78" and the current fiscal year [EIP]
• Position 3 of the violation link violation ID must be V or position 3 through 7 of the violation link violation ID must be numeric |E8M]
• Position 4 through 7 of the violation link violation ID must be numeric and greater than zero [E8N]
Additionally, the enforcement action date (C1203. ENF-ACTION-DATE) and enforcement action follow-up action (C1205.
ENF-FOLLOW-UP-ACTION) must also be specified [E6U]
e Comments
Since multiple violations can relate to a single enforcement action, the FRDS-II computer system determines what specific viofation(s) are
related to each unique enforcement action.
If X5000 is used. ENF-LINK-VIO-ID will be generated only If the specified finks are properly resolved If YSOOO to used, ENF-UNK-VIO-ID will
be generated from the YSOOO specification on Data Capture Form E1 only If the specified violation Is found.
If 25000 Is used. ENF-UNK-VIO-ID will be generatec only If the specified links are properly resolved Another violation ID Is maintained In data
element C1101. VIO-ID.
Effective Date 1/31/93
Release Number 2.00
Page: II -159
-------
FRDS-II Data Element Description
Name: ENF-LINK-RANGE-BEGIN
Number C1283
• Description
The beginning dale of the period covering those violations which are related to the associated enforcement action (i.e.. ASSOCIATED
VIOLATION RANGE).
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .El
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length: 6
Data Base Record: C1280 ENF-VIOLAT1ONS
Data Base Family: .8
Data Category: JjO
Data Type: DATE
Picture: MMDDYY
Registration Requirement: ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting a violation link record with a •XSOOO1 [E9U]
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1 - 2;
. day. in position 3 - 4; and
. year. In position 5 • 6
• must be before the violation link range end date (C1285, ENF-UNK-RANGE-END) [E9X]
• must not be after the enforcement action date (C1203. ENF-ACTION-DATE) [EOS]
Additionally, the enforcement action date (C1203, ENF-ACTION-DATE) and enforcement action follow-up action (C1205,
ENF-FOLLOW-UP-ACTION) must also be specified [E6UJ
• Comments
This data element is input as a portion of the XSOOO specification on Data Capture Form E1.
Effective Date- 1/31/93
Release Number: 2.00
Page: II-160
-------
FRDS-II Data Element Description
Name: ENF-LINK-RANGE-END
Number C1285
• Description
The ending date of the period covering those violations which are related to the associated enforce
RANGE).
int action 0.e.. ASSOCIATED VIOLATION
• Source
Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
ENF-ID
J§
Data Base Record: C1280 ENF-VIOLATIONS
Data Base Family: .8
Data Category: J30
Data Type: DATE
Picture: MMDDYY
NO
Registration Requirement:
Grant Requirement
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
When specified:
• must be a six digit numeric calendar date, somprised of:
. month. In position 1 • 2;
. day, In position 3 • 4; and
. year, In position 5 • 6
• must be after the violation link rarge begin date (C1283, ENF-LINK-RANGE-BEGIN) [E9X]
• must not be after the enforcemeir acton date (C1203. ENF-ACTION-DATE) [E9S]
Additionally:
• a violation link range begin date (C12S3. ENF-LINK-RANGE-BEGIN) must also be specified [E9U]
• the enforcement action date (C12D3. ENF-ACTION-DATE) and enforcement action follow-up Action (C1205.
ENF-FOLLOW-UP-ACTION) must alsc be specified [E6U]
• Comments
This data element is input as a portion of the X5000 specification on Data Capture Form El.
If ENF-LINK-RANGE-END Is not specified In an X5000 specification, a value Is assigned which Is equal to the value stored In data element
C1203. ENF-ACTION-DATE.
Effective Date 1/31/93
Release Number. 2.00
-------
FRDS-II Data Element Description
Name: ENF-LINK-PERIOD-BEGIN
Number C1287
• Description
A value that represents the calendar date of the beginning of the monitoring period during which a violation that is related to the entoreement
action (i.e.. part of the ASSOCIATED VIOLATION CONTAMINANT GROUP.) was incurred.
Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
ENF-ID
6
Data Base Record: C1280
Data Base Family: 8
Data Category: 60
Data Type: DATE
Picture: MMDDYY
ENF-VIOLATIONS
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• inserting or modifying a violation link record using a 'Z50001 [E9Z]
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1 - 2;
. day. in position 3 - 4; and
. year, in position 5 - 6
• must not be after the enforcement action date (C1203. ENF-ACTION-DATE) [E9S]
Additionally, the enforcement action date (C1203, ENF-ACTION-DATE) and enforcement action follow-up action (C1205.
ENF-FOLLOW-UP-ACTION) must also be specified [E6U]
e Comments
This data element is input as a portion of the 25000 specification on Data Capture Form El.
Effective Date. 1/31/93
Release Number: 200
Page: II • 162
-------
FRDS-II Data Element Description
Name: ENF-LINK-VIO-TYPE
Number C1289
• Description
A value that represents the violation type of a violation that Is related to the enforcement action (i.e., part of the ASSOCIATED VIOLATION
CONTAMINANT GROUP).
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
ENF-ID
-2
Data Base Record: C1280 ENF-VIOLATIONS
Data Base Family 8 Registration Reauirem
Data Cateoory: 10 Grant Reauirement
Data Type: CHARACTER Access:
Picture: X(2) Code Table ID:
ent •
NO
NON-KEY
ID08
• Edit Criteria
Must be specified when:
• inserting or modifying a violation link recorc using a •Z5000* [E9Z]
When specified:
• must be one of the Violation Type Codes (see Section VI; Table ID08)
Additionally:
• the enforcement action date (C1203, ENF-ACTION-DATE) and enforcement action follow-up action (C1205.
ENF-FOLLOW-UP-ACTION) must also be specified [E6U]
• for certain MCL or Monitoring violations (i.e., C1105. VIO-TYPE Is W through W or *2r through "2ff). the violation link contaminant
code must be also be specified [E8U]
• Comments
This data element is Input as a portion of the Z5000 specification on Data Capture Form E1.
Another violation type code is maintained In C1105 VIO-TYPE.
Effective Date 1/31/93
Release Number: 2.00
-------
Description
FRDS-II Data Element Description
Name: ENF-LINK-CONTAMINANT
Number C1291
A code value that represents an identification number of a contaminant for a violation that Is related to the enforcement action (i.e.. part of
the ASSOCIATED VIOLATION CONTAMINANT GROUP).
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: El
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length: 4
Data Base Record: C1280 ENF-VIOLATIONS
Data Base Family: 8
Data Category: JO
Data Type: CHARACTER
Picture: X(4)
Registration Requirement
Grant Requirement
NO
Code Table ID:
NON-KEY
ID06
e Edit Criteria
When specified:
• must be one of the Contaminant Identification Codes (see Section VI; Table ID06)
• must not be a wild-card violation link contaminant code (i.e., a contaminant code containing an asterisk) unless the submitted data
Is for a Monitoring and Reporting violation (i.e.. C1291. ENF-UNK-CONTAMINANT is •03* or W) [E8Q]
• must not be a volatile organic chemical group code (i.e., position 2 of C1291 is 'U' or V) unless the violation link violation type is
Monitoring and Reporting or a Notification violation (i.e.. C1289, ENF-UNK-VIO-TYPE is W through "06') [E8R]
• Inserting or modifying a violation link record for certain MCL or Monitoring violations (i.e.. C1289. ENF-UNK-VIO-TYPE is "01' through
•04' or -21" through -26') [E8U]
Additionally:
• a violation link violation type (C1289. ENF-UNK-VIO-TYPE) and violation link range begin date (C1287. ENF-UNK-PERIOD-BEGIN)
must also be specified [E9Z]
• the enforcement action date (C1203, ENF-ACTION-DATE) and enforcement action follow-up action (C1205.
ENF-FOLLOW-UP-ACTION) must also be specified [E6U]
e Comments
This data element value is generated from the Z5000 specification on Data Capture Form El.
Other contaminant identification numbers are maintained in the following data elements:
• C1103 VIO-CONTAMINANT
• C1357 NCP-CONTAMINANT
• C2107 SAMPLE-CONTAMINANT
• C3003 VE-CONTAMINANT
Effective Date 1/31/93
Release Number- 200
Page:
-------
FRDS-II Data Element Description
Name: ENF-L1NK-TYPE
Number C1293
• Description
A computed code value that represents the method used to relate violations to the enforcement action.
The term computed, as used here. Implies that this value Is not reported by the State. ENF-UNK-TYPE Is determined automatically by the
FRDS-II computer system during its normal course of operation.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID. J1
Data Qualifiers: PWS-ID
ENF-ID
Maximum Length: _1_
Data Base Record: C1280 ENF-VIOLATIONS
Data Base Family: 8 Registration Requirement
Data Category: 10 ' Grant Requirement
Data Type: CHARACTER Access:
Picture: X(1) Code Table ID:
NO
KEY
1293
• Edit Criteria
Entries from the Associated Link Type Codes (below):
•X- - link Is by ASSOCIATED VIOLATION DATE RANGE (i.e.. from X5000 transaction on Data Capture form E1)
•Y* - link is by ASSOCIATED VIOLATION ID (i.e.. from Y5000 transaction on Data Capture form E1)
•Z1 - link is by ASSOCIATED VIOLATION CONTAMINANT GROUP 0-«-. trom 25000 transaction on Data Capture form El)
• Comments
None
Effective Date 1/31/93
Release Number: 200
Page: II -165
-------
FRDS-II Data Base Record Description Number C1300
Name: NCP-CNTL-NODE __
• Description
A SYSTEM 2000 data base record identification name and number.
The C1300. NCP-CNTL-NODE. data base record contains no data elements, ft is Included In the FRDS-II Data Base solely for the purpose
of efficiently processing violation, enforcement action, and non-compliance profile data.
The FRDS-II Data Base has one NCD-CNTL-NODE data base record for each public water system that has at least one
NON-COMPLIANCE-PROFILE data base record.
• Data Characteristics
Data Type: RECORD Data Base Family: J Parent Record: C1000 NON-COMPLIANCE-DATA
• Record Contents
This data base record doesn't contain any data elements
• Comments
None
Effective Date: 1/31/93 Release Number: 2.00 Pege: 11-166
-------
FRDS-II Data Base Record Description Number C1350
Name: NON-COMPLIANCE-PROFILE
• Description
A SYSTEM 2000 data base record Identification name and number.
The C1350. NON-COMPUANCE-PROFILE. data base record contains data elements that characterize the compliance status (i.e.. violations
and enforcement actions) of a public water system for a specific period of time.
The number of NON-COMPUANCE-PROFILE data base records in the FRDS-II Data Base for a public water system to dependent upon a
number of factors. They are:
• the number of non-compliance windows (i.e., periods of time) that have been established by the FRDS Data Base Administrator; .
• the contaminants) for which MCL and/or major M&R violations were encountered that fall within these non-compliance windows;
and
• the absence or presence of enforcement actions taken by the State that fall within these non-compliance windows.
e Data Characteristics
Data Type: RECORD Data Base Family:
Parent Record: C1300 NCP-CNTL-NODE
e Record Contents
This data base record contains the following data elements-
C1351 NCP-WINDOW-BEGIN-YYMM
C1353 NCP-WINDOW-MONTHS
C1355 NCP-WINDOW-PURPOSE
C1357 NCP-CONTAMINANT
C1359 NCP-MCL-VIOLATIONS
C1361 NCP-MCL-DURATION
C1363 NCP-MON-VIOLATIONS
C1365 NCP-MON-DURATION
C1367 NCP-ENF-ACTIONS
e Comments
Each data element name contained within the NON-COMPLIANCE-PROFILE data base record Is prefaced with... NCP-
Eftective Date 1/31/93
Release Number 2.00
Page: II • 167
-------
FRDS-II Data Element Description
Number C1351
Name: NCP-WINDOW-BEGIN-YYMM
• Description
A computed numeric value that represents the calendar year and month in which a non-compliance profile window begins.
NCP-WINDOW-BEQIN-YYMM Is of the form: yymm (space inserted tor clarity only)
Where: yy = the calendar year in which a non-compliance profile window begins
mm = the calendar month in which a non-compliance profile window begins
.The term computed, as used here, implies that this calendar year and month is not reported by the State. It is determined automatically by
the FRDS-II computer system during its normal course of its operation when a new non-compliance profile data base record is inserted into
the FRDS-II Data Base.
Source
FRDS-II Data Transfer File
GENERATED DATA ITEM •••
• Data Characteristics
Data Base Record: C1350
Data Base Family: _9
Data Category: 61
Data Type: INTEGER
Picture:
NON-COMPLIANCE-PROFILE
9(4)
• Acceptable Values
A four digit numeric calendar date, comprised of:
year, in position 1 - 2; and
month, in position 3 - 4
In the range 7801 (i.e., January. 1978) to the current year and month, inclusive
Registration Requirement: _;
Grant Requirement NO
Access:
Code Table ID:
KEY
N/A
• Comments
Data element C1353. NCP-WINDOW-MONTHS, identifies the number of consecutive calendar
non-compliance profile window.
that are represented in a
Effective Date. 1/31/93
Release Number 200
Page:
-------
FRDS-II Data Element Description
Name: NCP-WINDOW-MONTHS
• Description
A computed numeric value that represents the nurrber of consecutive calendar months that are reflected In a non-compliance profile window.
The term computed, as used here, implies that Mis number Is not reported by the State. It Is determined automatically by the FRDS-II
computer system during its normal course of Its operation when a new norvcomplianoa profile data base record Is Inserted Into the FRDS-II
DataBase.
• Source
• Data Characteristics
FRDS-II Data Transfer File
•** DBA SUPPLIED •••
• Acceptable Values
An integer number
Entries from the NCP Window Sizes (below):
•03' - three months
•1? • twelve months
•24" - twenty-four months
^36* - thirty-six months
•48'- forty-eight months
Data Base Record: C1350
Data Base Family: 9
Data Category: 30
Data Type: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement
Grant Requirement:
AOQOfHE'
Code Table ID:
.
NO
NON-KEY
N/A
(for BACH and Turbidity only)
• Comments
Data element C1351. NCP-WINDOW-BEGIN-YYMM. Identifies the calendar year and month In which a non-compliance profile window begins.
Effective Date. 1/31/93
Release Number: 200
Page: 11-169
-------
FRDS-II Data Element Description
Name: NCP-WINDOW-PURPOSE
Number C13S5
• Description
A computed alphanumeric value that repr
nts the purpose for which a non-compliance profile window was established.
Examples of NCP-WINDOW-PURPOSE Include purposes such as SNC determination, trend analysis, special study, etc.
The term computed, as used here. Implies that this code value is not reported by the State. It is assigned by the FHDS Data Base
Administrator.
• Source
• Data Characteristics
FRDS-II Data Transfer File
DBA SUPPLIED'
Data Base Record: C1350 NON-COMPLIANCE-PROFILE
Data Base Family: 9
Data Category: 01
Data Type: CHARACTER
Picture: X(4)
Registration Requirement
Grant Requirement:
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An alphanumeric value
• Comments
None
Effective Date- 1/31/93
Release Number:
Page: II -170
-------
FRDS-II Data Element Description
Name: NCP-CONTAMINANT
Number C1357
• Description
A computed numeric value that represents an identification number of a contaminant tor which a non-compliance profile window has been
established.
The term computed, as used here, Implies that this code value Is not reported by the State. It Is determined automatically by the FRDS-II
computer system during Its normal course of its operation when a new non-compliance profile data base record Is Inserted into the FRDS-II
DataBase.
• Source
e Data Characteristics
FRDS-II Data Transfer File
•" DBA SUPPLIED •"
Data Base Record: C1350 NON-COMPLIANCE-PROFILE
Data Base Family: JJ
Data Category: 10
Data Type: CHARACTER
Picture: XM)
Registration Requirement ^
Gram Requirement NO
Access: KEY
Code Table ID: IPOS
• Acceptable Values
Entries from the Contaminant Identification Codes Non-complia
i Profile Related (see Section VI; Table ID06)
In addition to contaminants selected from the Contaminant Identification Codes (see Section VI; Table ID06). the following summary
contaminants are also computed for ALL contaminants:
•2-'
•4-'
•GRND1
- total of all contaminant
e Comments
Other contaminant Identification numbers are maintained in the following data elements:
• C1103 VIO-CONTAMINANT
• C1291 ENF-UNK-CONTAMINANT
• C2107 SAMPLE-CONTAMINANT
• C3003 VE-CONTAMINANT
Effective Date. 1/31/93
Release Number: 2.00
Page: Jl -171
-------
FRDS-II Data Element Description
Number C1359
Description
Name: NCP-MCL-VIOLATIQMS
A computed numeric value that represents the total number of MCL violations that a public water system had during the subject
non-compliance profile window for the subject contaminant
The term computed, as used here. Implies that this number Is not reported by the State. It is determined automatically by the FRD&II
computer system during its normal course of its operation when a new non-compliance profile data base record Is Inserted Into the FRDS-II
DataBase.
• Source
• Data Characteristics
FRDS-il Data Transfer File
' GENERATED DATA ITEM
Data Base Record: C1350
Data Base Family: 9
Data Category: 30
Data Type: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement
Grant Requirement
Access:
Code Table ID:
•
NO
NON-KEY
N/A
• Acceptable Values
An integer number
• Comments
Data element C1351. NCP-WINDOW-BEGIN-YYMM. Identifies the calendar year and month in which a norvcompliance profile window begins.
Data element C1353. NCP-WINDOW-MONTHS, identifies the number of consecutive calendar months that are represented in a
non-compliance profile window.
Data element C1357. NCP-CONTAMINANT. identifies a contaminant reflected in a norvcompliance profile window.
Data element C1361. NCP-MCL-DURATION. Identifies the total number of calendar months In which a public water system was In violation
of a MCL regulation for a non-compliance profile window end contaminant
Etlective Date 1/31/93
Release Number: 200
Page. 11-172
-------
FRDS-II Data Element Description
Number. C1361
Name: NCP-MCL-DURATION
• Description
A computed numeric value that represents the total number of calendar months hi which a public water system had an MCL violation during
the subject non-compliance profile window for tie subject contaminant
The term computed, as used here, implies tfur this number Is not reported by the State. It is determined automatically by the FRDS-II
computer system during Its normal course of its operation when a new non-compliance profile data base record Is Inserted Into the FRDS-II
DataBase.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM *"
Data Base Record: C1350
Data Base Family: 9
Data Category: 30
Data Tvoe: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement -
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An Integer number
• Comments
It is important to note that In no case will NCP-MCL-DURATION exceed NCP-WINOOW-MONTHS. Thus, MCL violation durations are not
double counted. For example, if a public wate- system had an Arsenic MCL violation and a Selenium MCL violation during the same 12
month monitoring period. NCP-MCL-DURATION for that 12 month monitoring period would be 12. not 24.
Data element C1351. NCP-WINDOW-BEGIN-YYMM. Identifies the calendar year and month In which a non-compliance profile window begins.
Data element C1353. NCP-WINDOW-MONTHS. Identifies the number of consecutive calendar months that are represented In a
non-compliance profile window.
Date element C1357. NCP-CONTAMINANT, identifies a contaminant reflected in a non-compliance profile window.
Data element C1359. NCP-MCL-VIOLATIONS. Identifies the total number of MCL violations that a public water system had for a
non-compliance profile window and contaminart
Effective Date 1/31/93
Release Number. 2.00
Page: 11-173
-------
FRDS-II Data Element Description
Name: NCP-MON-VIOLATIONS
Number. C1363
• Description
A computed numeric value that represents the total number of major M&R violations that a public water system had during the subject
non-compliance profile window for the subject contaminant
The term computed, as used here. Implies that this number Is not reported by the State. It is determined automatically by the FRDS-II
computer system during its normal course of its operation when a new non-compliance profile data base record is Inserted into the FRDS-II
DataBase.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM •"
Data Base Record: C13SO
Data Base Family: _9
Data Category: 30
Data Type: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement -
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An Integer number
• Comments
Data element C1351. NCP-WINDOW-BEGIN-YYMM. Identifies the calendar year and month In which a norvcomplianoa profile window begins.
Data element C1353. NCP-WINDOW-MONTHS. Identifies the number of consecutive calendar months that are represented in a
non-compliance profile window.
Data element C1357. NCP-CONTAMINANT. identifies a contaminant reflected in a norvcompllance profile window.
Data element C1365, NCP-MON-DURATION. identifies the total number of calendar months In which a public water system had a majbr
monitoring or reporting violation for a norvcomplianoa profile window and contaminant.
Etlective Date- 1/31/93
Release Number. 2.00
Page:
-------
FRDS-II Data Element Description
Name: NCP-MON-DURATION
Number C1365
• Description
A computed numeric value that represents the total number of calendar months in which a public water system had a major M&R violation
during the subject non-compliance profile window tor the subject contaminant
The term computed, as used here, implies that this number is not reported by the State. It is determined automatically by the FRDS-II
computer system during Its normal course of its operation when a new non-compliance profile data base record is inserted into the FRDS-II
DataBase.
• Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C1350
Data Base Family: 9
Data Category: 30
Data Tvoe: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
JJ2
NON-KEY
N/A
• Acceptable Values
An integer number
e Comments
It is important to note that In no case will NCP-MON-DURATION exceed NCP-WINDOW-MONTHS. Thus, -monitoring or reporting violation
durations are not double counted. For example, if a public water system had an Arsenic monitoring or reporting violation and a Selenium
monitoring or reporting violation during the same 12 month monitoring period. NCP-MON-DURATION for that 12 month monitoring period
would be 12. not 24.
Data element C1351. NCP-WINDOW-BEGIN-YYMM, Identifies the calendar year and month in which a n
mpliance profile window begins.
Data element C1353. NCP-WINDOW-MONTHS. Identifies the number of consecutive calendar months that are represented In a
non-compliance profile window.
Data element C1357. NCP-CONTAMINANT, Identifies a contaminant reflected In a non-compliance profile window.
Data element C1363. NCP-MON-VIOLAT1ONS. Identifies the total number of monitoring or reporting violations that a public water system had
tor a non-compliance profile window and contaminant.
Effective Date. 1/31/93
Release Number 2.00
Page: II -175
-------
FRDS-II Data Element Description
Name: NCP-ENF-ACTIONS
Number C1367
• Description
A computed numeric value that represents the total number of enforcement actions that were taken by the State against a public water
system's violations during the subject non-compliance profile window for a specific contaminant
The term computed, as used here. Implies that this number Is not reported by the State. It is determined automatically by the FRDS-II
computer system during its normal course of its operation when a new non-compliance profile data base record Is inserted Into the FRDS-II
Data Base.
e Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM '
Data Base Record: C1350
Data Base Family: 9
Data Category: 30
DataTvoe: INTEGER
Picture: 9(3)
NON-COMPLIANCE-PROFILE
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
NON-KEY
N/A
e Acceptable Values
An integer number
e Comments
Enforcement actions which are not contaminant specific will be saved Jn a window for which there Is no contaminant
Data element C1351. NCP-WINDOW-BEGIN-YYMM. identifies the calendar year and month in which a non-compliance profile window begins.
Data element C1353. NCP-WINDOW-MONTHS. identifies the number of consecutive calendar months that are represented in a
non-compliance profile window.
Data element C1357. NCP-CONTAMINANT. identifies a contaminant reflected in a non-compliance profile window.
Effective Date' 1/31/93
Release Number 200
Page: II • 176
-------
FRDS-ll Data Base Record Description Number C2000
Name: SAMPLE-DATA-CNTL-NODE
• Description
A SYSTEM 2000 data base record identification name and number.
The C2000, SAMPLE-DATA-CNTL-NODE. data base record contains no data elements. It is Included In the FRDS-ll Data Base tar the purpose
of efficiently processing sample data.
The FRDS-ll Data Base has one SAMPLE-DATA-CNTL-NODE data base record tor each public water system that has at least one sample
—I— •»•*.. J ••> CDA
reponea ID trA.
• Data Characteristics
Data Type: RECORD Data Base Family: J4 Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record doesn't contain any data elements
• Comments
Effective Date 1/31/93 Release Number: 2.00 Page: 11-177
-------
FRDS-II Data Base Record Description
Name: SAMPLE-DATA
Number C2100
• Description
A SYSTEM 2000 data base record Identification name and number.
The C2100. SAMPLE-DATA, data base record contains data elements that characterize a sample that has been taken for a public water
system.
The FRDS-II Data Base has one SAMPLE-DATA data base record for each sample that has been reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: 14
Parent Record: C2000 SAMPLE-DATA-CNTL-NODE
• Record Contents
This data base record contains the following data elements:
• C2101 SAMPLE-ID
• C2103 SAMPLE-BEGIN-DATE
• C2105 SAMPLE-END-DATE
C2107 SAMPLE-CONTAMINANT
C2111 SAMPLE-ANALYSIS-RESULT
C2117 SAMPLE-FY
• Comments
Each data element name contained within the SAMPLE-DATA data base record is prefaced with ... SAMPLE-
Effective Date- 1/31/93
Release Number: 200
Page. II • I7i
-------
FRDS-II Data Element Description Number C2101
Name: SAMPLE-ID
• Description
An alphanumeric value used to uniquely identify a specific sampling occurrence for lead as It occurs under the Lead and Copper Rule.
SAMPLE-ID Is of the form: nnnnn
Where: nnnnn <= a sample identification number assigned by the State or generated by the FRDS-II computer system (the first position
consists of the letter'S1 if the ID was generated)
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID: _H1
Data Qualifiers: PWS-ID
SAMPLE-ID
Maximum Length: £
Data Base Record: C2100 SAMPLE-DATA
Data Base Family: _14 Registration Requirement
Data Category: 26 Grant Requirement NO
Data Type: CHARACTER Access: NON-KEY
Picture: X(5) Code Table ID: N/A
• Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a sample record [E4W]
When specified:
• position 1 must be 'G1 or "S1, or position 1 - 5 must be numeric [E1S]
• position 1 must not be *S' when inserting a sample record [E2V]
• position 1 must not be "G1 when modifying or deleting a sample record [E2W]
• and position 1 is 'G' or "SV
. position 2 - S must be numeric [E3JJ
. position 2-5 must be greater than zero
• and position 1 is neither 'G' nor 'SV
. position 1 - 5 must be numeric
. position 1 - 5 must be greater than zero
. the ID must exist in the FRDS-II data base for the PWS, when modifying or deleting a sample record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a sample record
• and position 1 is 'SV
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a sample record
Each new sample record must include values for those data elements within the sample record (C2100, SAMPLE-DATA) that are Identified
as Registration Requirement data elements (see 'Data Characteristics1 on this page) [ERR]
• Comments
If desired, the user can have the FRDS-II computer system generate a SAMPLE-ID number by specifying a Group Generation Code (GGC)
when a new sample data base record Is to be Inserted into the data base.
This Is accomplished by substituting the GGC for an actual ID (I.e., Gnnnn where ... the letter 'G' tells FRDS-II to generate the ID and the
•nnnn' is an arbitrary number assigned to all related C2100. SAMPLE-DATA, data elements so that their logical grouping will remain Intact).
SAMPLE-ID must be valued for a new SAMPLE-DATA data base record to be Inserted into the FRDS-II Data Base.
Etlective Date 1/31/93 Release Number 2.00 Page: II -179
-------
FRDS-II Data Element Description
Name: SAMPLE-BEGIN-DATE
Number. C2103
• Description
A value that represents the calendar date of the first day of the monitoring period in which 90th percentile data for lead was acquired.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length
HI
PWS-ID
SAMPLE-ID
.6
Data Base Record: C2100 SAMPLE-DATA
Data Base Family: 14
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting a sampling record
• inserting a sample record for Lead (i.e.. C2107. SAMPLE-CONTAMINANT of 'PB901) [E7R]
• modifying the current value
When specified.
• must be a six digit numeric calendar date, comprised of:
. month, in position 1-2;
. day. in position 3 - 4; and
. year, in position 5 - 6
• must be after June 30.1991 (06/30/91) [EHZ]
• must be the same as. or before the current calendar date [EQW]
• the sample begin date (C2103. SAMPLE-BEGIN-DATE) must be before the sample end date (C2105. SAMPLE-END-DATE) [EBK]
• the sample begin date (C2103. SAMPLE-BEGIN-DATE) must be at least six months before the sample end date (C2105.
SAMPLE-END-DATE), when the sample contaminant (C2107. SAMPLE-CONTAMINANT) is 'PB901 [E8L]
• Comments
Data element C2105. SAMPLE-END-DATE, identifies the end of the monitoring period.
SAMPLE-BEGIN-DATE must be valued for a new SAMPLE-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date. 1/31/93
Release Number. 2.00
Page:
-------
FRDS-II Data Element Description
Name: SAMPLE-END-DATE
Number C2105
• Description
A value that represents the calendar date of the last day of the monitoring period In which 90th peroantile data tor lead was acquired.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: H1
Data Qualifiers: PWS-ID
SAMPLE-ID
Maximum Length: 6
Data Base Record: C2100 SAMPLE-DATA
Data Base. Family: 14
Data Category: 60
Data Type: DATE
Picture: MMDDYY
NO
Registration Requirement: 2
Grant Requirement
Access: NON-KEY
Code Table ID:
N/A
Edit Criteria
Must be specified when:
• Inserting a sampling record
• Inserting a sample record for Lead (i.e.. C2107. SAMPLE-CONTAMINANT of 'PB901) [E7S]
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1 • 2j
. day, in position 3 • 4; and
. year, in position 5-6
• must be after December 31.1991 (12/31/91) [EHW]
• the sample begin date (C2103. SAMPLE-BEGIN-DATE) must be before the sample end date (C2105. SAMPLE-END-DATE) [E8KJ
• the sample begin date (C2103. SAMPLE-BEGIN-DATE) must be at least six months before the sample end date (C2105.
SAMPLE-END-DATE), when the sample contaminant (C2107. SAMPLE-CONTAMINANT) is 'PB90' [E8L]
e .Comments
Data element C2103. SAMPLE-BEGIN-DATE. identifies the beginning of the monitoring period.
SAMPLE-END-DATE must be valued for a new SAMPLE-DATA data base record to be inserted Into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number: 2.00
Page: II -181
-------
FRDS-II Data Element Description
Name: SAMPLE-CONTAMINANT
Number
• Description
A code value that represents an Identification number representing a lead 90th percentile sample.
• Source
FRDS-II Data Transfer File
Form ID: .HI
Data Qualifiers: PWS-ID
SAMPLE-ID
Maximum Length: 4
• Data Characteristics
Data Base Record: C2100 SAMPLE-DATA
Data Base Family: J4
Data Category: JO
Data Type: CHARACTER
Picture: XM1
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
KEY
2107
• Edit Criteria
Must be specified when:
• inserting a sampling record
• modifying the current value
Must only be submitted for Lead samples [EIU]
When specified:
• must be one of the Sample Contaminant Identification Codes (see Section VI; Table 2107): 'PB901 - Lead 90th Percentile Value
• Comments
Other contaminant Identification numbers are maintained in the following data elements:
• C1103 VIO-CONTAMINANT
• C1291 ENF-UNK-CONTAM1NANT
• C1357 NCP-CONTAMINANT
• C3003 VE-CONTAMINANT
SAMPLE-CONTAMINANT must be valued for a new SAMPLE-DATA data base record to be Inserted into the FRDS-II Data Base.
Effective Date: 1/31/93
Release Number. 2.00
Page:
-------
FRDS-II Data Element Description
Number C2111
Name: SAMPLE-ANALYSIS-RESULT
• Description
A numeric value that represents the result obtained from a samples' analysis.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _H1
Data Qualifiers: PWS-ID
SAMPLE-ID
Maximum Length: 15
Data Base Record: C2100 SAMPLE-DATA
Data Base Family: _14
Data Category: .41
Data Type: DECIMAL
Picture: 9(71.9(81
Registration Requirement: .2_^—_^^^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting a sampling record
• inserting a sample record for Lead (i.e.. C2107. SAMPLE-CONTAMINANT of 'PB901) [E7U]
• modifying the current value
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount Is Intended
must not be a negative number [EGA]
• Comments
SAMPLE-ANALYSIS-RESULT must be valued for a new SAMPLE-DATA data base record to be Inserted Into the FRDS-II Data Base.
Effective Date: 1/31/93
Release Number 2.00
Page: II-183
-------
FRDS-II Data Element Description
Name: SAMPLE-FY
Number C2117
• Description
A computed numeric value that represents the Federal fiscal year in which the sample was taken.
The term computed, as used here. Implies that this value is not reported by the State. SAMPLE-FY is determined automatically by the FRDS-II
computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM **•
Data Base Record: C2100
Data Base Family: 14
Data Category: .31
Data Type: INTEGER
Picture1 99
SAMPLE-DATA
Registration Requirement: •
Grant Requirement ' NO
Access: KEY
Code Table ID: N/A
• Acceptable Values
An integer number
The Federal fiscal year
• Comments
Other Federal fiscal year's are maintained in the following data elements:
• C1135 VIO-FY
• C1209 ENF-FY
• C3023 VE-FY
Effective Date. 1/31/93
Release Number: 200
Page: 11-184
-------
FRDS-II Data Base Record Description
Number C3000
Name: VARIANCE-EXEMFTION-DATA
• Description
A SYSTEM 2000 data base record identification
ime and number.
The C3000. VARIANCE-EXEMPTION-DATA, data base record contains data elements that characterize a variance, exemption, or other event
that Is applicable to a public water system.
The FRDS-II Data Base has one VARIANCE-EXEMPTION-DATA data base record tor each variance, exemption, or other event that has been
reported to EPA.
• Data Characteristics
Data Type: RECORD Data Base Family: 10
Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
C3001 VE-ID
C3003 VE-CONTAMINANT
C3005 VE-RECORD-TYPE
C3007 VE-EFFECTIVE-DATE
C3009 VE-EXPIRATION-DATE
C3011 VE-STATUS-CODE
C3013 VE-MOWYICL
C3015 VE-TREATMENT-PROCESS
C3017 VE-ALT-PROCESS
C3019 VE-REASON-CODE
C3021 VE-LAST-UPDATE
C3023 VE-FY
C3025 VE-DATA-ORIGIN
C3027 VE-VUL-FLAQ
C3029 VE-ALT-MON-FREQ
C3031 VE-SE-ID
C3033 VE-INSERT-DATE
• Comments
Each data element name contained within the VARIANCE-EXEMPTION-DATA data base record is prefaced with... VE-
Note that VARIANCE-EXEMPTION-DATA data base records will NOT be deleted If a Total Replace1 of Actto Is submitted and a previously
submitted variance, exemption, or other event data base record Is omitted.
Effective Date- 1/31/93
Release Number. 200
Page: 11-185
-------
FRDS-II Data Element Description
Number. C3001
Name: VE-ID
• Description
An alphanumeric value used to uniquely Identity a specific variance, exemption, or other event that Is applicable to a public water system.
It Is unique tor each public water system within the Federal fiscal year for which the variance, exemption or other event was reported.
VE-ID is of the form: yynnnnn (space Inserted for clarity only)
Where: yy • the Federal fiscal year in which the variance, exemption, or other event was granted or became effective.
nnnnn = an identification number assigned by the State or generated by the FRDS-II computer system (the first position consists
of the letter V if the ID was generated)
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
Ft
PWS-ID
VE-ID
2
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family: JO
Data Category: 24
Data Type: CHARACTER
Picture: X(7)
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• inserting, modifying or deleting a variance, exemption or other event record
• Inserting, modifying or deleting a variance, exemption or other event schedule record
When specified:
position 1 - 2 must be the Federal fiscal year of the variance, exemption or other event
position t - 2 must be greater than 77 and less than or equal to the current Federal fiscal year
position 1 - 2 must be greater than 88 and less than or equal to the current Federal fiscal year, for filtration requirement records (i.e..
C3005. VE-RECORD-TYPE of 'FR')
position 3 must be 'G' or V. or position 3 • 7 must be numeric
position 3 must not be "X* when inserting a variance, exemption or other event record
position 3 must not be "G" when modifying or deleting a variance, exemption or other event record
and position 3 is 'G1 or -X1:
. position 4 - 7 must be numeric
. position 4 - 7 must be greater than zero
• and position 1 is neither 'G' nor •X':
. position 1 - 7 must be numeric
. position 1 - 7 must be greater than zero
. the ID must exist in the FRDS-II data base tor the PWS. when modifying or deleting a variance, exemption or other event record.
or variance, exemption or other event schedule record
. the ID must not exist in the FRDS-II data base for the PWS. when Inserting a variance, exemption or other event record
. the ID must exist in the FRDS-II data base for the PWS or the variance, exemption or other event record, also, must be specified.
when inserting a variance, exemption or other event schedule record
• and position 1 is •X':
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a variance, exemption or other event record
Each new variance, exemption or other event record must include values for those data elements within the variance, exemption or other event
record (C3000. VARIANCE-EXEMPTION-DATA) that are identified as Registration Requirement data elements (see 'Data Characteristics1 on
this page) [ERR]
• Comments
•Other events' include turbidity waivers and filtration requirement events.
If desired, the user can have the FRDS-II computer system generate a VE-ID number by specifying a Group Generation Code (GGC) when
a new VARIANCE-EXEMPTION-DATA data base record is to be inserted into the dab base. This is accomplished by inserting the GGC in
positions 3 - 7 of the VE-ID.
VE-ID must be valued for a new VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date.
Release Number: 2.00
Page: II-186
-------
FRDS-II Data Element Description
Name: VE-CONTAM NANT
Number C3003
• Description
A code value that represents an identification number of a contaminant for which a variance, exemption, or other event applicable to a public
water system has been reported to EPA by State.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: Fl
Data Qualifiers: PWS-ID
VE-ID
Maximum Length: 4
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family: 10
Data Category: JO
Data Type: CHARACTER
Picture: XM)
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
NON-KEY
ID06
• Edit Criteria
Must be specified when:
• modifying the current value
Must not be specified when inserting or modifying a filtration requirement record (i.e., C3005. VE-RESORD-TYPE of "FR") [EXC]
When specified:
• must be one of the Contaminant Identification Codes (see Section VI; Table ID06)
• must not be a wild-card contaminant code (i.e.. a contaminant code containing an asterisk) unless the V&E modified MCL is specified
(i.e.. C3013. VE-MOD-MCL) [E9N]
• Comments
•Other events' include turbidity waivers and filtration requirement events.
Other contaminant identification numbers are maintained in the following data elements:
• C1103 VIO-CONTAMINANT
• C1291 ENF-LINK-CONTAMINANT
•• C1357 NCP-CONTAMINANT
• C2107 SAMPLE-CONTAMINANT
VE-CONTAMINANT must be valued for a new VARIANCE-EXEMPTION-DATA data base record to be Inserted Into the FRDS-II Data Base for
a variance, exemption, or turbidity waiver record. It must not be valued tor a filtration requirement event record.
Effective Date: 1/31/93
Release Number: 2.00
-------
FRDS-II Data Element Description
Name: VE-RECORD-TYPE
Number C300S
• Description
A code value that represents whether the VARIANCE-EXEMPTION-DATA data base record is a variance, exemption, or <
to a public water system.
nt applicable
• Source
• Data Characteristics
FRDS-II
Form ID:
Data Qualifiers:
Maximum Length
Data Transfer File
F1
PWS-ID
VE-ID
: 2
• Edit Criteria
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: X(2)
10
10
NO
Registration Requirement
Grant Requirement
Access:
Code Table ID: 3005
KEY
Must be specified when:
• Inserting a variance, exemption or other event record
• modifying the current value
When specified:
• must be one of the Variance/Exemption/Other Record Type Codes (see Section VI; Table 3005)...
•EX* • Exemption Record
•FR' - Filtration Requirement Record (SWTR)
TW - Turbidity Waiver Record
•VA' •• Variance Record
Additionally:
• the reason code (C3019, VE-REASON-CODE) must not be less than fKO1 or between -023' and >029>. inclusive, when inserting or
modifying a filtration requirement record (i.e.. C3005. VE-RECORD-TYPE of 'FR') [E8X]
• when inserting or modifying a filtration requirement record (i e.. C3005. VE-RECORD-TYPE of 'FR1) an effective date (C3007.
VE-EFFECTIVE-DATE) and reason code (C3019. VE-REASON-CODE) must also be provided [ERE]
• Comments
•Other events' include turbidity waivers and filtration requirement events.
VE-RECORD-TYPE must be valued for a new VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date- 1/31/93
Release Number. 200
Page: 11-188
-------
FRDS-II Data Element Description
Name: VE-EFFECTIVE-DATE
Number. C3007
• Description
A value that represents the calendar date on which a variance, exemption, or other event became, or will become, effective.
Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _Fl
Data Qualifiers: PWS-ID
VE-ID
Maximum Length:
Data Base Record: C3000
Data Base Family: JO
Data Category: 60
Data Type: DATE
Picture: MMDDYY
VARIANCE-EXEMPTION-DATA
Registration Requirement .4
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the record specifies a filtration requirement (j.e.. C3005. VE-RECORD-TYPE of 'FR1) [ERE]
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1-2;
. day. in position 3 • 4; and
. year. In position 5 - 6
• must be less than the V&E expiration date (C3009, VE-EXPIRATION-DATE) [E9V]
• must be greater than September 30. 1989, for filtration requirement records (i.e.. C3005. VE-RECORD-TYPE of W)
• Comments
•Other events' include turbidity waivers and filtration requirement events.
Data element C3009. VE-EXPI RATION-DATE, identifies the calendar date on which a variance, exemption, or other event expired, or wBI expire.
For a filtration requirement event, VE-EFFECTIVE-DATE must be valued for a new VARIANCE-EXEMPTION-DATA data base record to be
Inserted Into the FRDS-II Data Base.
For a variance, exemption, or turbidity waiver. VE-EFFECTIVE-DATE must be valued for a new VARIAN CE-EXEMPTION-DATA data base record
to be Inserted into the FRDS-II Data Base If an effective date has been established.
Effective Date V31/93
Release Number: 200
Page: 11-189
-------
rnus-ll Data Element Description
Name: VE-EXPIRATION-DATE
Number C3009
• Description
A value that represents the calendar date on which a variance, exemption, or other event expired, or will expire.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: .£]
Data Qualifiers: PWS-ID
VE-ID
Maximum Length: 6
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family: 10
Data Category: 60
Data Type: DATE
Picture: MMDDYY
Registration Requirement
Grant Requirement:
Code Table ID:
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month, in position 1 • 2;
. day, in position 3 • 4; and
. year, in position 5 - 6
• must be greater than the V&E effective date (C3007, VE-EFFECTIVE-DATE) [E9VJ
e Comments
•Other events' include turbidity waivers and filtration requirement events.
Data element C3007. VE-EFFECTIVE-DATE. identifies the calendar date on which a variance, exemption, or other event became effective,
or will become effective.
VE-EXPIRATION-DATE must be valued for a new VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-II Data Base
If an expiration date has been established.
Effective Date 1/31/93
Release Number:
Page: 11-1
-------
FRDS-II Data Element Description
Name: VE-STATUS-CODE
Number C3011
• Description
A code value that represents the current status of a variance, exemption, or other event applicable to a public water system.
Examples of VE-STATUS-CODE Include a status such as application received, hearing scheduled, compliance schedule prescribed, etc.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID: F1
Data Qualifiers: PWS-ID
VE-ID
Maximum Length:
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family: JO
Data Category: JO
Data Type: CHARACTER
Picture: XM)
NO
Registration Requirement:
Grant Requirement
Access: NON-KEY
Code Table ID: 3011
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be one of the Variance/Exemption/Other Status Codes (see Section VI; Table 3011):
•A'
•B-
•C-
•£•
•G§
T
•K-
•M'
•C"
•Q-
•R'
•S1
T
•u-
V
•W
•X-
•v
•z-
Interest Expressed (In Variance/Exemption/Other)
Completed. PWS in compliance (Variance/Exemption/Other)
Application Received .• (For Variance/Exemption/Other)
State Proposes to Deny (Variance/Exemption/Other Application)
State Proposes to Grant (Variance/Exemption/Other Application)
Hearing Scheduled on Proposal
Hearing Held on Proposal
Compliance Schedule Prescribed
Hearing Scheduled on Compliance Schedule
Hearing Held on Compliance Schedule
Additional Information Desired
Request Granted (For Variance/Exemption/Other)
Request Denied (For Variance/Exemption/Other)
State Sets Monitoring Requirements
EPA Sets Monitoring Requirements
Notification given to Public
Other
Notification given to EPA
Pending Deletion
• Comments
•Other events' include turbidity waivers and filtration requirement events.
VE-STATUS-CODE must be valued for a new
VARIANCE-EXEMPTION-DATA data base record to be Inserted Into the FRDS-II Data Base tor a variance, exemption, or turbidity waiver.
VE-STATUS-CODE does not need to be valued to Insert a new VARIANCE-EXEMPTION-DATA data base record tor a filtration requirement
event
Effective Date. 1/31/93
Release Number: 2.00
Page: II -191
-------
FRDS-II Data Element Description
Number C3013
Name: VE-MOD-MCL
• Description
A numeric value that represents a modified maximum contaminant level that has been approved as a condition to a variance or an exemption
granted to a public water system by the State.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _F1
Data Qualifiers: PWS-ID
VE-ID
Maximum Length: 15
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Family: 10
Data Category: .41
Data Type: DECIMAL
Picture: 9m.9(8)
Registration Requirement J
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
Must not be specified when inserting or modifying a filtration requirement record (i.e.. C3005. VE-RECORD-TYPE of 'FR1) [EXC]
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount is intended
must not be a negative number [EGA]
• Comments
•Other events' include turbidity waivers and filtration requirement events.
If a modified maximum contaminant level has been approved as a condition to variance or an exemption, this data element must be valued
for a new VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date: 1/31/93
Release Number: 200
Page: 11-192
-------
FRDS-II Data Element Description Number C301S
Name: VE-TREATMENT-PROCESS
• Description
A code value that represents a treatment process for which a variance or an exemption is being granted to a public water system by the State.
Examples of VE-TREATMENT-PROCESS include processes such as chlorination. filtration, fluoridation. pH adjustment
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _F1
Data Qualifiers: PWS-ID
VE-ID
Data Base Record: C3000 VARIANCE-EXEMPTION-DATA
Data Base Famitv: 10
Data Cateoorv: 10
DataTvoe: INTEGER
Picture: 9f3)
Registration Requtrem
Grant Requirement
Access:
Code Table ID:
ant -
NO
NON-KEY
ID04
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the V&E alternate process (C3017. VE-ALT-PROCESS). has been specified [E9W]
Must not be specified when inserting or modifying a filtration requirement record (I.e., C3005. VE-RECORD-TYPE of "FR") [EXC]
When specified:
• must be one of the Treatment Process Codes (see Section VI; Table ID04)
• Comments
•Other events* include turbidity waivers and filtration requirement events.
Other treatment process codes are maintained in the following data elements:
• C485 PWS-SE-TREATMENT-PROCESS
• C3017 VE-ALT-PROCESS
Effective Date 1/31/93
Release Number: 2.00
Page: 11-193
-------
Description
FRDS-ll Data Element Description
Name: VE-ALT-PROCESS
Number C3017
A code value that represents an alternate treatment process that has been approved as a condition to a variance or an exemption granted
to a public water system by the State.
Examples of VE-ALT-PROCESS Include processes such as chlorination. filtration, fluoridation. pH adjustment
Source
• Data Characteristics
FRDS-ll Data Transfer File
Form 10:
Data Qualifiers:
Maximum Length:
F1
PWS-ID
VE-ID
_3
Data Base Record: C3000
Data Base Family: 10
Data Category: 10
Data Type: INTEGER
Picture: 9(3)
VARIANCE-EXEMPTION-DATA
Registration Reauirement 4
Grant Requirement NO
Access: NON-KEY
Code Table ID: ID04
• Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the V&E treatment process (C3015. VE-TREATMENT-PROCESS). has been specified [E9W]
Must not be specified when inserting or modifying a filtration requirement record (i.e., C3005. VE-RECORD-TYPE of 'FR') [EXC]
When specified:
• must be one of the Treatment Process Codes (see Section VI; Table ID04)
• Comments
•Other events' include turbidity waivers and filtration requirement events.
Other treatment process codes are maintained in the following data elements:
• C485 PWS-SE-TREATMENT-PROCESS
• C3015 VE-TREATMENT-PROCESS
If a treatment process has been approved as a condition to variance or an exemption, this data element must be valued for a new
VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-ll Data Base.
Effective Date: t/31/93
Release Number 200
Page:
-------
FRDS-II Data Element Description
Name: VE-REASON-CODE
Number. C3019
Description
A code value that represents the reason for which a variance, exemption, or turbidity waiver was issued by the State, or a filtration requirement
event was triggered for a public water system.
Examples of VE-REASON-CODE include reasons such as cannot comply with regulations due to economic factors, cannot comply with
regulations despite application of the best available treatment, treatment is not necessary to protect the public health, filtration is required
due to the system's failure to meet the daily CT criteria.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _F1
Data Qualifiers: PWS-ID
VE-ID
Maximum Length- 3
Data Base Record: C3000
Data Base Family: 10
Data Category: 10
Data Tvoe: INTEGER
Picture: 9(3)
VARIANCE-EXEMPTION-DATA
Registration Reaulrement 4
Grant Requirement NO
Access: NON-KEY
Code Table ID: 3019
Edit Criteria
Must be specified when:
• modifying the current value
• not presently valued and the record specifies a filtration requirement (i.e.. C3005. VE-RECORD-TYPE of 'FR1) (ERE]
must be one of the Variance/Exemption/Other Reason Codes (see Section VI; Table 3019)
must not be less than "020* or between •023* and '0291, inclusive, when inserting or modifying a filtration requirement record (i.e..
C3005, VE-RECORD-TYPE of 'FR-) [E8W]
• Comments
•Other events' include turbidity waivers and filtration requirement events.
VE-REASON-CODE must be valued for a new
VARIANCE-EXEMPTION-DATA data base record to be Inserted into the FRDS-II Data Base for a filtration requirement event.
VE-REASON-CODE does not need to be valued to insert a new VARIANCE-EXEMPTION-DATA data base record tor a variance, exemption.
or turbidity waiver.
EWectveDate 1/31/93
Release Number. 2.00
Page: 11-195
-------
FRDS-II Data Element Description
Name: VE-LAST-UPDATE
Number C3021
Description
A computed value that represents the calendar date on which a variance, exemption, or other event was initially posted to the FRDS-II Data
Base or when a subsequent State-supplied modification was made.
The term computed, as used here, Implies that this date is not reported by the State. VE-LAST-UPDATE is determined automatically by the
FRDS-II computer system during its normal course of operation when a variance, exemption, or other event data base record to inserted Into
the FRDS-II Data Base or when It is subsequently modified.
Source
• Data Characteristics
FRDS-II Data Transfer File
••• GENERATED DATA ITEM •••
Data Base Record: C3000
Data Base Family: 10
Data Category: 60
Data Type: DATE
Picture: MMDDYY
VARIANCE-EXEMPTION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 - 2;
day. in position 3 - 4; and
year, in position 5-6
• Comments
This date is changed for State reported updates only (i.e., updates submitted via DTF transactions}.
Other last update dates are maintained in the following data elements:
• C7 ST-ANY-DATA-LAST-UPDATE •
• C9 ST-INV-LAST-UPDATE •
• C13 ST-VIO-LAST-UPDATE •
• C15 ST-ENF-LAST-UPDATE •
• C17 ST-VE-LAST-UPDATE •
C29 ST-SAMPLE-LAST4JPDATE
C167 PWS-INV-LAST-UPOATE
C169 PWS-ANY-DATA-LAST-UPDATE
C1133 VIO-LAST-UPDATE
C1207 ENF-LAST-UPDATE
Effective Date'
Release Number 200
Page.
I-196
-------
FRDS-II Data Element Description
Name: VE-FY
Number. C3023
• Description
A computed numeric value that represents the Federal fiscal year In which a variance, exemption, or other event was Initiated or granted.
The term computed, as used here, implies that this value is not reported by the State. VE-FY is determined automatically by the FRDS-II
computer system during its normal course of operation.
• Source
• Data Characteristics
FRDS-II Data Transfer File
•** GENERATED DATA ITEM •••
Data Base Record: C3000
Data Base Family: 10
Data Category: 31
Data Type: INTEGER
Picture: 9(2)
VARIANCE-EXEMPTION-DATA
Registration Requirement
Grant Requirement
Access:
Code Table ID:
NO
KEY
N/A
• Acceptable Values
An integer number
The Federal fiscal year in the range 80 to the current fiscal year (90 to present in filtration requirement records), inclusive
e Comments
•Other events' include turbidity waivers and filtration requirement events.
Other Federal fiscal year's are maintained in the following data elements:
•m C1135 VIO-FY
* • C1209 ENF-FY
• C2117 SAMPLE-FY
Effective Date: 1/31/93
Release Number: 2.00
Page: II -197
-------
FRDS-II Data Element Description
Name: VE-DATA-ORIGIN
Number. C3025
• Description
A code value that represents the source or origin of the various values lhat are maintained in the C3000. VARIANCE-EXEMPTION-DATA, data
base record.
Examples of VE-DATA-ORIGIN include sources or origins such as State reported, reported by an EPA region, generated by the FRDS-II
computer system during its normal course of operation, etc.
• Source
• Data Characteristics
FRDS-II Data Transfer File
GENERATED DATA ITEM •••
Data Base Record: C3000 VARIANCE-EXEMP
Data Base Family: 10 Registration Requirement
Data Category: • 10 Grant Requirement:
Data Type: CHARACTER Access:
Picture: X(1) Code Table ID:
.
NO
NON-KEY
ID07
• Acceptable Values
Entries from the Record Data Origin Codes (see Section VI; Table ID07):
•H' • Headquarters (EPA) supplied data (EPA Use Only)
•R' - Region (EPA) supplied data (EPA Use Only)
•S* • State supplied data
• Comments
This value is not Input directly by the State. Rather. It is conveyed to Production Control at the time the data is to be processed. Production
Control then communicates to FRDS-II the correct value to assign to this data element
Other data origins are maintained in the following data elements:
• C413 PWS-SE-DATA-ORIGIN
• C517 PWS-GA-DATA-ORIGIN
• CB09 PWS-MILESTONE-ORIGIN
This value cannot be modified.
C1137 VIO-DATA-ORIGIN
C1211 ENF-DATA-ORIGIN
Effective Date: 1/31/93
Release Number: 200
Page: 11-198
-------
FRDS-II Data Element Description
Number. C3027
Name: VE-VUL-FLAG
Description
A code value that Indicates whether a specific source/entity (Identified in data element C3031. VE-SE-ID) is vulnerable to the contaminant
specified in data element C3003. VE-CONTAMINANT.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: _F1
Data Qualifiers: PWS-ID
VE-ID
Maximum Length:
Data Base Record: C3000 VARIANCE-EXEMPT1ON-DATA
10
10
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: XMJ
Registration Requirement-
Grant Requirement
NO
Code Table ID:
NON-KEY
3027
• Edit Criteria
Must be specified when:
• modifying the current value
Must not be specified when inserting or modifying a filtration requirement record (i.e.. C300S. VE-RECORD-TYPE of "FR") [EXC]
When specrfied:
• must be one of the Variance/Exemption/Other Vulnerability Flag Codes (see Section VI; Table 3027):
•N- . PWS is NOT Vulnerable to Contaminant
•V - PWS is Vulnerable to Contaminant
• Comments
•Other events* include turbidity waivers and filtration requirement events.
Effective Date 1/31/93
Release Number: 2.00
Page: 11-199
-------
FRDS-II Data Element Description
Number
Name: VE-ALT-MON-FREQ
• Description
An alternate monitoring frequency for a given contaminant required to be monitored by the public water system. This represents an allowance
to monitor at a frequency differing from the prevailing frequency, and is reported in the permissable number of months between samples.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
VE-ID
3
Data Base Record: C3000
Data Base Family: 10
Data Cateaorv: 30
Data Type: INTEGER
Picture: 9(3)
VARIANCE-EXEMPTION-DATA
Registration Requirement:
Grant Requirement:
£***t»ff-
Code Table ID:
_
NO
NON-KEY
N/A
e Edit Criteria
Must be specified when:
• modifying the current value
Must not be specified when inserting or modifying a filtration requirement record (i.e., C3005. VE-RECORD-TYPE of 'FR1) [EXC]
When specified:
• must be an integer number
• Comments
•Other events' include turbidity waivers and filtration requirement events.
If an alternate monitoring frequency has been approved as a condition to variance or an exemption, this data element must be valued for
a new VARIANCE-EXEMPTION-DATA data base record to be inserted into the FRDS-II Data Base.
Effective Date. 1/31/93
Release Number: 200
Page: 11-200
-------
FRDS-II Data Element Description
Name: VE-SE-ID
Description
A numeric value used to uniquely Identify a specific source of water that is utilized by, or an entity (e.g.. an entry point, a treatment plant,
or other related facility) that Is related to. a public water system.
This data element offers the opportunity to designate a specific source/entity to which the variance, exemption, or other event applies.
• Source
FRDS-II Data Transfer File
Form ID: _F1
Data Qualifiers: PWS-ID
VE-ID
Maximum Length: _3
• Data Characteristics
Data Base Record: C3000
Data Base Family: 10
Data Category: 20
Data Type: INTEGER
Picture: 9(3)
VARIANCE-EXEMPTION-DATA
Registration Requirement _;
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an integer number
• must be less than or equal to 949 [EEH]
e Comments
Other source/entity IDs are maintained in the following data elements:
• C401 PWS-SE-ID
-. C1143 VIO-SE-ID
• C2119 SAMPLE-SE-ID
Effective Date. 1/
Release Number: 2.00
Page: II-201
-------
FRDS-II Data Element Description
Number C3033
Description
Name: VE-INSERT-DATE
A computed value that represents the calendar date on which a variance, exemption, or other event base record was Initially posted to the
FRDS-II Data Base.
The term computed, as used here, implies that this date is not reported by the State. VE-INSERT-DATE is dele
id automatically by the
FRDS-II computer system during its normal course of operation when a new variance, exemption, or other event data base record is initially
Inserted into the FRDS-II Data Base.
• Source
• Data Characteristics
FRDS-II Data Transfer File
' GENERATED DATA ITEM '
Data Base Record: C3000
Data Base Family: 10
Data Cateoory: 60
Data Tvc-e: DATE
Picture. MMDDYY
VARIANCE-EXEMPTION-DATA .
Registration Requirement
Grant Requirement
Access:
Code Table ID:
.
NO
NON-KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, in position 1 • 2;
day, in position 3 - 4; and
year, in position 5 - 6
• Comments
This date is valued for State reported data only (i.e.. data submitted via DTF transactions).
Other insert dates are maintained in the following data elements:
• C168 PWS-INSERT-DATE
• CB11 PWS-M1LESTONE-INSERT-DATE
C1M7 VJO-INSERT-DATE
C1213 ENF-INSERT-DATE
Effective Date 1/31/93
Release Number: 200
Page: 11-202
-------
FRDS-II Data Base Record Description
Name: VE-SCHEOULE
Number C3100
• Description
A SYSTEM 2000 data base record identification name and number.
The C3100. VE-SCHEDULE. data base record contains data elements that characterize a schedule ot specific actions that are related to a
variance, exemption, or other event that is applicable to a public water system.
The FRDS-II Data Base has one VE-SCHEDULE data base record for each specific action w
event that has been reported to EPA.
i it related to a variance, exemption, or other
• Data Characteristics
Data Type: RECORD Data Base Family: 10
Parent Record: C3000 VARIANCE-EXEMPTION-DATA
• Record Contents
This data base record contains the following data elements-
• C3101 VE-SCHED-ID
• C3103 VE-SCHED-ACTION
C3105 VE-SCHED-DATE
C3107 VE-SCHED-ACCOMP-DATE
e Comments
Each data element name contained within the VE-SCHEDULE data base record is prefaced whh: tfE-SCHED- Note that VE-SCHEDULE data
base records will NOT be deleted if a Total Replace1 of Actions is submitted and a previously submitted variance, exemption, or other event
schedule data base record is omitted.
Effective Date 1/31/93
Release Number: 2.00
Page:
-------
Description
FRDS-II Data Element Description
Name: VE-SCHEP-ID
Number C3101
A numeric value used to uniquely identify a specific action that is related to a variance, exemption, or other event applicable to a public water
system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: .£2
Data Qualifiers: PWS-ID
•VE-ID
VE-SCHEP-ID
Maximum length: .2
Data Base Record: C3100 VE-SCHEDULE
Data Base Family: 10 .
Data Category: 20 '
Data Type: INTEGER
Picture: 9(2)
Registration Requirement 3
Grant Requirement NO
Access: NON-KEY
Code Table ID:
N/A
Edit Criteria
Must be specified when:
• inserting, modifying or deleting variance, exemption or other event schedule record
When specified:
• position 1 must be 'G' or position 1 - 2 must be numeric
• position 1 must not be 'G' when modifying or deleting a variance, exemption or other event schedule record
• and position 1 is 'G':
. position 2 must be numeric
. position 2 must be greater than zero
. position 3 - 7 must be blank
• and position 1 is not 'G':
. position 1 - 2 must be numeric
. position 1-2 must be greater than zero
. position 3 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS, when modifying or deleting a variance, exemption or other event schedule
record
. the ID must not exist in the FRDS-II data base for the PWS. when inserting a variance, exemption or other event schedule record
• and position 1 is 'X':
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a variance, exemption or other event schedule
record
Each new variance, exemption or other event schedule record must include values for those data elements within the variance, exemption
or other event schedule record (C3100. VE-SCHEDULE) that are identified as Registration Requirement data elements (see 'Data
Characteristics' on this page) [ERR]
Additionally, a variance, exemption or other event record must be inserted when inserting a variance, exemption or other
record for a new Public Water System [E6Q]
it schedule
• Comments
•Other events' include turbidity waivers and filtration requirement events.
If desired, the user can have the FRDS-II computer system generate a VE-SCHED-ID number by specifying a Group Generation Code (GGC)
when a new variance, exemption, other event schedule data base record is to be inserted into the data base. This is accomplished by
substituting the GGC for an actual ID (i.e. Gn. where ... the letter 'G' tells FRDS-II to generate the ID. and the If is an arbitrary number
assigned to all related C3100. VE-SCHEDULE. data elements so that their logical grouping will remain intact).
VE-SCHED-ID must be valued for a new VE-SCHEDULE data base record to be inserted into the FRDS-II Data Base.
Effective Date. 1/31/93
Release Number: 200
Page: 11-204^
-------
FRDS-II Data Element Description Number C3103
Name: VE-SCHED-ACT1ON
• Description
A code value that represents a specific action that is to be taken by the State or the public water system (or was taken by the State or the
public water system) relating to a variance, exemption, or other event applicable to a public water system.
Examples of VE-SCHED-ACTION include actions such as explore alternate sources of water, explore regional system development, obtain
financial aid. design treatment system, etc.
• Source • Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers: PWS-ID
VE-ID
VE-SCHED-ID
Maximum Length: _2
Data Base Record: C3100 VE-SCHEDULE
Data Base Family: JO Registration Requirement
Data Category: JO Grant Requirement NO
Data Type: CHARACTER Access: NON-KEY
Picture: XB1 Code Table ID: 3103
• Edit Criteria
Must be specified when:
• modifying the current value
Should be specified when:
• not presently valued and the variance, exemption or requirement schedule date (i.e.. C3105, VE-SCHED-DATE) has been specified
• not presently valued and the variance, exemption or requirement schedule accomplished data (i.e., C3107,
VE-SCHED-ACCOMP-DATE) has been specified
When specified:
• must be one of the Variance/Exemption/Other Schedule Action Codes (see Section VI; Table 3103)...
•0V - Letter to PWS from State
•04' - Administrative Hearing • PWS & State
•OT • Other State Administrative Procedure
•19- • Explore Alternate Sources of Water
•22' - Explore Regional System Development
•25' - Financial Aid Obtained
•28' • Treatment System Designed
•31* • Treatment System Approved
•34* • Treatment System Built
•37" • Periodic Monitoring Required
• Comments
•Other events' include turbidity waivers and filtration requirement events.
Data element C310S. VE-SCHED-DATE. identifies the calendar date on which a specific action Is scheduled (or was scheduled) to occur.
Data element. C3107. VE-SCHED-ACCOMP-DATE. Identifies the calendar date on which a specific action was accomplished, If completed.
Effective Date 1/31/93 Release Number: 200 Page: II-205
-------
FRDS-II Data Element Description
Name: VE-SCHED-DATE
Number: C3105
• Description
A value that represents the calendar date on which a specific action relating to a variance, exemption, or other event is scheduled (or was
scheduled) to occur.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: F2
Data Qualifiers: PWS-ID
VE-ID
VE-SCHED-ID
Maximum Length:
Data Base Record: C3100
Data Base Family: 10
Data Category: 60
Data Type: DATE
Picture: MMDDYY
VE-SCHEDULE
Registration Requirement •
Grant Requirement NO
Access: NON-KEY
Code Table ID:
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
Should be specified when not presently valued and the variance, exemption or requirement schedule action (C3103. VE-SCHED-ACTION)
has been specified
When specified:
• must be a six digit numeric calendar date, comprised ol:
. month, in position 1 • 2;
. day. in position 3 - 4; and
. year, in position 5 - 6
• Comments
•Other events' include turbidity waivers and filtration requirement events.
Data element C3103. VE-SCHED-ACTION. identifies a specific action that is scheduled (or was scheduled) to occur on this calendar date.
Data element, C3107. VE-SCHED-ACCOMP-DATE. identifies the calendar date on which a specific action was accomplished. H completed.
Effective Date 1/31/93
Release Number: 200
Page: 11-206
-------
FRDS-II Data Element Description Number. C3107
Name: ^E-SCHED-ACCOMP-DATE „
• Description
A value that represents the calendar date on which a specific action relating to a variance, exemption, or other event was accomplished, II
completed.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
VE-ID
VE-SCHED-ID
Data Base Record: C3100 VE-SCHEDULE
Data Base Family:
Data Category:
Data Type: DATE
Picture: MMDDYY
10
60
Registration Requirement: ^^^_^^^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of:
. month. In position 1 • 2;
. day, In position 3 • 4; and
. year, in position 5 • 6
• Comments
•Other events' Include turbidity waivers and filtration requirement events.
Data element C3103, VE-SCHED-ACTION. Identifies a specific action that Is scheduled (or was scheduled) to occur on this calendar date.
Data element C3105. VE-SCHED-DATE. Identifies the calendar date on which a specific action Is scheduled (or was scheduled) to occur.
Effective Date 1/31/93
Release Number: 200
Page: II-207
-------
FRDS-II Data Base Record Description Number C4000
Name: STATE-DISCRETIONARY-DATA
• Description
A SYSTEM 2000 data base record identification name and number.
The C4000. STATE-DISCRETIONARY-DATA, data base record contains data elements that characterize a specific set of values defined at
the discretion of the State.
The FRDS-II Data Base has one STATE-DISCRETIONARY-DATA data base record for each single set of State specific data values that has
been reported to EPA tor a public water system.
• Data Characteristics
Data Type: RECORD Data Base Family: J1 Parent Record: C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements:
• C4001 SDD-ID • C4007 SOD-QUANTITY
• C4003 SDD-NAME . C4009 SDD-DATE
• C4005 SDD-VALUE
• Comments
Each data element name contained within the STATE-DISCRETIONARY-DATA data base record is prefaced with ... SDD-
Note that STATE-DISCRETIONARY-DATA data base records will NOT be deleted If a Total Replace' of Inventory to submitted arid a previously
submitted State Discretionary Data data base record is omitted.
Effective Date: 1/31/93 Release Number. 2.00 Page. II-20B
-------
FRDS-II Data Element Description
Name: SDD-ID
Number C4001
• Description
A numeric value used to uniquely identify a specific State Discretionary Data data element applicable to a public water system.
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: G1
Data Qualifiers: PWS-1D
SDD-ID
Maximum Length: 3
Data Base Record: C4000
Data Base Family: J1
Data Category: 20
Data Type: INTEGER
Picture:
STATE-DISCRETIONARY-DATA
3
9(3)
Registration Requirement
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
e Edit Criteria
Must be specified when:
• Inserting, modifying or deleting a Stale discretionary data record
When specified.
• position 1 must be *G' or position 1 - 3 must be numeric
• position 1 must not be 'G* when modifying or deleting a State discretionary data record
• and position 1 is 'G':
. position 2 through 3 must be numeric
. position 2 through 3 must be greater than zero
. position 4 - 7 must be blank
• and position 1 is not 'G1:
. position 1 - 3 must be numeric
. position 4 - 7 must be blank
. the ID must exist in the FRDS-II data base for the PWS. when modifying or deleting a State discretionary data record
. the ID must not exist in the FRDS-II data base tor the PWS, when inserting a State discretionary data record
• Comments
If desired, the user can have the FRDS-II computer system generate a SDD-ID number by specifying a Group Generation Code (GGC) when
a new State Discretionary Data data base record is to be inserted Into the data base. This Is accormlished by substituting the GGC for an
actual ID (i.e. Gnn, where... the letter *G* tells FRDS-II to generate the ID. and the "nrf Is an arbitrary number assigned to all related C4000.
STATE-DISCRETIONARY-DATA, data elements so that their logical grouping will remain Intact).
SDD-ID must be valued for a new STATE-DISCRETIONARY-DATA data base record to be Inserted into the FRDS-II Data Base.
Effective Date 1/31/93
Release Number. 2.00
Page:
-------
FRDS-II Data Element Description
Name: SDD-NAME
Number: C4003
• Description
An alphanumeric value that names (i e.. Identities) a State Discretionary Data data element
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
PWS-ID
SDD-ID
40
e Edit Criteria
Data Base Record: C4000 STATE-DISCRETIONARY-DATA
Data Base Family: 1 1 Registration Reauirement:
Data Category: 01 Grant Reauirement:
Data Type: CHARACTER Access:
Picture: X(4) Code Table ID:
.
NO
KEY
N/A
Must be specified when-
• modifying the current value
When specified.
• must be an alphanumeric value
e Comments
None
Effective Date 1/31/93
Release Number. 2.00
Page: II - 210
-------
FRDS-II Data Element Description
Name: SDD-VALUE
Number C400S
• Description
An alphanumeric value that is associated with a State Discretionary Data data element
• Source
• Data Characteristics
FRDS-II Data Transfer File
Form ID: G1
Data Qualifiers: PWS-ID
SDD-ID
Maximum Length:
Data Base Record: C4000
Data Base Family: _11
Data Category: _01
Data Type: CHARACTER
Picture: XM)
STATE-DISCRETIONARY-DATA
Registration Requirement ^
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be an alphanumeric value
• Comments
The State Discretionary Data data element name that is related to a SDD-VALUE is maintained in data element C4003. SDD-NAME.
If an alphanumeric value is not associated with a State Discretionary Data data element, refer to C4007. SOD-QUANTITY and/or C4009.
SDD-DATE.
Effective Date 1/31/93
Release Number: 200
Page: II - 2111_
-------
FRDS-II Data Element Description
Name: SOD-QUANTITY
Number. C4007
• Description
A numeric value that is associated with a State Discretionary Data data element
• Source
• Data Characteristics
FRDS-tl Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
G1
PWS-ID
SDD-ID
15
Data Base Record: C4000
Data Base Family: ji
Data Category: _41
Data Type: DECIMAL
Picture: 9m.9(8)
STATE-DISCRETIONARY-DATA
Registration Requirement •
Grant Requirement: NO
Access: NON-KEY
Code Table ID: N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
must be a numeric real number
whole portion cannot exceed seven digits
decimal portion cannot exceed eight digits
a decimal point may or may not be included
a decimal point must be specified when a fractional amount is intended
must not be a negative number [EGA]
• Comments
The State Discretionary Data data element name that is related to an SDD-OUANTITY is maintained in data element C4003, SDD-NAME.
If a numeric value is not associated with a State Discretionary Data data element, refer to C4005, SDD-VALUE and/or C4009. SDD-DATE*
Eflective Date. 1/31/93
Release Number. 200
-------
FRDS-II Data Element Description
Name: SDD-DATE
Number C4009
• Description
A calendar date value that Is
iated with a State Discretionary Data data element.
• Source
e Data Characteristics
FRDS-II Data Transfer File
Form ID:
Data Qualifiers:
Maximum Length:
G1
PWS-ID
SDD-ID
J
Data Base Record: C4000
Data Base Family: .11
Data Category: 60
Data Type: DATE
Picture: MMDDYY
STATE-DISCRETIONARY-DATA
Regstrafon Requirement ^
Grant Requirement NO
Code Table ID:
NON-KEY
N/A
• Edit Criteria
Must be specified when:
• modifying the current value
When specified:
• must be a six digit numeric calendar date, comprised of.
. month, in position 1 - 2;
. day. In position 3 - 4; and
. year. In position 5 - 6
• Comments
The State Discretionary Data data element name that is related to SDD-DATE is maintained in data element C4003. SDD-NAME.
If e calendar date te not associated with a State Discretionary Data data element, refer to 04005. SDD-VALUE. and/or C4007. SOD-QUANTITY.
Eflective Date 1/31/93
Release Number: 2.00
Page:
-------
FRDS-II Data Base Record Description Number. C4050
Name: DBA-DATA
• Description
A SYSTEM 2000 data base record identification name and number.
The C4050. DBA-DATA, data base record contains data elements that characterize a specific set of values defined at the discretion of the
FRDS Data Base Administrator. Predominantly, the DBA data base record is used for storage of SNC Information.
The FRDS-II Data Base has one DBA-DATA data base record for each single set of DBA specific values that nave been determined for a public
water system.
• Data Characteristics
Data Type: RECORD Data Base Family: .12 Parent Record. C100 PWS-SUMMARY
• Record Contents
This data base record contains the following data elements'
• C4051 DBA-NAME • C4057 DBA-COMMENT
• C4053 DBA-VALUE • C4059 DBA-ID
• C4055 DBA-DATE • C4061 DBA-SNC-CRITERIA
• Comments
Each data element name contained within the DBA-DATA data base record Is prefaced with ... DBA-
Effective Date: 1/31/93 Release Number. 200 Page:
-------
FRDS-II Data Element Description
Name: DBA-NAME
Number: C4051
• Description
An alphanumeric value that names (i.e.. identifies) an associated set of a DBA data values
• Source
• Data Characteristics
FRDS-II Data Transfer File
DBA SUPPLIED •••
Data Base Record: C4050 DBA-DATA
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: X(151
12
01
Registration Requirement j
Grant Requirement NO
Access: KEY
Code Table ID: N/A
• Acceptable Values
An alphanumeric value
• Comments
The most prevalent usage of this data element is in identifying significant non-compilers (SNCs). The content of DBA-NAME varies with the
SNC definition In effect at a given time. The content of DBA-NAME for the most recent SNCs (FY91. quarter 3. to present) Is as follows:
TIER1 -SNC-yy-qq-CHEM-RAD-MCL
TIER1-SNC-yy-qq-TCR-COMB
TIERI-SNC-yy-qq-TURB-COMB
TlER1-SNC-yy-qq-CHEM-RAD-MON
TIER1-SNC-yy-qq-TCR-MAJOR
TIERI-SNC-yy-qq-TURB-MAJOR
TIERI-SNC-yy-qq-TCR-MCL
TIERI-SNC-yy-qq-TURB-MCL
TIERI-SNC-yy-qq-TCR-MJRPT
• Less significant SNCs have a T1ER2-* prefix in place of TIER1-* and the same suffixes as above.
Since FY91, quarter 4. preliminary Tier 1 SNCs have been Identified prior to the actual SNC determination. Preliminary SNCs have a 'PTIER1-'
prefix in place of TIERV and have the same suffixes as above. Tier 2 preliminary SNCs are not determined.
Older SNCs have slightly different names. To obtain a complete listing of all DBA-NAME values, enter the following command from the
SYSTEM 2000 Self-Contained Facility (i.e.. SCF or Natural Language):
TALLY/EACH/C4051:
Effective Date 1/31/93
Release Number
Page:
-------
FRDS-II Data Element Description
Name: DBA-VALUE
Number: C4053
• Description
An alphanumeric value that is associated with a DBA defined data element
• Source
• Data Characteristics
FRDS-il Data Transfer File
DBA SUPPLIED'
Data Base Record: C4050 DBA-DATA
Data Base Family: 12 Registration Reauirement
Data Cateoory: 01 Grant Reauirement
Data Type: CHARACTER Access:
Picture: X(4) Code Table ID:
—
NO
KEY
N/A
• Acceptable Values
An alphanumeric value
• Comments
The name of the DBA data that identifies DBA-VALUE is maintained in data element C4051. DBA-NAME.
Effective Date 1/31/93
Release Number.
Page: II - 216
-------
FRDS-II Data Element Description
Name: DBA-DATE
Number. C40SS
• Description
A calendar date value that Is associated with a DBA defined data element.
• Source
• Data Characteristics
FRDS-II Data Transfer File
DBA SUPPLIED'
Data Base Record: C4050
Data Base Family 12
Data Category: 60
Data Tvoe: DATE
Picture- - MMDDYY
DBA-DATA
Registration Requin
Grant Requirement
Access:
Code Table ID:
arrant -
NO
KEY
N/A
• Acceptable Values
A six digit numeric calendar date, comprised of:
month, In position 1 - 2;
day, In position 3 - 4; and
year, in position 5 • 6
• Comments
The name of the DBA data that Identifies DBA-DATE Is maintained In data element C4051. DBA-NAME.
Effective Date: JV31/93
Release Number. 2.00
Page: II - 217
-------
FRDS-II Data Element Description
Name: DBA-COMMENT
Number. C4057
• Description
An alphanumeric value that represents any description, characteristic, or attribute that the Data Base Administrator wants to record lor the
associated DBA data base record.
For DBA data base records used to record information about SNCs. DBA-COMMENT contains individual violation IDs (separated with a slash)
which contributed to the SNC determination. A maximum of 31 violation IDs may be stored in DBA-COMMENT.
• Source
• Data Characteristics
FRDS-II Data Transfer File
•*• DBA SUPPLIED *"
Data Base Record: C4050 DBA-DATA
Data Base Family: .12
Data Category: 01
Data Type: CHARACTER
Picture: XM)
Registration Requirement •
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An alphanumeric value
• Comments
A maximum of 12 violation IDs can be printed when using the FRDS/lnteractive QuickLook Report Generator and the FRDS43B report
Only one comment is allowed per DBA data base record.
Other comments are maintained in the following data elements:
• C813 PWS-MILESTONE-COMMENT
• C1215 ENF-COMMENT
Effective Date 1/31/93
Release Number: 2.00
Page: II • 21B
-------
FRDS-II Data Element Description
Name: DBA-ID
Number. C4059
• Description
A numeric value used to Identify a specific DBA-DATA data base record. This value Is utilized at the discretion of the Data Base Administrator:
• Source
e Data Characteristics
FRDS-II Data Transfer File
••• DBA SUPPLIED •••
Data Base Record: C4050
Data Base Family: 12
Data Category: JO
Data Type: INTEGER
Picture: 9(3)
DBA-DATA
Registration Requirement ^
Grant Requirement NO
Code Table ID:
NON-KEY
N/A
• Acceptable Values
An integer number
• Comments
DBA-ID is utilized at the discretion of the FRDS Data Base Administrator.
Eflectrve Date 1731/93
Release Number 200
-------
FRDS-II Data Element Description
Name: DBA-SNC-CRITERIA
Number C4061
• Description
An alphanumeric data element that contains a two character code describing, tor TCR SNC's. the specific monitoring frequency criteria upon
which the SNC was generated. The monitoring frequency is generated based upon the duration of the most recent violation qualifying a
public water system as a TCR SNC.
• Source
• Data Characteristics
FRDS-II Data Transfer File
DBA SUPPLIED'
Data Base Record: C4050 DBA-DATA
Data Base Family:
Data Category:
Data Type: CHARACTER
Picture: XM)
12
01
Registration Requirement •
Grant Requirement NO
Access: NON-KEY
Code Table ID: N/A
• Acceptable Values
An alphanumeric value
• Comments
None
Effective Date: 1/31/93
Release Number. 2.00
Page: 11-220
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section III
Quick Reference
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31, 1993
Section III Quick Reference
Section III contains information on all of the data base records and elements residing in the
FRDS-II Data'Base in quick reference, table format.
• III A. FRDS-II Structure Chart
• III B. Comprehensive Data Element Table (Component Number Sequence)
• III C. Name to Number Cross Reference
• III D. Data Element Requirements
* Registration Requirement
» Grant Requirement
Effective Date: 1/31/93 Release: 2.00 Page: III - 1
-------
Ill A. FRDS-II Structure Chart
r»
I
Federal Reporting Data System (FRDS-III
Structure Chart
December 1. 1992
LmlO
Unit
In* 2 I
H
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III B. FRDS-II Comprehensive Data Element Table
Element Winter and Name
Data- Print -Requirement- --Source-- Hist Tble
Key Type Lth. Dec. Cat. Mask Regist. Grant Form Other Kept ID
CO STATE -SUMMARY
C1 ST- REG ION -CODE
C3 ST- STATE -CODE
C4 ST-IND-RES-CODE
C5 ST-PRIMACY-FLAG
C7 ST-ANY-DATA-LAST-UPDATE
C9 ST- I NV- LAST -UPDATE
C13 ST-VIO-LAST-UPDATE
CIS ST-ENF-LAST-UPDATE
C17 ST-VE-LAST-UPDATE
C19 ST-RECON-FLAG
C29 ST-SAMPLE-LAST-UPDATE
••• RECORD •••
KEY INT
KEY CHAR
KEY CHAR
KEY CHAR
DATE
DATE
DATE
DATE
DATE
KEY CHAR
DATE
2
2
7
1
6
6
6
6
6
1
6
Level: 0 Family: ALL
10
10
10
10
60
60
60
60
60
10
60
99
99
56
99
20
20
20
20
20
99
20
DBA
DBA
DBA
DBA
GEN
GEN
GEN
GEN
GEN
GEN
GEN
0001
0003
ID01
0005
0019
C100 PUS-SUMMARY
C101 PUS-ID
C102 PUS-GRANT-ELIGIBLE
C103 PUS-STATUS
C105 PUS-TYPE
C107 PUS-ACTIVITY-FLAG
C109 PUS-HI STORY-FLAG
C111 PUS-SYSTEM-BEGIN-YYMM
C113 PUS-DEACT-YYMM
C115 PUS-POP-CATEGORY
C117 PUS-RETAIL-POP-SERVED
C119 PUS-PRIMARY-SOURCE
C121 PUS-PCT-SURFACE
C123 PUS-PCT-GROUND
C125 PUS-PCT-PUR-SURFACE
C127 PUS-PCT-PUR-GROUND
C129 PUS-TREATMENT-CLASS
C131 PUS-SYSTEM-NAME
C133 PUS-SYSTEM-ADDR-LINE-1
C135 PUS-SYSTEM-ADDR-L1NE-2
C137 PUS-SYSTEM-CITY
C139 PUS-SYSTEM-STATE
CH1 PUS-SYSTEM-ZIP
C143 PUS-PHONE
C145 PUS-METERS
C147 PUS-SERVICE-CONNECT IONS
CU9 PUS-AVG-DAILY-PROO
C151 PUS-TOT-DESIGN-CAPACITY
C153 PUS-TOT-EMERGENCY-PROD
C155 PUS-TOT-STORAGE-CAPACITY
C157 PUS-MAX-DAILY-PROO
C159 PUS-SEASON-BEGIN-NMDD
C161 PUS-SEASON-END-MMDD
C163 PUS-OUNER-TYPE
C165 PUS-REGULATING-ENTITY
C167 PUS-INV-LAST-UPDATE
C168 PUS-INSERT-DATE
C169 PUS-ANY-DATA-LAST-UPDATE
C171 PUS-RECON-FLAG
C173 PUS-FYNN-TRACKER
••* RECORD ••• Level: 1 Family: ALL Parent: CO
Hist
KEY CHAR
KEY CHAR
KEY CHAR
KEY CHAR
KEY CHAR
KEY CHAR
INT
INT
KEY CHAR
INT
KEY CHAR
INT
INT
INT
INT
KEY CHAR
CHAR
CHAR
CHAR
KEY CHAR
CHAR
KEY CHAR
CHAR
INT
KEY INT
INT
INT
INT
INT
INT
INT
INT
KEY CHAR
CHAR
KEY DATE
DATE
KEY DATE
KEY CHAR
CHAR
9
1
3
1
1
1
4
4
1
8
1
3
3
3
3
1
40
40
40
40
2
9
10
7
7
10
10
10
10
10
4
4
1
1
6
6
6
1
60
21
10
10
10
10
10
61
61
10
30
10
30
30
30
30
10
01
01
01
01
10
70
71
30
30
30
30
30
30
30
62
62
10
10
60
60
60
10
01
99
99
99
99
99
99
18
18
99
08
99
17
17
17
17
99
99
99
99
99
99
59
61
07
07
10
10
10
10
10
18
18
99
99
20
20
20
99
99
1 Grant
2 Grant
2 Grant
4
2 Grant
Grant
Grant
Grant
Grant
2 Grant
Cond
Cond
A2
A2
A2
A2
A2
A2
A2
A2
A2
A2
A1
A1
A1
A1
A1
A1
A1
A2
A2
A2
A2
A2
GEN 0102
GEN Hist 0103
0105
0107
GEN 0109
Hist
GEN Hist 0115
GEN Hist 0119
GEN Hist 0129
Hist
ID02
Hist
0163
0165
GEN
GEN
GEN
GEN 0171
GEN
Effective Date: 1/31/93
Release: 2.00
Page: III - 3
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III B. FRDS-II Comprehensive Data Element Table (continued)
Element Number and Name
Data Print -Requirement- --Source-- Hist Tble
Key Type Lth. Dec. Cat. Nask Regist. Grant Form Other Kept ID
0303
ID02
C300
C301
C303
C305
C307
C309
C311
C313
C31S
C400
C401
C403
C405
C407
C409
Mil
C413
C415
C417
C418
C419
C421
C423
C425
C426
C427
C429
C431
C480
C481
C483
C485
CSOO
C501
CS03
C505
CS07
CS08
C509
C511
CS13
C515
C517
C600
C601
C603
C605
PUS-ADDRESS-DATA
PUS-AD-ID
PUS-AD-TYPE
PUS-AD-NAME
PUS-AD-ADDR-LINE-1
PUS-AD-ADDR-LINE-2
PUS-AD-CITY
PUS-AD-STATE
PUS-AD-ZIP
PUS-SOURCE-ENTITY-INFO
PUS-SE-ID
PUS -SE- NAME
PUS -SE- RECORD -TYPE
PUS -SE- CODE
PUS-SE-AVAILABILITY
PUS-SE-SELLER-PUS-ID
PUS-SE-DATA-ORIGIN
PUS-SE-LATITUDE
PUS-SE-LONGITUDE
PUS-SE-HERIDIAN-NAME
PUS-SE-TOUNSHIP
PUS -SE- RANGE
PUS -SE- SECT ION
PUS-SE-QTR-SECTION
PUS-SE-OTR-QTR-SECTION
PUS-SE-RIVER-REACH-NUH
PUS-SE-ON-REACH
PUS-SE-REACH-MILES
PUS- SE - TREATMENT -DATA
PUS-SE-TREATHENT-ID
PUS-SE-TREATMENT-OBJECTIVE
PUS-SE-TREATHENT-PROCESS
PUS-GEOGRAPHIC-AREAS-SERVED
PUS-GA-ID
PUS-GA-ADMIN-REGION
PUS-GA-ADMIN-DIST
PUS-GA-CONGRESSIONAL-DIST
PUS-GA-STATE-COUNTY-CODE
PUS-GA-F1PS-COUNTY-CODE
PUS-GA-MSA-CODE
PUS-GA-C I TY- SERVED
PUS-GA-IND-RES-CODE
PUS-GA-DATA-ORIGIN
PUS-SERVICE-AREAS
PUS-SERV-1D
PUS-SERV-CATEGORY
PUS-SERV-PRIMARY-FLAG
***
KEY
KEY
KEY
RECORD
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
*••
1
1
40
40
40
40
2
9
*•• RECORD •••
KEY
KEY
KEY
KEY
KEY
•**
KEY
KEY
••*
KEY
KEY
KEY
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
INT
INT
CHAR
CHAR
CHAR
INT
CHAR
CHAR
CHAR
CHAR
DEC
3
40
1
1
1
9
1
6
7
40
4
4
2
2
2
11
1
6
RECORD *••
INT
CHAR
INT
2
1
3
RECORD •*•
INT
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
CHAR
2
2
2
2
3
3
4
40
5
1
*•• RECORD •••
KEY
KEY
INT
CHAR
CHAR
2
2
1
Level:
20
10
01
01
01
01
10
70
Level:
20
01
10
10
10
21
10
72
73
01
74
75
76
10
10
10
10
2 41
Level:
20
10
10
Level:
20
02
02
10
15
10
10
01
10
10
Level:
20
10
10
2 Family:
1
99 3
99
99
99
99
99
99
59
2 Family:
99
99
99
99
99
99
99
21
22
99
52
53
19
55
55
62
99
13
3 Fami.y:
99
99
99
2
1
1
2
4
4
4
4
4
4
4
: 2
3
3
3
2 Family: 3
99
99
99
51
54
54
99
99
56
99
3
2 Family: 4
99
99
99
3
3
4
Parent: C100
A3
A3
A3
A3
A3
A3
A3
A3
Parent: C100
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
B1
GEN
Parent: C400
B2
B2
B2
Parent: C100
C1
C1
C1
C1
C1
C1
C1
C1
GEN
GEN
Parent: C100
C2
C2
C2
0405
ID10
0409
0003
ID07
ID11
ID11
0427
0429
ID05
ID03
0507
0508
0509
0511
ID01
ID07
0603
0605
Effective Date: 1/31/93
Release: 2.00
Page: III - 4
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III B. FRDS-II Comprehensive Data Element Table (continued)
Element Number and Name
Data Print -Requirement- --Source-- Hist Tble
Key Type Lth. Dec. Cat. Mask Regist. Grant Form Other Kept ID
0705
0805
ID07
C700
C701
C703
C705
C800
C801
C803
C805
C809
C811
C813
C815
C900
C901
C903
C905
C907
PWS-ON-SITE-VISITS
PUS-VISIT-ID
PWS-VISIT-OATE
PWS- VISIT-REASON
PUS-MI LESTONES-EVENTS
PUS-MILESTONE-ID
PUS-NILESTONE-DATE
PUS-MILESTONE-CODE
PUS-MILESTONE-ORIGIN
PUS-MILESTONE-INSERT-DATE
PUS-MILESTONE-COMMENT
PUS-MILESTONE-VALUE
PUS-HISTORY
PUS • H I ST - CHANGED - 1 TEM
PUS-HIST-CHANGE-DATE
PUS-HIST-OLD-VALUE
PUS- HIST -NEW- VALUE
•«* RECORD •*•
INT
DATE
KEY CHAR
2
6
2
*** RECORD **•
CHAR
DATE
KEY CHAR
CHAR
DATE
CHAR
DEC
4
6
4
1
6
40
15
••• RECORD •**
KEY CHAR
DATE
CHAR
CHAR
4 .
6
40
40
Level :
20
60
10
Level :
25
60
10
10
60
01
8 41
Level :
02
60
01
01
2 Fami ly: 5
99 3
20
99
2 Family: 13
99 3
20 2
99 2
99
20
99
14 4
2 Family: 6
99
20
99
99
Parent: C100
C3
C3
C3
Parent: C100
C4
C4
C4
GEN
GEN
C4
C4
Parent: C100
GEN
GEN
GEN
GEN
C1000 NON-COMPLIANCE-DATA
C1001 NCD-RECON-FLAG
C1100 VIOLATION-DATA
C1101 VIO-ID
C1103 VIO-CONTAMINANT
C1105 VIO-TYPE
C1107 VIO-COMP-PERIOD-BEGIN-DATE
C1109 VIO-COMP-PERIOD-END-DATE
C1111 VIO-COMP-PERIOD-MONTHS
C1115 VIO-AUARE-DATE
C1117 VIO-INSERT-DATE
C1121 VIO-ANALYSIS-METHX
C1123 VIO-ANALYSIS-RESULT
C112S VIO-MCL-VIOLATED
C1127 VIO-SAMPLES-REOUIRED
C1129 VIO-SAMPLES-TAKEN
C1131 VIO-MAJOR-VIOLATION-FLAG
C1133 VIO-LAST-UPDATE
C1135 VIO-FY
C1137 VIO-DATA-ORIGIN
C1143 VIO-SE-1D
C1180 VIO-ENFORCEMENTS
C1181 VIO-LINK-ENF-ID
C1183 VIO-LINK-ENF-DATE
C1185 VIO-LINK-FOLLOU-UP-ACTION
••• RECORD •** Level: 2 Family: 7/9 Parent: C100
KEY CHAR 1 10 99 GEN
•** RECORD •** Level: 3 Family: 7 Parent: C1000
CHAR
KEY CHAR
KEY CHAR
KEY DATE
KEY DATE
INT
KEY DATE
KEY DATE
CHAR
DEC
DEC
INT
INT
KEY CHAR
KEY DATE
KEY INT
CHAR
INT
•** RECORD
CHAR
DATE
KEY CHAR
7
4
2
6
6
3
6
6
3
15
15
3
3
1
6
2
1
3
*•*
7
6
3
22
10
10
60
60
30
60
60
10
8 41
8 41
30
30
10
60
31
10
31
Level: 4
23
60
10
56
99
99
20
20
03
20
20
99
14
14
03
03
99
20
99
99
99
Family
56
20
99
3
4
2
2
4
4
4
4
4
4
4
: 7
D1
D1
D1
01
D1
D1
D1
D1
D1
D1
D1
D1
01
D1
Parent :
GEN
GEN
GEN
GEN
C1100
GEN
GEN
GEN
1001
ID06
I DOS
1121
1131
ID07
ID09
Effective Date: 1/31/93
Release: 2.00
Page: III - 5
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III B. FRDS-II Comprehensive Data Element Table (continued)
Element Number and Name
Data Print -Requirement- --Source-- Hist Tble
Key Type Lth. Dec. Cat. Mask Regist. Grant Form Other Kept ID
C1200
C1201
C1203
C1205
C1207
C1209
C1211
C1213
C1215
C1280
C1281
C1283
C1285
C1287
C1289
C1291
C1293
C1300
C13SO
C1351
C1353
C13S5
C1357
C13S9
C1361
C1363
C1365
C1367
ENFORCEMENT-DATA
ENF-ID
ENF-ACTION-DATE
ENF-FOLLOW-UP-ACTION
ENF-LAST-UPDATE
ENF-FY
ENF-DATA-ORIGIN
ENF- INSERT-DATE
ENF-COMHENT
ENF-VIOLATIONS
ENF-LINK-VIO-ID
ENF-LINK-RANGE-BEGIN
ENF-LINK-RANGE-END
ENF-LINK-PERIOO-BEGIN
ENF-LINK-VIO-TYPE
ENF-LINK-CONTAMINANT
ENF-LINK-TYPE
NCP-CNTL-NOOE
NON-COMPLIANCE-PROFILE
NCP-WINDOU-BEGIN-YYMM
NCP-UINDOU-MONTHS
NCP- WINDOW-PURPOSE
NCP-CONTAMINANT
NCP-MCL- VIOLATIONS
NCP-MCL -DURATION
NCP-MON-VIOLATIONS
NCP-MON-DURATION
NCP-ENF-ACTIONS
•**
.KEY
KEY
KEY
KEY
KEY
RECORD
CHAR
DATE
CHAR
DATE
INT
CHAR
DATE
*••
7
6
3
6
2
1
6
CHAR 40
***
KEY
***
***
KEY
KEY
RECORD
CHAR
DATE
DATE
DATE
CHAR
CHAR
CHAR
RECORD
RECORD
INT
INT
CHAR
CHAR
INT
INT
INT
INT
INT
•**
7
6
6
6
2
4
1
•**
•••
4
3
40
4
3
3
3
3
3
Level: 3
23
60
10
60
31
10
60
01
Level: 4
22
60
60
60
10
10
10
Level: 3
Level: 4
61
30
01
10
30
30
30
30
30
Fami ly: 3
56 3
20 2
99 2
20
99
99
20
99
Family: B
56
20
20
20
99
99
99
Family: 9
Family: 9
18
03
99
99
03
03
03
03
03
Parent:
El
E1
El
El
Parent :
El
E1
E1
E1
El
El
El
Parent:
Parent:
C1000
GEN
GEN
GEN
GEN
C1200
C1000
C1300
GEN
DBA
DBA
DBA
GEN
GEN
GEN
GEN
GEN
ID09
ID07
ID08
ID06
1293
ID06
C2000 SAMPLE-DATA-CNTL-NODE
*** RECORD *** Level: 2 Family: 14 Parent: C100
C2100 SAMPLE-DATA
C2101 SAMPLE-ID
C2103 SAMPLE-BEGIN-DATE
C2105 SAMPLE-END-DATE
C2107 SAMPLE-CONTAMINANT
C2111 SAMPLE-ANALYSIS-RESULT
C2117 SAMPLE-FY
C3000 VARIANCE-EXEMPTION-DATA
C3001 VE-ID
C3003 VE-CONTAMINANT
C3005 VE-RECORD-TYPE
C3007 VE-EFFECTIVE-DATE
C3009 VE-EXP1RATION-DATE
C3011 VE-STATUS-CODE
C3013 VE-MOO-MCL
•** RECORD *** Level: 3 Family: 14 Parent: C2000
CHAR
DATE
DATE
KEY CHAR
DEC
KEY INT
"** RECORD
CHAR
CHAR
KEY CHAR
DATE
DATE
CHAR
DEC
5
6
6
4
15
2
«•*
7
4
2
6
6
1
15
26
60
60
10
8 41
31
Level:
24
10
10
60
60
10
8 41
99
20
20
99
14
02
2 Family:
'56
99
99
20
20
99
14
3
2
2
2
2
10
3
4
2
4
4
4
4
H1
H1
HI
HI
HI
Parent:
F1
F1
F1
F1
F1
F1
F1
GEN
C100
2107
ID06
3005
3011
Effective Date: 1/31/93
Release: 2.00
Page: III - 6
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III B. FRDS-II Comprehensive Data Element Table (continued)
Element Number and Name
Data Print -Requirement- --Source-- Hist Tble
Key Type Lth. Dec. Cat. Nask Reg1st. Grant Form Other Kept ID
C3015 VE-TREATHENT-PROCESS
C3017 VE-ALT-PROCESS
C3019 VE- REASON -CODE
C3021 VE-LAST-UPDATE
C3023 VE-FY
C3025 VE-DATA-ORIGIN
C3027 VE-VUL-FLAG
C3029 VE-ALT-MON-FREO
C3031 VE-5E-ID
C3033 VE- INSERT-DATE
C3100 VE- SCHEDULE
C3101 VE-SCHED-1D
C3103 VE-SCHED-ACTION
C3105 VE-SCHED-DATE
C3107 VE-SCHED-ACCOMP-DATE
C4000 STATE-DISCRETIONARY-DATA
C4001 SDD-ID
C4003 SOD -NAME
C4005 SOD -VALUE
C4007 SDD-QUANTITY
C4009 SDD-DATE
C4050 DBA-DATA
C4051 DBA-NAME
C4053 DBA -VALUE
C4055 DBA-DATE
C40S7 DBA-COMMENT
C40S9 DBA- ID
C4061 DBA-SNC-CRITERIA
INT 3
INT 3
INT 3
KEY DATE 6
KEY INT 2
CHAR 1
CHAR 1
INT 3
INT 3
DATE 6
*•• RECORD •••
INT 2
CHAR 2
DATE 6
DATE 6
•*• RECORD •••
INT 3
KEY CHAR 40
CHAR 40
DEC 15
DATE 6
•** RECORD •**
KEY CHAR 40
KEY CHAR 40
KEY DATE 6
CHAR 99
INT 3
CHAR 40
10
10
10
60
31
10
10
30
20
60
Level :
20
10
60
60
Level:
20
01
01
8 41
60
Level:
01
01
60
01
20
01
99
99 4
99 4
20
99
99
99
03
99
20
3 Family: 10
99 3
99
20
20
2 Family: 11
99 3
99
99
14
20
2 Family: 12
99
99
-20
99
99
99
F1
F1
F1
GEN
GEN
GEN
F1
F1
F1
GEN
Parent: C3000
F2
F2
F2
F2
Parent: C100
G1
G1
G1
G1
G1
Parent: C100
DBA
DBA
DBA
DBA
DBA
DBA
ID04
ID04
3019
ID07
3027
3103
Effective Date: 1/31/93
Release: 2.00
Page: III - 7
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III C. Name to Number Cross Reference
Element Umber and Mane
Element matter and Name
C4057 DBA-COMMENT
C4050 DBA-DATA
C4055 DBA-DATE
C4059 DBA-ID
C4051 DBA-NAME
C4061 DBA-SNC-CRITERIA
C4053 DBA-VALUE
C1203 ENF-ACTION-DATE
C1215 ENF-COMMENT
C1211 ENF-DATA-OR1GIN
C120S ENF-FOLLOU-UP-ACTION
C1209 ENF-FY
C1201 ENF-1D
C1213 ENF-INSERT-DATE
C1207 ENF-LAST-UPDATE
C1291 ENF-LINK-CONTAMINANT
C1287 ENF-LINK-PERIOO-BEG1N
C1283 ENF-LINK-RANGE-BEG1N
C128S ENF-L1NK-RANGE-ENO
C1293 ENF-LINK-TYPE
C1281 ENF-LINK-VIO-1D
C1289 ENF-UNK-VIO-TYPE
C1280 ENF-VIOLATIONS
C1200 ENFORCEMENT-DATA
C1001 NCD-RECON-FLAG
C1300 HCP-CNTL-NODE
C1357 NCP-CONTAM1NANT
C1367 NCP-ENF-ACTIONS
C1361 NCP-MCL-DURAT10N
C1359 NCP-MCL-V10LAT10NS
C1365 NCP-MON-DURATIOtt
C1363 NCP-MON-VIOLATIONS
C1351 NCP-UINDOU-BEG1N-YYMM
C13S3 NCP-UINDOW-NONTHS
C13S5 NCP-UINDOU-PURPOSE
C1000 NON-COMPLIANCE-DATA
C1350 NON-COMPLIANCE-PROFILE
C107 PUS-ACTIVITY-FLAG
C307 PWS-AD-ADDR-LINE-1
C309 PUS-AD-ADDR-LINE-2
C311 PWS-AD-CITY
C301 PWS-AO-ID
C305 PUS-AD-NAME
C313 PUS-AD-STATE
C303 PUS-AD-TYPE
C31S PUS-AD-ZIP
C300 PUS-ADDRESS-DATA
C169 PUS-ANY-OATA-LAST-UPDATE
CU9 PUS-AVG-DAILY-PROD
C113 PUS-DEACT-YYMM
C173 PWS-FYNN-TRACKER
C505 PWS-GA-ADMIN-DIST
C503 PUS-GA-ADHIN-REGION
C513 PUS-GA-CITY-SERVED
C507 PUS-GA-CONGRESSIONAL-DIST
C517 PUS-GA-DATA-OR1GIN
C509 PUS-GA-FI PS-COUNTY-CODE
C501 PUS-GA-ID
CS15 PUS-GA-IND-RES-CODE
C511 PUS-GA-MSA-COOE
CS08 PUS-GA-STATE-COUNTY-COOE
CSOO PUS-GEOGRAPHIC-AREAS-SERVED.
C102 PUS-GRANT-ELIGIBLE
C903 PUS-HIST-CHANGE-DATE
C901 PUS-HIST-CHANGED-ITEM
C907 PUS-HIST-NEU-VALUE
C905 PUS-H1ST-OLD-VALUE
C900 PUS-HISTORY
C109 PUS-HISTORY-FLAG
C101 PWS-ID
C168 PUS-INSERT-DATE
C167 PUS-INV-LAST-UPDATE
C157 PUS-MAX-DAILY-PROD
C145 PUS-METERS
C80S PUS-MILESTONE-CODE
C813 PUS-MILESTONE-COMMENT
C803 PUS-MILESTONE-DATE
C801 PUS-MILESTONE-ID
C811 PUS-MILESTONE-INSERT-DATE
C809 PUS-MILESTONE-ORIGIN
C815 PUS-MILESTONE-VALUE
CSOO PUS-MILESTONES-EVENTS
C700 PUS-ON-SITE-VISITS
C163 PUS-OUNER-TYPE
C123 PUS-PCT-GROUND
C127 PUS-PCT-PUR-GROUND
C12S PUS-PCT-PUR-SURFACE
C121 PUS-PCT-SURFACE
C143 PUS-PHONE
C115 PUS-POP-CATEGORY
C119 PUS-PRIMARY-SOURCE
C171 PUS-RECON-FLAG
C165 PUS-REGULATING-ENTITY
C117 PUS-RETAIL-POP-SERVED
C409 PUS-SE-AVAILABILITY
C407 PUS-SE-CODE
C413 PUS-SE-DATA-ORIGIN
C401 PUS-SE-ID
C41S PUS-SE-LATITUDE
C417 PUS-SE-LONGITUDE
C418 PUS-SE-HERIDIAN-NAME
C403 PUS-SE-NAME
C429 PUS-SE-ON-REACH
£426 PUS-SE-OTR-QTR-SECTION
C425 PUS-SE-QTR-SECTION
:421 PUS-SE-RANGE
;431 PUS-SE-REACH-MILES
:405 PUS-SE-RECORD-TYPE
:427 PUS-SE-RIVER-REACH-NUM
=423 PUS-SE-SECTION
Mil PUS-SE-SELLER-PUS-IO
Ml 9 PUS-SE-TOUNSHIP
C480 PUS-SE-TREATMENT-DATA
C481 PUS-SE-TREATMENT-ID
C483 PUS-SE-TREATMENT-OBJECTIVE
C485 PUS-SE-TREATMENT-PROCESS
Effective Date: 1/31/93
Release: 2.00
Page: III - 8
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III C. Name to Number Cross Reference (continued)
Element Nunber and Name
Element Nuifcer and Name
C1S9 PWS-SEASON-BEGIN-NNDD
C161 PUS-SEASON-END-MMDD
C603 PUS-SERV-CATEGORY
C601 PUS-SERV-1D
C605 PUS-SERV-PR1MARV-FLAG
C600 PUS-SERVICE-AREAS
CU7 PUS-SERVICE-CONNECTIONS
C400 PUS-SOURCE-ENTITY-INFO
C103 PUS-STATUS
C100 PUS-SUMMARY
C133 PUS-SYSTEM-AODR-LINE-1
C135 PUS-SYSTEM-AODR-LINE-2
C111 PUS-SYSTEM-BEGIN-YYMM
C137 PUS-SYSTEM-CITY
C131 PUS-SYSTEM-NAME
C139 PUS-SYSTEM-STATE
CU1 PUS-SYSTEM-ZIP
C151 PUS-TOT-DESIGN-CAPACITY
C153 PUS-TOT-EMERGENCY-PROD
C155 PUS-TOT-STORAGE-CAPACITY
C129 PUS-TREATMENT-CLASS
C105 PUS-TYPE
C703 PUS-VISIT-DATE
C701 PUS-VISIT-ID
C705 PUS-VISIT-REASON
C2111 SAMPLE-ANALYSIS-RESULT
C2103 SAMPLE-BEGIN-DATE
C2107 SAMPLE-CONTAMINANT
C2100 SAMPLE-DATA
C2000 SAMPLE-DATA-CNTL-NODE
C2105 SAMPLE-END-DATE
C2117 SAMPLE-FY
C2101 SAMPLE-ID
C4009 SDD-DATE
C4001 SDD-ID
C4003 SDD-NAME
C4007 SOD-QUANTITY
C4005 SDD-VALUE
C7 .ST-ANY-DATA-LAST-UPDATE
CIS ST-ENF-LAST-UPDATE
C4 ST-INO-RES-CODE
C9 ST-INV-LAST-UPDATE
C5 ST-PRIHACY-FLAG
C19 ST-RECON-FLAG
C1 ST-REGION-CODE
C29 ST-SAMPLE-LAST-UPDATE
C3 ST-STATE-CODE
C17 ST-VE-LAST-UPDATE
C13 ST-VIO-LAST-UPDATE
C4000 STATE-DISCRETIONARY-DATA
CO STATE-SUMMARY
C3000 VARIANCE-EXEMPTION-DATA
C3029 VE-ALT-HON-FREO
C3017 VE-ALT-PROCESS
C3003 VE-CONTAMINANT
C3025 VE-DATA-ORIGIN
C3007 VE-EFFECTIVE-DATE
C3009 VE-EXPIRATION-DATE
C3023 VE-FY '
C3001 VE-ID
C3033 VE-INSERT-DATE
C3021 VE-LAST-UPDATE
C3013 VE-MOD-MCL
C3019 VE-REASON-CODE
C3005 VE-RECORD-TYPE
C3107 VE-SCHED-ACCOMP-DATE
C3103 VE-SCHEO-ACTION
C3105 VE-SCHED-DATE
C3101 VE-SCHED-ID
C3100 VE-SCHEDULE
C3031 VE-SE-ID
C3011 VE-STATUS-CODE
C3015 VE-TREATMENT-PROCESS
C3027 VE-VUL-FLAG
C1121 VIO-ANALYSIS-METHOD
C1123 VIO-ANALYSIS-RESULT
C111S VIO-AUARE-DATE
C1107 VIO-COHP-PERIOD-BEGIN-DATE
C1109 VIO-COMP-PERICO-END-DATE
C1111 VIO-COMP-PERIOD-MONTHS
C1103 VIO-CONTAMINANT
C1137 VIO-DATA-ORIGIN
C1180 V10-ENFORCEMENTS
C113S VIO-FY
C1101 VIO-ID
C1117 VIO-INSERT-DATE
C1133 VIO-LAST-UPDATE
C1183 VIO-LIMK-ENF-DATE
C1181 VIO-LINK-ENF-ID
C1185 VIO-LINK-FOLLOU-UP-ACTION
C1131 VIO-NAJOR-VIOLATION-FLAG
C1125 VIO-MCL-VIOLATED
C1127 VIO-SAMPLES-REOUIRED
C1129 VIO-SAMPLES-TAKEN
C1143 VIO-SE-ID
C110S VIO-TYPE
C1100 VIOLATION-DATA
Effective Date: 1/31/93
Release: 2.00
Page: III - 9
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III D. Data Element Requirements
Element
Number
Element Name
C101 PUS-ID
C105 PWS-TYPE
C107 PWS-ACTIVITY-FLAG
C113 PWS-DEACT-YYHM
C117 PUS-RETAIL-POP-SERVED
C131 PUS-SYSTEM-NAME
C137 PUS-SYSTEM-CITY
C139 PUS-SYSTEM-STATE
GUI PUS-SYSTEH-ZIP
CUT PUS-SERVICE-CONNECTIONS
C159 PUS-SEASON-BEGIN-HMDD
C16J PUS-SEASON-END-NHDO
C301 PUS-AD-ID
C401 PUS-SE-ID
C405 PUS-SE-RECORD-TYPE
C407 PWS-SE-COOE
C415 PUS-SE-LATITUDE
C417 PUS-SE-LONGITUDE
C418 PUS-SE-MERIDIAN-NANE
C419 PUS-SE-TOUNSHIP
C421 PUS-SE-RANGE
C423 PUS-SE-SECTION
C425 PUS-SE-QTR-SECTION
C481 PUS-SE-TREATMENT-ID
C483 PUS-SE-TREATHENT-OBJECTIVE
C485 PUS-SE-TREATHENT-PROCESS
C501 PUS-GA-ID
C601 PUS-SERV-ID
C603 PUS-SERV-CATEGORY
C605 PUS-SERV-PRIHARY-FLAG
C701 PUS-VISIT-ID
C80.1 PUS-MILESTONE-ID
C803 PUS-MILESTONE-DATE
C80S PWS-MILESTONE-CQOE
C815 PUS-MILESTONE-VALUE
C1101 VIO-ID
C1103 VIO-CONTAMINANT
C1105 VIO-TYPE
C1107 VIO-COMP-PERIOD-BEGIN-DATE
C1109 VIO-COMP-PERIOD-END-DATE
C1111 VIO-COMP-PERIOO-MONTHS
C111S VIO-AUARE-DATE
C1123 VIO-ANALYSIS-RESULT
C1125 VIO-HCL-VIOLATED
C1129 VIO-SANPLES-TAKEN
C1131 VIO-MAJOR-VIOLATION-FLAG
C1201 ENF-ID
C1203 ENF-ACTION-DATE
C120S ENF-FOLLOU-UP-ACTION
C2101 SAMPLE-ID
C2103 SAMPLE-BEGIN-DATE
C2105 SAMPLE-END-DATE
C2107 SAMPLE-CONTAMINANT
C2111 SAMPLE-ANALYSIS-RESULT
C3001 VE-ID
C3003 VE-CONTAMINANT
C3005 VE-RECORD-TYPE
Registration
Requirement
1
2
2
4
2
2
3
1
1
2
4
4
4
4
4
4
4
3
3
3
3
3
3
4
3
3
2
2
4
3
4
2
2
4
4
4
4
4
4
4
3
2
2
3
2
2
2
2
3
4
2
Grant
. Requirement
YES
YES
YES
YES
Y=S
YES
YES
YES
YES
COND
COND
Record
Number
C100
C100
C100
C100
C100
C100
C100
C100
C100
C100
C100
C100
C300
C400
C400
C400
C400
C400
C400
C400
C400
C400
C400
C480
C480
C480
C500
C600
C600
C600
C700
C800
C800
C800
C8DO
C1100
C1100
C1100
C1100
C1100
C1100
C1100
C1100
C1100
C1100
C1100
C1200
C1200
C1200
C2100
C2100
C2100
C2100
C2100
C3000
C3000
C3000
Effective Date: 1/31/93
Release: 2.00
Page: III - 1C
-------
FRDS-D DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
III D. Data Element Requirements (continued)
Element
Number
Element Name
Registration
Requirement
Grant
Requi
C3007 VE-EFFECT1VE-OATE
C3009 VT-EXPIRAUON-DATE
C3011 VE-STATUS-COOE
C3013 VE-HOO-HCL
C3017 VE-ALT-PROCESS
C3019 VE-REASON-COOE
C3101 VE-SCNED-ID
C4001 SOD-ID
4
4
4
4
4
4
3
3
Record
Nunber
C3000
C3000
C3000
C3000
C3000
C3000
C3100
C4000
Effective Date: 1/31/93
Release: 2.00
Page: HI- 11
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section IV
FRDS 1.5 Versus FRDS-II Comparison Tables
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Section IV FRDS 1.5 Versus FRDS-II Comparison Tables
Section IV contains information on the conversion of FRDS 1.5 to FRDS-II. Since this
'material remains unchanged from Release 1.00 of the FRDS-n Data Element Dictionary,
and is considered no longer relevant, it has not been included in Release 2.00. A section
cover sheet, however, has been provided for this section enabling the user to insert Section
IV, Release 1.00, in the new release document if so desired.
Effective Date: 1/31/93 Release: 2.00 Page: IV - 1
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section V
FRDS 1.5 To FRDS-II Conversion Rules
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Section V FRDS 1.5 To FRDS-II Conversion Rules
Section V contains information on the conversion of FRDS 1.5 to FRDS-II. Since this
material remains unchanged from Release 1.00 of the FRDS-n Data Element Dictionary,
and is considered no longer relevant, it has not been included in Release 2.00. A section
cover sheet, however, has been provided for this section enabling the user to insert Section
V, Release 1.00, in the new release document if so desired.
Effective Date: 1/31/93 Release: 2.00 Page: V - 1
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section VI
Lists Of Acceptable Code Values With Associated
Descriptions
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Section VI Lists of Acceptable Code Values with Associated
Descriptions
A. Introduction
Section VI contains comprehensive lists (i.e., tables) of acceptable code values along with
each code's description and other related comments, as appropriate, for each of the FRDS-II
data elements that have code values.
, In addition to this introduction, Section VI consists of an index to each of the code tables
utilized by FRDS-II (Section VI B.) with the individual code tables (Section VI C.)
immediately following. The Legend for the noted items in VI, B., is on page V - 9.
The index and the individual code tables are listed in code table ID sequence. Thus, table
IDs ID01 through ID11 appear first, followed by table IDs 0001 through 3103.
Except as designated below, the codes within individual tables are listed in sequence by
code value. The exceptions are as follows:
• The following code tables are listed by code value within USPS Postal State Code:
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village
Codes
Table 0507, FIPS PUB 9, Federal Congressional District Codes
Table 0508, State-specific County Codes
Table 0509, FIPS PUB 6-4, County Codes
• The following code table is listed by code value within Treatment Objective Code:
Table ID03, Combined Treatment Objective and Treatment Process Codes
• The following code tables are listed by code value within Contaminant Group Code:
Table ID06, Contaminant Identification Codes
Table 1121, Analysis Method Codes
• The following code table is listed by code value within Source/Entity Record Type
Code:
Table ID 10, Combined Source / Entity Record Type and Source / Entry Point /
Plant Type Codes
Effective Date: 1/31/93 Release: 2.00 Page: VI - 1
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-200:
January 31, 1993
• The following code table is listed by code value within U.S. Water Resources
Council Region:
Table 0427, FIPS PUB 103, Hydrologic Unit Codes
Table IDs which begin with the letters "ID" are known as "Common Tables." Common
tables are used when either of two circumstances exist:
• More than a single data element utilizes the same set of code values.
For example: Acceptable values for data elements C139,
PWS-SYSTEM-STATE, and C313, PWS-AD-STATE, are USPS
Postal State Codes. Rather than having two identical code tables
(one for C139 and one for C313), table ID02 was established.
• The code values for two different data elements are combined together. This is
necessary when there exists a set of valid combinations of two data elements' values.
For example: Table 0405 consists of valid codes for data element C40S,
PWS-SE-RECORD-TYPE, and table 0407 consists of valid codes
for data element C407, PWS-SE-CODE. However, only certain
C407 code values are valid for each C405 code value. Thus, table
ID 10 was established.
Table IDs that consist of 4 numeric digits are known as "Data Element Tables." The table
ID for a data element table is the same as the data element number for which the table is
established. For example: The code values for data element C3, ST-STATE-CODE, are
maintained in code table 0003. Please note that leading zeros have been added to the code
table ID to ensure that it is 4 numeric digits. Each of the following data element numbers
are synonymous when referring to ST-STATE-CODE: C3, C03, C003, and C0003.
The remainder of this introduction contains explanatory notes relative to the "Associated
Description" and/or "Comments" column(s) in Section VI., C., where further explanation is
appropriate. If the contents of the these columns are self-explanatory, no further details are
provided herein.
Effective Date: 1/31/93 Release: 2.00 Page: VI - 2
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Table ID01, FITS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
"County" The FIPS county code. See table 0509.
"Class" A descriptive categorization of the type of Indian reservation or Alaska
remote village.
• Dl identifies a Federally-administered reservation.
• D4 identifies a State-administered reservation that does not serve as a
minor civil division (MCD).
• DS identifies a State-administered reservation that is serving as an MCD
equivalent.
• D9 identifies an Indian Historic Reservation Area.
• El identifies an Alaska remote village not serving as a census designated
place (CDP) and not identically named and coincident with an
incorporated place.
• E2 identifies an Alaska remote village serving as a CDP.
• E6 identifies an Alaska remote village with the same name and coincident
with an incorporated place.
Table ID02, USPS Postal State Codes
"ZIP code Prefix" The 1st digit of the ZIP code.
Table ID06, Contaminant Identification Codes
"Regulated" The contaminant has a Federal MCL and Monitoring requirement
if the letter "R" appears in the comments column beneath
"Regulated."
"Monitoring Only" The contaminant has a Federal Monitoring requirement ONLY if
the letter "M" appears in the comments column beneath
"Monitoring Only."
Effective Date: 1/31/93 Release: 2.00 Page: VI - 3
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2001
January 31, 1993
Table 0003, FTPS PUB 5-2, Alphabetic State Codes and Selected EPA Region Codes
"CONUS" An acronym for the Contiguous United States. If the State is NOT in the
contiguous United States (lower 48 states), an "N" appears in the
comments column beneath "CONUS."
Table 0427, UPS PUB 103, Hydrologic Unit Codes
For each the Planning Subregion, Accounting Unit, and Cataloging Unit, the "Associated
Description" column shows the approximate square miles encompassed by the area.
For each U.S. Water Resources Council Region, Planning Subregion, Accounting Unit, and
Cataloging Unit, the "Comments" column identifies the State or States in which the area is
located.
For each the Planning Subregion, Accounting Unit, and Cataloging Unit, the "Comments"
column shows the minimum and maximum latitude and the minimum and maximum
longitude of the area in which the entity is located.
Table 0508, State-specific County Codes
"FIPS Code" The FIPS county code equivalent of the State-specific county code.
Table 0509, FTPS PUB 6-4, County Codes
For each county in the Contiguous United States, the "Comments" column shows the
minimum and maximum latitude and the minimum and maximum longitude of the area in
which the county is located.
Table 0511, FIPS PUB 8-5, Metropolitan Statistical Area (MSA) Codes, with PMSAs,
NECMAs, & CMSAs
"2-digit CMSA" An alternate coding scheme for identifying the CMSA.
Effective Date: 1/31/93 Release: 2.00 Page: VI - 4
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
"Pop. Level" The 1980 census population of the area.
• Identifies areas of 1 million or more persons.
• Identifies areas of 250,000 or more, but less than 1 million persons.
• Identifies areas of 100,000 or more, but less than 250,000 persons.
• Identifies areas of less than 100,000 persons.
Effective Date: 1/31/93 Release: 2.00 Page: VI - 5
-------
FRDS-H DATA ELEMENT DICTIONARY
SDC-0055-03I-LN-2003
January 31, 1993
Section VI
Lists of Acceptable Code Values with Associated Descriptions
B. Index to Code Tables
Sea Table
Note XD
Table Description
Code values and
Associated Descriptions for
D.B. Data Eleaent Name
Page
VI-
ID01 FTPS PUB 55-2, Indian
Reservation and Alaska
Remote Village Codes
ID02 USPS Postal State Codes
ID03 Combined Treatment Objective
and Treatment Process
Codes
ID04 Treatment Process Codes
ID05 Treatment Objective Codes
ID06 Contaminant Identification
Codes
ID07 Record Data Origin Codes
ID08 Violation Type Codes
ID09 Enforcement Follow-up Action
Codes
ID10 Combined Source/Entity
Record Type and Source/
Entry Point/Plant Type
Codes
C4 ST-IND-RES-CODE
CS15 PWS-GA-IND-RES-CODE
C139 PWS-SYSTEM-STATE
C313 PHS-AD-STATE
C483 PWS-SE-TREATMENT-OBJECTIVE
combined with
C485 PWS-SE-TREATMENT-PROCESS.
C485 PWS-SE-TREATMENT-PROCESS
C3015 VE-TREATKENT-PROCESS
C3017 VE-ALT-PROCESS
C483 PWS-SE-TREATMENT-OBJECTIVE
C1103 VIO-CONTAMINANT
C1291 ENF-LIN>:-COMTAMINANT
C1357 NCP-CONTAMINANT
C3003 VB-CONTAMINANT
C413 PHS-SE-DATA-ORIGIN
C517 PWS-GA-DATA-ORIGIN
C809 PNS-MILESTONE-ORIGIN
C1137 VIO-DATA-ORIGIN
C1211 ENF-DA7A-ORIGIN
C3025 VE-DATA-ORIGIN
C1105 VIO-TYPE
C1289 ENF-LINX-VIO-TYPE
C1185 VIO-LINK-FOLLOW-UP-ACTIOH
C1205 ENF-FOLLOW-UP-ACTION
C405 PWS-SE-3ECORD-TYPE
combined with
C407 PWS-SE-CODE
10
51
53
71
74
75
87
88
89
99
ID11 Township/Range Quarter
Section and Quarter-Quarter C425 'PWS-SE-QTR-SECTION
Section Codes C426 PHS-SE-2TR-QTR-SECTION
100
0001 EPA Region Codes
Cl
ST-REGION-CODE
101
Effective Date: 1/31/93
Release: 2.00
Page: VI -1
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
B. Index to Code Tables (Continued)
See Table
Note ZD
Table Description
Code values and
Associated Descriptions for
D.E. Data Element Mi
Page
VI -
0003 FIPS PUB 5-2, Alphabetic
State Codes and Selected
EPA Region Codes
0005 Primacy Flag Codes
0019 State Reconciliation Flag
Codes
0102 Grant Eligibility Codes
0103 PHS Status Codes
0105 PHS Type Codes
0107 PHS Activity Flag Codes
0109 History Flag Codes
0115 Population Category Codes
0119 Primary Source Type Codes
0129 Treatment Class Codes
0163 PHS Owner Type Codes
0165 Regulating Entity Codes
0171 PHS Reconciliation Flag
Codes
0303 Addressee Type Codes
0405 Source/Entity Record Type
Codes
0407 Source/Entry Point/Plant
Type Codes
0409 Source Availability Codes
0427 FIPS PUB 103, Hydrologic
Unit Codes
0429 On Reach Flag Codes
C3 ST-STATE-CODE 102
C5 ST-PRINACY-FLAG 105
C19 ST-RECON-FLAG 106
C102 PHS-GRANT-ELIGIBLE 107
C103 PHS-STATUS 108
C105 PHS-TYPE 109
C107 PHS-ACTXVXTY-FLAG 110
C109 PHS-HISTORY-FLAG 111
C115 PHS-POP-CATEGORY 112
C119 PHS-PRZHARY-SOURCE 113
C129 PHS-TREATMENT-CLASS 114
C163 PHS-OHNER-TYPE 115
C165 PHS-REGULATING-ENTITY 116
C171 PHS-RECON-FLAG 117
C303 PHS-AD-TYPE 118
C405 PHS-SE-RECORO-TYPE 119
C407 PHS-SE-CODE 120
C409 PHS-SE-AVAILABZLITY 121
C427 PHS-SE-RIVER-REACH-NUM 122
C429 PHS-SE-ON-REACH 385
Effective Date: 1/31/93
Release: 2.00
Page: VI - 7
-------
FRDS-n DATA ELEMENT DICTIONARY
SDC-0055-031-LN-2003
January 31, 1993
B. Index to Code Tables (Continued)
See Table
Note ID
Code values and
Associated Descriptions for
Table Description
Page
VI -
D.B. Data Eleaent Haae
C507 PWS-GA-CONGRESSIONAL-DIST 386
CSOB PWS-GA-STATE-COUNTY-CODE 447
C509 PWS-GA-FIPS-COUNTY-CODE 512
C511 PWS-GA-MSA-CODE 639
C603 PWS-SERV-CATEGORY 643
C605 PWS-SERV-PRIMARY-FLAG 644
C705 PWS-VISIT-REASON 645
C805 PWS-MILESTONE-CODE 646
C1001 NCD-RECON-FLAG 647
C1121 VIO-ANALYSZS-METHOD 648
C1131 VIO-MAJOR-VIOLATION-FLAG 654
.1 0507 PIPS PUB 9, Federal
Congressional District
Codes
1 0508 State-specific County Codes
1 0509 FZPS PUB 6-4, County Codes
6 0511 FZPS PUB 8-5, Metropolitan
Statistical Area (MSA)
Codes, with PMSAs, NECMAs,
& CMSAS
0603 Service Area Category Codes
0605 Primary Service Area Flag
Codes
0705 On-site Visit Reason Codes
0805 Pb/Cu Milestone Event Codes
1001 Non-compliance Data
Reconciliation Flag Codes
3 1121 Analysis Method Codes
1131 Major/Minor Violation Flag
Codes
1293 Enforcement Link Type Codes
2107 Sample Contaminant
Identification Codes
3005 Variance/Exemption/Other
Record Type Codes
3011 Variance/Exemption/Other
Status Codes
3019 Variance/Exemption/Other
Reason Codes
3027 Variance/Exemption/Other
Vulnerability Flag Codes
3103 Variance/Exemption/Other
Schedule Action Codes
C1293 ENF-LZNX-TYPE
C2107 SAMPLE-CONTAMINANT
C3005 VE-RECOSD-TYPE
I
C3011 VE-STArJS-CODE
C3019 VE-REASDN-CODE
C3027 VE-VUL-FLAG
C3103 VE-SCHED-ACTION
655
656
657
658
659
660
661
Effective Date: 1/31/93
Release: 2.00
Page: VI - b
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
Note Legend
Note Description
1 Values for this code table are listed by USPS Postal State Code.
2 Values for this code table are listed by Treatment Objective Code.
3 Values for this code table are listed by Contaminant Group Code.
4 Values for this code table are listed by Source/Entity Record Type Code.
5 Values for this code table are listed by U.S. Water Resources Council Region.
6 This code table is incomplete at this time.
Effective Date: 1/31/93 Release: 2.00 Page: VI - 9
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table ID01. FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Coda Value Associated Description Comment!B)
00430
00655
00765
00675
01095
01205
01310
01425
01640
01670
01975
02065
03330
03445
03555
03600
03865
03990
04210
04300
04435
05205
05750
05980
06525
07410
07620
06745
09605
10150
11600
12665
13235
13560
Indian Reservations and Alaska Remote
Villages of Alaska (AK>
Afognak (ANV) ANV701
Akhiok (ANV) ANV703
Akiachok (ANV) ANV704
Ak ink* ANV) ANV705
AKutan (ANV) ANV707
Alakanuk (ANV) ANV706
Alatna (ANV) (Included In Allakaket)
ANV709
Aleknagik IANV) ANV711
Alexander IANV) ANV713
Allakahet (ANV) ANV716
Ambler (ANV) ANV716
Anaktuvuk Pass (ANV) ANV720
Andreafsky (ANV) (Included In Saint
Mary's) ANV721
Angoon (ANV) ANV722
Aniak (ANV) ANV723
Annette Islands Reserve (Indian
Reservation)
Anvik (ANV) ANV726
Arctic Village (ANV) ANV727
Atka IANV) ANV728
Atkasook (Variant: Atkasuk) (ANV) ANV729
AtnautluaX IANVJ ANV730
Barrow (Utkiavil (ANVI ANV732
Beaver IANV) ANV733
Belkofsky (Belkofski) (ANV) ANV735
Bethel (ANV) ANV737
Bill Moore's (ANV) ANV739
Birch Creek (ANV) ANV741
Brevig Mission (ANVI ANV743
Buckland (ANV) ANV744
Cantwell (ANV) ANV746
Chalkyitsik (ANV) AHV748
Chefornak (ANV) ANV750
Chevak (ANV) ANV752
Chignik (ANV) ANV754
County Class (See Section VI., A.I
150 El
150 E6
050 El
050 E6
E6
270 E6
El
E6
170 El
E6
188 E6
165 E6
270 El
E6
050 E6
201 01 (Federally-administered)
E6
E2
E2
185 E2
050 E6
IBS E6
E2
El
050 E6
270 El
E2
180 E6
168 E6
E2
E2
050 E6
270 E6
E6
Effective Date: 1/31/93
Release Number: 2.00
Pane: VI -
10
-------
Section VI. Lists of Acceptable Code Values Mith Associated Descriptions
C. Detailed Lists of Code Values
Table ID01. FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
13670
13780
13630
14000
14110
14880
15455
17300
1774S
17650
18515
18955
19720
20390
21045
21150
21460
21700
21615
22255
22915
23790
24670
26765
27420
27535
27645
26350
29185
29295
30065
30500
31380
Note: TM« list begins on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska (AK)
Chignik Lagoon (ANVI ANV755
Chignik Lake (ANV) ANV756
Chilket (ANV) (Native name for Klukuan)
ANV757
Chistochina (ANV) ANV756
Chi tine (ANV) ANV759
Circle IANV) ANV762
Clark's Point (ANV) ANV763
Copper Center (ANV) ANV7&4
Craig (ANV) ANV766
Crooked Creek (ANV) ANV767
Deering (ANV) ANV769
Dillinghan IANV) ANV771
Dot Lake IANV) ANV773
Eagle (ANV) ANV775
Eek IANV) ANV776
Egegik (ANV) ANV777
Eklutna (ANV) (Included In Anchorage)
ANV776
EkuK (ANV) ANV779
EKuok (ANV) ANV760
Elim (ANV) ANV761
Enmonak (ANV) ANV782
English Bay lANVj ANV763
tvansville (ANV) ANV784
False Pass (ANV) ANV786
Fort Yukon (ANV) ANV768
Gakona (ANV) ANV789
Galena (ANV) ANV790
Gambell (ANV) ANV791
Georgetown (ANV) ANV792
Golovin (ANV) ANV794
Goodneus Bay (ANV) ANV795
Grayling (ANV) ANV796
Guldens (ANV) ANV797
Hamilton (ANV) ANV799
County Class (See Section VI., A.)
E2
E2
El
261
261
261
201
050
186
050
020
180
270
122
261
160
050
180
050
261
270
E2
E2
E2
E6
E2
E6
E2
E6
E6
E2
El
E6
E2
El
El
E6
E6
C6
C2
E2
E2
E6
E2
E6
E6
El
E6
E&
E6
E2
El
Effecti%
e: 1/31/93
Release Number:
Paoe: VI -
11
-------
Section VI. Lists of Acceptable Cede Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01. FIPS PUS 55-Zi Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
32310
33035
33365
33475
33915
34355
34465
34790
35120
35170
35890
36660
36775
36995
37320
37435
37540
37655
37980
39305
39415
39965
40405
40620
40B45
41200
41500
41610
41725
41635
41945
42055
42385
42490
Note: This list begins on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska (AK)
Healy Lake CANV) ANV800
Holy Cross (ANV) ANV601
Hoonah (ANV) ANVS02
Hooper Bay (ANV) ANV603
Hughes (ANV) ANV804
Huslia (ANV) ANV605
Hydaburg (ANV) ANV806
Igiugig (ANV) ANV607
Iliamna (ANV) ANV008
Inalik (ANV) (Native name for Diomede)
ANV809
Xvanof Bay (ANV) ANV810
Kaguyak (ANV) ANV812
Kake (ANV) ANV813
Kaktovik (ANV) ANV814
Kelskag (ANV) (Native name for Upper
Kalskag) ANV815
Kaltag (ANV) ANVB16
Karluk (ANV) ANV817
Kasaan (ANV) ANV818
Kasigluk (ANV) ANVA19
Kiana (ANV) ANV822
King Cove (ANV) ANV823
Kivalina (ANV) ANV826
Klauock (ANV) ANV827
Knik (ANV) ANV828
Kobuk (ANV) ANV829
Kokhanok (ANV) ANV831
Koliganek (ANV) ANV832
Kongiganak (ANV) ANV833
Kotlik (ANV) ANVB34
Kotzebue (ANV) ANV835
Koyuk (ANV) ANV836
Koyukuk (ANV) ANV837
Kwethluk (ANV) ANV839
Kwi^illingok (ANV) ANV840
County Class (See Section VI., A.)
E2
E6
E6
E6
270
201
180
150
280
185
050
150
201
050
188
188
201
170
186
050
270
188
160
050
050
E6
E6
E6
E2
E2
El
El
El
E6
E6
El
E6
E2
E6
E6
E6
E6
E6
E6
El
E6
E2
E2
E2
E6
E6
E6
E6
E6
E2
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
12
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Re
Code Valus Associated Description
>te Village Codes
Comment! s)
Effect!
43045
43810
44030
45465
46015
46780
46695
47000
47220
47955
46540
49530
sues
52060
52250
52395
52725
52940
53055
53275
53711
53630
53935
54155
54260
54480
54700
55035
55145
56240
56325
56355
56680
57060
e: 1/31/93
Note: This list begins on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska (AK)
Larsen Bay (ANV) ANV842
Level ock (ANV) ANV643
Line Village (ANV) ANVB45
Lower Kalskag IANV) ANV84A
McGreth IANV) ANV849
Manley Hot Springs (ANV) ANV850
Hanokotak (ANV) ANV851
Marshall IANV) (Native nan* for Fortune
Ledge) ANV852
Mary's Igloo (ANV) ANV653
rtekoryuk (ANV) ANV855
Hentasta Lake (ANV) ANVB56
Hinto IANV) ANVB57
Mountain Village (ANV) ANV659
Naknek (ANV) ANV860
Napainute (ANV) ANVB61
Napakiak (ANV) AHV862
Napaskiak (ANV) ANV863
Nelson Lagoon (ANV) ANV864
Nenana (ANV) ANV865
Newhalen (ANV) ANV661
Neu Stuyahok (ANV) ANVB69
Newtek (ANV) ANV870
Nightnute (ANV) ANVB71
Nikolai (ANV) ANVB72
NikolsM (ANV) ANV873
Ninilchik (ANV) ANV874
Noatak (ANV) ANV676
Nondalton (ANV) ANV87B
Noorvik IANV) ANV680
NorthMoy (ANV) ANV882
Nuiqsut (ANV) ANV863
Nulato (ANV) ANV8B4
Nunapitchuk-(ANV) (Included In Akolmiut)
ANV8B5
Ohogamiut (ANV) ANV686
Release Number:
County
150
050
050
270
180
050
261
270
060
050
050
050
050
050
122
188
IBB
IBS
050
270
Class (See Section VI.. A.)
E6
E2
E2
E6
E6
E2
E6
El
El
E6
E2
E2
E6
E2
El
E6
E6
E2
E6
E6
E6
El
E6
E6
E2
E2
E2
E6
E6
E2
E6
E6
El
El
Pa«
13
-------
Section VI. Lisis of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001. FIPS PUB 55-2i Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
57345
58330
58555
58600
58990
59540
60200
60640
60755
60660
61085
61635
61700
62290
63200
63395
63615
64605
64820
64930
65595
65720
65740
65810
66145
66365
66475
66510
67025
67465
67575
67685
Note: This list begins on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska (AK)
Old Harbor I ANYI ANVB87
Oscarville IANV) ANVBB9
OuzinMe
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village. Codes
Code Value Associated Description Coiment(s)
68235
68345
68675
68095
69270
69775
70105
70930
71090
71750
72190
72965
73290
73400
74610
75050
75165
75380
75490
75020
75935
76590
77695
76245
76795
79120
79235
79780
79890
60110
60160
60665
60775
60630
81960
62420
Note: Thim list begin* on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska (AK)
Solawik (ANV) ANV933
Seldovia (ANV) ANV934
Shagaltik (ANV) ANV936
ShaktooliK (ANV) ANV937
Sheldon's Point (ANV) ANV936
Shishmaref (ANV) ANV94D
Shungnak (ANV) ANV942
Slana tANV) ANV945
Sleetnute (ANV) ANV946
Solomon (ANV) ANV948
South Naknek (ANV) ANV950
Stebbins (ANV) ANV952
Stevens Village (ANV) ANV953
Stony River (ANV) ANV954
Takotna (ANV1 ANV956
Tanacross (ANV) ANV957
Tanana (ANV) ANV958
Tatitlek (ANV) ANV960
Tazlina (ANV) ANV961
Telida (ANV) ANV963
Teller (ANV) ANV964
Tetlin (ANV) ANVQiSl
logiak (ANV) ANV967
Toksook Bay (ANV) ANV9A9
Tuluksak (ANV) ANV971
Tuntutuliak (ANV) ANV972
Tununak (ANV) ANV973
Twin Hills (ANV) ANV975
Tyonek (ANV) ANV976
Ugashik (ANV) ANV976
Ukivok (ANV) ANV979
UnalaMeet (ANV) ANV961
Unalaska (ANV) ANV982
Unga IANV) ANV963
Uyak (ANV) ANV985
Venetie (ANV) ANV967
County Class (See Section VI., A.)
186
122
160
270
180
188
261
050
180
060
180
050
261
261
160
050
050
050
050
122
180
160
150
Eft
E6
E6
E6
El
E6
E6
E2
E2
El
E2
E6
E2
E2
E2
E2
E6
E2
E2
E2
E6
E2
E6
E6
K6
E2
E6
E2
E2
El
El
E6
E6
El
El
E2
Effectiv
e: 1/31/93
Release Number:
Pane: VI -
15
-------
Section' VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
62755
82865
64075
66270
66495
Note: This li*t begins on VI - 10
Indian Reservations and Alaska Remote
Villages of Alaska IAK)
Mairwright (ANV) ANV986
Hales (ANV) ANV969
Mhite Mountain (ANV) ANV991
Moody Island IANV) ANV993
Yakutat (ANV) ANV995
County Class (See Section VI., A.)
185
180
180
150
E6
E6
E6
El
E6
Effective Date: 1/31/93
Release Number: 2.00
P«ge: VI -
16
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOlt FXPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Conment(s)
09760
14660
14940
34320
24880
24910
25100
27120
27330
31740
33560
34470
36570
44400
48730
52650
53420
53720
62770
62980
64450
65120
Indian Reservations of Arizona (AZ)
Camp Verde Indian Reservation
Coeopah Indian Reservation
Colorado River Indian Reservation
CAlso CA)
Fort Apache Indian Reservation
Fort McDowell Indian Reservation
Fort Mojave Indian Reservation
(Also CA)
Fort Yuna Indian Reservation
(Also CA)
Gils Bend Indian Reservation
Gila River Indian Reservation
Havasupai Indian Reservation
Hop! Indian Reservation
Hualapai Indian Reservation
Kaibab Indian Reservation
Haricopa Indian Reservation (Ak Chin)
Navajo Indian Reservation
(Also NF1)
Papago Indian Reservation
Pasqua Yaqui Indian Reservation
Payson Community of Yavapai-Apache
(Indian Reservation)
Salt River Indian Reservation
San Carlos Indian Reservation
San Xaviar Indian Reservation
Yavapai Indian Reservation
County Class (See Section VI.. A.)
025 Dl (Federally-administered)
027 Dl (Federally-administered)
012 Dl (Federally-administered)
001 01 (Federally-administered)
013 Dl (Federally-administered)
015 Dl (Federally-administered)
027 01 (Federally-administered)
013 01 (Federally-administered)
013 Dl (Federally-administered)
005 01 (Federally-administered)
005 Dl (Federally-administered)
005 Dl (Federally-administered)
005 01 (Federally-administered)
021 Dl (Federally-administered)
001 01 (Federally-administered)
013 01 (Federally-administered)
019 01 (Federally-administered)
007 01 (Federally-administered)
013 01 (Federally-administered)
007 01 (Federally-administered)
019 01 (Federally-administered)
025 01 (Federally-administered)
Effectiv ~-te: 1/31/93
Release Number:
Page: VI -
17
-------
Section VI. Lists of Acceptable Code Values MIth Associated Descriptions
C. Detailed Lists of Code Values
Table IDOlt FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
01448
03214
03974
05353
06074
06400
06578
06630
06840
08244
09367
09424
09528
1C522
11030
12342
12786
14458
14876
16494
16819
17732
19966
22738
25044
25100
25184
25324
31294
Indian Reservations of California (CA)
Agua Caliente Indian Reservation
Alturas Rancheria I Indian Reservation)
Augustine Indian Reservation
Barona Rancheria (Indian Reservation)
Benton Paiute Indian Reservation
Berry Creek Indian Reservation
Big Bend Rancheria (Indian Reservation)
Big Lagoon Rancheria (Indian
Reservation)
Big Pine Rancheria (Indian Reservation)
Bishop Rancheria (Indian Reservation)
Bridgeport Colony (Indian Reservation)
Cabazon Indian Reservation
Cachil Dehe Rancheria (Indian
Reservation)
Cahuilla Indian Reservation
Canpo Indian Reservation
Copitan Grande Indian Reservation
Cedarville Rancheria (Indian
Reservation)
Chemehuevi Indian Reservation
Cold Springs Rancheria (Indian
Reservation)
Colorado River Indian Reservation
(Also AZ)
Cortina Rancheria (Indian Reservation)
Coyote Valley Rancheria (Indian
Reservation)
Cuyapaipe Indian Reservation
Dry Creek Rancheria (Indian Reservation)
Enterprise Rancheria (Indian
Reservation)
Fort Bidwell Indian Reservation
Fort Independence Indian Reservation
Fort Mojave Indian Reservation
(Also KV)
Fort Yuna Indian Reservation
(Also AZ)
Grindstone Creak Rancheria (Indian
Reservation)
County Class (See Section VI., A.)
065 Dl (Federally-administered)
049 Dl (Federally-administered)
065 Dl (Federally-administered)
073 01 (Federally-administered)
051 Dl (Federally-administered)
007 Dl (Federally-administered)
089 01 (Federally-administered)
023 Dl (Federally-administered)
027 Dl (Federally-administered)
027 Dl (Federally-administered)
051 Dl (Federally-administered)
065 01 (Federally-administered)
Oil .01 (Federally-administered)
065 Dl (Federally-administered)
073 01 (Federally-administered)
073 01 (Federally-administered)
049 01 (Federally-administered)
071 01 (Federally-administered)
019 01 (Federally-administered)
065 01 (Federally-administered)
Oil Dl (Federally-administered)
045 Dl (Federally-administered)
073 Dl (Federally-administered)
097 01 (Federally-administered)
007 01 (Federally-administered)
049 Dl (Federally-administered)
027 01 (Federally-administered)
071 01 (Federally-administered)
025 01 (Federally-administered)
021 01 (Federally-administered)
Effective Date: 1/31/95
Release Number: 2.00
Paoe: VI -
18
-------
Section VI. Lists of Acceptable Code Values Nith Associated Descriptions
C. Detailed Lists of Code Values
Table ID01,. FIPS PUB 55-2. Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!»)
34554
34558
34659
36316
37000
39374
40317
40932
41394
42594
43130
44070
45390
45582
47056
47336
49002
49334
55062
56164
56330
60347
60823
62146
63162
63306
66188
68312
70112
70122
Note: This list begins on VI - 18
Indian Reservations of California (CA)
Hoopa Valley (Indian Reservation)
Hoopa Valley Extension Indian
Reservation
Hopland Rancheria (Indian Reservation)
Inaja-Cosmit Indian Reservation
Jackson Rancheria (Indian Reservation)
La Jolla Indian Reservation
La Posta Indian Reservation
Laytonville Rancheria (Indian
Reservation)
Likely Rancheria (Indian Reservation)
Lone Pine Rancheria (Indian Reservation)
Lookout Rancheria (Indian Reservation)
Los Coyotes Indian Reservation
Manchester Rancheria (Indian
Reservation)
Kanzanita Indian Reservation
Mesa Grande Indian Reservation
MiddletoHn Rancheria (Indian
Reservation)
Montgomery Creek Rancheria (Indian
Reservation)
Morongo Indian Reservation
Pala Indian Reservation
Pauma Indian Reservation
Pechanga Indian Reservation
Ramona Indian Reservation
Resighini Rancheria (Indian Ri
Rincon Indian Reservation
lervation)
Roaring Creek Rancheria (Indian
Reservation)
Round Valley Indian Reservation
Ramsey Rancheria (Indian Reservation)
San Manuel Indian Reservation
San Pasqual Indian Reservation
Santa Rosa Indian Reservation
Santa Rosa Rancheria (Indian
Reservation)
County Class (See Section VI.. A.)
C23 Dl (Federally-administered)
015 Dl (Federally-administered)
045 Dl (Federally-administered)
073 Dl (Federally-administered)
005 01 (Federally-administered)
073 Dl (Federally-administered)
073 Dl (Federally-administered)
045 Dl (Federally-administered)
049 Dl (Federally-administered)
027 Dl (Federally-administered)
049 01 (Federally-administered).
073 01 (Federally-administered)
045 Dl (Federally-administered)
073 01 (Federally-administered)
073 01 (Federally-administered)
033 Dl (Federally-administered)
089 Dl (Federally-administered)
065 Dl (Federally-administered)
073 01 (Federally-administered)
073 Dl (Federally-administered)
065 Dl (Federally-administered)
065 Dl (Federally-administered)
015 Dl (Federally-administered)
073 Dl (Federally-administered)
089 Dl (Federally-administered)
045 01 (Federally-administered)
113 01 (Federally-administered)
071 Dl. (Federally-administered)
073 01 (Federally-administered)
065 01 (Federally-administered)
031 01 (Federally-administered)
Effective
1/31/93
Release Number:
Paoe: VI -
19
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2t Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
70166
70210
71306
71518
71558
72468
74162
75652
77368
77524
BOC28
60452
80714
60774
81002
62655
66276
86657
Note: This list begins on VI - 18
Indian Reservations of California (CA)
Santa Ynez Indian Reservation
Santa Ysabel Indian Reservation
Sheep Ranch Rancherin (Indian
Reservation)
Sherwood Valley Rancheria (Indian
Reservationl
Shingle Springs Rancher!a (Indian
Reservation)
Soboba Indian Reservation
Stewart's Point Rancheria (Indian
Reservation)
Sulphur Bank Rancheria (Indian
Reservation)
Susanville Indian Reservation
Sycuan Indian Reservation
Torres-Martinez Indian Reservation
Trinidad Rancheria (Indian Reservation)
Tule River Indian Reservation
Tuolumne Rancheria (Indian Reservation)
Twenty-Nine Pains Indian Reservation
Viejas Rancheria (Indian Reservation)
Hoodfords Community (Indian Reservation)
XL Ranch Indian Reservation
County Class (See Section VI., A.)
083 01 (Federally-administered)
073 Dl (Federally-administered)
009 01 (Federally-administered)
045 01 (Federally-administered)
017 Dl (Federally-administered)
065 Dl (Federally-administered)
097 Dl (Federally-administered)
033 Dl (Federally-administered)
035 01 (Federally-administered)
073 Dl (Federally-administered)
025 Dl (Federally-administered)
023 Dl (Federally-administered)
107 01 (Federally-administered)
109 Dl (Federally-administered)
071 Dl (Federally-administered)
073 Dl (Federally-administered)
003 Dl (Federally-administered)
049 Dl (Federally-administered)
Effective Datfll 1/31S93
Release Numberi 2.00
Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values Mtth Associated Descriptions
C. Detailed Lists el Code Values
Table ID01, FXPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Con«nt(sl
Indian Reservations of Colorado ICO) County Class (Sea Section VI., A.)
72340 Southern Ute Indian Reservation 007 01 (Federally-administered*
79930 Ute Mountain Indian Reservation 067 01 (Federally-administered)
(Also MM
Etfectiv »e: 1/31/93 Release Number: Pa tie: VI - 21
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
Indian Reservations of Connecticut (CT) County Class (See Section VI., A.)
21560 Eastern Pequot Indian Reservation Oil 04 (State-administered)
31700 Golden Hill Indian Reservation 001 04 (State-administered)
67230 Schaghtieoke Indian Reservation 005 04 (State-administered)
62130 Western Pequot Indian Reservation Oil D4 (State-administered)
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 22
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOlt FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!a)
Indian Reservations of Florida (FL) County Class (See Section VI., A.)
06400 Big Cypress Indian Reservation 051 Dl I Federally-administered)
08550 Brighton Indian Reservation 043 Dl (Federally-administered)
32125 Hollywood Indian Reservation Oil Dl (Federally-administered)
45310 Miceo9uK«e Indian Reservation Oil D4 (State-administered)
Eftecti- ••: 1/31/93 Release Number: Page: VI - 23
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-Zi Indian Reservation and Alaska Renote Village Codes
Code Value Associated Description Comment!•)
Indian Reservations of Georgia (6A) County Class (See Section VI.• A.)
75454 Tana Indian Reservation 131 04 (State-administered)
Effective Date: 1/31/93 Release Number: Z.OO Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Coimeent(s)
Indian Reservations of Iowa (IA» County Class (See Section VI., A.)
59092 Omaha Indian Reservation 133 Dl (Federally-administered)
69600 Sac and Fox Indian Reservation 171 Dl (Federally-administered)
Etfecti- 'e: 1/31/93 Release Number: Paoe: VI - 25
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!»)
16840
23050
28450
44220
57340
Indian Reservations of Idaho I ID)
Coeur d'Alene Indian Reservation
Duck Valley Indian Reservation
(Also NV)
Fort Hall Indian Reservation
Kootenai Indian Reservation
Nez Perce Indian Reservation
County Class ISee Section VI., A.)
009 Dl (Federally-administered)
073 Dl (Federally-administered)
005 01 (Federally-administered)
021 Dl (Federally-administered)
035
01 (Federally-administered)
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
26
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
Indian Reservations of Kansas IKS) County Class (See Section VI.• A.)
34462 Iowa Indian Reservation 013 Dl (Federally-administered)
(Also HE)
36725 Kickapoo Indian Reservation 013 01 (Federally-administered)
57262 Pottauatoai Indian Reservation 065 01 (Federally-administered)
62037 Sac and Fox Indian Reservation 013 01 (Federally-administered)
(Alsa HE I
Effect*. te: 1/31/93 Release Humbert Pioe: VI - 27
-------
Section VI. Lists of Acceptable Cede Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, TIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!•»
Indian Reservations of Louisiana (LA) County Class (See Section VI., A.I
15060 Chitinacha Indian Reservation 101 01 (Federally-administered)
16065 Coushatta Indian Reservation 003 01 (Federally-administered)
76660 Tunica-Biloxi Indian Reservation 009 04 (State-administered)
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 20
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Commentls)
Indian Reservations of Massachusetts
County Class (See Section VI. • A.)
29141 Hassananisco Indian Reservation 027 D4 (State-administered)
72720 Hanpanoag Indian Reservation 005 D4 (State-administered)
Effectiv >: 1/31/93 Release Number:.. Pane: VI - 29
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOL FIPS PUB S5-Z, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Coimnent(s)
Indian Reservations of Maine (ME) County Class (See Section VI.• A.)
34750 Indian Township Indian Reservation 029 D5 (State-administered)
57955 Penobscot Indian Island Indian 019 D5 (State-administered)
Reservation . . .
59635 Pleasant Point Indian Reservation 029 05 (State-administered)
Effective Date: 1/31/93 Release Number: 2.00 •*«» « ' 30
-------
Section VI. Li sis of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli FIPS PUB 55-2. Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
06000
36370
41180
45560
60604
64244
71745
Indian Reservations of Michigan (MI)
Bay Mills Indian Reservation
Hannahville Community (Indian
Reservation)
Isabella Indian Reservation
L'Arise Indian Reservation
Ontonagon Indian Reservation
Pine CreeK Indian Reservation
Sault Ste. Maria Indian Reservation
County Class (See Section VI., A.)
033 Dl (Federally-administered)
109 Dl (Federally-administered)
073 Dl (Federally-administered)
013 Dl (Federally-administered)
131 Dl (Federally-administered)
025 D4 (State-administered)
033 01 (Federally-administered)
Effective ~ te: 1/31/93
Release Number: ? "0
Pane: VI -
31
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!•)
06074
15206
21590
25062
36242
36348
42200
43135
52280
53512
56459
59356
66316
66856
70042
Indian Reservations of Minnesota (MM) County
Bois Forte (Nett Lake) Indian 071
Reservation
Deer Creek Indian Reservation 061
Fond Du Lac Indian Reservation 017
Grand Portage Indian Reservation 031
Leech LaKe Indian Reservation 007
Lower Sioux Community (Indian 127
Reservation)
Mi lie Lacs Indian Reservation 001
Minnesota Chippewa Trust Lands (Indian 001
Reservation)
Prairie Island Community (Indian 049
Reservation I
Red LaKe Indian Reservation 007
Sandy Lake Indian Reservation 001
Shakopee Community (Indian Reservation) 139
Upper Sioux Community (Indian 173
Reservation)
Ver«iillion Lake Indian Reservation 137
White Earth Indian Reservation 005
Class (See Section VI., A.)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01> FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
Indian Reservations of Mississippi (MS) County Class (See Section VI., A.I
47980 Mississippi Chocton Indian Reservation 007 01 (Federally-administered)
Effecti te: 1/31/93 Release Nunber: 1 Paoe: VI - 33
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01. FIP3 PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comrnent(s)
Indian Reservations of Montana A.)
06081 Big Horn Other Reservation Land 003 Dl (Federally-administered)
07225 Blackfeet Indian Reservation 035 Dl (Federally-administered)
183ZS Crow Indian Reservation 003 Dl (Federally-administeredI
26650 Flathead Indian Reservation 029 Dl (Federally-administered)
27925 Fort Belkrup Indian Reservation DCS Dl (Feder»Lly-admimsteredl
285Z5 Fort Peck Indian Reservation 019 01 (Federally-administered)
54550 Northern Cheyenne Indian Reservation 003 Dl (Federally-administered)
43925 Rocky Boy'a Indian Reservation 015 Dl (Federally-administered)
Effective Oat«i 1/31/93 Release Humbert B.OO Paoet VI - 3*
-------
Section VI. Li sis of Acceptable Coda Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Coamtent(s)
Indian Reservations of North Carolina
(NCI County Class (Sea Section VI.. A.I
19390 Eastern Cherokee Indian Reservation 039 01 (Federally-administered)
Effecti te: 1/31/93 Release Number: 1 Paae: VI - 35
-------
Section VI. Lists of Acceptable Code Values Nith Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Conmentls)
Indian Reservations of North Dakota (NO) County Class (See Section VI., A.)
27340
27780
73460
75300
60020
Fort Berthold Indian Reservation
Fort Totten Indian Reservation
Sisseton Indian Reservation
(Also SDI
Standing Rock Indian Reservation
(Also* SDI
Turtle Mountain Indian Reservation
025 Dl (Federally-administeredI
005 01 (Federally-administered)
077 Dl (Federally-administered)
085 Dl (Federally-administered)
079 Dl (Federally-administered)
Effective Date: 1/31/93
Release Number: 2.00
Pane: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001, FIPS PUB 55-2. Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
24160
37035
42900
43545
53310
Indian Reservations of Nebraska (NE) County
Iowa Indian Reservation 147
(Also KSI
Omaha Indian Reservation 021
Sac and Fox Indian Reservation 147
(Also KS)
Santee'Indian Reservation 107
Hinnebago Indian Reservation 051
Class (See Section VI.. A.)
Dl (Federally-administered)
01 (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Effecti
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 100li FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
00660
01815
11240
16630
34690
35180
35390
37210
47990
51000
51560
56080
58700
61290
67000
67380
67470
67490
67940
68700
70160
70320
70740
76340
77110
61380
66350
86630
Indian Reservations of New Mexico (MM)
Acona Pueblo (Indian Reservation)
Alamo Indian Reservation
Canoncito Indian Reservation
Cochiti Pueblo (Indian Reservation)
Isleta •Hieblo (Indian Reservation)
Jemer Pueblo (Indian Reservation)
Jicarilla Apache Indian Reservation
Laguna Pueblo (Indian Reservation)
Kescalero Apache Indian Reservation
Nambe Pueblo (Indian Reservation)
Navajo Indian Reservation
(Also UT)
Picuris Pueblo (Indian Reservation)
Pojoaque Pueblo (Indian Reservation)
Ramah Community (Indian Reservation)
Sandia Pueblo (Indian Reservation)
San Felipe Pueblo (Indian Reservation)
San Felipe/Santa Ana Joint Area
San Felipe/Santo Domingo Joint Area
San Ildefonso Pueblo (Indian
Reservation)
San Juan Pueblo (Indian Reservation)
Santa Ana Pueblo (Indian Reservation)
Santa Clara Pueblo (Indian Reservation)
Santo Domingo Pueblo (Indian
Reservation)
Taos Pueblo (Indian Reservation)
Tesuque Pueblo (Indian Reservation)
Ute Mountain Indian Reservation
(Also CO)
Zia Pueblo (Indian Reservation)
Zuni Pueblo (Indian Reservation)
County Class (See Section VI., A.)
006
053
001
043
001
043
039
001
035
049
031
055
049
006
001
043
043
043
043
039
043
039
043
055
049
045
043
006
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
Dl (Federally-administered)
(Federally-administered)
Dl
01
(Federally-administered)
01 (Federally-administered)
01 (Federally-administered)
01 (Federally-administered)
Dl (Federally-administered)
01 (Federally-administered)
01 (Federally-administered)
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
36
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli F1P3 PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Commentls)
10000
19550
19900
20300
23550
24200
24300
25500
25550
29900
40300
43050
47800
56800
60650
71000
72200
81200
82200
84850
05600
85800
Indian Reservations of Nevada INV)
Carson Colony (Indian Reservation)
Dress lervi lie Colony (Indian
Reservation)
Duck Valley (Western Shoshone) Indian
Reservation (Also ID)
Duckwater Indian Reservation
Ely Colony (Indian Reservation)
Fallen Colony (Indian Reservation)
Fallen Indian Reservation
Fort McDermitt Indian Reservation
(Also OR)
Fort Hojave Indian Reservation
(Also AZ)
Goshute Indian Reservation
(Also UT)
Las Vegas Colony (Indian Reservation)
Lovelock Colony (Indian Reservation)
Moapa River Indian Reservation
Pyramid Lake Indian Reservation
Reno-Sparks Colony (Indian Reservation)
Summit Lake Indian Reservation
Te-Moak Indian Reservation
Halker River Indian Reservation
Hashoe Indian Reservation
Hirmenucca Colony (Indian Reservation)
Ym nnftuii IinJinn Reaviva
Yonba' Indian Reservation
County Class (See Section VI., A.)
510 Dl (Federally-administered)
005 01 (Federally-administered)
007 01 (Federally-administered)
023 01 (Federally-administered)
033 01 (Federally-administered)
001 01 (Federally-administered)
001 01 (Federally-administered)
013 Dl (Federally-administered)
003 01 (Federally-administered)
033 01 (Federally-administered)
003 Dl (Federally-administered)
027 Dl (Federally-administered)
003 Dl (Federally-administered)
019 Dl (Federally-administered)
031 01 (Federally-administered)
013. 01 I Federally-administered)
007 01 (Federally-administered)
001 Dl (Federally-administered)
005 01 (Federally-administered)
013 01 (Federally-administered)
01? 01 (r*d«-«lly-administered)
023 01 (Federally-administered)
Effectiv
e: 1/31/93
Release Number:
Paoe: VI - 39
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation end Alaska Remote Village Codes
Code Value Associated Description Comment!s)
01308
13035
54523
54980
59106
64727
67059
75011
75748
Indian Reservations of Hen York (NY)
Allegany Indian Reservation
Cattaraugus Indian Reservation
Oil Springs Indian Reservation
Onondaga Indian Reservation
Poospatuck Indian Reservation
St. Regis HohatA Indian Reservation
Shinnecock Indian Reservation
TonaManda Indian Reservation
Tuscarora Indian Reservation
County Class (See Section VI.. A.)
009 D5 (State-administered!
009 D5 (State-administered)
003 D5 (State-administered)
067 D5 (State-administered)
103 D5 (State-administered)
033 D5 (State-administered)
103 05 (State-administered)
029 05 (State-administered)
063 05 (State-administered)
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI.-
40
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!a)
Indian Reservations of Oklahoma (OK) County Class (See Section VI., A.)
55075 Oklahoma Historic Reservation Area 001 09
56300 Osage Indian Reservation 113 Dl (Federally-administeredI
Effective : 1/31/93 Release Number:
paa«: VI -
-------
Section VI. Lists of Acceptable Cede Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1001, FIPS PUB 55-3, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment! •)
______....__•. •»_____.. _«__••__.•_« ___________ •__•_____—~ V — __•»_»•- ______«____•_.. — •. *____*_______•
Indian Reservations of Oregon IOR) County Class (See Section VI., A.)
07825 Burns Indian Reservation 025 Dl (Federally-administered)
26475 Tort ncDermitt Indian Reservation 045 Dl (Federally-administered)
(Also NVI
75750 Unetilla Indian Reservation 059 Dl (Federally-administered)
78650 Mara Springs Indian Reservation 005 01 (Federally-administered)
Effective Date: 1/31/91 Release Number: 2.00 Peoe: VI -
-------
Section VI. Lists of Acceptable Code Values nith Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli FIPS PUB 55-2. Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description CommentIs)
Indian Reservations of South Carolina
(SO County Class (See Section VI., A.)
12455 Cstaubo Indian Reservation 091 D4 (State-administered)
Effect
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIP5 PUB 55-2. Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
Indian Reservations of South Dakota (SO) County Class (See Section VI.. A.)
11660
14660
21620
39220
49700
55980
59340
61260
73100
Cheyenne River Indian Reservation
Crow Creek Indian Reservation
Flandreau Indian Reservation
Lower Brule Indian Reservation
Pine Rvdge Indian Reservation
Rosebud Indian Reservation
Sisseton Indian Reservation
(Also NO)
Standing Rock Indian Reservation
CAlso ND)
Yankton Indian Reservation
041 Dl (Federally-administered)
017 Dl (Federally-administered)
101 01 (Federally-administered)
005 Dl (Federally-administered)
007 01 (Federally-administered)
053 01 (Federally-administered)
029 01 (Federally-administered)
031 Dl (Federally-administered)
023 01 (Federally-administered)
Effective Data: 1/31/93
Release Numbert 2.00
Page i VI -
-------
Section VI. Lists of Acceptable Code Values Ni'th Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!si
Indian Reservations of Texas (TX) County Class (See Section VI., A.1
01556 Alabana-Coushatta Indian Reservation 373 D* (State-administered)
7298* Tigua Indian Reservation 141 D4 (State-administered)
Effect* -lata: 1/31/W Release Number- 00 p'aqe: VI - 45
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2i Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Coimnent(s)
30350
53700
69420
70795
77920
Indian Reservations of Utah (UTI
Goshute Indian Reservation
(Also NV)
Navajo Indian Reservation
(Also AZ)
Skull Valley Indian Reservation
Southern Paiute Indian Reservation
Uintah And Ouray Indian Reservation
County Class (See Section VI., A.)
023 .01 (Federally-administered)
037 Dl (Federally-administered)
045 01 (Federally-administered)
021 04 (State-administered)
007 01 (Federally-administered)
Effective Date: 1/31/93
Release NumberI 2.00
Pane: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1D01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!8J
Indian Reservations of Virginia (VAI County Class (See Section VI., A.)
50160 Mattaponi Indian Reservation 101 04 I State-administered)
60496 Paounkey Indian Reservation 101 04 (State-administered)
Etfecti- te: 1/31/93 Release Number: Paae: VI - 47
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIPS PUB 55-2, Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment(s)
11510
14240
31565
34715
40575
40665
42205
47700
49205
49285
52470
55610
55715
56720
57010
57060
61402
63910
64785
67105
67350
69310
72730
73652
00045
Indian Reservations of Washington (NA)
Chehalis Indian Reservation
Colville Indian Reservation
Hoh Indian Reservation
Kalispel Indian Reservation
Lower Plush Indian Reservation
Lummi Indian Reservation
r1akah Indian Reservation
Kuckleshoot Indian Reservation
Misqually Indian Reservation
Nooksack Indian Reservation
Ozette Indian Reservation
Port Gamble Indian Reservation
Port Madison Indian Reservation
Puyallup Indian Reservation
Quileute Indian Reservation
Quinault Indian Reservation
Sauk-Suiattle Indian Reservation
Snoalwater Indian Reservation
Skokomish Indian Reservation
Spokane Indian Reservation
Squaxin Island Indian Reservation
SMinonish Indian Reservation
Tulalip Indian Reservation
Upper Skagit Indian Reservation
Yakina Indian Reservation
County Class ISee Section VI., A.)
027 Dl (Federally-administered)
019 Dl (Federally-administered)
031 Dl (Federally-administered)
051 Dl (Federally-administered)
009 01 (Federally-administered)
073 Dl (Federally-administered)
009 Dl (Federally-administered)
033 Dl (Federally-administered)
053 Dl (Federally-administered)
073 Dl (Federally-administered)
009 Dl (Federally-administered)
035 Dl (Federally-administered)
035 01 (Federally-administered)
053 01 (Federally-administered)
009 Dl (Federally-administered)
027 01 (Federally-administered)
061 Dl (Federally-administered)
049 Dl (Federally-administered)
045 01 (Federally-administered)
043 01 (Federally-administered)
045 Dl (Federally-administered)
057 01 (Federally-administered)
061 01 (Federally-administered)
057 01 (Federally-administered)
039 Dl (Federally-administered)
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
48
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOli FIPS PUB 55-2• Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Commentls)
01225
40650
40725
50985
60025
64600
66600
70600
74540
77450
68212
Indian Reservations of Hi sconsin (HI)
Bad River Indian Reservation
Lac Courts Oreilies Indian Reservation
Lac du Flambeau Indian Reservation
Menoninee Indian Reservation
Oncida'Indian Reservation
Potawatoai Indian Reservation
Red Cliff Indian Reservation
St. Croix Indian Reservation
Sokaogan Chippem Community (Indian
Reservation)
Stockbridca Indian Reservation
Wisconsin Mimebago Indian Reservation
County Class «See Section VI.. A.)
003 Dl (Federally-administered)
113 Dl (Federally-administered)
051 Dl (Federally-administered)
078 Dl (Federally-administered)
009 01 (Federally-administered)
041 Dl (Federally-administered)
007 Dl (Federally-administered)
005 Dl (Federally-administered)
041 Dl (Federally-administered)
115 Dl (Federally-administered)
053 Dl (Federally-administered)
Effective
-: 1/31/93
Release Number: Z--*'
Paae: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID01, FIP3 PUB 55-2• Indian Reservation and Alaska Remote Village Codes
Code Value Associated Description Comment!s)
Indian Reservations of Wyoming (NY) County Class (See Section VI.. A.)
64200 Hind River Indian Reservation 013 01 (Federally-administered)
Effective Date: 1/31/93 Release Number» 2.00 Pace: VI - 50
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
-Code Value
Table 1002, USPS Postal State Codas
Associated Description
Comment! at
AK
AL
A°
AS
AZ
CA
CO
CT
DC
OE
FL
FM
CA
GU
HI
I A,
ID
IL
IN
KS
KT
LA
HA
H>
ME
HH
Ml
HH
no
HP
ns
HT
NC
NO
NE
NH
Alaska
Alabama
Arkansas
American Sanoa
Art cone
California
Colorado
Connecticut
District of Columbia
Delaware
Florida
Federated States of Micronesia
Georgia
Guam
Hawai i
Iowa
Idaho
Illinois
Indi ana
Kansas
Kentucky
Louisiana
Massachusetts
Maryland
Maine
Marshall Islands i Republic ol the
Nichrgan
Minnesota
Missouri
Northern Mariana Islands
Hississippi
Montana
North Carolina
North Dakota.
Nebraska
New Haapshire
ZlPcodt
Prefix
9
3
7
9
5
9
6
0
2
1
3
9
3
9
9
5
8
6
4
6
4
7
•
2
0
9
4
5
6
9
3
5
2
5
6
0
! Telephone
Area Code! 5) (As of 11/92)
907
205
501
664
602
209 213 310 40S 415 510 619 707
714 80S 818 909 916
303 719
203
202
302
305 407 613 904
404 7D« 912
671
606
319 SIS 712
208
217 309 312 618 706 815
219 317 612
316 913
502 606
318 504
413 5CS 617
301 410
207
313 517 616 906
216 507 612
314 417 816
Z34(Susupe) 433fTinian)
5321Rota> 670(Saipan)
601
406
704 914
701
306 402
603
Effectiv
e: 1/31/93
Release Number:
Paqe: VI -
51
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDOZi USPS Postal State Codes
Associated Description
Comment! s)
NJ
NM
NV
NY
OH
OK
OR
PA
PR
PH
RI
SC
SO
TN
TX
UT
VA
VI
VT
HA
HI
HV
MY
Note: This list begins on VI - 51
New Jersey
New Mexico
Nevada •
New York
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Palaui Republic of
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Utah
Virginia
Virgin Islands of the U.S.
Vermont
Washington
Wisconsin
West Virginia
Wyoming
ZIPcode Telephone
Prefix Area Code(s) (As of 11/92)
0 201 609 908
a 505
6 702
1 212 315 516 516 607 716 718 914
917
4 216 419 513 614
7 405 918
9 503
1 215 412 717 614
0 809
9
0 401
Z 803
5 605
3 615 901
7 210 214 409 512 713 806 817 915
8 801
2 703 804
0 009
.0 802
9 206 509
5 414 608 71S
2 304
8 307
Effective Date: 1/31/93
Release Number: 2.00
Pane: VI -
52
-------
Code Value
Section VI. Lids of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003, Combined Treatment Objective and Treatment Proceac. Codes
Associated Description Comment*9)
A996
A997
A99B
Additional Treatment Elsewhere
Treatment Processes
Treatment Applied by Seller
Treatment Applied at.Plant
Treatment Applied at Entry Point
This table contains valid combinations
of values for data elements C483 A MflS
Pos. 1 = C463
Pos. Z - 4 = C465
In'addition to other treatment(s)
In addition to other treatment!9)
In addition to other treatment!si
Effective
1/31/93
Release Number: 2
Paee: VI -
53
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03, Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
B1Z1
B125
B141
B143
B145
B147
B149
B160
B200
B220
B240
B344
B345
B360
B500
B541
B543
B600
B640
B660
B7ZO
B741
B742
Disinfection By-products Control
Treatment Processes
Activated Carboni Granular
Activated Carbon, Powdered
Aeration, Cascade
Aeration, Diffused
Aerationi Packed Touer
Aerationi Slat Tray
Aerationt Spray
Algae Control
Chloraaines
Chlorine Dioxide
Coagulation
Filtrationi Pressure Sand
Filtration• Rapid Sand
Flocculation
Lime - Soda Ash Addition
Ozonationi Post
Ozonation, Pre
Rapid Mix
Reverse Osmosis
Sedimentation
Ultraviolet Radiation
pH Adjustment, Post
pH Adjustmenti Pre
This table contains valid combinations
of values for data elements C483 ft C485
Pos. 1 = C483
Pos. 2 - 4 = C465
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table .1003> Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
C441
C443
C445
C449
C680
C710
C741
Corrosion Control
Treatment Processes
Inhibitor! Bimetallic Phosphate
Inhibitor• Hexametaphosphate
Inhibitor, Orthophosphate
Inhibitor. Polyphosphate
Inhibitor. Silicate
Sequestration
pH Adjustment
pH Adjustmenti Post
This table contains valid combinations
of values for data elements C463 • C4B5
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective
-: 1/31/93
Release Number: ?
Paqe: VI -
55
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
0190
0200
0220
D346
0401
0403
0421
D423
0455
0541
0543
0720
Disinfection
Treatment Processes
Brominization (Special Use)
Chloranines
Chlorine .Dioxide
Filtration. Slow Sand
Gaseous Chlorination. Post
Gaseous Chlorination, Pre
Hypochlorination. Post
Hypochlorinationi Pre
Iodine
Ozonationi Post
Ozonationi Pre
Ultraviolet Radiation
This table contains valid combinations
of values for data elements C483 t C485
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective Date: 1/31/93
Release Number: 2.00
Paqe: VI -
56
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table -ID03. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
Em
E141
E143
E145
E147
E149
E620
E623
E625
E627
Dechlorination
Treatment Processes
Activated Carboni Granular
Aerationt Cascade
Aerationi Diffused
Aerationi Packed Toner
Aeration( Slat Tray
Aerationi Spray
Reducing Agents
Reducing Agenti Sodium Bisulfate
This table contains valid combinations
of values for data elements C483 & C465
Pos. 1 = C483
Pos. 2 - 4 = C465
Reducing Agent»
Reducing Agent•
Sodium Sulfite
Sulfur Dioxide
Effective
1/31/93
Release Number: '
Paae: VI -
57
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
F141
F143
F145
F147
FI49
F300
F343
F344
F345
F403
F423
F560
F560
F640
F660
F680
F700
F740
F742
Iron Removal
Treatment Processes
Aeration• Cascade
Aerationi Diffused
Aerationi Packed Tower
Aerationi Slat Tray
Aeration* Spray
Distillation
Filtration* Greensand
Filtrationi Pressure Sand
Filtration. Rapid Sand
Gaseous Chlorinatton> Pre
Hypochlorination* Pre
Ozonationi Pre
Permanganate
Peroxide
Reverse Osmosis
Sedimentation
Sequestration
Sludge Treatment
pH Adjustment
pH Adjustment. Pra
This table contains valid combinations
of values for data elements C483 ft C485
Pos. 1 = C463
Pos. 2 - 4 = C485
Effective Date: 1/31/93
Release Number: 2.00
Page: VI -
56
-------
Code Value
Section VI. Lists of Accepiable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
1100
1121
1160
1300
1320
1344
1345
1360
1460
1500
1600
1640
1660
1660
1700
1742
Inorganics Removal
Treatment Processes
Activated Alumina
Activated Carboni Granular
Bone CHar
Coagulation
Distillation
Electrodialysis
Filtration* Pressure Sand
Filtration, Rapid Sand
Flocculation
Ion Exchange
Lime - Soda Ash Addition
Rapid Nix
Reverse Osmosis
Sedimentation
Sequestration
Sludge Treatment
pH Adjustment. Pre
This table contains valid combinations
of values for data elements C463 4 C465
Pos. 1 = C463
Pos. 2 - 4 = C485
Effectiv
1/31/93
Release Number:
Paoe: VI -
59
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03, Combined Treatment Objective and Treatment Process Codes
Associated Description Conment(s)
11300
M343
M403
M423
H543
M640
M680
Manganese Removal
Treatment Processes
Distillation
Filtrationi Greensand
Gaseous Chlorination, Pre
Hypochlorinationi Pre
Ozonationi Pre
Reverse Osmosis
Sequestration
This table contains valid combinations
of values for data elements C483 ft C4S5
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
60
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table-ID03» Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!a)
NO 00
No Treatment at Source
Treatment Processes
No Treatment / Not Applicable
This table contains valid combinations
of values for data elements C4B3 ft C485
Pas. 1 = C4B3
Pos. 2 - 4 = C485
N349
N350
N351
Unfiltered, Avoiding Filtration
Unfiltered. Must Install Filtration
Not Subject to SWTR
N996
N997
N998
Treatment Applied by Seller
Treatment Applied at Plant
Treatment Applied at Entry Point
El feet iw
: 1/31/93
Release Number:
Pane: VI -
61
-------
Code Value
Section VI. .Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03, Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
0121
0125
0141
0143
0145
0147
0149
0160
0240
0300
0345
0360
0403
0423
0543
0560
0580
0620
0640
0660
0742
Or games Removal
Treatment Processes
Activated Carbon. Granular
Activated Carbon, Powdered
Aeration1! Cascade
Aeration* Diffused
Aeration. Packed Tower
Aeration. Slat Tray
Aeration. Spray
Algae Control
Coagulation
Distillation
Filtration. Rapid Sand
Flocculation
Gaseous Chlorination, Pre
Hypochlorination, Pre
Ozonation. Pre
Permanganate
Peroxide
Reducing Agents
Reverse Osmosis
Sedimentation
pH Adjustment, Pre
This table contains valid combinations
of values for data elements C483 S C485
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective Date: 1/31/93
Release Number: 2.00
Pone: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003• Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
P240-
P300
P341
P34Z
P344
P345
P346
P347
P348
P360
P520
P600
P660
P700
P742
Participate Removal
Treatment Processes
Coagulation
Distillation
Filtration. Cartridge
Filtration. Diatomaceous Earth
Filtrationi Pressure Sand
Filtration. Rapid Sand
Filtration. Slow Sand
Filtration. Ultrafiltration
Filtered
Flocculation
Microscreening
Rapid Mix
Sedimentation
Sludge Treatment
pH Adjustment. Pre
This table contains valid combinations
of values for data elements C4fl3 t C465
Pos. 1 = C4B3
Pos. 2 - 4 = C465
Effective
1/31/93
Release Number: 2
Paae: VI -
63
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003, Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
R100
R121
RI4I
R143
R145
R147
R149
R180
R240
R300
R320
R344
R345
R360
R460
R500
R600
R640
R660
R660
R700
R742
Radionuclides Removal
Treatment Processes
Activated Alumina
Activated Carbon. Granular
Aeration, Cascade
Aeration> Diffused
Aeration• Packed Tower
Aeration, Slat Tray
Aeration, Spray
Bone Char
Coagulation
Distillation
Electrodialysi*
Filtration* Pressure Sand
Filtration. Rapid Sand
Flocculation
Ion Exchange
Lime - Soda Ash Addition
Rapid Mix
Reverse Osmosis
Sedimentation
Sequestration
Sludge Treatment
pH Adjustmenti Pre
This table contains valid combinations
of values for data elements C483 S C485
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective Datei 1/31/93
Release Number: 2.00
Paaei VZ -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03i Combined Treatment Objective and Treatment Process Codes
Associated Description Comment! s»
5240
3300
'S344
3345
S360
S460
S500
5600
3640
S660
3660
3700
3742
Softening (Hardness Removal)
Treatment Processes
Coagulation
Distillation
Filtration. Pressure Sand
Filtration. Rapid Sand
Flocculation
Ion Exchange
Lime - Soda Ash Addition
Rapid Mix
Reverse Osmosis
Sedimentation
Sequestration
Sludge Treatment
pH Adjustment, Pre
This table contains valid combinations
of values for data elements C483 t C4A5
Pos. 1 = C483
PCS. 2 - 4 = C485
Effectiv
1/31/93
Release Number: 9 ~"
Paws: VI -
65
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
T1Z1
TI25
T141
T143
T145
T149
T160
T403
T423
T543
T560
T580
Taste / Odor Control
Treatment Processes
Activated Carbon* Granular
Activated Carbon. Powdered
Aerations Cascade
Aerationi Diffused
Aeration* Packed Tower
Aerationi Slat Tray
Aeration. Spray
Algae Control
Gaseous Chlorination. Pre
Hypochlorination. Pre
Ozonation. Pre
Permanganate
Peroxide
This table contains valid combinations
of values for data elements C463 * C4S5
Pos. 1 = C463
Pos. 2 - <» = C465
Effective Date: 1/31/93
Release Number: 2.00
Page: VI -
66
-------
Code Value
Section VI. Lists of Aceepiable Code Values uith Associated Descriptions
C. Detailed Lists of Code Values
Table -1003. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
X001
Treatment Unknown
Treatment Processes
(Converted FRDS 1.5)
Treatnent Not Reported
This table contains valid combinations
of values for data elements C4B3 t C465
Pos. 1 = M61
Pos. 2 - 4 = C4B5
•X0011 may not be used on any FRDS-II
input transaction. It Mas assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
Effectiv
e: 1/31/93
Release Number:
Paoe: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03. Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
Y081
Y082
Y063
YOB4
Y085
Y086
Y087
Y088
Treated
Treatment Processes
(Converted FRDS 1.5)
Aeration (Converted FRDS 1.5)
Prechlorination (Converted FRDS 1.5)
Coagulation (Converted FRDS 1.5)
Sedimentation (Converted FRDS 1.5)
Filtration (Converted FRDS 1.5)
Corrosion Control (Converted FROS 1.5)
Softening (Converted FRDS 1.5)
Taste / Odor Control*Converted FRDS 1.5)
This table contains valid combinations
of values for data elements C483 » C485
Pos. 1 = C483
Pos. 2 - * = C48S
•YOB1' nay not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y0821 may not be used on any FRDS-II
input transaction. It Mas assigned by
the FRDS-II computer system during the
conversion of data from FROS 1.5 to
FRDS-II.
•Y0831 may not be used on any FRDS-II
input transaction. It Mas assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y0841 may not be used on any FRDS-II
input transaction. It MBS assigned by
the FROS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•YOBS' may not be used on any FRDS-II
input transaction. It Mas assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y086' may not be used on any FRDS-II
input transaction. It Mas assigned by
the FROS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y087' may not be used on any FRDS-II
input transaction. It MBS assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y088* may not be used on any FRDS-II
input transaction. It Mas assigned by
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
68
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1003, Combined Treatment Objective and Treatment Process Codes
Associated Description Comment(s)
Y088
Y089
Y090
Y091
Y092
Y093
Note: This list begins on VI - 68
Treated
Treatment Processes
(Converted FRDS 1.5)
Previous page is continued on next line
Iron Removal (Converted FRDS 1.5)
Automation (Converted FRDS 1.5)
Fluoride Adjustment IConverted FROS 1.5)
Disinfection (Converted FRDS 1.5)
Other Treatment (Converted FRDS 1.5)
This table contains valid combinations
of values for data elements C483 I C485
Pos. 1 = C483
Pos. 2 - 4 = C485
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
'Y089* may not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y090' nay not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FROS 1.5 to
FRDS-II.
•Y091* may not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•Y0921 may not be used on any FRDS-II
input limuabliuii. It w» Maigiied by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRuS-11.
•Y093' nay not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
Effectiv
«: 1/31/93
Release Number:
Paoe: VI -
69
-------
Coda Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID03» Combined Treatment Objective and Treatment Process Codes
Associated Description Comment!s)
Z3SO
Other
Treatment Procc
Fluoridation
This table contains valid combinations
of values for data elements C483 I C485
Pos. 1 = C483
Pos. 2 - 4 = C485
Effective Date: 1/31/93
Release Number: 2.00
Page: VI -
70
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 1004> Treatment Process Codes
Associated Description
Comment!s)
000
001
081
082
003
084
065
086
No Treatment / Not Applicable
Treatment Not Reported (Converted 1.51
Aeration {Converted PROS 1.5)
Prechlorination (Converted FRDS 1.5)
Coagulation (Converted FRDS 1.5)
Sedimentation (Converted FRDS 1.51
Filtration (Converted FRDS 1.5)
Corrosion Control (Converted FRDS 1.5)
See Table ID03 for valid combinations
of these codes in conjunction with
Treatment Objective (C463) codes
'001' nay not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•0811 nay not be used on any FRDS-IX
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•08Z1 nay not be used on any FRDS-II
input transaction. It Mas assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
'083* nay not be used on any FRDS-II
input transaction. It MBS assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FROS-II.
,'084' nay not be used on any FRDS-II
input transaction. It Has assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
•085' may not be used on any FROS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of date from FRDS 1.5 to
FRDS-IX.
'086' nay not be used on any FRDS-II
input transaction. It Has assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FRDS-II.
Effective
V 1/31/93
Release Number:
Peoe: VI -
71
-------
Section .VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID04, Treatment Process Codes
Associated Description
Commentls)
067
068
069
090
091
092
093
100
Effective Date: 1/31/93
Note: This list begins on VI - 71
Softening (Converted PROS 1.5)
Taste / Odor ControKConverted PROS 1.5)
Iron Removal (Converted PROS 1.5)
Ammoniation (Converted FRD3 1.5)
Fluoride Adjustment (Converted PROS 1.5)
Disinfection (Converted PROS 1.5)
Other Treatment (Converted PROS 1.5)
See Table 1003 for valid combinations
of these codes in conjunction with
Treatment Objective (C483) codes
•087* may not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
•086' cay not be used on any PRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
•089' may not be used on any FRDS-II
input transaction. It MBS assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
•090* may not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
'091' may not be used on any FRDS-II
input transaction. It was assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
•092' may not be used en any FRDS-II
input transaction. It MBS assigned by
the FROS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
'093' may not be used on any FROS-II
input transaction. It Has assigned by
the FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
Activated Alumina
Release Number: 2.00
Pane: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values Mith Associated Descriptions
C. Detailed Lists of Coda Values
Table ID04, Treatment Process Codes
Associated Description
Comment!s)
121
125
141
145
147
149
160
160
190
200
220
240
300
320
341
342
343
344
345
346
347
348
349
350
351
360
380
401
403
421
423
441
443
445
Note: This list begins on VI - 71
Activated Carbon* Granular
Activated Carboni Powdered
Aeration* Cascade
Aerationt Diffused
Aerationi Packed Tower
Aeration, Slat Tray
Aerationi Spray
Algae Control
Bone Char
Brominization (Special Use)
Chloramines
Chlorine Dioxide
Coagulation
Distillation
Electrodialysis
Filtration, Cartridge
Filtration, Diatomaceous Earth
Filtration, Greensand
Filtration, Pressure Sand
Filtration, Rapid Sand
Filtration, Slow Sand
Filtration. Ultrafiltration
Filtered
Unfiltcredi Avoiding Filtration
Unfiltered, Must Install Filtration
Not Subject to SNTR
Flocculation
Fluoridation
Gaseous Chlorination, Post
Gaseous Chlorination, Pre
Hypochlorination, Post
Hypochlorination, Pre
Inhibitor, Bimetallic Phosphate
Inhibitor, ~Hexometaphosphate
Inhibitor, Orthophosphate
See Table 1003 for valid combinations
of these codes in conjunction with
Treatment Objective (C483I codes
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
73
-------
Section VI. Lilts of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 1004, Treatment Process Codes
Associated Description
Comment! s)
447
449
455
460
500
520
541
543
560
580
600
620
623
625
627
640
660
680
700
720
740
741
742
996
997
998
Note: This list begins on VI - 71
Inhibitor. Polyphosphate
Inhibitor. Silicate
Iodine
Ion Exchange
Lime - Soda Ash Addition
nicroscreening
Ozonetioni Post
Ozonation. Pre
Permanganate
Peroxide
Rapid Hix
Reducing Agents
See Table ID03 for valid combinations
of these codes in conjunction with
Treatment Objective IC483) codes
Reducing Agent>
Reducing Agent.
Reducing Agent.
Reverse Osmosis
Sodium Bisulfate
Sodium Sulfite
Sulfur Dioxide
Sedimentation
Sequestration
Sludge Treatment
Ultraviolet Radiation
pH Adjustment
pH Adjustment. Post
pH Adjustment. Pre
Treatment Applied by Seller
Treatment Applied at.Plant
Treatment Applied at Entry Point
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
73.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table IDG5> Treatment Objective Codes
Associated Description
Comment! a)
Sea Table 1003 for valid combinations
of these codes in conjunction HIth
Treatment Process (C485) codes
A
B
C
0
E
F
I
M
N
0
P
R
S
T
Additional Treatment Elsewhere
Disinfection By-products Control
Corrosion Control
Disinfection
Dechlorination
Iron Removal
Inorganics Removal
Manganese Removal
Ho Treatment at Source
Organics Removal
Participate Removal
Padionuclides Removal
Softening (Hardness Removal)
Taste / Odor Control
Treatment Unknown (Converted PROS 1.5)
Treated (Converted PROS 1.5)
Other
'X1 may not be used on any FRDS-II input
transaction. It Mas assigned by the
FRDS-II computer system during the
conversion of date from FRDS 1.5 to
FRDS-II.
'V may not be used on any FRDS-IZ input
transaction. It Mas assigned by the
FRDS-II computer system during the
cpnvftrjiinn nf riata frnm FBtlS I.S to
FRDS-II.
Effective
1/31/93
Release Number: ?
Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06, Contaminant Identification Codes
Associated Description
Comment! s)
GRNO
Non-compliance Profile Related
All Contaminants
Alsot see 1 » 2 • « *
(listed subsequently I for other
NCR related codes
GRND is used in FRDS-II NCP records
to identify a summary containing all
violation and enforcement counts for
all contaminants and periods of tine
for each PWS having a violation or
enforcement.
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
75
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06t Contaminant Identification Codes
Code Value Associated Description Commentls)
Physical Contaminants Regulated Monitoring Only
-R- -M-
0100 Turbidity R
Effective >: 1/31/93 Release Number: ? P»oe: VI - 75.5
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06, Contaminant Identification Codes
Associated Description Comment(s)
!*««
Inorganic Contaminants
All NIPDHR Inorganic Contaminants
Regulated
-R-
Monitoring Only
-M-
!*»• may be used for MIR violations
which occurred before 1/1/93 ONLY
Group Contaminant Codes may not be used
after 12/31/92
!»»» includes Arsenic. Barium* Cadmium.
Chromium, Fluoride, Lead, Mercury,
Nitrate, Selenium, and Silver
1—
All Inorganic Contaminants
1 is used in FRDS-II NCP records
to identify a summary containing all
Inorganic violation and enforcement
counts for a given window of time
in which a PWS hod a violation or
enforcement .•
1002
1003
1005
1006
1007
1006
1009
1010
1012
1015
1016
1017
1018
1020
1021
1022
1024
1025
1026
1027
1020
1029
Aluminum
Nitrogen-Ammonia as (N)
Arsenic
Chloranine
Chlorate
Chlorine Dioxide
Chlorite
Barium
Residual Chlorine
Cadmium
Calciun
Chloride
Carbon* Total
Chromium
Hydroxide as Calciun Carbonate
Copper
Cyanide
Fluorids.
Bicarbonate as HC03
Hydrogen Sulfide
Iron
Iron, Suspended
R
R
R
R
R
Effective Date: 1/31/93
Release Number* 2.00
Pace: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06, Contaminant Identification Codes
Code Value Associated Description Comment(s)
Note: This list begins on VI - 76
Inorganic Contaminants Regulated Monitoring Only
-R- -M-
1030 Lead R
1031 Magnesium
1032 Manganese
1033 Manganesei Suspended
1035 Mercury R
1036 Nickel R
1037 Total Kjeldahl Nitrogen (in Hater ng/1)
1038 Nitrate-Nitrite
1040 Nitrate R
1041 Nitrite R
1042 Potassium
1043 Phosphatei Total
1044 Orthophosphate
1045 Selenium R
1049 Silica
1050 Silver
1051 Strontium
1052 Sodium M
1055 Sulfate 1
1057 Residuei Total• Filterable
1050 Residue^ Filterable-Volatile
1059 Residuei Filterable-Fixed
1060 Residue. Total-Volatile
1061 Residue, Total-Fixed
1063 Residuei Nonfilterable-Fixed
1064 Conductivity 9 25 C U-HHO
1066 pH, CaCOS Stability S.U.
1067 Alkalinity CeC03, Stabl
1068 Acidity Total. CaC03
1C69 Acidity M.O., CaC03
1070 Residue. Total
1071 Residue. S«ttleable (by Height I
1072 Phosphorus Sol
1073 Phosphate.-Reactive
1074 Antimony. Total R
1075 Beryllium, Total R
Effecti» %e: 1/31/93 Release Number: Paoe: VI - 76.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions ,
C. Detailed Lists of Code Values
Table ID06» Contaminant Identification Codes
Code Value Associated Description Comment(s)
Note: This list begins on VI - 76
Inorganic Contaninants Regulated Monitoring Only
-B- -M-
1076 COD mg/1
1077 Residue. Nonfilterable. Volatile
1078 Bismuth, Total
1079 Boron. Total
1080 Chromium, Hex
1061 Cobalt. Total
1062 Iron. Dissolved
1063 Lithium, Total
1064 Molybdenum, Total
1065 Thallium. Total R
1086 Tin. Total
1087 Titanium, Total
1088 Vanadium. Total
1069 MBAS
1090 Oil-Grease. Total
1091 BOD. 5-Day mg/1
1093 TOD mg/1
1093 Phosphorus, Total
1094 Asbestos R
1095 Zinc
1901 Carbon Dioxide
1905 Color
1910 Corrosivity
1915 Hardness. Total (as CaC03) M
1916 Hardness. Carbonate
1917 Hardness, Noncarbonate
1918 Hardness. Calcium Magnesium
1919 Calcium
1920 Odor
1925 pH M
1927 Alkalinity, Total M
1928 Alkalinity,-Bicarbonate
1929 Alkalinity, Carbonate
1930 Total Dissolved Solids (TDS) M
1931 Alkalinity, Phenolphtalein
1993 Stability Index
Effective Date: 1/31/93 Release Number: 2.00 • Paoe: VI - 77
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Valua
Table ID06, Contaminant Identification Codes
Associated Description
Comment! s)
199*
1995
1996
1997
1998
1999
Note: This list begins on VI - 76
Inorganic Contaminants
Aggressive Index
Scale Forming
Temperature (Centigrade)
Langelier Index (PHS)
Saturation Index
Note: (Reserved by MSIS)
Regulated Monitoring Only
-R- -fl-
H
M
Effectiv
«: 1/31/93
Release Number:
Paae: VI -
77.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06, Contaalnant Identification Codes
Associated Description
Connent(s)
2***
Organic Contaminants
All NIPDUR Organic Contaminants
Regulated
-R-
Honltorlng Only
-N-
2*** My be used for HSR violations
which occurred before 1/1/93 ONLY
Croup Contanlnant Codes nay not be used
after 12/31/92
2*** Includes Endrlnj Llndane;
Hethoxychlor; Tozaphene; 2,4-D;
and 2,4-TP (Sllvex)
2—
All Organic Contaminants
2— is used in FRDS-II NCP records
to Identify a summary containing all
Organic violation and enforcement
counts for a given window of tine
In which a PVS had a violation or
enforcement.
2A01
2A02
2A03
2A04
2AOS
2A06
2A07
2AOB
2A09
Casollne
ff2 Fuel Oil
Jet Fuel
«4 Fuel Oil
K$ Fuel Oil
Motor Oil
Submersible
Varsol
Propane
Pump Oil
2U1S
IS Unregulated Phase I VOCs
2D1S may be used for M&R violations
which occurred before 1/1/93 ONLY
Croup Contaminant Codes may not be used
after 12/31/92
During early 1994, each occurrence of
201S In the data base will be replaced
with IS individual M&R violations
M&R violations
2U34
34 Unregulated Phase I VOCs
2U34 may be used for M&R violations
Effectlv
1/31/93
Release Humbert
Page: VF -
78
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06, Contaminant Identification Codes
Associated Description
Comment(s)
2U34
Notei This list begins on VI - 78
Organic Contaminants
Previous page is continued on next line
Regulated
-R-
Honitoring Only
-H-
which occurred before 1/1/93 ONLY
Croup Contaminant Codes may not be used
after 12/31/92
During early 1994, each occurrence of
2034 In the data base will be replaced
with 34 individual H&R violations
H&R violations
2036
36 Unregulated Phase I VOCs
2U36 «ay be used for H&R violations
which occurred before 1/1/93 ONLY
Croup Contaminant Codes nay not be used
after 12/31/92
During early 1994, each occurrence of
2D36 In the data base will be replaced
with 36 Individual H&R violations
H&R violations
2V07
7 Regulated Phase I VOCs
2V07 say be used for H&R violations
which occurred before 1/1/93 ONLY
Croup Contaminant Codes may not be used
after 12/31/92
During early 1994, each occurrence of
2V07 In the data base will be replaced
with 7 individual H&R violations
violations
2V08
8 Regulated Phase I VOCs
2V08 may be used for H&R violations
which occurred before 1/1/93 ONLY
Croup Contaminant Codes may not be used
after 12/31/92
During early 1994, each occurrence of
Effective Date, 1/31/93
Release Number: 2.00
Page: VI -
78.5
-------
Code Value
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06i Contaminant Identification Codes
Associated Description
Comment! s)
2V08
2005
2010
2015
2020
2021
2022
2030
2031
2032
2033
2034
2035
2036
2037
203P
2039
2040
2041
2042
2043
2044
2045
2046
2047
2046
2049
2050
2051
2052
2053
2054
2055
Note: This list begins on VI - 78
Organic Contaminants
Previous page is continued on next line
Endrin
BHC-gamma (Lindane)
Methoxychlor
Toxaphene
Carbaryl
Kethomyl
P-Isopropyltoluene (P-Cymene)
Dalapon
Diquat
Endotholl
Glyphosate
Di (2-EthyIhexyl) Adipate
Oxamyl (Vydate)
Simazine
PAH's
Di (2-EthyIhexyl) Phthalate
Piclornra
Dinoaeb
Hexachloroeyclopentadi ene
Aldicarb'Sulfoxide
Aldicarb Sulfone
Metolachlor
Carbofuran
Aldicarb
Hypochlorite Ion
1,4-Dioxane
Atrazine
Alachlor (basso)
EPTC (Eptan)
Butylate (Sutan)
Cyanazine (Bladex)
Trifluralin
Regulated
-R-
Monitoring Only
-M-
2V08 in the data base will be replaced
with 8 individual M»R violations
violations
R
R
R
R
n
n
H
R
R
R
R
R
R
R
R
R
H
n
R
R
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
79
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06, Contaminant Identification Codes
Associated Description
Comment!s)
2056
2057
2 OSS
2059
2060
2061
2062
2063
2064
2065
2066
2067
2068
2069
2070
2071
2072
2073
2074
2075
2076
2077
2070
2079
2080
2081
2082
2083
2084
2085
2086
2087
2088
2089
2090
2091
Note: This list begins on VI - 78
Organic Contaminants
Diazinon (Spectracide)
Lorsban (Cholropyri foa)
Malathion
Azinphos-Methyl (Guthion)
Isofenphos (Oflanoll
Trithion
Ethion
2,3,7,8-TCDD (Dioxinl
Parathion (Ethyl)
Heptachlor
3-Hydroxycarbofuran
Heptachlor Epoxide
Endosulfan 1
para-para DDE
Dieldrin
para-para ODD
Endosulfan II
Phosdrin
Endosulfan Sulfate
para-para DDT
Butachlor (Machete)
Propachlor (Ramrod)
Cryptosporidium
Dihromoacetuiii Iri le
Cyanogen Chloride
Amyl Acetate
Butane
Butyl Acetate
n-Butyl Alcohol
sec-Butyl Alcohol
1-Chlorobutane
1-Chlorohexane
Ethyl Acetate
Ethyl Alcohol
Ethyl Ether *
Iso-Octane
Regulated
-R-
Monitoring Only
-M-
H
n
Effectiv ' te: 1/31/93
Release Number:
Pane: VI -
79.5
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06. Contaminant Identification Codes
Associated Description
Comment(s)
2092
2093
2094
2095
2105
2110
2111
2200
2201
2202
2203
2204
2210
2212
2214
2216
2216
2219
2222
2223
2224
2225
2226
2227
2226
2229
2230
2231
2232
2233
2234
2235
2236
2237
2236
Note: This list begins on VI - 76
Organic Contaminants
Isobutyl Acetate
Isobutyl Alcohol
Isopropyl Acetate
Isopropyl Alcohol
2.4-0
2.4,5-TP (Silvex)
2,4,5-T
2-Nitrosniline
3-Nitroaniline
Dibenzofuran
4-Nitroaniline
Azobenzene
Methylchloride (Chloroemethane)
Dichlorodifluoromethane
Bromonethane
Chloroethane
Tr i chlorofluoromethane
(Fluorot r i chloromethane)
Tri chloroacetonitr ile
bis (2-Chloroethyl) Ether
Di-N-Octylphthelata
trans-1i3-Dichloropropene
Hexachloroethane
trans-1i2-Dichloropropene
2-Methyl-4,6-Dinitrophenol
cis-1>3-Dichloropropene
n-Ni trosodiphenylamine
Aniline
Benzyl Alcohol
1,2-Dibromoethylene
2-Methylphenol
2-Chloroethy.lvinyl Ether
4-Methylphenol
Di iodonethane
Benzoic Acid
Acrolein
Regulated
-R-
Monitortng Only
-M-
R
R
n
M
n
n
Effective Date: 1/31/93
Release Number: 2.00
Page: VI -
60
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06» Contaminant Identification Codes
Associated Description
Comment(s)
2239
2240
2241
2242
2243
2244
2245
2246
2247
2248
2249
2250
2251
2254
2257
2250
2260
2261
2262
2263
2264
2265
2266
2266
2270
2274
2276
2270
2200
2262
2264
2266
2286
2290
2292
2294
Note: This list begins on VI - 78
Organic Contaminants
4-Chloroaniline
Acrylonitrile
2-tlethyl Naphthalene
2i4i5-Trichlorophenol
Acetone
bis (2-Chloroisopropyl) Ether
Isopropyl Ether
Hexachlorobutadi ene
Methyl Ethyl Ketone
Naphthalene
Methyl Isobutyl Ketone
bis (2-Chloroethoxy) Methane
Methyl-Tert-Butyl-Ether
Nitrobenzene
Epichlorohydrin
2-Chloronaphthalene
Acenaphthylene
Acenaphthene
Isophorone
Tetrahydrofuran
Fluorene
Aerylaoide
2t6-Dinitrotoluena
112-0 i phenylhydrazi ne
2,4-Dinitrotoluene
Hexachlorobenzene (HCB)'
4-Bromophenyl Phenyl Ether
Phenanthrena
Anthracene
Dirnethylphthalate
Diethylphthalate
Fluoronthene
Pyrene
Di-N-Butylphthalete
Benzidine
Butyl Benzylphthalate
Regulated
-R-
Monitoring Only
-M-
M
M
Has Treatment Technique Requirement
•Has Treatment Technique Requirement
Effectiv
«: 1/31/93
Release Number:
Paae: VI -
60.5
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06, Contaminant Identification Codes
Associated Description
Comment!s)
2295
2296
2298
2300
2302
2304
2306
2308
2310
2312
2314
2316
2318
2320
2324
2325
23Z6
2327
2326
2330
2332
2334
2336
2340
2342
2344
2346
2348
2350
2354
2356
2365
2367
2369
2370
2371
Note: This list .begins on VI - 78
Organic Contaminants
Methyl Methacrylate
Chrysene
bis (2-Cthylhexyll Phthalate
Benzo (A) Anthracene
Benzo (Bl Fluoranthene
Benzo IK) Fluoranthene
Benzo (A) Pyrene
Ideno (1,2,3-Cd) Pyrene
Dibenzo (A.H) Anthracene
Benzo (G.HiI) Perylene
n-Nitrosodimethylamine
n-Ni trosodi-N-Propylamene
4-Chloro-Phenyl-Phenyl Ether
3i3-Dichlorobenzidine
bis (Chloronethyll Ether
Pentana
Pentachlorophenol
Pentachloroethane
2.4-Dinitrophenol
p-Chloro-H-Cresol
2 > 4 > 6-Tri chlorophenol
2i4-Dichlorophenol
2.4-Dinethylphenol
2-Ni trophenol
4-Nitrophenol
2-Chlorophenol
4,6-Dinitro-O-Cresol
elpha-BHC
beta-BKC
delta-BHC
Aldrin
ortho-para JDDE
ortho-para ODD
ortho-para DDT
Kelthane (Dicofal)
Tedion
Regulated
-R-
Monitoring Only
-tl-
Effective Date: 1/31/93
Release Number; 2.00
Paemi VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06i Contaminant Identification Codes
Associated Description Comment(s)
3372
2374
2376
2370
2380
2383
2304
2388
2390
2392
2394
2396
2398
2399
2400
2401
2408
2410
2412
2413
2414
2416
2418
2420
2422
2424
2426
2428
2430
2440
2441
2442
2443
2444
2445
2446
Note: This list begins on VI - 78
Organic Contaminants
Endrin Aldehyde
Kerosene
n-Hexene'
1 1 2 • 4-Tr i chlorobenzerM
cis-l,2-Dichloroethylene
Total Polychlorinated Biphenyls (PCB)
Dechlorobi pheny 1
Aroclor 1016
Aroelor 1221
Aroclor 1232
Aroclor 1242
Aroclor 1248
Aroelor 1254
PCB 1262
Aroelor 1260
Total Dichlorobenzenes
D i br omomethane
1 , 1 -D i chloropropene
1 .3-Dichloropropane
1 • 3-D i chloropropene
1 1 2 > 3-Tr i chloropropene
2 • 2-0 i chloropropene
| t?r4-Trimathylnf»nrpnit
1 1 Z 1 3- 1 r i chlorobenzene
n-Butylbenzene
l,3i5-TrimethylbenzerM
ter t -Butylbenzene
sec-Butylbenzene
Bromochloromethane
Dicanba
Methane
Methyl Acetate
Methyl Alcohol
Methyl Cellosolve
Propyl Acetate
n-Propyl Aleohol
Regulated Monitoring Only
-R- -M-
R
R
R
M
M
M
M
M
M
H
M
M
M
M
M
M
M
Effective
1/31/93
Release Number: f
Paoe: VI -
81.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06. Contaminant Identification Codes
Associated Description
Comment! s)
2447
25ZO
2545
2570
2590
2595
2605
2615
2620
2635
2650
2655
2904
2905
2910
2920
2930
2931
2932
2940
2941
2942
2943
2944
2946
2949
2950
2955
2959
2960
2961
2962
2964
2965
2966
Note: This list begins on VI - 70
Organic Contaminants
Vinyl Acetate
Vinyl 2 Chloroethyl Ether
Counter (Terbufos)
Dyfonat*
Mocap
Metribuzin (Sencor)
Phorata (Thinat)
Prowl
Ami ben
dolstar
Dichlorethylenat Total
1 t3-Dichloropropylen«i Total
Trichlorotrifluoroethane (Freon 113)
Foaming Agents C Surfactants)
Phenols
Carbon i Total-Organic
Kepono ,
Ii2 Dibromo-3-Chloropropane (DBCP)
Mi rex
HMPA
Chloroform
Bromoform
Brornodi chloromethane
Dibromochlorome thane
( Chlorodi bromoaethane )
Ethylene D? bromide (.E.DB)
Maximum Total Trihalomethane Potential
TTHH
Xylenes, Total
Chlordane
Ethylene Glycol
Formaldehyde
p-Xylene
Methylcne Chloride IDi chloromethane)
o-Chlorotoluena
p-Chlorotoluene
Regulated Monitoring Only
-R- -M-
M
R
H
H
M
M
R
R
R
R
R
H
M
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Coda Value
Table ID06i Contaminant Identification Codes
Associated Description
Comment!s)
2967
2968
2969
2975
2976
2977
2978
2979
2900
2961
29BZ
2903
2984
2965
2986
2987
2988
2989
2990
2991
2992
2993
2994
2995
2996
2997
299S
2999
Note: This list begins on VI - 78
Organic Contaminants
•-D i chlorobenzene
o-D i chl orobenzene
p-D i chlorobanzene
Dichloroiodomethane
Vinyl Chloride
1 f 1 -D i chloroe thylene
1 » 1 -Di chloroe thane
•trans-1 > 2-0 i chloroe thylene
1 1 2 -0 i chloroethane
1 1 1 • 1 -Tr i chloroethane
Carbon Tetrechloride
1 1 2 -0 i chloropropane
Trichloroethylene
1 » 1 . 2-Tr i chloroe thane
1 > 1 > 1 i 2-Tetrachloroethane
Tetrachloroethylene
1 • 1 ,2,2-Tctr»chloro«thane
Monochlorobenzena ( Chlorobenzene 1
Benzene
Toluene
Ethylbenzenfl
Bromobenzene
Isopropylbenzene
m-Xylene
Styrene
e-Xylene
n-Propylbenzene
Note: (Reserved by HSIS)
Regulated Monitoring Only
-R- -M-
M
R
R
R
R
M
R
R
R
R
R
R
R
M
R
n
R
R
R
R
M
M
R
M
Effective P '-: 1/31/93
Release Number: 2.
Page: VI -
62.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table ID06, Contaminant Identification Codes
Code Value Associated Description Comment!s)
Bacteriological Contaminants Regulated Monitoring Only
-R- -M-
3000 Col i form (Pre-TCR)
3001 Heterotrophic Bacteria (HPC or SPC)
3002 Enterococci /100 ml
3003 Fecal Streptococcus
3004 Staphylocoecin
3005 Non-col5form Growth Identification
3006 Iron Bacteria Id
3007 Salmonella-Shigella
3008 Giardia Lamblia
3009 Fungus /ml
3010 Virus PFU/gal
3011 Actinonycetes /ml
3012 Legionella
3013 Fecal Col if oral
3100 Coliform (TCR)
Effective Date: 1X31/93 Release Number: 2.00 Paae: VI - 83
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1006, Contaminant Identification Codes
Associated Description Comment(s)
Radiological Contaminants
All Radiological Contaminants
Regulated
-R-
Monitoring Only
-M-
4— is used in FRDS-II NCP records
to identify a summary containing all
Radiological violation and enforcement
counts for a given window of time
in which a PHS had a violation or
enforcement.
4000
4002
4004
4006
4007
4008
4009
4010
4012
4020
4030
4040
4041
4042
4043
4044
4100
4101
4102
4104
4106
4108
4109
4110
4112
4114
4116
4118
4120
4122
4124
Gross Alpha. Excl. Radon ft U
Gross Alpha. Incl. Radon i U
Radon
Combined Uranium"
Uraniun-234
Uraniun-235
Urantua-238
Combined Radium (-226 I -228)
Photon Emitters
Radium-226
Radium-228
Alphai Dissolved
Alphai Suspended
Betai Dissolved
Betai Suspended
Potassium-40i Total
Gross Beta Particle Activity
Han-Made Beta Particle ft Photon Emitters
Tritiua
4-Berylliu!n-7
4-Beryllium-10
6-Carbon-14
Gross Alpha Particle Activity
ll-Sodium-22
lS-Phosphorus-32
16-Sulfur-35
17-Chlorine-36
20-Calcium-45
20-Calcium-47
21-Scandium-46
21-Scandium-47
Effectivr
1/31/93
Release Number:
Paqe: VI -
84
-------
Section.VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06f Contaminant Identification Codes
Associated Description
Comment! s)
4126
4128
4130
4132
4134
4136
4138
4140
4142
4144
4146
4148
4150
4152
4154
4156
4158
4160
4162
4164
4166
4168
4170
4172
4174
4176
4178
4180
4182
4184
4166
4188
4190
4192
4194
4196
Note: This list begins on VI - 84
Radiological Contaminants Regulated Monitoring Only
-R- -M-
21-Scandium-48
23-Vanodiun-48
24-Chromlum-51
25-Manganese-54
26-Iron-55
26-Iron-59
27-Cobalt-57
27-Cobalt-58
27-Cobolt-60
Zfl-Nickel-59
28-NicKel-63
30-2inc-65
32-Seponium-71
33-Arscnic-73
33-Arsenic-74
33-Arsenic-76
33-Arsenic-77
34-Seleniun-75
34-Selenium-79
35-BroDide-62
37-Rubidium-86
37-Rubidium-e?
38-Strontium-B5
3B-Strontium-89 "
38-Strontiun-90 M
39-Vttriun-90
39-Yttriun-91
39-Yttrium-91M
40-Zirconiun-93
40-Zirconium-95
41-Niobiun-93
41-Niobiura-95
42-riolybdenum-93
42-Molybdenum-99
43-Technetium-96
43-Technetium-97M
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI - 84.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID06, Contaminant Identification Codes
Associated Description
Comment! s)
4198
4200
4202
4204
4Z06
4208
4210
4212
4214
4216
4216
4220
4222
4224
4226
4228
4230
4232
4234
4236
4236
4240
4242
4244
4246
4246
4250
4252
4254
4256
4256
4260
4262
4264
4266
4270
Note: This list begins on VI - 84'
Radiological Contaminants Regulated Monitoring Only
-R- -M-
43-Technetium-97
43-Technetium-99
43-Technetium-99M
44-Rutheniun-97
44-Ruthenium-103
44-Rutheniun-106
45-Rhodium-105
46-Palladium-103
46-Palladiun-107
47-Silver-10SM
47-Silver-110M
47-Silver-110
47-Silver-lll
46-Cadniun-109
48-Cadmun-113N
48-Cadniua-115n
46-Cadnium-115
49-Indium-115
50-Tin-113
50-Tin-123
50-Tin-125
51 -Antimony- 122
51-Antimony-124
51-Antinony-125
51-Antimony-127
52-Tellurium-125H
52-T«lluriura-127M
52-Tellurium-127
52-Tellurium-129M
52-Tellurium-129
52-Tellurium-132
53-Iodine-126
53-Iodine-129
53-Iodine-131 "
55-Cesium-13[
55-Cesium-134 H
Effective
1/31/93
Release Number: ?
Paoe: VI -
65
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 1006. Contaminant Identification Codes
Associated Description
Comment! s)
4272
4274
4276
4278
4260
4282
4284
4286
4268
4290
4292
4294
4296
4298
4300
4302
4304
4306
4308
4310
4312
4314
4316
4318
4320
4322
4324
4326
4326
4330
4332
4334
4336
4338
4340
4342
Note: This list begins on VI - 84
Radiological Contaminants Regulated Monitoring Only
-R- -H-
55-Cesium-135
55-Cesium-136
55-Cesiun-137
56-Bariun-140
57-Lanthanum-140
58-Cerium-141
58-Cerium-143
58-Cer Jura- 144
56-Praseodynium-143
60-Neodyniun-147
61-Pronethium-147
61-Procethium-148
61-Promethium-148M
61-Proaethiun-149
62-Samarium-151
62-Samoriun-153
63-Europiun-152
63-Europium-154
63-Europium-155
63-Europium-156
64-Gadolium-153
65-Terbiun-160
66-Dysprosium-166
67-Holaium-166
67-Holniura-166M
68-Erbium-169
69-Thulium-170
69-Thulium-171
70-Ytterbium-175
71-Lutetium-177
72-Hafnium-181
73-Tantalura--162
74-Tungsten-181
74-Tungsten-ie5
74-Tungsten-187
75-Rheniun-183
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
65.5
-------
Code Value
Section VI. Lists of Acceptable Code Values uith Associated Descriptions
C. Detailed Lists of Code Values
Table ID06( Contaminant Identification Codes
Associated Description
Comment! s)
4344
4346
4348
4350
4952
4354
4356
4358
4360
4362
4364
4366
4366
4370
4372
4374
4376
4376
4380
4382
4999
Note: This list begins on VI - 84
Radiological Contaminants
75-Rhenium-186
75-Rhenium-167
76-Osmiunf-185
76-usmiun-191
76-Osmium-193
77-Iridium-190
77-Iridium-192
78-Platinum-191
76-Platinum-193M
78-Platinun-193
79-6old-196
79-Gold-198
81-Thallium-204
82-Lead-203
82-Lead-ZlO
83-Bismuth-206
63-Bisinuth-207
83-Bismuth-210
64-Poloniuo-210
91-Protactinium-233
Note: (Reserved by MSIS)
Regulated
-R-
Honitoring Only
-M-
Effeetivr
1/31/93
Release Number:
Paae: VI -
86
-------
Section VI. Lisis of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID06. Contaminant Identification Codes
Code Value Associated Description Comment(s)
Lead and Copper Rule Regulated Monitoring Only
-R- -M-
5000 Lead S Copper Rule R
Effective Date: 1/31/93 Release Number: Z.OO Page: VI - 86.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID07, Record Data Origin Codes
Code Value Associated Description Comment(s)
H Headquarters (EPA) supplied data EPA Use Only
R Region (EPA) supplied data EPA Use Only
3 State supplied data
Effective ' 1/31/93 Release Huaber: 2. Paoe: VI - 87
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID08, Violation Type Codes
Code Value Associated Description Comment(s)
01 MCL, Single Sample
02 MCLi Average
03 Monitoring. Regular
04 Monitoring. Check/Repeat/Confirmation
05 Notification, State
06 Notification, Public
07 Treatment Techniques
08 Variance/Exemption/Other Compliance
Schedule
09 Record Keeping
10 Operations Report
21 MCL, Acute (TCR)
22 MCL, Monthly (TCR)
23 Monitoring, Routine Major CTCR)
24 Monitoring, Routine Minor (TCR)
25 Monitoring. Repeat Major (TCR)
26 Monitoring, Repeat Minor (TCR)
26 Sanitary Survey (TCR)
31 Monitoring, Routine/Repeat (SHTR-Unfilt)
36 Monitoring. Routine/Repeat (SMTP-Filter)
41 Treatment Technique (SHTR)
51 Initial Tap Sampling for Pb and Cu
52 Follow-up and Routine Tap Sampling
53 Initial Hater Quality Parameter HQP MSR
54 Follow-up 1 Routine E.P. MQP MKR
55 Follow-up ft Routine Tap HUP M*R
56 Initial, Follow-up, or Routine SOUT MtR
57 OCCT Study Recommendation
56 OCCT Installation/Demonstration
59 UQP Entry Point Non-Compliance
60 MQP Tap Non-Compliance
61 SOHT Recommendation
62 SOHT Installation
63 MPL Non-Compliance
64 Lead Service Line Replacement (LSLR)
65 Public Education
Effective Date: 1/31/93 Release Number: 2.00 Paqe: VI - 88
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09t Enforcement FolloM-up Action Codes
Associated Description Coi
t(s)
Federal Enforcement Actions
EF<
Fed CFP issued
Federal Complaint for Penalty issued
An administrative action in Mhich EPA
seeks to collect up to $5.000 for
violation of a final administrative
order.
EF*
Fed Crim Case referred to DOJ
Federal Criminal Case referred to the
U.S. Department of Justice
The sending of the required litigation
report and other documents to the U.S.
Department of Justice for the filing
of a criminal case in an appropriate
U.S. District Court
EF!
Fed PAD issued
Federal Proposed Administrative Order
issued
An order issued by EPA under the
authority of Section 1414 of the SDHA
to a PHS which proposes to require
compliance with the national primary
drinking Mater regulations. The
proposed order provides the
opportunity for a hearing on the
violations and the schedule allowed
for achieving compliance.
EF-
Fed CFP Consent Order/Decree M/penalty
Federal CFP Consent Order or Consent
Decree
An agreement signed by both the PHS and
EPA as a result of the issuance of
Complaint for Penalty ICFP). It
specifies the payment of a penalty by
the PHS for violation of the final
administrative order.
EF/
Fed 1431 (Emergency) Order
Federal 1431 Emergency Administrative
Order
Effective
1/31/93
Release Number: 2
Paae: VI -
89
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID09, Enforcement Follow-up Action Codes
Associated Description Comment(s)
Note: Thim list begins on VI - 69
Federal Enforcement Actions
Previous page is continued on next line
EF/
An order issued by EPA under the
authority of Section 1431 of the SDHA.
Section 1431 enables EPA to act
whenever there is an "imminent and
substantial endangerment" to the
health of persons. EPA nay order the
measures necessary to protect public
health, including the provision of
bottled Mater.
EFX
Fed Civil Case concluded
Federal Civil Case concluded
Federal civil case resolved through
verdicti pleas> injunction! EPA/DOJ
decision to drop the casei etc.
EF =
Fed CFP Default Judgement
Federal CFP Default Judgement
An administrative judgement! entered as
a consequence of the failure of the
owner/opentor of a PHS to respond to
a Complaint for Penalty or to appeal
at the administrative hearing.
EFG
Fed Publ:c Motif issued
Public Notification issued by EPA
Public notification issued by EPA. It
may be issued in response to
violations about which the supplier
failed to notify the public, or where
EPA believes there is a risk to
health. It may be issued
simultaneously with a Boil Hater
Order.
EFH
Fed Boil Hater Order
Federally issued Boil Hater Order
Order which notifies the system1!
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
90
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09, Enforcement Follow-up Action Codes
Associated Description
Comment(s)
Note: This list begins on VI - 69
Federal Enforcement Actions
Previous page is continued on next line
EFH
customers/users of a deficiency (MCL
or M/R violation(s)) that could result
in an acute risk to healthi and that
they (the users) should boil water
before using it (for drinkingi
cooking, possibly bodily contact).
This would be issued generally only
where EPA is acting as the primacy
agency• or as part of a Federal AO.
EFJ
Fad Formal NOV issued
Federally issued Notice of Violation
A notice issued under the authority of
Section 1414 of the SDHA to the PUS
and the State that the system is in
violation of the national primary
driaKing Mater regulations and that
if the Stata does not commence an
appropriate enforcement action within
30 daysi EPA will either issue an
order or file a civil case.
EFK
Fed BCA signed
Federal EPA Bilateral Compliance
Agreement signed
An agreement signed by both EPA and the
PUS that contains a schedule to return
the system to compliance. The
agreement should comport with OGHDM
guidance on the use of BCAs.
EFL
Fed FAD Issued
Federal Final Administrative Order
Federal Final Administrative Order
issued
An order issued by EPA under the
authority of Section 1414 of the SDHA.
The order requires compliance with the
national primary drinking water
Effectivr
'«: 1/31/93
Release Number: 9
Paoe: VI -'
90.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09. Enforcement Follow-up Action Codes
Associated Description
Connnent(s)
Note: This list begins on VI - 69
Federal Enforcement Actions
Previous page im continued on next line
EFL
regulations and nay specify a
reasonable time for the PUS to achieve
compliance. If the order is violated!
EPA nay administratively assess a
penalty of up to $5tOOO or assess up
to $Z5(000 in a civil action.
EFN
Fed ShoN-cause Hearing
A hearing held to provide opportunity
for the violator to present
information to the Federal EPA and the
public on reasons for not complying.
Such hearings often result in
compliance agreements or other formal
actions. This Mould be issued
generally only where EPA is acting as
the prinacy agency.
EFQ
Fed Civil Case filed
Federal Civil Case filed in an
appropriate U.S. District Court
The action by the U.S. Department of
Justice to place the civil case on the
docket of the appropriate U.S.
District Court.
EFR
Fed Consent Decree/Judgement
Federal Consent Decrea or Consent
A formal agreement between EPA and the
PUS that settles a civil case. The
decree contains the actions the PHS
must take to return to compliance with
the national primary drinking water
regulations and the SDMA. and a
schedule for those actions. The
decree usually assesses a penalty for
past violations and specifies the
penalties a PHS will pay for
violations of the consent decree.
Jurisdiction is retained by the court
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
91
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09, Enforcement Follow-up Action Codes
Associated Description
Conment(s)
Note: This list begins on VI - 69
Federal Enforcement Actions
Previous page is continued on next line
EFR
to oversee compliance with the
Decree/Judgement provisions.
EFS
Fed Default Judgement
Federal Default Judgement
A Federal court judgement that is
rendered as a consequence of the
non-appearance of the system
owner/operator.
EFT
Fed Injunction
Federal Injunction
An order issued by the Federal court
that directs the PMS to take certain
actions (or forbids the PHS to take
certain actions). An injunction
usually contains penalties for
violations of its tc
EFU
Fed Temp Restrain Order/Prelim Injune
Federal Temporary Restraining
Order/Preliminary Injunction
An immediatei non-final order issued by
the Federal court that forbids the PHS
from taking certain actions» or orders
the PMS to take some. Often used in
emergency situations.
EFV
Fed Crira Case filed
Federal Criminal Case filed in •
Federal court
The action taken by the U.S. Department
of Justice to place a criminal case on
the docket of the appropriate U.S.
District Court. (Occurs after
indictments)
Effective
EFU
1/31/93
Fed Crim Case concluded
Federal Criminal Case concluded
Release Number: 2
Paoe: VI -
91.5
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID09. Enforcement Follow-up Action Codes
Associated Description Comment(s)
Note: This list begins on VI - 89
Federal Enforcement Actions
Previous page is continued on next line
EFH
Federal criminal case resolved through
verdict> picas> injunction* etc.
EF9
Fed Civil Case referred to DOJ
Federal Civil Case referred to the U.S.
Department of Justice
The sending of the litigation report and
other required documents to the U.S.
Department of Justice for filing of •
civil case in an appropriate U.S.
District Court.
EZA
Fed Violation/Reminder Notice
Informal written or oral notification
that a violation occurred, explaining
whit the violation MBS (MCL. hVR.
etc.). It may specify that public
notification should occur.
Includes Violation Notice. Reminder
Latter. Warning Letter.
A Reminder Letter is an infernal Mritten
notification that a violation has
occurred.
A Darning Letter contains ell the same
elements as a Reminder Letter but also
specifies what legal or adninistrative
actions may occur if the system does
not return to compliance.
This code should generally be used only
where EPA is acting as the primacy
agency.
EZ8
Fed Compliance Meeting conducted
Meeting between EPA officials and
representatives of the PUS to discuss
the violation and to explain the
requirements for compliance. This
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID09, Enforcement Follow-up Action Codes
Associated Description Comment(s)
Note: This list begins on VI - 69
Federal Enforcement Actions
Previous page is continued on next line
EIB
serves as an informative meeting about
requirements of the SDMA» as opposed
to an enforcement meeting.
EIC
Fed Tech Assistance Visit
Technical Assistance Visit or Meeting
Meeting between EPA officials and
representatives of the PUS to discuss
the system's status* the requirements
for monitoring and reporting, and
operational problems. This visit is
usually triggered by a complaint or
request from a system owner/operator.
EPA usually provides assistance of a
technical nature to return the system
to compliance (e.g. calibrating'
equipmenti a lesson in "how" to take
samples).
EID
Fed Site Visit (enforcement)
Site visit for enforcement purposes
A visit to the PUS in which a Federal
official attempts to confirm or
. discover additional violations. This
visit could include discussion of
regulatory requirements and the
system's violations! collection of
samples using full chain-of-custody
quality assurance procedures>
discussion of penalties if compliance
is not aehievedi etc. A site visit
can be considered a preliminary step
for a formal enforcement action.
EIE
Fed Public Notif requested
Public Notification requested of system
Request by EPA for a supplier to giva
public notification that a violation
of the national primary drinking water
regulations has occurred. This
Effective
1/31/93
Release Number: f
Paqe: VI -
92.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Coda Value
Table ID09i Enforcement Follow-up Action Codes
Associated Description
Comment! •)
EIE
Note: This list begins on VI - 89
Federal Enforcement Actions
Previous page is continued on next line
request can be oral or written and
would generally folloH the violation
notice.
EIF
Fed Public Notif received
Public Notif received from system
Receipt of public notification issued by
the supplier in response to a
violation.
E0»
Fed No addtl Formal Action needed
Additional Formal Action unnecessary
EPA has determined that no additional
formal Federal action Hill be needed
to bring a PHS back into compliance.
EOX
Fed Compliance achieved
Required for chemical/radiological
violators only.
For H/R violations* the submission of
monitoring result. For HCL
violattonst the submission of
monitoring results demonstrating
contaminant levels below the maximum
contaminant levels (MCLs).
Used when compliance is achieved as a
result of Federal action.
EOY
Fed Variance/Exemption issued
Fed Variance or Exemption issued
The issuance to a PHS by EPA of a
variance, as allowed by Section 1415
of the SDHAi or and exemption! as
allowed by Section 1416 of the SDHA.
Only used where EPA is acting as the
primacy agency.
Effective Datei 1/31/93
Release Number: 2.00
Pane: VI -
-------
Section VI. Lists of Acceptable Coda Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09, Enforcement FolloM-up Action Codes
Associated Description
Comment! s)
Note: This list begins on VI - 89
Federal Enforcement Actions
EOZ
Fed Turbidity Maiver issued
The issuance to the PUS by EPA of •
waiver that increases the allowable
turbidity limit for the systemi as
allowed by 40 CFR 141.13. Only used
where EPA is acting as the primacy
agency.
E06
Fed Intentional no-action
EPA has reviewed the public water
system's compliance history and has
decided to take no action in response
to this specific violation.
E07
Fed Unresolved
No action has been taken by EPA in
response to this violation. There has
been no general review of the PHS's
compliance history and no decision not
to proceed.
E08
Fed Other
An action has been taken by EPA that
cannot be placed into one of the other
categories. This code should be used
very infrequently.
Effective
'e: 1/31/93
Release Number: ?
Paae: VI -
93.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09, Enforcement Follow-up Action Codes
Associated Description
Comment!s)
State Enforcement Actions
SF»
St Crim Case referred to AG
State Criminal Case referred to the
State Attorney General
The sending of the required litigation
report and other documents to the
State Attorney General for the filing
of • criminal case in State court.
SFX
St Civil Case concluded
State Civil Case concluded
State civil case resolved through
verdicti pleas, injunction, etc.
SFG
St Public Notif issued
Public notification issued by the
primacy agent. It may be issued in
response to violations about which the
supplier did not notify the public or
where the State feels there is a risk
to health. It may be issued
simultaneously with a Boil Hater
Order.
SFH
St Boil Hater Order
State issued Boil Hater Order
Order which notifies the system's
customers/users of e deficiency (MCI
and/or M/R violation(s)) that could
result in an acute risk to health, and
that they (the users of the water)
should boil the water before using it
(for drinking, cooking, possibly
bodily contact).
SFJ
St Formal MOV issued
State issued Formal Notice of Violation
A formal notification to a public water
system that it is in violation of a
drinking water regulation, that the
PUS must take some action to rectify
its problem (e.g.. disinfect, give
public notification, take samples
correctly, report results), and that
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1009* Enforcement Follow-up Action Codes
Associated Description Comment(s)
Note: This list begins on 'VI - 94
State Enforcement Actions
Previous page is continued on next line
SFJ
formal legal action nay follow if the
specified actions are not taKen. 'A
NOV may specify dates by which actions
should be taken.
SFK
St BCA signed
State Bilateral Compliance Agreement
signed
An agreement signed by both the State
and the Public Hater System that
contains a schedule to return the
system to compliance. The agreement
should comport with OGHDH guidance on
the use of BCAs.
SFL
St AO IN/O penaltyI issued
State Administrative Order/Cotnpliance
Order issued without penalty
An order issued by the Executive branch
of the State government that orders
the PUS to come into compliance or to
undertake remedial actions. No
penalty is assessed.
SFM
St Admin Penalty assessed
State Administrative Penalty assessed
A penalty (usually monetary) assessed by
a non-judicial body (e.g.. program
director or field staffi depending on
specific legislative authorities) in
response to a violation of the
regulations or failure to take actions
ordered by the primacy agent to
achieve compliance. Host often issued
after a State has issued an AO/CO
without penalty and the system
violates that order.
SFN
Effective Date: 1/31/95
St Shou-cause Hearing A hearing held to provide opportunity
Release Number: 2.00 Paoe: VI
94.5
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID09i Enforcement FolloM-up Action Codes
Associated Description Comment(s)
Note: This list begins on 'VI - 94
State Enforcement Actions
Previous page is continued on next line
SFN
for the violator to present
information to the State and the
public on its reasons for not
complying with the State SDHA and/or
regulations. Such hearings often
result in compliance agreements or
other formal actions.
SFO
St AO (w/penalty) issued
State Administrative Order/Compliance
Order issued with Penalty
An order issued by the Executive branch
of the State government» that orders
the PX'S to come into compliance or to
undertake remedial actions. A penalty
is assessed.
SFP
St Civil Case under development
State Civil Case under development
Technical/legal staff are preparing
documents to refer a civil case to the
State Attorney General.
SFQ
St Civil Case filed
State Civil Case filed in State court
The action by the State Attorney General
to place the civil case on the docket
of the appropriate State court.
SFR
St Consent Decree/Judgement
State Consent Decree or Consent
Judgement
A formal agreement filed in a State
court between the PUS end the primacy
agency that settles a civil ease and
that specifies the actions and a
schedule for those actions that must
be taken by the PUS to achieve
compliance with the regulations. The
Effective
1/31/93
Release Number: ?
Pane: VI -
95
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09i Enforcement Follow-up Action Codes
Associated Description
Comment(s)
Note: This list begins on 'VI - 94
State Enforcement Actions
Previous page is continued on next line
SFR
decree generally also contains the
actions that the primacy agent may
take if the system fails to comply
with the terms of the Consent Decree.
It generally includes penalties for
each day of violation of the schedule.
Jurisdiction is retained by the court
to oversee compliance Mtth the
Decree/Judgement provisions.
SFS
St Default Judgement
State Default Judgement
A State court judgement that is
renderedi in accordance with State
civil proeedurei generally as a
consequence of the non-appearance of
the system owner/operator.
SFT
St Injunction
State Injunction
A final order issued by the State court
that directs the PMS to take certain
actions (or forbids the PHS to take
certain actions). An Injunction
usually contains penalties for
violations of its terms.
SFU
St Temp Restrain Order/Prelim Injune
State Temporary Restraining Order/
Preliminary Injunction
An immediate* non-final order issued by
the State court that forbids the PHS
to take certain actions• or orders the
PUS to take certain actions. Often
used in emergency situations.
SFV
St Cria Case filed
State Criminal Case filed in State court
The action by the State Attorney General
Effective Date: 1/31/93
Release Number: 2.00
Pace: VI -
95.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Coda Value
Table ID09, Enforcement Follow-up Action Codes
Associated Description
Comment! s)
Note: This list begins on 'VI - 94
State Enforcement Actions
Previous page is continued on next line
SFV
to place a criminal case on the docket
of the appropriate State court.
SFM
St Crim Case concluded
State Criminal Case concluded
State criminal case resolved through
verdict, pleas, injunction* etc.
SF3
St Case appealed
The PUS has filed an appeal relating to
the decision in or outcome of a
previous State administrative* civil
or criminal action.
SF4
St Case dropped
Civil or criminal action against the PHS
has been discontinued by the primacy
agent. This code should only be used
uhere actions concerning civil or
criminal cases ISFP, SF9, SFQ, SFX,
SFR, SFSi SFT. SFU, SF«, SFV and/or
SFM) have been reported.
SF5
St Hook-up/Extension Ban
•An order by the State, County or local
health agency that bans further
connections to the Mater system,
extensions of Meter system to serve
new customer*, or-bans Issuance of
septic tank/building permit/occupancy
permits. '
SF9
St Civil Case referred to AS
State Civil Case referred to State
Attorney General
The sending of the required litigation
report end other documents to the
State Attorney General for the filing
of e civil case in State court.
Effectiv
•: 1/51/95
Release Number:
Page: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09. Enforcement Follow-up Action Codes
Associated Description
Comment! s)
SIA
Note: This list begins on 'VI - 94
Stste Enforcement Actions
St Violation/Reminder Notice
Informal written or oral notification to
representatives of the public water
system (PHS) from State officials that
a violation has occurred, explaining
what the violation was (MCLt tl/Ri
etc.). It may specify that public
notification should occur.
Includes Violation Notice* Reminder
Letter* Naming Letter.
A Reminder Letter is an informal written
notification that a violation has
occurred (e.g.i • sample was missed).
A Naming Letter contains all the sane
elements as a Reminder Letter but also
specifies what legal or administrative
actions may occur if the system does
not return to compliance.
SIB
St Compliance Meeting conducted
Meeting between State official* and
representatives of the PHS to discuss
the violations) and to explain the
requirements for compliance. This
serves as an informative meeting about
the requirements of the SDHA, as
opposed to an enforcement meeting.
SIC
St Tech Assistance Visit
Technical Assistance Visit or Meeting
Meeting between State officials and
representatives of the PHS to discuss
the system's status, the requirements
for monitoring and reporting, and
operational problems. This visit is
usually triggered by a complaint or
request from a system owner/operator.
The State usually provides assistance
of a technical nature to return the
system to compliance (e.g.* calibrate-
equipment) a lesson in "how" to take
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI -
96.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09. Enforcement Follow-up Action Codes
Associated Description
Comment(s)
SIC
SID
Note: This list begins on 'VI - 94
State Enforcement Actions
Previous page is continued on next line
St Site Visit (enforcement)
samples).
Site visit for enforcement proposes
A visit to the PUS in which B State
official attempts to confirm or
discover additional regulatory
violations. This visit could include
discussion of requirements and the
system's violations* collection of
samples using full chain-of-custody
quality assurance procedures>
discussion of penalties if compliance
is not achieved! etc. A site visit
can be considered a preliminary step
for e formal enforcement action.
SIE
St Public Hotif requested
Public Notification requested of system
Request by the State for a supplier to
give public notification that a
violation of the regulations has
occurred. This request can be oral or
written and Hould generally follow the
violation notice.
SIF
St Public Notif received
Public Notification received from system
Receipt of public notification issued by
the supplier in response to a
violation.
SO*
St No addtl Formal Action needed
Additional Formal Action unnecessary
The State has determined that no
additional formal State action Mill be
needed to bring a PMS back into
compliance.
Effective
>: 1/31/93
Release Number:
Paqe: VI -
97
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table ID09, Enforcement Follow-up Action Codes
Associated Description
CommentIs)
SOX
Note: This list begins on 'VI - 94
State Enforcement Actions
St Compliance achieved
Required for chemical/radiological
violators only.
For M/R violations! the submission of .
the code SOX indicates that the system
is monitoring and reporting properly
in accordance with the criteria for
compli once.
For HCL violations* the submission 'of
the code SOX means that subsequent
monitoring of the system indicates
that the system is operating below the
maximum contaminant level (MCL) and is
thus in compliance with the MCL.
SOY
St Variance/Exemption issued
St Variarice or Exemption issued
The issuance to a PUS by a State of a
variance as allowed by Section 1415 of
the SDHA or an exemption as allotted by
Section 1416 of the SDHA.
SOZ
St Turbidity Haiver issued
The issuance to the PHS by a State of
waiver that increases the allowable
turbidity limit for the systenf. n
allowed by 40 CFR 141.13.
S06
St Intentional no-action
The State has reviewed the public water
system's compliance history and has
decided to take no enforcement action
in response to this specific
violation.
S07
St Unresolved
No action has been taken by the State in
response to this violation. There has
been no general review of the PMS's
compliance history, and no decision
not to proceed.
Effectivr
1/31/93
Release Number:
Page: VI -
97.5
-------
Code Value
Section .VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID09, Enforcement Follow-up Action Codes
Associated Description Comment! s)
Note: This list begins on 'VI
State Enforcement Actions
st Other
An action has been taken by the State
that cannot be placed into one of the
other categories. This code should
rarely be used.
Effective Date: 1/31/9}
Release Number: 2.00
•«»«: VI -
98
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table IDlOi Combined Source/Entity Record Type and Source/Entry Point/Plant Type Codes
Code Value Associated Description Comment(s)
This table contains valid combinations
of values for data elements C405 ft C407
Pos. 1 = C405 Pos. 2 = C407
Entry Point Records
Source/Entry Point/Plant Type Codes
EA Surfacei Permanent
EB Surfacei Non-permanent
EC Groundwater, Permanent
ED Groundwater. Non-permanent
Plant/Facility Records
Source/Entry Point/Plant Type Codes
PH Hell Head
PI Intake
PM Pumping Facility
PO Other Plant or Facility
PR Storage Facility
PT Treatment Plant
Source Records
Source/Entry Point/Plant Type Codes
SG Groundwater, Non-purchased
SP Surface, Purchased
S3 Surface. Non-purchased
SH Groundwater, Purchased
SY Groundwater IUDI), Non-purchased
SZ Groundwater (UDI)» Purchased
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 99
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table ID11,- Township/Range Quarter Section and Quarter-Quarter Section Codes
Code Value Associated Description Comment(s)
NE Northeast Quarter
MM Northwest Quarter
SE Southeast Quarter
SM Southwest Quarter
Effective ' -: 1/31/93 Release Number: 2 Pane: VI - 100
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 000It EPA Region Codes
Associated Description
Comment! s)
01
02
03
04
05
06
07
06
09
10
Boston. EPA Region X
New York, EPA Region II
Philadelphia, EPA Region III
Atlanta, EPA Region IV
Chicago. EPA Region V
Dallas. EPA Region VI
Kansas City, EPA Region VII
Denver, EPA Region VIII
San Francisco, EPA Region IX
Seattle, EPA Region X
States within EPA Region
CT HE HA NH RI VT
NJ NY PR VI 02
DC DE HD PA VA NV
AL FL GA KY HS NC SC TN 04
IL IN HI HN OH HI 05
AR LA NH OK TX 06
IA KS HO NE 07
CO HT ND SO UT HY 06
AS AZ CA FH GU HI HH HP NV PH 09
AK ID OR HA 10
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI - 101
-------
Section VI. Lists of Acceptable Coda Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0003. FTPS PUB 5-2, Alphabetic State Codes and Selected EPA Region Codes,.
Code Value Associated Description Comment!s)
AK
AL
AR
AS
AZ
CA
CO
CT
DC
DE
FL
rn
6A
GU
HI
ZA
ID
XL
IN
KS
KY
LA
MA
HO
ME
MH
MI
MN
MO
MP
MS
MT
NC
NO
FIPS PUB 5-2, Alphabetic State Codes
Alaska
Alabama
Arkansas
American Samoa
Arizona
California
Colorado
Connecticut
District of Columbia
Delaware
Florida
Federated States of Micronesia
Georgia
Guam
Hawaii
Iowa
Idaho
Illinois
Indi ana
Kansas
Kentucky
Louisiana
Massachusetts
Maryland
Maine
Marshall Islands. Republic of the
Michigan
Minnesota
Missouri
Northern Mariana Islands
Mississippi
Montana
North Carolina
North Dakota
EPA Region
in which
State
is Located
X
IV
VI
IX
IX
IX
VIII
I
III
III
IV
IX
IV
IX
IX
VII
X
V
V
VII
IV
VI
I
III
I
IX
V
V
VII
IX
IV
VIII
IV
VIII
Number of
Federal
Congressional
Districts
1
7
4
1
6
52
6
6
1
1
23
0
11
1
2
5
2
20
10
4
6
7
10
a
2
0
16
6
9
0
5
1
12
1
C
0
N
U
s
N
N
N
N
N
N
N
Effective
1/31/93
Release Number: 2
Pane: VI - 102
-------
Section VI.. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0003, FIP5 PUB 5-2, Alphabetic State Codes and Selected EPA Region Codes
Code Value Associated Description Coirment(s)
NE
NH
NJ
NH
NV
NY
OH
OK
OR
PA
PR
PH
RI
SC
SD
TN
TX
UM
UT
VA
VI
VT
HA
HI
HV
HT
Note: This list begins on VI - 102
FIPS PUS 5-2, Alphabetic State Codes
Nebraska
Net* Hampshire
New Jersey
New Mexico
Nevada
New York
Ohio
Oklahoma
Oregon
Pennsylvania
Puerto Rico
Palaui Republic of
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
U.S. Minor Outlying Islands
Utah
Virginia
Virgin Islands of the U.S.
Vermont
Hashington
Wisconsin
Hest Virginia
Wyoming
EPA Region
in which
State
is Located
VII
I
II
VI
IX
II
V
VI
X
III
II
IX
I
IV
VIII
IV
VI
Not Applicable
VIII
III
II
I
X
V
III
VIII
Number of
Federal
Congressional
Districts
3
2
13
3
2
31
19
6
5
21
1
0
2
6
1
9
30
0
3
11
1
1
9
9
3
1
C
0
N
U
s
N
N
N
N
Effective Datei 1/31/93
Release Number! 2.00
Paae: VI - 103
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0003, FIPS PUB 5-2. Alphabetic State Codes and Selected EPA Region Codes
Code Value Associated Description Coimnent(s)
Selected EPA Region Codes
02 New York. EPA Region II
04 Atlanta. EPA Region IV
05 Chicago. EPA Region V
06 Dallas. EPA Region VI
07 Kansas City, EPA Region VII
06 Denver. EPA Region VIII
09 San Francisco. EPA Region IX
10 Seattle, EPA Region X
Effective 1/31/93 Release Number: 2. Paoe: VI - 104
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0005» Primacy Flag Codes
Code Value Associated Description Comment(s)
N Native Entity has Primacy Indian Tribe/Reservation
R EPA Region ha* Primacy
S State Agency has Primacy
Effective Date: 1/31/93 Release Nu«ber: 2.00
»05
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0019. State Reconciliation Flag Codes
Code Value Associated Description Comment!s)
N Reconciliation NOT Needed for State
Y Reconciliation Needed for State
Effective >: 1/31/93 Release Number: ? Page: VI - 106
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Data!led Lists of Code Values
Table 0102. Grant Eligibility Codes
Code Value Associated Description Conment(s)
N PUS NOT Grant Eligible
Y PHS Grant Eligible
Effective Date: 1/31/93 Release Number: 2.00 P«o*s VI - 107
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 0103, PUS Status Codes
Associated Description
it(s)
CAC
CAN
CIC
CIH
NAC
NAH
NIC
NIH
PAC
PAH
PIC
PIH
CMS, Active, Current
CHS, Active, Historical
CHS, Inactive, Current
CHS, Inactive, Historical
TNCHS, Active, Current
TNCHS, Active, Historical
TNCHS, Inactive, Current
TNCHS, Inactive, Historical
NTNCHS. Active, Current
NTNCHS, Active, Historical
NTNCHS, Inactive, Current
NTNCHS, Inactive, Historical
Community PHSs
Community PHSs
Community PHSs
Community PHSs
Transient Non-community PHSs
Transient Non-community PHSs
Transient Non-community PHSs
Transient Non-community PHSs
Non-transient Non-community PHSs
Non-transient Non-cosmunity PHSs
Non-transient Non-community PHSs
Non-transient Non-community PHSs
Effective
1/31/93
Release Number:
Page: VI - 108
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed List* of Code Values
Table 0105. PUS Type Codes
Code Value Associated Description Comment!»)
C Community PUS (CHS)
N Transient Non-community PUS (TNCMS)
P Non-transient Non-community PUS INTNCMS)
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 109
-------
Section VI. Lists of Acceptable Code Values uith Associated Descriptions
C. Detailed Lists of Code Values
Table 0107. PUS Activity Flag Codes
Code Value Associated Description Comment(s)
A Active PHS
I Inactive PHS
Effective' -: 1/31/93 Release Number: Z" Paoe: VI - 110
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0109, History Flag Codes
Code Value Associated Description Comment!s)
C Current Inventory
H Historical Inventory
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 111
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table OllSi Population Category Codes
Associated Description
Comment! a)
A
B
C
D
E
F
6
H
I
J
K
Under 101 persons served
101-500 person* served
501-1.000 persons served
1,001-2,500 persons served
2,501-3,300 persons served
3,301-SvOOO persons served
5,001-10,000 persons served
10,001-50,000 persons served
501001-751000 persons served
75,001-100i000 persons served
Over 100,000 persons served
Effective
1/31/93
Release Number: r
Paoe: VI - 112
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0119t Primary Source Type Codes
Code Value Associated Description Comrnentlsl
6 Groundkiatert Non-purchased
P Surfacei Purchased
S Surface.* Non-purchased
H Grounduateri Purchased
Y Groundttater (UDI)» Non-purchased
Z Groundwater (UDI), Purchased
Effective Date: 1/J1/93 Release Number: 2.00 Paae: VI - 113
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 0129. Treatment Class Codes
Associated Description
Comment! s)
Mixed Treated/Untreated
Some sources have treatment applied but
not all
Treated
Untreated
All sources have treatment applied
No sources have treatment applied
Effective t: 1/31/93
Release Number: 2
Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 0163. PUS Owner Type Codes
Associated Description
Comment!s)
Not Reported by State
'*' nay not be used on any FRDS-II input
transaction. It was assigned by the
FRDS-II computer system during the
conversion of data from PROS 1.5 to
FRDS-II.
Federal Government
Private
Subdivisions! Investors* Trusts•
Cooperatives, Hater Associations, etc.
State Government
Local Government
Authorities, Commissions, Districts*
Municipalities, Cities, Towns,
Counties, etc.
5
6
Mixed Public/Private
Native American
Indian Tribes a Reservations, Alaska
Remote Villages
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI - 115
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0165, Regulating Entity Codes
Code Value Associated Description Comment(•)
B Both State ft Federal Governments
F Federal Government Only
N Neither Mate nor Federal Govt.
S State Government Only
Effectiv "e: 1/31/93 Release Number: Paoe: VI - 116
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0171. PUS Reconciliation Flag Codes
Code Value Associated Description Comment!s)
N Reconciliation NOT Needed for PNS
Y Reconciliation Needed for PUS
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 117
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0303i Addressee Type Codes
Code Value Associated Description Comment!s)
D Distribution Facility
E Employee
L Labor-atony
H Hailing
0 System Owner/Responsible Party
P Pumping Facility
R Operator
S Storage Facility
T Mater Treatment Plant/Facility
V Vendor
X Other
Effectivr ^ 1/31/93 Release Number: ? Page: VI - 118
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0405. Source/Entity Record Type Codes
Associated Description Comment!s)
See Table ID10 for valid combinations
of these codes in conjunction with
Source/Entry Point/Plant Type (C407)
codes
Entry Pdint Record
Surface or Groundwater, and Permanent or
Non-permanent
Plant/Facility Record
Treatment Plant. Storage* Pumping, and
Distribution Facilities, Hell Head,
Intake, etc.
Source Record
Surface, Groundwater, Purchased Source
Effeotive Data: 1/31/93
Release Numberi 2.00
Pa«
VI - 119
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0407i Source/Entry Point/Plant Type Codes
Associated Description Comment!s)
A
B
C
D
6
H
I
H
0
P
R
S
T
N
Y
Z
Sur face» Permanent
Surfacei Non-permanent
Groundwatert Permanent
Groundua ter» Non-pernanent
GrounoViateri Non-purchased
Hell Head
Intake
Pumping Facility
Other Plant or Facility
Surface, Purchased
Storage Facility
Surfacei Non-purchased
Treatment Plant
GroundMatert Purchased
Grounduater (UOI)i Non-purchased
Groundunter (UDI)i Purchased
See Table ID10 for valid combinations
of these codes in conjunction with
Source/Entity Record Type (C405) codes
Record Type to which Applicable
Entry Point
Entry Point
Entry Point
Entry Point
Source
Plant/Facility
Plant/Facility
Plant/Facility
Plant/Facility
Source
Plant/Facility
Source
Plant/Facility
Source
Source
Source
Effective n*te: 1/31/93
Release Number: 2.«0
Paoe: VI - 120
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0409. Source Availability Codes
Code Value Associated Description Comment!s)
___________ ______________•__________________________ ____________________________
E Emergency Utilization
I Interin Utilization
0 Other Utilization
P Permanent Utilization
S Seasonal Utilization
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 121
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0429. On Reach Flag Codes
Code Value Associated Description Comment(s)
N Intake NOT on defined River Reach
Y Intake on defined Rivor Reach
Effective Datei 1/31/93 Release Humbert 8.00 Pane: VI - 365
-------
Section VI. Lists of Acceptable Code Values with-Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress),
Code Value Associated Description Comment!si
• ««•_••«_«••« _V_«»_K««B«H«~V« •••• • — B__I__IW«M«MH«H^ •«••«••••••«•«•••••••• ™«««™«««»«™»™~~
State of Alaska (AK)
00 At Large IAK) One Representative
Effecti- te: 1/31/93 Release Hunter: Paoe: VI - 386
-------
Saction'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Cod* Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Conment(s)
State of Alabama (AD
01 1st District (AD
02 2nd District (AD
03 3rd District (AD
04 4th District (AD
05 5th District (AD
06 6th District (AD
07 7th District (AD
Effective Data: 1/31/93 Release Number: 2.00 P«w« VI - 387
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, fIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Arkansas (AR)
01 1st District (AR)
02 2nd District (AR)
03 3rd District (AR)
04 4th District (AR)
Effective -: 1/31/93 Release Number: ? Page: VI - 388
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9i Federal Congressional District Codes 1103rd Congress)
Code Value Associated Description Comment)s)
American Samoa (AS) U.S. Possession
98 Non-voting Delegate (AS)
Effective Date: 1/31/93 Release Number: 2.00 Paoei VI - 389
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table 0507, FIPS PUB 9t Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Arizona (AZ)
01 1st District (AZ)
02 2nd District (AZ)
03 3rd District (AZ)
04 4th District (AZ)
05 5th District (AZ)
06 6th District (AZ)
Effectn
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
State of California (CA)
01 1st District (CAI
02 2nd District (CA)
03 3rd District (CA)
04 4th District (CA)
OS 5th District (CA)
06 6th District (CA)
07 7th District (CA)
Ofi 8th District (CA)
09 9th District (CA)
10 10th District (CA)
11 llth District (CA)
12 12th District (CA)
13 13th District (CA)
14 14th District (CA)
15 15th District (CA)
16 16th District (CA)
17 17th District (CA)
18 18th District (CA)
19 19th District (CA)
20 20th District (CA)
21 21st District (CA)
22 22nd District (CA)
23 23rd District (CA)
24 24th District (CA)
25 25th District (CA)
26 26th District (CA)
27 27th District (CA)
26 28th District (CA)
29 29th District (CA)
30 30th District (CA)
31 31st District (CA)
32 32nd District (CA)
33 33rd District (CA)
34 34th District (CA)
35 35th District" (CA)
36 36th District (CA)
37 37th District (CA)
38 38th District (CA)
Effective Date: 1/31/93 Release Numbers ft.00 fae: VI • 991
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C, Detailed Lists of Cade Values
Table 0507, FIPS PUB 9t Federal Congressional District Codes '(103rd Congress)
Code Value Associated Description ConmenttsJ
Note: This list begins on VI - 391
State of California (CA)
39 39th District (CAI
40 40th District (CA)
41 41st District (CA)
42 42nd District (CA)
43 43rd District (CA)
44 44th District (CA)
45 45th District (CA)
46 46th District CCA)
47 47th District (CA)
46 46th District (CA)
49 49th District (CA)
50 50th District (CA)
51 51st District (CA)
52 52nd District (CA)
ffective Ds>' V31/93
Release Number: 2.OP •»•<*: VI - 392
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507t FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value. Associated Description Conment(s)
State of Colorado (CO)
01 1st District (CO)
02 2nd District (CO)
03 3rd District (CO)
04 4th District (CO)
OS 5th District (CO)
06 6th District (CO)
Effective Data: 1/31/93
Release Number: 2.00 Paoe: VI - 393
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Connecticut (CT)
01 1st District (CT)
02 2nd District (CT)
03 3rd District (CT)
04 4th District (CT)
05 5th District (CT)
06 6th District (CT)
Effectivr ^: 1/31/93 Release Number: 7 Paoe: VI - 394
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FTPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
District of Columbia (DC)
98 Non-voting Delegate (DC)
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 395
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
State of Delaware (DE)
00 At Large IDE) One Representative
E1f*etiv te: 1/11/91 Release Number: - "0 Paoe: VI - 596
-------
Section VI. Lists of Acceptable Code Values nith Associated Descriptions
C. Detailed Lists of Code Values
Table 0507i F1P5 PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
State of Florida (FLI
01 1st District IFL)
02 2nd District IFL)
03 3rd District (FLI
04 4th District (FL)
05 5th District (FL)
06 6th District (FL)
07 7th District (FL)
08 8th District (FL)
09 9th District (FL)
10 10th District (FL)
11 llth District (FL)
12 12th District (FL)
13 13th District (FL)
14 14th District (FL)
15 15th District IFL)
16 16th District IFL)
17 17th District (FL)
IB 16th District (FL)
19 19th District (FL)
20 20th District (FL)
21 21st District (FL)
22 22nd District (FL)
23 23rd District (FL)
Effective Date: 1/31/93 Release Number: 2.00 P«ae: VI - 397
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507; FIPS PUB 9i Federal Congressional District Codes 1103rd Congress),
Code Value Associated Description Comment(s)
Federated States of Micronesia (FM) Freely Associated State
99 No Representative (FM)
Effectiv ^e: 1/31/93 Release Number: Paoe: VI - 398
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes 1103rd Congress)
Code Value Associated Description Commentls)
State of Georgia (GA)
01 1st District (6A)
02 2nd District (GA)
03 3rd District (GA)
04 4th District (GA)
05 5th District (6A)
06 6th District (GA)
07 7th District (GA)
06 6th District (GA)
09 9th District (GA)
10 10th District (GA)
11 llth District (GA)
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 399
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507i-.FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
Guam (GUI U.S. Possession
96 Non-voting Delegate (GUI
Effectiv t: 1/31/93 Release Number: 9 Paae: VI - '400
-------
Section VI. Lists of Acceptable Code Values uith Associated Descriptions
C. Detailed Lists of Code Values
Tabl* 0507, FIPS PUB 9> Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Hawaii (HI)
01 1st District (HI)
02 2nd District (HI)
Effective Datat 1/11/93 Release Humbert 2.00 Paaei VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Iowa (ZA)
01 1st District (IA)
02 2nd District (IA)
03 3rd District (IA)
04 4th District (IA)
05 5th District (IA)
Effectiv ««: 1/31/93 Release Number: ?•«»: VI - 402
-------
Section VI.. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lista of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Idaho I ID I
01 1st District (ID)
02 2nd District (ID)
Effective Oatet 1/31/93 Release Numberi 2.00 Paae: VI - 403
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 05071, FIPS PUB 9, Federal Congressional District Codes (103rd Congress!
Code Value Associated Description Comment!9)
State of Illinois (ID
01 1st District (ID
02 2nd District (ID
03 3rd District (ID
04 4th District (ID
05 5th District (ID
06 6th District (ID
07 7th District (ID
00 0th District (ID
09 9th District (ID
10 10th District (ID
11 llth District (IL1
12 12th District (ID
13 13th District (ID
14 14th District (ID
15 15th District (ID
16 16th District (ID
17 17th District (ID
16 10th District (ID
19 19th District (ID
20 20th District (ID
Effectiv 'e: 1X31/93 Release Number: Pane: VI - 404
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIP3 PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!•)
State of Indiana (IN)
01 1st District (IN)
02 2nd District (IN)
03 3rd District (IN)
04 4th District (IN)
OS 5th District (IN)
06 6th District (IN)
07 7th District (IN)
08 6th District (IN)
09 9th District (IN)
10 10th District (IN)
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 405
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Kansas (KS)
01 1st District (KS)
02 2nd District (KS)
03 3rd District (KS)
04 4th District (KS)
Effectiv e: 1/31/93 Release Number: Paoe: VI - 406
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
Commonwealth of Kentucky (KY)
01 1st District IKY)
02 2nd District (KY)
03 3rd District (KY)
04 4th District (KY)
05 5th District (KY)
06 6th District (KY)
Effective Date: 1/31/93 Release number: 2.00 P"Q«» VI - 407
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507* FIPS PUB 9( Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
State of Louisiana (LA)
01 1st District (LA)
02 2nd District (LA)
03 3rd District (LA)
04 4th District (LA)
05 5th District (LA)
06 6th District (LA)
07 7th District (LA)
Effectiv •: 1/31/93 Release Number: Page: VI - 408
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
Commonwealth of Massachusetts (HA)
01 1st District (HA)
02 2nd District (MA)
03 3rd District (MA)
04 4th District (MA)
05 5th District (MA)
06 6th District (MA)
07 7th District IMA)
08 8th District (MA)
09 9th District (MA)
10 10th District (HA)
Effective Date: 1/31/93
Release Number: 2.00 »•»«•: VI - 409
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Maryland (MD)
01 1st District (MO)
02 2nd District IMD)
03 3rd District (HO)
04 4th District (MD)
05 5th District (MD)
06 6th District (MD)
07 7th District (MD)
08 6th District (MD)
Effective >: 1/31/93 Release Number: ? Pane: VI - 410
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIP3 PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Maine (HE)
01 1st District (ME)
02 2nd District (ME)
Effective Data: 1/31/93 Release Number: 2.00 Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507t FIP3 PUB 9i Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
Republic of the Marshall Islands (MH) Freely Associated State
99 No Representative (MH)
Effective n=te: 1/31/93 Release Number: 2 — Page: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comnientls)
State of Michigan (HI)
01 1st District (MI)
02 2nd District (Mil
03 3rd District (HI)
04 4th District (HI)
05 5th District (MI)
06 6th District (MI)
0? 7th District (Ml)
06 flth District (MI)
09 9th District (MI)
10 10th District (MI)
11 llth District (MI)
12 lath District (MI)
13 13th District (MI)
14 14th District (MI)
15 15th District (Nil
16 16th District (MI)
Effective Date: 1/31/93 Release Humbert 2.00 Paae: VI - 413
-------
Section VI. Lists of Acceptable Cod* Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table 0507, FIPS PUB 9. Federal Congressional District Codes (103rd Congress I
Code Value Associated Description Comment!s)
State of Minnesota
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes 1103rd Congress)
Code Value Associated Description Comment!s)
State of Missouri (MO)
01 1st District (HO)
02 2nd District (MO)
03 3rd District (MO)
04 4th District (HO)
05 5th District (RO)
Ob 6th District (MO)
07 7th District (NO)
08 6th District (HO)
09 9th District (MO)
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 415
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!si
Northern Mariana Islands IMP) U.S. Possession
99 No Representative (HPI
Effecti- te: 1/31/93 Release Number: ' 1 Paoe: VI -
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9> Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Mississippi CMS)
01 1st District CHS)
02 2nd District (MS)
03 3rd District IKS)
04 4th District (MS)
05 5th District (MS)
Effective Date: 1/31/93 Release Number: 2.00 Peat: VI - 417
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507.. FIPS PUB 9i Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Conrnient(s>
State of Montana IMTJ
00 At Large IhT) One Representative
Eff«cti< ve: 1/31/93 Release Number: Pane: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Conunent<»>
State of North Carolina INC)
01 1st District INC)
02 2nd District (NO
03 3rd District (NO
04 4th District (NO
05 5th District (NO
06 6th District (NO
07 7th District (NO
08 8th District (NO
09 9th District (NO
10 10th District (NO
11 llth District (NO
12 12th District (NO
Effective Date: 1/31/93 Release Number: 2.00 P»oe: VI - 419
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, PIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Commentls)
State of North Dakota (ND)
00 At Large (ND) One Representative
Effectiv »e: 1/31/93 Release Number: f "» P»oe: VI - 4ZO
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
_._..«•»•••»«•« — — — — — ——••—— »— — — »••»» — • •— — » «««««••••«•— MM •« • «_•_»••«
State of Nebraska (NE)
01 1st District (NE)
02 2nd District (NE)
03 3rd District (NE)
Effective Date: 1/31/93 Release Number: 2.00 Paw VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507,, FIPS PUB 9, Federal Congressional District Codes (103rd Congress),
Code Value Associated Description Comment!s)
State of New Hampshire (NH)
01 1st District (NH)
02 2nd District (NH)
Effectiv e: 1/31/93 Release Number:, Page: VI - 422
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9> Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
State of New Jersey (NJ1
01 1st District (NJ)
02 2nd District (NJ)
03 3rd District (NJ)
04 4th District (NJ)
05 5th District (NJ)
06 6th District (NJ)
07 7th District (NJ)
08 8th District (NJ)
09 9th District (NJ)
10 10th District (NJ)
11 llth District (NJ)
12 12th District (NJ)
13 13th District (NJ)
Effective Date: 1/31/93 Release Number: 2.00 Pane* VI - 423
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9> Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comnent(s)
State of New Mexico (NN)
01 1st District (Ml)
OZ 2nd District (MM)
03 3rd District (NMI
Effectiv
-------
Section VI. List* of Acceptable Cede Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!sI
State of Nevada (NV)
01 1st District (NV)
02 2nd District (NV)
Effective Date: 1/31/91 Release Number: 2.00 Pao»: VI - «2S
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of NeN York INT)
01 1st District CN\T)
02 2nd District (NY)
03 3rd District (NY)
0*i 4th District (NY)
OS 5th District (NY)
06 6th District (NY)
07 7th District (MY)
06 8th District (NY)
09 9th District (NT)
10 10th District (NY)
11 llth District (NY)
12 12th District (NY)
13 13th District tW)
14 14th District (NY)
15 15th District (NY)
16 16th District (NY)
17 17th District (NY)
16 16th District (NY)
19 19th District (NY)
20 20th District (NY)
21 21st District (NY)
22 22nd District (NY)
23 23rd District (NY)
24 24th District (NY)
25 25th District (NY)
26 26th District (NY)
27 27th District (NY)
2S 28th District (NY)
29 29th District (NY)
30 30th District (NY)
31 31st District (NY)
Effectv ^te: 1/31/93 Release Number: " 10 Pane: VI - • 426
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comirent(s)
State of Ohio (OH)
01 1st District COH)
02 2nd District (OH)
03 3rd District (OH)
04 4th District (OH)
05 5th District (OH)
06 6th District (OH)
07 7th District (OH)
08 8th District (OH)
09 9th District (OH)
10 10th District (OH)
11 llth District (OH)
12 12th District (OH)
13 13th District (OH)
14 14th District (OH)
15 15th District (OH)
16 16th District (OH)
17 17th District (OH)
18 18th District (OH)
19 19th District (OH)
Effective Date: 1/31/93 Release Number: 2.00 Pace: VI - 427
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
____________ HHWW_HH_H«HA«>M«H_H««B ««««•«••«••»«•_» -.••••.«.••••••——••.•••••« —^-. ————«•
State of Oklahoma (OK)
01 1st District (OK)
OZ 2nd District (OK)
03 3rd District (OK)
04 4th District (OK)
05 5th District (OK)
06 6th District (OK)
Effecti- t«: 1/31/93 Release Number: •« Paae: VI - 428
-------
Section VI. Lists of Acceptable Code Values Kith Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comrnent(s)
State of Oregon (ORI
01 1st District (OR)
02 Znd District (OR)
03 3rd District (OR)
04 4th District (OR)
05 5th District (OR)
Effective Datet 1/31/93 Release Number: 2.00 Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Coimnent(s)
»••_*••»«« •••••••••••• — — ••• — • — ——•• — — — — — » — — — ••••— — — —™ — — «» — — — —»^ —••••• — • — •»• — •• — •• — — — — •« ——— — M«
Commonwealth of Pennsylvania (PA)
01 1st District (PA)
02 2nd District (PA)
03 3rd District (PA)
04 4th District (PA)
05 5th District (PA)
06 6th District (PA)
07 7th District (PA)
08 8th District (PA)
09 9th District (PA)
10 10th District (PA)
11 llth District (PA)
12 12th District (PA)
13 13th District (PA)
14 14th District (PA)
15 15th District (PA)
16 16th District (PA)
17 17th District (PA)
1ft 16th District (PA)
19 19th District (PA)
20 20th District (PA)
21 21st District (PA)
Effecti -«te: 1/31/93 Release Number: '0 Paaa: VI - 430
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comnent(s)
Commonwealth of Puerto Rico (PR) U.S. Possession
98 Non-voting Delegate (PR)
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507.. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Coimnent(s)
Republic of Palau IPW) U.S. Possession
99 No Representative (PM)
Effect' >te: 1/31/93 Release Number 1 Pane: VI - 432
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9, Federal Congressional District Codes (103rd Congress]
Code Value Associated Description Comment(s)
State of Rhode Island IR1I
01 1st District (RII
OZ 2nd District (RI)
Effective Date: 1/31/M Release Humbert Z.OO Paae: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes <103rd Congress I
Code Value Associated Description CoimnentJs)
State of South Carolina ISC)
01 1st District CSC)
02 2nd District (SO
03 3rd District ISC)
04 4th District ISC)
05 5th District ISC)
06 6th District ISC)
Eftecti>
«e: 1/31/93 Release Number: ' •• p»a*s VI - 434
-------
Section' VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of South Dakota (SO)
00 At Large (SD) One Representative
Effective Date: 1/31/93 Release Number: 2.00 P«ae: VI - 435
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Conunent(s)
State of Tennessee (TNI
01 1st District (TN)
02 2nd District (TN)
03 3rd District (TN)
04 4th District (TN)
05 5th District (TN)
06 6th District (TN)
07 7th District (TN)
08 6th District (TN)
09 9th District (TN)
Effectv te: 1/31/93 Release Number: Paoe: VI - 436
-------
Section VI. Lists of Acceptable Code Value* with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, TIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
01
02
03
04
05
06
07
06
09
10
11
12
13
14
15
16
17
16
19
20
Zl
22
23
24
25
26
27
26
29
30
State of Texas (TX)
1st District (TX)
2nd District (TX)
3rd District (TX)
4th District (TX)
5th District (TX)
6th District (TX)
7th District (TX)
6th District (TX)
9th District (TX)
10th District (TX)
llth District (TX)
12th District (TX)
13th District (TX)
14th District (TX)
15th District ITX)
16th District (TX)
17th District (TX)
16th District (TX)
19th District (TX)
20th District (TX)
21st District (TX)
22nd District (TX)
23rd District (TX)
24th District (TX)
25th District (TX)
26th District (TX)
27th District (TX)
26th District (TX)
29th District (TX)
30th District (TX)
Effective Date: 1/31/93
Release Number: 2.00
Page: VI - 437
-------
Section VI. Lists of Acceptable Cod* Values with Associated Descriptions
C. Detailed Lists of Coda Values
Table 0507* FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!s)
U.S. Minor Outlying Areas U.S. Possessions
99 No Representative (UN)
Effect* ite: 1/31/93 Release Number "0 Pane: VI - 438
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Oelailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comnent(s)
State of Utah CUT)
01 1st District IUT)
02 2nd District (UT)
03 3rd District (UT)
Effective Dat«: 1/31/93 Release Humbert 2.00 Paae: VI - 439
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507* FIPS PUB 9, Federal Congressional District Codes (103rd Congress)„
Code Value Associated Description Comment!s>
__ — __„_»„»— .__...*..«««•___••»—«—— — « — •»••••-»•••••» — « — »•• —• — » — •• — — — — — — • — • — — — — — — ••.•••«• — ——«
Commonwealth of Virginia (VA)
01 1st District (VA)
02 2nd District (VA)
03 3rd District (VA)
04 4th District (VA)
05 5th District (VA)
06 6th District (VA)
07 7th District (VA)
08 Ath District (VA)
09 9th District (VA)
10 10th District (VA)
11 llth District (VA)
Effect*' »e: 1/31/93 Release Number: Paoe: VX -
-------
Section VI: Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
Virgin Islands of the U.S. (VI) U.S. Possession
90 Non-voting Delegate (VI)
Effective Octet 1/31/93 Release Numbert 2.00 P»oe: VI -
-------
Section VI. Lists of Acceptable Code Values Kith Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FTPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment!»)
State of Vermont (VT>
00 At Large IVT) One Representative
Effectiv 'e: 1/31/93 Release Number: Paoe: VI -
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. D-stailed Lists of Code Values
Table 0507. FIPS PUB 9. Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Comment(s)
State of Washington (HA)
01 1st District (HA)
02 2nd District (HA)
03 3rd District (HA)
04 4th District (HA)
05 5th District (HA)
06 6th District (MA)
07 7th District (HA)
06 8th District (HA)
09 9th District (HA)
effective Oatei 1/31/93 Release Numberi 2.00 Paae: VX - 443
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507i FIPS PUB 9, Federal Congressional District Codes (103rd Congress)
Code Value Associated Description Conment(s)
State of Wisconsin (HI)
01 1st District (NI)
02 2nd District (MI)
03 3rd District (HI)
04 4th District (HI)
05 5th District (HI)
06 6th District (HI)
07 7th District (HI)
00 6th District (HI)
09 9th District (HI)
Effecti- -
-------
Section Vl. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FTPS PUB 9. Federal Congressional District Codes 1103rd Congress)
Code Value Associated Description Comment(s)
State of Hesl Virginia
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0507, FIPS PUB 9( Federal Congressional District Codes 1103rd Congress)
Code Value Associated Description Comment(s)
State of Myoning (MY)
00 At Large (MY) One Representative
Effect* te: 1/31/93 Release Number.* Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508i State-specific County Codes
Code Value Associated Description Comment! s>
Boroughs/Census Areas of Alaska (AKI FIPS codes utilized - See Table 0509
Counties of Alabama IAL) FIPS codes utilized - See Table 0509
Effective Date: 1/31/93 Release Number: 2.00 Pace: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!a)
001
002
003
004
005
006
007
000
009
010
Oil
012
013
014
015
016
017
oie
019
020
021
022
023
024
025
026
027
026
029
030
031
032
033
034
035
036
037
te: 1/31/93
Counties of Arkansas (
Arkansas (AR)
Ashley (AR)
Baxter (AR)
Benton (AR)
Boone (AR)
Bradley (AR)
Calhoun (AR)
Carroll (AR)
Chi cot (AR)
Clark (AR)
Clay (AR)
Cleburne (AR)
Cleveland (AR)
Columbia (AR)
Corway (AR)
Crai ahead (AR)
Crawford (AR)
Crittenden (AR)
Cross (AR)
Dallas (AR)
Desna (AR)
Drew (AR)
Faulkner (AR)
Franklin (AR)
Fulton (AR)
ear land (AR)
Grant (AR)
Greene (AR)
Hemps tead CAR)
Hot Spring (AR)
Howard (AR)
Independence (AR)
Izard (AR)
Jackson (AR)
Jefferson (AR)
Johnson (ARj
Lafayette (AR)
AR) FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2^0 Pi
Effectiv te: 1/31/93 Release Number: 2^0 Paoe: VI - 448
-------
Section' VI. Lists of Acceptable Code Values Mith Associated Descriptions
C. Detailed Lists of Code Values
Table 0508• State-specific County Codes
Code Value Associated Description Comment*s)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
064
065
066
067
068
069
070
071
072
073
Note: This list begins on VI - 448
Counties of Arkansas CAR)
Lawrence (AR)
Lee (AR)
Lincoln
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
Note: This list begins on VI - 448
Counties of Arkansas CAR) FIPS
Code
074 Woodruff (AR) 147
075 Yell (AR) 149
Effect!' te: 1/31/93 Release Number: Pane: VI - 450
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0509, State-specific County Codes
Code Value Associated Description Comment!»)
Districts/Islands of American Samoa (ASI FIPS codes utilized - See Table 0509
Effactive Oatet 1/31/93 Release Number: 2.00 Paoei VI - 451
-------
Section VI. Lists of Acceptable Code Values Mith Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
Counties of Arizona (AZ) FIPS
Code
01 Apache (AZ) 001
02 CochisB IAZ) 003
03 Coconino (AZ) 005
04 Gila (AZ) 007
i
05 Graham (AZ) 009
06 Greenlee (AZ) Oil
07 Haricopa (AZ) 013
06 Mohave (AZ) 015
09 Navajo (AZ) 017
10 Pima (AZ) 019
11 Final (AZ) 021
12 Santa Cruz (AZ) 023
13 Yavapai (AZ) 025
14 Yuma (AZ) 027
15 La Paz (AZ) 012
19 naricepa (AZ) 013
County 07 (tlaricopa) Overflow
20 Pi ma (AZ) 019
County 10 (Pina) Overflow
Effecti> te: 1/31/93 Release Number:,-' '•» Paoe: VI - 452
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
001
002
003
004
005
006
007
ooa
009
010
Oil
012
013
014
015
016
017
016
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
Counties of California (CA>
Alameda (CA)
Alpine (CA)
Amsdor (CA)
Butt* (CA)
Calaveras (CA)
Colusa (CA)
Contra Cost* (CA)
Del Norte (CA)
El Dorado (CA)
Fresno (CAI
Clem (CA)
Humboldt (CA)
Imperial (CA)
Inyo (CAI
Kern (CA)
Kings (CA)
Lake (CA)
Lassen (CA)
Los Angeles (CA)
Madera (CA)
narin (CA)
Mariposa (CA)
Mendocino (CA)
Merced (CA)
Modoc (CA)
Mono ICA)
Monterey (CA)
Napa ICA)
Nevada (CA)
Orange ICA)
Placer ICA)
Pluma* ICA)
Riverside (CA)
Sacramento (CA)
San Bent to (CA)
San Bernardino ICA)
FTPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063.
065
067
069
071
037 San Diego (CA) 073
Effective Date: 1/31/91 Release Numberi 2.00 Pace: VI - 453
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508» State-specific County Codes
Code Value Associated Description Comment(s)
Note: This list begins on VI - 453
Counties of California (CA) PIPS
Coda
038 San Francisco (CA) 075
039 San Jooquin (CA) 077
040 San Luis'Obispo (CA) 079
041 San riateo (CA) 061
042 Santa Barbara (CA) 083
043 Santa Clara (CA) 065
044 Santa Cruz (CA) 087
045 Shasta (CA) 069
046 Sierra (CA) 091
047 SicKiyou (CA) 093
046 Solano (CA) 095
049 Sonoma (CA) 097
050 Stanislaus (CA) 099
051 Sutter (CA) 101
052 Tehana (CA) 103
053 Trinity (CA) 105
054 Tulare (CA) 107
055 Tuolumne (CA) 109
056 Ventura (CA) 111
057 Yolo (CA) 113
058 Tuba (CA) 115
Effective P-' • 1/31/93 Release Number: 2.0' Page: VI - '• 454
-------
Section' VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. Stats-specific County Codes
Code Value Associated Description Comment(s)
001
002
00)
004
005
006
007
005
009
010
Oil
012
013
014
015
016
017
010
019
020
021
02Z
023
024
025
026
027
028
029
030
031
032
033
034
035
036
Counties of Colorado (C0>
Adams (CO)
Alamosa (CO)
Arapahoa (CO)
Archuleta (CO)
Boca ICO)
Bant (CO)
Boulder (CO)
Chaffee (CO)
Cheyenne (CO)
Clear Creek (CO)
Conejos (CO)
Cost ilia (CO)
Crowley (CO)
Custer (CO)
Delta (CO)
Denver (CO)
Dolores (CO)
Douglas (CO)
Eagle (CO)
Elbert (CO)
El Paso (CO)
Fremont (CO)
Garfield (CO)
Gilpin (CO)
Grand ICO)
Gunniaon ICO)
Hinsdole (CO)
Huerfano (CO)
Jackson ICO)
Jefferson (CO)
Kiow* (CO)
Kit Carson ICO)
Lake ICO)
La Plata (CO)
Larimer (CO)
Las Aninas (CO)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
• 041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
037 Lincoln (CO) 073
Effective Date: 1/31/93 Release Number: 2.00 Paqe: VI - 455
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Conmientls)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
Note: This list begins on VI - 455
Counties of Colorado (CO)
Logan (CO I
Mesa (CO)
Mineral 4 CO)
Moffet (CO)
Montezuma (CO)
Montros* (CO)
Morgan (CO)
Otero (CO)
Ouray (CO)
ParK (CO)
Phillips (CO)
Pitkin (CO)
Prowers (CO)
Pueblo (CO)
Rio Blanco (CO)
Rio Grande (CO)
Routt (CO)
Saguach* (CO)
San Juan (CO)
San Miguel (CO)
Sedgwicfc (CO)
Summit (CO)
Taller (CO)
Washington (CO)
Held (CO)
Yuma (CO)
FIPS
Code
075
077
079
081
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
Effective ' • 1/31/93 Release Number: 2 Paqe: VI - 456
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
Counties of Connecticut (CT) FIPS codes utilized - See Table 0509
County Equivalent for the District of
Columbia (DC) FIPS codes utilized - See Table 0509
Countturf of Delaware IDE) FIPS codes utilized - See Table 0509
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 457
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!9)
01
02
03
04
05
06
07
06
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
29
26
27
26
29
30
31
32
33
34
35
36
37
1/31/93
Counties of Florida (FL)
Alachuo (FL)
BaKer (FL)
Bay (FL)
Bradford IFL)
Brevard (FL)
Broward IFL)
Calhoun IFL)
Charlotte (FL)
Citrus (FL)
Clay (FL)
Collier (FL)
Columbia (FL)
Dade (FL)
OeSoto (FL)
Dixie IFL)
Duval IFL)
Eicambia (FL)
Flagler (FL)
Franklin IFL)
Gadsden IFL)
Gilchri»t (FL)
Glades (FL)
Gulf (FL)
Hamilton (FL)
Hardee (FL)
Hendry (FL)
Hernando (FL)
Highlands (FL)
Hillsborough (FL)
Holmes (FL)
Indian River (FL)
Jackson (FL)
Jefferson (FL)
Lafayette (FL)
Lake (FL)
Lee (FL)
Leon (FL)
FTPS
Code
001
003
005
007
009
on
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2 Pai
Effective : 1/31/93 Release Number: 2 Paae: VI - • 458
-------
Section VT. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0506, State-specific County Codes
Code Value Associated Description Commentls)
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
Note: This list begins on VI - 458
Counties of Florida (FL)
Levy CFL)
Liberty (FL)
HadisonMFL)
Manatee (FL)
Marion (FL)
Martin (FL)
Monroe (FL)
Nassau (FL)
Okeloosa (FL)
Okeechobee IFL)
Orange (FL)
Osceola (FL)
Palm Beach (FL)
Pasco (FL)
Pinellas (FL)
Polk (FL)
Putnam (FL)
St Johns (FL)
St Lucie (FL)
Santa Rose (FL)
Sarasote (FL)
Seminole (FL)
Sumter (FL)
Siaiannee (FL)
Taylor (FL)
Union (FL)
Volusia (FL)
Hakulla (FL)
Walton (FL)
Washington (FL)
FIPS
Code
075
077
079
081
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
Effective Datet 1/31/93 Release Number* 2.00 Paqe: VI - 459
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508i State-specific County Codes
Associated Description Comracnt(s)
States of the Federated States
of Micronesia (FHI
FIPS codes utilized - See Table 0509
Counties of Georgia (GA)
County Equivalent for Guam (GU)
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
Effective r
1/31/93
Release Number: i.f
Page: VI - '460
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508• State-specific County Codes
Code Value Associated Description Comment!»)
Counties of Hawaii (HI) FIPS
Code
001 Hawaii IHI> 001
002 Maui (HI) 009
naui includes Kalawao (Hit 005
003 Honolulu (HI) 003
DO* Kauai «HI) 007
Effective Oatet 1/31/93 Release Number: 2.00 Paoe: VI - 461
-------
Section VI. Lists of Acceptable Code Values with A-.ociated Descriptions
C. Detailed Lists of Code Values
Table 0508» State-specific County Codes
Code Value Associated Description Comment(s)
01
02
03
04
05
06
07
08
09
10
11
12
13
1*
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
1/31/93
Counties of Iowa IIA)
Adair (IA)
Adams IIA)
Allamakee (IA)
Appanoose (IA)
Audubon (IA)
Benton (IA)
Black Hawk (IA)
Boone (IA)
Bremer (IA)
Buchanan (IA)
Buena Vista (IA)
Butler (IA)
Calhoun (IAI
Carroll (IA)
Cass (IA)
Cedar (IA)
Cerro Sordo (IA)
Cherokee (IA)
ChickasaM (IA)
Clarke (IA)
Clay (IA)
Clayton (IA)
Clinton (IA)
Cranford (XA)
Dallas (IA)
Davis (IA)
Decatur (IA)
Delaware (IA)
DM Hoines (XA)
Dickinson (IA)
Dubuque (IA)
Emmet (IA)
Fayette (XA)
Floyd (IA)
Franklin (IA)
Fremont (IA).
Greene (IA)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2.' Pa
Effective r 1/31/93 Release Number: 2.' Paae: VI - -462
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table .05081 State-specific County Codes
Code Value Associated Description Conmentls)
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
Note: This list begins on VI - 462
Counties of Iowa (IAI
Grundy IIA)
Guthrie IIA)
Hamilton (IA)
Hancock (IA)
Hardin (IA)
Harrison (IA)
Henry (ZA)
Howard (IA)
Humboldt (IA)
Ida (IA)
Iowa (IA)
Jackson (IA)
Jasper (IA)
Jefferson (IA)
Johnson (IA)
Jones (ZA)
Keokuk (IA)
Kossuth (IA)
Lee (IA)
Lim (ZA)
Louisa (IA)
Lucas (IA)
Lyon (IA)
Madison (IA)
Mahaska (IA)
tori on (IA)
Marshall (IA)
Mills (IA)
Mitchell (ZA)
Monona (IA)
Monroe (IA)
Montgomery (IA)
Muscat ine (IA)
O'Brien (IA)
Oseeola (IA)
Page (IA)
FIPS
Code
075
077
079
061
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 463
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table OSOBt State-specific County Codes
Code Value Associated Description Comment(s)
74
75
76
77
78
79
60
81
82
83
84
85
66
67
68
69
90
91
92
93
94
95
96
97
98
99
Note: This list begins on VI - 462
Counties of loua (IA)
Palo Alto (IA)
Plymouth (IA)
Pocahontas (IA)
Polk (IA)
Pottawattanie (IA)
Poueshiek (IA)
Ringgold (IA)
Sac (IA)
Scott (IA)
Shelby (IA)
Sioux (IA)
Story (IA)
TMM (IA)
Taylor (IA)
Union (IA)
Van Buren (IA)
Hapello (IA)
Harren (IA)
Washington (IA)
Hayne (IA)
Webster (IA)
Hinnebago (IA)
Wimeshiek (IA)
Noodbury IIA)
North (IA)
Wright (IA)
FIPS
Code
147
149
151
153
155
157
159
161
163
165
167
169
171
173
175
177
179
161
183
185
187
189
191
193
195
197
Effective 1/31/93 Release Number: 2. Pacw: VI - 464
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!*}
Counties of Idaho (ID) FIPS codes utilized - See Table 0509
Counties of Illinois (ID FIPS codes utilized - See Table 0509
Effective Date: 1/31/93 Release Humbert 2.00 Paoe: VI - 465
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
001
002
003
004
005
006
007
008
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
037
1/31/93
Counties of Indiana (IN)
Adam (IN)
Allen (IN)
Bartholomew (IN)
Benton (IN)
Blackford (IN)
Boone (IN)
Brown (IN)
Carroll (IN)
Cams (IN)
Clark (IN)
Clay (IN)
Clinton (IN)
Crawford (IN)
Daviess (IN)
Dearborn (IN)
Decatur (IN)
De Kalb (IN)
Delaware (IN)
Dubois (IN)
Elkhart (IN)
Fayette (IN)
Floyd (IN)
Fountain (IN)
Franklin (IN)
Fulton (IN)
Gibson (IN)
Grant (IN)
Green* (IN)
Hamilton (IN)
Hancock (IN)
Harrison (IN)
Hendricks (IN)
Henry (IN)
Howard (IN)
Hunt ing ton (IN)
Jackson (IN)
Jasper (IN)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2.' P«
Effective ' 1/31/93 Release Number: 2.' Paoe: VI - 466
-------
Section VI. List* of Acceptable Code Values with Associated Description*
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
038
039
040
041
042
043
044
045
046
047
046
049
050
051
052
053
054
055
056
057
056
059
060
061
062
063
064
065
066
067
068
069
070
071
072
073
Note: This list begins on VI
Counties of Indiana (IN)
Jay (IN)
Jefferson (IN)
Jennings' (IN)
Johnson (IN)
Knox (IN)
Kosciuako (IN)
LaGrange (IN)
Lake (IN)
La Porte (IN)
Lawrence (IN)
Madison (IN)
Marion (IN)
Marshall (IN)
Martin (IN)
Miami (IN)
Monroe (IN)
Montgomery (IN)
Morgan (IN)
Newton (IN)
Noble (IN)
Ohio (IN)
Orange (IN)
ONen (IN)
Parke (IN)
Perry (IN)
Pike (IN)
Porter (IN)
Posey (IN)
Pulaski (IN)
Putnam (IN)
Randolph (IN)
Ripley (INT
Rush (IN)
St Joseph (IN)
Scott (IN)
Shelby (IN)
- 466
FIPS
Code
075
077
079
081
083
085
087
069
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective Date: 1/31/93
Release Number: 2.00 ''•a*' VI - 467
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description CommentCsl
Note: This list begins on VI - 466
Counties of Indiana (IN) FIPS
Code
074 Spencer (IN) 147
075 Starke (IN) 1*9
076 StaubenMIN) 151
077 Sullivan (IN) 153
076 Switzerland (INI 155
079 Tippecanoa (IN) 157
060 Tipton (IN) 159
061 Union (IN) 161
062 Vanderburgh (IN) 163
063 Vet-million (IN) 165
064 Vigo (IN) 167
065 Habash (IN) 169
066 Harren (IN) 171
087 Narrick (IN) 173
068 Washington (IN) 175
069 Wayne (IN) 177
090 Nells (IN) 179
091 White (IN) 161
09Z Whitley (IN) 163
Effective r 1/31/93 R«lea«a Number: Z.f P«««s v* -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codes
Code Value Associated Description Comment(s)
Counties of Kansas (KS) FIPS codes utilized - See Table 0509.
Effective Date: 1/31/9} Release Number: 2.00 Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0500. State-specific County Codes
Code Value Associated Description Conmentfs)
001
002
003
004
005
006
007
006
009
010
Oil
012
013
014
015
016
017
016
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
037
'ate: 1/31/93
Counties of Kentucky 1
Adair (KY)
Allen (KY)
Anderson (KY)
Ballard (KY)
i
Barren (KY)
Bath (KY)
Bell (KY)
Boone (KY)
Bourbon (KY)
Boyd (KY)
Boyle (KY)
Bracken (KY)
Breath! tt (KY)
Breckinridge (KY)
Bullitt (KY)
Butler (KY)
Caldmll (KY)
Calloway (KY)
Campbell (KY)
Carlisle (KY)
Carroll (KY)
Carter (KY)
Casey (KY)
Christian (KY)
Clark (KY)
Clay (KY)
Clinton (KY)
Crittenden (KY)
Cumberland (KY)
Daviess (KY)
Edmonson (KY)
Elliott (KY)
Estill (KY)
Fayette (KY)
Fleming (KY)
Floyd (KY)
Franklin (KY)
KY) FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number 10 P«
Effect 'ate: 1/31/93 Release Number ^0 Pace: VI - «70
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
036
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
056
059
060
061
062
063
064
065
066
067
066
069
070
071
072
073
Note: This list begins on VI - 470
Counties of Kentucky (KY)
Fulton (KY)
Gallatin (KY)
Garrard (KY)
Grant (KY)
Graves (KY)
Grayson (KY)
Green (KY)
Greenup (KY)
Hancock (KY)
Hardin (KY)
Harlan (KY)
Harrison (KY)
Hart (KY)
Henderson (KY)
Henry (KY)
Hicknan (KY)
Hopkins (KY)
Jackson (KY)
Jefferson (KY)
Jessamine (KY)
Johnson (KY)
Kenton IKY)
Knott (KY)
Knox IKY)
LaRue (KY)
Laurel (KY)
Lawrence (KY)
Lee (KY)
Leslie (KY)
Letcher (KY)
Lewis (KY)
Lincoln (KYJ
Livingston (KY)
Logan IKY)
Lyon (KY)
HcCracken (KY)
FIPS
Code
075
077
079
061
063
065
067
069
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 471
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Coda Value
Table 0508, State-specific County Codes
Associated Description
t(s)
07*
075
076
077
078
079
OBO
001
062
063
064
065
086
087
068
069
090
091
092
093
094
095
096
097
09S
099
100
101
102
103
104
105
106
107
108
109
Note: This list begins on VI - 470
Counties of Kentucky (KYI
McCreary (KYI
tic Lean IKYI
Madison
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
Note: This list begins on VI - 470
Counties of Kentucky
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0506. State-specific County Codes
Code Value Associated Description Comment! s)
Parishes of Louisiana (LA) FIPS codes utilized - See Table 0509
Counties of Massachusetts IMA). FIPS codes utilized - Sea Table 0509
Effective 1/31/93 Release Number: 2 Pane: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Cod* Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
001
002
003
004
005
006
007
006
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
Counties of Maryland IHD)
Allegany (MD)
Anne Arundel (MD)
Baltimore (MD)
Calvert (MD)
Caroline (MD)
Carroll (MD)
Cecil (MD)
Charles (MD)
Dorchester (MD)
Frederick (MD)
Garrett (MD)
Harford (MD)
Howard (MD)
Kent (MD)
Montgomery (MD)
Prince George's (MD)
Queen Anne's (MD)
St Mary's (MD)
Somerset (MD)
Talbot (MD)
Washington (NO)
Hicomico (MD)
Worcester (MD)
InfJaMtMwIftM** OS 4S*»a* M< Mnvul ••**! f MO 1
naepenaenT i»i TICS OT naryiflnci inn i
FIPS
Code
001
003
005
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
FIPS
Code
030 Baltimore City (MD) 510
Effective Date: 1/31/93 Release NumberI 2.00 Pane: VI - 475
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 050d> State-specific County Codes
Code Value Associated Description Comment!si
•VH*KHHBV*»V »—————— —••«« — ™™ —— ——• — •• — — — — •••»•• — »•• — ————• — — •» — »— —^— —•»••••.».•.•• •, •••«••. — • — — — ••——•- — — — —
Counties of Maine (HE) FIPS codes utilized - See Table 0509
Municipalitias/lslands/Atolls of the
Republic of the Marshall Islands IHH1 FIPS codes utilized - See Table 0509
Effective 1/31/93 Release Number: 2.' Pane: VI - -476
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
001
002
003
004
005
006
007
008
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
Counties of Michigan (HI)
Aleona (MI)
Alger (HI)
Allegan (MI)
Alpena (HI)
Antrim (HI)
Arenac (HI)
Baraga (HI)
Barry (HI)
Bay (HI)
Benzie (HI)
Berrien (HI)
Branch (HI)
Calhoun (HI)
Cass (HI)
Charlevoix (HI)
Cheboygan ( HI )
Chippewa (HI)
Clare (HI)
Clinton (HI)
Crawford (HI)
Delta (HI)
Dickinson (HI)
Eaton (HI)
Emmet (HI)
Genesee (HI)
Gladwin (HI)
Gogebic (HI)
Grand Traverse (MI)
Gratiot (HI)
Hillsdale (HI)
Houghton (HI)
Huron (HI)
Ingham (HI)
Ionia (HI)
losco (HI)
Iron (HI)
FIPS
Coda
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
037 Isabella (HI) 073
Effective Date: 1/31/93 Release Number: 2.00 Paqe: VI - 477
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
064
065
066
067
068
069
070
071
072
073
Note: This list begins on VI - 477
Counties of Michigan (MI)
Jackson (MI)
Kalamazoo
-------
Section VI. Lists of Acceptable Code Values uith Associated Descriptions
C. Detailed Lists of Code Values
Table 0506, State-specific County Codes
Code Value Associated Description Commentls)
Note: This list begins on VI - 477
Counties of Michigan (HI) FIPS
Coda
074 St Clair (HI) 147
075 St Joseph (NX) 149
076 Sanilac'(HI) 151
077 Schoolcraft (HI) 153
076 Shfaiiassee (HI) 155
079 Tuscola (HI) 157
080 Van Buren (HI) 159
061 Hashtenaw (HI) 161
002 Wayne (HI) 163
063 Hexford (HI) 165
Effective Date: 1/31/93 Release Number: 2.00 Page: VI - 479
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Associated Description
Conunentls)
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
Counties of Minnesota (HN)
Counties of Missouri (MO)
Independent Cities of Missouri (MO)
Municipalities of the Northern
Mariana Islands IMP)
Counties of Mississippi (MS)
Counties of Montana (HT)
Effective ' • 1/31/93
Release Number: 2.
Pacw: VI - 460
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0500, State-specific County Codes
Code Value Associated Description Comment(s)
000
001
002
003
004
005
006
007
ooa
009
010
Oil
012
013
014
015
016
017
016
019
020
021
022
023
024
025
026
027
026
029
030
031
032
033
034
035
Counties of North Carolina (NC)
Yancey (NC)
Alananca (NC)
Alexander (NC)
Alleghany (NC)
Anson (NC)
Ash* (NC)
Avery (NC)
Beaufort (NC)
Bertie (NC)
Bladen (NC)
BrunsHicK (NC)
Buncombe (NC)
Burke (NC)
Cefaarrus (NC)
CaldNell (NC)
Cemden (NC)
Certeret (NC)
Casiiell INC)
CataHba (NC)
Chatham (NC)
Cherokee (NC)
Chouan (NC)
Clay (NC)
Cleveland (NC)
Coluabus (NC)
Craven INC)
Cumberland (NC)
Currituck (NC)
Dare (NC)
Davidson (NC)
Davie (NC)
Duplin (NC)
Durhan (NC* .
Edgeeoobe (NC)
Forsyth (NC)
Franklin (NC)
F1PS
Code
199
001
003
005
007
009
OU
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
036 Gaston INC) 071
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 481
-------
Section VI. Lists of Acceptable Code Values with Associated Description!
C. Detailed Lists of Code Values
Table 0506, State-specific County Codes
Code Value Associated Description Comment(s)
037
036
039
040
041
042
043
044
045
046
047
045
049
050
051
052
053
054
055
056
057
056
059
060
061
Hk»
VV4
063
064
065
066
067
068
069
070
071
072
Note: This list begins on VI - 461
J
Counties of North Carolina (NCI
Gates INC)
Graham (NC)
Granvill* (NC)
Greene INC)
Guilford INC)
Halifax (NC)
Harnett INC)
HayMOod (NC)
Henderson INC)
Hertford (NC)
HoKe (NC)
Hyde INC)
Iredell (NC)
JacKson (NC)
Johnston (NC)
Jones (NC)
Lee INC)
Lenofr (NC)
Lincoln INC)
McDowell (NC)
Macon INC)
Madison INC)
Martin (NC)
Mecklenburg INC)
Mitchell INC)
Mantonnoru 1 NT 1
Moore INC)
Nash INC)
Hen Hanover (NC)
Northampton (NC)
OraloM (NC)
Orange INC)
Pamlico (NC)
Pasquotank-INC)
Fender INC) '
Perquinans INC)
FIPS
Code
073
075
077
079
081
083
065
087
069
091
093
095
097
099
101
103
105
107
109
111
113
.115
117
119
121
123
A CiV
125
127
129
131
133
135
137
139
141
143
Effective -: 1/31/93 Release Number: 2 Paoe: VI -' • 482
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Coimnent(s)
073
074
075
076
077
078
079
080
081
082
083
084
065
086
087
088
089
090
091
092
093
094
095
096
097
098
099
Note: This list begins on VI -
Counties of North Carolina (NC
Person (NO
Pitt (NC)
Polk (NCt
Randolph (NC)
Richmond (NC)
Robeaon (NO
Rockinghan (NCI
Rowan (NC)
Rutherford (NC)
Sampson (NO
Scotland (NO
Stanly (NO
Stokes (NO
Surry (NO
Suain (NO
Transylvania (NO
Tyrrell (NO
Union (NC)
Vance (NO
Make (NO
Harren (NO
Washington (NO
Hatauga (NO
Kayne (NO
Hi Ikes (NO
Wilson (NO
Yadkin (NO
• 481
) FIPS
Code
145
147
149
151
153
155
157
159
161
163
165
167
169
171
173
175
177
179
181
183
185
187
189
191
193
195
197
Effective Oatei 1/31/93 Release Nuoberi 2.00 P»oei VI - 483
-------
Saction VI. Lists of Acceptable Cede Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!*)
Counties of North Dakota (ND) FIPS
001
002
003
004
005
006
00?
006
009
010
Oil
012
013
014
015
016
017
016
019
020
021
022
023
024
025
026
027
026
029
030
031
032
033
034
035
036
037
• 1/31/95
Adams (NO)
Barnes (ND)
Benson 1NDI
Billing* (NO)
Bottineau (ND)
Bowman (ND)
Burke (ND)
Burleigh (ND)
CMS IND)
Cavalier (ND)
Dickey (ND)
Divide (ND)
Dunn (ND)
eddy (ND)
Cannons (ND)
Foster (NDI
Golden Valley (ND)
Grand Forks (ND)
Grant (ND)
Griggs (ND)
Hettinfler (ND)
Kidder (ND)
LeHoure (ND)
Logan (ND)
McHenry (ND)
nclntosh (ND)
HcKenxic (ND)
McLean (ND)
Mercer (ND)
ftor ton (ND)
Mountrail IND)
Nelson (ND)
Oliver (ND)
Penbina (ND)
Pierce (ND)
Ramsey (ND)
Ransom (ND)
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2.«" P«
Effective •* • 1/31/93 Release Number: 2.''" . Paoe: VI - 4B4
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Litts of Coda Values
Table 0508. State-specific County Codes
Code Value Associated Description Comment! 9-)
Note: This list begins on VI - 4B4
Counties of North Dakota (NO) FIPS
Code
036 Renville (ND> 075
039 Richland 077
040 Rolette (ND) °79
041 Sargent (ND) 061
042 Sheridan (MM 083
043 SiauK I NO I 085
044 Slope (ND) 067
045 Stark (NDI 069
046 Stecle (ND) 091
047 Stutsnon (ND) 093
048 Tenner (ND) 095
049 Traill (ND) 097
050 Walsh (ND) 099
051 Hard (NO) 101
052 Hells (ND) 101
053 Hilliaos (NDI 105
Effective Date: 1/31/93
Release Number: 3.00 Pwe: VI " *85
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0500* State-specific County Codes
Code Value Associated Description- Comment(s)
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
16
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
: 1/31/93
Counties of Nebraska
Adams INE)
Antelope (NE)
Arthur (NE)
Banner (NE)
Blaine (NE)
Boor* (NE)
Box Butte (NE)
Boyd (NE)
Brown (NE)
Buffalo (NE)
Burt (NE)
Butler (NE)
Cass (NE)
Cedar (NE)
Chase INE)
Cherry (NE)
Cheyenne (NE)
Clay (NE)
Col fax (NE)
Cuming (NE)
Custer (NE)
Dakota (NE)
Dawes (NE)
Dauson (NE)
Deuel (NE)
Dixon (NE)
Dodge (NE)
Douglas (NE)
Dundy (NE)
Fillnore (NE)
Franklin (NE)
Frontier (NE)
Furnas (NE)
Gage (NE)
Garden (NE)
Garfield (NE)
Gosper INE)
(NE) FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2 *•" Pa
Effective -: 1/31/93 Release Number: 2 *•- Paoe: VI - 486
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
38
39
40
41
42
43
44
45
46
47
46
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
Note: This list begins on VI - 486
Counties of Nebraska (NE)
Grant (NE)
Greeley (NE)
Hall (ME I
Hamilton (NE)
Harlan (NE)
Hayes (NE)
Hitchcock (NE)
Holt (NE)
Hooker (NE)
Howard (NE)
Jefferson (NE)
Johnson (NE)
Kearney (NE)
Keith (NE)
Key* Poha (NE)
Kinball (NE)
Knox INE)
Lancaster (NE)
Lincoln (NE)
Logan (NE)
Loup (NE)
Madison (NE)
tlcPherson (NE)
Her rick (NE)
Herri 11 (NE)
Nance (NE)
Nemoha (NE)
Nuckolls (NE)
Otoe (NE)
Pawnee (NE)
Perkins INE)
Phelps (NE)
Pierce (NE)
Platte (NE)
Polk (NE)
Red Willow (NE)
FIPS
Code
075
077
079
081
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
119
117
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 487
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Commentls)
Note: This list begins on VI - 486
Counties of Nebraska (ME) FIPS
Code
74 Richardson (NE) 1*7
75 Rock (NE) 149
76 Saline (N5I 151
77 Sarpy INE) 153
78 Sounders (NE) 155
79 Scotts Bluff (NE) 157
SO Seward (NE) 159
61 Sheridan (NE) 161
02 Sherman (NE) 163
63 Sioux (NE) 165
84 Stanton (NE) 167
85 Thayer (NE) 169
86 Thomas (NE) 171
87 Thurston (NE) 173
88 Valley (NE) 175
89 Washington (NE) 177
90 Wayne (NE> 179
91 Webster INE) 181
92 Wheeler (NE) 183
93 York (NE) 185
Effective r 1/31/93 Release Number: 2.09- P"OT! VI '
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508i State-specific County Codes
Code Value Associated Description Comnent(s)
Counties of NBM Hampshire INHJ FIPS codes utilized - See Table 0509
Counties of Nan Jersey INJ) FIPS codes utilized - Sea Table 0509
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 489
-------
Section VI. Lists of Acceptable Code Values with'Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Code*
Code Value Associated Description Comment(s)
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
Counties of New Mexico (NM)
Bernalille (MM)
Catron (Ml)
Chaves (NM)
Colfax rNM)
Curry (MM)
DeBaca (NM)
Dona Ana (NM)
Eddy (NM)
Grant (NM)
Guadalupe (NM)
Harding (NM)
Hidalgo (NM)
Lea (NH)
Lincoln (NM)
Los Alamos (NM)
Luna (NM)
McKinley (NM)
Mora (NM)
Otero (NM)
Quay (NM)
Rio Arriba (NM)
Roosevelt (NM)
Sandoval (NM)
San Juan (NM)
San Miguel (NM)
Santa Fe (NM)
Sierra (NH)
Socorro (NM)
Taoa (NM)
Tor ranee (NM)
Union (NM)
Valencia (NM)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
028
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
33 Cfbola (NM) 006
Effective r • 1/31/93 Release Number: 2.' . Pane: VI - 490
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Cod* Value Associated Description Comnent(sl
Counties of Nevada (NVI FIPS codes utilized - See Table 0509
Independent Cities of Nevada (NV) FIPS codes utilized - See Table 0509
Effective Date: 1/31/93 Release Number: 2.00 Pam: VI - 491
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description ComaientIsI
001
002
003
004
005
006
007
006
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
037
': 1/31/93
Counties of New York (NY)
Albany (NY)
Allegany (NY)
Broome (NY)
Cattaraugus (NY)
Cayuga (NY)
Chautauqua (NY)
Chemung (NY)
Chenango (NY)
Clinton (NY)
Columbia (NY)
Cortland (NY)
Delaware (NY)
Dutchess (NY)
Erie (NY)
Essex (NY)
Franklin (NY)
Fulton (NY)
Genesee (NY)
Greene INY)
Hamilton (NY)
Herkioer (NY)
Jefferson (NY)
Kings (NY)
LeMis (NY)
Livingston (NY)
Madison (NY)
Monroe (NY)
Montgomery (NY)
Nassau (NY)
New York (NY)
Niagara (NY)
Cneida (NY)
Onondaga (NY)
Ontario (NY)
Orange (NY)
Orleans (NYJ.
Oswego (NY)
FTPS
Code
001
003
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
.049
051
053
055
057
059
061
063
065
067
069
071
073
075
Release Number: 2. — Pai
Effective <: 1/31/93 Release Number: 2. — Pane: VZ - 492
-------
Section Vl. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codes
Code Value Associated Description Coimnent(s)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
Note: This list begins on VI - 492
Counties of Net* York (NY)
Otsego (NY)
Putnam (NY)
Queens' (NY)
Rensselaer (NY)
Richmond (NY)
Rockland (NY)
St Laurence (NY)
Saratoga (NY)
Schenectady (NY)
Schoharie (NY)
Schuyler (NY)
Seneca (NY)
Steuben (NY)
Suffolk (NY)
Sullivan (NY)
Tioga (NY)
Tompkins (NY)
Ulster (NY)
Warren (NY)
Washington (NY)
Wayne (NY)
Westchester (NY)
Wyoming (NY)
Yates (NY)
FIPS
Code
077
079
081
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
999 Bronx (NY) 005
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 493
-------
Seeiion VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Cod* Value
Table 0508, State-specific County Codes
Associated Description
Comment!s)
Effective '
001
002
003
004
005
006
007
008
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
026
029
030
031
032
033
034
035
036
037
1/31/93
Counties of Ohio (OH)
Adams (OH)
Allen (OH)
Ashland (OH)
Ashtabule (OH)
Athens (OH)
Auglaize (OH)
Belmont (OH)
Brown (OH)
Butler (OH)
Carroll (OH)
Champaign (OH)
Clerk (OH)
Clernont (OH)
Clinton (OH)
Columbiana (OH)
Coshocton (OH)
Crawford (OH)
Cuyahoga (OH)
Darke (OH)
Defiance (OH)
Delaware (OH)
Erie (OH)
Fairfield (OH)
Fayette (OH)
Franklin (OH)
Fulton (OH)
Gall i a (OH)
Geauga (OH)
Greene (OH)
Guernsey (OH)
Hani 1 ton (OH)
Hancock (OH)
Hardin (OH)
Harrison (OH)
Henry (OH)
Highland (OH)
Hocking (OH)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
04 L.
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
073
Release Number: 2.'"1 Pa<
Paae: VI -• 494
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codes
Code Value Associated Description Connnent(s)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
056
059
060
061
062
063
064
065
066
067
066
069
070
071
072
073
Note: This list begins on VI
Counties of Ohio (OH)
Holmes (OH)
Huron (OH)
Jackson A OH )
Jefferson (OH)
Knox (OH)
Lake (OH)
Laurence (OH)
Licking (OH)
Logan (OH)
Lorain (OH)
Lucas (OH)
Madison (OH)
nahoning (OH)
Marion (OH)
Medina (OH)
rieigs (OH)
Mercer (OH)
Miami (OH)
Monroe (OH)
Montgomery (OH)
Morgan (OH)
Morrow (OH)
Muskingun (OH)
Noble (OH)
Ottawa (OH)
Paulding (ON)
Perry (OH)
Pickamy (OH)
Pike (OH)
Portage (OH)
Preble (OH)
Putnam (OH*
Richland (OH)
Ross (OH)
Sandusky (OH)
Scioto (OH)
- 494
FIPS
Code
075
077
079
081
083
065
087
069
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 495
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table OSOBi State-specific County Codes
Code Value Associated Description Corament(s)
Note: This list begins on VI - 494
Counties of Ohio (OH) FIPS
Code
074 Seneca (OH) 147
075 Shelby (OH) 149
076 Stark (CHI 151
077 Summit (OH) 153
076 Trumbull (OH) 155
079 Tuscarattas (OH) 157
060 Union (OH) 159
061 Van Nert (OH) 161
06? Vinton (OH) 163
063 Harren (OH) 165
064 Washington (OH) 167
065 Hayne (OH) 169
066 Hilliams (OH) 171
087 Nood (OK) 173
066 Hyandot (OH) 175
Effective r 1/31/93 Release Number: I.I" Pace: VI - 496
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 05081 State-specific County Codes
Code Value Associated Description Comment(s)
001
002
003
004
005
006
007
006
009
010
Oil
012
013
014
015
016
017
018
019
020
021
022
023
024
025
026
027
020
029
030
031
032
033
03<»
035
036
Counties of Oklahoma I OKI
Adatr (OK)
Alfalfa (OK)
Atoka (OK)
Beaver (OK)
Beckhaa (OK)
Elaine (OK)
Bryan (OK)
Caddo (OK)
Canadian (OK)
Carter (OK)
Cherokee (OK)
ChoctaM (OK)
Cinarron (OK)
Cleveland (OK)
Coal (OK)
Comanche (OK)
Cotton (OK)
Craig (OK)
Creek (OK)
Ouster (OX)
Delaware (OK)
Dewey (OK)
Ellis (OK)
Gar field (OK)
Garvin (OK)
Srady (OK)
Grant (OK)
Greer (OK)
Harmon (OK)
Harper (OK)
Haskell (OK)
Hughes (OK)
Jackson IOK>
Jeffersbn (OK)
Johnston (OK)
Kay (OK)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
037 Kingfisher (OK) 073
Effective Oatei 1/31/93 Release Numbers 2.00 Pane: VI - 497
-------
Section VI. Lists of Acceptable Coda Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codes
Code Value Associated Description Commentls)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
064
065
066
067
06S
069
070
071
072
073
Note: This list begins on VI - 497
Counties of Oklahoma (OK)
Kiowa (OK)
Lo timer (OK)
Le Flor* (OK)
Lincoln (OK)
Logan (OK)
Love (OK)
Major (OK)
Marshall (OK)
Hayes (OK)
McClain (OK)
rtcCurtom (OK)
Mclntosh (OK)
Murray (OKI
Huskogea (OK)
Noble (OK)
Nowata (OK)
Okfuskee (OK)
Oklahoma (OK)
Oknulsee (OK)
Osaga (OK)
Ottawa (OK)
Pawnee (OK)
Payne (OK)
Pittsburg (OK)
Pontotoe (OK)
PottBHOtoaie (OK)
Pushmatsha (OK)
Roger Hill* (OK)
Rogers (OK)
Seminole (OK)
SequoyaS (OK)
Stephens (OK)
Texas (OK)
Tillnan (OK)
Tulsa (OK)
Wagoner (OK)
FIPS
Code
075
077
079
081
083
065
093
095
097
087
089
091
099
101
103
105
107
109
111
113
115
,117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective >: 1/31/93 Release Number: 2 " Paqe: VI -' • 498
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
Note: This list begins on VI - 497
Counties of Oklahoma (OK) FIPS
Coda
074 Washington (OK) 147
075 Mashtta (OK) 149
076 Hoods (OK> 151
077 Woodward (OK) 153
Effective Date: 1/31/93 Release Number: 2.00 P»e*s VI - 499
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment(s)
001
002
003
004
005
006
007
008
009
010
Oil
012
013
014
015
016
01?
018
019
020
021
022
023
024
025
026
027
028
029
030
031
032
033
034
035
036
Counties of Oregon (OR)
Baker (OR)
Benton (OR)
Claekaaas (OR)
Clatsop (OR).
Columbia (OR)
Coos (OR)
Crook (OR)
Curry (OR)
Deschutes (OR)
Douglas ( OR )
Gillian (OR)
Grant (OR)
Harney (OR)
Hood River (OR)
Jackson (OR)
Jefferson (OR)
Josephine (OR)
Klamath (OR)
Lake (OR)
Lane (OR)
Lincoln (OR)
Linn (OR)
Malheur (OR)
Marion (OR)
HorroM (OR)
Multnooah (OR)
Polk (OR)
Sherman (OR)
Tillamook (OR)
Una t ilia (OR)
Union (OR)
Halloua (OR)
Haseo (OR)
Washington (OR)
Nheeler (OR)
Yamhill (OR*
FIPS
Coda
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
065
067
069
071
Effective 1/31/93 Release Number: 2 Paqe: VI - 500
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508t State-specific County Codes
Associated Description Comment(s)
Counties of Pennsylvania (PA)
Municipios of Puerto Rico (PR)
States o* the Republic of Palau (PH)
Counties of Rhode Island (RI)
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
Effective Date: 1/31/93
Release Number: 2.00
Paae: VI - 501
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508» State-specific County Codes
Code Value Associated Description Comment(s)
01
02
03
04
05
06
07
08
09
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
1/31/93
Counties of South Carolina (SO
Abbeville (SO
A i Ken (SO
Allendale (SO
Anderson (SO
Bamberg (SO
Barnwell (SO
Beaufort (SO
Berkeley (SO
Calhoun (SO
Charleston (SO
Cherokee (SO
Chester (SO
Chesterfield (SO
Clarendon (SO
Col le ton (SO
Darlington (SO
Dillon (SO
Dorchester (SO
Edgefield (SO
Fairfield (SO
Florence (SO
Georgetown (SO
Greenville (SO
Greenwood (SO
Hampton (SO
Kerry (SO
Jasper (SO
Kershaw (SO
Lancaster (SO
Laurens (SO
Lee (SO
Lexington (SO
Marion (SO
Marlboro (SO
McCormick (SO
Newberry (SO
Oconee (SO
Release Number:
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
061
063
067
069
065
071
073
2 Pai
Effective ' • 1/31/93 Release Number: 2 Paoe: VI - 502
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!si
Note: This list begins on VI - 502
Counties of South Carolina (SO FIPS
Code
38 Orangeburg (SO 075
39 Pickers (SO 077
40 Richland »SCI 079
41 Saluda (SCI 081
42 Spartanburg (SCI 063
43 Sumter (SCI 085
44 Union (SO 087
45 Hilliastsburg (SO 089
46 York ISO 091
Effective Data: 1/31/93 Release Number: 2.00 Paae: VI - 503
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codas
Code Value Associated Description Comment!s)
AU
BD
BF
B6
BH
BL
BN
BT
BU
CA
CO
CK
CL
CM
CN
CU
DA
DG
ON
OU
DM
ED
FA
FR
GT
GY
HD
HK
Htl
HR
H3
HT
HU
HY
JA
JE
Counties of South Dakota (SO)
Aurora I SO )
Beadle (SO)
Buffalo (SO)
BrooKings (SO)
Bon Honme (SO)
Brule (3D)
Brown (3D)
Bennett (SO)
Butte (SO)
Campbell (SO)
Codington (SOI
Clark (SO)
Clay (SD)
Charles Mix ISO)
Corson (SO)
Custer (SO)
Day (SD)
Douglas (SD)
Davison (SO)
Deuel (SD)
Dewey (SD)
Edmunds (SO)
Fsulk (SD)
Fall River (SD)
Grant (3D)
Gregory (30)
Hand (SD)
HaaKon (SD)
Namlin (SO)
Harding (SO)
Hanson (SO)
Hutchinson (3D)
Hughes (SO)
Hyde ISO)
Jackson (SD)
Jerauld (SD)
FIP3
Code
003
005
017
Oil
009
015
013
007
019
021
029
025
027
023
031
033
037
043
035
039
041
045
049
047
051
053
059
055
057
063
061
067
065
069
071
073
JN Jones (SD) 075
Effective ' •«: 1/31/93 Release Number: 2.OB. Page: VI - 504
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0506• State-specific County Codes
Code Value Associated Description Comment(s)
KG
LA
LK
LN
LY
MA
ric
no
ML
HP
MR
MT
MY
PE
PK
PT
RB
SA
SN
SP
ST
SU
TO
TR
TU
UN
HL
YA
Note: This list begins on VI - 504
Counties of South Dakota (SD)
Kingsbury (SD)
Laurence (SD)
Lake (3D).
Lincoln (SD)
Lyman (SO)
niraiehahe (SD)
McCook (SD)
Meade (SD)
Marshall (SD)
McPherson (SD)
Miner (SD)
Mellette (SD)
Moody (SD)
Permington (SD)
Perkins (SD)
Potter (SD)
Roberts (SD)
Sanborn (SD)
Shannon (SD)
Spink (SD)
Stanley (SD)
Sully (SD)
Todd (SO)
Tripp (SD)
Turner (SD)
Union (SD)
HalMorth (SD)
Yenkton (SD)
FIPS
Code
077
081
079
083
085
099
087
093
091
089
097
095
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
135
ZB Ziebach (SD) 137
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 505
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508. State-specific County Codes
Code Value Associated Description Comment!s)
Counties of Tennessee (TN> FIPS codes utilized - See Table 0509
Effective •: 1/31/93 Release Number: Z Paoe: VI -'• 506
-------
Section Vl. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0506• State-specific County Codes
Cede Value Associated Description Comment! s>
001
002
003
004
005
006
007
008
009
010
Oil
012
013
014
015
016
017
oia
019
020
021
022
023
024
025
026
027
026
029
030
031
032
033
034
035
036
Counties of Texas (TX)
Anderson (TX)
Andrews (TX)
Angelina (TXI
Aransas (TX)
Archer (TX)
Armstrong (TX)
Atascosa (TX)
Austin (TX)
Bailey (TX)
Bandera (TXI
Bastrop (TXI
Baylor (TX)
Bee (TX)
Bell (TX)
Bexar (TX)
Blanco (TX)
Borden (TXI
Bosque ITX)
Bowie (TXI
Brazoria (TX)
Brazos (TX)
Brews ter (TX)
Briscoe (TX)
Brooks (TX)
Broun (TX)
Burleson (TX)
Burnet (TX)
Caldmll (TXI
Calhoun (TX)
Callahan (TX)
Cameron (TXI
Camp (TX)
Carson (TX)
Cass (TX)
Castro (TX)
Chambers (TX)
FIPS
Code
001
003
005
007
009
Oil
013
015
017
019
021
023
025
027
029
031
033
035
037
039
041
043
045
047
049
051
053
055
057
059
06 1
063
065
067
069
071
037 Cherokee (TX) 073
Effective Date: 1/31/93 Release Number: 2.00 Paaa: VI - 507
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Conment(s)
038
039
040
041
042
043
044
045
046
047
048
049
050
051
052
053
054
055
056
057
058
059
060
061
062
063
064
065
066
067
068
069
070
071
072
073
Note: This list begins on VI - 507
Counties of Texas (TX)
Childress (TX)
Clay (TX)
Cochran (TX)
Coke (TX)
Colenan (TX)
Coll in (TX)
CollingsMorth (TX)
Colorado (TX)
Conal (TX)
Comanche (TX)
Concho (TX)
Cooke (TX)
Coryell (TX)
Cottle (TX)
Crane (TX)
Crockett (TX)
Crosby (TX)
Culberson (TX)
Dallam (TX)
Dallas (TX)
Dawson (TX)
Deaf Smith (TX)
Delta (TX)
Denton (TX)
DeMitt (TX)
Dickens (TX)
Dimmit (TX)
Donley (TX)
Duval (TX)
Eastland (TX)
Ector (TX)
Edwards (TX)
Ellis (TX)
El Paso (TX)
Erath (TX)
Falls (TX)
FIPS
Code
075
077
079
081
083
085
087
089
091
093
095
097
099
101
103
105
107
109
111
113
115
117
119
121
123
125
127
129
131
133
135
137
139
141
143
145
Effective P ' •: 1/31/93 Release Number: 2.0" Page: VI -• -507.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0506, State-specific County Codes
Code Value Associated Description Comment!s)
074
075
076
077
078
079
OSO
001
082
083
094
085
086
087
088
089
090
091
092
093
094
095
096
097
098
099
100
101
102
103
104
105
106
107
108
109
Note: This list begins en VI
Counties of Texas (TX)
Farmin (TX)
Fayette ITX)
Fisher (TX)
Floyd (TX)
Foard (TX)
Fort Bend (TX)
Franklin (TX)
Freestone (TX)
Frio (TX)
Gaines (TX)
Calves ton (TX)
Garze (TX)
Gillespie (TX)
Glasscock (TX)
Goliad (TX)
Gonzales (TX)
Gray (TX)
Grayson (TX)
Gregg (TX)
Grimes (TX)
Guadalupe (TX)
Hale (TX)
Hall (TX)
Hamilton (TX)
Hansford (TX)
Hardemon (TX)
Hardin (TX)
Harris (TX)
Harrison (TX)
Hartley (TX)
HasKell (TX)
Hays (TX)
Hemphill (TX)
Henderson (TX)
Hidalgo (TX)
Hill (TX)
- 507
FIPS
Code
147
149
151
153
155
157
159
161
163
165
167
169
171
173
175
177
179
181
183
185
187
189
191
193
195
197
199
201
203
205
207
209
211
213
215
217
Effective Date: 1/31/93
Release Number: 2.00 Pane: VI - 508
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508f State-specific County Codes
Code Value Associated Description Comment!s)
110
111
112
113
114
115
116
117
116
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
136
139
140
141
142
143
144
145
Note: This list begins on VI - 5
Counties of Texas (TX)
Hockley (TX)
Hood (TX)
Hopkins (TK)
Houston (TX)
Howard (TX)
Hudspeth (TX)
Hunt (TX)
Hutehinson (TX)
Irion (TX)
Jack (TX)
Jackson (TX)
Jasper (TX)
Jeff Davis (TX)
Jefferson ITX)
Jim Hogg (TX)
Jim Hells (TX)
Johnson (TX)
Jones (TX)
Karnes (TX)
Kaufman (TX)
Kendall (TX)
Kenedy (TX)
Kent (TX)
Kerr (TX)
KfmbU (TX)
King (TX)
Kinney (TX)
Kleberg (TX)
Knox (TX)
Lamar (TX)
Lamb (TX)
Lampasas (TX)
La Sail* (TX)
Lavaca (TX4
Lee (TX)
Leon (TX)
07
FIPS
Code
219
221
223
225
227
229
231
233
235
237
239
241
243
245
247
Z49
251
253
255
257
259
261
263
265
267
269
271
273
275
277
279
261
283
285
287
289
Effectivi : 1/31/93
Release Number: P»«e: VI - 508.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 05081 State-specific County Codes
Code Value Associated Description Comoient(s)
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
Note: This list begins on VI - 507
Counties of Texas (TX)
Liberty (TX)
Limestone (TX)
Lipscoob'(TX)
Live Oak (TX)
Llano (TX)
Loving (TX)
LubbocK (TX)
Lynn (TX)
tlcCulloch (TX)
ncLennan (TX)
McMullen ITX)
Madison (TX)
Marion (TX)
Martin (TX)
Mason ITX)
Matagorda (TX)
Maverick (TX)
Medina (TX)
Menard (TX)
Midland (TX)
Milan (TX)
Mills (TX)
Mitchell (TX)
Montague (TX)
Montgomery (TX)
Moore (TX)
Morris (TX)
Motley (TX)
Nacogdoches (TX)
Navarro (TX)
Newton ITX)
Nolan ITX).
Nueces (TX)
Ochiltree (TX)
Oldham (TX)
Orange (TX)
FIPS
Code
291
293
295
297
299
301
303
305
307
309
311
313
315
317
319
321
323
325
327
329
331
333
335
337
339
341
343
345
347
349
351
353
355
357
359
361
Effective Date: 1/31/93 Release Number: 2.00 Paae: VI - 509
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508• State-specific County Codes
Code Value Associated Description Comment(s)
182
183
184
185
186
167
188
169
190
191
192
193
194
195
196
197
198
199
200
201
ZOZ
203
204
205
206
207
200
209
210
211
212
213
214
215
216
217
Note: This list begins on VI - 507
Counties of Texas (TX)
Palo Pinto (TXI
PanoU (TX)
Parker (TX)
Former (TX)
Pecos (TX)
Polk (TX)
Potter (TX)
Presidio (TX)
Rains (TX)
Randall (TX)
Reagan (TX)
Real (TX)
Red River (TX)
Reeves (TX)
Refugio (TX)
Roberts ITX)
Robertson ITX)
Roc knoll (TX)
Runnels (TX)
Rusk (TX)
Sabine (TX)
San Augustine (TX)
San Jacinte (TX)
San Patrieio (TX)
San Saba (TX)
Schleicher (TX)
Scurry (TX)
Shaekelford (TX)
Shelby (TX)
Sherman (TX)
Smith (TX)
Sonervell (TX)
Starr (TX)
Stephens (TX)
Sterling (TX)
Stonewall (TX)
FIPS
Code
363
365
367
369
371
373
375
377
379
381
383
385
387
389
391
393
395
397
399
401
403
405
407
409
411
413
415
417
419
421
«?
425
427
429
431
433
Effective ' • 1/31/93 Release Number: Z.<" Pace: VI -• 509.5
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 05081 State-specific County Codes
Code Value Associated Description Comment!s)
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
Note: This list begins on VI - 507
Counties of Texas CTX)
Sutton (TX)
Swisher (TX)
Terr ant <(TX)
Taylor (TX)
Terrell
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Code Value Associated Description Comment!s)
Note: This list begins on VI - 507
Counties of Texas (TX) FIPS
Code
254 Zavala (TX) 507
Effective r 1/31/93 Release Number: Z.' Paae: VZ - 510.5
-------
Coda Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0508, State-specific County Codes
Associated Description
Comment! a)
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
FIPS codes utilized - See Table 0509
Counties of Utah (UT)
Counties of Virginia (VA)
Independent Cities of Virginia (VA)
Islands of the Virgin Islands of the
United States IVI)
Counties of Vermont
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0509. FIPS PUB 6-4, County Codes
Associated Description
Comment(s)
013
016
020
050
060
068
070
090
100
110
122
130
150
164
170
iao
185
188
201
220
232
240
261
270
280
282
290
999
Boroughs/Census Areas of Alaska (AK)
Aleutians East (AK)
Aleutian West (AK)
Anchorage (AK)
Bethel (AK)
Bristol Bay (AK)
Denali (AK)
Dillinghem (AK)
Fairbanks North Star (AK)
Haines (AK)
Juneau (AX)
Kenai Peninsula (AK)
Ketchikan Gateway (AK)
Kodiak Island (AK)
Lake and Peninsula (AK)
Hatanuska-Susitna (AK)
(AK)
North Slope (AK)
Northwest Arctic (AK)
Prince of Males-Outer Ketchikan (AK)
Sitka (AK)
Skaguay-Hoonah-Angoon (AK)
Southeast Fairbanks (AK)
Valdez-Cordova (AK)
Hade Hampton (AK)
Hrangell-Petersburg (AK)
Yakutat (AK)
Yukon-Koyukuk (AK)
Unorganized Borough (AK)
All Latitudes N All Longitudes H
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
.Census area within unorganized Borough
Census area within unorganized Borough
Census area within unorganized Borough
Effective
: 1/31/93
Release Number: 2
Paoe: VI - 512
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0509, FIPS PUB 6-4, County Codes
Cod* Value Associated Description Comment(s)
Districts/Islands of American Samoa (AS) U.S. Possession
All Latitudes S All Longitudes N
010 Eastern IAS) District
020 Manu'a IAS) District
030 Rose Island (AS)
040 Strains Island (AS)
050 Western IAS) District
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 518
-------
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Code Value
Table 0509, FIPS PUB 6-4, County Codes
Associated Description
Comment(s)
002
005
040
060
States of the Federated State
of Micronesia (fH)
ChuuK (FM>
Kosraa
Freely Associated State
All Latitudes N All Longitudes E
Effective Data: 1/31/93
Release Number: 2.00
Paw: VI - 529
-------
Code Value
Section'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0509, FIPS PUB 6-4, County Codes
Associated Description
Comment(s)
075
077
079
061
083
085
067
089
091
093
095
097
099
101
103
105
107
109
111
113
Note: This list begins on VI .- 577
Counties of Montana (MT)
Powder River (MT)
Powell (MT)
Prairie (MT)
Ravalli (MT)
Richland (MT)
Roosevelt (MT)
Rosebud (MT)
Sanders (MT)
Sheridan (MT)
Silver BOM (MT)
Stillwater (MT)
Sweet Grass (MT)
Teton (MT)
Tool* (MT)
Treasure (MT)
Valley (MT)
Hheatland (MT)
Hibaux (MT)
Yellowstone (MT)
Yellowstone National Park (MT)
The portion of Yellowstone National
ParK in Montana is not located in
any county
Minimum Maximum
Latitude Latitude
44560IN 455025N
461324N 473737N
463036N 471318N
452532N 464130N
471920N 481041N
475709N 483551N
450935N 465355N
470458N 481623N
46211ON 490211N
453512N 461212N
450828N* 460943N
450837N 461454N
472759N . 460931N
481021N 490149N
454954N 463054N
473804N 490204N
461052N 464612N
463630N 472555N
452553N 463136N
442720N 450746N
Minimum Maxin
Longitude Longitude
104560Iw 1061716M
1121512H 1132935H
1043313U 1060559M
1133008M 1143537H
1040046H 1051556H
1040046H 1055142M
1060134M 1075424M
114075IN 1160436M
1040046U 1050516M
1120735M 1130624H
1064816M 1100531H
1092318H 1102014H
1112128H 1130053M
1111301N 1121457H
1065340H 1074559M
1054512H 1072717H
1092105H 1101902W
1040046H 1043731H
1072329H 1085742M
1095624M 1110857H
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI - 578
-------
Section VI. Limt» of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0509. FIPS PUB 6-4. County Codes
Code Value Associated Description Comment!s)
States of the Republic of Palau (PH) U.S. Possession
(Note: Palau is also known as Belau) All Latitudes N All Longitudes E
002
004
010
050
100
150
212
214
218
222
224
226
227
226
350
370
Aimeliik (PH)
Airai (PMI
Angaur IPM)
HatoboheiMPH)
Kayangel (PH)
Koror (PH)
Melekeok (PH)
Ngaraard (PH)
Ngarchelong (PH)
Ngardnau (PH)
Ngatpang (PH)
Ngchesar (PH)
Ngeremlengui (PH)
NgiMal (PH)
Peleliu (PH)
Sonsorol (PH)
Effective Date: 1/31/93 Release Number: 2.00 Pace: VI - 606
-------
Section VI. Lists of Acceptable Cade Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0511, FIPS PUB 6-5, Metropolitan Statistical Area (MSA) Codes, with PMSAs, NECtlAap t CMSAs
Code Value Associated Description Comment(i)
0060
0360
0440
0620
0733
0645
0875
1120
1122
1123
1125
1145
1160
1163
1170
1200
1260
1262
1305
1310
1600
1602
1640
1642
1680
1692
1920
1922
Metropolitan Statistical Area (USA),
Primary Metropolitan Statistical Area
(PM3JU, New England County Metro-
politan Area (NECMA), and Consolidated
Metropolitan Statistical Area (CMS A)
Codes
Akron, OH
Anahein-Sante Clara. CA
Am Arbor. MI
Aurora-Elgin, XL
Bangor, HE
Beaver County, PA
Bergen-Passaic, NJ
Boston, MA
BoBton-LaMrence-Stlen, MA-NH
Boston-Laurence- Salem- Lowell-Brock ton, MA
Boulder- Longnont, CO
Brazwia* TX
Bridgeport-Mi Herd. CT
Bridgeport-Stanfard-Nonielk-Danbury, CT
Bristol, CT
Brockton. HA
Buffalo, NY
Buffalo-Niagara Falls, NIT
Burlington, VT
Caguas . PR
Chicago, IL
Chtcago-Gary-Lake County, IL-1H-HI
Cincinnati, OH-KY-IN
Cincirmati-Hanilton, OH-KY-ZH
Cleveland, OH
Cleveland- AKron-Lorain, OH
Dallas; TX
Dallas-Fort Worth, TX
CMS As r PMSAs.
provided at
included at
Type 2-d>0it
PMSA
PM5A
PMSA
PMSA
NECMA
PHSA
PMSA
PMSA
CMSA 07
NECMA
PMSA
PMSA
PMSA
NECMA
PtlSA
PMSA
PMSA
CMSA 10
NECMA
PMSA
PMSA
CMSA 14
PMSA
CMSA 21
PMSA
CMSA 28
PMSA
CMSA 31
and NECMAs ONLY have been
this tine. MSAs will be
a later date.
CMSA In CMSA
1692
4472
2142
1602
6262
5602
1122
2082
3362
5«02
3282
1122
1262
7442
1402
1642
1692
1922
Pop. Level
B
A
B
B
C
C
A
A
A
A
C
C
B
B
D
C
A
A
C
B
1930
Danbury, CT
PMSA
5602
Effective Date: 1/31/93
Release Number: 2.00
Paqe: VI - 639
-------
Section 'VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0511. FIPS PUB 8-5. Metropolitan Statistical Area (MSA) Codes, with PUSAs, NECMAs, ft CMSAs
Code Value Associated Description Comment!s)
2080
2082
2160
2162
2460
2660
2600
2920
2960
3200
3280
3282
3283
3360
3362
3640
3690
3800
3965
4160
4243
4440
4472
4480
4560
4763
4992
5000
5015
5020
5030
5082
Note: This list begins on VI - 639
Denver, CO
Denver-Boulder, CO
Detroit, MI
Detroit-Ann Arbor, MI
Fall River. MA-RI
Fort Louderdale-Hollywood-Pompano Beach
FL
Fort Worth-Arlington, TX
Galveston-Texas City, TX
Gary-Hammond. IN
Hamilton-Middletown, OH
Hartford, CT
Hartford-New Britain-Middletown, CT
Hartford-New Br i ta i n-Mi ddletown-Br i stol
CT
Houston, TX
Houston-Galveston-Brazoria, TX
Jersey City. NJ
Joliet. IL
Ix0nosno t NX
Lake County, IL
Lawrence-Haverhi 11 , MA-NH .
Lewiston-Auburn, ME
Lorain-Elyria, OH • .
LOB Angeles-Anahein-Riverside, CA
Los Angeles-Long Beach, CA
Lowell . MA-NH
Manchester-Nashua, NH
Hi ami -Fort Lauderdale, FL
Miami -Hialeah, FL
Middlesex-Sonerset-Hunterdon, NJ
Middletown, CT
Milwaukee, HI
Milwaukee-Racine, HI
CMSAs. PMSAs,
provided at
included at
Type 2-dt git
PMSA
CMSA 34
PMSA
CMSA 35
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
CMSA 41
NECMA
PMSA
CHSA 42
PMSA
PHSA
PMSA
PMSA
PMSA
NECMA
PMSA
CMSA 49
PMSA
PMSA
NECMA
CMSA 56
PMSA
PMSA
PMSA
PMSA
CMSA 63
and NECMAs ONLY
this tine. MSA
a later date.
CMSA In CHSA
2082
2162
6482
4992
1922
3362
1602
1642
3282
3362
5602
1602
1602
1602
1122
1692
4472
1122
4992
5602
3282
5082
have been
s will be
Pop. Level
A
A
A
A
C
A
B
C
B
B
B
A
A
A
A
B
B
C
B
B
0
B
A
A
C
B
A
A
B
0
A
A
Effective Data: 1/31/93
Release Number: 2.00
Pane: VI - 640
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0511, FIPS PUB 6-5, Metropolitan Statistical Area (MSA) Codes, with PUSAs, NECMAs, * CMSAs
Code Value Associated Description Comment!s)
Note: This list begins on VI - 639
5190
5350
5380
5403
5440
5483
5523
5600
5602
5640
5700
5760
5775
5950
6000
6060
6160
6162
6280
6262
6323
6403
6440
6442
6453
6480
6462
6463
6600
6780
7090
7360
CMSAs. PHSAs, and NECMAs ONLY have been
provided at this tine. MSAs Mill be
included at a later date.
Type 2-digit CMSA In CMSA Pop. Level
Monmouth-Ocean, NJ
Nashua, NH
Nassau-Suffolk, NY
New Bedford-Fall River-Attleboro,
HA
New Britain, CT
New Haven-Haterbury-Meriden,
NCM London-Nomich, CT
New York. NY
CT
New York-Northern New Jersey-Long Island
NY-NJ-CT
Newark, NJ
Niagara Falls, NY
Norwalk, CT
Oakland, CA
Orange County, NY
Oxnard-Ventura, CA
Pawtucket-Woonsocket-Attleboro, RI-MA
Philadelphia, PA-NJ
Philadelphia-Hilnington-Trenton
PA-NJ-DE-MD
Pittsburgh, PA
Pittsburgh-Beaver Valley, PA
Pittsfield. MA
Portland. ME
Portland. CR
Portland-Vancouver, OR-HA
Portsrauth-Dover-Rochester. NH
Providence, RI
Providence-PaMtucket-Fall River, RI-MA
Providence-PaNtucket-Moonsocket, RI
Racine, HI
Riverside-San Bernardino, CA
Salem-61oucester, MA
San Francisco, CA
PMSA
PMSA
PMSA
NECMA
PMSA
NECMA
NECMA
PMSA
CMSA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
CMSA
PMSA
CMSA
NECMA
NECMA
PMSA
CMSA
NECMA
PMSA
CMSA
NECMA
PMSA
PMSA
PMSA
PMSA
70
77
78
79
60
5602
1122
5602
3282
5602
5602
1262
5602
7362
5602
4472
6482
6162
6282
6442
6462
5082
4472
1122
7362
B
C
A
B
C
B
C
A
A
C
C
A
B
B
B
A
A
A
A
C
C
A
A
B
B
A
B
C
A
B
A
Effective P
1/31/93
Release Number: 2.M
Pace: VI - 641
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0511. FIPS PUB 8-5, Metropolitan Statistical Area (MSA) Codes, with PUSAs, MECMAs, I CMSAs
Code Value Associated Description Comment!s)
Note: This list begins on VI - 639
7362
7400
7440
7442
7485
7500
7600
7602
6003
8040
8200
8460
8720
6725
6760
9160
9243
San Francisco-Oakland-San Jose, CA
San Jose, CA
San Juani PR
San Juan-Caguast PR
Santa Cruz, CA
Santa Rosa-Pataluma, CA
Seattle, NA
Seattle-Tacona, HA
Springfield, MA
Stamford. CT
Tacoma, MA
Trenton, NJ
Vallajo-Fairfield-Napa, CA
Vancouver, MA
Vineland-Nillville-Brtdgeton, NJ
Wilmington, DE-NJ-MD
MorcMter-Fitchburg-Leoainster, MA
CMSAsi PMSAs, and NECMAs ONLY have been
provided at this tine. MSAs Mill be
included at a later date.
Type 2-digit CMSA In CMSA Pop. Level
84
CMSA
PMSA
PMSA
CMSA
PMSA
PMSA
PMSA
CMSA
NECMA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
PMSA
NECMA
67
91
7362
7442
7362
7362
7602
5602
7602
6162
7362
6442
6162
6162
B
C
B
B
C
C
B
Effective Date: 1/31/93
Release Number: 2.00
Page: VI - 642
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0603. Service Area Category Codes
Associated Description
Coment(s)
01
02
09
Interstate Carrier
Wholesaler (Sells Hater)
Other Area
Major Category
Other
Other
Other
Rl
R2
R9
Residential Area
Mobile Home Park
Other Residential Area
Residential
Residential
Residential
31
32
S3
S4
S5
39
School
Institution
Medical Facility
Industrial/Agricultural
Day Care Center
Other Seni-residential Area
Semi-residential
Serai-residential
Semi-residential
Semi-residential
Semi-residential
Semi-residential
n
T2
T3
T5
T6
T9
Recreation Area
Service Station
Summer Camp
Restaurant
Highway Rest Area
Hotel/Motel
Other Transient Area
Transient
Transient
Transient
Transient
Transient
Transient
Transient
Effective D
V31/9J
Release Number: Z.,y
Paae: VI - 643
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0605, Primary Service Area Flag Codes
Code Value Associated Description Comment! s)
N Non-Primary Service Area Secondary Service Area
Y Primary Service Area
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI -
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 0705i On-site Visit Reason Codes
Code Value Associated Description Comment!s)
1 Sanitary Survey
2A Training
2C Laboratory Certification
2E Emergency Assistance
2G Engineering Determination/Advice
21 Investigation IComplaint/Violet!on/etc.)
2L Laboratory Inspection
zn Informal System Inspection
20 Other
2P Permit (Qualification/Review/Compliance I
2R Regularly Scheduled
25 Sample Collection
2T Technical Assistance I Non-specific)
2V Variance/Exemption/Other Compliance
Schedule Related
Effective C ' 1/31/93 Release Number: 2.£" Pane: VI - 6«
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed List* of Code Values
Table 0805, Pb/Cu Milestone Event Codes
Code Value Associated Description Comment!s)
CCSR Corrosion Control Study Required
CSSC Corrosion Control Study Completed
CU90 Copper Action Level Exceedance
LSLR Lead Service Line Replacement Required
MPLS Hax. Permissible Levels in Source Hater
OTDE OCCT Treatment Designated or Approved
OTIN OCCT Treatment Installed
PB90 Lead 90th Action Level Exceedance
STDE SOUT Designated or Approved
STIN SOHT Treatment Installed
WPS Mater Quality Parameters
Effective Date: 1/31/93 Release Number: 2.00 Paqe: VI - 646
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table lOOli Non-compliance Data Reconciliation Flag Codes
Code Value Associated Description Comment!s)
MB ««__••_«_« H« V V «•• • ••••«•.»••»"—«««™»» — ™«»™ — ——-.•—— W «_ _BWA«VK_MM__ _«_»•> _«•««••«««••»«
NULL Reconciliation NOT Needed for NCP/LINK NULL inplies no Data Base value
1 NCP Reconciliation Needed
2 NCP and L4NK Reconciliation Needed
Effective : 1/31/93 Release Number: 9.-' Pane: VI - 6*7
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1121 • Analysis Method Codes
Code Value Associated Description Comment!sI
Analysis Methods for Physical
Contaori rants
001 Nephelometric
003 Nephelonetriei with Styrene Diviny
Effective Date: 1/31/93 Release Number: 2.00 ' ' Paae: VI - 648
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1121, Analysis Method Codes
Code Value Associated Description Comnient(s)
Analysis Methods for Inorganic
Contaminants
101 Atonic Absorption, Direct Aspiration
103 Atonic Absorption, Flaneless
105 Brucine Colorinetric
107 Electrode
109 Cadmiun Reduction
111 Colorinetric, Prelininary Distillation
113 Silver Oiethyidithiocarbamate
115 Alizarin Fluoride Blue
116 Modified Alizarin Fluoride Blue
117 Zireoniun-Eriochrome Cyanine
118 Automated Electrode (Fluoride)
119 Automated Cold Vapor (Mercury)
121 Automated Hydrazine Reduction
122 Nitrate Ion Electrode IV Kimn)
123 Hydride Generation (Atonic Absorption)
124 Chronotropie Acid Method
125 Graphite Furnace (Flaneless AA)
127 Potentionetric
128 Silver Nitrate Method
129 Platinun-Cobalt (Color)
130 TherouNMtHc (Temperature)
131 Titrimetrie Iodine
133 Consistent Series (Odor)
135 Bless Electrode (pH)
136 Potentiomatric
137 Turbidimtrie (Sulfate)
138 Langelier Index (Corrosion)
139 Total Filterable Residue (TOS)
141 Edte Titrinetric Test
142 Methyl Orange End Point pH 4.5
143 Heteropoly Blue (Silica)
144 Acidity Measurement (SM-401)
145 Specific Conductants Meter
147 Direct Thenate (Ammonia)
149 Electronetric Titretion
151 Specific Conductivity
153 Mercuric Nitrate
Effective' '•«: 1/31/93 Release Number: 2.00 Paqe: VI -' 649
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1121. Analysis Method Codes
Code Value Associated Description Comraent(s)
Note: This list begins on VI - 6*9
Analysis Methods for Inorganic
Contaminants
155 Kethylene Blue Colorimetric
157 Ti tration-pH-Electrode-Endpoint
159 Colorimetric Ferricyanide Auto
161 Automated Colorimetric Method
163 Automated Cadmium Reduction
165 Flame Photometric (Sodium)
Effective Datet 1/31/93 Relewa Number: 2.00 P««l VI - 650
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1121, Analysis Method Codes
Code Value Associated Description Comment(s)
Analysis Methods for Organic
Contaminants
201 Organoehlorine Pesticides
203 Chlorinated Phenoxy ft Herbicides
204 Organoehlorine Pesticides
205 Gas Chromatographie
206 Chlorinated Phenoxy Acid Herbicides
207 Methylone Blue I Foaming Agent)
209 Chloroform Extract (Phenols)
211 Colorimetrici Preliminary Distillation
213 Purge ft Trap Method (TTHM)
215 Liquid/Liquid Extraction (TTHM)
216 Purge ft Trap GC (VOCs 502.1)
217 Purge ft Trap EC (VOCs 502.2)
218 Purge ft Trap GC (VOCs 503.1)
219 Hicroextraction ft GC (EOB ft DBCP 504) -
220 Purge ft Trap 6C/MS (VGCs 524.1)
221 Purge ft Trap Cap.Col. GC/HS (VOCs 524.2)
Effective • 1/31/93 Release Number: Z Pacre: VI -' 651
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 11Z1. Analysis Method Codes
Code Value Associated Description Commentls)
Analysis Methods for Microbiological
Contaminants
301 Dpn - Chlorine Residual
302 400G-FactSi Syringaldazini
303 Membrane Filter
305 Fermentation Tube. 10 nl
307 Fermentation Tube, 100 nl
Effective Date: 1/31/93 Release Number: 2.00 Pane: VI - 6S2
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1121. Analysis Method Codes
Code Value Associated Description Coimnentfs)
Analysis Methods for Radiological
Contaminants
401 Gross Alpha I Beta, Method 302
402 Gross Alpha I Beta Analysis
403 Strontiun-69,90 Method 303
404 Strontium 89,90 Analysis (NJ)
405 Total Radium. Method 304
407 Radium-226. Method 305
409 Tritium. Method 306
410 Tritium, Liquid Scintillation
4tl Cesium-134, ASTM D-2459
413 Uranium, ASTM D-2907
414 Iodine-131, Radiechemical Analysis
415 Iodine-131. Precipitation
416 Iodine-131• Gamma Procedure
417 Radium-226. Radon Emination
416 Radium-226.226 Sequential Method
419 Radium-226. Brooks-Blanchard
999 Other
Effective 1/31/93 Release Number: 2 Pae»: VX - 653
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1131, Major/Minor Violation Flag Codes
Code Value Associated Description Comment(s)
N Minor Monitoring Violation
Y Major Monitoring Violation
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 654
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 1293* Enforcement Link Type Codes
Code Value Associated Description Comment!s)
X Linked by Violation Date Range!s) Via X5000 DTP transaction (Form El)
Y Linked by Violation I0(s) Via Y5000 DTF transaction (Fern El)
Z Linked by Violation Type/Contaa./Date(s) Via Z5000 DTF transaction (For* El)
Effective <: 1/31/93 Release Number: 2 Paoe: VI - 655
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 2107t Sanple Contaminant Identification Codes
Cade Value Associated Description Comment!s)
P890 Lead 90th Percentile Value
Effective Date: 1/31/93 Release Number: 2.00 Paoe: VI - 656
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
.Table 3005, Variance/Exemption/Other Record Type Codes
Code Value Associated Description Comment!8)
EX Exemption Record
FR Filtration Requirement Record (SMTP)
TN Turbidity Waiver Record
VA Variance Record
Effective •»: 1/31/93 Release Number: ? Paoe: VI - 657
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 3011, Variance/Exemption/Other Status Codes
Associated Description Comment!m>
A
B
C
E
6
I
K
M
D
Q
R
S
T
U
V
M
X
Y
Z
Interest Expressed
Completed! PUS in compliance
Application Received
State Proposes to Deny
State Proposes to Grant
Hearing Scheduled on Proposal
Hearing Held on Proposal
Compliance Schedule Prescribed
Hearing Scheduled on Compliance Schedule
Hearing Held on Compliance Schedule
Additional Information Desired
Request Granted
Request Denied
State Sett Monitoring Requirements
EPA Sets Monitoring Requirements
Notification given to Public
Other
Notification given to EPA
Pending Deletion
In Vari ance/Exemption/Other
Variance/Exempt i on/Other
For Variance/Exemption/Other
Variance/Exemption/Other Application
Variance/Exemption/Other Application
For Variance/Exemption/Other
For Variance/Exemption/Dther
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI - 656
-------
Code Value
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 30I9t Variance/Exemption/Other Reason Codes
Associated Description Comment(s)
001
003
005
007
009
Oil
013
Cannot Comply after Treatment
Cannot Afford Facility Construction
Funds Pending
Facility Construction Pending
Unable to Afford Treatment
TreatmentlUnnecessary
Treatment Impractical
021
022
Source Hater Coif form
Source Hater Turbidity
Source Hater Criteria under the SHTR
Source Hater Criteria under the SHTR
031
032
033
034
035
036
037
Failure to Meet Daily CT
Residual Disinfectant <= 0.2 mo/1
Residual Disinfectant Not Detected
Lack of Redundant Disinfection Equipment
Hatershed Control is Inadequate
On-site Inspection Harrants Filtration
Haterborne Disease Outbreak
Site-specific Criteria under the SHTR
Site-specific Criteria under the SHTR
Site-Specific Criteria under the SHTR
Site-specific Criteria under the SHTR
Site-specific Criteria under the SHTR
Site-specific Criteria under the SHTR
Site-specific Criteria under the SHTR
041
042.
043
MCLi Monthly/Acute (TCR1
HCL, TTHM
Turbidity
Violations of Other Rules (SHTR Related)
Violations of Other Rules (SHTR Related)
Violations of Other Rules (SHTR Related)
051
052
PHS Opts to Install Filtration Other
State Requires Installation (not NPDHR) Other
098
Turbidity Halver (Converted FRDS 1.5)
•098' My not be used on any FRDS-II
input transaction. It MBS assigned by
the FRDS-II computer system during the
conversion of data from FRDS 1.5 to
FROS-II.
099
Other
Effective Date: 1/31/93
Release Number: 2.00
Paoe: VI - 659
-------
Section VI. List* of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 3027, Variance/Exemptton/Other Vulnerability Flag Codes
Code Value Associated Description Coomentls)
PUS is NOT Vulnerable to Contaminant
PUS is Vulnerable to Contaminant
Effective Date: 1/31/93 Release Number: 2.00 P»oe: VI - 660
-------
Section VI. Lists of Acceptable Code Values with Associated Descriptions
C. Detailed Lists of Code Values
Table 3103, Variance/Exemption/Other Schedule Action Codes
Code Value Associated Description Comment!s)
01 Letter to PUS from State
04 Administrative Hearing - PUS A State
07 Other State Administrative Procedure
19 Explore Alternate Sources of Hater
22 Explore Regional System Development
25 Financial Aid Obtained
28 Treatment System Designed
31 Treatment System Approved
34 Treatment System Built
37 Periodic Monitoring Required
Effective D 1/31/93 Release Number: 2.00 Paoe: VZ - 661
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section VII
References
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section VII References
The following EPA documents provide the user with information helpful in understanding
FRDS-n reporting requirements. They are readily available from regional offices or
Headquarters.
FRDS REPORTING GUIDANCE
Memoranda
• Final Guidance on Reporting to FRDS Violations of the VOC (Phase I) Requirements
(10/22/90)
• Reporting Enforcement Actions and "Compliance Achieved" to FRDS (11/13/90)
New Follow-up Actions, code values and definitions.
• Detailed FRDS Reporting Guidance for the Surface Water Treatment (SWT) and
Total Coliform (TC) Rules (1991)
Implementation and FRDS reporting guidance for these two rules.
• Follow-up to the Review of the FRDS-n Grant Eligible Data Elements (5/12/91)
Re-definition of the FRDS-11 grant eligible data elements superceeding Water Supply
Guidance V-2
• Final Guidance for Phase II Rule (1992)
FRDS reporting guidance for Phase II.
• Final Guidance for the Lead and Copper Rule - Definitions of Federal Reporting for
Milestones, Violations and SNC's (5/92).
ENFORCEMENT GUIDANCE
Memoranda
• Change in the PWSS Program's Definition of Timely and Appropriate Actions
(4/20/90).
Changes the "Timely' definition of follow-up actions to be within six months of the
discovery of a SNCfor microbiohgical/turbidityffniM SNC's, and within 12 months
for chemical/radiological SNC's.
Effective Date: 1/31/93 Release: 2.00 Page: VH - 1
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
• Revised Definition of Significant Noncomplier (SNC) and the Model for Escalating
Responses to Violations for the PWSS Program (5/22/90).
Provides a modification to the SNC definition and clarifies the Office's expectations
for State and federal responses to violations.
• Final SNC Definition for the TCR and Proposed SNC definition for SWTR
(12/19/90).
• Final SNC Definition for the SWTR (2/28/91).
FRDS OPERATIONS
Guidance
• FY93 STARS Reporting Process and Schedule for the PWSS Program (11/16/92).
FRDS and STARS reporting schedules for FY93, including SNC creation and
region/state/HQ STARS reporting schedules.
PWSS IMPLEMENTATION
Memoranda
• Data Verification Protocol (3/91).
Recommended, methodology for the data audits of primacy agencies.
• FY 91 Compliance Report (3/91).
EPA HQ repon on the status ofPWS noncompliance during FY91. This report is
produced annually.
LEGAL INTERPRETATION OF SAFE DRINKING WATER ACT
Memoranda
• Definition of Public Water System (7/12/78).
Legal definition ofPWS based upon its provision of water for human consumption.
• Definition of Non-Transient Non-Community Water System (9/16/87).
Definition of factors for identification of Non-Transient PWS.
Effective Date: 1/31/93 Release: 2.00 Page: VH - 2
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section VIII
Glossary Of Technical And Drinking Water Programmatic
Terms
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section VIII Glossary Of Technical And Drinking Water Programmatic
Terms
-A-
ACT
The Public Health Service Act, as amended by the Safe Drinking Water Act (SDWA),
and the SDWA amendments of 1986. Public Laws 93-523 and 99-339, respectively. See
also: SDWA, N1PDWR, NRPDWR, NPDWR.
ACTION LEVEL
The concentration of lead or copper in tap water [specified in §141.80(c)] which
determines, in some cases, the treatment requirements [contained in subpart I (Control of
Lead and Copper) of the NPDWRs] that a water system is required to complete.
Contrast with: MAXIMUM CONTAMINANT LEVEL.
ACTIONS
A term used to refer to violation, enforcement action, and variance/exemption/other
related data submitted as a part of a State's quarterly update to FRDS-H. When reported,
Actions data must be segregated from Sample data, but may be reported individually or
combined with Inventory data, as desired. Contact FRDS Production Control for
additional details.
Actions data refers to that information which is stored in the following FRDS-II Data
Base records:
C1100, VIOLATION-DATA
C1200, ENFORCEMENT-DATA
C3000, VARIANCE-EXEMPTION-DATA
C3100, VE-SCHEDULE
See also: ENFORCEMENT ACTION, EXEMPTION, VARIANCE, VIOLATION. Contrast
with: INVENTORY, SAMPLES.
ACTIVE
A term used to refer to a public water system that is producing water on a regular basis
(obtaining, treating, pumping, storing, and/or distributing).
Effective Date: 1/31/93 Release Number: 2.00 Page: Vffl - 1
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
The active versus inactive classification is often confused with the current versus
historical classification. Classifying a public water system as active or inactive is
exclusively at the State's discretion. It is the way in which the State indicates the present
operational status of a public water system. Classifying a public water system as part of
the current or historical inventory is performed automatically by the FRDS-n computer
system. It indicates whether or not a public water system is embodied in the most recent
inventory submission from the State.
See also: ACTIVE WATER SYSTEM. Contrast with: CURRENT INVENTORY,
HISTORICAL INVENTORY, INACTIVE.
ACTIVE PWS
See ACTIVE WATER SYSTEM.
ACTIVE WATER SYSTEM
,A public water system that is active.. See also: ACTIVE. Contrast with: INACTIVE
WATER SYSTEM.
ALPHABETIC
A term used to describe a class of data element values. An alphabetic data element's
values consist of combinations of the letters A to Z and blank spaces. Contrast with:
ALPHANUMERIC, NUMERIC. See also: CHARACTER, TEXT.
ALPHANUMERIC
A term used to describe a class of data element values. An alphanumeric data element's
values can consist of combinations of the letters A to Z, blank spaces, the numbers zero
through nine, and/or a set of special symbols used for punctuation or special meaning.
Contrast with: ALPHABETIC, NUMERIC. See also: CHARACTER, TEXT.
AQUIFER
An aquifer, or water-bearing formation, is an underground layer of permeable rock or
soil that permits the passage of water. Aquifers are either artesian (confined) or water/
table (unconfined) dependent upon the permeability of the surrounding material. See
also: ARTESIAN AQUIFER, WATER TABLE AQUIFER, ZONE OF SATURATION,
GROUND WATER SOURCE, WELL.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 2
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
ARTESIAN AQUIFER
One of two general classifications of aquifers. An artesian aquifer consists of confined
ground water that is under artesian pressure. In other words, when an overlying
impermeable formation confines the water in the zone of saturation under a pressure
greater than atmospheric pressure. Contrast with: WATER TABLE AQUIFER. See also:
AQUIFER, ZONE OF SATURATION, GROUND WATER SOURCE, WELL.
AVAILABILITY
,A term used to identify the way in which a source of water is utilized. For example, a
source of water can be utilized on a permanent basis, seasonal basis, interim basis, or
emergency basis. The availability of a source of water is used when the primary source
of water of a public water system is determined, and when classifying a public water
system as a surface, ground water, ground water UDISW, purchased surface, purchased
ground water, or purchased ground water UDISW water system.
See also: PRIMARY SOURCE, SURFACE WATER SYSTEM, GROUND WATER UDISW
SYSTEM, GROUND WATER SYSTEM, PURCHASED SURFACE WATER SYSTEM,
PURCHASED GROUND WATER UDISW SYSTEM, PURCHASED GROUND WATER
SYSTEM.
-B-
BACTI
An abbreviation used to refer to a microbiological, or bacterial, contaminant in drinking
water. Contrast with: TURBIDITY, CHEMS, RADS. See also: TOTAL COLIFORM
BACTERIA, FECAL COLIFORM BACTERIA, HETEROTROPHIC BACTERIA, GIARDIA
LAMBLIA, LEGIONELLAE, PATHOGENIC VIRUSES, CONTAMINANT.
BASE LINE
A base line is an imaginary east-west surveyor's line which has been defined in
conjunction with an imaginary north-south line (i.e., a principal meridian) from which
township coordinates are determined.
Townships are plots of land, each approximately six miles to the side (i.e., 36 square
miles) defined under the Rectangular Survey System of the U.S. Department of Interior,
Bureau of Land Management. See also: PRINCIPAL MERIDIAN.
Effective Date: 1/31/93 Release Number: 2.00 Page: Vffl - 3
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
BAT
An abbreviation for Best Available Technology. See BEST AVAILABLE TECHNOLOGY.
BEST AVAILABLE TECHNOLOGY
The best technology, treatment techniques, or other means which the Administrator finds,
after examination for efficacy under field conditions and not solely under laboratory
conditions, are available (taking cost into consideration).
-c-
CDP
An abbreviation for a Census Designated Place. See CENSUS DESIGNATED PLACE.
CENSUS COUNTY DIVISION
A statistical area serving as a primary county division in twenty States which have no
minor civil divisions appropriate for census use. See also: MINOR CIVIL DIVISION,
PRIMARY COUNTY DIVISION.
CENSUS DESIGNATED PLACE
A populated place, not within the limits of an incorporated place, that has been delimited
for census purposes; serves, in one instance, as a primary county division. See also:
INCORPORATED PLACE, POPULATED PLACE, PRIMARY COUNTY DIVISION.
CENSUS SUBAREA
A statistical area in Alaska serving as a primary county division. See also: PRIMARY
COUNTY DIVISION.
CENSUS SUBDISTRICT
A legally established statistical area in the Virgin Islands of the United States serving as a
primary county division. See also: PRIMARY COUNTY DIVISION.
CHAR
See CHARACTER.
CHARACTER
A SYSTEM 2000™ data element data type. Character data element values are
alphanumeric with all extraneous blank spaces (i.e., leading spaces, trailing spaces,
multiple embedded spaces) removed. Contrast with: TEXT. See also: INTEGER,
DECIMAL, DATE, ALPHANUMERIC.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 4
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031 -LN-2003
_^__ January 31. 1993
CHEMS
An abbreviation used to refer to inorganic and organic contaminants in drinking water.
Contrast with: BACTI, TURBIDITY, RADS. See also: INORGANIC CHEMS, ORGANIC
CHEMS, SOCs, VOCs, CONTAMINANT.
CMSA
An abbreviation for a Consolidated Metropolitan Statistical Area. A CMSA is a
geographic area consisting of a large population nucleus together with adjacent
communities having a high degree of economic and social integration with that nucleus.
To be classified as a CMSA, however, the area must serve more than one million people
and meet certain other specific requirements. A CMSA is divided into major components
which are referred to as primary metropolitan statistical areas (PMSAs). CMSAs and
PMSAs are defined in Federal Information Processing Standard Publication (FIPS PUB)
8-5 entitled, Metropolitan Statistical Areas flncluding CMSAs, PMSAs, and NECMAs).
See also: MSA, PMSA, NECMA.
COAGULATION
A treatment process which uses coagulant chemicals and mixing by which colloidal and
suspended material are destabilized and agglomerated in non-filterable floes which settle.
COLIFORM BACTERIA
See TOTAL COLIFORM BACTERIA, FECAL COLIFORM BACTERIA,
COLIFORM-POSITTVE SAMPLE
A drinking water sample of 100 ml in which at least one coliform bacterium is detected
by an EPA approved analytical method.
COMMUNITY PWS
See COMMUNITY WATER SYSTEM.
COMMUNITY WATER SYSTEM
A type of public water system. Community water system means a public water system
which serves at least IS service connections used by year-round residents or regularly
serves at least 25 year-round residents.
Contrast with: TRANSIENT NON-COMMUNITY WATER SYSTEM, NON-TRANSIENT
NON-COMMUNITY WATER SYSTEM. See also: NON-COMMUNITY WATER SYSTEM,
CONSECUTIVE WATER SYSTEM, PUBLIC WATER SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 5
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
COMPLIANCE CYCLE
A 9-year calendar year cycle during which public water systems must monitor for
chemical substances or compounds regulated in the NPDWRs. (This presently includes
the Phase I, II, IIB, and V contaminants.)
Each compliance cycle consists of three 3-year compliance periods.
The first calendar year compliance cycle begins January 1, 1993, and ends December 31,
2001. The second calendar year compliance cycle begins January 1, 2002, and ends
December 31, 2010. The third calendar year compliance cycle begins January 1, 2011,
and ends December 31, 2019.
Contrast with: COMPLIANCE PERIOD. See also: INITIAL COMPLIANCE PERIOD,
REPEAT COMPLIANCE PERIOD.
COMPLIANCE PERIOD
Compliance period can have two distinct definitions, one definition when we refer to the
Standardized Monitoring Framework (SMF), which applies to the Phase I, II, JIB, and V
contaminant monitoring requirements, and a completely separate definition when we refer
toFRDS.
Under the SMF, a compliance period means a three-year period of time (calendar year
based) within a nine-year compliance cycle. The first compliance period of the first
compliance cycle begins 01/01/93 and ends 12/31/95; the second compliance period of
the first compliance cycle begins 01/01/96 and ends 12/31/98; and the third compliance
period of the first compliance cycle begins 01/01/99 and ends 12/31/2001.
In FRDS, a compliance period means the period of time during which monitoring was to
have been performed, such as a quarter, a year, etc. For example, assume a public water
system is required to monitor for contaminant X each calendar quarter. If this PWS fails
to conduct the required monitoring for contaminant X for the first calendar quarter of
1993, a regular sampling M&R violation is incurred. When this M&R violation is
reported to FRDS, the State must supply the beginning date of the compliance period,
and either the ending date of the compliance period or the duration of the compliance
period. The beginning date of the compliance period in this example would be 01/01/93,
the ending date of the compliance period would be 03/31/93, and the duration of the
compliance period would be three months.
Contrast with: COMPLIANCE CYCLE. See also: INITIAL COMPLIANCE PERIOD,
REPEAT COMPLIANCE PERIOD.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 6
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
COMPONENT
See COMPONENT NAME, COMPONENT NUMBER, DATA ELEMENT NAME, DATA
ELEMENT NUMBER.
COMPONENT NAME
A name assigned to a particular piece of information, or data, in a SYSTEM 2000™ data
base (e.g., In FRDS-n, PWS-ED is the component name used to refer to a public water
system identification number). See also: COMPONENT NUMBER, DATA ELEMENT
NAME, DATA ELEMENT NUMBER.
COMPONENT NUMBER
A number assigned to a particular piece of information, or data, in a SYSTEM 2000™
data base (e.g., In FRDS-n, C101 is the component number used to refer to a public
water system identification number). See also: COMPONENT NAME, DATA ELEMENT
NAME, DATA ELEMENT NUMBER.
COMPUTED CODE VALUE
See COMPUTED VALUE.
COMPUTED DATE VALUE
See COMPUTED VALUE.
COMPUTED NUMERIC VALUE
See COMPUTED VALUE.
COMPUTED VALUE
A code, date, number, or other value that is determined by the FRDS-II computer system
during its normal course of operation. A computed value is generally not supplied by the
State (i.e., there are a few data elements whose values will be computed only if the State
does not supply them).
CONFLUENT GROWTH
Continuous bacterial growth covering the entire filtration area of a membrane filter, or a
portion thereof, in which bacterial colonies are not discrete. Contrast with: TOO
NUMEROUS TO COUNT.
CONSECUTIVE PWS
See CONSECUTIVE WATER SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 7
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
CONSECUTIVE WATER SYSTEM
A public water system that is interconnected with another public water system. A public
water system that buys water from another public water system is a consecutive water
system. The public water system that sells the water is not consecutive. A consecutive
public water system can be a community, a transient non-community, or a non-transient
non-community public water system. However, monitoring requirements for consecutive
public water systems may be modified to the extent that the interconnection of the system
to another public water system justifies treating them as a single system.
In FRDS-II, the State may specify for each purchased source of water, the public water
system identification number of the system from whom the water is purchased.
See also: COMMUNITY WATER SYSTEM, NON-COMMUNITY WATER SYSTEM,
TRANSIENT NON-COMMUNITY WATER SYSTEM, NON-TRANSIENT NON-
COMMUNITY WATER SYSTEM, PUBLIC WATER SYSTEM.
CONTAMINANT
Any physical, chemical, biological, or radiological substance or matter in water.
See also: BACT1, TURBIDITY, CHEMS, INORGANIC CHEMS, ORGANIC CHEMS,
SOCs, VOCs, TTHM, RADS.
CONVENTIONAL FILTRATION
A series of treatment processes including coagulation, flocculation, sedimentation, and
filtration.
CORROSION INHIBITOR
A substance capable of reducing the corrosivity of water toward metal plumbing
materials, especially lead and copper, by forming a protective film on the interior surface
of those materials. See also: EFFECTIVE CORROSION INHIBITOR RESIDUAL.
COUNTY EQUIVALENT
A primary division, other than a county, of a State or a State equivalent. For example, a
parish in Louisiana, a borough or census area in Alaska, or an independent city in
Maryland, Missouri, Nevada, or Virginia. See also: STATE EQUIVALENT,
INDEPENDENT CITY.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 8
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
CT
The product of residual disinfectant concentration (C) determined before or at the first
customer, and the corresponding disinfectant contact time in minutes (T) (i.e., C x T).
See also: DISINFECTANT CONTACT TIME, RESIDUAL DISINFECTANT
CONCENTRATION.
CURRENT INVENTORY
One of two general classifications of FRDS-II public water system related data.
The definition of current inventory is influenced by whether or not a State submitted a
"total replacement" to its public water system inventory in the most recent reporting
period.
If a State submits a "total inventory replacement", the term current inventory refers to
those public water systems which were submitted in that most recent reporting period.
Those systems that existed in the current inventory prior to the update, for which a
replacement was not submitted, would become pan of the historical inventory.
If a State submits "inventory updates only" to its inventory in the most recent reporting
period, current inventory refers to those public water systems that existed in the current
inventory prior to the update, plus any new public water, systems which were reported in
that most recent period.
The active versus inactive classification is often confused with the current versus
historical classification. Classifying a public water system as active or inactive is
exclusively at the State's discretion. It is the way in which the State indicates the present
operational status of a public water system. Classifying a public water system as part of
the current or historical inventory is performed automatically by the FRDS-II computer
system. It indicates whether or not a public water system is embodied in the most recent
inventory submission from the State.
Contrast with: ACTIVE, HISTORICAL INVENTORY, INACTIVE. See also: TOTAL
REPLACE UPDATE.
cws
An abbreviation for a Community public Water System. See COMMUNITY WATER
SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 9
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
-D-
DATA ELEMENT
See COMPONENT NAME, COMPONENT NUMBER, DATA ELEMENT NAME, DATA
ELEMENT NUMBER.
DATA ELEMENT NAME
The name used to refer to a particular piece of data. For example, ADDRESS-LINE-1 is
the name of a data element which refers to a specific part of an address. See also:
COMPONENT NAME, COMPONENT NUMBER, DATA ELEMENT NUMBER.
DATA ELEMENT NUMBER
A number assigned to a particular piece of information, or data, in a SYSTEM 2000™
data base (e.g., In FRDS-II, C101 is the data element number used to refer to a public
water system identification number). See also: COMPONENT NAME. COMPONENT
NUMBER, DATA ELEMENT NAME.
DATA BASE
An organized collection of related records and data elements that are treated as a whole.
In FRDS-II, a hierarchically arranged set of records which contain information relating to
the Public Water System Supervision Program. See also: DATA BASE MANAGEMENT
SYSTEM, DBMS, SYSTEM 2000™, DATA BASE RECORD, ACT. SDWA, NIPDWR,
NRPDWR, NPDWR.
DATA BASE FAMILY
A reference to a particular set of data base records that lie within a common path of the
data base structure. A data base family includes all ascendant and descendant records to
a given node. For example, the C400, PWS-SOURCE-ENTITY-INFO, record belongs
to data base family 2. Each of its ascendant records (C100, PWS-SUMMARY, and CO,
STATE-SUMMARY) belong to data base family 2, as does its sole descendant record
(C480, PWS-SE-TREATMENT-DATA).
Please note that records CO, STATE-SUMMARY, and C100, PWS-SUMMARY, can
belong to any data base family. This definition is FRDS-II specific and differs from the
SYSTEM 2000™ definition for a data base family. See also: SYSTEM 2000"", DATA
BASE, DATA BASE RECORD, FRDS-II.
DATA BASE MANAGEMENT SYSTEM
The entire collection of procedures, programs, operations, and functions that are devoted
to the generation, collection, communication, storage, evaluation, retrieval, and
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 10
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-03I-LN-2003
January 31. 1993
dissemination of information contained in a data base. See also: DATA BASE, DBMS.
SYSTEM 2000", FRDS-1I.
DATA BASE RECORD
A group of logically related data elements. For example, the C500, PWS-
GEOGRAPHIC-AREAS-SERVED, record contains 8 unique data elements which identify
(from various perspectives) the geographic area(s) served in whole or in part by a public
water system. In mis particular example, the 8 unique data elements are: The State's
administrative region; the State's administrative district; the Federal congressional
district; the city served; a code which identifies the State county; a FIPS county code; a
code which identifies the metropolitan statistical area (MSA), primary metropolitan
statistical area (PMSA), or New England county metropolitan area (NECMA); and, if the
public water system is on an Indian reservation or in an Alaska remote village, a code
which identifies the Indian reservation, or the Alaska remote village. See also: DATA
BASE, DATA ELEMENT.
DATA CATEGORY
A two-digit number which categorizes FRDS-II data elements into logical groupings.
These data categories are used by the FRDS-II computer system during its normal course
of operation. A complete list of data categories is provided in Section VII, References,
of Release 1.00 of this document. Each data category falls into one of ten groups which
are as follows:
0 Alphanumeric data element 5 Unassigned
1 Code value data element 6 Date data element
2 Identification number data element 7 Other data element
3 Numeric integer data element 8 Unassigned
4 Numeric real data element 9 Unassigned
Section VII, References, Release 1.00, specifically defines each data category that exists.
DATA TRANSFER FILE
A collection of logically related records formatted for input to the FRDS-II Computer
System. See also: DTP. Contrast with: DATA TRANSFER FORMAT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 11
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31, 1993
DATA TRANSFER FORMAT
The specific format in which the FRDS-II computer system expects to receive all data for
verification and entry into its data base. The data transfer format does not resemble the
FRDS-II data capture forms, but in fact, is quite different. The format is as follows:
Positions Contents Comments / Example
1-2 Form ID The letter/number combination that appears in the
left hand margin on the data capture forms.
3-11 Qualifier #1. Is always the PWS-ID.
12-18 Qualifier #2 e.g., 017 (a source ID number).
19 - 25 Qualifier #3 e.g., 05 (a treatment ID number).
26-26 DIM Code e.g., M (modify).
27-31 Data Element e.g., C0483 (the data element for the treatment
objective).
32-71 Data Value e.g., D (code for disinfection).
72 - 74 Blank/Error Blank on input, error code if transaction rejected
75 - 80 Batch Date e! g., 061892 (a date).
See also: DIM CODE. Contrast with: DATA TRANSFER FILE.
DATE
A SYSTEM 2000™ data element data type. Date data element values are calendar dates.
In FRDS-II, date data elements are presented in mm/dd/yy format. See also:
CHARACTER, TEXT, INTEGER, DECIMAL.
DBMS
An abbreviation for a Data Base Management System. See also: SYSTEM 2000", DATA
BASE MANAGEMENT SYSTEM, FRDS-II.
DEACTIVATED
The process whereby a public water system is changed from an active water system to an
inactive water system by explicit action of the State. See also: ACTIVE, ACTIVE
WATER SYSTEM, INACTIVE, INACTIVE WATER SYSTEM.
DEC
See DECIMAL.
DECIMAL
A SYSTEM 2000™ data element data type. Decimal data element values are numeric real
numbers (i.e., they may contain a decimal point). Contrast with: INTEGER. See also:
CHARACTER, TEXT, DATE, NUMERIC.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 12
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-200i
January 31, 1993
DIATOMACEOUS EARTH FILTRATION
A treatment process which results in substantial paniculate removal in-which (1) a
precoat cake of diatomaceous earth filter media is deposited on a support membrane
(septum), and (2) while water is filtered by passing through the cake on the septum,
additional filter media known as body feed is continuously added to the feed water, in
order to maintain the permeability of the filter cake.
DIM CODE
An abbreviation for the Delete/Insert/Modify update action code on FRDS-II Data
Transfer File (DTP) transactions. See also: DATA TRANSFER FORMAT.
DIRECT FILTRATION
A series of treatment processes including coagulation and filtration, but excluding
sedimentation, which result in substantial paniculate removal.
DISINFECTANT
Any oxidant, including but not limited to chlorine, chlorine dioxide, chloramines, and
ozone added to water in any part of the treatment or distribution process, that is intended
to kill or inactivate pathogenic microorganisms. See also: PATHOGENIC,
DISINFECTION.
DISINFECTANT CONTACT TIME
The time in minutes that it takes for water to move from the point of disinfectant
application or the previous point of disinfectant residual measurement to a point before or
at the point where residual disinfectant concentration (C) is measured. See also: CT,
RESIDUAL DISINFECTANT CONCENTRATION.
DISINFECTION
A treatment process which inactivates pathogenic organisms in water by chemical
oxidants or equivalent agents. See also: PATHOGENIC, DISINFECTANT.
DISTRIBUTION SYSTEM
The means through which finished drinking water is conveyed from the point of its
production to the consumer's tap (i.e., the network of water lines including, the prime
conduit and the major, minor, and transmission arteries of the water conveyance system).
More formally stated, the term applies specifically to the network of pipelines,
distributing reservoirs, mains, service pipes, and the like.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 13
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
DOMESTIC OR OTHER NON-DISTRIBUTION SYSTEM PLUMBING PROBLEM
A coliform contamination problem in a public water system with more than one service
connection that is limited to the specific service connection from which a coliform-
positive sample was taken.
DTF
An abbreviation for Data Transfer File. See also: DATA TRANSFER FILE, DATA
TRANSFER FORMAT.
-E-
EFFECTTVE CORROSION INHIBITOR RESIDUAL
This definition is applicable to those NPDWRs which apply to the Control of Lead and
Copper.
A concentration sufficient to form a passivating film on the interior walls of a pipe. See-
also: CORROSION INHIBITOR.
ENFORCEMENT
See ENFORCEMENT ACTION.
ENFORCEMENT ACTION
Any action (formal or informal) taken against a public water system in response to a
violation. See also: ACTIONS. Contrast with: VIOLATION.
ENTITY
In FRDS-II, an entity can be any facility which is related to a public water system. The
term facility includes, but is not necessarily limited to, any of the following:
• Water collection apparatus (e.g., an intake, a well).
• Treatment plant (e.g., chlorinator at a well head, a large water treatment plant).
• Entry point to the distribution system.
• Water storage tank or holding area (e.g., elevated tank, reservoir, pressure tank
ground-level cistern).
• Auxiliary pumping equipment (e.g., a booster pump).
Effective Date: 1/31/93 Release Number: 2.00 Page: VHI - 14
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
ENTRY POINT
The point at which drinking water enters the distribution system.
The term "Entry Point" is often confused with and incorrectly interchanged with "Point-
of-Entry." In actuality, the two terms refer to completely different locations which are
not interrelated.
If the water is treated, entry point refers to the point at which the water exits the
treatment facility and enters the distribution system.
If treated or untreated water is stored, entry point refers to the point at which the water
exits from the storage facility and enters the distribution system.
If the water is untreated, entry point refers to the point at which the water exits from the
source and its facilities (e.g., its pump) and enters the distribution system.
Contrast with: POINT-OF-ENTRY, POINT-OF-USE. See also: SERVICE
CONNECTION.
ETIOLOGIC
• Assigning or seeking to assign a cause.
• Of, or relating to, etiology.
See GIARDIA LAMBL1A.
ETIOLOGY
• All of the causes of a disease or abnormal condition.
• A branch of knowledge dealing with causes.
EPA
An abbreviation for the United States Environmental Protection Agency.
EXEMPTION
A means by which a public water system is exempted from a maximum contaminant level
requirement, treatment requirement, or both, of an applicable primary drinking water
regulation. An exemption may be granted if all of the following conditions are met:
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 15
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
• Due to compelling reasons (including economic factors), the public water system is
unable to comply with the requirement.
• The public water system was in operation on the date on which the MCL or treatment
requirement was effective.
• The granting of the exemption will not result in an unreasonable risk to health.
Contrast with: VARIANCE, TURBIDITY WAIVER.
-F-
FAdLITY
See ENTITY.
FECAL COLIFORM BACTERIA
Coliform bacteria that are fecal in origin (fecal coliforms). Their presence in drinking
water is strong evidence of recent sewage contamination and indicates that an urgent
public health problem exists, since fecal pathogens often co-exist with fecal coliforms.
See also: BACTI, TOTAL COLIFORM BACTERIA, HETEROTROPHIC BACTERIA,
GIARDIA LAMBLIA, LEGIONELLAE, PATHOGENIC VIRUSES, CONTAMINANT.
FILTRATION
A treatment process for removing paniculate matter from water by passage through
porous media.
FTPS
An abbreviation used to refer to a federal Information Processing Standard.
FTPS PUBS
An abbreviation used to refer to the Federal Information Processing Standard
PUBlicationS.
FIRST DRAW SAMPLE
A one-liter sample of tap water [collected in accordance with §141.86(b)(2)] that has been
standing in plumbing pipes at least 6 hours and is collected without flushing the tap.
Contrast with: SERVICE LINE SAMPLE.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 16
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
FLOCCULATION
A treatment process to enhance agglomeration or collection of smaller floe particles into
larger, more easily settleable particles through gentle stirring by hydraulic or mechanical
means.
FRDS
An abbreviation for the Federal Reporting Data System. See also: FRDS-II.
FRDS-DE
FRDS-DE (pronounced FERDY) is a PC-based data entry package developed and
maintained by the Office of Ground Water and Drinking Water. FRDS-DE supports
input of data contained on all FRDS-II Data Capture Forms and formats the entered data
into the FRDS-II Data Transfer File (DTP) format. See also DATA TRANSFER
FORMAT.
FRDS-n
The Federal Reporting Data System, version U. Operated and maintained by the U.S.
EPA, Office of Ground Water and Drinking Water. A data base management system
application that stores public water system inventory, violation, enforcement action,
milestone, sample, variance/exemption/other related data, and State Discretionary Data.
Data contained in FRDS-II is reported to EPA by the States having jurisdiction over
public water systems. When reported, this data fulfills the States' data reporting
obligations as established in the National Primary Drinking Water Regulations. See also:
ACT, SDWA, N1PDWR, NRPDWR, NPDWR, STATE. PRIMACY AGENT, MSIS, SYSTEM
200CT, DATA BASE MANAGEMENT SYSTEM, DBMS.
-G-
GIARDIA LAMBLIA
A protozoan that causes more waterborne disease outbreaks in the United States than any
other single identified etiologic agent. Symptoms of giardiasis include diarrhea, fatigue,
abdominal cramps, and possibly other gastrointestinal symptoms.
Filtration and disinfection requirements for surface water systems have been promulgated
to protect against the potential adverse health affects of exposure to Giardia lamblia,
pathogenic viruses, Legionella, and heterotrophic bacteria, as well as many other
pathogenic organisms that are removed by these treatment techniques.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 17
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
See also: E17OLOGIC, PATHOGENIC, BACTI, TOTAL COLIFORM BACTERIA,
FECAL COLIFORM BACTERIA, HETEROTROPHIC BACTERIA, LEG1ONELLAE,
PATHOGENIC VIRUSES, CONTAMINANT.
GGC
An abbreviation for group generation £ode. See GROUP GENERATION CODE.
GRANT ELIGIBLE
A term used to refer to whether or not a public water system in the FRDS-n Data Base is
to be counted in the computation of a State's grant allocation. See also: GRANT
REQUIREMENT.
GRANT REQUIREMENT
In FRDS-II, certain data elements must contain a valid value for a public water system to
be counted when the State's grant allocation is computed. If ANY of these data elements.
are not valued, the public water system will NOT be counted for grant allocation
purposes. This is otherwise referred to as grant eligibility.
NOTE 13 in the Section II, Data Element Descriptions Introduction interprets the
meaning of the several values which appear within Section n next to the heading which
reads, "Grant Requirement," and Section HI, Quick Reference, sub-section B,
Comprehensive Data Element Table, identifies all data elements which must be valued for
a public water system to be considered grant eligible. Contrast with: REGISTRATION
REQUIREMENT. See also: GRANT ELIGIBLE.
GROUND WATER PWS
See GROUND WATER SYSTEM.
GROUND WATER SOURCE
An underground source of water (i.e., the water is extracted via a well). All water in the
zone of saturation is referred to as ground water.
Contrast with: SURFACE SOURCE, GROUND WATER UDISW SOURCE, PURCHASED
SURFACE SOURCE, PURCHASED GROUND WATER SOURCE, PURCHASED
GROUND WATER UDISW SOURCE. See also: PRIMARY SOURCE, AQUIFER,
ARTESIAN AQUIFER, WATER TABLE AQUIFER, ZONE OF SATURATION, WELL.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 18
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
GROUND WATER SYSTEM
A public water system which has a ground water primary source designation.
A ground water system is a public water system that obtains water from one or more
permanently available non-purchased ground water sources, and does not obtain water
from any permanently available surface or ground water UDISW sources (purchased or
non-purchased).
In classifying a public water system as a ground water system, the way in which each
source of water is utilized (i.e., the availability of the source) is of utmost importance.
Contrast with: SURFACE WATER SYSTEM, GROUND WATER UDISW SYSTEM,
PURCHASED SURFACE WATER SYSTEM, PURCHASED GROUND WATER SYSTEM,
PURCHASED GROUND WATER UDISW SYSTEM. See also: GROUND WATER
SOURCE, PRIMARY SOURCE, AVAILABILITY.
GROUND WATER UDISW PWS
See GROUND WATER UDISW SYSTEM.
GROUND WATER UDISW SOURCE
Note: UDISW is an abbreviation for, "Under the Direct Influence of Surface Water."
Any water beneath the surface of the ground with (1) significant occurrence of insects or
other macroorganisms, algae, or large-diameter pathogens such as Giardia lamblia, or (2)
significant and relatively rapid shifts in water characteristics such as turbidity,
temperature, conductivity, or pH which closely correlate to climatological or surface
water conditions.
Contrast with: SURFACE SOURCE, GROUND WATER SOURCE, PURCHASED
SURFACE SOURCE, PURCHASED GROUND WATER SOURCE, PURCHASED
GROUND WATER UDISW SOURCE. See also: PRIMARY SOURCE, AQUIFER,
ARTESIAN AQUIFER, WATER TABLE AQUIFER, ZONE OF SATURATION, WELL.
GROUND WATER UDISW SYSTEM
A public water system which has a ground water under the direct influence of surface
water (UDISW) primary source designation.
A ground water UDISW system is a public water system that obtains water from one or
more permanently available non-purchased ground water UDISW sources, and does not
obtain water from any permanently available surface water sources (purchased or non-
purchased).
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 19
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
In classifying a public water system as a ground water UDISW system, the way in which
each source of water is utilized (i.e., the availability of the source) is of utmost
importance.
Contrast with: SURFACE WATER SYSTEM, GROUND WATER SYSTEM, PURCHASED
SURFACE WATER SYSTEM, PURCHASED GROUND WATER SYSTEM, PURCHASED
GROUND WATER UDISW SYSTEM. See also: GROUND WATER UDISW SOURCE,
PRIMARY SOURCE, AVAILABILITY.
GROUP GENERATION CODE
A group generation code (GGC) is used to communicate to FRDS-n that the user wants
the computer to automatically generate an ID number for a set of related data (e.g., the
name, street, city, state, and zip code of an owner address) that is to be inserted into the
FRDS-II Data Base.
In order to use a GGC, the user must specify the letter "G" in conjunction with a
sequential number on all related items of data. Each data base record in the input file
must have its own unique GGC. By design, the GGC itself is not retained in the FRDS-
II Data Base, but serves in a temporary capacity only. When encountered during update
processing, FRDS-II converts a GGC into the next available ID number (specific to an
individual public water system) for the type of data encountered (e.g., source of water,
geographic area served).
-H-
HETEROTROPHIC BACTERIA
A broad class of organisms which use organic nutrients for growth. This group includes
virtually all of the bacterial pathogens as well as many other innocuous bacteria and those
bacteria which infect when the host's defenses are weakened (opportunistic pathogens).
Filtration and disinfection requirements for surface water systems have been promulgated
to protect against the potential adverse health affects of exposure to Giardia lamblia,
pathogenic viruses, Legionella, and heterotrophic bacteria, as well as many other
pathogenic organisms that are removed by these treatment techniques.
See also: HETEROTROPHIC PLATE COUNT BACTERIA, HPC, PATHOGENIC,
BACTI, TOTAL COLIFORM BACTERIA, FECAL COLIFORM BACTERIA, GIARDIA
LAMBLIA, LEGIONELLAE, PATHOGENIC VIRUSES, CONTAMINANT.
Effective Date: 1/31/93 Release Number: 2.00 Page: Vffl - 20
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
HETEROTROPHIC PLATE COUNT BACTERIA
A measurement of the population density of heterotrophic bacteria by the Heterotrophic
Plate Count (HPC) analytical technique. HPC was previously known as the Standard
Plate Count (SPC) technique. See HETEROTROPHIC BACTERIA, HPC.
HISTORICAL INVENTORY
One of two general classifications of FRDS-n public water system inventory data.
Historical inventory refers to those public water systems that were in the current
inventory at one time, but were assigned to the historical inventory during the conversion
from FRDS 1.5 to FRDS-II, were assigned to the historical inventory by explicit action
of the FRDS Data Base Administrator, or were assigned to the historical inventory as a
result of "total replacement" update processing as described below, and, consequently,
are no longer part of the current inventory.
Conversion from FRDS 1.5 to FRDS-II
In FRDS 1.0 and 1.5, all inventory data relating to public water systems was maintained
in separate fiscal year data bases ... one data base for each Federal fiscal year beginning
with 1979. When this data was consolidated for entry into the FRDS-n Data Base, each
public water system in the individual fiscal year data bases was checked to see if it
existed in the most current fiscal year data base. If it did, the public water system was
placed into the current inventory category. If not, the public water system was placed
into the historical inventory category.
Assigned by explicit action of the FRDS Data Base Administrator
A public water system that has been inactive for a substantial period of time may be
assigned to the historical inventory, at the discretion of the FRDS Data Base
Administrator.
Total Replace Update Processing
If a State submitted a "total replacement" to its inventory of public water systems in the
most recent reporting period, the term current inventory refers to those public water
systems which were reported in that most recent period. Those systems that existed in
the current inventory prior to the update, for which a replacement was not submitted,
would become part of the historical inventory.
The active versus inactive classification is often confused with the current versus
historical classification. Classifying a public water system as active or inactive is
Effective Date: 1/31/93 Release Number: 2.00 Page: Vffl - 21
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
exclusively at the State's discretion. It is the way in which the State indicates the present
operational status of a public water system. Classifying a public water system as part of
the current or historical inventory is performed automatically by the FRDS-II computer
system. It indicates whether or not a public water system is embodied in the most recent
inventory submission from the State.
Contrast with: ACTIVE, CURRENT INVENTORY, INACTIVE. See also: TOTAL
REPLACE UPDATE.
HPC
An abbreviation for the Eeterotrophic Elate Count analytical technique used to measure
the population density of heterotrophic bacteria. HPC was previously known as the
Standard Plate Count (SPC) technique. See HETEROTROPHIC BACTERIA,
HETEROTROPHIC PLATE COUNT BACTERIA.
HUC CODE
An abbreviation for a Hydrologic Unit Code. See HYDROLOGIC UNIT CODE.
HYDROLOGIC UNIT CODE
A code that identifies a hydrologic system which divides the United States and the
Caribbean into 21 major regions. These regions are further subdivided into
approximately 2,150 units that delineate river basins having drainage areas usually greater
than 700 square miles.
The HUC code provides a standardized base for use by water-resources organizations in
the storage, retrieval, and exchange of hydrologic data; the indexing and inventorying of
hydrologic data and information; the cataloging of water-data acquisition activities; and a
variety of other applications.
The hydrologic unit code is eight digits in length, and consists of a two digit region, a
two digit subregion, a two digit accounting unit, and a two digit cataloging unit. Each ;
portion of the HUC code, respectively, defines a drainage basin, form largest to smallest
in size. See also: STORET, RIVER REACH.
Effective Date: 1/31/93 Release Number: 2.00 Page: vm - 22
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
-I-
INACTTVE
A term used to refer to a public water system that is not an active public water system.
Such a system has discontinued operation.
A public water system that has closed permanently is an obvious example of a system that
would be an inactive system.
A public water system that has closed temporarily, but for a substantial period of time,
could be designated as inactive by the State, but not necessarily so. This decision
depends upon State specific policy regarding such systems.
The active versus inactive classification is often confused with the current versus
historical classification. Classifying a public water system as active or inactive is
exclusively at the State's discretion. It is the way in which the State indicates the present
operational status of a public water system. Classifying a public water system as part of
the current or historical inventory is performed automatically by the FRDS-II computer
system. It indicates whether or not a public water system is embodied in the most recent
inventory submission from the State.
Contrast with: ACTIVE, CURRENT INVENTORY, HISTORICAL INVENTORY. See also:
INACTIVE WATER SYSTEM.
INACTIVE PWS
See INACTIVE WATER SYSTEM.
INACTIVE WATER SYSTEM
A public water system that is inactive. Contrast with: ACTIVE WATER SYSTEM. See
also: INACTIVE.
INCORPORATED PLACE
A populated place possessing legally defined boundaries and legally constituted
governmental functions. May serve as a primary county division in some States. See
also: POPULATED PLACE, PRIMARY COUNTY DIVISION.
INDEPENDENT CITY
An incorporated place not included in a county or another county equivalent. Serves as a
county equivalent. See also: INCORPORATED PLACE, COUNTY EQUIVALENT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 23
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
INITIAL COMPLIANCE PERIOD
This definition is applicable only to the Phase I, II, IIB, and V contaminant monitoring
requirements.
For those-contaminants regulated prior to the Phase V rule (i.e., the Phase I rule, the
Phase II rule, and the Phase IIB rule), the initial compliance period is the first full three-
year compliance period which begins at least 18 months after promulgation.
For those contaminants regulated by the Phase V rule, the initial compliance period is
dependent upon the number of service connections a public water system has, as follows:
• If the public water system has ISO or more service connections, the initial compliance
period is the first full three-year compliance period after promulgation (i.e., January,
1, 1993, to December 31, 1995).
• If the public water system has fewer than. 150 service connections, the initial
compliance period is the first full three-year period after the effective date of the
regulation (i.e., January 1, 1996, to December 31, 1998).
Contrast with: REPEAT COMPLIANCE PERIOD. See also: COMPLIANCE CYCLE,
COMPLIANCE PERIOD.
INORGANICS
See INORGANIC CHEMS.
INORGANIC CHEMS
Chemical substances that are characterized by the absence of the chemical element
Carbon.
Contrast with: ORGANIC CHEMS, RADS. See also: CONTAMINANT.
INT
See INTEGER.
INTAKE
The point at which water is withdrawn from a surface water source.x The term intake
refers the intake structure itself (e.g., the float, inlet screen, and anchor).
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 24
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
INTEGER
A SYSTEM 2000™ data element data type. Integer data element values are numeric
whole numbers (i.e., no decimal points are permitted). Contrast with: DECIMAL. See
also: CHARACTER, TEXT. DATE, NUMERIC.
INVENTORY
A term used to refer to public water system inventory data submitted as a part of a
State's quarterly update to FRDS-II. When reported, Inventory data must be segregated
from Sample data, but .may be reported individually or combined with Actions data, as
desired. Contact FRDS Production Control for additional details.
Inventory data refers to that information stored in the following FRDS-II Data Base
records:
C100, PWS-SUMMARY
C300, PWS-ADDRESS-DATA
C400, PWS-SOURCE-ENTTTY-INFO
C480, PWS-SE-TREATMENT-DATA
C500, PWS-GEOGRAPHIC-DATA
C600, PWS-SERVICE-AREAS
C700, PWS-ON-SITE-VISITS
C800, PWS-MILESTONES-EVENTS
C4000, STATE-DISCRETIONARY-DATA
Contrast with: ACTIONS, SAMPLES.
IOC
An abbreviation for JnQrganic Chemical. See: INORGANIC CHEMS.
IOCS
An abbreviation for InQrganic Chemicals. See: INORGANIC CHEMS.
-K-
KEY
A SYSTEM 2000™ term used to refer to a data element for which an internal index is
maintained to optimize retrieval. Contrast with: NON-KEY.
Effective Date: 1/31/93 Release Number: 2.00 Page: Vin - 25
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
-L-
LARGE WATER SYSTEM
This definition is applicable to those NPDWRs which apply to the control of Lead and
Copper.
A water system that serves more than 50,000 persons.
Contrast with: MEDIUM-SIZE WATER SYSTEM, SMALL WATER SYSTEM, See also:
PUBLIC WATER SYSTEM.
LEAD AND COPPER RULE
Regulations promulgated on June 7, 1991, for controlling lead and copper in drinking
water.
The rule encompasses monitoring requirements and treatment technique requirements
that include corrosion control treatment, source water treatment, lead service line
replacement, and public education.
LEAD SERVICE LINE
A service line made of lead which connects the water main to the building inlet and any
lead pigtail, gooseneck, or other fitting which is connected to such lead line.
LEGIONELLAE
Bacteria that have been identified as the cause of legionellosis. It has been estimated that
between 50,000 and 100,000 cases of this disease occur annually within the United
States, and are caused primarily by 1 of the 26 currently recognized species of the genus
Legionella.
Filtration and disinfection requirements for surface water systems have been promulgated
to protect against the potential adverse health affects of exposure to Giardia lamblia,
pathogenic viruses, Legionella, and heterotrophic bacteria, as well as many other
pathogenic organisms that are removed by these treatment techniques:
See also: PATHOGENIC, BACTI, TOTAL COLIFORM BACTERIA, FECAL COLIFORM
BACTERIA, GIARDIA LAMBLIA, HETEROTROPHIC BACTERIA, PATHOGENIC
VIRUSES, CONTAMINANT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 26
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LNr2003
January 31, 1993
-M-
MAJOR VIOLATION
One of two general classifications of some monitoring and reporting (M&R) violations.
Categorization of a violation as "Major" does not apply to sanitary survey M&R,
maximum contaminant level (MCL), treatment technique, public notification (PN), and/or
other types of violations associated with the Lead and Copper Rule.
The definition of what constitutes a major violation differs depending upon the rule in
question. In the absence of a rule-specific definition, the general definition presented
below applies.
TCR
Routine Samples (i.e., violation type 23)
A system that fails to take all (takes no samples) of the required routine samples
in a compliance period.
Repeat Samples (i.e., violation type 25)
A system that does not conduct follow-up monitoring after a total coliform-
positive sample (i.e., takes no repeat samples and/or conducts no speciation for
fecal/E. coli).
SWTR (i.e., violation types 31 and 36)
Systems that fail to take more than 10% of the required samples per reporting period.
GENERAL
An M&R violation in which no samples were collected and/or reported.
Applies only to regular monitoring violations (i.e., violation type 03). Does not apply
to check/repeat/confirmation sampling violations (i.e., violation type 04).
Contrast with: MINOR VIOLATION.
MAXIMUM CONTAMINANT LEVEL
The maximum permissible level of a contaminant in water which is delivered to any user
of a public water system.
MCD
An abbreviation for a Minor £ivil Division. See MINOR CIVIL DIVISION.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 27
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
MCL
An abbreviation for Maximum Contaminant Level. See MAXIMUM CONTAMINANT
LEVEL.
MCLG
An abbreviation for Maximum Contaminant Level Goal. This term replaces the
previously used term of RMCL (i.e., recommended maximum contaminant level).
MCLGs are non-enforceable health goals which are set at the level at which no known or
anticipated adverse effects t>n the health of persons occur and which allows an adequate
margin of safety.
MEDIUM-SIZE WATER SYSTEM
This definition is applicable to those NPDWRs which apply to the Control of Lead and
Copper.
A water system that serves greater than 3,300 persons and less than or equal to 50,000
persons.
Contrast with: LARGE WATER SYSTEM, SMALL WATER SYSTEM. See also: PUBLIC
WATER SYSTEM.
MICROBIOLOGICAL
See BACH.
MINOR CIVIL DIVISION
A political or administrative area of a county or county equivalent, other than an
incorporated place, established by appropriate State or local government authorities and
adopted as a primary county division. MCDs occur in 29 States and in several State
equivalents (e.g., a township in Ohio or a town in Vermont). See also: COUNTY
EQUIVALENT, INCORPORATED PLACE, PRIMARY COUNTY DIVISION, STATE
EQUIVALENT.
MINOR VIOLATION
One of two general classifications of some monitoring and reporting (M&R) violations.
Categorization of a violation as "Minor" does not apply to sanitary survey M&R,
maximum contaminant level (MCL), treatment technique, public notification (PN), and/or
other types of violations associated with the Lead and Copper Rule..
The definition of what constitutes a minor violation differs depending upon the rule in
question. In the absence of a rule-specific definition, the general definition presented
below applies.
Effective Date: 1/31/93 Release Number: 2.00 Page: VHI - 28
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
TCR
Routine Samples (i.e., violation type 24)
A system that fails to take some (but not all) of the required routine samples in a
compliance period.
Repeat Samples (i.e., violation type 26)
A system that fails to take some of the-required repeat samples and/or a system
that fails to speciate at least one (but not all) total coliform-positive samples for
fecal/E. coli.
SWTR (i.e., violation types 31 and 36)
Any other violators (i.e., the M&R violation is NOT a major violation)
GENERAL
An M&R violation in which some, but not all, of the samples required to be collected
and reported were actually collected and/or reported.
Applies only to regular monitoring violations (i.e., violation type 03). Does not apply
to check/repeat/confirmation sampling violations (i.e., violation type 04).
Contrast with: MAJOR VIOLATION.
MODEL STATE INFORMATION SYSTEM
Originally developed for the U.S. EPA, Office of Water Supply (now known as the
Office of Ground Water and Drinking Water). MSIS is a management information
system that was made available to the States to assist them in their data management
activities relating to implementation of the Safe Drinking Water Act, and its associative
National Primary Drinking Water Regulations. See also: FRDS-1I, ACT, SDWA,
NIPDWR, NRPDWR, NPDWR.
MSA
An abbreviation for a Metropolitan Statistical Area. An MSA is a geographic area,
consisting of a large population nucleus together with adjacent communities having a high
degree.of economic and social integration with that nucleus. MSAs are defined in
Federal Information Processing Standard Publication (FIPS PUB) 8-5 entitled,
Metropolitan Statistical Areas (Including CMSAs, PMSAs, and NECMAs). See also:
CMSA, PMSA, NECMA.
MSIS
An abbreviation for the Model State Information System. See MODEL STATE
INFORMATION SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 29
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
-N-
NCC
An abbreviation for EPA's National Computer Center located at Research Triangle Park,
North Carolina.
NCP
An abbreviation for N_on Compliance Pjofile. See also: NCP PROCESSING, NCP
RECORD, NCP WINDOW.
NCP PROCESSING
A process whereby the FRDS-II computer system re-generates NCP windows. See also:
NCP, NCP RECORD, NCP WINDOW, PUP. Contrast with: RECON, VALLINKS.
NCP RECORD
The C1350 Data Base record of the FRDS-II Data Base. See also: NCP, NCP
PROCESSING, NCP WINDOW.
NCP WINDOW
An NCP record which depicts a specific period of time (defined by the window begin
date and the number of months in the window) for a specific contaminant.
For example: If one chose to examine those public water systems having two or more
BACTI MCL violations during the third quarter of Federal fiscal year 1992, he/she could
retrieve public water systems with:
Window begin date (C1351) = 9204 AND
W'indow months (C1353) = 3 AND
(Contaminant (C1357) = 3000 OR
Contaminant (C1357) = 3100) AND
MCL violations (C13S9) > 1
Note: NCP windows do not address/incorporate violations for the following rules:
• TCR
• SWTR
• Lead/Copper
See also: NCP, NCP PROCESSING, NCP RECORD.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 30
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031 -LN-2003
January 31, 1993
NCWS
An abbreviation for a Non-Community public Water System. See NON-COMMUNITY
WATER SYSTEM.
NEAR THE FIRST SERVICE CONNECTION
One of the 20 percent of all service connections in the entire system that are nearest the
water supply treatment facility, as measured by the water transport time within the
distribution system. See also: DISTRIBUTION SYSTEM, SERVICE CONNECTION.
NECMA
An abbreviation for a New England County Metropolitan Area. A NECMA is a
geographic area consisting of a large population nucleus together with adjacent
communities having a high degree of economic and social integration with that nucleus.
NECMAs, however, are for the New England States only. NECMAs are defined in
Federal Information Processing Standard Publication (FIPS PUB) 8-5 entitled,
Metropolitan Statistical Areas (Including CMSAs, PMSAs, and NECMAs). See also:
CMSA, MSA, PMSA.
NIPDWR
An abbreviation for the National Interim Primary Drinking Water Regulations.
Originally published in the Federal Register on December 24, 1976. Amended several
times. Subsequent to the 1986 Amendments to the Safe Drinking Water Act, known as
National Primary Drinking Water Regulations (NPDWR). See also: NRPDWR,
NPDWR, SDWA, ACT, PRIMARY REGULATION, SECONDARY REGULATION.
NON-COMMUNITY PWS
See NON-COMMUNITY WATER SYSTEM.
NON-COMMUNITY WATER SYSTEM
A type of public water system that is not a community public water system.
There are two types of non-community public water systems; a transient non-community
public water system and a non-transient non-community public water system.
Contrast with: COMMUNITY WATER SYSTEM. See also: TRANSIENT NON-
COMMUNITY WATER SYSTEM, NON-TRANSIENT NON-COMMUNITY WATER
SYSTEM, CONSECUTIVE WATER SYSTEM, PUBLIC WATER SYSTEM.
NON-KEY
A SYSTEM 2000™ term used to refer to a data element for which an internal index is
NOT maintained to optimize retrieval. Contrast with: KEY.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 31
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-OOS5-031-LN-2003
January 31. 1993
NON-TRANSIENT NON-COMMUNITY PWS
See NON-TRANSIENT NON-COMMUNITY WATER SYSTEM.
NON-TRANSIENT NON-COMMUNITY WATER SYSTEM
A type of public water system. Non-transient non-community water system means a
public water system that is not a community water system and that regularly serves at
least 25 of the same persons over six months per'year.
Contrast with: COMMUNITY WATER SYSTEM, TRANSIENT NON-COMMUNITY
SYSTEM. See also: NON-COMMUNITY WATER SYSTEM, CONSECUTIVE WATER
SYSTEM, PUBLIC WATER SYSTEM.
NON-PLACE COUNTY EQUIVALENT
A county equivalent that is not an independent city. See also: COUNTY EQUIVALENT,
INDEPENDENT CITY.
NPDWR
An abbreviation for the National Primary Drinking Water Regulations.
Establishes primary regulations pursuant to Section 1412 of the Public Health Service
Act, as amended by the Safe Drinking Water Act.
All National Interim Primary Drinking Water Regulations (NIPDWR) and National
Revised Primary Drinking Water Regulations (NRPDWR) are known as National Primary
Drinking Water Regulations subsequent to the 1986 Amendments to the Safe Drinking
Water Act.
See also: NIPDWR, NRPDWR, SDWA, ACT, PRIMARY REGULATION, SECONDARY
REGULATION.
NRPDWR
An abbreviation for the Rational Revised Primary Drinking Water Regulations.
Originally intended to replace the National Interim Primary Drinking Water Regulations
(NIPDWR). Subsequent to the 1986 Amendments to the Safe Drinking Water Act,
known as National Primary Drinking Water Regulations (NPDWR). .See also: NIPDWR,
NPDWR, SDWA, ACT, PRIMARY REGULATION, SECONDARY REGULATION.
NTNCWS
An abbreviation for a Non-Transient Non-Community public W.ater System. See NON-
TRANSIENT NON-COMMUNITY WATER SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 32
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
NUMERIC
A term used to describe a class of data element values. A numeric data element's values
consist of combinations of the numbers zero through nine, and, if needed, a decimal
point. There are two distinct types of numeric values ... integer values and real values.
Contrast with: ALPHABETIC, ALPHANUMERIC. See also: INTEGER, DECIMAL.
-o-
OGWDW
An abbreviation for the Office of Ground Water and Drinking Water of the United States
Environmental Protection Agency (EPA). Responsible for the establishment and
maintenance of national drinking water regulations, as well as the operation and
maintenance of the Federal Reporting Data System (FRDS-II). See also: ACT, SDWA.
NIPDWR. NRPDWR, NPDWR. FRDS-II.
OPTIMAL CORROSION CONTROL TREATMENT
This definition is applicable to those NPDWRs which apply to the Control of Lead and
Copper.
The corrosion control treatment that minimizes the lead and copper concentrations at
users' taps while insuring that the treatment does not cause the water system to violate
any national primary drinking water regulations.
ORGANICS
See ORGANIC CHEMS.
ORGANIC CHEMS
Chemical substances that are characterized by the presence of the chemical element ,
Carbon in their compounds. The majority of regulated organic compounds are classified
into either Synthetic Organic Chemicals (SOCs) or Volatile synthetic Organic Chemicals
(VOCs). A third classification of regulated organic compounds are the Total
trihalomethanes (TTHM), which are disinfection by-products.
Contrast with: INORGANIC CHEMS, RADS. See also- SOCs, VOCs, TTHM,
CONTAMINANT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 33
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-OOSS-031-LN-2003
January 31.1993
-P-
PATHOGEN
A specific causative agent (as a bacterium or virus) of disease. See also:
PATHOGENIC, PATHOGENIC VIRUSES.
PATHOGENIC
Causing or capable of causing disease. See also: PATHOGEN, PATHOGENIC
VIRUSES.
PATHOGENIC VIRUSES
Viruses are a class of infectious agents which are extremely small (smaller than bacteria)
and reproduce only within cells of a suitable living host such as humans. They contain
genetic material surrounded by a protein coat. Pathogenic viruses, by definition, are
those that adversely affect health. See also: PATHOGEN, PATHOGENIC, TOTAL
COLIFORM BACTERIA, FECAL COLIFORM BACTERIA, HETEROTROPHIC
BACTERIA, GIARDIA LAMBLIA, LEGIONELLAE, CONTAMINANT, VIRUS.
Filtration and disinfection requirements for surface water systems have been promulgated
to protect against the potential adverse health affects of exposure to Giardia lamblia,
pathogenic viruses, Legionella, and heterotrophic bacteria, as well as many other
pathogenic organisms that are removed by these treatment techniques.
See also: PATHOGENIC, BACTI, TOTAL COLIFORM BACTERIA, FECAL COLIFORM
BACTERIA, GIARDIA LAMBLIA, HETEROTROPHIC BACTERIA, LEGIONELLAE,
PATHOGEN, CONTAMINANT.
PHASE I RULE
Regulations promulgated on July 8, 1987 for 8 Volatile synthetic Organic Chemicals .
(VOCs) and 51 Unregulated Chemicals. Refer to 52 FR 25690. See also: PHASE II
RULE, PHASE IIB RULE, PHASE V RULE.
PHASE H RULE
Regulations promulgated on January 30, 1991, for 10 Volatile synthetic Organic
Chemicals (VOCs), 14 Synthetic Organic Chemicals (SOCs), 2 water treatment
chemicals, 7 Inorganic Chemicals (lOCs), 24 Unregulated Organic Chemicals, and 6
Unregulated Inorganic Chemicals. Refer to 56 FR 3526. See also: PHASE I RULE,
PHASE IIB RULE. PHASE V RULE.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 34
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31. 1993
PHASE US RULE
Regulations promulgated on July 1, 1991, for 4 Synthetic Organic Chemicals (SOCs) and
1 Inorganic Chemical (IOC), revisions to the monitoring requirements for the Phase I
VOCs, and technical corrections/clarifications to the Phase II rule. Refer to 56 FR
30266. See also: PHASE 1 RULE, PHASE II RULE, PHASE V RULE.
PHASE V RULE
Regulations promulgated on July 17, 1992, for 3 Volatile synthetic Organic Chemicals
(VOCs), IS Synthetic Organic Chemicals (SOCs), and 5 Inorganic Chemicals (lOCs),
revisions to the list of Unregulated Organic and Inorganic Chemicals, and technical
corrections/clarifications to the Phase I, n, and IIB rules. Refer to 57 FR 31776. See
also: PHASE 1 RULE, PHASE II RULE, PHASE IIB RULE.
PLANT
See TREATMENT FACILITY.
PMSA
An abbreviation for a Primary Metropolitan Statistical Area. A PMSA is a geographic
area consisting of a large population nucleus together with adjacent communities having a
high degree of economic and social integration with that nucleus.
Unlike an MSA, however, PMSA is a subdivision or major component of a consolidated
metropolitan statistical area (CMSA) which has more than one million people and meets
certain other specific requirements. PMSAs and CMSAs are defined in Federal
Information Processing Standard Publication (FTPS PUB) 8-5 entitled, Metropolitan
Statistical Areas (Including CMSAs, PMSAs, and NECMAs). See also: CMSA, MSA,
NECMA.
POINT OF DISINFECTANT APPLICATION
The point at which the water being disinfected is no longer subject to surface runoff.
POINT-OF-ENTRY
The point at which drinking water enters a house or building.
The term "Point-of-Entry" is often confused with and incorrectly interchanged with
"Entry Point." In actuality, the two terms refer to completely different locations which
are not interrelated.
Contrast with: ENTRY POINT, POINT-OF-USE. See also: POINT-OF-ENTRY
TREATMENT DEVICE, SERVICE CONNECTION.
Effective Date: 1/31/93 Release Number: 2.00 Page: VJJI - 35
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
POINT-OF-ENTRY TREATMENT DEVICE
A treatment device applied to the drinking water entering a house or building for the
purpose of reducing contaminants in the drinking water distributed throughout the house
or building.- Contrast with: PO1NT-OF-VSE TREATMENT DEVICE. See also: POINT-
OF-ENTRY.
POINT-OF-USE
The point at which drinking water is.obtained from a single tap.
Contrast with: ENTRY POINT, POINT-OF-ENTRY. See also: POINT-OF-USE
TREATMENT DEVICE, SERVICE CONNECTION.
POINT-OF-USE TREATMENT DEVICE
A treatment device applied to a single tap used for the purpose of reducing contaminants
in drinking water at that one tap. Contrast with: POINT-OF-ENTRY TREATMENT
DEVICE. See also: POINT-OF-USE.
POPULATED PLACE
A concentration of residential population.
PRIMACY
See PRIMARY ENFORCEMENT RESPONSIBILITY.
PRIMACY AGENT
The agency of the State government which has been granted primary .enforcement
responsibility (primacy) ... the agency which has jurisdiction over public water systems.
See also: STATE, PRIMARY ENFORCEMENT RESPONSIBILITY.
PRIMARY COUNTY DIVISION
One of a set of principal territorial units into which a county or county equivalent is
completely subdivided without overlap for census purposes. All counties and non-place.
county equivalents are so subdivided. See also: COUNTY EQUIVALENT, NON-PLACE
COUNTY EQUIVALENT, CENSUS COUNTY DIVISION, INCORPORATED PLACE,
MINOR CIVIL DIVISION, UNORGANIZED TERRITORY.
PRIMARY ENFORCEMENT RESPONSIBILITY
The primary responsibility for administration and enforcement of primary drinking water
regulations and related requirements applicable to public water systems within a State.
See also: ACT, SDWA, NIPDWR, NRPDWR, NPDWR, PRIMACY AGENT, STATE.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIH - 36
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
PRIMARY REGULATION
A drinking water regulation that applies to public water systems, and that specifies
maximum contaminant levels and monitoring requirements for contaminants deemed to
have an adverse effect on health. Related to the protection of the public health. Contrast
with: SECONDARY REGULATION. See also: NIPDWR, NRPDWR, NPDWR.
PRIMARY SOURCE
A designation of the type of water system based upon the types of water sources that are
utilized, as well as the way in which the sources are utilized. Used in compliance
determination processing.
Determination of primary source is based upon two factors. The types of sources being
utilized by a public water system, and the availability of those sources (e.g., used on a
permanent, seasonal, interim, emergency basis).
A specific hierarchy is followed in determining the primary source. It is as follows:
1) Initially, all permanently available sources are examined.
2) If a non-purchased surface source is encountered, the public water system is
considered to be a surface water system, and the determination process is complete.
3) If a purchased surface source is encountered, the public water system is considered to
be a purchased surface water system, and the determination process is complete.
4) If a non-purchased ground water UDISW source is encountered, the public water
system is considered to be a ground water UDISW system, and the determination
process is complete.
5) If a purchased ground water UDISW source is encountered, the public water system
is considered to be a purchased ground water UDISW system, and the determination
process is complete.
6) If a non-purchased ground water source is encountered, the public water system is
considered to be a ground water system, and the determination process is complete.
7) If a purchased ground water source is encountered, the public water system is
considered to be a purchased ground water system, and the determination process is
complete.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 37
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
8) If there are no permanently available sources, all sources are treated equally,
regardless of their individual availability, and steps 2 through 7 are repeated.
PRINCIPAL MERIDIAN
A principal meridian is an imaginary north-south surveyor's line which has been defined
in conjunction with an imaginary east-west line (Le., a base line) from which township
coordinates are determined. By convention, principal meridians are identified by name.
Townships are plots of land, each approximately six miles to the side (i.e., 36 square
miles) defined under the Rectangular Survey System of the U.S. Department of Interior,
Bureau of Land Management. See also: BASE LINE.
PUBLIC WATER SUPPLY
See PUBLIC WATER SYSTEM.
PUBLIC WATER SYSTEM
A system that provides piped water to^the public for human consumption. To qualify as
a public water system, a system must have IS or more service connections, or regularly
serve an average of at least 25 individuals 60 or more days per year.
Although some State regulations differ in the definition of what constitutes a public water
system, drinking water obtained from individual household wells, and the like, generally
are not public water systems.
Commonly known as a PWS.
According to the Federal definition, a public water system is either a community public
water system, a transient non-community public water system, or a non-transient non-
community public water system.
See also: COMMUNITY WATER SYSTEM. NON-COMMUNITY WATER SYSTEM,
TRANSIENT NON-COMMUNITY WATER SYSTEM, NON-TRANSIENT NON-
COMMUNITY WATER SYSTEM, CONSECUTIVE WATER SYSTEM.
PUP
An abbreviation for Post Update Processing.
After each update of the FRDS-II Data Base, three processes are performed (the PUPS),
as needed. The re-generation of NCP records, reconciliation, and establishment or. re-
establishment of violation links to enforcements and enforcement links to violations. See
also: NCP PROCESSING, PUPS, RECON, VALLINKS.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIH - 38
-------
FRDS-O DATA ELEMENT DICTIONARY SDC-0055-031 -LN-2003
January 31, 1993
PUPS
An abbreviation for the three Post Update Processing functions. See also: PUP.
PURCHASED GROUND WATER PWS
See PURCHASED GROUND WATER SYSTEM.
PURCHASED GROUND WATER SOURCE
A source of water that is purchased from a supplier whose primary source is ground
water.
Contrast with: SURFACE SOURCE, GROUND WATER SOURCE, GROUND WATER
UDISW SOURCE, PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER
UDISW SOURCE. See also: PRIMARY SOURCE.
PURCHASED GROUND WATER SYSTEM
A public water system which has a purchased ground water primary source designation.
A purchased ground water system is a public water system that obtains water from one or
more permanently available purchased ground water sources, and does not obtain water
from any permanently available surface or ground water UDISW sources (purchased or
non-purchased), or from any permanently available non-purchased ground water sources.
In classifying a public water system as a purchased ground water system, the way in
which each source of water is utilized (i.e., the availability of the source) is of utmost
importance.
Contrast with: SURFACE WATER SYSTEM, GROUND WATER SYSTEM, GROUND
WATER UDISW SYSTEM, PURCHASED SURFACE WATER SYSTEM, PURCHASED
GROUND WATER UDISW SYSTEM. See also: PURCHASED GROUND WATER
SOURCE, PRIMARY SOURCE, AVAILABILITY.
PURCHASED GROUND WATER UDISW PWS
See PURCHASED GROUND WATER UDISW SYSTEM.
PURCHASED GROUND WATER UDISW SOURCE
A source of water that is purchased from a supplier whose primary source is ground
water under the direct influence of surface water (UDISW).
Contrast with: SURFACE SOURCE, GROUND WATER SOURCE, GROUND WATER
UDISW SOURCE, PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER
SOURCE. See also: PRIMARY SOURCE.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 39
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
PURCHASED GROUND WATER UDISW SYSTEM
A public water system which has a purchased ground water UDISW primary source
designation.
A purchased ground water UDISW system is a public water system that obtains water
from one or more permanently available purchased ground water UDISW sources, and
does not obtain water from any permanently available surface water sources (purchased
or non-purchased), or from any permanently available non-purchased ground water
UDISW sources.
In classifying a public water system as a purchased ground water UDISW system, the
way in which each source of water is utilized (i.e., the availability of the source) is of
utmost importance.
Contrast with: SURFACE WATER SYSTEM, GROUND WATER SYSTEM, GROUND
WATER UDISW SYSTEM, PURCHASED SURFACE WATER SYSTEM, PURCHASED
GROUND WATER SYSTEM. See also: PURCHASED GROUND WATER UDISW
SOURCE, PRIMARY SOURCE, AVAILABILITY.
PURCHASED SURFACE PWS
See PURCHASED SURFACE WATER SYSTEM.
PURCHASED SURFACE SOURCE
A source of water that is purchased from a supplier whose primary source is surface.
Contrast with: SURFACE SOURCE, GROUND WATER SOURCE, GROUND WATER
UDISW SOURCE, PURCHASED GROUND WATER SOURCE, PURCHASED GROUND
WATER UDISW SOURCE. See also: PRIMARY SOURCE.
PURCHASED SURFACE WATER SYSTEM
A public water system which has a purchased surface water primary source designation,
A purchased surface water system is a public water system that obtains water from one or
more permanently available purchased surface water sources, and does not obtain water
from any permanently available non-purchased surface water sources.-
In classifying a public water system as a purchased surface water system, the way in
which each source of water is utilized (i.e., the availability of the source) is of utmost
importance.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 40
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Contrast with: SURFACE WATER SYSTEM, GROUND WATER SYSTEM, GROUND
WATER UDISW SYSTEM, PURCHASED GROUND WATER SYSTEM, PURCHASED
GROUND WATER UDISW SYSTEM. See also: PURCHASED SURFACE WATER
SOURCE, PRIMARY SOURCE, AVAILABILITY.
PURCHASED PWS
See PURCHASED SURFACE WATER SYSTEM, PURCHASED GROUND WATER
SYSTEM, PURCHASED GROUND WATER UDISW SYSTEM.
PURCHASED SOURCE
See PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER SOURCE,
PURCHASED GROUND WATER UDISW SOURCE.
PURCHASED WATER
See PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER SOURCE,
PURCHASED GROUND WATER UDISW SOURCE.
PURCHASED WATER SOURCE
See PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER SOURCE,
PURCHASED GROUND WATER UDISW SOURCE.
PURCHASED WATER SYSTEM
See PURCHASED SURFACE WATER SYSTEM, PURCHASED GROUND WATER
SYSTEM, PURCHASED GROUND WATER UDISW SYSTEM.
PWS
An abbreviation commonly used to refer to a Public Water System. See also: PUBLIC
WATER SYSTEM, COMMUNITY WATER SYSTEM, NON-COMMUNITY WATER
SYSTEM, TRANSIENT NON-COMMUNITY WATER SYSTEM, NON-TRANSIENT NON-
COMMUNITY WATER SYSTEM.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 41
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
-R-
RADIOLOGICAL
SeeRADS.
RADS
An abbreviation used to refer to the natural occurring, man-made, and photon emitting
radioactive contaminants in drinking water. Contrast with: BACTI, TURBIDITY,
CHEMS. See also: CONTAMINANT.
RECON
A process whereby the FRDS-II computer system performs a "reconciliation" of
generated data element values.
For example: If the State provided a new population served for a public water system,
reconciliation results in the re-calculation of the value assigned to the population
category.
See also: PUP. Contrast with: NCP PROCESSING, VALLINKS.
RECORD
See DATA BASE RECORD.
REGISTRATION REQUIREMENT
This term is used to characterize and delineate which FRDS-H data element values are
necessary in order for a public water system, or some other event related to that public
water system (e.g., violation, enforcement, variance/exemption, etc.), to get "recorded"
into the FRDS-II Data Base. There are four different registration requirements. They
are as follows:
1 Operationally required
The FRDS-II computer system cannot process data related to a public water system
without a value for this data element.
Examples:
• PWS-ID to insert a new public water system
• PWS-SE-RECORD-TYPE to insert a new source or other entity
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 42
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-20Q3
January 31. 1993
2 ProgrammaticaUy required
Based upon programmatic need, EPA has determined that a value must always be
reported for this data element for public water system inventory, violation,
enforcement, sample, milestone, or variance/exemption/other related data to be
inserted into the FRDS-II Data Base.
Examples:
PWS-TYPE to insert a new public water system,
PWS-SE-CODE to insert a new source or entity,
VIO-TYPE to insert a new violation,
ENF-ACTION-DATE to insert a new enforcement,
VE-RECORD-TYPE to insert a new variance/exemption
3 Operationally required, conditionally
Under certain circumstances, the FRDS-II computer system cannot process data
related to a public water system without a value for this data element.
Examples:
• VIO-ID if inserting a new violation,
• ENF-ID if inserting a new enforcement,
• VE-ID if inserting a new variance/exemption/other related data, turbidity waiver,
or filtration requirement event
4 ProgrammaticaUy required, conditionally
Based .upon programmatic need, EPA has determined that, under certain
circumstances, a value must be reported for this data element for public water system
inventory, violation, enforcement, sample, milestone, or variance/exemption other
related data to be inserted into the FRDS-II Data Base.
Examples:
• PWS-SEASON-BEGIN-MMDD and PWS-SEASON-END-MMDD if inserting a
non-community PWS,
• VIO-CONTAMINANT if inserting an MCL or M/R violation
Effective Date: 1/31/93 Release Number: 2.00 Page: vm - 43
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Section III, Quick Reference, sub-section B, Comprehensive Data Element Table,
identifies all data elements which have a registration requirement.
Contrast with: GRANT REQUIREMENT.
REPEAT COMPLIANCE PERIOD
This definition is applicable only to the Phase I, II, IIB, and V contaminant monitoring
requirements.
Any subsequent compliance period after the initial compliance period.
Contrast with: INITIAL COMPLIANCE PERIOD. See also: COMPLIANCE CYCLE,
COMPLIANCE PERIOD.
RESIDUAL DISINFECTANT CONCENTRATION
The concentration of disinfectant measured in mg/1 in a representative sample of water.
See also: CT, DISINFECTANT CONTACT TIME.
RIVER REACH
River reaches are linear sections of streams, lakes, reservoirs, estuaries, etc. that are
linked to form a skeletal structure which represents the branching patterns of surface
water drainage systems. An individual river reach code is an 11 digit number which
consists of an 8 digit USGS hydrologic unit code coupled with a 3 digit segment number
defined by the U.S. EPA STORET office. Thus, the river reach is a subdivision of the
hydrologic unit code.
The hydrologic unit code is comprised of a two digit region, a two digit subregion, a two
digit accounting unit, and a two digit cataloging unit. Each portion of the HUC code,
respectively, defines a drainage basin, from largest to smallest in size.
The segment number is arbitrarily assigned without regard for the hydrological
relationships of the river reaches. However, reaches are linked in a hydrological
sequence which allows analysis in either an upstream or downstream order.
See also: STORET, HYDROLOGIC UNIT CODE.
RMCL
An abbreviation for Recommended Maximum Contaminant Level. This term is no
longer used in the setting of drinking water regulations. Instead, the term MCLG (i.e.,
maximum contaminant level goal) is used.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 44
-------
FRDS-D DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
-s-
SAMPLES
A term used to refer to Sample data submitted as a part, of a State's quarterly update to
FRDS-II. When reported, Sample data must be segregated from Inventory and Actions
data (i.e., it must be reported individually). Contact FRDS Production Control for
additional details.
Sample data refers to that information stored in the following FRDS-II Data Base record:
C2100, SAMPLE-DATA
Contrast with: ACTIONS. INVENTORY.
SANITARY SURVEY
An on-site review and evaluation of the water source, facilities, equipment, operation,
and maintenance of a public water system for the purpose of evaluating the adequacy of
such source, facilities, equipment, operation, and maintenance for producing and
distributing safe drinking water.
SCHEMA
See DATA BASE RECORD.
SCHEMA RECORD
See DATA BASE RECORD.
SDWA
An abbreviation for the Safe Drinking Water Act, as amended in 1986. Public Laws
93-523 and 99-339, respectively. Amends the Public Health Service Act. See also:
ACT, NIPDWR, NRPDWR, NPDWR.
SECONDARY REGULATION
A drinking water regulation that applies to public water systems, and that specifies
maximum contaminant levels for any contaminant in drinking water that is deemed to
have an adverse effect on the public welfare. Related to the aesthetic quality of water
(e.g., color, taste, odor, etc.). Secondary regulations may vary from State to State and
are not Federally enforceable. Contrast with: PRIMARY REGULATION. See also:
NIPDWR, NRPDWR, NPDWR.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIE - 45
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31, 1993
SEDIMENTATION
A treatment process for removal of solids before filtration by gravity or separation.
SERVICE CONNECTION
In general, the point at which the water distribution system pipe connects to a consumer's
water meter in a home or building. This definition is not completely comprehensive,
however, since water meters are not always present.
In the absence of water meters, the number of service connections is dependent upon the
number of water bills that, are paid.
For example, an apartment building that pays a single water bill for all of its residents
(regardless of the number of residents) is said to have a single service connection. On
the other hand, a duplex, whose 2 residents each pay their own water bill, is said to have
2 service connections.
See also: NEAR THE FIRST SERVICE CONNECTION, SYSTEM WITH A SINGLE
SERVICE CONNECTION, POINT-OF-ENTRY. Contrast with: ENTRY POINT, POINT-
OF-USE.
SERVICE LINE SAMPLE
A one-liter sample of water [collected in accordance with §141.86(b)(3)] that has been
standing for at least 6 hours in a service line. Contrast with: FIRST DRAW SAMPLE.
SINGLE FAMILY STRUCTURE
This definition is applicable to those NPDWRs which apply to the Control of Lead and
Copper.
A building constructed as a single-family residence that is currently used as either a
residence or a place of business.
SLOW SAND FILTRATION
A treatment process involving passage of raw water through a bed of sand at low velocity
resulting in substantial paniculate removal by physical and biological mechanisms.
SMALL WATER SYSTEM
This definition is applicable to those NPDWRs which apply to the Control of Lead and
Copper.
A water system that serves 3,300 persons or fewer.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 46
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
Contrast with: LARGE WATER SYSTEM, MEDIUM-SIZE WATER SYSTEM. See also:
PUBLIC WATER SYSTEM.
SNC
An abbreviation for Significant Eton-Compliance (pronounced SNICK).
SNC status is assigned to a public water system when certain types of violations have
been incurred over a specific period of time. The types of violations which result in the
SNC designation are based upon the contaminant (e.g., coliform) or rule (e.g., Lead and
Copper) in question.
soc
An abbreviation for a Synthetic Organic Chemical. See SOCs.
SOCs
An abbreviation for Synthetic Qrganic Chemicals. One of three classifications of
regulated organic chemical compounds. SOCs are used in the manufacture of a wide
variety of agricultural and industrial products. Pesticides and herbicides are the best-
known types of SOCs. Contrast with: INORGANIC CHEMS, VOCs, TTHM, RADS. See
also: ORGANIC CHEMS, CONTAMINANT.
SOURCE OF WATER
See SURFACE SOURCE, GROUND WATER UDISW SOURCE, GROUND WATER
SOURCE, PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER
SOURCE, PURCHASED GROUND WATER UDISW SOURCE, PRIMARY SOURCE,
AVAILABILITY.
STATE
The term State can mean any of the 50 United States, the District of Columbia, the
Virgin Islands of the U.S., the Commonwealth of Puerto Rico, American Samoa, Guam,
the Northern Mariana Islands, the Trust Territory of the Pacific Islands (presently known
by its component entities which are the Federated States of Micronesia, the Republic of
the Marshall Islands, and the Republic of Palau), any Indian reservation that has been
granted primary enforcement responsibility, or any of the 10 EPA regional offices. It
refers to the agency of the State government which has jurisdiction over public water
systems.
If no State agency possesses such jurisdiction, the term State means the Regional
Administrator, U.S. EPA. See also: PRIMACY AGENT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VHI - 47
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
STATE EQUIVALENT
For the purposes of FIPS PUB 55-2, Guideline: Codes for Named Populated Places,
Primary County Divisions, and other Locational Entities of the United States and
Outlying Areas, one of the following: District of Columbia, American Samoa, Guam,
Northern Mariana Islands, Puerto Rico, U.S. Minor Outlying Islands, Virgin Islands of
the U.S., Federated States of Micronesia, Marshall Islands, or Palau.
STORET
An abbreviation for the U.S. EPA STOrage and RETrieval system for Water Quality
Data. EPA's STORET office developed the river reach concept that is utilized in FRDS-
H. See also: HYDROLOGIC UNIT CODE, RIVER REACH.
SUB-SCHEMA
See DATA BASE RECORD.
SUB-SCHEMA RECORD
See DATA BASE RECORD.
SURFACE PWS
See SURFACE WATER SYSTEM.
SURFACE SOURCE
A surface source of water. Water which is open to the atmosphere and subject to surface
runoff.
Water that has not entered the ground through infiltration or that has not been returned to
the atmosphere by evaporation flows over the ground surface and is classified as direct
run-off. Direct run-off is water that moves over saturated or impermeable surfaces, and
in stream channels or other natural or artificial storage sites. Examples of surface water
sources include sources such as an ocean, lake, pond, stream, river, reservoir, etc.
Contrast with: GROUND WATER SOURCE, GROUND WATER UD1SW SOURCE,
PURCHASED SURFACE SOURCE, PURCHASED GROUND WATER SOURCE,
PURCHASED GROUND WATER UDISW SOURCE. See also: PRIMARY SOURCE.
SURFACE WATER SYSTEM
A public water system which has a surface water primary source designation.
A surface water system is a public water system that obtains water (in whole or in part)
from one or more permanently available surface water sources.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIII - 48
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
_____ . January 31, 1993
In classifying a public water system as a surface water system, the way in which each
source of water is utilized (i.e., the availability of the source) is of utmost importance.
Contrast with: GROUND WATER SYSTEM, GROUND WATER UDISW SYSTEM,
PURCHASED SURFACE WATER SYSTEM, PURCHASED GROUND WATER SYSTEM,
PURCHASED GROUND WATER UDISW SYSTEM. See also: SURFACE WATER
SOURCE, PRIMARY SOURCE, AVAILABILITY.
SURFACE WATER TREATMENT RULE
Regulations promulgated on June 29, 1989, for public water systems using surface water
sources or ground water under the direct influence of surface water that include:
• Criteria under which filtration is required and procedures by which the States are to
determine which systems must install filtration
• Disinfection requirements.
The filtration and disinfection requirements are treatment technique requirements to
protect against the potential adverse health effects of exposure to Giardia lamblia,
viruses, Legionella, and heterotrophic bacteria, as well as many other pathogenic
organisms that are removed by these treatment techniques.
Refer to 54 FR 27486.
See also: FILTRATION, GIARDIA LAMBLIA, GROUND WATER UDISW SOURCE,
HETEROTROPHIC BACTERIA, LEGIONELLAE, PATHOGENIC VIRUSES, VIRUS.
SWTR
An abbreviation for the Surface Water Treatment Rule. See SURFACE WATER
TREATMENT RULE.
SYSTEM
See PUBLIC WATER SYSTEM.
SYSTEM 2000™
A general purpose data base management system that is commercially available. S2K is
currently marketed by the SAS Institute of Cary, North Carolina, and is licensed for use
on the U.S. EPA's National Computer Center (NCC). FRDS-II is one of several EPA
application systems that operate within the SYSTEM 2000" DBMS environment. See
also: DATA BASE MANAGEMENT SYSTEM, DBMS, FRDS-II.
Effective Date: 1/31/93 Release Number: 2.00 Page: Vffl - 49
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
SYSTEM WITH A SINGLE SERVICE CONNECTION
A system which supplies drinking water to consumers via a single service line. See also:
SERVICE CONNECTION.
S2K
An abbreviation for the SYSTEM 2000™ data base management system. See also:
SYSTEM 2000™.
-T-
TCR
An abbreviation for the Total £oliform Rule. See TOTAL COL1FORM RULE.
TEXT
A SYSTEM 2000™ data element data type. Text data element values are alphanumeric
with all extraneous blank spaces (i.e., leading spaces, trailing spaces, multiple embedded
spaces) retained. Contrast with: CHARACTER. See also: INTEGER, DECIMAL,
DATE, ALPHANUMERIC.
TNCWS
An abbreviation for a Transient ^on-Community public Water System. See TRANSIENT
NON-COMMUNITY WATER SYSTEM.
TNTC
An abbreviation for Too Numerous jo Qount. See TOO NUMEROUS TO COUNT.
TOO NUMEROUS TO COUNT
More than 200 bacterial colonies on a 47 mm diameter membrane filter used for coliform
detection. Contrast with: CONFLUENT GROWTH.
TOTAL COLIFORM BACTERIA
A group of closely related organisms used to evaluate the effectiveness of water
treatment, to determine the integrity of the distribution system, and to signal the possible
presence of fecal contamination. Total coliforms, which include the fecal coliforms, are .
usually not pathogenic in themselves. However, their presence in drinking water
indicates the potential presence of fecal pathogens which are frequently associated with
waterborne disease outbreaks.
Effective Date: 1/31/93 Release Number: 2.00 Page: VIH - 50
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
The measure of total coliform bacteria has been used by public health officials and
professionals for decades as the primary means of assessing the microbiological quality of
drinking water.
Total coliform is a primary contaminant in the National Primary Drinking Water
Regulations.
See also: BACH, FECAL COLIFORM BACTERIA, HETEROTROPHIC BACTERIA,
GIARDIA LAMBLIA, LEGIONELLAE, PATHOGENIC VIRUSES. PATHOGEN,
CONTAMINANT, WATERBORNE DISEASE OUTBREAK.
TOTAL COLIFORM RULE
Regulations promulgated on June 29, 1989, which amended the NPDWRs for total
coliform bacteria, including fecal coliforms and Escherichia coli (E.coli).
See also: BACTI, FECAL COLIFORM BACTERIA, HETEROTROPHIC BACTERIA.
GIARDIA LAMBLIA, LEGIONELLAE, PATHOGENIC VIRUSES, PATHOGEN,
CONTAMINANT, WATERBORNE DISEASE OUTBREAK.
TOTAL REPLACE UPDATE
A process wherein a State chooses to replace its complete inventory of public water
systems, actions (i.e., violations and enforcements), or samples maintained in FRDS-II
with a set of inventory or actions data which they provide to EPA.
Historical data (i.e., C900) and DBA data (i.e., C4050) are generated by the FRDS-II
computer system. As such, total inventory or actions replace processing may result in an
update to, but does not replace this data.
Due to the nature of the data, on-site visit data (i.e., C700), variance and exemption data
(i.e., C3000 and C3100), and state discretionary data (i.e., C4000) are not replaced
during total inventory or actions replace processing. They may be modified ONLY
through a traditional update.
See also: CURRENT INVENTORY, HISTORICAL INVENTORY. Contrast with:
TRADITIONAL UPDATE.
Effective Date: 1/31/93 Release Number: 2.00 Page: vm - 51
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-OQ55-031-LN-2003
January 31. 1993
TRADITIONAL UPDATE
A process whereby a State chooses to change its inventory, actions (i.e., violations and
enforcements), variances & exemptions, and/or state discretionary data through the
process of inserting new data (DIM code "I"), and modification and/or deletion of
existing data (DIM code "M" and "D").
See also: DIM CODE. Contrast with: TOTAL REPLACE UPDATE.
TRANSDINT NON-COMMUNITY PWS
See TRANSIENT NON-COMMUNITY WATER SYSTEM.
TRANSDINT NON-COMMUNITY WATER SYSTEM
A type of public water system. Transient non-community water system means a public
water system that is not a community water system and is not a non-transient non-
community water system.
Contrast with: COMMUNITY WATER SYSTEM, NON-TRANSIENT NON-COMMUNITY
SYSTEM. See also: NON-COMMUNITY WATER SYSTEM, CONSECUTIVE WATER
SYSTEM, PUBLIC WATER SYSTEM.
TREATMENT FACDLITY
A treatment facility refers to the site at which source water is treated. This encompasses
a wide range ... from the large and complex metropolitan water treatment plant to a small
and simple ground water well which has a chlorinator attached to disinfect the water.
TRfflALOMETHANES
SeeTHM.
THM
An abbreviation for a JriHaloMethane. A trihalomethane is one of the families of
organic compounds derived from methane wherein three of the four hydrogen atoms in
the methane are each substituted by a halogen atom in the molecular structure. See
TTHM.
TTHM
An abbreviation for Total IriHaloMethane. One of three classifications of regulated
organic chemical compounds. Total trihalomethanes are by-products of disinfection.
TTHM is the sum of the concentration (in mg/1) of the following trihalomethane
compounds: trichloromethane (chloroform), dibromochloromethane,
bromodichloromethane, and tribromomethane (bromoform). Contrast with: INORGANIC
CHEMS, SOCs, VOCs, RADS. See also: ORGANIC CHEMS, CONTAMINANT.
Effective Date: 1/31/93 Release Number: 2.00 Page: VTO - 52
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31, 1993
TURBIDITY
Turbidity in water is a non-specific measure of suspended material in drinking water. It
is measured by determining die degree of light scattering caused by participates in a
sample. Turbidity has been used for decades as an indicator of drinking water quality by
indicating the presence of such particulates as clay, silt, finely divided organic and
inorganic matter, and microorganisms. Contrast with: BACH, CHEMS, RADS. See
also: CONTAMINANT.
TURBIDITY WAIVER
The means by which a public water system is permitted to exceed the one turbidity unit
(TU) monthly average maximum contaminant level requirement.
Up to five TUs may be allowed if the supplier of water can demonstrate to the State that
the higher turbidity does not do any of the following:
• Interfere with disinfection.
* Prevent maintenance of an effective disinfectant agent throughout the distribution
system.
• Interfere with microbiological determinations.
Contrast with: VARIANCE, EXEMPTION.
-U-
UDISW
An abbreviation for Under the Direct Influence of Surface Water. See also: GROUND
WATER UDISW SOURCE, GROUND WATER UDISW SYSTEM.
UNORGANIZED TERRITORY
An area of a county or county equivalent, not subdivided into minor civil divisions or
including any incorporated places, that has been bounded and named for census purposes.
Occurs only in those States and State equivalents that have minor civil divisions. An
unorganized territory always serves as a primary county division. See also: COUNTY
EQUIVALENT, MINOR CIVIL DIVISION, INCORPORATED PLACE, STATE
EQUIVALENT, PRIMARY COUNTY DIVISION.
Effective Date: 1/31/93 Release Number: 2.00 Page: VHI - 53
-------
FRDS-H DATA ELEMENT DICTIONARY SDC-0055-031-LN-2003
January 31. 1993
UNREGULATED CONTAMINANT
A contaminant for which a monitoring requirement has been established in the NPDWR
but for which a Maximum Contaminant Level has not been established. Unregulated
contaminant monitoring requirements were promulgated in the Phase I and Phase II
Rules.
uses
An abbreviation for-the United States .Geological Survey. The agency who defmed the
list of acceptable hydrologic unit code values that have been adopted as a Federal
Information Processing Standard (i.e., defined in FiPS PUB 103), and that are used in
FRDS-IL
-V-
VALLINKS
A process whereby the FRDS-II computer system attempts to link each violation to its
related enforcements and each enforcement to its related violations. See also: PUP.
Contrast with: NCP PROCESSING, RECON.
VARIANCE
A means by which a public water system is permitted ro vary from a.{r.axiimtm
contaminant level requirement, treatment requirement, or both, of an app1.ico.bi4 piiivnary
drinking water regulation.
A variance to a maximum contaminant level requirement may be granted if each of the
following conditions are met:
• Due to the characteristics of the raw water sources which arc reasonably available to
the public water system, the public water system cannoi meet the requirements
respecting the maximum contaminant level despite application of the best technology.
treatment techniques, or other means, which are found to be generally available
(taking cost into consideration);
• The granting of the variance will not result in an unreasonable risk to the health of
persons served by the public water system.
Effective Date: 1/31/93 Release Number: 2.00 Page: VUi - 34
-------
FRDS-n DATA ELEMENT DICTIONARY SDC-0055-03 l-LN-2003
January 31. 1993
A variance to a treatment requirement may be granted upon a finding that the public
water system applying for the variance has demonstrated that such treatment technique is
not necessary to protect the health of the population served due to the nature of the raw
water sources available to the public water system.
Contrast with: EXEMPTION, TURBIDITY WAIVER.
VIOLATION
A public water system's non-conformance to Federal or State drinking water regulations.
See also: ACTIONS. Contrast with: ENFORCEMENT ACTION.
VIRUS
In terms of the national drinking water program, a virus is of fecal origin and is
infectious to humans by waterborne transmission. See also: PATHOGENIC VIRUSES.
voc
An abbreviation for a Volatile synthetic Qrganic Chemical. See VOCs.
VOCs
An abbreviation for Volatile synthetic Qrganic Chemicals. One of three classifications of
regulated organic chemical compounds. VOCs are a broad class of synthetic chemical
compounds used commercially as degreasing agents, paint thinners, varnishes, glues,
dyes, and pesticides. They are most commonly used in urban industrial areas, where
they can contaminate ground water if improperly disposed. Contrast with: INORGANIC
CHEMS, SOCs, TTHM, RADS. See also: ORGANIC CHEMS, CONTAMINANT.
VULNERABLE
A term used to refer to the susceptibility of a public water system to a specific
contaminant or group of contaminants. See also: VULNERABILITY ANALYSIS.
VULNERABILITY ANALYSIS
. A process whereby a determination is made as to whether or not a public water system is.
vulnerable to contamination of a given type. See also: VULNERABLE.
Effective Date: 1/31/93 Release Number: 2.00 Page: Vm - 55
-------
FRDS-H DATA ELEMENT DICTIONARY SD€-0055-Q3 l-LN-2003
January ffi. 1993
-W'-
see
WATER TABLE AQUIFER
One of two general classifications of aquifers.. A Water table aquifer-consists .of
unconfined ground water (i.e., not confined by impermeable material).that i?
the upper surface ot%e%o*e Jpf saturation, :Cantrast with: ARTESIAN AQWFER. $&*
also: AQUIFER, ZONE OF SATURAtfdN^ROVND WATER SOURCE, WELL.
WATER TREATMENT PLANT
See TREATMENT FACILITY.
WATERBOR&E DISEASE OUTBREAK
The significant occurrence of :acute.in$ecttou&'jiUiiess, epidemiologically associated, with
the ingestion of >yaier fr6m a public, wk^^y^tj^^rhicn is deficient in treatment;-as.
determined, by the appropriate local or -Stare agency..
WELL
A.narrow shaft that can be used to extract ground water from an aquifer. .The amount of
water that can be pumped from a well ^depends on-jthe character of the aquifer and,the : •
construction pf-the well.. Common VWUl cdnsftjiiCfion methods iricladeidiig, bored, drivea,
drille4, or jetted. See also: AQVIFEA, ARTESIANXQUIFER? WATER TABLE
AQVIFER..GROUND WATER SOURCE.
WELL HEAD
A term which refers to the location of a water weU or'well field.
-z-
ZONE OF SATURATION
The zone located below the root zone where the ground water has reached %: level at
which all of the openings or voids in the earth's materials anf^lled..
AQUIFER, ARTESIAN AQUIFER, WATER TABLE AQUIFER. GROUND
SOURCE.
Effective Date: 1/31/93 Release Number: 2.0Q Psge^ni? 56
•itVA COVUNMENT PHNT1NC OTT|CC41M> -
------- |