## Introduction

This guide documents the specifications for submitting data for the
Unregulated Contaminant Monitoring Regulation (UCMR) program to the U.S.
Environmental Protection Agency (EPA) using Extensible Markup Language
(XML) standards. Only laboratories that are registered with EPA's
Central Data Exchange (CDX) can submit data to the Safe Drinking Water
Accession and Review System (SDWARS), the information system that
supports the collection of data for the UCMR.

Preliminary analytical data are entered by laboratories on behalf of the
public water systems (PWSs) participating under the rule. The PWS can
then review their data online. Data approved by the PWS are then
available for state and EPA review before being transmitted to the
National Drinking Water Contaminant Occurrence Database (NCOD). To learn
more about CDX and how to register, contact the CDX Helpdesk by phone
(1-888-890-1995) or by e-mail at EPACDX@CSC.COM.

## Error Corrections and Resubmissions

**Correcting Errors**

If a submission contains errors that prevent it from being parsed into
SDWARS, CDX will notify you of the error by sending a notification to
your "MyCDX" inbox (see Figure 1) and your registered e-mail address.

*Figure 1. CDX Inbox with Error Notification*

Data checks occur at two stages during the file upload
process---authentication and data validation. Authentication occurs as
soon as CDX receives the file. CDX authenticates your account and the
file name. These messages are sent to your "MyCDX" inbox and your e-mail
address registered with CDX. Table 1 shows the error messages you could
receive.

*Table 1. Authentication Error Messages*

  -----------------------------------------------------------------------
  **Error Message**

  TBD
  -----------------------------------------------------------------------

The data validation function performs checks by the parser and
additional checks in two parts---format and UCMR validations. There are
two different error messages for XML---parsing errors and data
validation errors. CDX will parse the file. If the file is not valid and
well-formed, CDX will provide a text file listing the parsing errors
(see Figure 2). This file is sent to your "MyCDX" inbox. While a copy of
the error notification will be sent to your registered e-mail address,
you can only view the list of errors through the error notice in your
"MyCDX" inbox. The parsing error messages are generic messages. If 50
errors are found, CDX stops parsing the file and sends the error
message, noting that the file may contain additional errors.

*Figure 2. Error Message from Parser*

TBD

If the file is valid and well-formed, CDX will conduct data validation
and verifications according to UCMR. If the file does not pass the
checks, CDX will provide an error message to your "MyCDX" inbox. Here
too, a copy of the notification will be sent to your e-mail address
directing you to view the error details online.

The message (see Figure 3) is numbered and provides an explanation, the
extract of the record that contains the error, and an administrator
message. The administrator message is applied to assist technical
support when typical solutions do not work. The technical support staff
may request the associated administrator message to assist them and the
programmers in identifying a solution to an error. The text file lists
up to the first 50 errors in the submitted file. Message number one of
Figure 3 does not include an administrator message while message number
two does.

SDWARS verifies the data by first checking general format and verifies
IDs (i.e., correct format for date, valid PWS ID, valid method, valid
facility ID, valid sample point ID). Table 2 lists common error messages
for data formatting and general validations. These messages identify the
probable cause for the error.

*Figure 3. Text File with Details of Errors*

TBD

*Table 2. Common Formatting/Validation Error Messages*

  -----------------------------------------------------------------------
  **Error message**

  analytical result is already on record

  analytical result is not on record

  facility identifier is not five digits

  facility is not on record

  lab is not on record

  PWS is not on record

  sample collection date postdates sampling event data entry

  sample collection date predates publication of the final rule

  sample collection date predates the start of monitoring

  sampling event is not on record

  sampling point identifier contains non-letter, non-digit characters

  sampling point is not on record

  sampling schedule is not on record

  user identifier is not formatted correctly
  -----------------------------------------------------------------------

**Resubmitting Data**

