IPTD-463
RCRAInfo Data Flow Upgrade to Schema v5.11
Description
DEP has been sending Enforcement & Inspection data to EPA’s RCRAInfo database since the mid-
2000s. The data exchange uses the Exchange Network and DEPs NODE to generate a single XML
file that is compliant with a very old v.5.1 XML Schema. The file generation and submission is
scheduled each evening and the data is automatically sent to CDX. Upon receipt, CDX conducts a
schema validation and business rule validation. CDX also sends DEP staff an email notification for
successful processing and a failure notification if errors were found. Any error will prevent the
entire submission from being processed. Human intervention is only required when a submission
contains errors. Over the years, EPA has changed the XML file schema but continues to accept files
in older schemas. The Exchange Network dataflow and XML schemas are scheduled to be retired in
December 2026. This dataflow and schemas are being replaced with new APIs and JSON file
formats. API and JSON details can be found at https://rcranodepreprod.epa.gov/rcraapi/
secured/swagger2/index.jsp#/
Initial Work Plan 205 identifies the tasks that will be performed by CGI to upgrade the RCRAInfo data
flow using the new APIs and JSON file formats for POST, PUT, GET, and DELETE. It will also
design NJDEP’s transition from NODE-based XML submissions to EPA API-based JSON
submissions. This effort aligns with IPTD-463 and incorporates new requirements from IPTD-588 in
response to EPA’s planned retirement of the RCRA NODE in December 2026.
• Facilitate Joint Application Design Sessions (JADS) to identify the requirements and draft JAD
notes.
• Draft Design document to outline the project's goals, and implementation plan, guiding
development
efforts.
Problem Statement
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
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
Draft JAD Notes
Work Plan 205 - RCRA Flow JADS & Design signed 4/15/2026. Work Plan deliverables and schedule:
IPTD-463 JADS/Design Work Plan 48 days Mon 4/27/26 Thu 7/2/26
JAD Sessions 25 days Mon 4/27/26 Fri 5/29/26
CGI Preparation for JADS 6 days Mon 4/27/26 Mon 5/4/26
CGI to Facilitate JADS 2 days Tue 5/5/26 Wed 5/6/26
Deliverable 1 - CGI to Draft JAD Notes 6 days Thu 5/7/26 Thu 5/14/26
DEP Review of JAD Notes 10 days Fri 5/15/26 Fri 5/29/26
Design 35 days Fri 5/15/26 Thu 7/2/26
Deliverable 2 - CGI to Author Draft Design Document 19 days Fri 5/15/26 Thu 6/11/26
DEP Review of Design Document 10 days Fri 6/12/26 Thu 6/25/26
Deliverable 3 - Final Document Delivered by CGI 5 days Fri 6/26/26 Thu 7/2/26
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