Air Enforcement data into EPA ICIS system

Description

No description

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.

Linked work items

relates to
Issue Type Icon IPTD-201 Integrated Compliance Information System (ICIS) – Air Auto Upload Priority: Medium Assignee:
Completed

Activity

Knute Jensen 9 April 2025, 17:27

downgraded to priority 6 as EPA status is in flux - not clear if EPA demands for data will be the same as historic.

james bridgewater 27 January 2025, 21:17

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.

Knute Jensen 22 January 2025, 16:52

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.

Knute Jensen 10 January 2025, 20:37

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.