A file containing only original data or including original and
replacement data can be submitted. The analyte results data may be
replaced only if the existing results have not been approved. When
resubmitting replacement data, you must use the code "r" in the
TransactionPurposeIdentifier element. The "r" indicates the transaction
contains records that will replace existing records. The resubmission
will overwrite the existing data in the SDWARS database. You may confirm
that the data was overwritten by viewing the records in the SDWARS Web
application.

Users from your laboratory are the only users that may edit your
sampling and analytical data. You can only edit data that is in "lab
hold" status in the SDWARS database. If you need to edit data that it
has already been approved, you can contact the PWS to return the control
of the record back to your lab for corrections. If the record was also
approved by the PWS, then the PWS must request that the SDWARS database
administrator/Workbook Manager return editing rights to your laboratory.
The SDWARS database administrator/Workbook Manager can be contacted
through CDX Technical Support.

**Checking the Range of Data Values**

In addition to the edit validations described in the preceding sections,
SDWARS reviews several fields for specific values or ranges. In some
cases it may entirely reject the record for failing the range check,
while in others it may create a warning that requires the laboratory to
manually review and either approve or modify the results. This section
describes each of these fields.

**UCMR Data Range Checks - ?????????????????????**

The UCMR has specific minimum values for different analytes. Information
about minimum reporting levels (MRLs) is in the following regulation:

\- 40 CFR, Part 141, "Monitoring requirements for the unregulated
contaminants;" final rule, January 4, 2007

**SDWARS Data Range Checks**

SDWARS will check the range of some data values. Table 4 shows the list
of elements that SDWARS checks. SDWARS assigns a range or value that the
element must satisfy, and the range or value it should satisfy. The
"must" checks will prevent the data from loading and will result in an
error notification to your "MyCDX" inbox and registered e-mail address.
However, the "should" checks will not result in preventing the data from
loading. Instead, the "should" checks will flag results as having
potential errors for your laboratory to confirm. **If data are submitted
that violate the "should" criteria, then the status of those records
will be "lab hold" and you must use the Web forms to override the range
check (or correct the value through Web forms or a replacement file)**.
You cannot approve data where a range check notification has not been
addressed. Thus, the data cannot be sent to the PWS to approve and will
remain in the "lab hold" status.

You have two options to edit a range check. In order to override the
warning message and approve the data, you must use the Web forms. If, in
reviewing the data, you believe the data should be corrected, you may do
so either by using the Web form or by correcting the data in your system
and issuing a replacement transaction.

*Table 4. Range Checks Performed by SDWARS*

  --------------------------------------------------------- ---------------
  **Error**                                                 **Can be
                                                            overridden?**

  concentration fortified result value is less than one     N
  half of the minimum reporting level                       

  concentration fortified result value is more than the     Y
  maximum reasonable value                                  

  field sample result value is less than the minimum        N
  reporting level                                           

  field sample result value is more than the maximum        Y
  reasonable value                                          

  field sample result value is not null with indication of  N
  below minimum reporting level                             

  field sample result value is null with no indication of   N
  below minimum reporting level                             

  lab fortified sample matrix duplicate result value is     N
  less than 0.0001                                          

  lab fortified sample matrix duplicate result value is     Y
  less than one tenth of the minimum reporting level        

  lab fortified sample matrix duplicate result value is     Y
  more than the maximum reasonable value                    

  lab fortified sample matrix result value is less than     N
  0.0001                                                    

  lab fortified sample matrix result value is less than one Y
  tenth of the minimum reporting level                      

  lab fortified sample matrix result value is more than the Y
  maximum reasonable value                                  
  --------------------------------------------------------- ---------------

**[UCMR XML]{.underline}**

Click here to download the XML Schema.

*Cory will provide the location!*

## UCMR File Structure Tree Diagram

This section provides a graphical depiction of the UCMR file structure.
It is not possible to provide a picture of the entire tree diagram at
once due to size limitations. In order to present the tree diagram, we
broke the file structure into four sections. Each section shows the
detail for a specific portion of the file structure.

