United States
Environmental Protection
Agency
Office of Enforcement
and Compliance Assurance
Washington, DC 20460
EPA300-B-96-013
September 1997
&EPA
Discharge Monitoring
Report (DMR) Electronic
Data Interchange (EDI)
Implementation Guideline
-------
-------
DMREDI IMPLEMENTATION GUIDELINE
TABLE OF CONTENTS
SECTION 1 - INTRODUCTION 1-1
1.1 Purpose of Guideline 1-1
1.2 Scope and Applicability 1-1
1.2.1 Project Overview 1-1
1.2.2 DMREDI Objective 1-3
1.2.3 EDI Approach 1-3
1.3 Responsible Entity 1-3
1.4 Introduction to EDI 1-5
1.5 How to Use the Implementation Guideline 1-5
1.6 References , 1-5
SECTION 2 - BUSINESS ISSUES 2-1
2.1 Implementation Considerations 2-1
2.2 Timing of Transactions 2-1
2.3 Modes of Operation 2-2
2.4 Security 2-2
2.5 Backup and Recovery Procedures 2-2
2.6 Audit Considerations 2-3
SECTION 3 - LEGAL CONSIDERATIONS 3-1
3.1 General Introduction 3-1
3.2 Record Keeping 3-1
3.3 Authentication 3-1
3.4 Trading Partner Agreement 3-2
3.5 Third-Party Agreement 3-2
3.6 Laws, Rules, and Regulations 3-2
SECTION 4 - ENVIRONMENTS 4-1
4.1 System Architecture 4-1
4.2 Application Integration 4-3
4.3 Translation 4-3
SECTION 5 - MAINTENANCE 5-1
5.1 Maintaining Guidelines 5-1
5.2 Maintaining ASC X12 Standards 5-1
5.3 Version/Release 5-1
SECTION 6 - COMMUNICATIONS 6-1
6.1 General Introduction 6-1
6.2 Protocols 6-1
6.3 Point-to-Point 6-1
6.4
Third-Party Services 6-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
6.5 Network Interconnects 6-2
SECTION 7 - MISCELLANEOUS 7-1
7.1 Industry Business Models 7-1
7.2 Related Business Topics 7-2
7.3 EDI Vendor References . 7-2
SECTION 8 - GLOSSARY OF TERMS 8-1
SECTION 9 - FORMS AND DOCUMENTS 9-1
9.1 ASC X12 Transactions 9-1
9.1.1 Header/Trailer Format 9-1
9.1.2 863 Report of Test Results Transaction Set 9-1
9.1.3 997 Functional Acknowledgment Form . . 9-2
9.1.4 842 Nonconformance Report Transaction Set 9-2
9.2 ASC X12 Documents 9-2
9.3 Sample of DMR (EPA Form 8700-02 (Rev. 9-88) 9-3
9.4 PCS Code Tables 9-4
9.5 Mapping of DMR Data Items to ASC X12 Segments 9-4
SECTION 10 - AGENCY CONVENTIONS,
INTERCHANGE CONTROL & TRANSACTION SETS 10-1
10.1 Introduction 10-1
10.2 X12 EDI Transmission Control Structure . 10-4
10.2.1 Control Segments 10-7
APPENDIX A A-l
APPENDIXB B-l
B.I Functional Acknowledgment - Transaction Set 997 B-l
B.2 997 Functional Acknowledgment Detail Mapping B-l5
B.3 997 Functional Acknowledgment Sample Transmission B-20
APPENDIX C C-l
C.I Report (863 - Report of Test Results) C-l
C.2 Sample Transmission C-34
C.3 Detailed Mapping C-40
APPENDIXD D-l
D. 1 PCS Error Response to Discharge Monitoring Report (842 - Nonconformance
Report) D-l
D.2 Detailed Mapping D-31
D.3 Sample Transmission D-37
-------
DMREDI IMPLEMENTATION GUIDELINE
SECTION 1 - INTRODUCTION
1.1 Purpose of Guideline
This supplement to the EPA EDI Implementation Guideline outlines the implementation
of the Electronic Data Interchange (EDI) interface for submission of the Discharge
Monitoring Report (DMR) to the U.S. EPA National Pollutant Discharge Elimination
System (NPDES).
1.2 Scope and Applicability
The Implementation Guideline is intended to provide NPDES permittees with the
information necessary to understand the EDI goals of EPA. This document contains
the specifics for conducting business with EPA using EDI for DMR submissions. For
copies of the DMR EDI Implementation Guideline contact the EPA Public
Information Center, U.S. EPA, Headquarters (3404), 401 M Street, S.W.
Washington, D.C. 20460 - Phone: (202) 260-2080 or the Water Resource Center,
Headquarters (4101) - Phone: (202) 260-7786.
1.2.1 Project Overview
Under the Federal Water Pollutant Control Act Amendments for 1972, EPA, in
coordination with the States, was authorized to issue permits to facilities discharging
pollutants into the country's navigable waterways and to limit the amount of pollutants
discharged. The National Pollution Discharges Elimination System (NPDES) requires
each permitted facility to periodically monitor its discharges and report the results to
EPA regional or state enforcement personnel using a Discharge Monitoring Report
(DMR).
The regulated facilities are self-monitoring. Each permittee monitors the levels and
types of pollutants discharged and reports them to EPA Regions or NPDES delegated
states. The DMR details the results of facilities self-monitoring activities. Upon
receipt of the DMR, EPA Regions or NPDES delegated States enter the data into the
Permit Compliance System (PCS). PCS is one of EPA's largest computerized
information systems, with approximately 15 million individual records in its data
base. PCS serves six major purposes in support of the planning and implementation
of the NPDES program. Some of the functions of PCS include:
• Maintaining an inventory of NPDES permittees;
• Providing data for Congress, State legislatures, and the general public;
• Supporting effective NPDES program implementation;
• Promoting sound planning, evaluation, and decision-making;
1-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
• Facilitating the use of NPDES-reported data; and
• Contributing to the formulation of NPDES policy and regulations.
The DMR form contains information on sample discharge data. Facilities voluntarily
report discharge levels of regulated pollutants (conventional, toxic, and
unconventional) as provided for in the 25 data elements of the DMR form. The DMR
data is loaded into PCS. A comparison of the actual pollutant discharge levels, to the
levels allowed by the facility's permit, is performed by PCS. The DMR data is used
by PCS to determine facility compliance with the issued permits.
The EPA Regions and NPDES states are responsible for maintaining a current and
accurate PCS data base. Currently, submitting DMR forms and entering DMR data
into PCS is largely a manual process. The DMR forms are submitted on a periodic
basis as specified by their permit (the majority of DMRs are submitted on a monthly
basis). Facility personnel physically complete the DMR form and mail the form to
the regulating EPA Region or NPDES State. The DMR data is then manually keyed
from the form into the PCS data base. This manual process has become increasingly
time consuming and expensive for both EPA and its permitted facilities.
The entry of DMR data into PCS is accomplished using one of three methods: on-
line data entry, microcomputer entry and upload, or batch data entry. On-line data
entry is an interactive method of PCS input allowing users to input data directly into
the EPA mainframe using terminal emulation. Microcomputer entry and upload is
accomplished using PC data entry software. Batch data entry involves the entry of
transactions into the system without interactive edit and correction. Regardless of the
method used to enter and edit PCS transactions, data is initially stored in temporary
"hold" files. On a biweekly basis, a PCS data base update job is executed which
edits the data and enters the accepted transactions into the PCS data base. Upon the
completion of this job, users receive an Update Audit Report that describes 'the
actions taken by the update in processing their data. For each transaction, the status
report provides a final verification that newly entered data has been successfully
incorporated into the PCS data base and identifies previously undetected errors that
need to be corrected (the rejected transactions).
Electronic Data Interchange (EDI) is offered as an alternative data entry mechanism
for those NPDES facilities, Regions or States supplying DMR data to EPA, or
specifically, the PCS on EPA's National Computer Center (NCC) mainframe. This
document provides guidance to those permittees (herein referred to as trading
partners) who voluntarily elect to submit DMR data electronically to EPA.
1.2.2 DMR EDI Objective
The objective of EPA's DMR EDI Program is to offer electronic reporting options to
the regulated community who must submit DMRs to EPA. The information can be
1-2
-------
DMR EDI IMPLEMENTATION GUIDELINE,
transmitted and loaded directly into the PCS data base. This also provides both state
and federal agencies easy access to current DMR information.
1.2.3 EDI Approach
The EPA has developed an approach to EDI that will benefit all participants - the
regulated community, the state environmental program offices, and service and
product suppliers. This approach involves:
• Implementing EDI using ANSI ASC X12 standards;
• Using transaction sets 863 Report of Test Results, 997 Functional
Acknowledgment, and 842 Nonconformance Report; and developing EPA-
specific convention documents;
• Developing national standards for the implementation of EDI DMR; and
• Seeking voluntary collaboration with the NPDES permitted facilities.
The transmission of the discharge monitoring report through EDI is consistent with
the Agency's electronic reporting (ER) policy. Notice of EPA policy was published
in the Federal Register, Notice No. FRL-3815-4, Volume 55, Number 146, July 30,
1990 and was entitled "EPA's Policy on Electronic Reporting." This policy
establishes a uniform EPA approach to electronic reporting by the regulated
community. In addition, the policy is intended to promote the adoption of electronic
reporting by EPA programs and to ensure that as they implement this technology,
they do so hi a manner that is both consistent across the Agency and compatible with
the current electronic reporting practices hi the regulated community.
Refer to the EPA EDI Implementation Guideline, Section 1 for Agency-wide EPA
EDI objectives. For copies of the EPA EDI Implementation Guideline contact the
EDI Team, U.S. EPA, Headquarters (2137), 401 M Street, S.W., Washington, D.C.,
20460 or call (202) 260-4825.
1.3 Responsible Entity
EPA Headquarters, regions, and NPDES delegated states are considered the
responsible entities under this Guideline.
1-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
1.4 Introduction to EDI
EDI is the transmission in ANSI ASC X12 syntax of information between computers
of independent organizations. The definition can be expanded further to include the
electronic transmission of business documents from the application program of one
computer to the application program of another computer within the framework of a
standard format. The key elements in this definition are computer-to-computer and
standard format. EDI reduces costs and errors associated with a paper document
environment. It replaces mail delivery and reentry of documents with an electronic
mailbox and delivery of business data directly to a Trading Partner's computer
application program.
1.5 How to Use the Implementation Guideline
This implementation guideline follows the ASC X12 recommended format specified in
the "ASC X12 Guideline for Electronic Data Interchange EDI Implementation
Reference Guidelines", approved February 1991, ASC X12 D/90-856. Chapters 1-
10 of this document contain information necessary for the Regions and NPDES states
and their trading partners to fulfill the requirements for implementing the exchange of
DMR data utilizing EDI. These sections include the EDI business background and
history, as well as EPA policy and logistic issues that should be addressed. The
appendices contain a checklist on how to get started with EDI DMR, and provide
conventions of the specific X12 transaction sets to satisfy the EDI information
requirements for transmittal of a DMR electronically.
1.6 References
Questions, comments, and suggestions regarding this DMR EDI Implementation
Guideline may be referred to:
Office of Enforcement and Compliance Assurance
U.S. Environmental Protection Agency
1200 Pennsylvania Avenue, N.W.
Washington , DC 20044
(202) 564-7277
Standards publications, guidelines and technical reports disseminate the technical and
logical concepts reflected in the X12 Standards. DISA (Data Interchange Standards
Association) publishes a catalog of the available standards. Pan I is a document titled
"An Introduction to Electronic Data Interchange". Part II is the catalog of the ASC
X12 Publications.
General or Technical questions about Electronic Data Interchange, ASC X12, ASC
X12 Standards and Updates, international standards, or DISA can be directed to:
Data Interchange Standards Association, Inc (DISA)
1-4
-------
DMREDI IMPLEMENTATION GUIDELINE
Technical Department
1800 Diagonal Road, Suite 200
Alexandria VA 22314-2852
Fax: (703) 548-5738
1-5
-------
-------
DMREDI IMPLEMENTATION GUIDELINE
SECTION 2 - BUSINESS ISSUES
2.1 Implementation Considerations
DMR implementation uses the following ASC X12 Transaction Sets referenced in the
EPA EDI Implementation Guideline:
863 Report of Test Results
997 Functional Acknowledgment
842 Nonconformance Report
These transaction sets are mapped in detail in the Appendices of this document.
2.2 Timing of Transactions
The EDI DMR must be received by the regions and NPDES delegated states in
accordance with each individual state's DMR submittal date. Trading partners can
transmit data at any time. EDI DMR transaction sets are submitted and retrieved at least
once daily. A transaction set 997 Functional Acknowledgment is generated to confirm
receipt of translatable data. The date and time stamp is considered to be the time at
which the corresponding 997 is generated. The 997 does not acknowledge the validity of
the data, only its receipt. The PCS data base updates twice weekly. If a trading partner
wants to ensure that a DMR transmission is included in a particular update cycle, the
transmission should be sent in a timely manner to assure that a transmission can be
successfully translated before the scheduled update.
If a 997 Functional Acknowledgment is not received, it is the responsibility of the
Trading Partner to assure that their transaction was received in translatable format. The
transmission of a transaction set 997 does not require an acknowledgment in return.
Each transmission should be retained in both translated and transmitted format by the
trading partners to assure a history of the data transmitted and received is maintained.
After a transaction set 997 Functional Acknowledgment is received, records of the
transmission can begin normal archiving procedures. Reference the DMR Terms and
Conditions Agreement (TCA) for more information.
PIN violations will be reported to the trading partner as an 842 Nonconformance Report
transaction as they are identified, usually daily. After the DMR is uploaded to PCS, the
PCS edit program generates error messages will also be transmitted to the trading partner
as an 842 Nonconformance Report. The 842 transaction will be sent after the data is first
processed by PCS Live Edit which normally occurs daily. Another 842 may be returned
as a result of the Live Update function of PCS which occurs twice a week.
2-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
2.3 Modes of Operation
The two modes of operation are production and test. Production is used when both
parties agree both systems are communicating the agreed upon data for the transaction
sets implemented. The test mode is used when implementing a new transaction, when
making a modification to implemented transactions, or when upgrading to a new
version/release. The Trading partners should be aware of when the test mode will be
used in order to provide assistance to each other. Identification of the mode of operation
is contained in the ISA (Interchange Control Header) Position ISA15, Data Element 114.
A "P" identifies production data and "T" identifies test data, (refer to Section 10.2 of this
document). Trading partner systems must have the provision to handle both production
and test transaction sets.
2.4 Security
The EDI process must include all steps necessary to ensure that the records are authentic,
are properly authorized, and are retained in a manner that will ensure the integrity of the
records. Audit trails must be maintained for accountability.
The EDI DMR uses a Personal Identification Number (PIN) that is issued, managed, and
validated by EPA Headquarters and Regions. The PIN identifies the person authorizing
the electronic submission of the DMR. It is equivalent to the signature of the principle
executive officer on the paper DMR.
Trading partners are responsible for keeping all PINs and Value Added Network (VAN)
log-on and local dial-up access numbers secure. If the trading partner suspects a security
breach, they must contact the appropriate regional or state NPDES staff member
immediately. EPA reserves the right to change Trading Partner PINs at any time. Please
see the EPA EDI Implementation Guideline, Section 2.4 for additional security
considerations.
2.5 Backup and Recovery Procedures
Backup and recovery procedures are necessary to provide:
• Retransmission capabilities; Translator re-run capabilities; Minimum 24-
to 48-hour immediate access backup; and Archive and recovery capabilities for
individual EDI transactions.
The backup and recovery procedures must be thoroughly documented to allow anyone
with the proper authority to access the system to retransmit data.
It will be up to each EDI trading partner to keep their own records and archives of EDI
transactions sent and received. Either partner must have the capability to retransmit an
EDI message.
2-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
The 997 Functional Acknowledgment transaction set can be used to provide a level of
automation in the backup and recovery area. If the EDI system expects to receive a
Functional Acknowledgment for every transaction it sends, the EDI message should be
available for retransmissions until a 997 corresponding to a specific EDI message is
received. Once the 997 Functional Acknowledgment is received, the original EDI
message can be archived regardless of the normal archive timing. The Agency requires
the use of the 997 Functional Acknowledgment. The 997 is used to confirm receipt of
the trading partner's 863 transmission and indicate acceptance or rejection of the
transaction set by the translator. A Functional Acknowledgment is not required for
receipt of Functional Acknowledgments; nor is it required for a trading partner's receipt
of a 842 Nonconformance Report.
Alternative plans must be developed to accommodate extreme problems such as the loss
of a data center, a local phone switch, or a catastrophic act of nature that prevents the
exchange of transmissions for an extended period of time. Alternatives may include use
of a different third party mailbox or direct asynchronous or bi-synchronous
transmissions.
2.6 Audit Considerations
Trading partners should maintain an adequate audit trail to ensure that they can
substantiate, when needed, information exchanged electronically. In an information
systems environment, an audit trail typically focusses on the transactions within the
system--the data processed, input/output devices accessed, and the date and time that
activities occurred. Documents in paper-form are usually available to validate
information input to or output from the automated information system. In the EDI
environment, paper-based documents, such as purchase orders, invoices, etc., no longer
exist. Therefore, an audit mechanism for the EDI environment must be more
comprehensive to substantiate the information transmitted and received electronically.
An EDI audit trail is a full set of records (maintained in either electronic or paper form)
documenting the data received, sent, retained, and stored. This set of records must
accurately reflect the actual events as they occurred.
Trading partners have multiple audit controls that they can take advantage of. They can
use error and exception reporting as an audit mechanism to follow-up and resolve errors
and exceptions. VAN reports can be used as an audit trail to substantiate EDI
transmissions. VANs typically offer several different types of reports, including:
• reports of all documents sent but not retrieved by trading partners,
• statistical reports on all documents sent and received, and
receiver and sender status reports that document the status of all documents
received and all documents sent.
A key audit control that trading partners should use is an electronic log of all their data
transmissions. This log should include the batch identifier, transaction set control
numbers, a date and time stamp, sender and receivers identifiers, and the status of the
2-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
transmission. This log is used to ensure the integrity of the data transmitted and received.
Trading partners can use the data in this log to conduct completeness checks to ensure
that all transactions are processed. The transaction set control numbers, e.g., the control
totals and unique sequence numbers in the trailer records, are used to verify that there are
no duplicates or omissions.
2-4
-------
DMR EDI IMPLEMENTATION GUIDELINE
SECTION 3 - LEGAL CONSIDERATIONS
3.1 General Introduction
The DMR EDI project was established to provide an option to facilities to allow
electronic submissions of DMR data to EPA. Typically, the DMR is submitted in paper
form. Regulations require use of the "form" and "signatures". The EPA has established
an electronic signature policy that would allow for the elimination of the paper form in
the future.
For more information on the legal considerations of using EDI with the EPA, refer to the
EPA EDI Implementation Guideline.
3.2 Record Keeping
The EDI DMR project will facilitate the submission of reporting data from regulated
facilities to their EPA regional or state NPDES program office.
Participating NPDES permittees should reevaluate their internal control systems in the
context of EDI to assure internal accountability for data maintenance, including audit
trail, transaction reconciliation, and backup capability. The DMR record retention
system should include the capability to maintain the following:
• Copies of all DMR transmissions must be retained for 5 years as with the paper
DMR.
• DMR transactions should be retained in both the original and translated format in
addition to normal application file retention.
• Transmission activity logs from the translator containing pertinent time
information should be retained.
• All application programs used in the EDI DMR system should be retained for the
life of the record retention.
• Records should be able to be retrieved in a form that can be admissible in any
judicial or other proceedings.
3.3 Authentication
The use of Personal Identification Numbers (PIN) are required on DMR EDI documents.
EPA headquarters or regions validate the PIN through internal EDI tables and through
VAN mailbox security. The PIN on the EDI DMR transmission is the equivalent of the
handwritten signature requirement on the paper DMR.
3.4 Trading Partner Agreement
Trading partner agreements (TPAs) are an important part of any EDI system. They serve
as the "interface specification" between trading partners and provide specific details of
the legal agreements that define how the electronic commerce is to be conducted. The
3-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
DMR pilot used a generic TPA for all trading partners involved. EPA has developed a
generic Terms and Conditions Agreement (TCA), a type of trading partner agreement,
which is published in the Federal Register. Interested NPDES permittees, in states where
EPA administers the NPDES program, may use EDI for DMR reporting by signing and
mailing the DMR TCA to EPA and complying with its terms.
3.5 Third-Party Agreement
The EDI DMR is submitted to EPA's mailbox. Currently, EPA's mailbox is located
on the AT&T Value Added Network (VAN). When searching for a VAN provider,
the Trading Partner (the NPDES permittee) and a telecommunications provider
should sign an agreement. The VAN of choice should be able to maintain all the
audit and security considerations outlined in the EPA EDI Implementation Guideline.
3.6 Laws, Rules, and Regulations
When implementing EDI, users and their counsel should consider whether any
special laws, rules or regulations apply to the users. Currently, there is no adequate
or comprehensive source of EDI law, but there are a few sources of laws, rules and
regulations that users may wish to consult. For more information, refer to the EPA
EDI Implementation Guideline.
3-2
-------
DMREDI IMPLEMENTATION GUIDELINE
SECTION 4 - ENVIRONMENTS
4.1 System Architecture
The trading partner initiates the EDI DMReport process by generating a DMR from
either its data base application or the EDI translation software. If the DMR is
generated in a data base application, the trading partner needs to run an application
interface program, which takes the data base output and reformats the data into an
ASC X12-formatted file and loads the data to the EDI translation software. The EDI
translation software translates the entered data or data base generated data and
translates the DMR information into the 863 Report of Test Results per the DMR EDI
convention. The 863 Report of Test Results is sent by the trading partner through the
VAN to the EPA mailbox.
The following outline organizes the steps that are needed to report DM R information
using EDI. This is then followed by a detailed discussion of the procedures involved
in each step.
a) DM R information is collected by the trading partner and retained until it is
ready for reporting to their EPA region or NPDES state. A copy of the paper
DMR form can be found in Figure 4.1.1.
b) Trading partner initiates exchange by creating a DMR in EDI format.
c) EDI DMR uploaded to VAN service by trading partner. (Trading partner
retains audit copy of complete message).
d) EDI DMR retrieved from VAN service by Enterprise Technology Services
Division (ETSD).
e) ETSD verifies the EDI message, translates it, and loads the information to the
DMR application system for final processing.
f) Audit copies of the message are retained by ETSD.
g) The ETSD application system generates a transaction set 997 and uploads the
message to the VAN service for delivery to the trading partner. An audit copy
is retained of the response message.
4-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
h) Where necessary, EPA and NPDES states make data updates to their
application system data base, and then requests re-transmission from the
trading partner. This can occur when the trading partner sends information
that either does not exist or match the reference information in the application
system.
A schematic of the Discharge Monitoring Report EDI flow is shown in Figure 4.1.2.
For comparison purposed, a diagram of the paper DMR flow appears in Figure 4.1.3.
Initial DMR Data Creation
The trading partner initiates the EDI DMR process by generating a DMR in EDI
format from either its own application system (from the data used in processing the
paper DMR forms) or by loading the same DMR data into a commercially available
piece of EDI translation software (the EDI translation software will translate the data
into the 863 Report of Test Results per the DMR EDI convention). The resulting 863
Report of Test Results is sent by the trading partner through the VAN to ETSD. The
VAN interaction is usually done via a local telephone dial-up access number utilizing
the communication module in either the EDI translation software or in access
software provided by the VAN service. Hardware requirements include an
internal/external modem on the computer system with access to a telephone line.
DMR Processing
Messages are retrieved from the mailbox at least once a day. The 863 transaction set
is translated by EDI translation software to their application format. As in a paper
process, the receiver time-stamps the receipt of the document. Receipt of the
document is defined as the time when the document is retrieved and successfully
translated from the VAN mailbox. The receiver acknowledges 863 transaction sets
by a 997 Functional Acknowledgment sent to the trading partner's mailbox. The data
is then checked for accuracy.
Error Reporting
Invalid PINs and other PCS error messages detected by the Live Edit are currently
reported to the EPA region or NPDES state. This information will be reported
directly to the trading partner by the transmission of an 842 Nonconformance Report
transaction.
The transaction will follow the reverse process of the DMR submission transaction,
The error messages are translated into the 842 transaction set format, sent to the EPA
VAN and distributed to the trading partner's VAN mailbox. The trading partner is
4-2
-------
DMREDI IMPLEMENTATION GUIDELINE
then notified to pickup and translate the message. The 842 convention document can
be found in Appendix D.
Data Corrections and Amendments
The trading partner can retransmit a 863 transaction set to replace a previously
submitted DMR. The trading partner modifies the 863 transaction previously
submitted and transmits the DMR as outlined above, but changing the transaction
type code (BTRO 1=05) to indicate a re-submit.
4.2 Application Integration
Application refers to the current functional processes which may or may not be
automated. To take full advantage of EDI, it should become part of the functional
processes and not an add-on. Planning for integration will reduce the impact of this
change and allow a smooth transition to an environment which maximizes your return
on investment. Total integration does not have to be achieved before starting EDI,
but it should be an established goal. Failure to achieve integration will result in the
attainment of some short-term benefits, but the real benefits which come from
increased automation will be unattainable.
4.3 Translation
Translation is the automated process of converting application data in a proprietary
format to X12 Standard formats for sending transactions. The process is reversed
when transactions are received in the X12 formats. The core translation program uses
table driven subroutines to generalize processing regardless of the actual application
being processed. The ASC XI2 standard provides a specific structure for the data. It
does not affect the program design or the program function. As a consequence, there
are many commercial software packages which provide core translation and other
related functions that are designed to support different EDI environments.
Some of the factors to be considered when deciding whether to make or to buy
translation software are the efforts required for programming, maintenance, testing,
incorporating upgrades to the X12 Standard, and the development of the
administrative programs necessary to satisfy EDI audits. The availability of
relatively inexpensive proven commercial software packages supported by a growing
industry should make development unnecessary. EDI software should be managed as
system software rather than application software.
4-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
Figure 4.1.1 Discharge Monitoring Report
4-4
-------
DMREDI IMPLEMENTATION GUIDELINE
Figure 4.1.2 EDI DMR Data Flow
DATA GATHERED
FOR DMR
SUBMISSION
TRANSLATE TO X12
DATA FORMAT
X12 TRANSMITTED
TO VAN
REGION
RETRIEVES X12
FROM VAN
/ COPY OF
_J TRANSMISSION/
~~1 STORED BY
\ REGION
DATA SET IS
CREATED ON EPA
MAINFRAME
JOBTRAC READS |<
THIS RLE AND
BEGINS
PROCESSING
Denotes the application interface
(COMMENTS
AND RELATED
INFORMATION
f
\
YM
+
COMMENTS ARE PARSED OFF TO PUBLIC
AREA FOR RETRIEVAL BY REGION.
SORTED BY PERMIT NUMBER, REPORTINQ
PERIOD. OUTFALL, AND PARAMETER.
DATA IS THEN CONVERTED T0 1440 BYTE
RECORDS
/ CONVERTED
_J DATA STORED
^ FOR AUDIT
\ PURPOSES
/
\
ASSIGNS
INTERNALLY
GENERATED PCS
DATA VALUES
(REGION NUMBER,
STATE, USER RIGHTS
TO PCS)
DATA FLOW OF DMR EDI PILOT PROJECT, PAGE 1 OF 2
4-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
Figure 4.1.2 EDI DMR Data Flow (Continued)
PAPER NOTIFICATION WILL OCCUR
UNTIL A TRANSACTION CONVENTION IS
DEVELOPED.
Y
Bad Data
Transactions
(Future)
DATA FLOW OF DMR EDI PILOT PROJECT, PAGE 2 OF 2
4-6
-------
DMR EDI IMPLEMENTATION GUIDELINE
Figure 4.1.3 Paper DMR Data Flow
DUMMY EDIT PROVIDES
A CHECK FOR FATAL
DMR ERRORS AND
CONVERTS RECORDS
TO 14.4 BYTE FORMAT
DATA FLOW OF PAPER DMR PROCESS
4-7
-------
-------
DMREDI IMPLEMENTATION GUIDELINE
1
SECTION 5 - MAINTENANCE
5.1 Maintaining Guidelines
The U.S. EPA in conjunction with regions and NPt)ES states is responsible for
maintaining the DMR EDI Implementation Guideline. Regions and NPDES states
notify trading partners of changes affecting existing EDI DMR document conventions
or document transfer.
5.2 Maintaining ASC X12 Standards
ASC X12 has a standard procedure for developing new transaction sets and
maintaining existing sets. Refer questions to the EPA EDI coordinator of the
program office responsible for the project. Should additional information be
required, the question will be referred to:
Data Interchange Standards Association, Inc (DISA)
Technical Department
1800 Diagonal Road, Suite 200
Alexandria VA 22314-2852
Phone: (703) 548-7005
Fax: (703) 548-5738
5.3 Version/Release
The version/release for the transaction sets used are found on the first page of each
Transaction Set appendix.
5-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
THIS PAGE LEFT INTENTIONALLY BLANK
5-2
-------
DMREDI IMPLEMENTATION GTJIDELIISJ;
SECTION 6 - COMMUNICATIONS
6.1 General Introduction
The transport of information in an EDI environment may be done physically or by
telecommunications. Physical means include the use of magnetic tape or courier
service. Data communication means the use of a public or private
telecommunications.
Each exchange method should be analyzed to determine whether or not the approach
meets the trading partners' communication needs. No matter which approach is
selected, a contingency plan should be formulated to address the possible event of a
communication failure.
Issues to consider are procedures to address system failures, transmission error
recovery including establishing the maximum number of retransmission attempts,
security, network response time, and error reporting.
Section 6 of the EPA EDI Implementation Guideline provides an overview of the
communication options available to trading partners planning to implement EDI.
6.2 Protocols
Protocols are a set of conventions between communicating devices. Simple protocols
define only hardware configuration, more complex protocols define timings, data
formats, error detection, and correction techniques. For more information on
protocols, see the EPA EDI Implementation Guideline.
6.3 Point-to-Point
Point-to-point or direct connect service is communication between two trading
partners. Point-to-point may employ dedicated circuits, dial circuits, or a
combination of the two. An EDI user that elects direct communication with trading
partners must have the necessary in-house staff capable of managing the network and
must address a number of issues with each individual trading partner.
An EDI user electing to implement direct connections must be aware that not all
trading partners will have similar capabilities and therefore the trading partner may
by necessity elect to use a third party service. For more information, refer to the
EPA EDI Implementation Guideline.
6-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
6.4 Third-Party Services
The EDI DMR is submitted to the EPA's mailbox. Currently, the EPA's mailbox is
located on the AT&T VAN. Refer to Section 3.5 of this document, and Section 6.4
of the EPA EDI Implementation Guideline, for more information regarding Third-
Party Services.
6.5 Network Interconnects
Network interconnects are a viable means of exchanging data when each trading
partner wishes to use their preferred VAN. It is the responsibility of each partner to
research whether their preferred VAN has the full complement of desired
interconnect capabilities with the others. This includes the ability to provide a full
audit trail for tracking transmissions.
6-2
-------
DMREDI IMPLEMENTATION GUIDELINE
SECTION 7 - MISCELLANEOUS
7.1 Industry Business Models
The following is an overview of the transaction sets used in the DMR process.
These documents mirror the information contained in the paper DMR documents.
It should be noted that the electronic documents DO NOT replace any legally
required paper equivalents. A Federal Register Notice will be published
announcing that EDI DMR will be accepted in lieu of the paper DMR.
Although this document presents the anticipated practice and events for the
exchange of documents pertaining to the DMR, this document can only serve as a
guide. Any discrepancy or inconsistency found should be clarified with the region
or NPDES state for exact procedures.
In commercial use of EDI trading partners do not restrict themselves to a
particular exchange model, and so may extend conventions to suit their
circumstance. This document however outlines the details required for meeting
federally regulated reporting and therefore a trading partner must follow the
region or NPDES state instructions to ensure compliance.
Transaction Sets
The following ASC X12 Transaction Sets are used for submitting the DMR. The
detailed mapping is contained in individual appendices for each transaction set.
863 Report of Test Results
The PCS receives pollutant discharge information from NPDES trading
partner via this transaction set. The information is utilized to track permit,
compliance, and enforcement status. See Appendix C for the detailed
mapping.
997 Functional Acknowledgment.
This transaction set communicates to the trading partner that their
transmission was received and the receiving party was able to translate the
transactions. The 997 does not guarantee the validity of the data submitted in
a transmission, it only acknowledges receipt of the transmission. Should a
transmission be untranslatable, the 997 will identify the problem and
communicate the errors to the transmitting party.
The return of 997, indicating a successful translation, also serves as the
"postmark date" for the submission of an EDI DMR. See Appendix B for the
detailed mapping.
7-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
842 Nonconformaace Report
The PCS uses this transaction set to report back to the trading partner any PIN
or errors detected during the PCS Live Edit processing. See Appendix D for
the detailed mapping.
7.2 Related Business Topics
Not currently used.
7.3 EDI Vendor References
EDI is offered as a standard interface so trading partners, software manufacturers and
value-added-networks can interact without concern for proprietary features. Trading
partners must acquire the services of an X12 translator and communications software.
For the purpose of the DMR EDI Project, trading partners shall acquire the EDI
software that best meets their needs for interfacing with the NPDES program offices
and with other trading partners they may have. ,
EPA does not recommend or endorse any vendors translation or communication
software. Listings of EDI software and service vendors can be obtained through ASC
X12, EDI periodicals and trade journals. Several buyer's guides have been published
that identify and provide details on commercially available EDI software packages.
Refer to Section 7.3 of the EPA EDI Implementation Guideline for more information
regarding vendors products.
7-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
SECTION 8 - GLOSSARY OF TERMS
ANSI, American National Standards Institute.
ANSI Standard, A document published by ANSI that has been approved through the
consensus process of public announcement and review. ANSI Standards are developed by
committees accredited by ANSI (see ASC) and must be revisited by the developing
committee within five years for updating.
Area, Transaction Set, Identifies a defined area within a transaction set containing
segments. The areas may be referred to as Table 1, Table 2, Table 3 or Header, Detail and
Summary.
ASC X12, Accredited Standards Committee XI2. Its purpose is to develop uniform
standards for electronic interchange of business documents. Membership is open to virtually
all organizations and individual with a material interest in the standards.
Authentication, A process whereby the receiver of a digital message can be confident of the
identity of the sender and the integrity of the message.
Compliance Checking, A checking process that is used to ensure that a transmission
complies with ASC X12 syntax rules.
Component Data Element, A data element used as a sub-element in a Composite Data
Structure.
Component Data Element Separator, Sometimes referred to as a sub-element separator.
A unique character that precedes each Component Data Element in a Composite Data
Structure. It is specified by the sender in the Interchange Control Header (ISA). The
separator has a range of influence from this header to the next Interchange Control Trailer
(IEA) segment. The sub-element must be different from the data element separator and
segment terminator and once specified in the ISA segment must not appear in a data element
value with the exception of its possible appearance in Data Element #785, Binary Data.
Within diagrams, the colon (:) is used to represent the separator character. Within diagrams,
the colon (:) is used to represent the separator character.
Composite Data Elements, One or more component data elements delimited by sub-
element separators.
Composite Data Structure, Structure that consists of two or more logically related
component data elements in a defined sequence and delimited by a Component Element
Separator.
Condition Designator, An indicator assigned to each data element in a segment and defines
how it is to be used in the segment. Data elements may be designated as Mandatory (M),
8-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
Optional (O) or Relational (X). Refer to the ASC X12 Standards, X Segment Directory,
Introduction.
Control Segment, A control segment has the same structure as a data segment but is used
for transferring control information for grouping data segments. Control Segments are Loop
Control Segments (L/LE), Transaction Set Control Segments (ST/SE), and Functional Group
Control Segments (GS/GE), defined in XI2.6 and Interchange Control Segments
(ISA/ffiA,TAl) defined in X12.5.
Control Validation, Confirmation that information within the control segments is correct.
Conventions, Common practices and/or interpretations of the use of the ASC XI2
standards, complying with the standards, as agreed upon by two or more trading partners.
Conventions define what is included in a specific implementation of an ASC XI2 standard.
Data Element, The smallest unit of information in the XI2. Data elements are defined in
the Data Element Dictionary, X12.3. Each data element is identified by a reference number.
Data Element Dictionary, Source document for Data Element specifications. Its official
name is X12.3 Data Element Dictionary. The dictionary specifies the name, description, and
minimum/maximum length for each data element. For ID-type or code type data elements,
the dictionary lists all code values and their definitions or indicates in an appendix where the
valid code list can be obtained.
Data Element Length, Number of character positions available to represent the data
element value. A data element may be of variable length with range from minimum to
maximum, or it may be of fixed length in which the minimum is equal to the maximum.
Data Element Reference Number, Reference number assigned to each data element as a
unique identifier. Numbers prefixed with a "C" or an "S" indicate a Composite Data
Element. Lack of a prefix indicates indicate a Simple Data Element.
Data Element Separator, A unique character preceding each data element that is used to
delimit data elements within a segment. It is specified by the sender in the Interchange
Control Header (ISA). The separator has a range of influence from this header to the next
Interchange Control Trailer (TEA) segment. The data element separator must be different
from the component or sub-element data separator and segment terminator and once
specified in the ISA segment must not appear in a data element value with the exception of
its possible appearance in Data Element #785, Binary Data. Within diagrams, the asterisk (*)
is used to represent the separator character. See "Delimiters".
Data Element Type, An identification which describes the format of the data in the
element. A data element may be one of eight types: Numeric (N), Decimal (R),
Identifier (ID), String (AN), Date pT), Time (TM), Binary (B), or Fixed Length String (FS).
Refer to X12.3 Data Element Dictionary, Introduction.
8-2
-------
DMREDI IMPLEMENTATION GUIDELINE
Delimiters, Delimiters are bit configurations that are used as data element separators,
component or sub-element separators and segment terminators. The design of XI2 is based
on the concept of variable lengths. Delimiters are necessary to identify the start of data
elements and sub-elements and to identify the end of segments. They are specified by the
sender in the Interchange Control Header (ISA). They have a range of influence from this
header to the next Interchange Control Trailer (IEA) segment. Delimiters are agreed upon by
the Trading partners. The instance of the terminator must be different from the instance of
the data element separator which must be different from the component (sub-element)
element separator. Once specified in the ISA segment they must not appear in a data element
value with the exception of its possible appearance in Data Element #785, Binary Data.
DISA, Data Interchange Standards Association. A not-for-profit organization which serves
as the Secretariat for ASC X12 and the Pan American EDIFACT Board(PAEB). It is
accredited by ANSI to administer the U.S. Technical Advisory Group on matters pertaining
to EDIFACT syntax before the International Organization for Standardization's(ISO's)
Technical Committee 154.
Direct Transmission, The exchange of data from the computer of the sending party directly
to the computer of the receiving party.
DMR, The Discharge Monitoring Report is a form used by National Pollution Discharge
Elimination System (NPDES) permitted facilities to report discharges into navigable
waterways.
Draft Standard for Trial Use (DSTU), A document approved by the full ASC XI2
committee following membership consensus and subsequent resolution of negative votes and
approved for publication by the Procedures Review Board. DSTU's must be submitted to
ANSI periodically for approval as National Standards. See ANSI Standard.
EDI Translation, The conversion of application data to and from the XI2 standard format.
EDI Translator, Computer software used to perform the conversion of application data to
and from the XI2 standard format.
Electronic Data Interchange (EDI), The computer application to computer application
exchange of business information in a standard format. An EDI transmission is a highly
structured message intended for automated processing by a computer. All references to EDI
under U.S. EPA programs refers to the utilization of ASC XI2 standards.
Electronic Envelope, Electronic package that contains a set(s) of documents sent from one
sender to one receiver. See Interchange Control Segments.
Electronic Mailbox, A repository where an EDI transmission is stored for pickup or
delivery. Mail boxes may be within a third-party service provider's system or in an
individual trading partner's domain.
8-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
Encryption, A process of transforming clear text (data in its original, uncoded form) into
ciphertext (encrypted output of a cryptographic algorithm) for security or privacy.
EPA, The Environmental Protection Agency. Also called USEPA for United States
Environmental Protection Agency. Established in 1970 by Presidential executive order, it
brings together parts of various government agencies involved with the control of pollution.
Note that some State environmental authorities may be called EPA also, as in Illinois EPA.
FEPS PUB 161, Federal Information Processing Standard, Publication 161.
Functional Acknowledgment, A transaction set (997) transmitted by the receiver of an EDI
transmission to the sender, indicating receipt and syntactical acceptability of data transmitted
according to the ASC XI2 standards. The functional acknowledgment allows the receiving
party to report back to the sending party problems encountered by the syntax analyzer as the
data is interpreted. It is not intended to serve as an acknowledgment of data content.
Functional Group, A group of one or more transaction sets enclosed by a Functional Group
Header (GS) segment and a Functional Group Trailer (GE) segment. Each instance of a
functional group applies to a specific business function defined by the specific application to
which it applies.
Functional Group Envelope, The envelope starting with a GS (Functional Group Header)
Element and terminated with a GE (Functional Group Trailer) Element.
Guideline, A document prepared by an EDI implementor that defines the use of the
ASC X12 standards in the implementor's environment.
Implementation Guideline, A document prepared by an industry group, association,
institute, government body or individual trading partner that defines how the ASC X12
standards are used by that industry.
Industry Conventions, A document prepared by an industry group, association, institute,
etc. that defines how the ASC X12 standards are used by that industry.
Interchange, A transfer of data between trading partners.
Interchange Control Envelope, The outer envelope that holds multiple functional group
envelopes in an ASC X12 transmission.
Interchange Control Segments, Segments that identify the boundaries of the ASC XI2
formats in a transmission. Interchange Control Header (ISA) and Interchange Control Trailer
(IEA) segments identify a unique interchange being sent from one sender to one receiver.
Interchange Control Structure, The Interchange Control Header (ISA) and Interchange
Control Trailer (DBA) segments envelope one or more functional groups or interchange
related control segments and perform the following functions: 1) defines the data element
8-4
-------
DMR EDI IMPLEMENTATION GUIDELINE
separators and the data segment terminators, 2) identifies the sender and receiver, 3) provides
Control information for the interchange, and 4) allows for authorization and security
information. (X12.5).
Level, A term used to identify hierarchical positions in an ASC X12 design. The levels used
from highest to lowest are Communications, EDI Interchange, Functional Group, Transaction
Set, Heading Area, Summary Area and Detail Area. Reference ASC X12 publication
DSTU X12.59 Implementation of EDI Structures - Semantic Impact.
Loop, A group of segments related only by design of the transaction set. Use of any
segment within a loop requires the use of the first or parent segment of the loop.
Mandatory (M), A data element/segment requirement designator that indicates that the
presence of a specified data element is required.
Mapping, The process of identifying the relationship between the data elements in the
standard transaction set and the data elements in the application..
Max Use, The maximum number of times a segment can be used at the location in a
transaction set.
Message, Entire data stream including the outer envelope.
Message Authentication, A mechanism that allows the receiver of an electronic
transmission to verify the sender of the integrity of the content of the transmission through
the use of an electronic "key" or algorithm, which is shared by the trading partners.
National Pollution Discharge Elimination System (NPDES), This program is run by
designated State Agencies or U.S. EPA Regions to monitor water pollution discharges. This
data, once collected, is maintained in the Permit Compliance System (PCS) of the U.S. EPA.
OPPE, Office of Policy, Planning, and Evaluation is an organization within the U.S. EPA.
Optional (O), A data element/segment requirement designator that indicates that the
presence of a specified data element/segment is at the option of the sending party, which can
be based on the mutual agreement of the interchange parties.
Permit Compliance System (PCS), This program is run by the U.S. EPA in support of
the EPA Regions. Its functions include maintaining an inventory of NPDES permittees;
providing data for Congress, State legislatures, and the general public; supporting
effective NPDES program implementation; promoting sound planning, evaluation, and
decision-making; and, facilitating the use of NPDES-reported data.
Personal Identification Number (PIN), A unique number assigned to a user for
identification purposes.
8-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
Qualifier, A data element that identifies or defines a related element. Qualifier elements are
ID Type Elements. The qualifier is a code taken from a list of approved codes.
Relational (X), See Segment Directory.
Repeating Segment, A segment that may be used more than once at a given location in a
transaction set. See Max Use.
Security, System screening that denies access to unauthorized users and protects data from
unauthorized uses.
Segment, Variable length set of logically related data elements in a defined sequence, a
unique segment identifier (which is not a data element), one or more data elements, each
preceded by a data element separator, and a segment terminator. Refer to X Segment
Directory.
Segment Directory (X), The standard that provides the definitions and specifications of the
segments used in the construction of transaction sets developed by ASC X12. The directory
lists each segment by name, purpose, identifier, the contained data elements in the specified
order, and the requirement designator for each data element.
Segment Identifier, A unique identifier for a segment composed of a combination of two or
three letters or digits. The segment identifier occupies the first character positions of the
segment. The segment identifier is not a data element.
Segment Terminator, A unique character appearing at the end of a segment to indicate the
termination of the segment. It is specified by the sender in the Interchange Control Header
(ISA). The segment terminator has a range of influence from this header to the next
Interchange Control Trailer (IEA) segment. The segment terminator must be different from
the data element and sub-element separators and once specified in the ISA segment must not
appear in a data element value with the exception of its possible appearance in Data Element
#785, Binary Data. Within diagrams, the notation "N/L" is used to represent the segment
terminator.
Standards, Standards are the technical documentation approved by ASC X12, including
Transaction Sets, Segments, Data Elements, Codes and Interchange Control Structures.
Standards provide the structure for ASC XI2.
Sub Element Separator, Sometimes referred to as a Component Data Element Separator.
A unique character that precedes each Component Data Element in a Composite Data
Structure. It is specified by the sender in the Interchange Control Header (ISA). The
separator has a range of influence from this header to the next Interchange Control Trailer
(IEA) segment. The sub-element must be different from the data element separator and
segment terminator and once specified in the ISA segment must not appear in a data element
value with the exception of its possible appearance in Data Element #785, Binary Data.
Within diagrams, the colon (:) is used to represent the separator character.
8-6
-------
DMREDI IMPLEMENTATION GUIDELINE
Syntax, The grammar or rules that define the structure of the EDI standards (i.e., the use of
loops, qualifier, etc.). Syntax rules are published in ANSI X12.6.
Trading Partner Agreement (TPA), Contractual agreements between tow entities that
contemplate trading electronically.
Trading Partner, The sending and/or receiving party involved in the exchange of electronic
data interchange transmissions.
Transaction Set, The transaction set unambiguously defines, in the standard syntax,
information of business or strategic significance and consists of a transaction set header
segment, one or more data segments in a specified order, and a transaction set trailer
segment.
Transaction Set ID, An identifier that uniquely identifies the transaction set. This identifier
is the first data element of the transaction set header segment.
Translation, The act of accepting documents in other than X12 standard format and
converting them to the XI2 standard format.
Transmission Control, Defines how information is transmitted across communications
lines and includes routing and recommendations.
VAN, Value Added Network. Third-party service organizations.
Version/Release, Identifies the publication of the standard being used for the generation or
the interpretation of data in the X12 standard format. May be found in the Functional Group
Header Segment (GS) and in the Interchange Control Header Segment (ISA). (E.g., Version
003040 means Version 3 Released.) See Control Segment.
X12, The ANSI committee responsible for the development and maintenance of standards
for Electronic Data Interchange (EDI).
X12.5, Interchange Control Structures. This standard defines the control structures, the
interchange envelope of a header (ISA) and trailer (TEA) for the electronic interchange
through a data transmission, and it provides a structure to acknowledge the receipt and
processing of this envelope.
X12.6, Application Control Structure. This standard defines the structure of business
transactions for computer-to-computer interchange.
8-7
-------
-------
DMR EDI IMPLEMENTATION GUIDELINE
SECTION 9 - FORMS AND DOCUMENTS
9.1 ASC X12 Transactions
The DMR EDI Project complies with the ASC X12 standards for Electronic Data
Interchange. The EPA DMR process supports the following ASC X12 standards at
this time:
ISA/TEA, GS/GE, ST/SE Header and Trailer Formats;
863 Report of Test Results (XI 2.41);
997 Functional Acknowledgment (X12.20); and
842 Nonconformance Report.
9.1.1 Header/Trailer Format
The EPA has defined the elements to be used in the Interchange Control
Header/Trailer (ISA/IEA), Functional Group Control Header/Trailer (GS/GE), and
the Transaction Set Header/Trailer (ST/SE) for all transmissions to and from the State
NPDES Program Office.
The interchange header and trailer segments envelop one or more functional groups
or interchange related control segments and perform the following functions:
• Define the data element separators and data segment terminators;
• Identify the sender and receiver;
• Provide control information for the interchange; and
• Allow for authorization and security information.
9.1.2 863 Report of Test Results Transaction Set
The 863 Report of Test Results transaction set is used to reproduce the Discharge
Monitoring Report. The transaction set has two functions: the first captures the
information as it appears in hard copy, and the second generates the flat file for the
Region or NPDES State.
The 863 Report of Test Results received by the Region or NPDES State is
acknowledged with a 997 Functional Acknowledgment. More information on the
863 is located in Appendix C.
9-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
9.1.3 997 Functional Acknowledgment Form
A 997 Functional Acknowledgment is sent by the Region or NPDES State to the
Trading Partner in response to the receipt of an 863 Report of Test Results. The 997
does not guarantee the validity of the data sent in the 863 Report of Test Results.
More information on the 997 is found in Appendix B.
9.1.4 842 Nonconformance Report Transaction Set
An 842 Nonconformance Report is sent by PCS to the Trading Partner to report PIN
or PCS errors that have been identified. A Functional Acknowledgement is NOT
required in response to the 842. More information on the 842 is found in Appendix
D.
9.2 ASC X12 Documents
The following ASC X12 documents should be referenced for additional information
standard format and implementation issues.
ASC XI2 Draft Standards
Version 003 Release 050
Document Number ASC X12S/90-856
Available through:
Data Interchange Standards Association, Inc. (DIS A)
1800 Diagonal Road, Suite 200
Alexandria, VA 22314-2852
Phone: (703)548-7005
FAX: (703) 548-5738
or:
EDI Support Services, Inc.
P.O. Box 203
Chardon, OH 44024-0203
Phone: (800)334-4912
9-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
9.3 Sample of DMR (EPA Form 8700-02 (Rev. 9-88)
9-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
9.4 PCS Code Tables
PCS Code Tables used in this implementation are found in the PCS Codes and
Descriptions maintained by the U.S. EPA. The tables used are:
Table 050 Frequency of Analysis Codes
Table 080 Monitor Location Codes
Table 150 Sample Type Codes
Table 160 Parameter Type Code
Table 180 Measure Unit Codes
Table 490 No Discharge Indicator Codes
9.5 Mapping of DMR Data Items to ASC X12 Segments
Table 1 represents the listing of field information in the order that it appears in the
EDI DMR. Presented in the table is the associated ASC X12 Segment and Looping
Hierarchy selected for describing the data in the ASC X12 format.
TABLE 1
EDI
Segment
GS01
GS02
GS03
GS04
GS05
GS06
GS07
GS08
ST01
ST02
BTR01
BTR02
BTR03
BTR04
EDI
Loop
Table
or Note
TRXTYPE
DMR for
NPDES
Column
or Note
TR'
Not Used
Not Used
Not Used
Not Used
Not Used
'X'
'003041'
'863'
Calculated
00 = Original
05 = Replace
DMR creation
date
DMR creation
time
DJ = Discharge
Monitoring
Report
Data Entity/Field Name
Functional ID
Sender ID
Receiver ID
Group Date
Group Time
Group Control Number
Standard Body
Version Release
Segment ID
TSCN
Document edit code
Date
Time
Report type code
Notes
05 replaces
entire DMR.
9-4
-------
DMREDI IMPLEMENTATION GUIDELINE
I
EDI
Segment
BTR05
BTR06
NTE01
NTE02
DTM01
DTM02
DTM03
DTM04
DTM05
DTM06
DTM07
N101
N102
N103
N104
EDI
Loop
N1
N1
N1
N1
Table
or Note
BATCHID
MVDT
YYMMDD
HHMMSS
Plant
Column
or Note
NCD = Non-
conformance
Specification
Text
090 = Report
begin
091 = Report
end
458 =
Certification
Not Used
Not Used
Not Used
Not Used
Not Used
8D = Permit
holder
ZD = Recipient
name
Free form
name of entity
94 = Code
assigned by the
organization
that is the
ultimate
destination of
the transaction
set.
Data Entity/Field Name
Reference #
Reference #
Note/Special Instruction
Free Form Message
Date/time qualifier
Date
Time
Time code
Century
Date/Time period format
qualifier
Date/Time Period
Entity ID code
Name
ID code qualifier
ID code
Notes
Report reference
# created by
sender.
Reference # of
transaction
replaced if
BTR01=05.
Carries permit
level notes or
comments
Monitoring period
begin date.
Monitoring period
end date.
Signature date
Used when
N101=ZDto
specify a mail
code.
Code from
Region/State
Route List
whenN101=ZD
9-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
EDI
Segment
N105
N106
REF01
REF02
REF03
PER01
PER02
PER03
PER04
PER05
PER06
REF01
REF02
REF03
L1N01
LIN02
LINOS
LIN04
LINOS
EDI
Loop
N1
N1
N1
N1
N1
N1/PER
N1/PER
N1/PER
N1/PER
N1/PER
N1/PER
N1/PER/
REF
N1/PER/
REF
N1/PER/
REF
LIN
LIN
LIN
LIN
LIN
Table
or Note
NPID
Certifier / Prin-
ciple Executive
Officer or other
Authorized
Agent
VDSC+VDRD
Column
or Note
Not Used
Not Used
PN = Permit #
NPDES permit
number of
permit holder
Not Used
AA =
Authorized
Representative
CE = Certifier
Text
TE =
Telephone
Number
Complete
Telephone #
Not Used
Not Used
4A=PIN
The appropriate
PIN
Not Used
P5 = Material
discharge
number.
Discharge #
Not Used
Not Used
Data Entity/Field Name
Entity relationship code
Entity identifier code
Reference number qualifier
Reference number
Description
Contact function code
Name
Communication # qualifier
Communication #
Communication # qualifier
Communication #
Reference number qualifier
Reference number
Description
Assigned ID
Product/Service ID qualifier
Product/Service ID
Product/Service ID qualifier
Product /Service ID
Notes
See code list of
DE #366 for an
appropriate value
to describe the
person identified
in N1 (for title of
Principle
Executive Officer)
Include country
and/or area code
if applicable.
Sequential
number that
identifies iteration
of the loop.
9-6
-------
DMREDI IMPLEMENTATION GUIDELINE
1
EDI
Segment
NTE01
NTE02
PID01
PID02
PID03
PID04
PID05
PID06
PID07
PID08
MEA01
MEA02
MEA03
EDI
Loop
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN
Table
or Note
NODI
VMLO
VPRM
RFRQ
REXC
Column
or Note
NCD = Non-
conformance
Specification
Text
S = Structured
from industry
code list
08 = Product
(for PCS
parameter
code)
12 = Type
and/or process
(for PCS
sample type
code)
28 = Test
sample
frequency (for
PCS frequency
of analysis
code)
29 = Test
sample location
(for PCS
monitoring
location code)
88 = Flow (for
PCS no
discharge
indicator code)
EP = U.S. EPA
The appropriate
PCS code
value.
Not Used
Not Used
PCS + the code
table number
Not Used
CT = Counts
Not Used
Number of
excursions
value
Data Entity/Field Name
Note/Special Instruction
Free Form Message
Item description type
Product/Process character
code
Agency qualifier code
Product description code
Description
Layer/position code
Source subqualifier
Yes/No response code
Measurement reference ID
code
Measurement qualifier
Measurement value
Notes
PID Segment is
optional, for Pipe
Level No
Discharges.
At least one of
"08" or "88" is
required for each
iteration of the
LIN loop.
9-7
-------
DMR EDI IMPLEMENTATION GUIDELINE
EDI
Segment
MEA04
MEA05
MEA06
MEA07
MEA08
MEA09
MEAIO
CID01
CID02
C1D03
CID04
CID05
CID06
CID07
MEA01
MEA02
MEA03
MEA04
MEA05
MEA06
EDI
Loop
LIN
LIN
LIN
LIN
LIN
LIN
LIN
LIN/CID
LIN/CID
LIN/CID
LIN/CID
LIN/CID
LIN/CID
LIN/CID
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
Table
or Note
PCS Code
Table
Value
MQAV
MCAV
MCMN
MCMX
MQMX
Column
or Note
1N = Count
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
TR = Length
Type: Random
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
TR = Test
results
CON =
Concentration
QUR =
Reportable
quantity
The average
value is
reported here.
EA = Each
Concentration
minimum value
Quantity or
concentration
maximum value
Data Entity/Field Name
Composite unit of measure
Range minimum
Range maximum
Measurement significance
code
Measurement attribute code
Surface/Layer position code
Measurement method
or
device
Measurement Qualifier
Product /Process
characteristic code
Agency qualifier code
Product description code
Description
Source subqualifier
Yes/No condition or response
code
Measurement reference ID
code
Measurement qualifier
Measurement value
Composite unit of measure
Range minimum
Range maximum
Notes
This segment
used to start the
LIN/CID Loop.
One or the other
is required.
Used as a
dummy unit. PCS
unit code is in
LM/LQ loop
This element will
be empty for
quantity
measurements.
9-8
-------
DMREDI IMPLEMENTATION GUIDELINE
EDI
Segment
MEA07
MEA08
MEA09
MEAIO
LM01
EDI
Loop
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA
LIN/CID/
MEA/LM
Table
or Note
Column
or Note
03 =
Approximately
06 = Greater
than
07 = Less than
23= Predicted
Not Used
Not Used
EP - U.S. EPA
Data Entity/Field Name
Measurement significance
code
Measurement attribute code
Layer/position code
Measurement method
Agency qualifier code
Notes
03 is used only
as a place holder
for 'Estimated1.
23 is also used
as a place holder
for Too
numerous to
count1. Data
maintenance will
be requested for
both of these
codes.
lfMEA07 = 23,
then either
MEA03, MEA05,
or MEA06 must =
99999.
This loop
specifies PCS'
unit of measure.
9-9
-------
DMR EDI IMPLEMENTATION GUIDELINE
EDI
Segment
LM02
LQ01
LQ02
SE
EDI
Loop
LIN/CID/
MEA/LM
LIN/CID/
MEA/LM
LIN/CID/
MEA/LM
Table
or Note
RUNT
RCUN
Column
or Note
PCS + the code
table number
Not Used
PCS unit of
measure code
Data Entity/Field Name
Source subqualifier
Code list qualifier code
Industry code
Transaction set trailer
Notes
Must be same
value as ST02.
9-10
-------
DMREDI IMPLEMENTATION GUIDELINE
SECTION 10 - AGENCY CONVENTIONS,
INTERCHANGE CONTROL & TRANSACTION SETS
10.1 Introduction
Section 10 contains the descriptions of the information used in the Interchange
Header (ISA), Interchange Trailer (IEA), Group Start (GS), Group End (GE), and the
control segments.
To help understand how the standards work, it is useful to begin by defining some
terminology and explaining some of the components that make electronic
communications possible. It is important to note that in the transaction set
implementation guidelines all text shown in italics is an EPA Convention. Non-
italicized text contain definitions and comments directly from the X12 standards.
A "transaction set" is the term used in business data interchange to describe the
electronic transmission of a single document (purchase order, Discharge Monitoring
Report, shipping notice, etc.) between one organization's computer and the computer
of the other trading partner. The data included in a transaction set conveys the same
information as a conventional printed document.
A transaction set generally but not always, consists of three areas - Header or Table
1, Detail or Table 2, and a Summary or Table 3. The Header Area contains
information that is of an administrative nature and pertains to the entire document
(document dates, identities, names of contacts, etc.). The Detail Area is used to
convey the actual business transaction such as quantities, prices, items. Data in the
Detail Area overrides equivalent Header Area data (i.e. if a contact is specified in the
Header and another contact is specified with a single item, the second contact takes
priority). The Summary Area contains control information and may contain other
data that relates to the entire transaction.
Transaction sets are a collection of a series of segments. A segment is a group of data
used to convey a logical grouping of data. The data within a segment is contained
within data elements. A segment is the smallest discrete piece of data in the ASC
X12 design.
Please note that in the design of Composite Data Elements, sub-elements are still
referred to as elements.
EDI transmissions are created from information extracted from internal information
systems, translated into ASC XI2 format and punctuated with control characters.
Quantity, unit of measure, unit price, catalogue number are typical purchase order or
invoice information. In an invoice transaction the information becomes a segment if
five data elements grouped in a specific sequence as follows:
10-1
-------
DMR EDI IMPLEMENTATION GUIDELINE
ITl**Quantity*Unit of Measure Code*Unit Price** Product
Service Qualifier*Product/Service Identification N/L
The AS C XI2 format requires each element be separated by an element separator and
the last element be followed by a segment terminator. Graphic representations of the
control characters usually use the asterisk as a element separator, N/L as the segment
terminator and a colonQ as a sub-element separator.
The segment in an actual transmission would appear as:
IT1**1*CA*1.08**CT*141151 N/L
In the ASC X12 code list "CA" is the unit of measure code for case, and "CT is the
product identification qualifier for carton.
The following list identifies terms associated with data segments and provides
references to codes and terms used in the X12 standard. The actual transmission does
not include all of the listed items as only the segment identifier characters, the values
for each data element, the data element separators and the segment terminator
characters are transmitted.
Segment Identifier, Two or three characters assigned to identify the segment. The
identifier occupies the first character positions of the segment.
Data Element Reference Number, A number assigned to the data element to
provide a reference to the ASC X12 Data Dictionary which defines specifications for
each data element.
Data Element Reference Designator, A structured code assigned to each data
element in a segment to indicate its unique position in the segment. It is composed of
the segment identifier and its sequential position within the segment.
Data Element Name, This is the name assigned to the data element in the ASC X12
Data Dictionary.
Attributes, Each data element has three ASC XI2 attributes: element usage or
Condition Designator, data element type, and Minimum/Maximum length.
Condition Designator
M Mandatory
The element is required to appear in the segment.
O Optional
10-2
-------
DMREDI IMPLEMENTATION Guromm
Appearance of the data element is at the option of the sending
party or is based on the mutual agreement of the trading
partners.
X Relational
Condition that may exist between two or more data elements
based on the presence or absence of one of the data elements.
Additional codes are used to identify the condition i.e. P -
Paired or Multiple, R - Required, E - Exclusion, C -
Conditional, or L - list Conditional. Refer to the XI2
Standards Manual, Introduction to X12.22 Segment Directory.
Data Element Type
ID Identifier
The data element must always contain a value from a
predefined list of values that is maintained by X12 or by other
bodies that are recognized by XI2 and identified by reference
in Appendix A in the Data Element Dictionary. The value is
left justified. Trailing spaces should be suppressed.
AN String •
Alpha-numeric sequence of characters containing at least one
non-space character. The significant characters must be left
justified. Leading spaces, if used are assumed to be significant
characters. Trailing spaces should be suppressed.
FS Fixed Length String
A sequence of any letters, spaces, and/or special characters
with spaces filled, if necessary, to satisfy minimum length:
DT Date
The format is YYMMDD where YY is the Year, MM is the
month and DD is the day of the month.
10-3
-------
DMREDI IMPLEMENTATION GUIDELINE
TM Time
Values for a time-type data element are in the HHMMSSd.d format
expressed using the 24-hour clock. HH expresses the hour(00-23),
MM expresses the minute(00-59), SS the seconds(00-59), and d..d is
the numeric expression of decimal seconds.
Nn Numeric
Numeric data element where N indicates a numeric and "n" indicates
the decimal places to the right of a fixed, implied decimal point. The
decimal point is not transmitted in the character stream! If the max
length of the data element was five position and the Type was N2, the
values sent would always have two decimal positions; an NO would
contain no decimal positions.
R Decimal
A numeric data element where the decimal point is optional for integer
values, but required for fractional values. Leading zeros should be
suppressed unless necessary to satisfy a minimum length requirement.
The decimal point and the minus sign when transmitted are not
counted when determining the length of the data element value. If the
max length of the data element was three positions, the following
represent the values that could be sent: NNN, .NNN, N.NN, NN.N, -
N.NN, etc.
B Binary
Any sequence of octets ranging in value from binary 00000000 to
binary 11111111. Binary may only exist in the BIN Segment.
Minimum/Maximum, This is the range, minimum to maximum, of the number of
character positions available to represent the data element value. It may be of
variable length with a minimum to maximum, or it may be of fixed length in which
the minimum is equal to the maximum.
10.2 X12 EDI Transmission Control Structure
The XI2 Transmission is a hierarchical structure of headers and trailers to allow
transaction sets of different types to be transmitted in the same transmission and
allows the data to be separated or segregated logically for easy interpretation and
internal routing by the receiver.
Transaction sets begin with an ST segment and end with an SE segment. Multiple
transaction sets of the same functional group are transmitted together beginning such
a group with a GS (Group Start) and ending with a GE (Group End) segment. One or
more functional groups are bound together for transmission within an interchange
envelope that starts with an ISA segment and ends with an IEA segment. There are
10-4
-------
DMREDI IMPLEMENTATION GUIDELINE
other segments available for Security and Interconnect control when using the
services of third party communications providers (VANS).
The interchange control structure is the interchange envelope consisting of a Header
(ISA) and a Trailer (IEA) for the electronic interchange through a data transmission,
and provides a structure to acknowledge the receipt and processing of the envelope.
The ISA and the IEA envelope one or more functional groups or interchange-related
control segments and perform the following functions:
• .Define the segment terminator, and the element and sub-element separators.
• Identify the sender and receiver, ,
• Provide control information for the interchange, and
• Allow for authorization and security information.
The GS and GE envelope transactions sets of the same type. Each type of transaction
is contained in a separate Functional Group to allow the receiver to parse the
information to the appropriate application. The GS segment provides the identity of
the Version and Release of the standard used to create the transaction. Both the GS
and the GE provide control information to ensure the validity of the interchange.
Every transaction set begins with an ST (Transaction Start) segment and is ended
with a SE (Transaction End) segment.
Translators normally strip off the ISA/TEA and GS/GE segments during translation.
It is the responsibility of the trading partners to make provision to archive the
transmissions before and after translation to satisfy EDI Audit Requirements.
The structures of the transaction set and functional group headers and trailers are
found in the Segment Directory. The structures of the interchange control header and
trailer are found in the Interchange Control Structures section of any current version
of the ASC XI2 Standards.
See the following EDI Transmission schematic. The schematic illustrates a typical format
for electronically transmitting a series of diverse business transactions.
10-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
Schematic of an EDI Transmission
ISA
ST
SE
ST
SE
GE
GS
ST
SE
//Communications Transport Protocol
Interchange Control Header
/ Functional Group Header
/ Transaction Set Header
Detail Segments
\Ttansaction Set Trailer
f Transaction Set Header
Detail Segments
X Transaction Set Trailer
X Functional Group Trailer
FUNCTIONAL GROUP |
/ Functional Group Header
/ Transaction Set Header
Detail Segments
X Transaction Set Trailer
\ FunctionalGiDup Trailer
| FUNCTIONAL GROUP
IEA x Interchange Co ntio I Trailer
O
cc
ui
O
CO
-------
DMREDI IMPLEMENTATION GUIDELINE
10.2.1 Control Segments
ICS Interchange Control Structures
Functional Group ID=
Introduction:
The purpose of this standard is to define the control structures for the electronic interchange of one or more
encoded business transactions including the EDI (Electronic Data Interchange) encoded transactions of
Accredited Standards Committee XI2. This standard provides the interchange envelope of a header and trailer
for the electronic interchange through a data transmission, and it provides a structure to acknowledge the receipt
and processing of this envelope.
Notes:
Pos. Seg.
No. ID
Not Used
010
020
030
040
050
ISA
TA1
GS
GE
IEA
Name
Interchange Control Header
Interchange Acknowledgment
Functional Group Header
Functional Group Trailer
Interchange Control Trailer
Req.
PCS.
M
O
O
O
M
Loop Notes and
Max.Use Repeat Comments
1
1
1
1
1
10-7
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment: JLt^A. Interchange Control Header
Position: 010
Loop:
Level:
Usage: Mandatory
Max Use: 1
Purpose: To start and identify an interchange of zero or more functional groups and
interchange-related control segments
Syntax Notes:
Semantic Notes:
Comments:
Notes:
•a&av &&& 4a& sspsent
Ref.
Des.
ISA01
ISA02
ISA03
Data
Element Name
Data Element Summary
Attributes
101 Authorization Information Qualifier M ID 2/2
Code to identify the type of information in the Authorization Information.
00 No Authorization Information Present (No Meaningful
Information in 102)
102 Authorization Information M AN 10/10
Information used for additional identification or authorization of the interchange
sender or the data in the interchange; the type of information is set by the
103 Security Information Qualifier M ID 2/2
Code to identify the type of information in the Security Information.
10-8
-------
DMREDI IMPLEMENTATION GUIDELINE
ISA04
ISA05
ISA06
ISA07
ISA08
» ISA09
» ISA10
» ISA11
» ISA12
104
105
106
105
107
00 No Security Information Present (No Meaningful
Information in 104)
Security Information M AN 10/10
This is used for identifying the security information about the interchange sender
or the data in the interchange; the type of information is set by the Security
Information Qualifier (103)
Interchange ID Qualifier M ID 2/2
Qualifier to designate the system/method of code structure used to designate the
sender or receiver ID element being qualified.
01 Duns (Dun & Bradstreet)
09 X.121(CCITT)
16 Duns Number With 4-Character Suffix
Interchange Sender ID M AN 15/15
Identification code published by the sender for other parties to use as the receiver
ID to route data to them; the sender always codes this value in the sender ID
element
Interchange ID Qualifier M ID 2/2
Qualifier to designate the system/method of code structure used to designate the
sender or receiver ID element being qualified.
01 Duns (Dun & Bradstreet)
09 X.121 (CCITT)
16 Duns Number With 4-Character Suffix
Interchange Receiver ID M AN 15/15
Identification code published by the receiver of the data. When sending, it is used
by the sender as their sending ID, thus other parties sending to them will use this
as a receiving ID to route data to them
M DT 6/6
M TM 4/4
108 Interchange Date
Date of the interchange.
109 Interchange Tune
Time of the interchange.
110 Interchange Control Standards Identifier M ID 1/1
Code to identify the agency responsible for the control standard used by the
message that is enclosed by the interchange header and trailer.
U U.S. EDI Community of ASG XI2, TDCC, and UCS
111 Interchange Control Version Number M ID 5/5
This version number covers the interchange control segments.
00304
Draft Standard for Trial Use Approved for Publication by
ASC XI2 Procedures Revi
10-9
-------
DMREDI IMPLEMENTATION GUIDELINE
ISA13
112 Interchange Control Number
A control number assigned by the interchange sender
M NO 9/9
ISA14
ISA15
113
114
ISA16
115
Acknowledgment Requested M ID 1/1
Code sent by the sender to request an interchange acknowledgment (TA1)
0 No Acknowledgment Requested
Test Indicator M ID 1/1
Code to indicate whether data enclosed by this interchange envelope is test or
production.
P Production Data
T Test Data
Component Element Separator M AN 1/1
This field provides the delimiter used to separate component data elements
within a composite data structure; this value must be different than the data
element separator and the segment terminator
10-10
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
Des.
GS01
GS02
GS03
GS04
GS05
GS06
GS07
Functional Group Header
030
Optional
1
To indicate the beginning of a functional group and to provide control information
Data Element Summary
Data
Element Name
Attributes
479 Functional Identifier Code M ID 2/2
Code identifying a group of application related Transaction Sets.
FA Functional Acknowledgment (997)
NC Nonconformance Report (842)
RT Report of Test Results (863)
142 Application Sender's Code M AN 2/15
Code identifying party sending transmission. Codes agreed to by trading
partners.
124 Application Receiver's Code M AN 2/15
Code identifying party receiving transmission. Codes agreed to by trading
partners.
373 Date M DT 6/6
Date (YYMMDD).
337
Time M TM 4/6
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59),
S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are
expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
.A* . +W ^rrrrr^^S^.5.. f * ft ^
28 Group Control Number M NO 1/9
Assigned number originated and maintained by the sender.
455 Responsible Agency Code M ID 1/2
Code used in conjunction with Data Element 480 to identify the issuer of the
standard.
10-11
-------
DMR EDI IMPLEMENTATION GUIDELINE
X Accredited Standards Committee XI2
» GS08 480 Version/Release/Industry Identifier Code M AN 1/12
Code indicating the version, release, subrelease, and industry identifier of the
EDI standard being used, including the GS and GE segments. If code in DE455
in GS segment is X, then in DE 480 positions 1 -3 are the version number;
positions 4-6 are the release and subrelease, level of the version; and positions 7-
12 are the industry or trade association identifiers (optionally assigned by user).
If code in DE455 in GS segment is T, then other formats are allowed
t!"- < * w ,. 'W „ v.^ ^
^•mmmg?** , , : ,,,'& -.- \ */££,„«
003040 Draft Standards Approved for Publication by ASC XI2
Procedures Review Board
003041 Draft Standards Approved for Publication by ASC X12
Procedures Review Board
003050 Draft Standards Approved for Publication by ASC XI2
Procedures Review Board
10-12
-------
DMREDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
GE
040
Functional Group Trailer
Optional
1
To indicate the end of a functional group and to provide control information
Ref.
Des.
GE01
GE02
Data
Element Name
97
Data Element Summary
Attributes
Number of Transaction Sets Included M NO 1/6
Total number of transaction sets included in the functional group or interchange
(transmission) group terminated by the trailer containing this data element.
28 Group Control Number
Assigned number originated and maintained by the sender.
M NO 1/9
10-13
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
PCS.
BEA01
IEA02
Interchange Control Trailer
050
Mandatory
1
To define the end of an interchange of zero or more functional groups and
interchange-related control segments
Data Element Summary
Data
Element Name
Attributes
116 Number of Included Functional Groups M NO 1/5
A count of the number of functional groups included in an interchange
112 Interchange Control Number M NO 9/9
A control number assigned by the interchange sender
10-14
-------
DMR EDI IMPLEMENTATION GUIDELINE
APPENDIX A
How To Get Started With
Electronic Data Interchange (EDI)
This is a check list for implementing EDI for the Discharge Monitoring Report (DMR)
process. EDI is the computer-to-computer (application-to-application) interchange of
predesignated message types hi standardized formats. The purpose of the DMR EDI
process is to electronically submit DMRs to the EPA Region or NPDES State Prograni
Office., ..;.-. _....;. .. : .
Check List For Pilot Participants
1. StartUp
Contact your EPA Region or NPDES State to get materials and set up a schedule.
Materials include the DMR Implementation Guideline and EDI software. The
schedule will include the folio whig tasks,
2. Orientation Meeting : <
Meet with the EDI coordinator for group orientation. The meeting will give an
overview of EDI and specific instructions on how to install and use the provided
software.
3. Equipment Setup
To operate the EDI DMR system, it is suggested that your microcomputer have the
folio whig:
640 KB RAM
40 MB Hard Drive
1 Floppy drive
Internal or External Modem
MS-DOS Based operating System version 3.2 or later
In addition, you must have access to a data line. Most EDI systems are stand-alone,
but the software may be configured to run on a Local Area Network (LAN) and use
LAN modems.
A-l
-------
DMR EDI Implementation Guideline
4. Installation
Install software and test communication facilities. The EDI coordinator will provide
assistance if needed.
5. Test Transmissions
Enter and transmit several DMR forms to assure that the process works correctly.
6. Operations Mode
Once you are assured that the transmissions are reliable, begin to send real DMR data
to your EPA Region or NPDES State, your trading partner. The Region or State will
maintain a data base of DMR data. Due to the paper requirements for the DMR, you
will still be required to follow the procedure of forwarding the paper reports to the
Region or State during the pilot.
7. Evaluation
Evaluate the effort for reliability, data accuracy and time savings.
Check List For State or Regional NPDES Program Offices
1. Feasibility Analysis
Initial analysis is important to the success of the EDI implementation. The following
issues should be considered before starting the implementation.
. Funding
Level of interest hi the reporting community
Regulatory language - determine legal applicability of electronic submission
Information systems support - determine effort needed to manage DMR data.
Identify the applicable in-house applications and develop an interface to the
EDI translation software. If no system already exists, consider building or
buying software to manage the data.
2. Select Pilot Participants
Identify good candidates for pilot participation. The EDI coordinator can contact
them and introduce them to the pilot.
3. Set up EDI Hardware and Software
A-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
The EDI coordinator will provide and set up the EDI software, establish a
communication service, and provide technical support for the Program Office. This
may require some coordination with internal information systems. The Regional or
State Program Office should have access to a microcomputer, and become familiar
with using the EDI software.
4. EDI Orientation
Each pilot participant should attend an orientation meeting to introduce them to the
technology and give them specific instructions for using the software. The EDI
coordinator will conduct the meeting.
5. Test Reception
The EDI coordinator will test your EDI system by receiving several DMRs from the
same or another system. DMRs must be received reliably before the pilot participants
start transmitting.
6. Organize DMR Data
Become familiar with a tool for managing DMR data. This is software developed in-
house, purchased, or provided by the EDI coordinator. Make sure you can at least
add, remove, find and view DMR records from the data base.
7. Schedule Participants
The EDI coordinator will setup a schedule with the pilot participants. For each pilot
participant, schedule a time to:
• Do a test transmission,
Begin sending "live" DMRs.
8. Receive Test DMR
The EDI coordinator will assist each pilot participant hi setting up and testing their
EDI system. Once a pilot sight has EDI equipment set up and configured, they
should create several dummy DMRs and attempt to send them via EDI. At the
Region or NPDES State, these test DMRs can be received and verified.
A-3
-------
DMR EDI Implementation Guideline
9. Receive Operational DMRs
Once a pilot participant's system is setup and tested, they may begin to send real
DMRs. They must also continue the current procedure of sending paper forms. At
this point it is unnecessary for both the trading partner and the Region or State to be •
in contact during the routine transmissions. DMRs can be received hi batches and I
transferred to the PCS data base.
10. Evaluation -
Evaluate the process of electronic submission for reliability, data accuracy and time
savings.
A-4
-------
DMR EDI iMPLElVffiNTATION GUIDELINE
APPENDIX B
B.I Functional Acknowledgment - Tranaction Set 997
PURPOSE: This implementation of this 997 Functional Acknowledgement is
transmitted as a return receipt to indicate the acceptance or rejection of a
863 Report of Test Results used for the submission of the Discharge
Monitoring Report to the EPA. This acceptance/rejection applies only to
the ability of submitted data to be translated under the X12
implementation convention-for this reporting. This transaction in no way
reflects on the validity of the data translated.
A Functional Acknowledgement indicating acceptance of an 863
transmission establishes the "Received Date" for the DMR.
TIMING: A 997 Transaction Set is generated and returned to the Trading Partner at
the completion of the translation of an inbound 863 Transaction Set.
TRANSACTION SET: ASC X12 Functional Acknowledgment (997), Version/Release
003040.
NOTE: The following symbols are found in the convention:
» indicates a required element
x indicates an element no used
B-l
-------
DMR EDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
B-2
-------
DMR EDI IMPLEMENTATION GUIDELINE
997 Functional Acknowledgment
Functional Group ED=JrA
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional
Acknowledgment Transaction Set (997) for use within the context of an Electronic Data Interchange (EDI)
environment. The transaction set can be used to define the control structures for a set of acknowledgments to
indicate the results of the syntactical analysis of the electronically encoded documents. The encoded documents are
the transaction sets, which are grouped in functional groups, used in defining transactions for business data
interchange. This standard does not cover the semantic meaning of the information encoded in-the transaction sets.
Pos.
No.
010
020
030
040
050
060
070
080
Seg.
ID
ST
AK1
AK2
AK3
AK4
AK5
AK9
SE
Name
Transaction Set Header
Functional Group Response Header
^£2? ^-T -""
Transaction Set Response Header
$j$$'ffi-~£j® ,-" r-^--—
Data Segment Note
Data Element Note
Transaction Set Response Trailer
Functional Group Response Trailer
Transaction Set Trailer
Req.
Des.
M
M
«- *.
O
,,,,,,,, --<- - -
0
0
u
M
U
Loop Notes and
Max.Use Repeat Comments
1 nl
1 n2
-; ,11!^^--*:-'^^
1 n3
--"" /%J.--- ^E!^ ,v,W" -SXS, vJ
1 cl
99
1
1
1
Transaction Set Notes
2.
3.
These acknowledgments shall not be acknowledged, thereby preventing an endless cycle of acknowledgments
of acknowledgments.
The Functional Group Header Segment (GS) is used to start the envelope for the Functional Acknowledgment
Transaction Sets. In preparing the functional group of acknowledgments, the application sender's code and the
application receiver's code, taken from the functional group being acknowledged, are exchanged; therefore,
one acknowledgment functional group responds to only those functional groups from one application
receiver's code to one application sender's code.
There is only one Functional Acknowledgment Transaction Set per acknowledged functional group.
AK1 is used to respond to the functional group header and to start the acknowledgement for a functional
group. There shall be one AK1 segment for the functional group that is being acknowledged.
AK2 is used to start the acknowledgement of a transaction set within the received functional group. The AK2
segments shall appear in the same order as the transaction sets in the functional group that has been received
and is being acknowledged.
B-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
Transaction Set Comments
1. The data segments of this standard are used to report the results of the syntatical analysis of the functional
groups of transaction sets; they report the extent to which the syntax complies with the standards for
transaction sets and functional groups. They do not report on the semantic meaning of the transaction sets (for
example, on the ability of the receiver to comply with the request of the sender).
B-4
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
!^ J. Transaction Set Header
010
Usage: Mandatory
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
1
To indicate the start of a transaction set and to assign a control number
1 The transaction set identifier (ST01) used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the invoice transaction set).
Ref.
DCS.
ST01
ST02
329
Data Element Summary
Name Attributes
Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set.
997 XI 2.20 Functional Acknowledgment
Transaction Set Control Number M AN
Identifying control number that must be unique within the transaction set
4/9
functional
a transaction set
B-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
A. JV JL Functional Group Response Header
020
Mandatory
1
To start acknowledgment of a functional group.
1 AK101 is the functional ID found in the GS segment (GSO1) in the functional group
being acknowledged.
2 AK102 is the data interchange control number found in the GS segment in the
functional group_ being acknowledged.
Data
Element Name
Data Element Summary
Attributes
» AK101 479 Functional Identifier Code M ID 2/2
Code identifying a group of application related Transaction Sets.
RT Report of Test Results (863)
» AK102 28 Group Control Number M NO 1/9
Assigned number originated and maintained by the sender.
B-6
-------
DMR EDI IMPLEMENTATION GUIDELINE
I
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
AK201
AK202
.A.JV^ Transaction Set Response Header
030
AK2
Optional
1
To start acknowledgment of a single transaction set.
1 AK201 is the transaction set ID found in the ST segment (STO1) in the transaction set
being acknowledged.
2 AK202 is the transaction set control number found in the ST segment in the
transaction set being acknowledged.
-••£...,,
Data
Element
143
329
Data Element Summary
Name Attributes
Transaction Set Identifier Code M ID 3/3
Code uniquely identifying a Transaction Set.
863 X12.41 Report of Test Results
Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
B-7
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
» AK301
» AK302
AK303
AK304
X AK305
X AK306
X AK307
X AK308
AJV«3 Data Segment Note
040
AK3
Optional , ...
1
To report errors in a data segment and to identify the location of the data segment.
Data Element Summary .. •
Name Attributes.
Segment ID Code M ID 2/3
Code defining the segment ID of the data segment in error. See Appendix A -
Number 77.
719 Segment Position in Transaction Set M NO 1/6
The numerical count position of this data segment from the start of the
transaction set: the transaction set header is count position 1.
447 Loop Identifier Code O AN 1/4
The loop ID number given on the transaction set diagram is the value for this
data element in segments LS and LE . ,
720 Segment Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a segment
Refer to 003040 Data Element Dictionary for acceptable code values.
720 Segment Syntax Error Code . O ID 1/3
Code indicating error found based on the syntax editing of a segment
Refer to 003040 Data Element Dictionary for acceptable code values.
720 Segment Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a segment
Refer to 003040 Data Element Dictionary for acceptable code values.
720 Segment Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a segment
Refer to 003040 Data Element Dictionary for acceptable code values.
720 Segment Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a segment
Refer to 003040 Data Element Dictionary for acceptable code values.
B-8
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
Des.
AK401
AK402
AK403
AK404
AK.4 Data Element Note
050
AK3
Optional .
99,
To report errors in a data element and to identify the location of the data element.
Data Element Summary
Name Attributes
Element Position in Segment M NO 1/2
This is used to indicate the relative position of the data element in error in this
data segment. The count starts with 1 for the data element immediately following
the segment ID. This value is 0 for an error in the segment ID.
725 Data Element Reference Number O NO 1/4
Reference number used to locate the Data Element Dictionary.
723 Data Element Syntax Error Code M ID 1/3
Code indicating the error found after syntax edits of a data element.
Refer to 003040 Data Element Dictionary for acceptable code values.
724 Copy of Bad Data Element O AN 1/99
This is a copy of the data element in error.
B-9
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
A Jv5 Transaction Set Response Trailer
060
AK2
Mandatory
1
To acknowledge acceptance or rejection and to report errors in a transaction set.
Data Element Summary
Ref. Data
DCS. Element Name Attributes
» AK501 717 Transaction Set Acknowledgment Code M ID 1/1
Code indicating accept or reject condition based on the syntax editing of the
transaction set.
A Accepted
R Rejected
AK502 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set.
Refer to 003040 Data Element Dictionary for acceptable code values.
AK503 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set.
Refer to 003040 Data Element Dictionary for acceptable code values.
AK504 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set.
Refer to 003040 Data Element Dictionary for acceptable code values.
AK505 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set.
Refer to 003040 Data Element Dictionary for acceptable code values.
AK506 718 Transaction Set Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of a transaction set.
Refer to 003040 Data Element Dictionary for acceptable code values.
B-10
-------
DMR EDI IMPLEMENTATION GUIDELINE
»
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
AK901
AK902
AK903
AK904
AK905
AK906
AK907
AK908
A.M\y Functional Group Response Trailer
070
Mandatory
1
To acknowledge acceptance or rejection of a functional group and report the number of
included transaction sets from the original trailer, the accepted sets, and the received sets
in this functional group.
1 If AK901 is 'A' or 'E', then the transmitted functional group is accepted. If AK901 is
'R', then the transmitted group is rejected
97
123
716
716
716
716
Data Element Summary
Name Attributes
Functional Group Acknowledge Code M ID 1/1
Code indicating accept or reject condition based on the syntax editing of the
functional group.
Refer to 003040 Data Element Dictionary for acceptable code values.
Number of Transaction Sets Included M NO 1/6
Total number of transaction sets included in the functional group or interchange
(transmission) group terminated by the trailer containing this data element
^ /-v »< T -L .'<., '-'±^^f^^^^.^^^^^i'^^^^^^
M NO 1/6
M NO 1/6
Number of Received Transaction Sets
Number of Transaction Sets received.
Number of Accepted Transaction Sets
Number of accepted Transaction Sets in a Functional Group.
Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group
header and/or trailer.
Refer to 003040 Data Element Dictionary for acceptable code values.
Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group
header and/or trailer.
Refer to 003040 Data Element Dictionary for acceptable code values.
Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group
header and/or trailer.
Refer to 003040 Data Element Dictionary for acceptable code values.
Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group
header and/or trailer.
B-ll
-------
DMR EDI IMPLEMENTATION GUIDELINE
Refer to 003040 Data Element Dictionary for acceptable code values.
AK909 716 Functional Group Syntax Error Code O ID 1/3
Code indicating error found based on the syntax editing of the functional group
header and/or trailer.
Refer to 003040 Data Element Dictionary for acceptable code values.
B-12
-------
I>MREI>I IMPLEMENTATION GUIDELINE
Segment:
' Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
Des.
SE01
SE02
Transaction Set Trailer
080
Mandatory
1
To indicate the end of the transaction set and provide Hie count of the transmitted segments
(including the beginning (ST) and ending (SE) segments).
1 SE is the last segment of each transaction set
Data Element Summary
Data
Element Name
Attributes
96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE
segments.
329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned bjp the originator for a transaction set
B-13
-------
DMR EDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
B-14
-------
DMR EDI IMPLEMENTATION GUIDELINE
B.2 997 Functional Acknowledgement Detail Mapping
This example is based on receipt of a transmission containing 3 reports (transaction set
863 - Report of Test Results); two were correct; the third had an error in the eighth
segment, a PER which contained an invalid code in the second data element (DE 366).
POS SEGMENT/ELEMENT INFORMATION
DE#
010 ST*997*0001 N/L
Transaction Set Header
143 ST01 997 Transaction Set ID Code.
997 - Functional Acknowledgement
329 ST02 0001 Transaction Set Control Number.
020 AK1*RT*2 N/L
Functional Group Response Header
479 AK101 RT Transaction Set Purpose .
RT - Report of Test Results (863)
28 AK102 2 Group Control Number (from GS06 of the
functional group being acknowledged)
030 AK2*863*0001 N/L
Transaction Set Response Header
143 AK201 863 Transaction Set Identifier Code
863 - Report of Test Results
329 AK202 0001 Transaction Set Control Number (from ST02 of
the transaction set being acknowledged)
060 AK5*A N/L
Transaction Set Response Trailer
717 AK501 A Transaction Set Acknowledgement Code
A - Accepted
030 AK2*863*0002 N/L
Transaction Set Response Header
143 AK201 863 Transaction Set Identifier Code
863 - Report of Test Results
B-15
-------
DMR EDI IMPLEMENTATION GUIDELINE
329 AK202 0002 Transaction Set Control Number (from ST02 of
the transaction set being acknowledged)
060 AK5*A N/L
Transaction Set Response Trailer
717 AK501 A Transaction Set Acknowledgement Code
A - Accepted
030 AK2*863*0003 N/L
Transaction Set Response Header
143 AK201 863 Transaction Set Identifier Code
863 - Report of Test Results
329 AK202 0003 Transaction Set Control Number (from ST02 of
the transaction set being acknowledged)
040 AK3*PER*8 N/L
Data Segment Note
721 AK301 PER Segment ID Code
PER
719 AK302 8 Segment Position in the Transaction Set
8th segment in the transaction
050 AK4*2*366*7 N/L
Data Element Note
C030 AK401 2 Position in Segment
Second element in the segment.
725 AK402 366 Data Element Reference Number
Data Element 366
723 AK403 7 Data Element Syntax Error Code
7 - Invalid code value
060 AK5*R N/L
Transaction Set Response Trailer
717 AK501 R Transaction Set Acknowledgement Code
R - Rejected
B-16
-------
DMR EDI IMPLEMENTATION GUIDELINE
070
715
AK9*A*3*3*2 N/L
Functional Group Response Trailer
AK901 A
97 AK902 3
123 AK903 3
2 AK903 2
080 SE* 12*0001 N/L
Transaction Set Trailer
96 SE01 XX
329 SE02 0001
Transaction Set Identifier Code
A - Accepted
Number of Transaction Sets Included in the
Functional Group being acknowledged (from
GE01 of the group being acknowledged).
Number of Received Transaction Sets
(Receiver's count)
Number of Accepted Transaction Sets
Number of Included Segments (in the
transaction).
Transaction Set Control Number. Must be the
same as in ST02.
B-17
-------
DMR EDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
B-18
-------
DMR EDI IMPLEMENTATION GUIDELINE
B.3 997 Functional Acknowledgement Sample Transmission
This example is based on receipt of a transmission containing 3 reports (transaction set
863 - Report of Test Results); two were correct; the third had an error in the eighth
segment, a PER which contained an invalid code in the second data element (DE 366).
ST*997*0001 N/L
AK1*RT*2 N/L
AK2*863*0001 N/L
AK5*A N/L
AK2*863*0002 N/L
AK5*A N/L
AK2*863*0003 N/L
AK3*PER*8 N/L
AK4*2*366*7 N/L
AK5*R N/L
AK9*A*3*3*2 N/L
SE* 12*0001 N/L
B-19
-------
-------
DMR EDI IMPLEMENTATION GUIDELINE
APPENDIX C
C.I Discharge Monitoring Report (863 - Report of Test Results)
PURPOSE: This implementation of the 863 Report of Test Results is used for the
submission of the Discharge Monitoring Report to the EPA. One 863 transaction will be
used to submit an entire DMR, i.e., all discharge monitoring data from a permittee for
one monitoring period.
TIMING: A translated DMR must be received by the EPA Region or NPDES delegated
State in accordance with the DMR submittal date of the state of the site reporting data. It
is the responsibility of the permittee submitting the DMR to assure that a translatable
transaction is received by EPA or State in a timely manner.
TRANSACTION SET: ASC X12 Report of Test Results (863), Version/Release
003041.
NOTE:
The following symbols are found in the convention:
» indicates an element is required
X indicates an element is not used
Replace Transactions: A Replace Transaction is identified by a "05" code in
BTR01. It is used to cancel a previously submitted DMR. PCS will overlay all
previously submitted data.
Zero Values: Standard ASC X12 translation procedures eliminate zero values.
The submitter must modify their translator to report a zero value when one is to
be reported.
c-i
-------
DMR EDI IMPLEMENTATION GUIDELINE
REGION AND STATE ROUTING CODE LIST
This is a code used to direct information within the EPA Region or State offices. Select
the code for the appropriate Region or State and place it in the Nl Segment, in N104
whenN101=ZD.
Region / State N104 Code
Region VI 6WEA
C-2
-------
PMR EDI IMPLEMENTATION GUIDELINE
863 Report of Test Results
Functional Group ID=Jx JL
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Report of Test Results
Transaction Set (863) for use within the context of an Electronic Data Interchange (EDI) environment. The
transaction set can be used to transmit the results of tests performed to satisfy a specified product or process
requirement. This includes, but is not limited to, test data such as inspection data, certification data, and statistical
process control measurements.
Heading:
No.
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Pos.
ID
010
020
030
040
050
060
065
070
080
090
100
110
120
130
140
Seg.
Name
ST
BTR
NTE
REF
DTM
PID
TMD
MEA
Nl
N2
N3
N4
REF
PER
REF
Des.
Transaction Set Header
Beginning Segment for Test Results
Note/Special Instruction
Reference Numbers
Date/Time/Period
Product/Item Description
Test Method
Measurements
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
fft&$m+m^' ,,,,, ,,,;;,...., ,,- ,
Administrative Communications Contact
Reference Numbers
Req.
Max.Use
M
M
F
0
O
O
o
o
' '•... •. *
o
o
o
o
o
""w,»-r~ " '"~, "
o
o
Loop Notes and
Repeat Comments
1
1
100
12
10
200
1
20
V.V f W.WJ- * •. V
^ •, vf.v,v \ f ff % ^^ AVi. ^
1
2
2
1
12
%,::„,, ^-Jt',* '£ ,xw--"- i
1
>1 nl
Detail:
Pos. Seg.
No. ID
010
Oil
020
LIN
NTE
PID
Name
Item Identification
Note/Special Instruction
Product/Item Description
Req.
Des.
O
F
O
Max. Use
Loop
Repeat
1
100
1000
Notes and
Comments
C-3
-------
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
025
030
031
032
034
040
050
051
052
053
054
055
056
057
060
070
090
100
120
130
150
160
170
172
174
180
190
195
197
200
TMD
MEA
PSD
SPS
QTY
DTM
REF
Nl
N2
N3
N4
REF
PER
QTY
CID
UIT
PSD
SPS
DTM
REF
MEA
DTM
REF
LM
LQ
STA
DTM
REF
LM
LQ
Test Method
Measurements
Physical Sample Description
Sampling Parameters for Summary Statistics
Quantity
Date/Time/Period
Reference Numbers
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
Administrative Communications Contact
Quantity
Characteristic/Class ID
Unit Detail
Physical Sample Description
Sampling Parameters for Summary Statistics
Date/Time/Period
Reference Numbers
Measurements
Date/Time/Period
Reference Numbers
&&*&$*» ___„,< ^
Code Source Information
Industry Code
pp£%;;i7 ^r^ *
Statistics
Date/Time/Period
Reference Numbers
PoUi-ii"" ,,, , 'fmf .,. „ ,,
Code Source Information
Industry Code
0 1
O 20
O >1
O >1
O 10
O 10
O 1000
0 1
0 2
0 2
0 1
O 10
03
O 10
0 1
0 1
o >i
O >1
o 10
O 10
0 1
O 10
O 10
,JL,r "::r, ,, -\/~ ,~, ?.-.*.* ~.
0 1
M >1
J« 1 _: -£/ !/ , ^1^ "'
0 1
0 10
O 10
\ --' »$ ' \
0 1
M >1
C-4
-------
DMR EDI IMPLEMENTATION GUIDELINE
NotUsed 201 TMD
NotUsed 202 MEA
NotUsed 203 DTM
NotUsed 204 REF
NotUsed 210 TSP
NotUsed 220 MEA
NotUsed 230 ,-DTM
NotUsed 240 REF
NotUsed 242 LM
NotUsed 244 LQ
Summary:
Pos. Seg.
No. ID
NotUsed 005 CTT
010
SE
'Name
Transaction Totals
Transaction Set Trailer
Test Method
Measurements
Date/Time/Period
Reference Numbers
Test Period or Interval
Measurements
Date/Time/Period.
Reference Numbers
Code Source Information
Industry Code
0 1
O >1
0 10
6 10
o i ~
O >1
O 10
O 10
0 1
M >1
Req. Loop
DCS. Max.Use Repeat
O 1
M 1
Notes and
Comments
Transaction Set Notes
1. The REF segment is to be used to send identification numbers associated with party referenced in the PER.
C-5
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
PCS.
ST01
ST02
1ST. Transaction Set Header
010
Heading
Mandatory
1
To indicate the start of a transaction set and to assign a control number
1 The transaction set identifier (STO1) used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the invoice transaction set).
c SI*
Data Element Summary
Data
Element
143
329
Attributes
M ID 3/3
Name
Transaction Set identifier Code
Code uniquely identifying a Transaction Set.
863 X12.41 Report of Test Results
Transaction Set Control Number
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
> ^ &f *•* MU&?^ vaa f i *" v=i> 'j. *V «•*• ,$.-ffff // *" vfv&$f$ >
AW. •''". K^ *v/Se?KS£ •> "^.....i ... u ., UJit, u5ii »*' JAWvil* AV«*j«A*»'tt*»A"i<*'!
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
-D A K. Beginning Segment for Test Results
020
Heading
Mandatory
1
To indicate the beginning of a test results transaction set.
1 If BTR01 equals 01, 02, 03, 04, 05, 18 or 19, then!
Comments:
Notes:
Ref.
DCS.
BTR01
BTR02
BTR03
BTR04
BTR05
BTR06
2
3
4
,,,
original test report reference number transmitted.
BTR02 is the date that this transaction set was created by the sending party.
BTR03 is the time that this transaction set was created by the sending party.
BTR05 specifies test results report reference number created by the sending party.
Data Element Summary
Data
Element Name
353 Transaction Set Purpose Code
Code identifying purpose of transaction set.
00 Original
05 Replace
Attributes
M ID 2/2
373
337
Date
Date (YYMMDD).
M DT 6/6
Time O TM 4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59),
S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are
expressed as follows- D = tenths (0-9) and DD = hundredths (00-99)
" <\ -1 w--www«ww \ •& ' •• V»WSfffffffffM 1 •"
\*\^ aM-S. ...i. .-. _ j> , v "^ J i Ji. •. ^ v^*1 ffffff
755
127
127
Report Type Code Q ID 2/2
Code indicating the title or contents of a document, report or supporting item
D J Discharge Monitoring Report
Reference Number Q AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Reference Number o AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
Segment: J^l JL lL Note/Special Instruct]
:ion
C-7
-------
DMR EDI IMPLEMENTATION GUIDELINE
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
030
Heading
Floating
100
To transmit information in a free-form format, if necessary, for comment or special
instruction
1 The NTE segment permits free-form information/data which,under ANSI XI2 standard
implementations, is not machine processable. The use of the' 'NTE" segment should
therefore be avoided, if at all possible, in an automated enyironment.
Ref.
PCS.
NTE01
NTE02
Data Element Summary
Data
Element Name Attributes
363 Note Reference Code O ID 3/3
Code identifying the functional area or purpose for which the note applies.
NCD Nonconformance Specification
3 Free Form Message M AN 1/60
Free-form text.
C-8
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
-DTJVl Bate/Time/Period
050
Heading
Optional
10
To specify pertinent dates and times
1 At least one of DTM02 DTM03 or DTM06 is required.
2 If either DTM06 or DTM07 is present, then the other is required.
Notes: TJ^»0«JC^miC^<^^^^g»^^re«|0^sl, €&#
"^ rf- *"*" V " 's " -fV"" '^
Ref.
DCS.
DTM01
X
DTM02
DTM03
DTM04
X
X
DTM05
DTM06
DTM07
Data Element Summary
Data
Element Name Attributes
374 Date/Time Qualifier M ID 3/3
Code specifying type of date or time, or both date and time.
090 Report Start
091 Report End
458 Certification
Date of a document attesting to a fact
373 Date X DT 6/6
Date (YYMMDD).
337 Time x JM 4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59),
S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are
expressed as follows: D = tenths (0-9) and DD = hundredths (00-99)
623 Time Code O ID 2/2
Code identifying the time. In accordance with International Standards
Organization standard 8601, time can be specified by a + or - and an indication in
hours in relation to Universal Time Coordinate (UTC) time. Since + is a
restricted character, + and - are substituted by P and M in the codes that follow.
Refer to 003041 Data Element Dictionary for acceptable code values.
624 Century O NO 2/2
The first two characters in the designation of the year (CCYY).
1250 Date Time Period Format Qualifier X ID 2/3
Code indicating the date format, time format, or date and time format.
Refer to 003041 Data Element Dictionary for acceptable code values.
1251 Date Time Period x AN 1/35
C-9
-------
DMR EDI IMPLEMENTATION GUIDELINE
Expression of a date, a time, or range of dates, times or dates and times.
C-10
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Nl Name
080
Nl
Heading
Optional
1
To identify a party by type of organization, name and code
1 At least one of N102 or N103 is required.
2 If either Nl 03 or Nl 04 is present, then the other is required.
1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
Ref.
Des.
N101
N102
N103
N104
Data Element Summary
Data
Element Name Attributes
98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
8D Permit Holder
ZD
93
66
67
Party to Receive Reports
The organization designated to receive reports
Name X AN 1/35
Free-form name.
Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code (67).
94 Code assigned by the organization that is the ultimate
destination of thetransaction set
Identification Code
Code identifying a party or other code.
AN 2/20
X
N105
706 Entity Relationship Code
Code describing entity relationship.
O ID 2/2
Refer to 003041 Data Element Dictionary for acceptable code values.
c-ll
-------
DMR EDI IMPLEMENTATION GUIDELINE
N106 98 Entity Identifier Code O ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Refer to 003041 Data Element Dictionary for acceptable code values.
C-12
-------
DMREDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
PCS.
REF01
REF02
REF03
JvJE_T Reference Numbers
120
Nl
Heading
Optional
12
To specify identifying numbers.
1 At least one of REF02 or REF03 is required.
Attributes
M ID 2/2
Data Element Summary
Data
Element Name
128 Reference Number Qualifier
Code qualifying the Reference Number.
PN Permit Number
127 Reference Number X AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
t^y)iKiy^f^^^^f^f^fffffff^fffffff^^JJ^J'4"Vff-'fJ-vjJJJ^*J-*-t-*-t-*-*-^-'-'-'-'-t-'-'->-f-I-f •••••••••••• •• yy*
352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
C-13
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
JL Jl/Jtv Administrative Communications Contact
130
PER
Heading
Optional
1
To identify a person or office to whom administrative communications should be directed
1 If either PER03 or PER04 is present, then the other is required.
2 If either PER05 or PER06 is present, then the other is required.
»
X
X
Ref.
DCS.
PER01
PER02
PER03
PER04
PER05
PER06
Data Element Summary
Data
Element Name Attributes
366 Contact Function Code M ID 2/2
Code identifying the major duty or responsibility of the person or group named.
93
AA Authorized Representative
CE Certifier
Name O AN 1/35
Free-form name.
365 Communication Number Qualifier O ID 2/2
Code identifying the type of communication number.
TE Telephone
364 Communication Number O AN 1/80
Complete communications number including country or area code when
applicable.
':£'•(
365 Communication Number Qualifier O ID 2/2
Code identifying the type of communication number.
Refer to 003041 Data Element Dictionary for acceptable code values.
364 Communication Number O AN 1/80
Complete communications number including country or area code when
applicable.
C-14
-------
DMREDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
REF01
J\JtL_r Reference Numbers
140
PER
Heading
Optional
To specify identifying numbers.
1 At least one of REF02 or REF03 is required.
X
REF02
REF03
Data Element Summary
Data
Element Name Attributes
128 Reference Number Qualifier M ID 2/2
Code qualifying the Reference Number.
4A Personal Identification Number (PIN)
A number that uniquely identifies an individual
127 Reference Number X AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
C-15
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
LIN01
J-jJLlN Item Identification
010
LIN
Detail
Optional
1
To specify basic item identification data.
1 If either LIN04 or LINOS is present, then the other is required.
2 If either LIN06 or LIN07 is present, then the other is required.
3 If either LINOS or LIN09 is present, then the other is required.
4 If either LIN10 or LIN11 is present, then the other is required.
5 If either LIN12 or LIN13 is present, then the other is required.
6 If either LIN14 or LIN15 is present, then the other is required.
7 If either LIN16 or LIN17 is present, then the other is required.
8 If either LIN18 or LIN19 is present, then the other is required.
9 If either LIN20 or LIN21 is present, then the other is required.
10 If either LIN22 or LIN23 is present, then the other is required.
11 If either LIN24 or LDSF25 is present, then the other is required.
12 If either LIN26 or LIN27 is present, then the other is required.
13 If either LIN28 or LIN29 is present, then the other is required.
14 If either LIN30 or LIN31 is present, then the other is required.
1 LIN01 is the line item identification
1 See the Data Dictionary for a complete list of ID's.
2 LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each
vitem. For Example: Case, Color, Drawing No, UPC No, ISBN No, Model No, SKU._
WW:-^-'-*- "-'** ~;r"sv
fts'm
Data Element Summary
Data
Element Name Attributes
350 Assigned Identification O AN 1/11
Alphanumeric characters assigned for differentiation within a transaction set.
LIN02
LINOS
LIN04
235 Product/Service ID Qualifier M ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
P5 Material Discharge Number
Number identifying the point where material is discharged
234 Product/Service ID M AN 1/30
Identifying number for a product or service.
235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
C-16
-------
DMR EDI IMPLEMENTATION GUIDELINE
Refer to 003041 Data Element Dictionary for acceptable code values.
X LINOS 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEV06 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LBV07 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LINOS 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN09 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEV10 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
: Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN11 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN12 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LBV13 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LBV14 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN15 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN16 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LJN17 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEV18 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN19 234 Product/Service ID O AN 1/30
C-17
-------
DMR EDI IMPLEMENTATION GUIDELINE
Identifying number for a product or service.
X LIN20 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN21 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LBST22 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN23 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X UN24 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN25 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN26 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN27 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEN28 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X IJN29 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LBV30 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003041 Data Element Dictionary for acceptable code values.
X LIN31 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
C-18
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
1^1 J. Ji/ Note/Special Instruction
Oil
LIN
Detail
Floating
100
To transmit information in a free-form format, if necessary, for comment or special
instruction
1 The NTE segment permits free-form information/data which,under ANSI XI2 standard
implementations, is not machine processable. The use of the'' NTE" segment should
therefore be Avoided, if at all possible, in an automated environment.
«fc«~.r. ..™.^W:^r '
Ref.
PCS.
NTE01
NTE02
Data Element Summary
Data
Element Name Attributes
363 Note Reference Code O ID 3/3
Code identifying the functional area or purpose for which the note applies.
NCD Nonconformance Specification
3 Free Form Message M AN 1/60
Free-form text.
C-19
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
JL \\J Product/Item Description
020
LIN
Detail
Optional
1000
To describe a product or process in coded or free-form format
1 If PID04 is present, then PID03 is required.
2 At least one of PID04 or PHD05 is required.
3 If PID07 is present, then PID03 is required.
4 If PID08 is present, then PID03 is required.
1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PDD04 should be used for industry-specific product description codes.
3 PID08 describes the physical characteristics of the product identified in PID04. A " Y"
indicates that the specified attribute applies to this item. A "N" indicates it does not
apply. Any other value is indeterminate.
1 If PED01 = "F", then PID05 is used. If PID01 ='' S", then PID04 is used. If PID01 =
"X", then both PID04 and PID05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being described in
the segment.
PID07 specifies the individual code list of the agency specified in PID03
Data Element Summary
Ref. Data
DCS. Element Name Attributes
» PID01 349 Item Description Type M ID 1/1
Code indicating the format of a description.
S Structured (From Industry Code List)
» PID02 750 Product/Process Characteristic Code O ID 2/3
Code identifying the general class of a product or process characteristic
08
12
28
Product
Type and/or Process
CodfcfitffiaFOTa&teOSQj ;
C-20
-------
DMR EDI IMPLEMENTATION GUIDELINE
Test Sample Location
X
X
X
prooa
PID04
FIDOS
PID06
Proo?
FIDOS
29
88
559 Agency Qualifier Code X ED 2/2
Code identifying the agency assigning the code values.
EP United States Environmental Protection Agency (EPA)
751 Product Description Code X AN 1/12
A code from an industry code list which provides specific data about a product
characteristic.
352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position that is being described.
Refer to 003041 Data Element Dictionary for acceptable code values.
822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier.
1073 Yes/No Condition or Response Code
Code indicating a Yes or No condition or response.
Refer to 003041 Data Element Dictionary for acceptable code values.
O ID 1/1
C-21
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Measurements
030
LIN
Detail
Optional
20
To specify physical measurements or counts, including dimensions, tolerances, variances,
and weights (See Figures Appendix for example of use of COO 1.)
1 At least one of MEA03 MEA05 MEA06 or MEA08 is required.
2 If MEA05 is present, then MEA04 is required.
3 If MEA06 is present, then MEA04 is required.
4 If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.
5 Only one of MEA08 or MEA03 may be present.
1 MEA04 defines the unit of measure for MEA03, MEA05, and MEA06. '
1 When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any
measurement where a positive (+) value cannot be assumed use MEA05 as the negative
(-) value and MEA06 as the positive (+) value.
ywr •• •• \ •• * "•''• -••
X
Ref.
DCS.
MEA01
MEA02
MEA03
MEA04
C00101
X
X
X
C00102
C00103
C00104
Data
Element
737
738
739
Data Element Summary
Name Attributes
Measurement Reference ID Code O ID 2/2
Code identifying the broad category to which a measurement applies
CT Counts
Measurement Qualifier O ID 1/3
Code identifying a specific product or process characteristic to which a
measurement applies
Refer to 003041 Data Element Dictionary for acceptable code values.
Measurement Value X R 1/10
The value of the measurement.
C001 Composite Unit of Measure X
To identify a composite unit of measure (See Figures Appendix for examples of
use.)
355 Unit or Basis for Measurement Code M ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
IN Count
1018 Exponent O R 1/15
Power to which a unit is raised.
649 Multiplier O R 1/10
Value to be used as a multiplier to obtain a new value
355 Unit or Basis for Measurement Code O ID 2/2
C-22
-------
DMR EDI IMPLEMENTATION GUIDELINE
X
X
X
X
X
X
X
X
X
C00105
C00106
C00107
COO 108
C00109
C00110
C00111
C00112
C00113
1018
649
355
1018
649
355
1018
649
355
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent O R
Power to which a unit is raised.
Multiplier O R
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code O ID
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent O R
Power to which a unit is raised.
Multiplier O R
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code O ID
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent OR
Power to which a unit is raised.
Multiplier O R
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code O ID
1/15
1/10
2/2
1/15
1/10
2/2
1/15
1/10
2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
X
X
X
X
X
X
C00114
C00115
MEA05
MEA06
MEA07
MEA08
1018
649
740
741
935
936
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent O R
Power to which a unit is raised.
Multiplier OR
Value to be used as a multiplier to obtain a new value
Range Minimum X R
The value specifying the minimum of the measurement range.
Range Maximum X R
The value specifying the maximum of the measurement range.
Measurement Significance Code O ID
Code used to benchmark, qualify or further define a measurement value.
Refer to 003041 Data Element Dictionary for acceptable code values.
Measurement Attribute Code X ID
1/15
1/10
1/10
1/10
2/2
2/2
X
MEA09
752
Code used to express an attribute response when a numeric measurement value
cannot be determined.
Refer to 003041 Data Element Dictionary for acceptable code values.
Surface/Layer/Position Code O ID 2/2
C-23
-------
DMR EDI IMPLEMENTATION GUIDELINE - .•
Code indicating the product surface, layer or position that is being described.
Refer to 003041 Data Element Dictionary for acceptable code values.
X MEA10 1373 Measurement Method or Device O ID 2/4
The method or device used to record the measurement
Refer to 003041 Data Element Dictionary for acceptable code values.
C-24
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
DCS.
crooi
X
X
X
X
CED02
CTO03
croo4
croos
CID06
croo?
CLD Characteristic/Class ID
060
CED
Detail
Optional
1 '
To specify the general class or specific characteristic upon which test results are being
reported or are to be taken
1 At least one of CIDO1 CID02 CID04 or CID05 is required.
2 If either CID03 or CID04 is present, then the other is required.
3 If CID06 is present, then both CID03 and CID04 are required.
4 If CID07 is present, then at least one of CID04 or CID05 is required.
1 CID06 specifies the individual code list of the agency specified in CID03.
2 CID07 refers to whether or not the characteristic identified in CID04 or CID05 or both
is affected by the product change. If it is affected, the value is " Y". A value of " N" is
used when it is known that it will not be affected. Any other value indicates it is
indeterminate.
t - <*
"
Data Element Summary
Data
Element Name Attributes
738 Measurement Qualifier X ID 1/3
Code identifying a specific product or process characteristic to which a
measurement applies
TR Length Type: Random
W^V.W.Wflrt
750 Product/Process Characteristic Code X ID 2/3
Code identifying the general class of a product or process characteristic
Refer to 003041 Data Element Dictionary for acceptable code values.
559 Agency Qualifier Code X ID 2/2
Code identifying the agency assigning the code values.
Refer to 003041 Data Element Dictionary for acceptable code values.
751 Product Description Code X AN 1/12
A code.from an industry code list which provides specific data about a product
characteristic.
352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier.
1073 Yes/No Condition or Response Code O ID 1/1
Code indicating a Yes or No condition or response.
Refer to 003041 Data Element Dictionary for acceptable code values.
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
I
1;
to
E
0
1
T
Q»
cli
1
2
3
4
S
1
1
Notes:
Ref.
PCS.
MEA01
MEA02
MEA03
IVJLJtLA Measurements
Optional
1
To specify physical measurements or counts, including dimensions, tolerances, variances,
and weights (See Figures Appendix for example of use of COO 1.)
At least one of MEA03 MEA05 MEA06 or MEA08 is required.
If MEA05 is present, then MEA04 is required.
If MEA06 is present, then MEA04 is required.
If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.
Only one of MEA08 or MEA03 may be present.
MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.
When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any
measurement where a positive (+) value cannot be assumed use MEA05 as the negative
Data Element Summary
Data
Element Name Attributes
737 Measurement Reference ID Code O ID 2/2
Code identifying the broad category to which a measurement applies
TR Test Results
Indicates that the data to follow are the results test
measurements
738 Measurement Qualifier O ID 1/3
Code identifying a specific product or process characteristic to which a
measurement applies
CON Concentration
The relative amount of a component of a sample of
product containing multiple components
QUR Reportable Quantity
739 Measurement Value X R 1/10
The value of the measurement.
C-26
-------
DMR EDI IMPLEMENTATION GUIDELINE
MEA04
C00101
C001
355
Composite Unit of Measure X
To identify a composite.unit of measure (See Figures Appendix for examples of
use.)
Unit or Basis for Measurement Code M ID 2/2
Code specifying the; units in which a value is being expressed, or manner in
which a measurement has been taken
Each
X
X
X
X
X
X
X
X
X
X
X
X
C00102
C00103
C00104
C00105
C00106
C00107
C00108
C00109
C00110
C00111
C00112
C00113
1018
649
355
1018
649
355
1018
649
355
1018
649
355
' EA '
Exponent
Power to which a unit is raised.
O R 1/15
O R 1/10
Multiplier
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent
Power to which a unit is raised.
Multiplier
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code
O R 1/15
O R 1/10
O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent
Power to which a unit is raised.
Multiplier
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code
O R 1/15
O R 1/10
O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
Exponent
Power to which a unit is raised.
O R 1/15
O R 1/10
Multiplier
Value to be used as a multiplier to obtain a new value
Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement Jias been taken
Refer to 003041 Data Element Dictionary for acceptable code values.
C-27
-------
DMR EDI IMPLEMENTATION GUIDELINE
X
X
X
X
X
C00114
C00115
MEA05
MEA06
MEA07
MEA08
MEA09
MEA10
1018 Exponent
Power to which a unit is raised.
O R
O R
649 Multiplier
Value to be used as a multiplier to obtain a new value
740 Range Minimum X R
The value specifying the minimum of the measurement range.
1/15
1/10
1/10
S«3Bgfo,va»»!3»?
741 Range Maximum X R
The value specifying the maximum of the measurement range.
1/10
935 Measurement Significance Code O ID 2/2
Code used to benchmark, qualify or further define a measurement value.
03 Approximately
06 Greater than
07 Less than
23 Predicted
936 Measurement Attribute Code X ID 2/2
Code used to express an attribute response when a numeric measurement value
cannot be determined.
Refer to 003041 Data Element Dictionary for acceptable code values.
752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position that is being described.
Refer to 003041 Data Element Dictionary for acceptable code values.
1373 Measurement Method or Device O ID 2/4
The method or device used to record the measurement
Refer to 003041 Data Element Dictionary for acceptable code values.
C-28
-------
DMR EDI IMPLEMEIVTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
Des.
LM01
LM02
Code Source Information
172
LM
Detail
Optional
1
To transmit standard code list identification information
LM02 identifies the applicable industry code list source information.
ff ef V. -. vffffffffffffff fff "• • ffffff ~ff sss %%s^ % ** f t^fj. fffffffffff ff ff fff f
Data
Element
559
822
Data Element Summary
Name , Attributes
Agency Qualifier Code M ID 2/2
Code identifying the agency assigning the code values.
EP United States Environmental Protection Agency (EPA)
Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier.
C-29
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Industry Code
174
LM
Detail
Mandatory
>1
Code to transmit standard industry codes
1 If LQO1 is present, then LQ02 is required.
Ref.
Des.
LQ01
LQ02
Data Element Summary
Data
Slement Name Attributes
1270 Code List Qualifier Code O ID 1/3
Code identifying a specific industry code list
Refer to 003041 Data Element Dictionary for acceptable code values.
1271 Industry Code X AN 1/20
Code indicating a code from a specific industry code list
C-30
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Transaction Set Trailer
010
Summary
Mandatory
1
To indicate the end of the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments).
SE is the last segment of each transaction set
W, ^ — -
Data Element Summary
Ref. Data
DCS. Element Name Attributes
SE01 96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE
segments.
SE02 329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
C-31
-------
DMR EDI IMPLEMENTATION GUIDELINE
C.2 Detailed Mapping
The following is a detailed mapping of an 863. It gives examples and explanations for the usage
of this transaction set.
HEADER AREA
POS SEGMENT/ELEMENT INFORMATION
DE#
010 ST*863*00001 N/L
Transaction Set Header
143 ST01 863 Transaction Set ID Code.
863 - Report of Test Results
329 ST02 00001 Transaction Set Control Number.
020 BTR*05*941202*1030*DJ*628307*62502 N/L
Beginning Segment for Test Results
353 BTR01 05 Transaction Set Purpose.
00-Original
05 - Replace
373 BTR02 941202 Date the transaction was created-December 2,1994.
337 BTR03 1030 Time the transaction was created-10:30 PM.
755 BTR04 DJ Report Type Code.
D J - Discharge Monitoring Report
127 BTR05 628307 Report Number.
127 BTR06 Previous Report Number when the report is to be Replaced, i.e when
BTR01 equals 05.
Floating NTE*NCD*Additional test information N/L
Note\Special Instruction
363 NTE01 NCD Note Reference Code
NCD - Nonconformance Specification. This segment is used to elaborate any addtional parameter
information.
3 NTE02 Text Free Form Message
Free-form text.
050 DTM*4S8*940115 N/L
Date/Time Reference
374 DTM01 458 Date/Time Qualifier.
458 - Certification
373 DTM02 940115 Date the Responsible Corporate Officer certified this Dischagre
Monitoring Report - January 15,1994.
050 DTM*090*941201 N/L
Date/Time Reference
C-32
-------
DMR EDI IMPLEMENTATION GUIDELINE
374 DTM01 090
373 DTM02 941201
050 DTM*091*941231 N/L
Date/Time Reference
374 DTM01 091
373 DTM02 941231
080 N1*8D*ABC Company N/L
Name
98 N101 8D
93 N102 ABC Company
66 N103
Date/Time Qualifier.
090 - Report Start
Date
December 1,1994
Date/Time Qualifier.
091 -Report End
Date
December 31,1994
Entity Identifier Code.
8D-Permit Holder
Name
Submitting Company Name.
Identification Code Qualifier.
Not Used
67 N104
120 REF*PN*XXD003301 N/L
Reference Numbers
128 REF01 PN
127
REF02 XXD003301
ID Code
Not used when Nl 01 = 8D
Reference Number Qualifier.
PN - Permit Number
Reference Number
NPDES permit number of the site reporitng.
130 PER*CE* John Smith*TE*(800)555-1212 N/L
Administrative Communications Contact
366 PER01 CE Contact Function Code.
CE - Certifier
See DE 366 for choices. Too many to
list here.
93 PER02 John Smith
365 PER03 TE
364 PER04 (800) 555-1212
140 REF*4A*AS34 N/L
Reference Numbers
128 REF01 4A
Name.
Communications Number Qualifier
TE - Telephone
Communication Number
Telephone number of certifier.
Reference Number Qualifier.
4A - Personal Identification Number
C-33
-------
DMR EDI IMPLEMENTATION GUIDELINE
127 REF02 A534
Reference Number
The number assigned by Region 6 to the individual responsible for
the signing the paper DMR.
080 N1*ZD**94*6WEAN/L
Name
98 N101 ZD
93 N102
66 N103 94
67 N104 6WEA
Entity Identifier Code.
ZD - Party to Receive Reports
Name
Not Used
Identification Code Qualifier.
94 - Code assigmed by the organization that is the ultimate
destination of the transaction set.
ID# assigned by the EPA.
Used when N101 = ZD. 6WEA is the Region 6 Mailcode
DETAIL AREA
010 LIN*1*P5*001AN/L
Item Identification
350 LIN01 1
235 LIN02 P5
234 LIN03 1
Assigned Identification
Sequential number to uniquely identifiy the repetition of the loop.
Begin with 1 and. increment by 1 for each subsequent occurrence of
the loop.
Product/Service ID. Qualifier.
P5 - Material Discharge Number.
Product/Service ID Number
Discharge Number.
Floating NTE*NCD*Additional test information N/L
NoteXSpecial Instruction
363 NTE01 NCD Note Reference Code
NCD - Nonconformance Specification. This segment is used to
elaborate any addtional parameter information.
NTE02 Text
040 PID*S*08*EP*TAB1B***PCS160
Product/Item Description
349 PID01 S
750 PBD02 08
Free Form Message
Free-form text.
Item Description Type
S - Structured from the PCS Codes and Descriptions Volume
Product/Process Characteristic Code
C-34
-------
DMR EDI IMPLEMENTATION GUIDELINE
559 PID03 EP
751 PID04 TAB1B
822 PED07 PCS 160
08 - for the PCS Parameter Code
12 - for the PCS Sample Type Code
28 - for the PCS Test Sample Frequency Code
29 - for the PCS Monitoring Location Code
88 - for the PCS No Discharge Indicator Code
Agency Qualifier Code
EP-U.S. EPA
Product Description Code
PCS Code from code table referenced in PID07.
Source Subqualifier
PCS + the appropriate code table number
PCS160whenPID02=08
PCS150whenPDD02=12
PCS050 when PID02=28
PCS080 when PID02=29
PCS490 when PID02=88
120 MEA*CT**3*1NN/L
Measurements
737 MEA01 CT
739 MEA03 3
C001 MEA04 59
Measurement Reference ID Code.
CT - Counts
Measurement Qualifier
Number of Excursions.
Composite Unit of Measure.
IN - Count
060
750
150
737
CID*TR N/L
Characteristic/Class ID
CID01 TR
Measurement Qualifier
TR - Length Type: Random. This code is in place to initiate the
CID loop.
MEA*TR*CON**EA*6.3 N/L (Concentration minimum is 6.3)
Measurements
MEA01 TR Measurement Reference ID Code.
TR-Test Results
738 MEA02 CON
Measurement Qualifier.
CON - Concentration
C-35
-------
DMR EDI IMPLEMENTATION GUIDELINE
001 MEA04 EA Composite Unit of Measure.
EA-Each. This is used as dummy code
740 MEA06 6.3 Range Minimum
The minimum value is 6.3.
150 MEA*TR*CON*2.3*EA N/L (Concentration average is 2.3)
Measurements
737 MEA01 TR Measurement Reference ID Code.
TR-Test Results
738 MEA02 CON Measurement Qualifier.
CON - Concentration
741 MEA03 2.3 Measurement Value
The average concentration is 2.3
C001 MEA04 EA Composite Unit of Measure.
EA - Each. This is used as dummy code
ISO MEA*TR*QUR**EA**1000*07 N/L (Quantity maximum is less than 1000)
Measurements
737 MEA01 TR Measurement Reference ID Code.
TR-Test Results
738 MEA02 QUR Measurement Qualifier.
QUR - Quantity
741 MEA06 1000 Range Maximum
935 MEA07 07 Measurement Significance Code
07 - Less than
ISO MEA*TR*QUR*99999***23 N/L (Average quantity is too number to count.)
Measurements
737 MEA01 TR Measurement Reference ID Code.
TR-Test Results
738 MEA02 QUR Measurement Qualifier.
QUR - Quantity
741 MEA03 99999 Measurement Value.
This segment is used to report the average value. When the average
is too numerous to count, this 99999 is reported to indicate average
value. MEA07=23 to indcates the attribute of too numerous to
count.
935 MEA07 07 Measurement Significance Code
23 - Predicted. This code value is used to indicate too numerous to
count. When 23 is used, either MEA03, MEA05, or MEA06 must
equal 99999 in order to show whether the average, minimum, or
maximum is too numerous to count..
c-36
-------
DMR EDI IMPLEMENTATION GUIDELINE
172 LM*EP*PCS180 N/L
Code Source Information
559 LM01 EP
822 LM02 PCS 180
174 LQ**57
Industry Code
1271 LQ02 57
Agency Qualifier Code
EP-U.S. EPA
Source Subqualifier
PCS 180 - Table 180 from the PCS Codes and Descriptions Manual
Industry Code
57 - Gallons. This value is from the code table listed in LM02.
SUMMARY AREA
020 SE*58*0001 N/L
Transaction Set Trailer
96 SE01 58
329 SE02 00001
Number of Included Segments (in the
transaction).
Transaction Set Control Number. Must be the same as in ST02.
C-37
-------
PMR EDI IMPLEMENTATION GUIDELINE
C.3 Sample Transmission
The following is a sample transmission of the DMR:
ISA*00* *01*SITE NAME *01*XXD003456780
*01*057944910*921014*1743*U*00304*000000034*0*T*: N/L
GS*RT*DMR PILOT*PCS*921014*1734*34*X*003040 N/L
ST*863*00822 N/L
BTR*00*921014*1730*DJ*0001 N/L
DTM*090*920501 N/L
DTM*091*920531 N/L
DTM*058*921014 N/L
N1*8D*ABC COMPANY N/L
REF*PN*XX03301 N/L
PER*CE*JOHN SMITH*TE*800/555-1212 N/L
REF*4A*02021 N/L
N1*ZD**94*6WEA N/L
LIN*1*P5*001A N/L (Discharge Number)
PID*S*08*EP*00011***PCS160 N/L (Parameter)
PID*S*12*EP*RT***PCS150 N/L (Sample Type)
PID*S*28*EP*01/01***PCS050 N/L (Frequency of Analysis)
MEA*CT**0*1N N/L (# of excursions)
CID*TR N/L
MEA*TR*CON**EA**92 N/L (Concentration)
LM*EP*PCS180 N/L
LQ**8X N/L
MEA*TR*CON*85.45*EA N/L
LM*EP*PCS180 N/L
LQ**8X N/L
LIN*2*P5*001A N/L
NTE*NCD*THERE WERE SEVEN EXCEEDANCES OF THE 6 - 9 PH MONITORING IN
MA N/L
NTE*NCD*Y (5 PH-HIGHS AND 2 PH-LOWS). N/L
NTE*NCD*THESE WERE NOT NON-COMPLIANCES, BUT EXCURSIONS 9PER PART
II N/L
NTE*NCD*I.5, THIS PERMIT. N/L
PID*S*08*EP*00400***PCS160 N/L
PID*S*12*EP*RT***PCS150 N/L
PID*S*28*EP*01/01***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
MEA*TR*CON**EA**10 N/L
LM*EP*PCS180 N/L
LQ**UN N/L
MEA*TR*CON*5.7*EA N/L
LM*EP*PCS180 N/L
LQ**UN N/L
LIN*3*P5*001A N/L
PID*S*08*EP*34641***PCS160 N/L
PID*S*12*EP*24***PCS150 N/L
PID*S*28*EP*01/30***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
C-38
-------
DMR EDI IMPLEMENTATION GUIDELINE
MEA*TR*QUR**EA**0 N/L
LM*EP*PCS180 N/L
LQ**8D N/L
MEA*TR*QUR*0*EA N/L
LM*EP*PCS180 N/L
LQ**8D N/L
LIN*4*P5*001A N/L
PID*S*08*EP*39084***.PCS160 N/L
PID*S*12*EP*24***PCS150 N/L
PID*S*28*EP*01/30***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
MEA*TR*QUR**EA**0 N/L
LM*EP*PCS180 N/L
LQ**8D N/L
MEA*TR*QUR*0*EA N/L
LM*EP*PCS180 N/L
LQ**8D N/L
LIN*5*P5*001A N/L
PID*S*08*EP*50050***PCS160 N/L
PID*S*12*EP*CA***PCS150 N/L
PID*S*28*EP*01/01***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
MEA*TR*QUR**EA**584 N/L
LM*EP*PCS180 N/L
LQ**7E N/L
MEA*TR*QUR*543.94*EA N/L
LM*EP*PCS180 N/L
LQ**7E N/L
LIN*6*P5*001A N/L
PID*S*08*EP*50060***PCS160 N/L
PID*S*12*EP*GR***PCS150 N/L
PID*S*28*EP*01/01***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
MEA*TR*QUR**EA**0 N/L
LM*EP*PCS180 N/L
LQ**8D N/L
MEA*TR*QUR*0*EA N/L
LM*EP*PCS180 N/L
LQ**8D N/L
LIN*7*P5*001A N/L
PID*S*08*EP*78171***PCS160 N/L
PID*S*12*EP*24***PCS150 N/L
PID*S*28*EP*01/30***PCS050 N/L
MEA*CT**0*1N N/L
CID*TR N/L
MEA*TR*QUR**EA**0 N/L
LM*EP*PCS180 N/L
LQ**8D N/L
MEA*TR*QUR*0*EA N/L
LM*EP*PCS180 N/L
LQ**8D N/L
C-39
-------
DMR EDI IMPLEMENTATION GUIDELINE
SE*99*00822 N/L
ST*863*00823 N/L
BTR*00*921014*1730*DJ*0002 N/L
DTM*090*920501 N/L
DTM*091*920531 N/L
DTM*058*920614 N/L
N1*8D*ABC COMPANY N/L
REF*PN*XXD003311 N/L
PER*CE*JOHN SMITH*TE*800/555-1212 N/L
REF*4A*22122 N/L
N1*ZD**94*6WEA N/L
LIN*1*P5*002A N/L (Discharge Number)
PID*S*08*EP*00400***PCS160 N/L (Parameter)
PID*S*12*EP*GR***PCS150 N/L (Sample Type)
PID*S*28*EP*01/30***PCS050 N/L (Frequency of Analysis)
MEA*CT**0*1N N/L (# of excursions)
CID*TR N/L
MEA*TR*CON**EA**7.6 N/L (Concentration)
LM*EP*PCS180 N/L
LQ**UN N/L
MEA*TR*CON*7.6*EA N/L
LM*EP*PCS180 N/L
LQ**UN N/L
LIN*2*P5*002A N/L (Discharge Number)
PID*S*08*EP*00556***PCS160 N/L (Parameter)
PID*S*12*EP*GR***PCS150 N/L (Sample Type)
PID*S*28*EP*01/30***PCS050 N/L (Frequency of Analysis)
MEA*CT**0*1N N/L (# of excursions)
CID*TR N/L
MEA*TR*CON**EA**0 N/L (Concentration)
LM*EP*PCS180 N/L
LQ**M1 N/L
LIN*3*P5*002A N/L (Discharge Number)
PID*S*08*EP*00680***PCS160 N/L (Parameter)
PID*S*12*EP*GR***PCS150 N/L (Sample Type)
PID*S*28*EP*01/30***PCS050 N/L (Frequency of Analysis)
MEA*CT**0*1N N/L (# of excursions)
CID*TR N/L
MEA*TR*CON**EA**28 N/L (Concentration)
LM*EP*PCS180 N/L
LQ**M1 N/L
LIN*4*P5*002A N/L (Discharge Number)
NTE*NCD*WHEN FLOWING N/L
PID*S*08*EP*50050***PCS160 N/L (Parameter)
PID*S*12*EP*ES***PCS150 N/L (Sample Type)
PID*S*28*EP*01/30***PCS050 N/L (Frequency of Analysis)
MEA*CT**0*1N N/L (# of excursions)
CID*TR N/L
MEA*TR*QUR**EA**.09 N/L (Concentration)
LM*EP*PCS180 N/L
LQ**7E N/L
MEA*TR*QUR*.09*EA N/L
LM*EP*PCS180 N/L
LQ**7E N/L
C-40
-------
DMR EDI IMPLEMENTATION GUIDELINE
SE*54*00823 N/L
GE*2*34 N/L
IEA*1*000000034 N/L
C-41
-------
DMREDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
C-42
-------
DMR EDI IMPLEMENTATION GUIDELINE
APPENDIX D
D.I PCS Error Response to Discharge Monitoring Report (842 - Nonconformance
Report)
PURPOSE: This implementation of the 842 - Nonconformance Report is used to
respond to the 863 - Report of Test Results submitted for the Discharge Monitoring
Report. It identifies errors uncovered by the Permit Compliance System (PCS) processing
and PEST validation. An 842 is not returned when the submitted data is successfully
processed.
TIMING: There are three processing steps that can result in an 842 being returned - PIN
Validation Processing, Live Edit Processing, and Update Processing. PIN Validation and
Live Edit Processing occurs daily. Update Processing occurs twice weekly.
TRANSACTION SET: ASC X12 Nonconformance Report (842), Version/Release
003050.
CONSTRUCTION: PIN violation errors are identified by the code NO - Notice in
BNR06 and an error message "Security Violation" in the NCD segment. It is the
responsibility of the recipient of the 842 to determine the exact cause of the violation. The
violation may be due to submission of an incorrect PIN, a Certifier whose name is
incorrect, or an incorrect Permit Number or any combination of the aforementioned.
Section D.3 contains an example of an 842 generated by the PIN Validation Module (see
Sample #1).
The construction of the 842 for reporting nonconformances from Live Edit Processing and
Update Processing uses the Heading or Table 1 and the Detail or Table 2 areas of the
transactions set. Nonconformance transactions reporting errrors from Live Edit
Processing are identified with the code PI - Preliminary in BNR06. Nonconformance
transactions reporting errors from Update Processing are identified with the code U5 -
Update in BNR06. Section D.3 contains an example of an 842 generated y the PCS
Processing (see Sample #2).
Two hierarchical levels are used, Parent or Component, and Child or Product
Characteristics. The parent level is used to identify the Discharge Number and the
Parameter containing the nonconformance identified by PCS. The child level is used to
identify the measurement data that conflicts with the NPDES Permit data. The Parent is
identified by the Hierarchical level code F - Component (see HL segment on page D-15).
The Child is identified by the Hierarchical level code PH - Product Characteristic (see HL
segment on page D-22).
The violation or nonconformance is identified in a NCD segment (see Page D-25). The
ISSUE DATE: 3/31/96
REVISION DATE: 1/29/97
D-l
-------
DMR EDI IMPLEMENTATION GUIDELINE
information is communicated using both the three digit PCS Nonconformance Code and
is supplemented with abbreviated text describing the violation or nonconformance. There
is one NCD Hierarchial Level for each violation or nonconformance.
NOTE: The following symbols are found in the convention:
» indicates an element is required
X indicates an element is not used
ISSUE DATE: 3/31/96
D-2 REVISION DATE: 1/29/97
-------
DMR EDI IMPLEMENTATION GUIDELINE
842 Nonconformance Report
Functional Group ID=JN Cx
Introduction:
This Draft Standard for Trial Use contains the format and establishes the data contents of the Nonconformance
Report Transaction Set (842) for use within the context of an Electronic Data Interchange (EDI) environment. The
transaction set can be used to report products and processes that do not fulfill specifications or requirements.The
Nonconformance Report Transaction Set provides the ability for the sender to report the nonconformance at the level
of detail that is required. It also provides the ability to report the specific nonconformances of a component/part
while identifying the assembly as the product that is in nonconformance. The Nonconformance Report Transaction
Set may be used to report, initiate, or request actions related to the nonconformance being reported. Financial and
accounting information is provided for reporting purposes only. The Nonconformance Report Transaction Set has the
capability to report the cause of the nonconformance and to state the proposed action to be followed to prevent a
repetition of the problem.
Heading:
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Pos.
No.
010
020
030
040
050
060
070
080
090
100
110
120
130
140
150
160
Seg.
12
ST
BNR
REF
DTM
PID
MEA
DTM
REF
PWK
REF
DTM
Nl
N2
N3
N4
REF
Name
Transaction Set Header
Beginning Segment For Nonconformance Report
Reference Numbers
Date/Time/Period
Product/Item Description
$QJj$ &!):••'$£$&, ^ v.
Measurements
Date/Time/Period
Reference Numbers
Paperwork
Reference Numbers
Date/Time/Period
OS. , "*s" %..™-
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
Rcq. Loop Notes and
PCS. Max.Use Repeat Comments
M 1
M 1
O >1
O >1
O >1
, , 5 X.V. , ,{», ssw.
O 1
O >1
O >1
O 1
O >1
O >1
O 1
O 2
O 2
O 1
O >1
D-3
-------
DMR EDI IMPLEMENTATION GUIDELINE
Not Used 170 PER
Administrative Communications Contact
O
>1
Detail:
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Pos.
No.
010
020
030
040
050
060
070
075
076
080
090
100
102
104
105
110
120
130
140
150
160
170
180
190
200
210
Seg.
Ifi
HL
LIN
PID
PRS
CID
DTM
REF
CS
AT
QTY
TMD
PSD
PWK
LM
LQ
MEA
DTM
REF
SPS
REF
PSD
MEA
DTM
REF
STA
DTM
Name
Hierarchical Level
Item Identification
Product/Item Description
Part Release Status
Characteristic/Class ID
Date/Time/Period
Reference Numbers
Contract Summary
Financial Accounting
Quantity
Test Method
Physical Sample Description
Paperwork
Code Source Information
Industry Code
§• >&•*«*•<+"* •i/aAf '* ** *fy***f'1*f
Measurements
Date/Time/Period
Reference Numbers
pcff^r ' ,„ 7"
Sampling Parameters for Summary Statistics
Reference Numbers
Physical Sample Description
>% ~ ^™ .. ^ •• *• > ../.• f ??"*
Measurements
Date/Time/Period
Reference Numbers
I&GPJMTA ^ '*~ ^j
Statistics
Date/Time/Period
Req. Loop Notes and
Des. Max.Use Repeat Comments
M 1 nl
O 1
O >1
O >1
O >1
O >1
O >1
O 1
O >1
O >1
O 1
0 1
O >1
<"» }' ' f '• f fr , f '•
0 1
M >1
-- , *" ->j 1
O 1
O >1
O >1
'"; " —*••;•-;£ ; ;
O 1
O >1
O 1
v ^ ™ ' '-<« ^ r
0 1
O >1
O >1
ov* *$•
0 1
O >1
D-4
-------
DMR EDI IMPLEMENTATION GUIDELINE
Not Used 220
REF
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
230
240
250
260
270
272
273
274
275
276
277
280
290
300
310
320
330
NCD
NTE
DTM
REF
QTY
AT
AMT
MEA
RC
EFI
BIN
Nl
N2
N3
N4
REF
PER
Not Used 333 LM
Not Used 334 LQ
Not Used 340
Not Used 350
Not Used 360
Not Used 370
Not Used 380
Not Used 390
Not Used 400
Not Used 410
Not Used 420
Not Used 430
NCA
NTE
DTM
REF
PWK
REF
DTM
Nl
N2
N3
Reference Numbers
Nonconformance Description
Note/Special Instruction
Date/Time/Period
Reference Numbers
Quantity
Financial Accounting
Monetary Amount
Measurements
Root Cause
Electronic Format Identification
Binary Data
AAA ^AWAW.^^11 *• V V.W.W A.-
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
Administrative Communications Contact
LOCSr 3U + %&&""""""
Code Source Information
Industry Code
;• — «;
Nonconformance Action
Note/Special Instruction
Date/Time/Period
Reference Numbers
Paperwork
Reference Numbers
Date/Time/Period
Name
Additional Name Information
Address Information
II
O 1
O >1
O >1
O >1
O >1
O >1
O >1
O >1
O >1
O 1
M 1
O 1
O 2
O 2
O 1
O >1
O >1
O 1
M >1
V\ VU1 yjUl1 'J
O 1
O >1
O >1
O >1
O 1
O >1
O >1
O 1
0 2
O 2
D-5
-------
D3MDR EDI IMPLEMENTATION GUIDELINE
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
Not Used
440
450
460
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
N4
REF
PER
LM
LQ
HL
LIN
PID
PRS
CID
DTM
REF
CS
AT
QTY
TMD
PSD
LM
LQ
MEA
DTM
REF
SPS
REF
PSD
MEA
DTM
REF
STA
DTM
Geographic Location
Reference Numbers
Administrative Communications Contact
lE^^l- - , — ,
Code Source Information
Industry Code
PpKflT' - ;, , ,^;\
Hierarchical Level
Item Identification
Product/Item Description
Part Release Status
Characteristic/Class ID
Date/Time/Period
Reference Numbers
Contract Summary
Financial Accounting
Quantity
Test Method
Physical Sample Description
Code Source Information
Industry Code
Measurements
Date/Time/Period .
Reference Numbers
Sampling Parameters for Summary Statistics
Reference Numbers
Physical Sample Description
Measurements
Date/Time/Period
Reference Numbers
jiSlin^TA " , ' J**""r^
?-i7 f f f jy~ 1 1 t t. f ts f: f\v.
Statistics
Date/Time/Period
0 1
O >1
O >1
*Jar£ '' V — ^. :;n. ^ V
0 1
M >1
M 1
0 1
O >1
O >1
o >i
O >1
0 >l
O 1
O 1
O >1
O 1
0 1
0 1
M >1
O 1
O . >1
O >1
0.1
O >1
0 1
0 1
O >1
. O >1
- -~ ' v^ ^ '
w % v, ^ %
0 1
O >1
D-6
-------
DMR EDI IMPLEMENTATION GUIDELINE
Not Used 491
REF
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
NotUsed
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
NCD
NTE
DTM
REF
QTY
AT
AMT
MEA
Nl
N2
N3
N4
REF
PER
LM
LQ
NCA
NTE
DTM
REF
PWK
REF
DTM
Nl
N2
N3
N4
REF
PER
Reference Numbers
tix^*%^'ry'""'''' ^ ^
V v£v.v * f •* jaiSXUOT™?"******* .. » * *
Nonconformance Description
Note/Special Instruction
Date/Time/Period '
Reference Numbers
Quantity
Financial Accounting
Monetary Amount
Measurements
IP?HI^\,,: ~s^~"'
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
Administrative Communications Contact
Code Source Information
Industry Code
.! • >• V," -f
Nonconformance Action
Note/Special Instruction
Date/Time/Period
Reference Numbers
Mm,m^----^ _
Paperwork
Reference Numbers
Date/Time/Period
$5o^J|Mg3 %s "'"'""'
Name
Additional Name Information
Address Information
Geographic Location
Reference Numbers
Administrative Communications Contact
II
-'"'"*"'; : :: ;— & „- i
, "••• r , ,,'..,
0 1
O >1
O >1
O >1
O >1
O >1
O >1
O >1
^ZT*' . .2:i :"">l™ ' \~
O 1
O 1
O 1
O 1
O >1
O >1
0 1
M >1
0 1
O >1
O >1
O >1
™J „ - ,, JH,, """" >^"" ™ --" -~,s
0 1
O >1
O >1
0 1
0 2
O 2
0 1
O >1
O >1
ua^ii*^ -„,„.'' " L^lUr "'-- ™~*r s , „ ' '
D-7
-------
DMR Et)I IMPLEMENTATION GUIDELINE
Not Used
Not Used
521
522
530
LM
LQ
SE
Code Source Information
Industry Code
Transaction Set Trailer
O
M
M
. mi
i
Transaction Set Notes
1. The HL levels are item, component, product characteristic, report, and serial number. Valid HL Parent-Child
relationships are 1) item - component, 2) item - product characteristic, 3) component - product characteristic,
4) report - item, 5) item - serial number, and 6) component - serial number.
D-8
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
PCS.
ST01
ST02
IS J. Transaction Set Header
010
Heading
Mandatory
1
To indicate the start of a transaction set and to assign a control number
1 The transaction set identifier (STO1) used by the translation routines of the
interchange partners to select the appropriate transaction set definition (e.g., 810
selects the invoice transaction set).
Data Element Summary
Data
Element Name
Attributes
M ID 3/3
143 Transaction Set Identifier Code
Code uniquely identifying a Transaction Set.
842 XI 2.21 Nonconformance Report Transaction Set
329 Transaction Set Control Number M AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Jil^l JK. Beginning Segment For Nonconformance Report
020
Heading
Mandatory
1
To indicate the beginning of a Nonconformance Report Transaction Set.
1 BNR02 is the nonconformance report identifier number.
2 BNR03 is the date that the nonconformance report was created.
3 BNR04 is the time that the nonconformance report was created.
l^^BNROSJndicates the status or intention of the Nonconformance Report
Ref.
Pes.
BNR01
BNR02
BNR03
BNR04
BNR05
BNR06
Data Element Summary
Name Attributes
Transaction Set Purpose Code M ID 2/2
Code identifying purpose of transaction set.
00 Original
127 Reference Number M AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier.
373 Date M DT 6/6
Date (YYMMDD).
' * •.„, > a", ••*•••, „ ,
337 Time O TM 4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59),
S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are
expressedjis follows: D = tenths (0-9) and DD = hundredths £00-99)
886 Nonconformance Report Status Code O ID 2/2
Code identifying the status of the nonconformance report.
OS Open, Waiting for Supplier Feedback
640 Transaction Type Code O ID 2/2
Code specifying the type of transaction.
Refer to 003050 Data Element Dictionary for acceptable code values.
D-10
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
DTM Date/Time/Period
040
Heading
Optional
>1
To specify pertinent dates and times
1 At least one of DTM02 DTM03 or DTM06 is required.
2 If either DTM06 or DTM07 is present, then the other is required.
Data Element Summary
Ref. Data
DCS. Element Name Attributes
» DTM01 374 Date/Time Qualifier M ED 3/3
Code specifying type of date or time, or both date and time.
050 Received
091 Report End
» DTM02 373 Date X DT 6/6
Date (YYMMDD).
X DTM03 337 Time X TM 4/8
Time expressed in 24-hour clock time as follows: HHMM, or HHMMSS, or
, ' , HHMMSSD, or HHMMSSDD, where H = hours (00-23), M = minutes (00-59),
S = integer seconds (00-59) and DD = decimal seconds; decimal seconds are
expressed as follows: D = tenths (0-9) and DD = hundredths (00-99) f
X DTM04 623 Time Code O ID 2/2
Code identifying the time, hi accordance with International Standards
;-.'.' Organization standard 8601, time can be specified by a + or - and an indication in
hours in relation to Universal Time Coordinate (UTC) time. Since + is a
' restricted character, + and - are substituted by P and M in the codes that follow.
Refer to 003050 Data Element Dictionary for acceptable code values.
X DTM05 624 Century O NO 2/2
... The first two characters in the designation of the year (CCYY).
X DTM06 1250 Date Time Period Format Qualifier X TD 2/3
Code indicating the date format, time format, or date and time format.
:, Refer to 003050 Data Element Dictionary for acceptable code values.
X DTM07 1251 Date Time Period X AN 1/35
Expression of a date, a time, or range of dates, times or dates and times.
D-ll
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Nl Name
120
Nl
Heading
Optional
1
To identify a party by type of organization, name and code
1 At least one of N102 or N103 is required.
2 If either N103 or N104 is present, then the other is required.
1 This segment, used alone, provides the most efficient method of providing
organizational identification. To obtain this efficiency the "ID Code" (N104) must
provide a key to the table maintained by the transaction processing party.
2 N105 and N106 further define the type of entity in N101.
•£*"* VA y^\ ^ A»^ S • Vtf£ f ' f • > • Y ft r
»
Ref.
Des.
N101
N102
N103
Data Element Summary
Data
Element Name Attributes
98 Entity Identifier Code M ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Regional Office
State
Permit Holder
93 Name X AN 1/35
12
2F
8D
Name
Free-form name.
66 Identification Code Qualifier X ID 1/2
Code designating the system/method of code structure used for Identification
Code(67).
93
Code assigned by the organization originating the
transaction set
D-12
-------
DMR EDI IMPLEMENTATION GUIDELINE
x
N104
N105
N106
67 Identification Code
Code identifying a party or other code.
X AN 2/20
706 Entity Relationship Code O ID 2/2
Code describing entity relationship.
Refer to 003050 Data Element Dictionary for acceptable code values.
98 Entity Identifier Code O ID 2/2
Code identifying an organizational entity, a physical location, or an individual
Refer to 003050 Data Element Dictionary for acceptable code values.
D-13
-------
DMR EDI IMPLERCENTATION GUIDELINE
X
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Jvlii_r Reference Numbers
160
Nl
Heading
Optional
>1
To specify identifying numbers.
1 At least one of REF02 or REF03 is required.
Ref.
PCS.
REF01
REF02
REF03
Attributes
M ID 2/2
Data Element Summary
Data
Element Name
128 Reference Number Qualifier
Code qualifying the Reference Number.
PN Permit Number
127 Reference Number X AN 1/30
Reference number or identification number as defined for a particular
Transaction Set, or as specified by the Reference Number Qualifier
ft. •fS'vlr&.+M At. **v *j 4r.>V •? j. ff " f f.f . .
352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
D-14
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Hierarchical Level
010
HL
Detail
Mandatory
1
To identify dependencies among and the content of hierarchically related groups of data
segments.
The HL Segment is used to identify levels of detail information using a Hierarchical
Structure, such as relating line item data to shipment data, and packaging data to line
item data.
HLO1 shall contain a unique alphanumeric number for each occurrence of the HL
segment in the transaction set. For example HL01 could be used to indicate the number
of occurrences of the HL segment, in which case the value of HLO 1 would be" 1" for the
initial HL segment, and would be incremented by one in each subsequent HL segment
within the transaction.
HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL
segment is subordinate.
HL03 indicates the context of the series of segments following the current HL segment
up to the next occurrence of an HL segment in the transaction. For example, HL03 is
used to indicate that subsequent segments in the HL loop form a logical grouping of data
referring to shipment, order or item level information.
HL04 indicates whether or not there are subordinate (or child) HL segments related to
the current HL segment. __
Notes:
Sxaaapte: BL»f**F*l WL
Ref.
Des.
HL01
Data
Element
628
Data Element Summary
Name Attributes
Hierarchical ID Number M AN 1/12
A unique number assigned by the sender to identify a particular data segment in a
hierarchical structure.
X
HL02
HL03
734
735
Hierarchical Parent ID Number O AN 1/12
Identification number of the next higher hierarchical data segment that the data
segment being described is subordinate to.
Hierarchical Level Code M ID 1/2
Code defining the characteristic of a level in a hierarchical structure.
F Component
HL04
736
Hierarchical Child Code O ID 1/1
Code indicating whether if there are hierarchical child data segments subordinate
to the level being described.
iD-15
-------
DMR EDI IMPLEMENTATION GUIDELINE
1 Additional Subordinate HL Data Segment in This
Hierarchical Structure.
D-16
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Li
020
HL
Det
Opl
1
To
1
2
3
4
5
6
7
8
9
10
11
12
13
14
1
1
2
LIN
Item Identification
Notes:
Ref.
DCS.
LIN01
LIN02
X
X
X
LEV03
LIN04
LINOS
LIN06
To specify basic item identification data.
If either LIN04 or LINOS is present, then the other is required.
If either LHST06 or LIN07 is present, then the other is required.
If either LINOS or LIN09 is present, then the other is required.
If either LIN10 or LDSfl 1 is present, then the other is required.
If either LDST12 or LIN13 is present, then the other is required.
If either LIN14 or LIN15 is present, then the other is required
If either LIN16 orLDSFl? is present, then the other is required.
If either LIN18 or LIN19 is present, then the other is required.
If either LIN20 or LIN21 is present, then the other is required.
If either LIN22 or LIN23 is present, then the other is required.
If either LDST24 or LIN25 is present, then the other is required.
If either LIN26 or LIN27 is present, then the other is required.
If either LIN28 or LIN29 is present, then the other is required
If either LIN30 or LIN31 is present, then the other is required.
LIN01 is the line item identification
See the Data Dictionary for a complete list of ID's.
LIN02 through LIN31 provide for fifteen (15) different product/service ID's for each
item For Example: Case, Color, Drawing No., UPC No., ISBN No., Model No., SKU.
',", ,*f w. - ' 3- -•KffifvsHr'-'-r "sv ' " -
Data Element Summary
Data
Element Name Attributes
350 Assigned Identification O AN 1/11
Alphanunieric characters assigned for differentiation witiiin a transaction set.
235 Product/Service ID Qualifier M ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
P5 Material Discharge Number
Number identifying the point where material is discharged
234 Product/Service ID M AN 1/30
Identifying number for a product or service.
235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
234 Product/Service ID O AN 1/30
Identifying number for a product or service.
235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234):
D-17
-------
DMR EDI IMPLEMENTATION GUIDELINE
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN07 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LINOS 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN09 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN10 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN11 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X IJN12 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN13 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X IIN14 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X IIN15 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN16 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN17 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X UN18 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN19 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN20 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
D-18
-------
DMR EDI IMPLEMENTATION GUIDELINE
X LEV21 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN22 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN23 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEV24 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LEV25 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LIN26 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LIN27 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LEV28 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LEV29 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
X LBV30 235 Product/Service ID Qualifier O ID 2/2
Code identifying the type/source of the descriptive number used in
Product/Service ID (234).
Refer to 003050 Data Element Dictionary for acceptable code values.
X LEV31 234 Product/Service ID O AN 1/30
Identifying number for a product or service.
D-19
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
»
Ref.
PCS.
prooi
PID02
Ju JLLJ Product/Item Description
030
HL
Detail
Optional
>1
To describe a product or process in coded or free-form format
If PID04 is present, then PID03 is required.
At least one of PID04 or PID05 is required.
If PID07 is present, then PID03 is required.
1
2
3
4 If PID08 is present, then PID03 is required.
1 Use PID03 to indicate the organization that publishes the code list being referred to.
2 PDD04 should be used for industry-specific product description codes.
3 PID08 describes the physical characteristics of the product identified in PID04. A " Y"
indicates that the specified attribute applies to this item. A ' 'N" indicates it does not
apply. Any other value is indeterminate.
1 If PDD01 = "F", then PID05 is used. If PID01 = ' ' S", then PID04 is used. If PID01 =
"X", then both PID04 and PED05 are used.
2 Use PID06 when necessary to refer to the product surface or layer being described in the
segment.
PID07 specifies the individual code list of the agency specified in PID03.
•M^,vff,v^fv^.^.:-.v.v.-.v^- .VV.V.-.V.W.W--.V--.V.-; ----- f ----------- -w - . v . v • • • ............. x - - -y - ..&.,.. v -^y^- •„ ...... -.-•.- ........... ,v s ffff f .... v. ..
SV^i— , * fttt S( ^ f ji^ff f A k VJ.WJAI. "* ' '*''
Data Element Summary
Data
Element Name
349 Item Description Type
Code indicating the format of a description.
S Structured (From Industry Code List)
Product/Process Characteristic Code O ID
Code identifying the general class of a product or process characteristic
08 Product
750
Attributes
M ID 1/1
2/3
12
28
29
Type and/or Process
s ,,,,,, •'•**'..'Yyf?.:-.
<&8f$£J08C$;{|0t»Bi|
•AW*. ..V'M.H... »^>»>^>^ f
Test Sample Frequency
Test Sample Location
PID03
Flow
88
559 Agency Qualifier Code
Code identifying the agency assigning the code values.
ro 2/2
D-20
-------
DMR EDI IMPLEMENTATION GUIDELINE
1
EP United States Environmental Protection Agency (EPA)
» PID04 751 Product Description Code X AN 1/12
A code from an industry code list which provides specific data about a product
characteristic.
X FIDOS 352 Description X AN 1/80
A free-form description to clarify the related data elements and their content.
X PID06 752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position that is being described.
» PID07 822 Source Subqualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier.
PID08 1073 Yes/No Condition or Response Code
Code indicating a Yes or No condition or response.
O ID 1/1
D-21
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
PCS.
HL01
HL02
HL03
HL04
Hierarchical Level
466
HL
Detail
Mandatory
1
To identify dependencies among and the content of hierarchically related groups of data
segments.
The HL Segment is used to identify levels of detail information using a Hierarchical
Structure, such as relating line item data to shipment data, and packaging data to line
item data.
HL01 shall contain a unique alphanumeric number for each occurrence of the HL
segment in the transaction set. For example HL01 could be used to indicate the number
of occurrences of the HL segment, in which case the value of HLO1 would be" 1" for the
initial HL segment, and would be incremented by one in each subsequent HL segment
within the transaction.
HL02 identifies the Hierarchical ID Number of the HL segment to which the current HL
segment is subordinate.
HL03 indicates the context of the series of segments following the current HL segment
up to the next occurrence of an HL segment in the transaction. For example, HL03 is
used to indicate that subsequent segments in the HL loop form a logical grouping of data
referring to shipment, order or item level information.
HL04 indicates whether or not there are subordinate (or child) HL segments related to
the current HL segment.
Data Element Summary
Data
Element Name Attributes
628 Hierarchical ID Number M AN 1/12
A unique number assigned by the sender to identify a particular data segment in a
hierarchical structure.
Hierarchical Parent ID Number O AN 1/12
Identification number of the next higher hierarchical data segment that the data
segment being described is subordinate to.
""^"
734
735 Hierarchical Level Code M ID 1/2
Code defining the characteristic of a level in a hierarchical structure.
PH
736 Hierarchical Child Code
Product Characteristic
O ID 1/1
D-22
-------
DMR EDI IMPLEMENTATION GUIDELINE
Code indicating whether if there are hierarchical child data segments subordinate
to the level being described
v
0 No Subordinate HL Segment in This Hierarchical
Structure.
D-23
-------
Nonconformance Description
492
NCD
Detail
Optional
1
To describe the nonconformance condition.
1 At least one of NCDO1 or NCD02 is required.
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Ref.
Pes.
NCD01
NCD02
X
X
NCD03
NCD04
NCD05
NCD06
NCD07
Data Element Summary
Data
Element Name Attributes
936 Measurement Attribute Code X ID 2/2
Code used to express an attribute response when a numeric measurement value
cannot be determined.
52 Nonconforming
888 Nonconformance Determination Code X ID 1/1
Code indicating whether a nonconforming condition was the reason for
submitting or the basis upon which a nonconformance report is initiated
5 Discrepant
Nonconformance resulted from deviation from acceptable
specifications or requirements
3^
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
IVJ-Jtt/A. Measurements
499
NCD
Detail
Optional
To specify physical measurements or counts, including dimensions, tolerances, variances,
Syntax Notes:
Semantic Notes:
Comments:
1
2
3
4
5
1
1
Notes:
Ref.
Des.
MEA01
MEA02
MEA03
MEA04
C00101
and weights (See Figures Appendix for example of use of COO 1.)
At least one of MEA03 MEA05 MEA06 or MEA08 is required.
If MEA05 is present, then MEA04 is required.
If MEA06 is present, then MEA04 is required.
If MEA07 is present, then at least one of MEA03 MEA05 or MEA06 is required.
Only one of MEA08 or MEA03 may be present.
MEA04 defines the unit of measure for MEA03, MEA05, and MEA06.
When citing dimensional tolerances, any measurement requiring a sign (+ or -), or any
measurement where a positive (+) value cannot be assumed use MEA05 as the negative
(-) value and MEA06 as the positive (+) value.
•*•» * 1 *••» ^- ff ffff JWff
Data Element Summary
Data
Element Name Attributes
737 Measurement Reference ID Code O ID 2/2
Code identifying the broad category to which a measurement applies
TR Test Results
Indicates that the data to follow are the results test
measurements
738 Measurement Qualifier O ID 1/3
Code identifying a specific product or process characteristic to which a
measurement applies
CON Concentration
The relative amount of a component of a sample of
product containing multiple components
Reportable Quantity
QUR
739 Measurement Value
The value of the measurement.
X R 1/10
••s.
C001 Composite Unit of Measure X
To identify a composite unit of measure (See Figures Appendix for examples of
use.)
355 Unit or Basis for Measurement Code M ID 2/2
D-25
-------
DMR EDI IMPLEMENTATION GUIDELINE
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
EA Each
X
X
X
X
X
X
X
X
X
X
X
X
X
X
C00102
C00103
C00104
C00105
C00106
C00107
C00108
C00109
C00110
C00111
C00112
C00113
C00114
C00115
MEA05
1018 Exponent
Power to which a unit is raised.
O R 1/15
O R 1/10
649 Multiplier
Value to be used as a multiplier to obtain a new value
355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003050 Data Element Dictionary for acceptable code values.
1018 Exponent ° R 1/1S
Power to which a unit is raised.
649 Multiplier OR 1/10
Value to be used as a multiplier to obtain a new value
355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003050 Data Element Dictionary for acceptable code values.
1018 Exponent ° R 1/15
Power to which a unit is raised.
649 Multiplier ° R 1/10
Value to be used as a multiplier to obtain a new value
355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003050 Data Element Dictionary for acceptable code values.
1018 Exponent ° R 1/1S
Power to which a unit is raised.
649 Multiplier ° R 1/10
Value to be used as a multiplier to obtain a new value
355 Unit or Basis for Measurement Code O ID 2/2
Code specifying the units in which a value is being expressed, or manner in
which a measurement has been taken
Refer to 003050 Data Element Dictionary for acceptable code values.
1018 Exponent ° R 1/1S
Power to which a unit is raised.
649 Multiplier ° R 1/10
Value to be used as a multiplier to obtain a new value
740 Range Minimum x R 1/10
The value specifying the minimum of the measurement range.
D-26
-------
DMR EDI IMPLEMENTATION GUIDELINE
x
MEA06
.MEA07
MEA08
MEA09
MEA10
741 Range Maximum X R
The value specifying the maximum of the measurement range.
1/10
935 Measurement Significance Code O ID 2/2
Code used to benchmark, qualify or further define a measurement value.
Refer to 003050 Data Element Dictionary for acceptable code values.
936 Measurement Attribute Code X ID 2/2
Code used to express an attribute response when a numeric measurement value
cannot be determined
Refer to 003050,D,ata Element Dictionary for acceptable code values.
752 Surface/Layer/Position Code O ID 2/2
Code indicating the product surface, layer or position that is being described.
Refer to 003050 Data Element Dictionary for acceptable code values.
1373 Measurement Method or Device O ID 2/4
The method or device used to record the measurement
Refer to Q03050 Data Element Dictionary for acceptable code values.
D-27
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Code Source Information
506
LM
Detail
Optional
1
To transmit standard code list identification information
1 LM02 identifies the applicable industry code list source information.
»
Ref.
DCS.
LM01
LM02
Attributes
M ID 2/2
Data Element Summary
Data
Element Name
559 Agency Qualifier Code
Code identifying the agency assigning the code values.
EP United States Environmental Protection Agency (EPA)
822 Source Sub qualifier O AN 1/15
A reference that indicates the table or text maintained by the Source Qualifier.
D-28
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
Notes:
Industry Code
507
LM
Detail
Mandatory
>1
Code to transmit standard industry codes
1 If LQ01 is present, then LQ02 is required.
x
Ref.
DCS.
LQ01
LQ02
Data Element Summary
Data
Element Name Attributes
1270 Code List Qualifier Code O ID 1/3
Code identifying a specific industry code list
Refer to 003050 Data Element Dictionary for acceptable code values.
1271 Industry Code x AN 1/20
Code indicating a code from a specific industry code list
D-29
-------
DMR EDI IMPLEMENTATION GUIDELINE
Segment:
Position:
Loop:
Level:
Usage:
Max Use:
Purpose:
Syntax Notes:
Semantic Notes:
Comments:
!jji< Transaction Set Trailer
530
Detail
Mandatory
To indicate the end of the transaction set and provide the count of the transmitted segments
(including the beginning (ST) and ending (SE) segments).
1 SE is the last segment of each transs
iction^set.
f
Notes:
Ref.
Pes.
SE01
SE02
Data Element Summary
Data
Element Name Attributes
96 Number of Included Segments M NO 1/10
Total number of segments included in a transaction set including ST and SE
segments.
329 Transaction Set Control Number C AN 4/9
Identifying control number that must be unique within the transaction set
functional group assigned by the originator for a transaction set
D-30
-------
PMR EPIIMPLEMENTATION GUIDELINE
D.2 Detailed Mapping
The following is a detailed mapping of an 842. It gives examples and explanations for the usage of
this transaction set.
HEADER AREA
POS SEGMENT/ELEMENT INFORMATION
DE#
010 ST*842*00001 N/L
Transaction Set Header
143 ST01 842
329 ST02 0001
Transaction Set ID Code.
842 - Nonconformance Report
Transaction Set Control Number.
020
353
BNR*00*628307*9501115*2300*OSN/L
Beginning Segment for Nonconformance Report
BNR01 05
127
373
337
886
640
040
374
373
040
374
BNR02 628307
BNR03 951015
BNR04 2300
BNR05 OS
BNR06
DTM*050*940115 N/L
Date/Time Reference
DTM01 091
DTM02 940115
DTM*091*941201 N/L
Date/Time Reference
DTM01 091
373 DTM02 941201
Transaction Set Purpose.
00 - Original
Report Number.
Date the transaction was created - October 15,1995.
Time the transaction was created -11:00 PM.
Nonconformance Report Status Code.
OS - Open, Waiting for Supplier Feedback
Transaction Type Code
Date/Time Qualifier.
050 - Received
Date the Report was received - January 15,1994
Date/Time Qualifier.
091-Report End
Date
December 1,1994
D-31
-------
DMQR. EDI IMPLEMENTATION GUIDELINE
050 DTM*091*941231 N/L
Date/Time Reference
374 DTM01 091
373 DTM02 941231
120 Nl*12*NNNN*93*codeN/L
Nl*2F*VA*93*code N/L
Name
98 N101 12
93 N102
66 N103 93
67 N104
Date/Time Qualifier.
091 -Report End
Date
December 31,1994
Entity Identifier Code.
12 - Regional Office
2F - State
Name
Regional Office or State code
Identification Code Qualifier.
93 - Code assigned by the organization originating the transaction set.
ID# assigned by the EPA.
Used when N101 = ??? (TBD)
120 N1*8D*ABC Company N/L
Name
98 N101 8D
93 N102 ABC Company
REF*PN*XXD003301 N/L
Reference Numbers
128 REF01 PN
127 REF02 XXD003301
DETAIL AREA
010 HL*1**F*1 N/L
Hierarchical Level
628 HL01 1
735 HL03 F
736 HL04 1
Entity Identifier Code.
8D - Permit Holder
Name
Submitting Company Name.
Reference Number Qualifier.
PN - Permit Number
Reference Number
NPDES permit number of the reporting site.
Hierarchical ID Number
Used to indicate the number of the occurrance of the HL segment.
the" 1" indicates the first HL segment.
Hierarchical Level Code
F - Component
Hierarchical Child Code
There is always a child hierarchical level when HL03 = F.
D-32
-------
DMR EDI IMPLEMENTATION GUIDELINE
010 LIN**P5*001AN/L
Item Identification
235 LIN02 P5
234 LIN03 001A
751
Product/Service ID. Qualifier.
P5 - Material Discharge Number.
Product/Service ID Number
Discharge Number.
030 PID*S*08*EP*NNNNN***PCS160*NN/L
Product/Item Description
349 PID01 S
750 PID02 08
559 PID03 EP
PID04 NNNNN
822 PID07 PCS 160
1073 PID08 N
Item Description Type
S - Structured from the PCS Codes and Descriptions Volume
Product/Process Characteristic Code
08 - for the PCS Parameter Code
12 - for the PCS Sample Type Code
28 - for the PCS Test Sample Frequency Code
29 - for the PCS Monitoring Location Code
88 - for the PCS No Discharge Indicator Code
Agency Qualifier Code
EP - U.S. EPA
Product Description Code
PCS Code from code table referenced in PID07.
Source Subqualifier
PCS + the appropriate code table number
PCS160 when PID02=08
PCS150whenPID02=12
PCS050 when PID02=28
PCS080 when PID02=29
PCS490 when PID02=88
Yes/No Condition or Response Code
D-33
-------
DMR EDI IMPLEMENTATION GUIDELINE
466
628
734
735
736
492
936
888
559
751
352
HL*2*1*PH*ON7L
Hierarchical Level
HL01
HL02
HL03
2
1
PH
HL04 0
Hierarchical ID Number
Hierarchical Parent ID Number
Hierarchical Level Code
PH - Product Characteristic
Hierarchical Child Code
Value is always "0" for this HL level.
NCD*52*5***EP*Errorcode*Error Message Text N/L
Nonconformance Description
NCD01 52
NCD02 5
NCD05 EP
NCD06 Errorcode
NCD07 Error Message Text
Measurement Attribute Code
52 - Nonconforming
Nonconformance Determination Code
5 - Discrepant
Agency Qualifier Code
EP - United States Environmental Protection Agency (EPA)
Product Description Code
Code corresponding to appropriate PCS Error Message
Description
Text of error message corrsponding to code in NCD06
499 MEA*TR*CON**EA**1047N/L
Measurements
737 MEA01 TR
738 MEA02 CON
739 MEA03 1047
C001 MEA04 EA
Measurement Reference ID Code.
TR-Test Results
Measurement Qualifier
CON - Concentration
Measurement Value
Composite Unit of Measure.
EA - Each
506 LM*EP*PCS180 N/L
Code Source Information
559 LM01 EP
Agency Qualifier Code
EP - United States Environmental Protection Agency
D-34
-------
J)MR EDI IMPLEMENTATION GUIDELINE
822 LM02 PCS 180
507 LQ**57
Industry Code
1271 LQ02 57
SUMMARY AREA
020 SE*58*0001 N/L
Transaction Set Trailer
96 SE01 58
329 SE02 0001
Source Subqualifier
PCS 180 - Table 180 from the PCS Codes and Descriptions Manual
Industry Code
57 - Gallons. This value is from the code table listed in LM02!
Number of Included Segments (in the
transaction).
Transaction Set Control Number. Must be the same as in ST02.
D-35
-------
DMR EDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
D-36
-------
DMR EDI IMPLEMENTATION GUIDELINE ^_^ _^__^
D.3 Sample Transmission
The following is a sample transmission of the DMR:
ISA*00* *00* *16*0579449100002P
*01*001315704T *960202*2350*U*00305*000000358*0*P*:N/L
GS*NC*DMR01*REC APPL*960202*2350*45*X*003050 N/L
ST*842*00001 N/L
BNR*00*628307*960202*2330*OS* N/L
DTM*050*960201 N/L
DTM*091*960131 N/L
N1*12*REGION 6*93*6WEA N/L
N1*8D*ABC COMPANY N/L
REF*PN*LA1234567 N/L
HL*1**F*1 N/L
LIN01**P5*001A N/L
PID*S*08*EP*04243***PCS160 N/L
PID*S*12*EP*VI***PCS150 N/L
PID*S*29*EP*1***PCS080 N/L
HL*2*1*PH N/L
NCD*52*5**EP*053*MCMN INVALID N/L
MEA*TR*CON*1047*EA N/L
LM*EP*180 N/L
LQ**1M N/L
SE*19*00001 N/L
GE*1*45 N/L
IEA*1*000000358 N/L
D-37
-------
DMR EDI IMPLEMENTATION GUIDELINE
[This page intentionally left blank.]
D-38 *U.S. GOVERNMENT PRINTING OFFICE: 1997-514-003/60604
-------
-------
------- |