Air Enforcement data into EPA ICIS system
Description
No description
Problem Statement
As part of the Performance Partnership Agreement with EPA, all compliance monitoring and enforcement information must be entered unto EPA’s ICIS-Air within 60 days of activity completion/determination or receipt of enforcement actions by violator. Currently, all the information for ICIS-Air are NJEMS queried using various reports generated by Office of Information Technology \[OIT] (John Smith). Previously, all data inputs were done manually by DAE and DOIT staff. To date, certain aspects of data submittals to ICIS-Air are automated using XML generating spreadsheets for Case Files, Stack Tests, TV ACCs, & updating existing spreadsheets to handle multi value fields like Air Program (MACT, TV, NSPS etc.). Automation should also include CMS workplan updates, Case Files to include HPV resolution. Further automation development needs to be completed to make data entry to ICIS-Air fully automated on a daily basis.
Project Justification
Currently, ICIS-Air upload is a monthly batch-upload process that requires several days of DOIT staff manual work, similar to ICIS-NPDES. Project scope is to develop a daily ICIS-Air flow like RCRAInfo flow for hazardous waste enforcement data.
Estimated Transactions
None
Created
14 November 2024, 14:24
Target Rollout Date
None
Target Rollout Date Reason
None
Updated
15 December 2025, 15:48
Linked work items
relates to
IPTD-201
Integrated Compliance Information System (ICIS) – Air Auto Upload
![Assignee:]()
IPTD-463
RCRAInfo Data Flow Upgrade to Schema v5.11
![Assignee:]()
IPTD-588
RCRAInfo Data Exchange with APIs instead of Node
![Assignee:]()
IPTD-558
ICIS NPDES - NJEMS Updates for Sewage Overflows - NODE BUILD OUT
![Assignee:]()
IPTD-38
ICIS NPDES – NJEMS updates for sewage overflows
![Assignee:]()
IPTD-201
Integrated Compliance Information System (ICIS) – Air Auto Upload
Completed
IPTD-463
RCRAInfo Data Flow Upgrade to Schema v5.11
Planning
IPTD-588
RCRAInfo Data Exchange with APIs instead of Node
Idea
IPTD-558
ICIS NPDES - NJEMS Updates for Sewage Overflows - NODE BUILD OUT
Research
IPTD-38
ICIS NPDES – NJEMS updates for sewage overflows
Completed
Activity
Show:
RCRAInfo Data Flow – On Hold until after 2-2026 while EPA defines the new API flow process
A 10/7 meeting with EPA surfaced a Dec 2026 end of support for the node for transferring data. Jim’s unit is aware of an intention to shift to an API approach in future. Not clear what hard deadlines may exist here. EPA’s ability or interest to insist on data at all could also be a future factor. NJDEP does not typically benefit from any of the node transfers which only satisfy EPA mandates that NJDEP has historically sought to provide in much simpler ways, such as with publicly available Dataminer reports.
downgraded to priority 6 as EPA status is in flux - not clear if EPA demands for data will be the same as historic.
Immediate data extraction process/queries being optimized by CGI (IPTD-201) under support. DOIT meeting internally to document LOE we have to take monthly to flow the data USEPA to determine ROI on whether to automate this process including costs to design/develop/test/maintain automized process.
TO Nicole 1/10/25: Hi Nicole,
After feedback from Connor and Jim, it occurred to me we might benefit from some new info, possibly a new IT sheet, but maybe a different format that can explain what has been done so far under [IPTD-201] Integrated Compliance Information System (ICIS) – which had an original IT project Sheet. And what is still needed going forward to achieve the intent of [IPTD-484] Air Enforcement data into EPA ICIS system | Exter
A previous note captured John Smith’s sentiment that at minimum he was expecting written SOP of the current process which seems part of the minimal info needed to judge how big a deal full automation may be. While Jim is wrangling with how to conceive of the next set of CGI projects, he and CGI will at some point need this kind of info to assess scope/scale here.
Holler if you have questions.
DOIT is aware of priority interest here and is evaluating whether/where things might fit in a next CGI schedule of work. Doing so effectively may call for more program input on what exactly is still happening manually and what, how and how much is expected to be automated. Connor Loftus notes there is not much documented beyond a desire for automation, and he is not certain if the past work on #201 means that prior project can be considered completed. Knute will suggest a new IT Project sheet to Nicole and program that can detail the current need and process.