Reading from left to right and top to bottom, Figure 4 shows the root
element of SafeDrinkingWaterSubmission and its sub-elements,
TransactionPurposeIdentifier and SamplingEventDetails. The sub-elements
of SamplingEventDetails are also shown in Figure 4. The
SchedulerIdentifierDetails section can be seen in Figure 5 and the
SampleDetails section of the file structure can be seen in Figures 6.

*Figure 4. SafeDrinkingWaterSubmission Tree Diagram -- Root Element and
sub-elements*

![](media/image1.png){width="7.499305555555556in"
height="3.479861111111111in"}

Figure 5 shows the sub-element SamplingEventDetails and its
sub-elements, SchedulerIdentifierDetails, SampleCollectionDate and
SampleDetails. The sub-elements of SchedulerIdentifierDetails are also
shown in Figure 5.

*Figure 5. SafeDrinkingWaterSubmission Tree Diagram with
SchedulerIdentifierDetails*

![](media/image2.png){width="7.499305555555556in"
height="4.810416666666667in"}

Figure 6 shows the sub-element SampleDetails and its sub-elements,
SampleIdentifier, LaboratoryIdentificationCode, LaboratoryCommentText,
and SampleMethodAnalyteDetails. The sub-elements of
SampleMethodAnalyteDetails are also shown in Figure 6.

*Figure 6. SafeDrinkingWaterSubmission Tree Diagram with
SampleMethodAnalyteDetails*

![](media/image3.png){width="7.49375in" height="5.708333333333333in"}

**Logical Structure**

This section contains tables defining the UCMR file content models. Each
section is titled with the parent or container element and is followed
by a table that lists the children or the contents of the container. The
sub-element column indicates the sub-element name. The description
column defines the element in the sub-element column of the table. A
more detailed definition with element attributes and associated code
lists (e.g., Analyte Code List and Method Code List) is in UCMR Data
Dictionary section.

**Namespace**

All elements belong to the namespace:

http://www.exchangenetwork.net/schema/sdwars/1

**The SafeDrinkingWaterSubmission Element**

The root element for the UCMR XML document is
SafeDrinkingWaterSubmission, as shown in Table 5. There are two elements
below the root element. They are TransactionPurposeIdentifier and
SamplingEventDetails. Table 6 describes the SamplingEventDetails
sub-element.

*Table 5. Top-Level Sub-Elements of SafeDrinkingWaterSubmission*

  ------------------------------ --------------------------------------------
  **Sub-element**                **Description**

  TransactionPurposeIdentifier   This sub-element identifies the type of
                                 backend processing.

  SamplingEventDetails           This sub-element contains the sample event
                                 related data elements.
  ------------------------------ --------------------------------------------

**SamplingEventDetails Sub-Element**

This container sub-element contains secondary sub-elements that hold the
sample event related data elements. Table 7 describes the
ScheduleIdentifierDetails sub-element and Table 8 describes the
SampleDetails sub-element.

*Table 6. SamplingEventDetails Sub-Elements*

  --------------------------- --------------------------------------------
  **Sub-element**             **Description**

  ScheduleIdentifierDetails   This sub-element contains schedule related
                              data elements.

  SampleCollectionDate        The date the sample is collected.

  SampleDetails               This sub-element contains sample related
                              data elements.
  --------------------------- --------------------------------------------

**ScheduleIdentifierDetails Sub-Element**

This container sub-element contains secondary sub-elements that hold the
schedule related data elements.

*Table 7. ScheduleIdentifierDetails Sub-Elements*

  -------------------------- --------------------------------------------
  **Sub-element**            **Description**

  PublicWaterSystemCode      This sub-element is the code used to
                             identify each PWS.

  FacilityIdentifier         This sub-element is an identification code
                             established by the state or, at the state's
                             discretion, by the PWS, following the format
                             of a 5-digit number unique within each PWS
                             for each applicable facility.

  SamplePointIdentifier      This sub-element is an identification code
                             established by the state, or at the state's
                             discretion, by the PWS, unique within each
                             applicable facility, for each applicable
                             sampling location.

  ScheduleEventCode          This sub-element indicates the sequence
                             number associated with the specific event.

  MonitorTypeCode            This sub-element is the code identifying
                             list 1 (AM) or list 2 (SS) monitoring.
  -------------------------- --------------------------------------------

