Frequent Questions about the Re-engineering Effort

Last updated: 3/2/2026

General

1) What is the re-engineering effort?

EPA's Industrial Processing & Power Division (IPPD) is conducting a multi-year effort to re-engineer the CAMD Business Suite of tools. In the first of two phases, EPA is re-engineering its Emissions Collection and Monitoring Plan System (ECMPS) and its data publication tool, Air Markets Program Data (AMPD). (Note: AMPD has been replaced by the new CAMPD tool. See the CAMPD section for more information.) The CAMD Business System (CBS) will be reengineered in the second phase.

2) Why is EPA re-engineering the data systems?

IPPD currently supports: 1) the ECMPS to enable industry to report data to EPA and comply with EPA’s allowance programs, 2) the AMPD tool to make data transparent and available to the public, and 3) the CBS to enable industry and EPA to carry out programmatic transactions. This effort will provide better system usability, reliability, and security, as well as new functionality to users through modern interfaces and technologies.

3) How can I learn more and find updates about progress?

We will provide project updates as appropriate via existing IPPD communications (web announcements, newsletter blasts) and this FAQ page. For system specific updates, see the questions below.

CDX Registration

1) Who should I contact if I have questions that aren’t addressed here (or general ECMPS 2.0/CBS questions)?

Contact cbs-support@camdsupport.com to open a ticket. Do not contact the CDX Help Desk for assistance related to the CDX registration process (CRK links, org ID lookups/matching, user roles) or about ECMPS 2.0/CBS. They are unfamiliar with our program applications and will likely direct you to us. Our team is happy to assist and will provide you with a quicker response.

2) When can I register for CDX and the EASEY Program Service?

Registration is occurring in phases, with the first phase involving designated representatives (DRs) or their delegates registering as initial authorizers. In mid-January 2026 we initiated phase 1 and initial authorizers were invited via email to register in CDX and create their organization IDs (org IDs) within the EASEY program service. On February 24^th, 2026, we entered phase 2 and opened registration to remaining users (alternate DRs and agents).

3) I’m the DR who is supposed to act as the initial authorizer for my organization, but I haven’t received the initial invitation. Can this be resent to me?

If an initial authorizer has not received the registration emails: 

First check spam/junk folders. 
Ask your IT team to allow messages from AskCAMD@epa.gov (sent via Constant Contact for ECMPS communications) and helpdesk@epacdx.net. 
Note: The instructions email was sent from AskCAMD@epa.gov via Constant Contact, and the unique CDX registration link was sent from helpdesk@epacdx.net (both sent in Jan 2026). Please complete the above checks before requesting a resend; otherwise, the emails may continue to be missed. 
If the emails still do not arrive, email cbs-support@camdsupport.com with the subject line “CDX Initial Authorizer Registration.” We will add the initial authorizer to our list for manual invitations.

4) I’m an initial authorizer and I’ve submitted my registration, but it says it’s pending EPA approval. What should I do next?

EPA is approving initial authorizer requests in batches, so please be patient while we get to your registration request. Once we approve your request, you will get an email confirming this with the final steps to finalize your registration. After you receive this email and complete the final steps, you will then be able to approve sponsorship requests made by others in your organizational hierarchy (i.e., alternate DRs, agents).

5) I’m an alternate DR or an agent at a facility. My DR or their delegate who will have the initial authorizer role hasn’t registered in CDX yet. Can I register for CDX while I wait for my initial authorizer to register?

No. If your facility’s initial authorizer (DR or their delegate) has not completed their CDX registration, you will not be able to request sponsorship in CDX for the EASEY program service. The initial authorizer is responsible for establishing the org ID that you will need to register for CDX. Without this org ID, you will not be properly linked in the role hierarchy and won’t have access to facility data in CBS/ECMPS when they roll out.

6) I’m an alternate DR or an agent at a facility. I haven’t received my CDX registration invitation email. Can you send it to me?

If you are not an initial authorizer (DRs or their delegates) you will not be receiving an invitation link automatically. You will need to manually request sponsorship from your organization’s initial authorizer, by following the steps in our CDX registration guide (Path 2 or Path 3). If your organization’s initial authorizer has not yet registered, reach out to them (in most cases this would be the DR) and have them follow the registration link that was sent to them via email. See question 2 if they haven’t received that invitation email.

