Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Overview

The ICIS-NPDES Data View allows for staging new submissions to ICIS-NPDES and for viewing staged and historically submitted data.

Submissions Tab

Data Viewer Tab

ICIS-NPDES Flow Process Business Rules

The information below describes the behavior of a stock nVIRO implementation. The logic below may have been customized for the specific business requirements of a given agency.

Basic/General Permit flow logic:

The permit version to flow to ICIS is determined by the following criteria:

  • The permit effective date is greater than or equal to today

  • The permit version status is active (e.g. In Effect, Extended, or Expired)

  • The permit’s Permit Category is mapped to an ICIS Permit Type Code (see Permit Categories)

  • The permit number is exactly nine alpha-numeric characters long

  • The permit is version 1.0 OR the permit version is the most recent submission flowed to ICIS (as determined by the ICS_FLOW_ICIS.ICS_PRMT_REISSU SRC_SYSTM_IDENT = to the PRMT.PRMT_ID above)

Reissuance Flow Logic:

A permit will be reissued in ICIS when the following criteria are met:

  • A newer active version of the permit exists in nVIRO compared to the most recent flowed version to ICIS-NPDES (as determined by the SRC_SYSTM_IDENT equal to the PRMT.PRMT_ID of the new, active version in nVIRO, as stored in the ICS_FLOW_ICIS Basic Permit, General Permit, and Master General Permit flow tracking tables)

  • There are no flow errors for the current permit version in ICIS

  • The issue, effective, and expiration date are present

  • The permit has not already been terminated in ICIS

  • The flow payload relating to the permit type is enabled (e.g. Basic, General and Master General Permit)

Permitted Feature Flow Logic:

Permitted Features are sent in ICIS when the following criteria are met:

  • The Basic, General, or Master General Permit version has successfully flowed to ICIS

  • The feature has at least one effluent limit added to it that is valid for flowing to ICIS-NPDES (e.g. maps to a valid ICIS parameter code, etc.)

  • The feature identifier is either 3 or 4 characters long

  • The feature’s Feature Type Code has been mapped to and ICIS Permitted Feature Type code (see Feature Types).

  • No labels