**SampleDetails Sub-Element**

This container sub-element contains secondary sub-elements that hold the
sample related data elements. Table 9 describes the
SampleMethodAnalyteDetails sub-element.

*Table 8. SampleDetails Sub-Elements*

  ------------------------------ --------------------------------------------
  **Sub-element**                **Description**

  SampleIdentifier               This sub-element uniquely identifies
                                 containers, or groups of containers, which
                                 hold the water samples collected at the same
                                 sampling location during the same sample
                                 collection date.

  LaboratoryIdentificationCode   This sub-element is the code, assigned by
                                 EPA, used to identify each laboratory.

  LaboratoryCommentText          This sub-element is used for ancillary
                                 information about the laboratory.

  SampleMethodAnalyteDetails     This sub-element contains method analyte
                                 related data elements.
  ------------------------------ --------------------------------------------

**SampleMethodAnalyteDetails Sub-Element**

This container sub-element contains secondary sub-elements that hold the
method analyte related data elements.

*Table 9. SampleMethodAnalyteDetails Sub-Elements*

  ------------------------------------------- --------------------------------------------
  **Sub-element**                             **Description**

  MethodCode                                  This sub-element is the identification code
                                              of the analytical method used.

  AnalyteCode                                 This sub-element is the identification code
                                              of the analyte being analyzed.

  SampleTypeCode                              This sub-element identifies the type of
                                              sample collected and/or prepared, as well as
                                              the fortification level.

  ResultMeasure                               This sub-element contains the actual numeric
                                              value of the analysis for chemical and
                                              microbiological results for: field samples;
                                              laboratory fortified matrix samples;
                                              laboratory fortified sample matrix
                                              duplicates; and concentration fortified.

  ResultBelowMinimumReportingLevelIndicator   This sub-element is a \"Yes/No\" indicator
                                              specifying whether the ResultMeasure value
                                              was below the measurable threshold for this
                                              analyte.

  ReviewStatusIdentifier                      This sub-element is the identifier
                                              indicating the review status of this sample
                                              method analyte data set.
  ------------------------------------------- --------------------------------------------

**UCMR Data Dictionary**

**Introduction**

This section contains the data dictionary for the UCMR schema. This
section also contains introductory materials about how to read the data
dictionary. Only the data content elements are defined here. Group
defining elements have a description in the logical structure of the
UCMR File Structure Tree Diagram section.

**How to Read This Data Dictionary**

The data dictionary contains the element name, definition of the
element, characteristics for the element, its relationship in the
hierarchy, and a code list (when applicable). Below you will find
further explanation for each segment of the definition in the dictionary
structure.

**Element Name**

[Definition]{.underline}:

This section provides a textual definition of the element and how it is
used in the schema.

[Characteristics]{.underline}:

The characteristics of an element provide information on the use of the
element. Characteristics include data type (alpha- numeric or numeric),
size or string length, requirement of optional or mandatory, and
occurrences.

[Parent Hierarchy]{.underline}:

The parent hierarchy section gives the relationship of the element to
the root element.

[Code List]{.underline}:

The code list presents all valid values for a particular "code" element,
when applicable.

**A Elements**

**AnalyteCode**

[Definition]{.underline}:

This element is the identification code of the analyte being analyzed.
The analyte must be applicable for the Method provided. See Appendix A
-- Analytes-to-Methods for a list of Methods and their Analytes.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-4

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

> SampleDetails
>
> SampleMethodAnalyteDetails

