RCRAInfo Data Flow Upgrade to Schema v5.11
Description
No description
Problem Statement
Background:
Daily, DEP sends Enforcement & Inspection data to EPA’s RCRAInfo database since the mid-2000s via XML file format. This is an automatic process that only requirement intervention when there are errors in the file. Over the years, EPA has changed the XML file schema but continues to accept files in older schemas. DEP is still using 5.1, however EPA is up to 5.11. Ten versions ahead of DEP. This could be become urgent if EPA announces they will no longer accept the version DEP uses.
Daily, DEP sends Enforcement & Inspection data to EPA’s RCRAInfo database since the mid-2000s via XML file format. This is an automatic process that only requirement intervention when there are errors in the file. Over the years, EPA has changed the XML file schema but continues to accept files in older schemas. DEP is still using 5.1, however EPA is up to 5.11. Ten versions ahead of DEP. This could be become urgent if EPA announces they will no longer accept the version DEP uses.
Project Justification
1. RCRA CME Flow Scope
a. CM&E – Compliance Monitoring and Enforcement module – Shane did the original data flow and NJEMS schemes – schema version 5.1 was used
b. EPA is at version 5.11; hence, need to upgrade to new schema
c. May have additional data points and elements that we need to look into to identify what fields need to be added to NJEMS to flow to EPA
d. Gap analysis is needed to review what is new with V 5.11 and add those fields to NJEMS for data flow changes
e. There is no EPA deadline just yet – they will eventually stop supporting 5.1 and hence, the need to move to 5.11 accordingly
f. Effort:
i. Gap Analysis
ii. Development for NJEMS changes
iii. Flow changes
a. CM&E – Compliance Monitoring and Enforcement module – Shane did the original data flow and NJEMS schemes – schema version 5.1 was used
b. EPA is at version 5.11; hence, need to upgrade to new schema
c. May have additional data points and elements that we need to look into to identify what fields need to be added to NJEMS to flow to EPA
d. Gap analysis is needed to review what is new with V 5.11 and add those fields to NJEMS for data flow changes
e. There is no EPA deadline just yet – they will eventually stop supporting 5.1 and hence, the need to move to 5.11 accordingly
f. Effort:
i. Gap Analysis
ii. Development for NJEMS changes
iii. Flow changes
Estimated Transactions
None
Target Rollout Date
None
Target Rollout Date Reason
None
Linked work items
relates to
IPTD-484
Air Enforcement data into EPA ICIS system
![Assignee:]()
IPTD-484
Air Enforcement data into EPA ICIS system
Idea
Activity
Show:
This project has completely changed because EPA is retiring their Exchange Network node and have implemented a new API they want all states to use. Only one state expects to have something built for early next year so the schedule for this NEW project must start around March - April and will be dependent on the success of the first state. Draft CGI Work Plan 205 will be placed on-hold and reevaluated in February 2026
While the RCRA dataflow has been repaired and is running daily, the flow still needs to be upgraded to the new XML Schema.
Per 1/22/25 email from Mike Matsko - A submission file was generated and submitted to the EPA the evening of 1/21, but it failed schema validation. Error report shared with CGI for troubleshooting.
CGI continuing to work on flow issues as of 1/10/2025, with DOIT testing continuing