Delete Limit Segment Level – LMT when more than one segment exists Limit Delete, Mass Delete (one transaction for each for the parameter: ICIS Limit Tech Spec segment in the Y Base Limit parameter of the Replace (like Permit Modification Limit (PML) Parameter Limit record updated) Change) Enforcement Action (EAL) LMT (one transaction for each Edit Limit Key (update Limit(s) Start Replace (like Parameter Limit ICIS Limit Tech Spec segment in the Y and End Date) Parameter Level Change) – parameter of the limit record updated) Submit Enforcement Action with Final Order data: LTS Submit new NPDES Closed Date Formal Enforcement Change, Replace ICIS Formal Enforcement (one transaction for each Y Delete existing Closed Date Action (like Change) Action Tech Spec LS updated) Change existing NPDES Closed Date Submit Enforcement Action Milestone LTS Enforcement Action Replace (like New ICIS Enforcement Action with NPDES Closed Date (which gets (one transaction for each Y Milestone and like Change) Milestone Tech Spec copied to Final Order Closed Date) LS updated) *When submitting data via EDT that will trigger DMR violation processing, the system will evaluate the data submitted to determine how many transactions to process for each trigger. The Type Code in icis_async_transaction” column specifies the number of transactions “Source If the same dates are submitted for CTS and DMR Non-Receipt, only one row will be added to the log, otherwise, one row per trigger will be added to the log. The Asynchronous Messaging Subsystem (AMS) can be in one of two states, Started or Stopped. While in started state, the AMS starts processing the incoming Asynchronous transactions as they arrive. A stop Command Message can be sent from a Cron job before planned interruptions, such as system going into read-only mode for reporting Extraction, Transformation or Loading (ETL). Upon receiving a stop Command Message, the AMS finishes processing the current transaction and stops processing the remaining Submitted (pending) transactions. In Stopped state, the AMS consumes
Delete – Limit Segment Level when more than one segment exists for the parameter: Base Limit Permit Modification Limit (PML) Enforcement Action (EAL) Limit Delete, Mass Delete ICIS Limit Tech Spec LMT (one transaction for each segment in the parameter of the record updated) Y Parameter Limit Replace (like Change) Edit Limit Key (update Limit(s) Start and End Date) – Parameter Level Parameter Limit Replace (like Change) ICIS Limit Tech Spec LMT (one transaction for each segment in the parameter of the limit record updated) Y Submit Enforcement Action with Final Order data: Submit new NPDES Closed Date Delete existing Closed Date Change existing NPDES Closed Date Formal Enforcement Action Change, Replace (like Change) ICIS Formal Enforcement Action Tech Spec LTS (one transaction for each LS updated) Y Submit Enforcement Action Milestone with NPDES Closed Date (which gets copied to Final Order Closed Date) Enforcement Action Milestone Replace (like New and like Change) ICIS Enforcement Action Milestone Tech Spec LTS (one transaction for each LS updated) Y *When submitting data via EDT that will trigger DMR violation processing, the system will evaluate the data submitted to determine how many transactions to process for each trigger. The “Source Type Code in icis_async_transaction” column specifies the number of transactions If the same dates are submitted for CTS and DMR Non-Receipt, only one row will be added to the log, otherwise, one row per trigger will be added to the log. The Asynchronous Messaging Subsystem (AMS) can be in one of two states, Started or Stopped. While in started state, the AMS starts processing the incoming Asynchronous transactions as they arrive. A stop Command Message can be sent from a Cron job before planned interruptions, such as system going into read-only mode for reporting Extraction, Transformation or Loading (ETL). Upon receiving a stop Command Message, the AMS finishes processing the current transaction and stops processing the remaining Submitted (pending) transactions. In Stopped state, the AMS consumes
Async_Technical_Specification_v1.1.docx