[Code List]{.underline}:

  ------------------- ---------------------------------------------------
  **Analyte Code**    **Analyte Name**

  2004                alachlor ESA

  2027                acetochlor

  2045                metolachlor

  2051                alachlor

  2096                hexahydro-1,3,5-trinitro-1,3,5-triazine

  2221                dimethoate

  2314                N-nitroso-dimethylamine

  2316                N-nitroso-di-n-propylamine

  U001                terbufos sulfone

  U002                2,2\',4,4\'-tetrabromodiphenyl ether

  U003                2,2\',4,4\',5-pentabromodiphenyl ether

  U004                2,2\',4,4\',5,5\'-hexabromobiphenyl

  U005                2,2\',4,4\',5,5\'-hexabromodiphenyl ether

  U006                2,2\',4,4\',6-pentabromodiphenyl ether

  U007                1,3-dinitrobenzene

  U008                2,4,6-trinitrotoluene

  U009                alachlor OA

  U010                acetochlor ESA

  U011                acetochlor OA

  U012                metolachlor ESA

  U013                metolachlor OA

  U014                N-nitroso-diethylamine

  U015                N-nitroso-di-n-butylamine

  U016                N-nitroso-methylethylamine

  U017                N-nitroso-pyrrolidine
  ------------------- ---------------------------------------------------

**F Elements**

**FacilityIdentifier**

[Definition]{.underline}:

This element is an identification code established by the state or, at
the state's discretion, by the PWS, following the format of a 5-digit
number unique within each PWS for each applicable facility. Leading
zeros are required.

[Characteristics]{.underline}:

Data Type: N

Size: 5

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

ScheduleIdentifierDetails

**L Elements**

**LaboratoryCommentText**

[Definition]{.underline}:

This element is used for ancillary information about the laboratory.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-4000

Requirement: Optional

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

**LaboratoryIdentificationCode**

[Definition]{.underline}:

This element is the code, assigned by EPA, used to identify each
laboratory. The code usually begins with the standard 2-character postal
state abbreviation or region code and the remaining 5 numbers are unique
to each Lab in the state.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 7

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

**M Elements**

**MethodCode**

[Definition]{.underline}:

This element is the identification code of the analytical method used.
Labs must be approved for a method, as displayed on the Lab home page.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-20

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

SampleMethodAnalyteDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Method Code**             **Method Description**

  EPA 521                     EPA 521

  EPA 525.2                   EPA 525.2

  EPA 527                     EPA 527

  EPA 529                     EPA 529

  EPA 535                     EPA 535
  --------------------------- -------------------------------------------

**MonitorTypeCode**

[Definition]{.underline}:

This element is the code identifying list 1 (AM) or list 2 (SS)
monitoring.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 2

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

ScheduleIdentifierDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Monitor Type Code**       **Monitor Type Description**

  AM                          Assessment Monitoring (List 1)

  SS                          Screening Survey (List 2)
  --------------------------- -------------------------------------------

**P Elements**

**PublicWaterSystemCode**

[Definition]{.underline}:

This element is the code used to identify each PWS which usually begins
with the standard 2-character postal state abbreviation or region code
and the remaining 7 numbers are unique to each PWS in the state, with
the exception of Utah where the code is 4 characters followed by 5
digits.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 9

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

ScheduleIdentifierDetails

**R Elements**

**ResultBelowMinimumReportingLevelIndicator**

[Definition]{.underline}:

This element is a \"Yes/No\" indicator specifying whether the
ResultMeasure value was below the measurable threshold for this analyte.
If ResultMeasure is provided, this **must** be "n" or non-existent.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1

Requirement: Optional

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

SampleMethodAnalyteDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Result Below MRL Code**   **Result Below MRL Description**

  N                           No

  Y                           Yes
  --------------------------- -------------------------------------------

**ResultMeasure**

[Definition]{.underline}:

This element contains the actual numeric value of the analysis for
chemical and microbiological results for: field samples; laboratory
fortified matrix samples; laboratory fortified sample matrix duplicates;
and concentration fortified. If a value is provided,
ResultBelowMinimumReportingLevelIndicator **must** be "n" or
non-existent.

[Characteristics]{.underline}:

Data Type: N

Size: 0.00000-99999.99999

