EPA Moderated Transaction System (EMTS)
Flow Configuration Document
Version: LO
United States
Environmental Protection
Agency
-------
EPA Moderated Transaction System (EMTS)
Flow Configuration Document
Version: LO
Compliance and Innovative Strategies Division
Office of Transportation and Air Quality
U.S. Environmental Protection Agency
Prepared for EPA by
Perrin Quarles Associates, Inc.
SER&
United States
Environmental Protection
Agency
EPA-420-B-10-013
January 2010
-------
EMTS Flow Configuration Document
1/19/10
Table of Contents 3
1 Change Tracking Log 4
1.1 Version and Component Alignment 4
2 Introduction 5
2.1 How to Use This FCD 6
3 Submission File Structure 7
3.1 Overview 7
3.2 Implementing the Header Document 7
3.3 Header Document Structure 7
3.3.1 Namespace and Schema 8
3.3.2 Document Header Definitions 8
3.4 EMTS Namespace 11
3.5 Payload 12
3.5.1 Validating the EMTS XML 12
4 Configuring the Network Exchange 13
5 Submission Processing and Feedback 14
5.1 Submission Using a Node or Node Client 14
5.2 Submission from the EMTS Website 16
5.3 Get Submission Status 19
5.4 Obtain Transaction History 19
5.5 Obtain Document History 20
5.6 Download Document 21
6 Web Service Methods 22
6.1 Authenticate 22
6.2 Submit 22
6.3 GetStatus 23
6.4 Query 23
6.5 Download 24
Appendix A Node Options A-1
Appendix B OTAQ Registration Process B-1
B- 1 New User Registration B-1
B-2 NAAS Node Clients User Registration B-1
B-2 NAAS Full Nodes User Registration B-2
B-2 NAAS User Revocation B-3
Appendix C Procedures To Test EMTS Flow C-1
Appendix D Accessing EMTS from MyCDXWeb D-1
Appendix E Notifications for EMTS Flow E-1
Appendix F EMTS Support F-1
-------
EMTS Flow Configuration Document
1/19/10
October 12, 2009
November 18, 2009
December 23, 2009
January 11, 2010
January 15, 2010
January 18, 2010
1.0
1.0
1.0
1.0
1.0
1.0
PQA
PQA
PQA
Description
Original Draft
Updates
Updates describing the
OTAQ Registration process.
Clarification provided in
section 5 on the EMTS data
flow.
Updates for submission, and CGI
registration
Updates CGI
Updates and addition of PQA
Notification appendix.
1.1 Version and Component Alignment
The following table indicates the version of related documents and components to which this document
applies.
Component
FCD
EMTS Schema
DET
V1.0
V1.0
V1.0
-------
EMTS Flow Configuration Document
1/19/10
2 Introduction
The purpose of this Flow Configuration Document (FCD) is to describe the operation of the EMTS flow
across the Exchange Network to the CDX Node. This includes data flow between industry users and
EPA that meet the RFS submission requirements.
An FCD is intended to describe the operational aspects of an Exchange Network data exchange. The
specifications included in this document define the supported data services, the approaches, and
processes that are used to exchange information between the EPA and submitters.
This document will describe the data exchange process by which industry users will submit XML files to
the EMTS.
The EMTS intends to offer outbound services that will allow Exchange Network partners to query data
collected and managed by the EMTS. These outbound data services will be documented once these
capabilities have been designated and developed in a future release.
The scope of this document is limited to the process of submitting electronically reported EMTS
submissions to EMTS from an EPA Exchange Network 2.0 compliant node, such as the EMTS Website,
Node, or Node Client.
The high-level process for the EMTS data flow includes the following steps:
1. An EMTS-registered user authenticates to NAAS.
2. The user submits EMTS transaction data to the CDX Node using an Exchange Network 2.0 Node
or Node Client.
3. The user's NAAS credentials are mapped to the user's Web CDX credentials, which are used by
the EMTS for authentication.
4. The CDX Node validates the structure of the XML file.
5. The CDX Node submits the XML file to the EMTS.
6. The EMTS processes the contents of the file.
7. The EMTS notifies the submitter regarding the status of the submission.
As the Renewable Fuel Standards rule undergoes comments and is finalized, it is
anticipated that this FCD may undergo further revisions. The EMTS is currently in the
beta testing phase. This document will be revised when the RFS rule is final and the
EMTS flow is moved to production.
-------
EMTS Flow Configuration Document
1/19/10
2.1 How to Use This FCD
This document provides guidance on implementing and using the EMTS flow, an XML-based submission
process through the CDX Node to the EMTS.
The document includes the following main sections:
Submission File Structure
This section describes the various portions that need to be implemented in the EMTS submission file, in
addition to the EMTS XML document. The submission file must adhere to this structure in order to be
processed properly in route through the exchange network to the EMTS. The EMTS flow makes use of
the Exchange Network Header Document to describe the payload content of a Network message. Every
submission to the EMTS must adhere to the Header Document structure.
Configuring the Network Exchange
This section describes how the EMTS Network Exchange is configured for the EMTS data flow.
In addition to this FCD, the submitter should obtain the following documents related to the EMTS Flow.
These documents can be requested from EMTS Support at emts testing@PQA.com during the testing
period and emts@PQA.com during production, or by contacting the EMTS Support line at 1-800-385-
6164.
EMTS Data Exchange Template
EMTS XSD
EMTS Transaction Instructions
Submission Processing and Feedback
This section of the FCD provides a description of the EMTS flow including submitting files from a Node or
Node Client and submitting files from the EMTS website.
Web Service Methods
This section describes the web service methods utilized by the Exchange Network Node to submit to the
EMTS flow.
Help and Technical Assistance
If you have questions on how to report your transactions to the EMTS or how to use the EMTS website,
technical assistance can be provided by sending your question to emts testing@PQA.com during the
testing period and emts@PQA.com during production, or by contacting the EMTS Support line at 1-800-
385-6164.
-------
EMTS Flow Configuration Document
1/19/10
3 Submission File Structure
3.1 Overview
The EMTS submission file consists of a single XML document that can only be submitted from a Node,
Node Client, or the EMTS website. The submission must adhere to the Exchange Header v2.0 document
structure. Information on the header can be found on the Exchange Network website at
http://www.exchangenetwork.net/dev schema/HeaderSpecification v2.0.doc. The Exchange Header xsd
is available at http://www.exchangenetwork.net/schema/header/2/header v2.0.xsd.
The header document provides the following information:
Description of payload; and
Information regarding the submitter and date of submission.
3.2 Implementing the Header Document
The header is required for all Submit operations through the Exchange Network. Every submission file
sent to the EMTS must use the Header Document structure to meet EPA CDX processing requirements.
The header contains information about the submitter and the contents of the payload. The root element
of the header document is the Document element, with two child elements, Header and Payload. The
Payload contains the actual EMTS data, adhering to the structure of the EMTS schema. The figure below
shows the file submission structure.
Figure 1: Submission File Structure
Submission File (.zip)
. ;
>£f?f^
Document (.xrnl)
H
eader (xml)
Pas
/toad (EMTS)
Multiple EMTS transactions
v J
»,?.],\r
\;^f{('.'
Bi
3.3 Header Document Structure
The following table describes the Header Document attributes and how they are used for the purposes of
an EMTS submission. Note that most elements are not required to be reported in the header, these data
are used as metadata. Only the user's application user identifier will be used by the EMTS to process the
payload.
-------
EMTS Flow Configuration Document
1/19/10
3.3.1 Namespace and Schema
The XML namespace for the Exchange Network Document is
http://www.exchangenetwork.net/schema/header/2.
All documents that use the Header 2.0 specification must use this namespace URL. The schema file is
located at http://www.exchangenetwork.net/schema/header/2/header v2.0.xsd.
3.3.2 Document Header Definitions
The document header is the first child of the Document tag. The header may contain the elements and
attributes defined below:
-------
EMTS Flow Configuration Document
1/19/10
Table 1: Exchange Header 2.0 Document Attribute
of an
ID
hdrXML
Namespace
xsi XML
Namespace
Schema
Location
ion
A unique identifier for the
XML document that is the
payload. This may be a file
name or a unique
identification number that
can be used to identify the
document.
The Exchange Header 2.0
namespace. This is
different from the EMTS
namespace which is
contained in the EMTS
document.
The w3c 2001 XML schema
instance namespace.
References an XML
Schema document that has
a target namespace.
ID123456789
Yes
xmlns:hdr =
"http://www.exchangene
twork.net/schema/heade
r/2"
Yes
xmlns:xsi =
"http://www.w3.org/2001
/XMLSchema-instance"
xsi:schemaLocation =
"http://www.exchangene
twork.net/schema/heade
r/2
http://www.exchangenet
work.net/schema/header
/2/header v2.0.xsd"
Yes
No
Must be
http://www.exchan
qenetwork.net/sch
ema/header/2.
All documents that
use the Header
2.0 specification
must use this
namespace URL.
The first member
of each pair is the
namespace for
which the second
member is the hint
describing where
to find to an
appropriate
schema document.
The following table describes the Header Document elements and how they are used for the purposes of
an EMTS submission.
-------
EMTS Flow Configuration Document
1/19/10
Table 2: Exchange Header 2.0 Elements
AuthorName
Originator of the document.
This should be the name of a
person or a network node Id if
the document is automatically
generated.
Organization The organization to which the
Name author belongs. It may be a
state name, an organization
name, or a company name.
For submissions to the CDX
Node, this should be the
name of the organization.
DocumentTitle Title of the document.
John Smith
DataService
Name
Not used by EMTS.
EMTS
CreationDate This is a timestamp that
Time marks when the document,
including the payload and
header part, was created.
Keywords Description of the payload.
Multiple keywords should be
separated by commas. This
is used only for document
categorization and searching.
Comment Additional comments for
processors.
DataFlowName The name of the data flow
associated with the payload.
2006-04-05T09:30:47-
05:00
EMTS
Yes. Tag
must be
present
but null
string can
be
provided.
Yes. Tag
must be
present
but null
string can
be
provided.
Yes. Tag
must be
present
but null
string can
be
provided.
Yes
(Cannot
be
empty).
No.
Used for reference
only.
Used for reference
only.
Reference to the
flow.
Must be in valid
xsd:datetime
format.
No.
No.
No.
(cont.)
10
-------
EMTS Flow Configuration Document
1/19/10
Table 2: Exchange Header 2.0 Elements (cont.)
SenderContact
Application
Userldentifier
The sender's additional P.O. Box 1234
contact information. It can Richmond, VA
contain sender's electronic
address and/or telephone
numbers where the author
can be reached.
Application specific submitter JohnSmith
identification.
SenderAddress A well-formed URI where
results or reports can be sent.
Property Other properties of the
document using named value
pairs.
Signature An XML signature associated
with the document.
No. Element is not
used by EMTS. If
data is provided it
will be ignored.
No. The submitter may
supply his CDX
registered account
information that is
used to access
MyCDX. The CDX
user Id is the
equivalent of the
EMS user
identifier.
No. Element is not
used by the
EMTS.
No. Element is not
used by the
EMTS.
No. Element is not
used by the
EMTS.
3.4 EMTS Namespace
The EMTS namespace uses a URL to reference the location of the current version of the EMTS on the
CDX network, and allows the user to reference it through a prefix "emts:". The major version number of
the EMTS is also included in the namespace. Without this reference, all complex types and XML
elements cannot be validated resulting in an XML file validation error.
Figure 2 provides an XML example which declares the EMTS namespace through the use of the xmlns
(XML Namespace) schema attribute and assigns the namespace a prefix of "emts:"
Figure 2: Declaring the EMTS Namespace
emts:EMTS xsi:schemaLocation="http://www.exchangenetwork.net/scherna/emts/1 EMTS_EMTS_v1.0.xsd"
xmlns:emts=Mhttp://www.exchangenetwork.net/schema/emts/1" xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance">
11
-------
EMTS Flow Configuration Document
1/19/10
The declaration of the namespace is included at the top of each XML file, and allows the user to
reference the EMTS complex types and elements with the "emts:" prefix followed by a colon (as in
emts:GenerateTransactionDetail). Each complex type and XML element, including root elements, must
contain the namespace prefix.
The following XML example demonstrates an XML submission file that contains the Exchange Network
Header with an EMTS payload. This file should be zipped before it is submitted to the EMTS.
Figure 3: Header Example
2Q09-12-18TQ9 : 22 : 50CindyFerreira
<:-.dr:Payload>
CinclyFerreira
2009-12-18
1234567
Non~ester Renewable Diesel RetireC/err.ts : 3ubir.ittalCoirjr.er.tText>
65
5atcr.Vol'_ur.e>65
FuelCode>5
Assigr.ir.er.tC ode >l
RINYear>2009
Retire3easor.Cade>70
Tran3actior.DetailCoirir.entText>No comment providedc/err.ts : Irar.3actionDetailCoirjr.eritText>
3.5 Payload
The EMTS supports the inclusion of only one payload per submission file. The CDX Node will not route
submissions including more than one payload. However, a payload can contain multiple EMTS
transactions. The format of the payload must be constructed in accordance with the EMTS schema.
3.5.1 Validating the EMTS XML
Prior to transmitting any XML files to EPA, the XML document should be checked for validity. This can be
accomplished using either or both of the following:
EPA's XML schema validation tool. This web-based validation tool is a set of XML web services
for validating XML documents against the associated schemas and custom rules. This can be
found at http://tools.epacdxnode.net/.
A third party XML validation tool (e.g., XML Spy, Liquid XML, etc.) is strongly encouraged. The
validation tool must validate that an XML document is both well-formed and valid against the
EMTS schema specifications.
12
-------
EMTS Flow Configuration Document
1/19/10
There is one flow for the EMTS on the Exchange Network, and is detailed in the following table.
Table 3: Configuration of Network Exchange Parameters
Flow Name
Network Method/Parameters
Payload Schema
Header Property
Payload Operation
Payload Formatting/Structure
Payload File Naming Convention
GetStatus Responses
Timing
Authentication and User Id's
Mapping
NAAS Authorized User Accts
EMTS
Submit
Parameters
SecurityToken: A security
ticket issued by the service
provider or a trusted service
provider.
Dataflow: The name of target
dataflow: "EMTS".
Node Submission will support one
payload per document. Only one
document will be provided,
comprised of the payload.
EMTS_EMTS_v1.0.xsd
N/A
N/A
The payload must be an XML
document that is compressed as a
ZIP document type.
All standard Get Status responses.
N/A
All node users must be registered in
NAAS and their CDX user Id's must
be mapped to their NAAS Id's.
Contact the EMTS Support Desk or
Appendix B for details.
CDX must authorize Submit to
EMTS
13
-------
EMTS Flow Configuration Document
1/19/10
In order to initiate an EMTS flow submission, the user must have a CDX web account to access the
MyCDX website and have registered their organization and facilities through the OTAQ Fuel Registration
process. The user must also have a NAAS account and have permission to participate in the EMTS data
flow. Both Node Client and Full Nodes must use user NAAS accounts registered for EMTS data flow.
See Appendix B: OTAQ Registration Process, for more information on acquiring account and
permissions.
5.1 Submission Using a Node or Node Client
The following diagram and steps demonstrate how an EMTS submitter submits an XML file using a Node
or Node Client.
Figure 4: Submission from Node or Node Client
Industry
EMTS
Submitter
Node
CDX (NAAS, CDX Node, CDX Web)
rf
QA Sever
12. Return XML
Validation
Report
11. Validate
-3. Submit
-8. Response-
10. Check user
Registration -
And Approval
6. Archive
7. Generate
Transaction id
EMTS
Data Flow
OTAQ Reg
database
Validate Payload
1
17. Response-
is. Notify
9. Map NAAS user
13. Create token To CDX account
NAAS
L2. Authenticate-
CDX (EMTS)
-18. Process
-16. Queue File
EMTS Node
15. Validate-
1. The submitter logs onto their Node Client or Full Node application. Depending on the node
application, this step may or may not be required.
2. The submitter logs in to NAAS via CDX Node using his NAAS user Id. The submitter node issues
an Authentication web service to CDX Node. The following end point URLs may be used:
Test: http://testnqn.epacdxnode.net/nqn-enws20/services/NetworkNode2Service
Prod: https://cdxnodenqn.epa.qov/nqn-enws20/services/NetworkNode2Service
The submitting node passes following parameters:
- Userld: NAAS user Id
Credential: password
14
-------
EMTS Flow Configuration Document
1/19/10
Domain: "default"
Authentication Method: "Password"
On success CDX Node returns security token to the submitter node. On failure, the CDX Node
returns an Authentication SOAP Fault.
The following sequence is performed as a synchronous set of actions. If an action fails, the CDX
Node returns a failed submission response containing error information and the transaction ends.
3. The submitter node submits the XML file to the CDX Node. The following end point URLs may be
used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
The submitting node passes following parameters:
Security token: Security token received in step 2.
Transaction Id: Not used.
- Dataflow: "EMTS"
FlowOperation: Not used.
Recipient: Not used.
Documents: One document containing zipped EMTS XML document.
4. The CDX Node validates security token against NAAS. This will authenticate the submitter and
authorize the submission to the EMTS.
5. The CDX Node validates the payload. The submission payload can contain only one document.
The document must be compressed and be a ZIP document type.
6. The CDX Node archives the submitted document.
7. The CDX Node generates a unique Transaction Id and assigns a status of "PROCESSING". The
CDX Transaction Id uniquely identifies the submission, and can be used to check the status of
the submission.
8. If the previous operations were successful, the CDX Node returns a Submit response to the
submitter node with the following information:
- Transaction Id: The unique CDX Transaction Id for the submission.
- Status: PROCESSING
- StatusDetails: Your submission has been accepted and can be tracked using the following
id:[cdx transaction id].
If the previous operation fails, the CDX Node returns a SOAP Fault to the submitter node and
archives the returned transaction for further processing. See section 5.3, "Get Submission
Status", for more details on the submit web service.
The following sequence is performed asynchronously after the submit response is sent back to the
submitting node.
9. The CDX Node maps the submitter's NAAS credentials to his Web CDX credentials. The
submitter's Web CDX credentials will be submitted to the EMTS and used by the the EMTS for
submission authentication and authorization. If the mapping fails, the transaction status is set to
"FAILED" and the transaction is ended. The CDX Node will send an email to the submitter and
the CDX Node Administrator regarding the failure.
10. The CDX Node verifies that the user is registered and active in the OTAQ Registration database.
If the user is not active or not registered in the OTAQ Registration database, the transaction
status is set to "FAILED" and the transaction is ended. The CDX Node will send an email to the
submitter and the CDX Node Administrator regarding the failure.
15
-------
EMTS Flow Configuration Document
1/19/10
11. The CDX Node performs XML validation against the QA Server. The QA Server performs XML
validation asynchronously. After completion of XML validation, the QA Server submits an XML
validation report to the CDX Node. The CDX Node archives the XML validation report. This XML
validation report can be downloaded by the submitter node via download web service. See
section 5.6, "Download Document", for more details on the download web service.
12. If the XML document does not pass XML validation, the transaction status is set to "FAILED" and
the transaction is ended. The CDX Node will send an email to the submitter regarding the failure.
The email text will contain XML validation errors.
13. The CDX Node creates a security token that includes the submitter's Web CDX user Id,
submitters email address, and affiliation. This is mapped from the submitter's NAAS user Id in
step 9 above.
14. The CDX Node submits the XML file to the EMTS Node, using the security token created in step
13. The CDX Node will retry three times if the submission to EMTS node is not successful. If the
CDX Node successfully submits the document to the EMTS Node, the transaction status is set to
"PENDING". If the submission fails, the transaction status is set to "FAILED" and the transaction
is ended. The CDX Node sends an email to the submitter and the CDX Node Administrator
regarding the failure.
15. The EMTS Node validates the security token with NAAS and extracts the submitter's Web CDX
user Id from the security token.
16. The EMTS Node queues the submission for processing.
17. If steps 15-16 were successful, the EMTS Node returns the CDX Transaction Id to the CDX
Node. If the transaction has failed, the EMTS Node returns a SOAP Fault to CDX Node. The
CDX Node sets the transaction status to "FAILED" and the transaction is ended. The CDX Node
sends an email to the submitter and the CDX Node Administrator regarding the failure.
The following sequence is performed asynchronously after the submit response action in step 19.
18. The EMTS processes the submission.
19. If processing is successful, the EMTS issues a Notify request to the CDX Node, informing the
CDX Node of the final status of the submission. The CDX Node ends the transaction and
updates the transaction status to "COMPLETED". If processing failed during any of the
processing steps, the EMTS issues a Notify request to inform CDX regarding the failure. The
CDX Node ends the transaction and updates the transaction status to "FAILED". The CDX Node
sends email to the submitter regarding the outcome of the transaction.
5.2 Submission from the EMTS Website
The following diagram and steps demonstrate how an EMTS submitter submits an XML file from the
EMTS website. The EMTS website has a node client interface customized for the EMTS flow.
16
-------
EMTS Flow Configuration Document
1/19/10
Figure 5: Submission from EMTS Website
Industry
EMTS
Submitters
I.Log
CDX (CDX Web, CDX Node, NAAS)
2. Click on EMTS link-
MyCDXWeb J-*
3. Return error if unregistered user-
15. Return XML
- Validation
_. Report
QA Sever
14. Validate-
13. Check user
Registration
And Approval
S-. -A 7. Validate-
10. Archive
11. Generate
Transaction id
i8. Validate Payload
Note
EMTS
Data Flow
OTAQ Reg
database
16. Create token
-W NAAS
6. Su
CDX (EMTS)
n i4. Select XML file
EMTS Web
amit
12. Response
19. Queue File
-17. Submit-
-20. Response.
22. Notify.
EMTS Node
-18. Validate-
21. Process
1. The user logs into the MyCDX website.
2. The user clicks the OTAQEMTS:OTAQ EMTS Application link. The user's CDX credentials are
passed to the EMTS website for auto sign-on to the EMTS.
3. If the user does not have permission to operate in the EMTS website, the user is given an error
message and redirected back to the MyCDX website.
The following sequence is performed as a synchronous set of actions:
4. The user selects an XML file to submit. The File Submission interface is customized for the
EMTS data flow. The CDX Node URL, data flow name, and other submission parameters are
provided automatically by the EMTS. The EMTS verifies that the document is zipped, and that
the XML conforms to the Exchange Network Header 2.0 and EMTS xsd specifications.
5. The EMTS creates a security token that contains the user's CDX Web user Id, email address,
and affiliation.
6. The EMTS submits the XML file to the CDX Node, using the security token created in step 5.
7. The CDX Node validates the security token against NAAS, which will authenticate the submitter
and authorize the submission to the EMTS.
8. The CDX Node validates the payload. The submission payload can contain only one document.
The document must be compressed and be a ZIP document type.
9. The CDX extracts the submitter's Web CDX user Id, email address, and affiliation.
10. The CDX Node archives the submitted document.
11. The CDX Node generates unique Transaction Id and assigns the status to "PROCESSING". The
submission CDX Transaction Id uniquely identifies the submission, and can be used to check the
status of the submission.
12. If the previous operations are successful, the CDX Node returns the following Submit response to
EMTS:
Transactionld: The unique CDX Transaction Id.
Status: PROCESSING
17
-------
EMTS Flow Configuration Document
1/19/10
- StatusDetails: Your submission has been accepted and can be tracked using the following
id:[cdx transaction id]
If the previous operation fails, the CDX Node returns a SOAP Fault to the submitter node. The
submitter node archives the returned transaction for further processing. See section 5.3, "Get
Submission Status", for additional information regarding the submission status.
The following sequence is performed asynchronously after the submit response is sent back to the
EMTS.
13. The CDX Node verifies that the user is registered and active in the OTAQ Registration database.
If the user is not active or not registered in the OTAQ Registration database, the transaction
status is set to "FAILED" and the transaction is ended. The CDX Node sends email to the
submitter and the CDX Node Administrator regarding the failure.
14. The CDX Node performs XML validation against the QA Server. The QA Server performs XML
validation asynchronously. After completion, the QA Server submits an XML validation report to
the CDX Node. The CDX Node archives the XML validation report.
15. If the document did not pass XML Validation, the transaction status is set to "FAILED" and the
transaction is ended. The CDX Node will send an email to the submitter regarding the failure.
XML validation content is provided within the email.
16. The CDX Node creates a security token that includes the submitter's Web CDX user Id, email
address, and affiliation. This is extracted from the security token in step 8 above.
17. The CDX Node submits the XML file to the EMTS Node, using the security token created in step
16. The CDX Node will retry three times if submission to the EMTS Node is not successful. If the
CDX Node successfully submits the document to the EMTS Node, the transaction status is set to
"PENDING". If the submission fails, the transaction status is set to "FAILED" and the transaction
is ended. The CDX Node sends email to the submitter and the CDX Node Administrator
regarding the failure.
18. The EMTS Node validates the security token with NAAS and extracts the submitter's Web CDX
user Id from security token.
19. The EMTS Node queues the submission for processing.
20. If steps 18 - 19 are successful, the EMTS Node returns the CDX Transaction Id to the CDX
Node. If steps 18-19 fail, the EMTS Node returns a SOAP Fault to the CDX Node. The CDX
Node sets the transaction status to "FAILED" and the transaction is ended.
The following sequence is performed asynchronously after the submit response action in step 20.
21. The EMTS processes the submission.
22. If processing is successful, the EMTS issues a Notify request to the CDX Node to inform the CDX
Node regarding the final status of the submission. The CDX Node ends the transaction and
updates the status to "COMPLETED". If processing fails during any of the processing steps, the
EMTS issues a Notify request to inform the CDX Node of the failure. The CDX Node ends the
transaction and updates the status to "FAILED".
18
-------
EMTS Flow Configuration Document
1/19/10
5.3 Get Submission Status
The following steps demonstrate how the submitter node obtains the current transaction status. This
functionality is applicable to all node types (Client Nodes, Full Nodes, EMTS Node).
1. The submitter logs into NAAS using his NAAS user Id. NAAS returns a security token to the
submitter node.
2. The submitter node issues the GetStatus web service method using one of the following end
point URLs:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
The following parameters are used:
Security token: Security token returned in step 1.
Transaction Id: Transaction Id returned in section 5.1 step 8.
3. The CDX Node validates the security token against NAAS.
4. If the user was authenticated and authorized, the CDX Node returns a StatusResponse
containing status information:
Transaction Id: Passed Transaction Id.
Status: CDX Node returns any of the following statuses:
o Processing: Submission was received and steps 4-13 from section 5.1 were
successfully performed.
o Pending: Submission was successfully distributed to EMTS Node.
o Completed: Submission was received by EMTS Node and processed.
o Failed: Submission failed.
5. The submitter node archives the received information.
5.4 Obtain Transaction History
The following steps demonstrate how the submitter node can obtain the transaction history using a Query
web service. This functionality is applicable to all node types (Client Nodes, Full Nodes, EMTS Node).
1. The submitter logs into NAAS using his NAAS user Id. NAAS returns a security token to the
submitter node.
2. The submitter node issues a Query web service method using one of the following end point
URLs:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
The following parameters are used:
Security Token: Security token.
Dataflow
Request (GetTransactionHistoryByTransactionld).
Parameters: Transaction Id (Transaction Id returned by CDX Node in step 9 section 5.1).
3. The CDX Node authenticate and authorizes the submitter node user via NAAS.
4. The CDX Node returns NAAS Authentication/Authorization SOAP Fault to the submitter node if
authentication on authorization fails.
19
-------
EMTS Flow Configuration Document
1/19/10
5. The CDX Node returns a transaction history XML to the submitter node. This XML contains the
transaction and document information in the following format:
transaction xmlns="">
transaction id
Processing/Pending/Pending/Completed/Failed
EMTS
yyyy-mm-ddThh:mm:cc
document id
file name
file type
document status
6. The submitter node archives the transaction history as needed.
5.5 Obtain Document History
The following steps demonstrate how the submitter node can obtain the document history for a
transaction using a Query web service. This functionality is applicable to all node types (Client Nodes,
Full Nodes, EMTS Node).
1. The submitter logs into NAAS using his NAAS user Id. NAAS returns a security token to the
submitter node.
2. The submitter node issues a Query web service method using one of the following end point
URLs:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
The following parameters are used:
Security Token: Security token.
Dataflow
Request (GetDocuments).
Parameters:
o Transaction Id: Transaction Id returned by CDX Node in step 9 section 5.1.
o Category: Document category (SUBMISSION, VALIDATION_REPORT).
3. The CDX Node authenticates and authorizes the submitter node user via NAAS.
4. The CDX Node returns NAAS Authentication/Authorization SOAP Fault to the submitter node if
authentication/authorization failed.
20
-------
EMTS Flow Configuration Document
1/19/10
5. The CDX Node returns the document history for a submission to the submitter node. The XML
contains the Transaction Id and document information in the following format:
transction id
< Documents
document id
document name
SUBMISSION/VALIDATION_REPORT
PENDING/PROCESSED/COMPLETED/FAILED
XML/ZIP
yyyy-mm-ddThh:mm:cc
document size
< Property >
property name
property value
5.6 Download Document
The following steps demonstrate how the submitter node may download a document using the Download
web service. This functionality is applicable to all node types (Client Nodes, Full Nodes, EMTS Node).
1. The submitter logs into NAAS using his NAAS user Id. NAAS returns a security token to the
submitter node.
2. The submitter node issues a Query web service method using one of the following end point
URLs:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
The following parameters are used:
- SecurityToken: The security token received in step 1.
- Dataflow: EMTS
- Transactionld: The Transaction Id for the submission. The Transaction Id must be the same
Transaction Id issued by the CDX Node (see step 8 section 5.1.).
- Documents: An array of NodeDocumentType. When the documents parameter is empty, the
CDX Node will return all documents associated with the Transaction Id. When a Document Id
is specified in the document's parameter, the node will return only the associated document.
3. The CDX Node shall authenticate and authorize the submitter node user through NAAS.
4. The CDX Node shall return a NAAS Authentication/Authorization SOAP Fault to the submitter
node if authentication on authorization fails.
5. The CDX Node shall return the requested document(s) to the submitter node.
21
-------
EMTS Flow Configuration Document
1/19/10
6 Web Service Methods
The following section describes the web service methods utilized by an Exchange Network 2.0 Node.
Please see the Exchange Network 2.0 functional specifications for detailed information of web services.
6.1 Authenticate
The Authenticate method is used to obtain a security token from the CDX Node. This token is passed in
any subsequent method calls in the exchange between the submitting node and the CDX Node.
The following URLs may be used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
Authenticate Parameters:
Userld: The submitter's NAAS user Id.
Credential: The submitter's NAAS password.
Domain: EMTS uses "default".
Authentication Method: EMTS uses "password".
Returns:
SecurityToken: A security token used to identify the submitter.
6.2 Submit
The Submit method is used to submit an XML file to EMTS.
The following URLs may be used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
Submit Parameters:
SecurityToken: The security token issued by NAAS and returned from the Authenticate method.
This security token can be used for several submissions as long as the token has not expired.
Transaction Id: Leave empty.
Dataflow: "EMTS".
FlowOperation: Leave empty.
Recipient: Not used by EMTS.
NotificationURI: Not used by the EMTS.
Documents: An array of type nodeDocument. Each nodeDocument structure contains a single
submission file. The EMTS requires a single nodeDocument.
22
-------
EMTS Flow Configuration Document
1/19/10
Returns:
A Submit response with the following data:
Transactionld: A unique CDX Transaction Id.
Status: Text describing the submission's status ("Processing", "Pending", "Completed", or
"Failed").
StatusDetails: Additional details regarding the submission.
6.3 GetStatus
GetStatus method is used to obtain the transaction status of a submission.
The following URLs may be used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
GetStatus Parameters:
SecurityToken: The security token issued by NAAS and returned from the Authenticate method.
Transactionld: The Transaction Id issued by the CDX Node from the Submit service.
Returns:
A GetStatus response with the following data:
StatusResponseType containing following information:
o Transactionld: The Transaction Id issued by the CDX Node from the Submit service.
o Status: Text describing the submission's status ("Processing", "Pending", "Completed",
or "Failed").
o StatusDetail: Additional details on the Status description.
6.4 Query
The Query method is used to obtain transaction and document history.
The following URLs may be used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
Query Parameters:
SecurityToken: The security token issued by NAAS and returned from the Authenticate method.
Dataflow: NODE
Request: GetTransactionHistoryByTransactionld/GetDocuments.
Parameters: See sections 5.4 and 5.5 for parameters.
Returns:
The XML representing transaction or document history. See 5.4 and 5.5 for details.
23
-------
EMTS Flow Configuration Document
1/19/10
6.5 Download
The Query method is used to download document. The following documents can be downloaded:
Original Submission
XML Validation Report
The following URLs will be used:
Test: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service
Prod: https://cdxnodengn.epa.gov/ngn-enws20/services/NetworkNode2Service
Download Parameters:
SecurityToken: The security token issued by NAAS and returned from the Authenticate method.
Dataflow: EMTS
Transactionld: The Transaction Id issued by the CDX Node from the Submit service. (See step 8
section 5.1.)
Documents: An array of NodeDocumentType. When the documents parameter is empty, the
CDX Node will return all documents associated with the Transaction Id. When a Document Id is
specified in the documents parameter, the Node will return only the associated document.
Returns:
A message contains an array of zero or more NodeDocumentType.
24
-------
EMTS Flow Configuration Document: Appendix A
1/19/10
Node Options
There are several options for how to transport the XML file through the Exchange Network.
CDX Network Node: A server that facilitates the interface between database systems and the Exchange
Network. It is a partner's "point of presence" on the Exchange Network. Each partner has only one node.
Nodes support:
Server accessibility on the web;
Protocols to ensure secure exchanges;
Sending and receiving standards-based messages; and
Returning requested information as XML.
Exchange Network Web Client: EPA's site for submitting environmental information via standard web
browsers. The web client supports:
Users to submit data via web-based forms and file uploads (flat file, XML file);
Users to receive submission confirmation and processing reports;
XML for the payload;
Simple Object Access Protocol (SOAP) as a wrapper for the payload;
Web Services Description Language (WSDL) for network exchange functions and services; and
Hypertext Transfer Protocol (HTTP) for secure communication via the Internet.
EMTS Web Client: The EMTS website also supports a submittal environment which allows:
Users to submit data via file uploads (XML file only); and
XML for the payload.
A-1
-------
EMTS Flow Configuration Document: Appendix A
1/19/10
THIS PAGE INTENTIONALLY LEFT BLANK
A-2
-------
EMTS Flow Configuration Document: Appendix B
1/19/10
OTAQ Registration Process
This section describes the business processes for obtaining a CDX and NAAS account and the
permissions to participate in the EMTS flow.
B - 1 New User Registration
The following procedures are for all new users that are currently not registered with CDX.
All users must register for a CDX Web account by self-registering in the following two available
environments:
TEST: https://test.epacdx.net/
PROD: https://epacdx.net/
Once the user has acquired a CDX Web account, they are prompted to register for one or more
programs. To register for the EMTS program, the steps are as follows:
The user registers for the EMTS flow. This will automatically register the user for the OTAQ
Registration Fuels flow.
The user enters all necessary information into OTAQ Registration Fuel application.
The user prints appropriate document prior to submitting registration information and mail the
document to the address provided on the screen.
EPA will review and approve registration materials.
User will request registration with NAAS (See section B-2).
Once approved, the user will receive permissions to submit documents to the EMTS flow and
access the EMTS website.
B-2 NAAS Node Clients User Registration
Users who plan to use Node Clients to submit files must be affiliated with the CDX Node EMTS Domain.
These users will be registered and managed by CDX Node Administrator. Setting access privileges for
the EMTS flow will be managed by the CDX Node Administrator via NAAS Web Ul. The mapping
between Web CDX user Id's and NAAS user Id's will be managed by the CDX Node Administrator via
NAAS application mapping Ul.
Following procedures will be required for all the users which were not registered with CDX or registered
with CDX for other than EMTS/OTAQ REG flows and does not have NAAS EMTS user id:
1. Register with CDX Web for the EMTS flow. The user will be automatically registered for OTAQ Reg
flow. (See Appendix B-1 for details.)
2. Enter all necessary information into OTAQ Reg application.
3. The OTAQ Registration Approver reviews and approves the user.
B-1
-------
EMTS Flow Configuration Document: Appendix B
1/19/10
4. Once approved, request the Node Administrator to register with NAAS and request privileges for
accessing EMTS flow and user mapping between the NAAS and CDX Web user Id's. Provide
following information to the Node Administrator:
o Email address to receive communications from the EMTS flow associated with the user
NAAS Id;
o EMTS Web CDX user Id; and
o Application: EMTS.
5. The CDX Node Administrator will register the user with NAAS. This includes:
5.1 Creating the NAAS user Id using email provided by the user.
5.2 Activating the user.
5.3 Setting privileges for the user to be able to:
Submit EMTS data; and
Get EMTS transaction status.
5.4 Query the CDX Node for the following:
Flow: "NODE";
Services: "GetTransactionHistoryByTransactionld" and "GetDocuments";
Parameters: Any; and
Download EMTS documents.
5.5 Map the NAAS user Id to CDX Web user Id for the EMTS Application using NAAS
application mapping Ul.
5.6 Send confirmation email to the user.
For users already registered with CDX Web for the EMTS flow and who do not have NAAS user Id's, see
sections 4.4. For all users registered with CDX Web for the EMTS flow with existing NAAS user Id's see
sections 4.5.3 through 4.5.5.
B - 2 NAAS Full Nodes User Registration
Users which are using Full Node will be affiliated with this Full Node. Full Node users will be registered
by the Full Node Administrator. Setting access privileges for EMTS flow for Node users will be managed
by CDX Node Administrator. Mapping between NAAS user Id and Web CDX user Id managed by CDX
Node Administrator.
The following procedures will be required for all users which were not registered with CDX Web or
registered with CDX Web for flows other than EMTS/OTAQ REG and do not have NAAS EMTS user Id:
1. Register with CDX Web for the EMTS flow. The user will be automatically registered for OTAQ
Reg flow. (See Appendix B-1 for details.)
2. Enter all necessary information into OTAQ Reg application.
3. The OTAQ Registration Approver reviews and approves the user.
4. Once approved, request the Node Administrator to register with NAAS and request privileges for
accessing EMTS flow and user mapping between the NAAS and CDX Web user Id's. Provide
following information to the Node Administrator:
o Email address to receive communications from the EMTS flow associated with the user
NAAS Id;
o EMTS Web CDX user Id; and
o Application: EMTS.
B-2
-------
EMTS Flow Configuration Document: Appendix B
1/19/10
S.The CDX Node Administrator will register the user with NAAS. This includes:
5.1 Creating the NAAS user Id using email provided by the user.
5.2 Activating the user.
5.3 Setting privileges for the user to be able to:
Submit EMTS data; and
Get EMTS transaction status.
5.4 Query the CDX Node for the following:
Flow: "NODE";
Services: "GetTransactionHistoryByTransactionld" and "GetDocuments";
Parameters: Any; and
Download EMTS documents.
5.5 Map the NAAS user Id to CDX Web user Id for the EMTS Application using NAAS
application mapping Ul.
5.6 Send confirmation email to the user.
For all the users already registered with CDX Web for EMTS Flow and does not have NAAS user Id's,
see sections 4.4 through 4.8. For all the users registered with CDX Web for EMTS Flow with existing
NAAS user Id see sections 4.5.3 through 4.8.
B - 2 NAAS User Revocation
If the user was deactivated from OTAQ Reg Application this user privileges to access EMTS flow will be
revoked. The following describes the steps taken to revoke a users privileges.
1. The OTAQ Reg Approver will send CDX Node Administrator email to revoke user privileges
providing the user NAAS user Id.
2. The CDX Node Administrator will revoke the following user privileges:
Submit EMTS data.
Get EMTS transaction status.
Query THE CDX Node for the following:
o Flow: "NODE";
o Services: "GetTransactionHistoryByTransactionld" and "GetDocuments"; and
o Parameters: Any.
Download EMTS documents.
4. The CDX Node Administrator will email OTAQ Reg Approver upon completion of revocation.
B-3
-------
EMTS Flow Configuration Document: Appendix B
1/19/10
THIS PAGE INTENTIONALLY LEFT BLANK
B-4
-------
EMTS Flow Configuration Document: Appendix C
1/19/10
C
Procedures To Test EMTS Flow
The following describe how a user should test their connectivity to the EMTS flow. The following steps
apply to the TEST environment and not Production.
1. If the user is not registered in either CDX or the OTAQ Registration, the user will create a Web
CDX account and register their information in the OTAQ Registration application at
https://test.epacdx.net/. See Appendix B-1 for more details.
2. The user will register their NAAS credentials. See Appendix B-2 for more details.
3. The user will produce a valid EMTS XML document for submission. See section 3 for more
details.
4. The user will validate XML document via QA Server Web Ul at https://tools.epacdxnode.net/ or
using any local XML validation tool.
5. The user will submit the XML document to the CDX Node using their submitter node. The
submitter node will submit the XML document to the CDX Node. The following end point URL will
be used: http://testngn.epacdxnode.net/ngn-enws20/services/NetworkNode2Service.
6. The CDX Node will process the submission and returns Transaction Id to the submitter node.
The submitter node retains the Transaction Id for future processing. See section 5.1 for more
details.
7. The user obtains the current transaction status using submitter node. See section 5.2 for more
details.
8. The user can obtain the transaction history for the Transaction Id. See section 5.3 for more
details.
9. The user can download submission documents. See section 5.4 for more details.
C-1
-------
EMTS Flow Configuration Document: Appendix C
1/19/10
THIS PAGE INTENTIONALLY LEFT BLANK
C-2
-------
EMTS Flow Configuration Document: Appendix D
1/19/10
Accessing EMTS from MyCDX Web
This section describes how users access the EMTS website from MyCDX Web. During the EMTS beta
testing period, select users will have access to the EMTS application. Users may only access the EMTS
through a registered account profile. An example of an account profile with access to the EMTS is shown
below in figure D-1.
Figure D-1: MyCDX Account Profile
Central Data E
Welcome,
Ms. Cindy Ferreira , None
C DX R e g i strati o n Statu s : Active
x c h a n g e - MyCDX
Last Login: December21, 2009
Registered Since: November23, 2009
Recertification Date: November 23, 2009
You have 1 new message in your Inbox
Change System Edit Personal
Password Information
Available Account Profiles:
* OTAQEMTS: OTAQ EMTS Application
* OTAQ REG: Fuels Proarams Reaistration
Edit Current Add New
Account Profiles Employer Profile
The EMTS URL link will be active for all registered OTAQ Fuels Registration participants. During the beta
testing period, active beta testers will have access to the EMTS by clicking on the OTAQEMTS:OTAQ
EMTS Application link. Users that are not approved beta testers will receive an error message indicating
that you are not a registered EMTS user.
After the end of the beta testing period, all users that have registered for EMTS and Fuels and have been
approved by EPA to participate in the EMTS flow can access the EMTS website through this link. Delays
may occur for new users waiting for approval of their registration materials by EPA.
D-1
-------
EMTS Flow Configuration Document: Appendix D
1/19/10
THIS PAGE INTENTIONALLY LEFT BLANK
D-2
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Notifications for EMTS Flow
The following table outlines the notifications that are sent from either the CDX Node or the EMTS to the
submitter.
Emails Sent from the CDX Node Regarding File Submission Status
Sender
Recipient
Notification Subject Line
Content
CDX
Submitter, CDX Help
Desk
CDX Node Failure to Distribute Document
to EMTS
CDX Node failed to distribute the following
document to the EMTS.
EMTS submission with Transaction Id of: On:
Submission time:
Document name:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Submission status: FAILED.
CDX Node may be experiencing some technical
difficulties. Please resubmit your document at a
later time. Contact the CDX Help Desk at
helpdesk@epacdx.net or 1-888-890-1995, option 1
if this problem persists.
CDX
Submitter
CDX Node XML Schema Validation Failure
on EMTS Document
Document: did not pass XML
schema validation.
EMTS submission with Transaction Id of: On:
Submission time:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Submission status: FAILED.
The following XML error report is
available for download. Please check the format of
your XML document against the EMTS schema to
ensure that it is valid and well-formed before re-
submitting your file.
(cont.)
E-1
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Emails Sent from the CDX Node Regarding File Submission Status (cont.)
Sender
Recipient
Notification Subject Line
Content
CDX
Submitter
CDX is Unable to Find CDX Web User
Identification based on NAAS
Identification.
CDX Node was unable to map NAAS user Id to CDX Web user Id.
EMTS submission with Transaction Id of: On:
Submission time:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Submission status: FAILED.
Please contact the CDX Node help desk at
nodehelpdesk(5)epacdx.net to verify that your
NAAS account has been completed properly.
EMTS
CDX
EMTS has completed is processing of the
document.
EMTS submission with Transaction Id of:
Document:
Submission status: COMPLETED/FAILED.
CDX
Submitter
CDX was unable to verify that the
submitter is a registered user in
OTAQReg
CDX is unable to verify that you are a registered
user in the OTAQ Registration system with
permission to submit documents to the EMTS.
EMTS submission with Transaction Id of:
Document:
Submission time:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Submission status: FAILED
Please contact the OTAQ Registration Help desk at
FuelsProgramsReporting(5)epa.gov or 1-202-343-
9755 for assistance.
CDX
Submitter
CDX Node has completed transaction
EMTS submission with Transaction Id of:
Document:
Submission time:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Submission status: COMPLETED/FAILED
You will receive additional email from the EMTS
containing additional information regarding your
submission document.
(cont.)
E-2
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Emails Sent from the CDX Node Regarding File Submission Status (cont.)
Sender
Recipient
Notification Subject Line
Content
EMTS
All Submitters
within an
Organization
EMTS Processing Failure
The following document submitted on on behalf of organization name
(organization id)> could not be processed due to
one or more critical errors.
submitted by
To see the full error report for these files please go
to.
EMTS
All Submitters
within an
Organization
EMTS Daily Processed Document
Summary
The following files submitted on submission date>
on behalf of organization name (organization id)>
have been successfully processed:
submitted by
submitted by
The following files submitted on submission date>
on behalf of were not successfully
processed due to one or more critical errors:
submitted by
submitted by
To see the full error report for these files please go
to .
EMTS
All Submitters
within an
Organization
EMTS Notification of Pending Trades
Your organization has been named as a trading
partner of RINs for the following transactions:
You have until to accept these transactions.
To accept or deny these transactions please go to
.
(cont.)
E-3
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Emails Sent from the CDX Node Regarding File Submission Status (cont.)
Sender
Recipient
Notification Subject Line
Content
EMTS
All Submitters
within an
Organization
EMTS Summary of RIN Transactions
The following actions have been taken on account
of on :
RINs Generated: total, RINs of type
, RINs of type
RINs Separated: total, RINs of type ,
RINs of type
RINs Sold: total, RINs of type ,
RINs of type
RINs Bought: total, RINs of type ,
RINs of type
RINs Retired: total, RINs of type
, RINs of type
To see transactions performed on previous dates,
please see .
EMTS
All Submitters
within an
Organization
EMTS RINs Retired
The following RINS have been retired by
organization nameforganization id)>for
compliance year> as of :
To see a complete history of all transactions
performed to date, please see .
EMTS
All Submitters
within an
Organization
EMTS Blocked Party Trade Denied
The trade transaction initiated by
on has been denied by
due to the RINS originating from a blocked source.
EMTS
All submitters
associated with the
organization
EMTS Submission Error due to Incorrect
Business Activities
The file
submitted by contains
transactions that are not allowable for
. No data was processed for this
submission.
Please update your registered information at
to update business activities for
.
EMTS
All Submitters
within an
Organization
EMTS Submission Error due to Incorrect
User Permissions
The following user attempted to submit
transactions on behalf of , but does
not have the correct permissions to do so.
EMTS submission with Transaction Id of:
Submission time:
Document name:
Submitter NAAS user Id:
Submitter CDX Web user Id:
Please update your registered information at
FuelsProgramsReporting@epa.gov or 1-202-343-
9755 for assistance.
(cont.)
E-4
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Emails Sent from the CDX Node Regarding File Submission Status (cont.)
Sender
EMTS
EMTS
EMTS
EMTS
EMTS
EMTS
EMTS
Recipient
All Submitters
within an
Organization
All Submitters
within an
Organization
All Submitters
within an
Organization
All Submitters
within an
Organization
All Submitters
within an
Organization
All Submitters
within an
Organization
All Submitters
within an
Organization.
All Submitters
within the Trading
Partner.
Notification Subject Line
EMTS Quarterly Report
EMTS Annual Statement
EMTS Annual Statement has not been
Received
EMTS Quarterly Report has not been
Received
EMTS has Changed Status of RINs
EMTSRIN Holdings
EMTS Reminder - Outstanding Trade
Transactions
Content
The quarterly RIN Holding report has been
generated for organization name (organization
id)>. Please download this report at .
The annual RIN holding statement has been
generated for organization name (organization
id)>. Please download this report at .
The annual RIN holding statement has been
generated for . This statement must be verified and
submitted to EPA. If you have not already done so,
please download this report at .
If you do not submit this report by this may
result in the locking of organization name> RIN
Holding account.
The quarterly RIN Holdings report has been
generated for organization name (organization
id)>. This statement must be verified and
submitted to EPA. If you have not already done so,
please download this report at .
If you do not submit this report by this may
result in the locking of organization name> RIN
Holding account.
The following RINS held by organization name
(organization id)> have been locked:
locked by
The following RINS have been unlocked:
locked by
The following RINS held by organization name
(organization id)> as of are:
To see all RIN Holding details, please see .
The following trade transactions initiated by
have not been accepted:
These transactions will expire on .
(cont.)
E-5
-------
EMTS Flow Configuration Document: Appendix E
1/19/10
Emails Sent from the CDX Node Regarding File Submission Status (cont.)
Sender
Recipient
Notification Subject Line
Content
EMTS
All Submitters
within an
Organization.
All Submitters
within the Trading
Partner.
EMTS Trade Expired
The following trade transaction initiated by
:
was not completed by . This
transaction has expired.
EMTS
All submitters
associated with the
organization and all
individuals for the
trading partner
EMTS Trade Cancelled by Seller
The trade transaction initiated by
on involving the following RINs has been
cancelled by the originating party.
EMTS
All Submitters
within an
Organization.
All Submitters
within the Trading
Partner.
EMTS Trade Denied by Buyer
The trade transaction initiated by
on for the following RINS has been denied
by .
E-6
-------
EMTS Flow Configuration Document: Appendix F
1/19/10
EMTS Support
Using EMTS
EMTS Technical Support
o emts-testing@pqa.com
o 1-800-385-6164
o (Monday through Friday 9:00 a.m. until 5:00 p.m. ET)
Establishing CDX Login
CDX Helpdesk
o helpdesk@epacdx.net
o 1-888-890-1995, then select Option 1.
NAAS Authentication and Node Questions
CDX Node Support
o nodehelpdesk@epacdx.net
o 1-888-890-1995, then select Option 2.
F-1
------- |