Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Manually adding a violation to an evaluation

A violation can be manually created on an evaluation. Once the evaluation is created, navigate to the Violations tab.

...

Image Added

Once there click the Add New Violation button. Once the violation is created here, it can then be linked to compliance actions, etc.

...

Image Added

A page will show that allows the user to configure the violation. Only the violation type is required.

...

Image Added

Field

Description

Program Area

The program area to which the violation relates.

Violation Category

The category of the violation. Categories are specific to one or more program areas.

Violation Type

The type of violation. A violation type relates to one or more violation categories.

Parameter

Indicates if the violation relates to a specific sampling parameter or analyte. This field is searchable by entering search text.

Start Date

The date the violation began. This can indicate the date the violation condition actually began, or the date it was first identified

...

. It depends on how the agency chooses to use this field.

Non-Compliance End Date

The date the violation condition ended. This field can be used for different purposes depending on how an agency chooses to use it. For example, it could be used to indicate the date

...

the violation condition was addressed via a compliance or enforcement action.

Continuous Period

Indicates that the violation condition occurred on an ongoing basis between the start and end date.

Is Significant Non-compliance

Indicates whether or not the violation is significant.

Use of this checkbox is at the discretion of individual agency and/or program. Checking this box does not affect any system behavior.

On this Page

Table of Contents

Sub-Topics

Rw pagetree macro
titlePage Tree
rootPage@self


Related Content