Requirement: Optional

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

SampleMethodAnalyteDetails

**ReviewStatusIdentifier**

[Definition]{.underline}:

This element the identifier indicating the review status of this sample
method analyte data set.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 2

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

SampleMethodAnalyteDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Review Status Code**      **Review Status Description**

  10                          Lab Hold

  30                          Lab Approve
  --------------------------- -------------------------------------------

**S Elements**

**SampleCollectionDate**

[Definition]{.underline}:

The date the sample is collected. This must **not** be a future date.

[Characteristics]{.underline}:

Data Type: Date

Size: YYYYMMDD

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

**SampleIdentifier**

[Definition]{.underline}:

This element uniquely identifies containers, or groups of containers,
which hold the water samples collected at the same sampling location
during the same sample collection date. This value must be unique for
the lab.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-30

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

**SamplePointIdentifier**

[Definition]{.underline}:

This element is an identification code established by the state, or at
the state's discretion, by the PWS, unique within each applicable
facility, for each applicable sampling location. This element **must**
contain only letters and numbers (a-z, A-Z, 0-9).

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-20

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

ScheduleIdentifierDetails

**SampleTypeCode**

[Definition]{.underline}:

This element identifies the type of sample collected and/or prepared, as
well as the fortification level.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1-5

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

SampleDetails

SampleMethodAnalyteDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Sample Type Code**        **Sample Type Description**

  CF                          Concentration Fortified

  FS                          Field Sample

  LFSM                        Lab Fortified Sample Matrix

  LFSMD                       Lab Fortified Sample Matrix Duplicate
  --------------------------- -------------------------------------------

**ScheduleEventCode**

[Definition]{.underline}:

This element indicates the sequence number associated with the specific
event.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 3

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

SamplingEventDetails

ScheduleIdentifierDetails

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Schedule Event Code**     **Schedule Event Description**

  SE1                         Schedule Event 1

  SE2                         Schedule Event 2

  SE3                         Schedule Event 3

  SE4                         Schedule Event 4
  --------------------------- -------------------------------------------

**T Elements**

**TransactionPurposeIdentifier**

[Definition]{.underline}:

The date the sample is collected.

[Characteristics]{.underline}:

Data Type: AlphaNumeric

Size: 1

Requirement: Mandatory

Occurrences: Once

[Parent Hierarchy]{.underline}:

SafeDrinkingWaterSubmission

[Code List]{.underline}:

  --------------------------- -------------------------------------------
  **Transaction Purpose       **Transaction Purpose Description**
  Identifier**                

  O                           Original

  R                           Replacement
  --------------------------- -------------------------------------------

**Appendix A**

**Analytes-to-Methods**

  ------------ ----------- -------------------- --------------------------
  **Analyte    **Method    **Maximum Reasonable **Minimum Reporting
  Code**       Code**      Value**              Level**

  2004         EPA 535     300                  1

  2027         EPA 525.2   99                   2

  2045         EPA 525.2   99                   1

  2051         EPA 525.2   99                   2

  2096         EPA 529     99                   1

  2221         EPA 527     70                   0.7

  2314         EPA 521     0.99                 0.002

  2316         EPA 521     0.99                 0.007

  U001         EPA 527     40                   0.4

  U002         EPA 527     30                   0.3

  U003         EPA 527     90                   0.9

  U004         EPA 527     70                   0.7

  U005         EPA 527     80                   0.8

  U006         EPA 527     50                   0.5

  U007         EPA 529     80                   0.8

  U008         EPA 529     80                   0.8

  U009         EPA 535     300                  2

  U010         EPA 535     300                  1

  U011         EPA 535     300                  2

  U012         EPA 535     300                  1

  U013         EPA 535     300                  2

  U014         EPA 521     0.99                 0.005

  U015         EPA 521     0.99                 0.004

  U016         EPA 521     0.99                 0.003

  U017         EPA 521     0.99                 0.002
  ------------ ----------- -------------------- --------------------------