7) Can I use an existing CDX org ID, or do I have to create a new one?

If you already belong to an org ID in CDX as you report to another program via CDX, you are welcome to use an existing org ID. Simply search for the existing org ID by number (do not type in a company name, this is notoriously unreliable and you may be adding an org that is completely unrelated to you). Org IDs in CDX are independent of one another across program services. This means that your org ID and related data in program service A does not affect your org ID and related data in program service B, and vice versa. If it is simpler for your organization to use a single org ID across all the different program services you belong to on CDX, that is great. If you’d like to have a unique program service just for EASEY, that’s great too. The most important thing is that all users in the organizational hierarchy use the same org ID when signing up for the EASEY program service (i.e., an alternate DR and agent should use the exact same org ID that the initial authorizer has within the EASEY program service).

8) I am the DR for multiple facilities. Should I create an org ID for each facility?

No. A DR should only be associated with one org ID regardless of the number of facilities they may be the DR for. Org IDs are attached to an individual, not a facility. This is why anyone associated with that DR (alt DR or agents) should use that same org ID to ensure that when accessing CBS or ECMPS, the correct facility or facilities show up for those users.

As an example: a user that is the DR at 10 facilities has the org ID 1234. Consequently, the alternate DRs and all related agents at each of the 10 facilities all use the same org ID, 1234. This means you could have 50 people at different facilities (that may even belong to different companies) using the same org ID. That is okay because they are all associated with the DR who uses that single org ID, 1234.

9) What happens if I’ve already created more than one org ID to correspond to more than one facility?

If you’ve created more than one org ID, we strongly recommend using a single one moving forward when sponsoring additional users that are brought on. You must ensure you pass along the correct org ID to whomever needs access; this is one of many reasons we do not suggest users create multiple org IDs. See question 8, above.

10) The DR/Alternate DR left our company. Does the new DR/Alternate DR need to create a new org ID to have access to the facility?

No. Once an org ID is established and associated with the DR and related users at a facility, that org ID should remain even if the original DR leaves the company. Simply have the new DR request sponsorship from the alternate DR for the Sponsor role in CDX for the EASEY program service using the existing org ID already used by the alternate DR and agents. This avoids the need to have everyone in the hierarchy re-request sponsorship under a new org ID, as all users in the hierarchy (DR, alternate DR, agents) need to have the same org ID in order for all users to have access to the necessary facility data.

11) I am an agent for many different facilities belonging to different companies. Is it okay if I request sponsorship from different DRs that all have their own unique org IDs? This would mean I have multiple org IDs under the EASEY program service – is that okay?

Yes, users can be associated with an unlimited number of org IDs within the EASEY program service. In fact, in order to have access to multiple facilities run by different DRs, you’ll need to be a part of each DR’s org ID. Remember, an org ID is associated with a person, not a facility, so if you have 10 facilities that just a single DR belongs to, you only need to add that single org ID that the DR belongs to in order to have access to all 10 facilities. But if there are multiple DRs each with their own unique IDs, you’ll need to go through the sponsorship process for each of those DRs to have those org IDs (and roles) added to your CDX profile.

12) As part of the initial authorizer (IA) registrations, a DR delegated another user to carry out the IA responsibilities. Will that person have access to facility data/information that they shouldn't have, given they have the IA role in CDX?

No. User roles in CDX are only used to establish role hierarchy and grant certain permissions within the CDX environment. CBS responsibilities are what govern access to facility data/submission capabilities on the CBS/ECMPS side. A user with an IA/sponsor role in CDX but with a more limited role in CBS like prepare agent (which cannot submit facility data), would still retain the more limited permissions based on their CBS responsibility. Users should still register for the correct role in CDX that matches their CBS responsibility to ensure users aren't granted CDX permissions they shouldn't have. If an organization wishes to revoke the IA role for a user after the initial org ID registration and initial sponsorship approval process is complete, please open a ticket with our support team (cbs-support@camdsupport.com) and we can assist. However, this is not necessary as long as the CBS responsibility remains.

ECMPS 2.0

1) What is ECMPS 2.0?

ECMPS 2.0 is the new web-based Emissions Collection and Monitoring Plan System that will replace the current ECMPS desktop application.

2) How will the new ECMPS change the way facilities report data to EPA?

The basic functionality of ECMPS will remain the same, facilities will be able to use the new web-based ECMPS 2.0 to review, edit, evaluate, and submit their monitoring plan, test data, and emissions data. IPPD is working with users and key stakeholders to implement new functionalities, enhancements, and methods of implementation while giving users a more intuitive, streamlined interface.

Because the new ECMPS 2.0 is web-based, users will no longer be required to install and update desktop ECMPS software. The data reporting file format will also change from XML to JSON (refer to the draft reporting instructions for more information).

3) Is ECMPS 2.0 available for testing?

Yes, the web-based ECMPS 2.0 is available for testing now. The Monitoring Plan functionality was initially released in December 2021. Additional functionality for the data types is available — QA, certifications, and emissions. Sign up for the ECMPS 2.0 newsletter to stay informed.

The following functionality has been released:

2021: Monitoring plan view
2022: CDX login; monitoring plan view, import/export, and evaluate; and linearity test view, import/export, and evaluate
2023: QA, certifications and exemptions, and emissions; import/export, evaluate and submit
2025: MATS data submission and configuration management

4) When am I required to use ECMPS 2.0 for reporting?

EPA is planning on releasing ECMPS 2.0 for use ahead of Q1 2026 reporting. Tentatively, we expect a release in mid-to-late March 2026 (subject to change).

5) Will EPA include the ability create Low Mass Emission (LME) monitoring method emissions files in ECMPS 2.0?

The current ECMPS 2.0 development timeline does not include plans for LME functionality within the application due to Central Data Exchange (CDX) and Cross-Media Electronic Reporting Rule (CROMERR) limitations. EPA is investigating the possibility of providing this functionality outside the application; however, EPA encourages affected sources to explore other options during this time.

6) How can I provide feedback?

If you have questions or feedback about the new ECMPS 2.0 web application, please use this form or email ecmps-beta@camdsupport.com

MATS

1) As a state, local, or regional MATS delegated permitting authority, what may MATS affected sources request to be waived from the electronic reporting requirements with respect to information required to be submitted to ECMPS beginning 1-1-2024?

Waiver requests under 40 CFR 63.10(f)(2) should be limited to the format specified by the MATS rule for the information required to be submitted to ECMPS beginning 1-1-2024. The requirement to report information to ECMPS should not be waived and electronic reporting cannot be waived according to 40 CFR 63.12(c). In addition, data elements 17-30 found in Appendix E of the MATS rule must be submitted to ECMPS in an XML format and all supporting documentation (section 31 of Appendix E) must be submitted as a PDF file. The issues detailed below do not absolve affected sources from compliance or specific data record reporting obligations. Affected sources should continue to monitor and report all data necessary for determining compliance with the rule.

The September 9, 2020, Mercury and Air Toxics Standards for Power Plants Final Electronic Reporting Revisions requires changes to MATS reporting beginning January 1, 2024.

A high-level summary of changes (i.e. additional MATS records required to be reported to ECMPS beginning 1-1-2024) is below, for exact details always refer to the 40 CFR Part 63 Subpart UUUUU itself:

For each affected unit (or group of units monitored at a common stack) using PM CEMS, HCl CEMS, or HF CEMS to measure PM, HCl, or HF hourly emissions, monitoring plan data, certification, recertification, and quality-assurance test reports shall be submitted in XML using ECMPS.
For each affected unit (or group of units monitored at a common stack) using PM CPMS to measure PM CPMS emissions, monitoring plan data, certification, recertification, and quality-assurance test reporting shall be submitted in XML using ECMPS.
30-boiler operating day rolling averages (or 90-boiler operating day rolling averages for Hg systems) for PM CEMS, approved HAP metals CEMS, PM CPMS, Hg CEMS, Hg sorbent trap systems, HCl CEMS, HF CEMS, and/or SO2 CEMS, in XML format, in the quarterly compliance reports required under 40 CFR 63.10031(g).
Quarterly compliance reports (previously semiannual compliance reports submitted in PDF format) shall now be submitted in XML format using ECMPS per 40 CFR 63.10031(f)(4), 40 CFR 63.10031(g).
For stack tests used to demonstrate compliance, RATAs, PM CEMS correlations, RRAs and RCAs that are completed on and after January 1, 2024, the applicable data elements in sections 17 through 30 of Appendix E to Subpart UUUUU of Part 63, Title 40 must be reported in an XML format. EPA has defined these data and XML reporting requirements via the Electronic Reporting Tool (ERT) and instructions. The XML and PDF files are supported in ECMPS 1.0 and must not be granted a waiver for format or otherwise. The owner, operator, or person preparing the test report can use the ERT application ERTv7 3_26_2024 (or later) to create the XML schema when a submission package is created. The owner, operator, or person preparing the test report can extract the XML schema from the ERT-created zip file for submission with the PDF file to ECMPS 1.0.

When the rule was finalized, it anticipated ECMPS 2.0 would be in production on or before the beginning of 2024 using the same XML reporting format as ECMPS 1.0, however due to development delays of ECMPS 2.0 and planned changes to reporting format (changing from XML to JSON) there is currently a mismatch between the required XML reporting formats specified in the rule and the and records available for reporting in ECMPS 1.0 (one exception, Appendix E data elements 17-30, noted above). During this interim reporting period EPA has chosen to focus resources on the development of ECMPS 2.0 and therefore has not defined an XML schema for the January 1, 2024, reporting requirements (one exception, Appendix E data elements 17-30, noted above).

With the exception of PM monitoring plan records, all of the MATS reports and records required to be reported beginning 1-1-2024 will be submitted to ECMPS using the revised MATS Data Submission module, until ECMPS 2.0 is fully developed and deployed. In the interim, after these reports and records are submitted using the MATS Data Submission module in ECMPS 1.0, they will then be transferred to the EPA WebFIRE application and will not be stored in ECMPS 1.0.

ECMPS 2.0 is being designed to store these reports and records (except for Appendix E paragraphs 17-31) in ECMPS 2.0 so that they will be publicly available with the ability to retrieve this information in a human readable format. Until ECMPS 2.0 is fully developed, reports and records submitted to ECMPS 1.0, using the MATS Data Submission module, will be transferred to WebFIRE.

EPA recommends sources work with their state, local, or regional delegated authority(s) to ensure the data are submitted in an agreed upon format. Possible format waiver requests include continuing to submit the data in PDF format. As with previous MATS PDF file submissions prior to January 1, 2024, all data submitted via the MATS data submission module will be transferred and posted to EPA’s WebFIRE application. EPA recommends that affected sources work with their delegated permitting authority(s) to ensure that any MATS reports or records required to be submitted to ECMPS beginning 1-1-2024 through the ECMPS submission process are also submitted (in a format specified by the delegated permitting authority) directly to the permitting authority if required or requested to do so. The following reports should be discussed with delegated authority to be submitted in PDF files until ECMPS 2.0 is fully developed:

For each affected unit (or group of units monitored at a common stack) using PM CEMS, HCl CEMS, and/or HF CEMS to measure PM, HCl, or HF hourly emissions, certification, recertification, and quality-assurance test reports.
For each affected unit (or group of units monitored at a common stack) using PM CPMS to measure PM CPMS emissions, monitoring plan data, certification, recertification, and quality-assurance test.
30-boiler operating day rolling averages (or 90-boiler operating day rolling averages for Hg systems) for PM CEMS, approved HAP metals CEMS, PM CPMS, Hg CEMS, Hg sorbent trap systems, HCl CEMS, HF CEMS, and/or SO2 CEMS, in XML format, in the quarterly compliance reports required under 40 CFR 63.10031(g).
Quarterly compliance reports (previously semiannual compliance reports submitted in PDF format).

Please note if any of these test reports contain methods covered in Section 17-31 of Appendix E, the XML schema does exist and can be created using the ERTv7 3_26_24 (or later) and PDF files alone will not be in compliance with the reporting requirements.

2) What PM monitoring plan data should be submitted?

The ECMPS 1.0 Monitoring plan schema and instructions have been updated to allow for MATS PM CEMS monitoring plan data submissions using ECMPS 1.0 in an XML schema. Units using PM CPMS should submit their monitoring plan via PDF using the MATS data submission module.

3) How should I submit my hourly PM data in ECMPS 1.0?

Sources should submit their hourly PM data in either XML, JSON, or PDF formats using the MATS data submission module and the Report Type Code “30-Day Rolling Averages.” Sources with questions on which format should be used for the submission of these data should contact their delegated authority(s) to ensure the data are submitted in an agreed upon format and work to ensure that these records are submitted directly to the delegated permitting authority in an agreed upon format, if requested.

4) Can Compliance tests be submitted in PDF or XML? Is PDF submittal sufficient without the XML schema?

According to 40 CFR Part 63 subpart UUUUU, Appendix E, Sections 17 to 30 data elements for performance test results, an XML schema is required and Section 31 requires a PDF file with all the supporting documentation.  ECMPS 1.0 can accept XML schema and the PDF file.  The ERTv7 3_26_24 can create the XML schema.  If you have alternative performance specification flags, those flags can be entered into the Tester DQ Assessment area and will be included in the XML schema as a comment tag. The XML schema can be found at the Electronic Reporting Tool (ERT) web page - ERT Full XML Schema(xsd).

5) How should I submit data for Sections 2-13 of Appendix E to Subpart UUUUU of Part 63, Title 40?

In anticipation of the transition to ECMPS 2.0 and the new JSON file format, EPA has not defined XML schema requirements for reporting Sections 2-13. EPA has modified the existing ECMPS 1.0 MATS data submission module to allow for the submission of PDF, XML, and JSON file formats. Sources with questions on which format should be used for the submission of these data should contact their delegated authority(s) to ensure the data are submitted in an agreed upon format and work to ensure that these records are submitted directly to the delegated permitting authority in an agreed upon format, if requested.

6) How should I submit sections 17-30 of Appendix E to Subpart UUUUU of Part 63, Title 40?

The ERT application ERTv7 3_26_2024 can be used to create the XML schema when a submission package is created. If you have alternative performance specification flags, you should put those flags into the Tester DQ Assessment Text Box of the ERT file.  The XML schema can be extracted from the ERT-created zip file for submission with the pdf (Section 31 of Appendix E) to ECMPS 1.0.  These files must be submitted using the ECMPS 1.0 MATS data submission module.  The XML schema can be found at the Electronic Reporting Tool (ERT) web page - ERT Full XML Schema(xsd).

7) Will ECMPS 1.0 be modified to accept multiple file uploads?

No, the ECMPS 1.0 MATS data submission module is limited to one file at a time. No changes can be made to this functionality. However, the MATS data submission module has been modified to allow multiple attachment types of either PDF, XML or JSON format.

8) If I have comments or questions regarding the reporting of data elements found in MATS Appendix E paragraphs 17-30, types of reports, reference methods, PDF file submissions (Appendix E paragraphs 14, 15, 16 and 31 respectively), whom should I contact and how?

For more information on the Electronic Reporting Tool (ERT), CEDRI interface or WebFIRE database please refer to the following link. For questions or comments regarding the ERT application please email Theresa Lowe at lowe.theresa@epa.gov.

CAMPD

1) How does the new CAMPD change the way data are accessed by the public?

AMPD was replaced by the Clean Air Markets Program Data (CAMPD) tool in June of 2022. The new tool can be accessed at https://campd.epa.gov. All data in AMPD is now available through CAMPD, including critical functionalities such as a custom query tool and access to prepackaged datasets. Brand new functionality including a gallery of interactive tools and REST APIs (see next question) provide additional access and context to the data. IPPD worked with users and key stakeholders to build CAMPD with a more intuitive, streamlined interface for downloading power sector emissions, allowance, compliance, and facility data.

2) Are there other ways the public can access the data?

An Application Programming Interface (API) allows a tool or service to interact with other tools or services. An API opens up data and functionality and is increasingly the way in which agencies and companies exchange data and services, both internally and externally.

The IPPD re-engineering effort uses specific type of APIs known as REST APIs. Our REST APIs, available via the Clean Air Markets Application Programming Interface (CAM API), will allow you to access Clean Air Markets Program data directly in your favorite programming language (Python, R, JavaScript, etc.). The APIs will be documented using the Open API Specification. This specification provides a way for both people and machines to discover and understand how to use the available services. If you have any questions about how you can use the CAM API in your project, send an email to campd-support@camdsupport.com or visit the CAM API portal to start exploring the APIs available.

3) Can I use my FACT or API.data.gov API key to access the CAM API?

If you have an API Key for FACT or anything on Data.gov developer network, you will be able to use the API Key to access the CAM APIs. You can sign up for a API Key here.

4) How can I provide feedback?

Please email campd-support@camdsupport.com.

« Return to the ECMPS Re-engineering page

« Return to the Data Resources page