Configuring violations in nCORE is a multi-step process involving entries into three lookup lists: Violation Categories, Violation Types, and Violation Types to Categories. 

The following diagram illustrates the relationship between these three lookups and how they relate to violations.

Violation Categories

Violation Categories are a way of grouping violations. 

This lookup contains three columns: Description, Program Area, and Status.

• The Description is the name of the Violation Category.

• The Program Area is the program area on the list of configured program areas to which the category is assigned. This can be left blank for violation categories which apply to multiple program areas.

• The Status is either Active or Inactive.

Example: A violation category may simply be "Agriculture Program", assigned to a program area of "Agriculture". Alternatively, a violation category may be "Storage of Infectious Waste" and be one of multiple categories assigned to the program area of "Infectious Waste".

Configuration of Violation Categories

To configure, or add, new violation categories, navigate to Admin > Lookups > Violation Categories, and click the Add New Violation Category button.

Each violation category must have a Code and a Description.

• The Code is the identifier in the SQL table. This field must be in SQL vernacular. This means it does not allow for special characters except an underscore ( _ ) and must be in all caps. A maximum of 15 characters is allowed. 

• The Description is the name that will display throughout the system.

The following additional fields are available to configure:

• Program Area - Same as above. This is the program area on the list of configured program areas that the category is assigned to. This can be left blank for violation categories that apply to multiple program areas.

• Show Sampling Tab - Makes visible the sampling tab on the violation details page. Check this box when the violation relates to media sampling results.

• Is Parameter Visible - Makes visible a drop-down box on the violation details page, allowing the user to select the media constituent (such as pH) that relates to the violation. 

Under the Integration heading, there is a field to add an EPA Violation Code. This code is used in mapping data from nCORE into EPA data systems such as RCRAInfo and ICIS-NPDES.

Violation Types

The Violation Type is the individual regulatory reference of the violation.

This lookup contains two columns: Violation Type and Regulation.

• The Violation Type is the description of the violation.

• The Regulation is the regulatory reference or stipulation. 

Example: A violation type may read "Failure of a transporter to develop a written infectious waste management plan" and the associated regulation may be "R.61-105.N.6.".

Configuration of Violation Types

To configure, or add, new violation types, navigate to Admin > Lookups > Violation Types, and click the Add New Violation Type button.

Each violation type must have a Code and a Description.

• The Code is the identifier in the SQL table. This field must be in SQL vernacular. This means it does not allow for special characters except an underscore ( _ ) and must be in all caps. A maximum of 15 characters is allowed.

• The Description is the text of the violation which will display throughout the system. 

• Optionally, a Regulation Reference may be configured. This is the regulatory reference, or stipulation.

Under the Integration heading, there is a field to add an EPA Violation Code. This code is used in mapping data from nCORE into EPA data systems such as RCRA Info and ICIS-NPDES.

Violation Types to Categories

The Violation Types to Categories lookup maps each Violation Type to a Violation Category. This is also where the nSPECT integration tag for the violation is established.

This lookup contains four columns: Violation Category, Violation Type, nSpect Tag, and Status.

• The Violation Category is a value that directly corresponds to a value in the Violation Categories lookup. 

• The Violation Type is a value that directly corresponds to a value in the Violation Types lookup. 

• The nSpect Tag is a new value created in the lookup page. The value in this column is the tag configured in nSpect inspection forms to enable auto-creation of a violation on import. This value is populated into the "Reference/Citation" field on individual questions of inspection forms. 

• The Status is either Active or Inactive.

Configuration of Violation Type to Category 

To configure, or add, new violation types, navigate to Admin > Lookups > Violation Type to Categories, and click the Add New Violation Type to Category Association button. This configuration simply requires the selection of an existing Violation Category and the selection of an existing Violation Type. These should be configured prior to adding the association. 

Additional Integration fields are available for the Violation Type: