**CONTENTS**

[**3.0** **ONLINE SYSTEM ADMINISTRATION
3-1**](#online-system-administration)

[3.1 Areas Served 3-2](#areas-served)

[3.1.1 Model Changes for Geographic Area
3-2](#model-changes-for-geographic-area)

[3.1.2 Geographic Area Page Flow 3-2](#geographic-area-page-flow)

[3.1.3 Model Changes for Service Area
3-14](#model-changes-for-service-area)

[3.1.4 Service Area Page Flow 3-15](#service-area-page-flow)

[3.2 User Accounts 3-21](#user-accounts)

[3.2.1 Model Changes for User Accounts
3-21](#model-changes-for-user-accounts)

[3.2.2 Maintain User Page Flow 3-21](#maintain-user-page-flow)

[3.3 Rule Authority 3-33](#rule-authority)

[3.3.1 Model Changes for Rule Authority
3-33](#model-changes-for-rule-authority)

[3.3.2 Rule Authority Page Flow 3-34](#rule-authority-page-flow)

[3.4 Analytes, Methods, and Rules 3-39](#analytes-methods-and-rules)

[3.4.1 Model Changes for Analytes 3-39](#model-changes-for-analytes)

[3.4.2 Analytes Page Flow 3-40](#analytes-page-flow)

[3.4.3 Model Changes for Analyte Groups
3-53](#model-changes-for-analyte-groups)

[3.4.4 Analyte Groups Page Flow 3-53](#analyte-groups-page-flow)

[3.4.5 Model Changes for Analyte Level
3-60](#model-changes-for-analyte-level)

[3.4.6 Analyte Level Search 3-61](#analyte-level-search)

[3.4.7 Standard Method 3-73](#standard-method)

[3.4.8 Analyte Method Pairings 3-73](#analyte-method-pairings)

[3.5 Enforcement Support 3-74](#enforcement-support)

[3.5.1 Model Changes for Action Types
3-74](#model-changes-for-action-types)

[3.5.2 Action Types Page Flows 3-74](#action-types-page-flows)

[3.5.3 Model Changes for Activity Types
3-82](#model-changes-for-activity-types)

[3.5.4 Activity Type Page Flows 3-82](#activity-type-page-flows)

[3.5.5 Model Changes for Violation Types
3-90](#model-changes-for-violation-types)

[3.5.6 Violation Type Page Flows 3-90](#violation-type-page-flows)

[3.5.7 Model Changes for Standard Responses
3-99](#model-changes-for-standard-responses)

[3.5.8 Standard Response Page Flows 3-99](#standard-response-page-flows)

[3.6 Permitted Values 3-117](#permitted-values)

[3.6.1 Model Changes for Permitted Values
3-117](#model-changes-for-permitted-values)

[3.6.2 Permitted Values Page Flows 3-118](#permitted-values-page-flows)

[3.7 Treatment 3-126](#treatment)

[3.7.1 Model Changes for Processes 3-126](#model-changes-for-processes)

[3.7.2 Processes Page Flows 3-127](#processes-page-flows)

[3.7.3 Model Changes for Pairings 3-130](#model-changes-for-pairings)

[3.7.4 Pairings Page Flows 3-130](#pairings-page-flows)

[3.8 Monitoring Periods 3-136](#monitoring-periods)

[3.8.1 Model Changes for Monitoring Periods
3-136](#model-changes-for-monitoring-periods)

[3.8.2 Monitoring Periods Page Flows
3-137](#monitoring-periods-page-flows)

[3.9 Monitoring Requirement Delete
3-146](#monitoring-requirement-delete)

[3.10 Non-TCR Schedule Template 3-148](#non-tcr-schedule-template)

[3.10.1 Model Changes for Non-TCR Schedule Template
3-149](#model-changes-for-non-tcr-schedule-template)

[3.10.2 Non-TCR Schedule Template Page Flows
3-149](#non-tcr-schedule-template-page-flows)

[3.11 SDWIS Configuration Setup 3-157](#__RefHeading___Toc139899508)

[3.11.1 Model Changes for SDWIS Configuration
3-157](#__RefHeading___Toc139899509)

[3.11.2 SDWIS Configuration Setup Page Flow
3-160](#__RefHeading___Toc139899510)

[3.12 Deficiency Types 3-163](#__RefHeading___Toc139899511)

[3.12.1 Model Changes for Deficiency Types
3-163](#__RefHeading___Toc139899512)

[3.12.2 Deficiency Type Page Flow 3-163](#deficiency-type-page-flow)

**EXHIBITS**

[**Exhibit 3-1.** SDWIS/STATE Home Page
3-2](#__RefHeading___Toc139958898)

[**Exhibit 3-2.** Geographic Area Search
3-3](#__RefHeading___Toc139958899)

[**Exhibit 3-3.** Geographic Area Maintenance List
3-6](#__RefHeading___Toc139958900)

[**Exhibit 3-4.** Geographic Area Association List
3-7](#__RefHeading___Toc139958901)

[**Exhibit 3-5.** Delete Geographic Area
3-8](#__RefHeading___Toc139958902)

[**Exhibit 3-6.** Geographic Area Maintenance
3-10](#__RefHeading___Toc139958903)

[**Exhibit 3-7.** Cancel Confirm 3-14](#__RefHeading___Toc139958904)

[**Exhibit 3-8.** Service Area Maintenance List
3-16](#__RefHeading___Toc139958905)

[**Exhibit 3-9.** Service Area Association List
3-17](#__RefHeading___Toc139958906)

[**Exhibit 3-10.** Delete Service Area
3-18](#__RefHeading___Toc139958907)

[**Exhibit 3-11.** Service Area Maintenance
3-19](#__RefHeading___Toc139958908)

[**Exhibit 3-12.** SDWIS User Maintenance List
3-22](#__RefHeading___Toc139958909)

[**Exhibit 3-13.** Government Agency Access List
3-24](#__RefHeading___Toc139958910)

[**Exhibit 3-14.** Delete User 3-25](#__RefHeading___Toc139958911)

[**Exhibit 3-15.** User Maintenance 3-27](#__RefHeading___Toc139958912)

[**Exhibit 3-16.** Government Agency Access List
3-31](#__RefHeading___Toc139958913)

[**Exhibit 3-17.** Rule Selection List
3-35](#__RefHeading___Toc139958914)

[**Exhibit 3-18.** Current Rule Association List
3-37](#__RefHeading___Toc139958915)

[**Exhibit 3-19.** Disassociate Confirmation
3-38](#__RefHeading___Toc139958916)

[**Exhibit 3-20.** Rule Details 3-39](#__RefHeading___Toc139958917)

[**Exhibit 3-21.** Analyte Search 3-40](#__RefHeading___Toc139958918)

[**Exhibit 3-22.** Analyte Maintenance List
3-42](#__RefHeading___Toc139958919)

[**Exhibit 3-23.** Analyte Delete Conflict
3-45](#__RefHeading___Toc139958920)

[**Exhibit 3-24.** Analyte Delete 3-48](#__RefHeading___Toc139958921)

[**Exhibit 3-25.** Analyte Maintenance
3-50](#__RefHeading___Toc139958922)

[**Exhibit 3-26.** Analyte Group Maintenance List
3-54](#__RefHeading___Toc139958923)

[**Exhibit 3-27.** Analyte Group Delete Confirm
3-55](#__RefHeading___Toc139958924)

[**Exhibit 3-28.** Analyte Group Maintenance
3-57](#__RefHeading___Toc139958925)

[**Exhibit 3-29.** Modify Analyte Sequence in Group
3-59](#__RefHeading___Toc139958926)

[**Exhibit 3-30.** Delete Analyte from Group Confirm
3-59](#__RefHeading___Toc139958927)

[**Exhibit 3-31.** Analyte Level Search
3-62](#__RefHeading___Toc139958928)

[**Exhibit 3-32.** Rule Selection List
3-63](#__RefHeading___Toc139958929)

[**Exhibit 3-33.** Analyte Level Maintenance List
3-65](#__RefHeading___Toc139958930)

[**Exhibit 3-34.** Delete Analyte Level
3-66](#__RefHeading___Toc139958931)

[**Exhibit 3-35.** Analyte Level Maintenance
3-68](#__RefHeading___Toc139958932)

[**Exhibit 3-36.** Analyte Level Exists
3-72](#__RefHeading___Toc139958933)

[**Exhibit 3-37.** Action Type Maintenance List
3-75](#__RefHeading___Toc139958934)

[**Exhibit 3-38.** Action Type Deletion Conflict
3-76](#__RefHeading___Toc139958935)

[**Exhibit 3-39.** Confirm Action Type Delete
3-77](#__RefHeading___Toc139958936)

[**Exhibit 3-40.** Action Type Maintenance
3-79](#__RefHeading___Toc139958937)

[**Exhibit 3-41.** Confirm Action Type Change
3-81](#__RefHeading___Toc139958938)

[**Exhibit 3-42.** Activity Type Maintenance List
3-83](#__RefHeading___Toc139958939)

[**Exhibit 3-43.** Activity Type Delete Conflict
3-84](#__RefHeading___Toc139958940)

[**Exhibit 3-44.** Alternative Activity Type Delete Conflict
3-84](#__RefHeading___Toc139958941)

[**Exhibit 3-45.** Confirm Activity Type Delete
3-85](#__RefHeading___Toc139958942)

[**Exhibit 3-46.** Activity Type Maintenance
3-87](#__RefHeading___Toc139958943)

[**Exhibit 3-47.** Confirm Activity Type Change
3-89](#__RefHeading___Toc139958944)

[**Exhibit 3-48.** Violation Type Maintenance List
3-91](#__RefHeading___Toc139958945)

[**Exhibit 3-49.** Violation Type Deletion Conflict
3-92](#__RefHeading___Toc139958946)

[**Exhibit 3-50.** Confirm Violation Type Delete
3-93](#__RefHeading___Toc139958947)

[**Exhibit 3-51.** Violation Type Maintenance
3-95](#__RefHeading___Toc139958948)

[**Exhibit 3-52.** Confirm Violation Type Change
3-98](#__RefHeading___Toc139958949)

[**Exhibit 3-53.** Standard Response Maintenance List
3-100](#__RefHeading___Toc139958950)

[**Exhibit 3-54.** Confirm Standard Response Delete
3-102](#__RefHeading___Toc139958951)

[**Exhibit 3-55.** Violation Standard Response Maintenance
3-103](#__RefHeading___Toc139958952)

[**Exhibit 3-56.** Violation Standard Response Enforcement Action Type
3-108](#__RefHeading___Toc139958953)

[**Exhibit 3-57.** Violation Standard Response PN Schedule Activity
Types 3-110](#__RefHeading___Toc139958954)

[**Exhibit 3-58.** Deficiency Standard Response Maintenance
3-112](#__RefHeading___Toc139958955)

[**Exhibit 3-59.** Deficiency Standard Response Activity Types
3-116](#__RefHeading___Toc139958956)

[**Exhibit 3-60.** Permitted Value Code Search
3-118](#__RefHeading___Toc139958957)

[**Exhibit 3-61.** Code Selection List
3-120](#__RefHeading___Toc139958958)

[**Exhibit 3-62.** Code Permitted Value Maintenance List
3-122](#__RefHeading___Toc139958959)

[**Exhibit 3-63.** Permitted Value Maintenance
3-124](#__RefHeading___Toc139958960)

[**Exhibit 3-64.** Referenced Permitted Value Change Confirmation
3-126](#__RefHeading___Toc139958961)

[**Exhibit 3-65.** Treatment Process Maintenance List
3-127](#__RefHeading___Toc139958962)

[**Exhibit 3-66.** Treatment Process Delete Confirmation
3-128](#__RefHeading___Toc139958963)

[**Exhibit 3-67.** Treatment Process Maintenance
3-129](#__RefHeading___Toc139958964)

[**Exhibit 3-68.** Treatment Objective Process Pairing Maintenance List
3-132](#__RefHeading___Toc139958965)

[**Exhibit 3-69.** Delete Treatment Objective Process Pairing
3-133](#__RefHeading___Toc139958966)

[**Exhibit 3-70.** Treatment Objective Process Pairing
3-136](#__RefHeading___Toc139958967)

[**Exhibit 3-71.** Monitoring Period Search
3-138](#__RefHeading___Toc139958968)

[**Exhibit 3-72.** Monitoring Period Maintenance List
3-139](#__RefHeading___Toc139958969)

[**Exhibit 3-73.** Monitoring Period Association List
3-141](#__RefHeading___Toc139958970)

[**Exhibit 3-74.** Delete Monitoring Period Confirmation
3-142](#__RefHeading___Toc139958971)

[**Exhibit 3-75.** Monitoring Period Maintenance
3-143](#__RefHeading___Toc139958972)

[**Exhibit 3-76.** Cancel Confirm 3-146](#__RefHeading___Toc139958973)

[**Exhibit 3-77.** Monitoring Requirement Delete Confirmation
3-148](#__RefHeading___Toc139958974)

[**Exhibit 3-78.** Non-TCR Schedule Template Maintenance List
3-149](#__RefHeading___Toc139958975)

[**Exhibit 3-79.** Non-TCR Schedule Template Maintenance
3-151](#__RefHeading___Toc139958976)

[**Exhibit 3-80.** SDWIS Configuration Setup
3-161](#__RefHeading___Toc139958977)

[**Exhibit 3-81.** Deficiency Type Maintenance List
3-164](#__RefHeading___Toc139958978)

[**Exhibit 3-82.** Deficiency Type Maintenance
3-166](#__RefHeading___Toc139958979)

# ONLINE SYSTEM ADMINISTRATION

The *System Administration* component enables the state's SDWIS/STATE
Administrator to establish users and to maintain reference tables that
are used to verify data entry. Only users with System Administrator
authority can make additions or changes to data maintained in this
component. The menu items available under the *SDWIS/STATE Home Page
System Administration* (Exhibit 3-1) will be:

> Areas Served
>
> User Accounts
>
> Rule Authority
>
> Analytes and Rules
>
> Enforcement Support
>
> Permitted Values
>
> Treatment
>
> SDWIS Configuration Setup
>
> Compliance Support

  ---------------------------------------------------- ---------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image2.png){width="3.995138888888889in"
  height="4.909027777777778in"}                        height="3.053472222222222in"}

  ---------------------------------------------------- ---------------------------------------------------

[]{#__RefHeading___Toc139958898 .anchor}**Exhibit 3-1.** SDWIS/STATE
Home Page

## Areas Served

Areas Served are created in the database to represent a variety of
geographic and service areas throughout a state in which water systems
reside or provide service. There are two menu items available under
**Areas Served**: **Geographic** and **Service Areas**.

### Model Changes for Geographic Area 

No model changes are planned for this release.

### Geographic Area Page Flow 

When the user selects **Geographic Area** from *the SDWIS/STATE Home
Page* *System Administration* menu item, the Geographic Area Search page
(Exhibit 3-2) will be presented, where the user may specify any search
criteria.

####  Geographic Area Search

Exhibit 3-2 depicts the Geographic Area Search page.

  ---------------------------------------------------- ---------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image3.png){width="4.122916666666667in"
  height="4.909027777777778in"}                        height="3.625in"}

  ---------------------------------------------------- ---------------------------------------------------

[]{#__RefHeading___Toc139958899 .anchor}**Exhibit 3-2.** Geographic Area
Search

[Entry Fields:]{.underline}

Starting Criteria Group Box:

*\[Geographic Area\]*

*Name* The name of the geographic area. The entry can be a partial or
full name of the geographic area. It can be combined with the geographic
area Type Code for further filtration.

> The *Name* field will be optional.

Filtering Criteria Group Box:

*\[Geographic Area\]*

*Type Code* The type code of the geographic area. To filter, the user
can select one type code from the dropdown list or can select "Display
All" for all type codes to be displayed. This field can be used as a
filter criterion to limit the search or it can be combined with the
geographic area Name.

In circumstances where the search has been invoked as the result of a
**Go To** button or other selection list function, the Type Code field
may be pre-selected and protected from input. An example is when the
selection is searching for a county to associate as the principal county
for the geographic area. In this situation the Type Code would be
pre-selected as COUNTY and protected from change.

The selections available in the dropdown list are:

> \*Display All Types\* (default value)
>
> ARV - Alaskan Remote Village
>
> CS - Census Tract
>
> CT - City
>
> CD - Congress District
>
> CN - County
>
> DS - District
>
> FA - Franchise Area
>
> HU - Hydrologic Unit
>
> IR - Indian Reservation
>
> MSA - Metropolitan Statistical Area
>
> NRD - Natural Resource District
>
> RG - Region
>
> SHD - State House District
>
> SS - State Senate District
>
> ST - State
>
> SD - Subdivision
>
> TW - Township
>
> UA - Unincorporated Area
>
> WD - Water District
>
> The Type Code field will be optional.

[Tab Sequence:]{.underline}

\[Geographic Area\] Name, \[Geographic Area\] Type Code, **Search**,
**Cancel**, and **Help**.

[Buttons:]{.underline}

**Search** Will initiate a search of the database for geographic area
data matching the search criteria in the Name field and restricted by
the Type Code. The results will be displayed on the

> Geographic Area Maintenance List (Exhibit 3-3).
>
> When only Name is provided, the search will result in Geographic Areas
> with names matching or greater than the criteria supplied.
>
> When only Type Code is selected, the search will result in Geographic
> Areas with type codes matching the criteria supplied. A selection of
> ALL TYPES is the same as applying no filter on type code.
>
> When both Name and Type Code are provided, the search will result in
> Geographic Areas with names matching or greater than the criteria
> supplied that are of the selected type code value.
>
> When neither Name nor Type Code is provided, the search will result in
> all Geographic Areas being presented.

**Cancel** Will close the Search page and return to the invoking page.

**Help** Will invoke online Help for this page.

####  Geographic Area Maintenance List

The Geographic Area Maintenance List (Exhibit 3-3) will display a list
of all the geographic areas based on the selection criteria entered on
the Search page.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image4.png){width="5.673611111111111in"
  height="4.909027777777778in"}                        height="4.439583333333333in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958900 .anchor}**Exhibit 3-3.** Geographic Area
Maintenance List

The page can list a maximum of 1000 geographic areas. If more than 1000
show as

resulting from the search criteria, the search must be narrowed to view
fewer geographic areas.

[List Columns:]{.underline}

Geographic Area Name, Type Code, FIPS Code, State Defined Code, and
Principal County (for Cities only). Multiple selections may be enabled
by the invoking page, such as Dynamic (Water System) Group Maintenance.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page.*

**Edit**

*Add* Will invoke the Geographic Area Maintenance page in Add mode. A
selection in the list box will not prohibit this item. This item may be
made unavailable when the list is invoked as a selection list from other
than the *System Administration* component.

*Change* When a record is selected in the list box, will invoke the
Geographic Area Maintenance page in Change mode. This item may be made
unavailable when the list is invoked as a selection list from other than
the *System Administration* component.

Double-clicking a geographic area in the list box will invoke the
Geographic Area Maintenance page in Change mode if the change menu item
is available.

*Delete* Will be available when a geographic area is selected in the
list box. The Geographic Area cannot be deleted if any Water System
Geographic Area Associations have been made to the Geographic Area
selected for deletion. The associations will be displayed on the
Geographic Area Association List (Exhibit 3-4). These associations must
be deleted before the geographic area can be deleted. The user can click
**OK** on the Geographic Area Association List to return to the
Geographic Area Maintenance List.

> ![](media/image5.png){width="5.997916666666667in"
> height="2.852777777777778in"}

[]{#__RefHeading___Toc139958901 .anchor}**Exhibit 3-4.** Geographic Area
Association List

If no association to Water Systems exists, will invoke the Delete
Geographic Area dialog box (Exhibit 3-5) requiring selection of **OK**
or **Cancel** prior to removing the geographic area from the Geographic
Area Maintenance List.

![](media/image6.png){width="4.364583333333333in"
height="2.0833333333333335in"}

[]{#__RefHeading___Toc139958902 .anchor}**Exhibit 3-5.** Delete
Geographic Area

> [Delete Geographic Area Buttons:]{.underline}
>
> **OK** Will delete the Geographic Area from the database, remove it
> from the list display, and return to the Geographic Area Maintenance
> List.
>
> **Cancel** Will cancel the delete request and return to the
>
> Geographic Area Maintenance List.

The Delete item may be made unavailable when the list is invoked as a
selection list from other than the *System Administration* component.

*Deselect* Will be enabled when a row is highlighted in the list area.
Choosing Deselect will remove highlight from all selected rows and reset
Number of rows selected to zero.

*Select* When a record is selected in the list box, will return the
selection(s) to the invoking page.

Double-clicking a geographic area in the list box will function as the
Select menu item if the Change menu item is not an available menu item.

**View**

*Filter By* Will invoke the standard filter page where the user may
filter by Type Code and Principal County.

*Refresh* Will retrieve the unfiltered list (original search criteria).
This menu item will be enabled only when the filter criteria has been
applied to the list.

*Search* Will initiate the Geographic Area Search page described above.
Any previously used search values will be presented. If the list has
been invoked as a selection list, the Search page may be presented with
a specific Geographic Area Type Code pre-selected and protected from
change.

*Sort* Will invoke the standard Sort page where the user may sort the
list by Name, Type Code, FIPS Code, State Defined Code, and Principal
County.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order is GEOGRAPHIC_AREA Name and GEOGRAPHIC_AREA
Type_Code in ascending order.

[Protected Fields:]{.underline}

*Number of rows*

*resulting from search*

*criteria entered:* The value in this protected field will show the
number of geographic areas that met the search criteria.

*Number of rows*

*Displayed*: The value in this protected field will indicate the number
of geographic areas available for viewing in the list box via the
vertical scroll bar. The list will be limited to 1000 geographic areas.
This value can be reduced by filtering after selecting the **View/Filter
By** menu item. To view the geographic areas beyond 1000, more specific
search criteria must be provided.

*Number of Rows*

*Selected:* Will display a count of the number of rows highlighted in
the list area.

####  Geographic Area Maintenance

The Geographic Area Maintenance page (Exhibit 3-6) will be presented
from the maintenance list.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image7.png){width="3.6791666666666667in"
  height="4.909027777777778in"}                        height="2.6909722222222223in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958903 .anchor}**Exhibit 3-6.** Geographic Area
Maintenance

[Protected Field:]{.underline}

*Principal County*

*(for cities only)* This field will display the principal county the
user selects for a city. For more information, see the design for the
**Associate County** button.

[Entry Fields:]{.underline}

*\[Geographic Area\]*

*Type* Type of the Geographic Area (e.g., City, County, District).

The selections available in the dropdown list are:

> ARV - Alaskan Remote Village
>
> CS - Census Tract
>
> CT - City
>
> CD - Congress District
>
> CN - County
>
> DS - District
>
> FA - Franchise Area
>
> HU - Hydrologic Unit
>
> IR - Indian Reservation
>
> MSA - Metropolitan Statistical Area
>
> NRD - Natural Resource District
>
> RG - Region
>
> SHD - State House District
>
> SS - State Senate District
>
> ST - State
>
> SD - Subdivision
>
> TW - Township
>
> UA - Unincorporated Area
>
> WD - Water District
>
> Type will be a required field.

*Geographic Area*

*Name* Name of the Geographic Area.

> Geographic Area Name will be a required field.

*FIPS Code* An eight-character alphanumeric Federal Information
Processing Standard (FIPS) Code that will identify the geographic area.
This code may also refer to the Indian Reservation Code, the FIPS County
Code, City Served Code, Congressional District Code, and Metropolitan
Statistical Area (MSA).

> The FIPS Code field will be optional. FIPS Code is mandatory for
> federal reporting when the type is County, Alaskan Remote Village, and
> Indian Reservation. Failure to provide a value for those types may
> result in a federal reporting error.

*State Defined Code* A four-character text value that will be associated
by the state to define the Geographic Area.

> The State Defined Code field will be optional.

*US State Code* The two-character USPS state code in which the
geographic area exists. Only valid USPS state codes will be accepted.
When tabbing off or clicking outside the field, if the state code is not
a valid value, the error message will be: **State Code must be a valid
USPS abbreviation.**

The US State Code field is optional for all geographic area types except
city (CT).

[Tab Sequence:]{.underline}

Type, Geographic Area Name, FIPS Code, State Defined Code, US State
Code, **Associate County**, **Disassociate County**, **OK**, **Cancel**,
and **Help**.

[Buttons:]{.underline}

**Associate County** Will invoke the Geographic Area Maintenance List
page for the user to select a county that can be associated to a city. A
county can be associated to a geographic area only if the geographic
area is a city. The list will contain only Geographic Areas with type =
'CN' (county). The Edit/Select will be the only menu item available
under the Edit option. If the user tries to associate a county to a
geographic area other than a city, the following message will be
presented: **Principal Counties may only be associated to Cities.**

When a selection is made, it will be displayed in the Principal County
field. The association will not occur until the **OK** button is
selected. If no selection is made, the prior value will be retained in
the Principal County field.

**Disassociate County** Will disassociate the County from the Geographic
Area via a disassociation of county from the city. The Principal County
field will display blanks when successfully disassociated. This action
is committed when this button is selected and does not wait for the
**OK** button.

**OK** When the user presses **OK**, the following edit checks will be
made:

Add or Change-

Mode Processing

-   The Type field must be populated. If it is not, the following
    message will be presented: **Geographic Area must have Type and
    Name.**

-   The Geographic Area Name must be populated. If it is not, the
    following message will be presented: **Geographic Area must have
    Type and Name.**

```{=html}
<!-- -->
```
-   The database will be checked for duplicates based on the Geographic
    Area Name and type code. If a record already exists with the same
    name and type code, the following error message will be presented:
    **A duplicate Geographic Area was found.**

-   The software will check that a county is associated only to a city.
    If the check fails, the following error message will be presented:
    **Principal Counties may only be associated to Cities.**

-   If the type was changed to a selection other than city and a
    Principal County is associated, the error message will be
    **Principal County must be removed before changing Type 'City' to
    something else.**

-   If a county was associated to the geographic area represented by the
    city, the selected county will be associated.

-   If the type is city and the US State Code is blank, the error
    message will be **US State Code is required for type of city.**

> If successful, will update database, close the page, and return to the
> maintenance list.

**Cancel** Will invoke an edit check to see if the user changed any
data. If data changed, the Cancel Confirm dialog box (Exhibit 3-7) will
appear.

![](media/image8.png){width="3.5520833333333335in"
height="2.0416666666666665in"}

[]{#__RefHeading___Toc139958904 .anchor}**Exhibit 3-7.** Cancel Confirm

> [Cancel Confirm Buttons:]{.underline}

**Yes** Will invoke the actions performed by the

**OK** button on the maintenance page.

**No** Will close the maintenance page, discard the changes, and return
to the maintenance list.

**Cancel** Will return to the maintenance page and retain all entered
data.

> \*Note\* the disassociation of a county from a city is committed when
> the **Disassociate County** button is pressed. Canceling will not undo
> the disassociation.
>
> If no data changed, the page will close and return to the maintenance
> list.

**Help** Will invoke online Help for this page.

### Model Changes for Service Area 

No model changes are planned for this release.

### Service Area Page Flow 

When the user selects **Service Area** from *the SDWIS/STATE Home Page*
*System Administration* menu item, the Service Area Maintenance List
page (Exhibit 3-8) will be presented.

####  Service Area Maintenance List

[List Columns:]{.underline}

Service Area Name, Name Code, and Classification Code.

[Protected Fields:]{.underline}

*Number of rows*

*Displayed*: The value in this protected field will indicate the number
of service areas available for viewing in the list box via the vertical
scroll bar.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page*.

**Edit**

*Add* Will invoke the Service Area Maintenance page (Exhibit 3-11) in
Add mode. Selecting an item from the list box will not disable this
item.

*Change* Will invoke the Service Area Maintenance page in Change mode.
This item will be enabled when a selection has been made in the list
area.

  ---------------------------------------------------- ---------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image9.png){width="4.450694444444444in"
  height="4.909027777777778in"}                        height="3.44375in"}

  ---------------------------------------------------- ---------------------------------------------------

[]{#__RefHeading___Toc139958905 .anchor}**Exhibit 3-8.** Service Area
Maintenance List

*Delete* Will invoke the following edit checks:

-   If the Type Code of the record selected for deletion is equal to
    "HQ," the following message will be presented: **HQ owned Service
    Areas cannot be deleted.**

-   If any Water System Service Area Associations have been made to the
    Service Area, the record cannot be deleted. The Service Area
    Association List (Exhibit 3-9) will be presented because these
    associations must be deleted before the service area can be deleted.
    The user can click **OK** on the Service Area Association List to
    return to the Service Area Maintenance List.

![](media/image10.png){width="5.991666666666666in"
height="5.263888888888889in"}

[]{#__RefHeading___Toc139958906 .anchor}**Exhibit 3-9.** Service Area
Association List

If the selected Service Area passes both edit checks, the user will be
presented the Delete Service Area dialog box (Exhibit 3-10) asking for
delete confirmation.

![](media/image11.png){width="4.229166666666667in" height="2.25in"}

[]{#__RefHeading___Toc139958907 .anchor}**Exhibit 3-10.** Delete Service
Area

> [Delete Service Area Buttons:]{.underline}
>
> **OK** Will delete the Service Area from the database, remove it from
> the list display, and return to the Service Area Maintenance list.

**Cancel** Will invoke the maintenance list page and the record will not
be deleted from the database.

*Select* When a record is selected in the list box, will return the
selection(s) to the invoking page.

Double-clicking a service area in the list box will function as the
Select menu item if the Change menu item is not an available menu item.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order is D_SERVICE_AREA_TYPE Name, SERVICE_AREA_TYPE
Tinsat_Class_Code ascending.

####  Service Area Maintenance

The Service Area Maintenance page (Exhibit 3-11) will be presented from
the Service Area Maintenance List.

[Entry Fields:]{.underline}

*Classification Code* The classification codes for Service Area will be:

Non-Transient

Other

Residential

Transient

This field will be protected in Change mode.

Classification Code will be a required field.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image12.png){width="4.221527777777778in"
  height="4.909027777777778in"}                        height="2.3881944444444443in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958908 .anchor}**Exhibit 3-11.** Service Area
Maintenance

*Service Area Name* Name of the Service Area. This will be the only
field that can be changed in Change mode.

Service Area Name will be a required field.

*Name Code* A code that represents the Service Area Name. This field
will be protected in Change mode.

Name Code will be a required field.

All the fields will be protected if the record\'s State Code is "HQ."

[Tab Sequence:]{.underline}

Classification Code, Service Area Code, Name Code, **OK**, **Cancel**,
and **Help**.

[Buttons:]{.underline}

**OK** Will invoke the following edit checks:

Add-Mode

-   If all fields are left blank, the following error message will be
    presented: **Blank Service Area record cannot be added.**

-   If the Classification Code field is blank, the following error
    message will be presented: **Classification Code cannot be blank.**

-   If the Service Area Name field is blank, the following error message
    will be presented: **Service Area Name cannot be blank.**

-   If the Name Code field is blank, the following error message will be
    presented: **Service Area Name Code cannot be blank.**

-   If Service Area Name Code already exists in the database, the
    following error message will be presented: **Duplicate Service Area
    Name Code found.**

> If all the checks pass, a record for the Service Area will be added to
> the database.

Change-Mode

-   Only the Service Area name can be changed. If the name is changed,
    then the D_SERVICE_AREA_TYPE table will be updated. The
    D_Last_Update_Timestamp and the D_Userid_Code will also be populated
    and displayed on the page.

**Cancel** If the page remained unchanged, will close the page and
return to the maintenance list.

If data was changed, the standard cancel confirmation will be presented.

**Help** Will invoke online Help for this page.

## User Accounts

### Model Changes for User Accounts 

Changes to USER_ROLE (TINUSERL):

-   Add permitted value of 'LB' described as Laboratory to the Rule_Code
    attribute. (R0059:A.3.2.1.a)

### Maintain User Page Flow 

When the user selects **Maintain User** from *the SDWIS/STATE Home Page*
*System Administration* menu item, the SDWIS User Maintenance List
(Exhibit 3-12) will be presented where the user can add a new user, and
modify or delete an existing user.

####  SDWIS User Maintenance List

The SDWIS User Maintenance List will display a list of all the
Individual Legal Entities identified as users for the state/region and
their current role designation(s). For each user, a 'Y' will indicate
that the user is currently assigned the authority of that role.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image13.png){width="4.363194444444445in"
  height="4.909027777777778in"}                        height="2.9805555555555556in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958909 .anchor}**Exhibit 3-12.** SDWIS User
Maintenance List

[List Columns:]{.underline}

First Name, Last Name, User ID, System Administrator, Compliance
Officer, Enforcement Officer, Data Entry, Inventory, Sampling Data
Entry, Site Visits, and Laboratory. (R0059:A.3.2.2.1.a)

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page*.

**Edit**

> *Add* A selection in the list box will not disable this item. Will
> present the Legal Entity Maintenance List page where only Individuals
> (type = IN) will be presented. Both **Edit/Select** and **Edit/Add**
> menu items will be enabled. When a selection is made, the User
> Maintenance page will be presented. If the Individual already has a
> d_user record, the maintenance page will be presented in change mode.
> If not, it will be presented in add-mode. If edit/add is selected, a
> new Individual can be added. Upon selecting the **OK** button on the
> Individual Maintenance page, the User Maintenance page will be
> presented in add-mode.

*Change*

*User* Will be available only when a record is selected in the list and
will invoke the User Maintenance page in Change mode.

Double-clicking a record on the list will also invoke the User
Maintenance page in Change mode.

*Change Govt.*

*Agency*

> *Access* Will invoke the Government Agency Access List (Exhibit 3-13)
> where the user can select **Edit/Add** or **Edit/Delete** to add or
> delete Government Agencies to whose Water System the user has access.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image14.png){width="5.147222222222222in"
  height="4.909027777777778in"}                        height="4.226388888888889in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958910 .anchor}**Exhibit 3-13.** Government
Agency Access List

*Delete* Will be available when a record is selected in the list.

If the User (Legal Entity) is associated to a Water System via a point
of contact designation, the record cannot be deleted and the following
error message will be presented: **Delete not allowed. Legal Entity is a
Water System Contact.** Otherwise will invoke the Delete User dialog box
(Exhibit 3-14), asking for confirmation of the action prior to the
record being deleted from the database.

![](media/image15.png){width="4.604166666666667in"
height="2.5416666666666665in"}

[]{#__RefHeading___Toc139958911 .anchor}**Exhibit 3-14.** Delete User

[Delete User Buttons:]{.underline}

**OK** Will delete the D_USER and all associated

> USER_ROLEs, INDIVIDUAL, and LEGAL_ENTITY.

**Cancel** Will abort the delete and return the user to the maintenance
page.

**View**

*Filter By* Will enable the user to filter by First Name, Last Name,
User Id, and Role. Use of this item will enable the Refresh item. Add
Filter by new laboratory (LB) role. (R0059:A.3.2.2.1.b)

*Refresh* Will retrieve the unfiltered list (original list). This menu
item will be enabled only when filtering criteria have been applied to
the list.

*Sort* Will invoke the standard Sort dialog box with all columns on the
list available as sort criteria. Three levels of sorting will be
supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order will be INDIVIDUAL Last_Name ascending.

[Protected Fields:]{.underline}

*Number of rows*

*Displayed*: Will show the total number of rows that are displayed in
the list, which may be less than the number of rows that are in the
database. The maximum number of rows displayed is 1000.

####  User Maintenance

The User Maintenance page (Exhibit 3-15) will be presented from the
SDWIS User Maintenance List. In add-mode, the Legal Entity Maintenance
List will be presented requiring the selection of a Legal Entity prior
to the User Maintenance page presentation. The User Maintenance page is
presented in change-mode directly from the SDWIS User Maintenance list.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image16.png){width="5.121527777777778in"
  height="4.909027777777778in"}                        height="4.644444444444445in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958912 .anchor}**Exhibit 3-15.** User
Maintenance

[Protected Fields:]{.underline}

*First Name* First name of the User (Individual). The data will be
stored in table INDIVIDUAL.

*Last Name* Last name of the User (Individual). The data will be stored
in table INDIVIDUAL.

[Entry Fields:]{.underline}

*Maintain User and Role*

*Group Box* This Group Box will enable the addition of a new role or
maintenance of an existing role. If no selection is made in the Role
History List box, these fields will contain their default value state,
as indicated below, in preparation for an add function. New values can
be provided and a new role created by pressing the **OK** button.

When a single selection is made in the Role History List box, these
fields will be populated with the values from the selected row. They can
then be modified with new values, according to the rules below. The
change will be processed via the **OK** button.

*User ID* Eight-character User ID code stored in table D_USER. This code
must be unique within table D_USER. It will not be case-sensitive.

User ID will be a mandatory field.

*Role* The role code to be added or changed for the user. When the Role
is populated via a single selection from the Role History list box, the
Role will be protected from modification.

The permitted values for the dropdown list will be:

IN -- Inventory (Default Value)

CO -- Compliance Officer

DE -- Data Entry

EO -- Enforcement Officer

SA -- System Administrator

SD -- Sampling Data Entry

SV -- Site Visits

LB -- Laboratory (R0059:A.3.2.2.a)

Refer to Chapter 1 of this design document for the specific authorities
granted by each Role.

Role is a required field in add mode. In change mode it is not required
in order to allow for the maintenance of the User ID. If a role is not
provided in change mode, no processing will occur relative to the
addition or modification of a user's authorities.

*Start*

*Date* The start date on which the user will have the authority granted
by the role code. This date will default to current date. It cannot
contain a date prior to current date in add mode nor be changed to a
date prior to current date in change mode. It can only be changed to a
future date if the current value is still in the future.

Start Date is a required field. In change mode, if the start date is in
the past, this field will be protected from modification.

*End*

*Date* The last date that the user will have the authority granted by
the role code. This date will default to null. It cannot contain a date
prior to current date nor a date prior to the effective start date. In
change mode, it can only be changed to a future date if the current
value is either null, current date, or a future date.

*Role History*

*List Box* This list will present all USER_ROLES for the D_USER. The
list columns will be Role, Start Date, End Date. The rows will be listed
in descending effective end date order so that the active rows are
displayed at the top, followed by descending effective start date and
ascending role. One selection may be made in the list box which will
cause the selected row values to be populated in the Maintain Role Group
box for maintenance if the effective_end_date is current date or in the
future.

[Tab Sequence:]{.underline}

**Maintain User and Role**, User ID, Role, Start Date, End Date, **OK**,
**Cancel**, **Help,** Role History List box.

[Buttons:]{.underline}

**OK** Will invoke the following edit checks:

-   If the User ID field is blank, the following error message will be
    presented: **The User ID must not be blank.**

```{=html}
<!-- -->
```
-   If the User Role is selected, the start date must have a value that
    is equal to or greater than the current date. If it is not, the
    error message will be: **Start Date must be equal or greater than
    current date.**

```{=html}
<!-- -->
```
-   If the end date has a value, it must be equal or greater than the
    start date. If it is valued and is not equal or greater than the
    start date, the error message will be: **End Date must be equal or
    greater than Start Date.**

-   If the Role field is left blank, the error message will be: **Role
    must not be blank.**

*Duplicate Check*

Duplicate check for the User ID. If a D_USER already exists with the
same User ID the error message will be: **This User ID is already used
by another User.**

If a role is being added or dates of an existing role are being changed,
the effective period of the role cannot conflict with an existing role
of the same code. There may be gaps in time, but no overlaps for like
role codes for the same User ID. If this is found, the error message
will be: **This role conflicts with an existing row of the same role
code.** Highlight the Role Code field as an error.

*Add Mode*

-   A D_USER will be created and linked to INDIVIDUAL. The new D_USER
    current group will not be set at this time.

-   A new USER_ROLE will be created and associated to the new D_USER
    row. The effective_end_date will be set to null if not supplied. The
    add_User ID and add_timestamp will be set to current values.

-   The page will close and proceed to the Government Agency Access
    List.

*Change Mode*

The User ID will be updated in the D_USER table and the D_Userid_Code
and d_last_update_ts will be set to current values.

If values existing the Maintain User and Role Group Box for a new role,
a new row will be created in the USER_ROLE table as described above in
add-mode processing. If the values exist in the Maintain Role Group Box
for a row highlighted in the list box, the selected row in USER_ROLE
will be updated and the D_Userid_Code and d_last_update_timestamp will
be set to current values.

**Cancel** If no data was changed, the page will close and return to the
maintenance list.

If data was changed, the standard cancel confirmation page will be
presented.

**Help** Will invoke online Help for this page.

####  Government Agency Access List

This Government Agency Access List page (Exhibit 3-16) will be presented
when the user selects **Edit/Change Government Agency Access** on the
SDWIS User Maintenance List or has added a new user. This page will list
the Government Agencies assigned to a particular user. The Government
Agencies linked to table INDIVIDUAL through INDIVIDUAL_GOVT_AGENCY_ASGMT
will appear in the list. These assignments control the list of water
systems to which the user will be granted access in all authorized
components of SDWIS/STATE.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image17.png){width="5.922916666666667in"
  height="4.909027777777778in"}                        height="4.719444444444444in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958913 .anchor}**Exhibit 3-16.** Government
Agency Access List

[Protected Fields:]{.underline}

*First Name* First name of the User in the SDWIS User Maintenance List
will be displayed.

*Last Name* Last name of the User in the SDWIS User Maintenance List
will be displayed.

*User ID* User ID of the User in the SDWIS User Maintenance List will be
displayed.

*Number of rows*

*Displayed*: The value in this protected field will indicate the number
of government agencies available for viewing in the list box via the
vertical scroll bar.

*Number of Rows*

*Selected:* Will display a count of the number of rows highlighted in
the list area.

[Menu Items:]{.underline}

**Edit**

*Add* Will be enabled regardless of a selection having been made from
the list. Selecting this menu item will invoke the Legal Entity
Maintenance List page (see Chapter 2, Exhibit 2-3) where the user can
select from the list of LEGAL_ENTITIES designated as Government
Agencies. Multiple selections will be allowed in the Legal Entity
Maintenance List where only the Edit/Select menu item will be enabled.

*Delete* Will be enabled only when one or more records are selected in
the list. Prior to deleting, an advisory will be presented notifying the
System Administrator that confirming the delete will delete all water
system groups defined by the User ID and that the User ID's current
group will need to be reset by the System Administrator by selecting one
of the remaining government agencies.

If the System Administrator chooses to continue with the delete request,
the following actions are taken:

-   Update the D_USER by removing the value from the
    current_group_is_number. If the D_USER current_tingovag_is_number
    and current_tingovag_st_code is equal to one of the government
    agency assignments being removed, remove the values from these two
    fields as well.

-   Delete all WATER_SYSTEM_GROUPS created by the D_USER. This will also
    delete all the group members in the WATER_SYSTEM_GROUP_ASGMT table.

> *Make* When a Government Agency has been selected in the group, the
>
> *Current* system administrator may select a government agency to be
> the current group of the User ID. At the time this menu item is
> selected, the D_USER current_tingovag_is_number and
> current_tingovag_st_code will be set to those of the selected
> government agency.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order will be Government Agency name ascending.

## Rule Authority

### Model Changes for Rule Authority

No model changes are planned for this release.

### Rule Authority Page Flow

When the user selects **Rule Authority** from the *System
Administration* menu item from the *SDWIS/STATE Home Page*, the Rule
Selection List (Exhibit 3-17) will be presented.

####  Rule Selection List

The Rule Selection List will display all the Rules that are final
(Status Type Code = "FN") and the end date of the regulation/rule is
greater than the current date or is null. Through this list, the user
can associate or disassociate a rule to a Government Agency.

[List Columns:]{.underline}

Rule Abbreviation and Rule Name.

[Protected Items:]{.underline}

*Number of Rows*

*Displayed:* The number of rules presented in the list area.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image18.png){width="5.386111111111111in"
  height="4.909027777777778in"}                        height="4.574305555555555in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958914 .anchor}**Exhibit 3-17.** Rule Selection
List

[Default Sort Order:]{.underline}

The default sort order is RULE Abbreviation_Text ascending.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the *SDWIS/STATE Home Page*.

**Edit**

*Select* Will be enabled only when a record is selected in the Rule
Selection List. Selecting this menu item will invoke the Current Rule
Association List (Exhibit 3-18), which will detail the Legal Entities
(Government Agency) to which the rule will apply and also provide the
functionality to assign more Government Agencies.

**Help** Will invoke online Help for this page.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Current Rule Association List

The Current Rule Association List page (Exhibit 3-18) will show the name
of the Government Agency type Legal Entities to which the rule is
associated. The user will be able to associate more Government Agency
type Legal Entities to this Rule or disassociate a Government Agency
from a Rule. When a Government Agency type Legal Entity is deleted, its
association to Rule is also deleted.

![](media/image19.png){width="5.992361111111111in"
height="5.063194444444444in"}

[]{#__RefHeading___Toc139958915 .anchor}**Exhibit 3-18.** Current Rule
Association List

The Government Agency Legal Entities displayed on this page will be
those associated to the rule selected by the user in the Rule Selection
List through RULE_GOVERNMENT_AGENCY_ASGMT.

[List Columns:]{.underline}

Government Agency name.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the previous page.

**Edit**

*Associate* Will be enabled regardless of a selection in the list.
Selecting this menu item will invoke the Legal Entity Maintenance list
where all the Government Agencies (Legal Entities) will be listed
excluding those already associated to that rule. Multiple selections
will be enabled in the list and only the Edit/Select menu item will be
available on the Legal Entity Maintenance List page.

*Disassociate* Will be enabled only when a record is selected from the
Current Rule Association List. Selecting this menu item will invoke the
Disassociate Confirmation dialog box (Exhibit 3-19) asking the user to
confirm the action of disassociating the government agency from the
rule.

![](media/image20.png){width="5.083333333333333in"
height="2.3541666666666665in"}

[]{#__RefHeading___Toc139958916 .anchor}**Exhibit 3-19.** Disassociate
Confirmation

[Disassociate Confirmation Buttons:]{.underline}

**OK** Will disassociate the Rule from the selected Government Agency.
The record linking the rule and the Government Agency (Legal Entity) in
the RULE_GOVERNMENT_AGENCY_ASGMT will be deleted and the user will be
returned to the refreshed Current Rule Association List page.

**Cancel** Will return the user to the Current Rule Association List and
remove the highlight from the record that was selected for
disassociation.

**View**

*Rule Details* Will detail the Rule under consideration on the Rule
Details page

(Exhibit 3-20). The following protected information about the rule will
be displayed:

> Abbreviation, Name, Description, Publication Date, Begin Date, End
> Date and the Status Type Code (Advance Notice, Draft, Final, or
> Proposed).

![](media/image21.png){width="5.997916666666667in" height="2.90625in"}

[]{#__RefHeading___Toc139958917 .anchor}**Exhibit 3-20.** Rule Details

[Rule Details Button:]{.underline}

**OK** Will close the Rule Details page and return to the Current Rule
Association List.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

## Analytes, Methods, and Rules 

### Model Changes for Analytes

-   Resize state_classification_code from 3 to 6. (R0036:A.3.4.1.a)

### Analytes Page Flow

When the user selects **Analytes, Methods and Rules/Analytes** from the
*System Administration* menu item on the *SDWIS/STATE Home Page*, the
Analyte Search page (Exhibit 3-21) will be presented through which the
user can search for analytes by Code, Name, Type, or CAS Registry
Number.

####  Analyte Search

The user will be able to enter only one search criterion on the Analyte
Search page. When the user enters data in any of the entry fields, the
rest of the fields will be protected/disabled.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image22.png){width="4.845833333333333in"
  height="4.909027777777778in"}                        height="3.7284722222222224in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958918 .anchor}**Exhibit 3-21.** Analyte Search

[Entry Fields:]{.underline}

*Analyte Code*

> Unique four-character code used by EPA and the states/regions to
> represent analytes in the national database. Will search for analyte
> codes equal to and greater than the value entered. The field is
> alpha-numeric and will follow alphabetic sort methods, meaning that a
> value of 4 will display all codes beginning with 4 and not all codes
> greater than the numeric 4, such as 30.

*Analyte Name* Forty-character common name of a contaminant as used by
states/regions and EPA. Will search for all analytes with a name equal
to or alphabetically greater than the value entered.

*CAS Registry*

*Number* Fifteen-character ID that defines the chemical code used
internationally. This number is defined by the Chemical Abstract Service
(CAS). Will search for analytes with CAS registry numbers equal to and
greater than the value entered. The field is alpha-numeric and will
follow alphabetic sort methods, meaning that a value of 4 will display
all codes beginning with 4 and above and not all codes greater than the
numeric 4, such as 30.

*Analyte Type* Three-character code defining the type of Analyte (e.g.,
IOCInorganic Chemical, MOR - Organism). Will perform an exact match and
list only analytes of the selected type. Permitted values are:

Inorganic Chemical (IOC)

> Organism (MOR)
>
> Radionuclide (RA)
>
> Water Quality (WQ)
>
> Organic Chemical (OC)
>
> Group Contaminant (GC)
>
> Rule (RL)
>
> Other (OT)

[Tab Sequence:]{.underline}

Analyte Code, Analyte Name, CAS Registry Number, and Analyte Type,
**Search, Clear, Cancel, Help**.

[Buttons:]{.underline}

**Search** Will search the Analyte Table and pull all the records
meeting the search criteria in the Analyte Maintenance List Exhibit
3-22).

**Clear** Will clear the data from the page and enable all the entry
fields.

**Cancel** Will close Search and return to the *SDWIS/STATE Home Page*.

**Help** Will invoke online Help for the page.

####  Analyte Maintenance List

The Analyte Maintenance List (Exhibit 3-22) will display the list of the
analytes based on the search.

  ---------------------------------------------------- -----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image23.png){width="5.995833333333334in"
  height="4.909027777777778in"}                        height="4.308333333333334in"}

  ---------------------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958919 .anchor}**Exhibit 3-22.** Analyte
Maintenance List

[List Columns:]{.underline}

Analyte Code, Analyte Name, Type, CAS Registry No., Reportable Start
Date, Reportable End Date, and Ownership.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page*.

**Edit**

*Add* Will be enabled regardless of a selection in the list. Selecting
**Edit/Add** will invoke the Analyte Maintenance page in Add mode where
the user can add a new Analyte.

*Change* Will be enabled only when a record is selected from the list.
Selecting **Edit/Change** will invoke the Analyte Maintenance page in
Change mode where the user can change the details of the Analyte if it
is not a federally maintained analyte.\
\
Double-clicking in the list box also will invoke the Analyte Maintenance
page in Change mode.

> *Delete* Will be enabled only when a record is selected from the list.
>
> The analyte cannot be deleted if it is a federally maintained analyte,
> i.e., the Tsaanlyt_St \_Code = "HQ." The error message will be: **This
> is a federally owned analyte record and cannot be deleted.**
>
> The state-owned analyte cannot be deleted if it is associated to:

-   violation (TMNVIOL)

-   standard method analyte assignment (TSASMAA)

-   analyte group assignment (TSAAGA)

-   sample analytical results (TSASAR)

-   sample summary (TSASMPSM)

-   monitoring requirement (TMNMNR)

-   sampling plan (TMNSAPLN)

-   analyte level rule assignment (TMNALRA)

-   facility analyte level (TMNFANL) which has an association to either
    an MDBP Summary or Violation

-   lab analyte method assignment (TSALAMA) (R0059:A.3.4.2.2.a)

> Any of these situations will present the Analyte Delete Conflict
> dialog box (Exhibit 3-23). Conflict details will be displayed in ten
> Group Boxes on the Analyte Delete Conflict page.

Sample Result Group Box:

> The SAMPLE_ANALYTICAL_RESULT table will be read for all the records
> that have an association with the Analyte selected for deletion. Then
> the samples related to the sample analytical results will be read. The
> water system related to the sample will be read for the Water System
> Name.

![](media/image24.png){width="5.99375in" height="7.611111111111111in"}

[]{#__RefHeading___Toc139958920 .anchor}**Exhibit 3-23.** Analyte Delete
Conflict

> The Sample Result Group Box will display the Water System No., Lab
> Sample No., Collection date, and State Sample No.

Violations Group Box:

> All the violations related to the analyte and the water system related
> to the violation will be read.
>
> The Violations Group Box will display the violation's year, FedRep ID,
> and Water System No.

Sample Summary Group Box:

All the Sample Summaries related to the analyte will be read. The
monitoring period and the water system related to the sample summaries
will be read and the details displayed.

Analyte Group Box:

If the analyte belongs to an Analyte Group, then all the Analyte Group
records related to the Analyte ID will be read.

> The Analyte Group Box will display the analyte group code and name.

Analyte Method Pairing Group Box:

The records in Standard_Method_Analyte_Assignment related to the Analyte
will be read. The Standard_Method related to the
Standard_Method_Analyte_Assignment for the Code.

> The Analyte Method Pairing Group Box will display the Analyte Code and
> Standard Method Number Code.

Analyte Level Rule Pairing Group Box:

The rule records related to the Analyte Level Rule Assignment related to
the Analyte will be read and will populate the Group Box.

> The Analyte Level Rule Pairing Group Box will display the Analyte Code
> and Rule.

Monitoring Requirement Group Box.

> The monitoring requirement records related to the Analyte will be read
> and will populate the Group Box.
>
> The Monitoring Requirement Group Box will display the Samples
> Required, Sample Type, Sample Periodicity, and M&R Violation Type.
>
> Sampling Plan Group Box
>
> The Sampling Plan records related to the Analyte will be read and will
> populate the group box. It will display the Water System No. of the
> Sampling Plan and the Sampling Plan effective begin date.
>
> Facility Analyte Level Group Box.
>
> The Facility Analyte Level Group Box will contain two lists, the MDBP
> Summaries and Violations.
>
> The MDBP Summaries list will contain the MDBP Summary records
> associated to the facility analyte level related to the Analyte being
> requested for deletion. The list will show the Water System No., WSF
> State Asgn ID, Summary Type, and Monitoring Period Name.
>
> The Violations list will contain the Violation records associated to
> the facility analyte level related to the Analyte being requested for
> deletion. The list will show the violation's year, FedRep ID, and
> Water System No.
>
> Lab Analyte Method Assignment Group Box: (R0059:A.3.4.2.2.a)
>
> All the Lab Analyte Method Assignments related to the Analyte being
> requested for deletion will be read. The Laboratory related to the Lab
> Analyte Method Assignment will be read for the Lab ID No. and
> Certifying Agency and the Standard Method for the Standard Method
> Code.
>
> The Lab Analyte Method Assignments list will display the Lab
> Certifying Agency, ID No. and Standard Method Code.

**OK** Will return the user to the Analyte Maintenance List.

> If no conflicts exist to prohibit the deletion, but the analyte is
> associated to a facility analyte level that does not have further
> associations to either MDBP Summary or Violation, an advisory will be
> presented that says: **Deletion of Analyte will remove related
> Facility Analyte Levels.** Pressing **Cancel** will abort the delete
> and return to the maintenance list page. Pressing **OK** will continue
> with the delete.
>
> If no conflict exists, will invoke the Analyte Delete dialog box
> (Exhibit 3-24), showing the details of the Analyte to be deleted.

![](media/image25.png){width="5.997222222222222in"
height="2.5805555555555557in"}

[]{#__RefHeading___Toc139958921 .anchor}**Exhibit 3-24.** Analyte Delete

[Analyte Delete Buttons:]{.underline}

**OK** Will delete the analyte and return to the Analyte Maintenance
List.

**Cancel** Will abort the delete request and return to the Analyte
Maintenance list.

*Select* Will close the page and return the selected analyte(s) to the
invoking page. This menu item will be enabled based upon the request of
the invoking page to function as a selection list. The invoking page may
also request that the list be single-select or multi-select. When the
Edit/Select menu item is available, the other Edit menu items will be
disabled for security reasons.

**View**

*Filter By* Will allow the user to filter by Analyte Code, Analyte Name,
Type, CAS Registry Number, Reportable Start Date, and Reportable End
Date. Use of this item will enable the Refresh item.

*Refresh* Will retrieve the unfiltered list (original search criteria).
This menu item will be enabled only when the filter criteria have been
applied to the list, otherwise it will be disabled.

*Search* Will take the user to the Analyte Search page where other
search criteria can be entered to retrieve records and display them in
the Analyte Maintenance List. Previous criteria used will be presented.

*Sort* Will invoke the standard Sort page with all columns on the list
may be used as sort criteria. Three levels of sorting will be supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Criteria:]{.underline}

The default sort criteria will be ANALYTE CODE ascending when no search
criteria were used. When search criteria were supplied, the list will
sort ascending by the selected search criteria.

[Protected Fields:]{.underline}

*Number of rows*

*resulting from search*

*criteria entered:* Will show the total number of rows that met the
search criteria.

*Number of rows*

*displayed* : Will show the total number of rows that are displayed in
the list, which may be less than the number of rows that met the search
criteria.

*Number of rows*

*selected* : Will show the total number of rows that are selected in the
list.

####  Analyte Maintenance

The Analyte Maintenance page (Exhibit 3-25) will be displayed when the
user selects **Edit/Add** or **Edit/Change** from the Analyte
Maintenance List. If the analyte state code is "HQ," then all but the
State Classification field will be protected.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image26.png){width="4.598611111111111in"
  height="4.909027777777778in"}                        height="3.4604166666666667in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958922 .anchor}**Exhibit 3-25.** Analyte
Maintenance

[Protected Fields:]{.underline}

*Reportable*

*Start Date* Will indicate when the analyte ceases to be an unregulated
contaminant for monitoring.

*Reportable*

*End Date* Will indicate when the analyte ceases to be a regulated
contaminant for monitoring.

[Entry Fields:]{.underline}

*Name* Forty-character entry field for name of the Analyte. If the Name
field is populated, then the analyte name entered is matched with a name
already existing in the database. If the name is already present in the
database, then the following message will be presented: **Analyte name
must be unique to both Name and Synonymous Name.**

Name will be a required field.

*Type* Type defines the type of the analyte e.g., organic, inorganic.
The selections available in the dropdown list will be:

IOC Inorganic Chemical

MOR \[Microbiological\] Organism

RA Radionuclide

WQ Water Quality

OC Organic Chemical

GC Group Contaminant

RL Rule

OT Other

Type will be a required field.

*Code* Four-character analyte code that will uniquely identify the
analyte.

> Code will be a required field. It will be protected from modification
> in change mode.

Code will be a required field.

*State Classification*

*Code* A six character code that the state may use to classify analytes.
The permitted values for the dropdown list will be retrieved from the
permitted values CODE table name of "SMPSTCLASS." This field can be
updated for all analytes including the federally-owned types with state
code = 'HQ'. (R0036:A.3.4.2.3.a)

State Classification Code will be an optional field.

*Synonymous*

*Name* Forty-character scientific name assigned to the analyte. If the
Synonymous Name is populated, then a duplicate check will be conducted.
If a duplicate is found in the database with either the same synonymous
name or analyte name OR if the provided synonymous name is the same as
the provided analyte name, the following message will be presented:
**Analyte Name must be unique to both Name and Synonymous Name.**

This will be an optional field.

*CFR Section*

*Reference* Twenty-character coded value which will provide a reference
to the Code of Federal Regulations Section.

This will be an optional field.

*CAS Registry*

*Number* Fifteen-character CAS Registry Number; a unique identifier
assigned by the Chemical Abstract Service (CAS) for a specific chemical
compound (e.g., an unregulated contaminant).

This will be an optional field.

*Comments* Will provide space for comment text for the analyte.

This will be an optional field.

[Buttons:]{.underline}

**OK** The following edit checks will be made:

-   The Name field must be populated. If it is not, the following
    message will be presented: **Analyte Name is a required field.**

```{=html}
<!-- -->
```
-   The Type field must be populated. If it is not populated, the
    following message will be presented: **Analyte Type is a required
    field.**

```{=html}
<!-- -->
```
-   The Code field must be populated. If it is not, the following
    message will be presented: **Analyte Code is a required field.**

```{=html}
<!-- -->
```
-   If the Code field is populated, it will be checked for duplicates.
    If the code already exists in the database, the following message
    will be presented: **Analyte Code must be unique.**

*Add Mode*

> A new record will be created in the Analyte table. The
> Tsaanlyt_ST_Code will be set to the primacy agency state code. The
> Reportable_Start_Date and Reportable_End_Date will be set to null.
>
> The last update timestamp will be set to the current timestamp and the
> last update User ID will be set to the current User ID.
>
> The page will close and return to the maintenance list.

*Change Mode* The Analyte will be updated. The page will close and
return to the maintenance list.

**Cancel** If data on the maintenance page has not changed, then the
Analyte Maintenance List will be presented. If changes have been made,
the standard Cancel Confirm page will be presented.

**Help** Will invoke the system online Help facility.

### Model Changes for Analyte Groups 

No model changes are planned for this release.

### Analyte Groups Page Flow 

From the *SDWIS/STATE Home Page System Administration Menu Item*,
selecting **Analytes, Methods, and Rules/Analyte Groups** will invoke
the Analyte Group Maintenance List page (Exhibit 3-26).

####  Analyte Group Maintenance List

The user will be able to initiate adding, changing, or deleting an
Analyte Group using the Analyte Group Maintenance List.

[List Columns:]{.underline}

Analyte Group Name and \[Analyte Group\] Code.

[Protected Fields]{.underline}:

*Analyte List* Will show the analytes of the highlighted Analyte Group.
List will be empty when no Analyte Group is selected or when more than
one Analyte Group is selected. When a selection is changed the list will
refresh. When returning from the Analyte Group Maintenance page the list
will be refreshed.

*Number of rows*

*displayed* : Will show the total number of rows that are displayed in
each list.

![](media/image27.png){width="5.99375in" height="4.117361111111111in"}

[]{#__RefHeading___Toc139958923 .anchor}**Exhibit 3-26.** Analyte Group
Maintenance List

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the Main Menu.

**Edit**

*Add* Will be available regardless of a selection having been made in
the list box. Will invoke the Analyte Search. After choosing the Search,
the Analyte Maintenance List will be presented in multi-select mode.

*Change* Will be available only when a record is selected in the list
box. Will invoke the Analyte Group Maintenance page in Change mode.

Double-clicking in the list box also will invoke the Analyte Group
Maintenance page in Change mode.

*Delete* Will be available when an Analyte Group is selected in the list
box. When this menu item is selected, a check will be conducted for
associations between monitoring requirements, sampling plans, or
violation groups. If there is a relationship, then the Analyte Group
cannot be deleted.

If referenced by a monitoring requirement, the following message will be
presented: **This Analyte Group is in use by a Monitoring Requirement
and cannot be deleted.**

If referenced by violation group, the following message will be
presented: **This Analyte Group is in use by a Violation Group and
cannot be deleted.**

If referenced by a sampling plan, the following message will be
presented: **This Analyte Group is in use by a Sampling Plan and cannot
be deleted.**

If no relationship exists, then the Analyte Group Delete Confirm dialog
box (Exhibit 3-27) will be presented.

> ![](media/image28.png){width="4.311805555555556in"
> height="2.7083333333333335in"}

[]{#__RefHeading___Toc139958924 .anchor}**Exhibit 3-27.** Analyte Group
Delete Confirm

> [Analyte Group Delete Confirm Buttons:]{.underline}
>
> **OK** Will delete the record in the database and return to the
> Analyte Group Maintenance List.
>
> **Cancel** Will not delete the record and will return to the Analyte
> Group Maintenance List.
>
> *Select* Will return the selected Analyte Group to the invoking page.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order will be ANALYTE GROUP Name.

#### Analyte Group Maintenance

The Analyte Group Maintenance page (Exhibit 28) will be displayed in Add
mode when the user clicks **Select** on the Analyte Maintenance List
after selecting one or more analytes from the list.

The Analyte Group Maintenance page will be displayed in Change mode when
the user selects **Edit/Change** from the Analyte Group Maintenance List
menu after highlighting a row or by double-clicking a highlighted row.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image29.png){width="1.4979166666666666in"   ![](media/image30.png){width="4.295833333333333in"
  height="5.370833333333334in"}                         height="3.4763888888888888in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958925 .anchor}**Exhibit 3-28.** Analyte Group
Maintenance

[Entry Fields:]{.underline}

*Analyte Group* Twenty-character field for Analyte Group Name. This
field will be enabled only in Add mode.

Analyte Group will be a required field.

*Code* Four-character entry field for Type Code. This field will be
enabled only in Add mode.

Code will be a required field.

[List Columns:]{.underline}

Analyte Name, Analyte Code, and Sequence Number (from Analyte Group
Asgmt).

The sequence number will be assigned chronologically by ascending
analyte code value. Subsequent selections will be appended
chronologically by ascending analyte code value.

[Default Sort Criteria:]{.underline}

The default sort criteria will be the ANALYTE_GROUP_ASGMT
Sequence_Number ascending.

[Buttons:]{.underline}

**Analyte List** Will first present Analyte Search to narrow the list of
analytes. Then, will display the Analyte Maintenance List, which will be
presented in multi-select mode. Analytes already selected for inclusion
in the analyte group that are listed will already be highlighted. In
Change mode, this button will be enabled only if a Monitoring
Requirement or Violation Group does not reference the Analyte Group

**Change** Will be enabled when the user selects a record from the
analyte list box and both the Analyte Name and Analyte Code columns are
filled. Clicking **Change** will take the user to the Modify Analyte
Sequence in Group (Exhibit 3-29) page where the user can change the
sequence of the Analytes in the group.

> **OK** The following edit checks will be conducted:

-   If the sequence number is less than zero, then the following error
    message will be presented: **Sequence number must be greater than
    zero.**

-   If the sequence number is greater than the total analytes, then the
    following error message will be presented: **New Sequence Number may
    not exceed number of analytes in list.**

> When successful, the selected analyte will be assigned the new
> sequence and all analytes in the group with a sequence number equal to
> and higher than the new sequence number will be incremented by one
> value.
>
> ![](media/image31.png){width="5.997222222222222in"
> height="2.401388888888889in"}

[]{#__RefHeading___Toc139958926 .anchor}**Exhibit 3-29.** Modify Analyte
Sequence in Group

**Delete** Will be enabled when the user selects an analyte from the
list box only if Monitoring Requirement or Violation Group does not
reference the Analyte Group. The Delete Analyte from Group Confirm
dialog box (Exhibit 3-30) will be displayed.

> ![](media/image32.png){width="5.676388888888889in" height="2.1875in"}

[]{#__RefHeading___Toc139958927 .anchor}**Exhibit 3-30.** Delete Analyte
from Group Confirm

[Delete Analyte from Group Confirm Buttons:]{.underline}

> **OK** Will close the dialog box, delete the Analyte Group Assignment
> record, and update the sequence numbers of each of the remaining
> analytes in ANALYTE_GROUP_ASSIGNMENT so as the sequence numbers range
> from 1 to the maximum number of analytes with no gaps in sequence
> numbers.
>
> **Cancel** Will return the user to Analyte Group Maintenance.

**OK** Will invoke the following edit checks:

-   If the Analyte Group Name is blank, the following error message will
    be presented: **Analyte Group name may not be left blank.**

-   If the Analyte Group Code is blank, the following error message will
    be presented: **Analyte group code should not be left blank.**

-   If the above checks pass, then a duplicate check will be conducted
    on both the Analyte Group Name and the Analyte Group Code.

> \- If the Analyte Group Name already exists, the following error
> message will be presented: **An Analyte Group of this same name
> already exists.**
>
> \- If the Analyte Group Code already exists, the following error
> message will be presented: **An Analyte group with the same code
> already exists.**

-   If all the edit checks pass, then a record will be added to
    ANALYTE_GROUP.

> After the record in ANALYTE_GROUP is created, the associations between
> the Analyte Group and the Analyte will be made through the
> ANALYTE_GROUP_ASGMT table. The following data will be entered in the
> ANALYTE_GROUP_ASGMT table: Sequence_Number, D_Last_Updt_TS,
> D_Userid_Code.

**Cancel** Will return the user to the Analyte Group Maintenance List.

**Help** Will invoke online Help for this page.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

### Model Changes for Analyte Level

No model changes are planned for this release.

### Analyte Level Search 

When the user selects **Analytes Methods and Rules/Analyte Level** from
the *System Administration* menu item on the *SDWIS/STATE Home Page*,
the Analyte Level Search page will be presented (Exhibit 3-31).

####  Analyte Level Search

The Analyte Level Search page will provide the flexibility to search for
Analyte Levels based on Analyte Code or Rule Abbreviations.

[Entry Fields:]{.underline}

*Analyte Code* Four-character analyte code. When the user tabs off this
field, the software will check the codes in the Analyte table to see if
the entry is valid. If it is not, the Analyte Maintenance List will be
presented in single-select mode where the user can select an analyte.

The Analyte Code field is optional.

*Rule Abbrev.* Four-character Rule abbreviation text. When the user tabs
off this field, the software will check to see if the entry is valid
against Rule table in the database. If it is not, the Rule Selection
List will be presented where the user can select a rule.

The Rule Abbrev. field is optional.

[Buttons:]{.underline}

\[Analyte Code\]

**Go To** Will invoke the Analyte Maintenance List in single-select
where the user can select one Analyte Code. Only the Edit/Select menu
item will be available.

  ------------------------------------------ -----------------------------------------------------
  ![](media/image33.png){width="1.56875in"   ![](media/image34.png){width="5.03125in"
  height="5.622916666666667in"}              height="3.064583333333333in"}

  ------------------------------------------ -----------------------------------------------------

[]{#__RefHeading___Toc139958928 .anchor}**Exhibit 3-31.** Analyte Level
Search

\[Rule Abbrev.\]

**Go To** Will invoke the Rule Selection List (Exhibit 3-32) where the
user can select a Rule. The list will display rules based on the search
criterion.

The records will be read from the Rule table where the
Rule_Abbreviation_Text is greater or equal to the text entered in the
Rule Abbrev. field.

[List Columns:]{.underline}

Rule and Name.

[Rule Selection List Default Sort Order:]{.underline} None

![](media/image35.png){width="5.686805555555556in"
height="3.957638888888889in"}

[]{#__RefHeading___Toc139958929 .anchor}**Exhibit 3-32.** Rule Selection
List

[Rule Selection List Buttons:]{.underline}

> **Select** Will be enabled only when the user has selected a record
> from the list. Clicking on the button will close the Rule Selection
> List and return to the Analyte Level Search List with the Rule Abbrev.
> field populated with the selection.

**Cancel** Will return to the Analyte Level Search List.

**Search** Will invoke the following actions:

-   If the Analyte Code and the Rule Abbreviation Code are used as the
    search criteria, the database will be searched for the Analyte Level
    Rule Assignment for the particular Analyte and Rule.

-   If only the Analyte Code is specified as the search criterion, the
    database will be searched for the Analyte Level Rule Assignment for
    the particular Analyte.

-   If only Rule Abbreviation Code is entered as the search criterion,
    the database will be searched for the Analyte Level Rule Assignment
    for that particular Rule.

-   If nothing is entered, then the database will be searched for the
    Analyte Level Rule Assignment for the all Analytes and Rules.

**Cancel** Will return to the *SDWIS/STATE Home Page*.

**Help** Will invoke online Help for this page.

####  Analyte Level Maintenance List

The Analyte Level Maintenance List (Exhibit 3-33) will be presented when
the user clicks **Search** in Analyte Level Search. The software will
search the database for the Analyte Levels for the specified search
criteria (Analyte Code/Rule or both) and display the results in the
Analyte Level Maintenance List.

[List Columns:]{.underline}

Analyte Code, Analyte Name, Contaminant Level \[Threshold Type Code\],
Detection Level \[Measure Level Type Code\], Measure, Measure Unit, MCL
Compliance Method, Begin Date, End Date, Rule.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page*.

**Edit**

*Add* Will be available regardless of a selection having been made in
the list. Will invoke the Analyte Level Maintenance page in Add mode.

*Change* Will be available when a record is selected from the list.
Clicking on this menu item or double-clicking the record will take the
user to the Analyte Level Maintenance page in Change mode.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image36.png){width="1.5395833333333333in"   ![](media/image37.png){width="4.294444444444444in"
  height="5.625694444444444in"}                         height="3.127083333333333in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958930 .anchor}**Exhibit 3-33.** Analyte Level
Maintenance List

*Delete* Will perform the following preliminary checks:

-   The record cannot be deleted if the Analyte Level Rule Assignment
    state code = "HQ." Error message will be **HQ owned assignment
    cannot be deleted.**

```{=html}
<!-- -->
```
-   If the Analyte Level is related to any Violation or Monitoring
    Requirement, it cannot be deleted. Error message will be **Analyte
    Pairing deletion is disallowed. Pairing is referenced.**

If both these checks pass will invoke the Delete Analyte Level dialog
box (Exhibit 3-34) where the user can delete the record or cancel the
delete operation.

![](media/image38.png){width="5.979166666666667in"
height="2.8958333333333335in"}

[]{#__RefHeading___Toc139958931 .anchor}**Exhibit 3-34.** Delete Analyte
Level

[Delete Analyte Level Buttons:]{.underline}

**OK** When the ANALYTE_LEVEL_RULE_ASGMT Threshold_Type_Code is equal to
"MCL," then the Sample Schedule Monitoring Period Averages associated to
the analyte via a monitoring requirement and sample schedule will have
the D_Last_Updt_TS updated to the current timestamp and the
ANALYTE_LEVEL_RULE_ASGMT record will be deleted.

When the ANALYTE_LEVEL_RULE_ASGMT Threshold_Type_Code is equal to "ACL"
or "TRL," the Sample Schedules associated to the analyte via a
monitoring requirement will have the Monitoring_Assessment_Flag reset to
spaces and the ANALYTE_LEVEL_RULE_ASGMT record will be deleted.

**Cancel** Will return to the Analyte Level Maintenance List.

*Select* Will return the selected row to the requesting page.
(R5000:A.3.5.6.2.a)

**View**

*Filter By* Will invoke a filter dialog box that will allow the user to
filter by Analyte Code, Contaminant Level, Detection Level, and Rule.
Use of this item will enable the Refresh item.

*Refresh* Will be enabled only when the filter criteria has been applied
to the list. Will retrieve the unfiltered list and disable this item.

*Search* Will invoke Analyte Level Search where the user can search by a
given Analyte Code or a given Rule Abbreviation Code. Prior search
criteria will be present.

*Sort* Will invoke the standard Sort dialog box where the list could be
sorted by Rule, Analyte Code, Contaminant Level, and Detection Level.
Three levels of sorting will be supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

The default sort order will be Analyte Code, Rule, Contaminant Level
\[Threshold Type Code\], and Detection Level \[Measure Level Type Code\]
respectively in ascending order.

[Protected Fields:]{.underline}

*Number of rows*

*resulting from the*

*search criteria*

*entered:* This protected field will show the total number of rows that
met the search criteria.

*Number of Rows*

*Displayed:* This protected field will show the total number of rows
that displayed in the list, which may be less than the number of rows
that met the search criteria.

####  Analyte Level Maintenance

The Analyte Level Maintenance page (Exhibit 3-35) will be displayed when
the user selects **Edit/Change** or double-clicks a record in the
Analyte Level Maintenance List.

"HQ" records or those associated to a violation or monitoring
requirement cannot be changed and all fields will be protected.

  ---------------------------------------- ----------------------------------------------------
  ![](media/image39.png){width="1.475in"   ![](media/image40.png){width="4.372222222222222in"
  height="5.240972222222222in"}            height="3.3680555555555554in"}

  ---------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958932 .anchor}**Exhibit 3-35.** Analyte Level
Maintenance

[Protected Fields:]{.underline}

*\[Analyte Name\]* The analyte name will be presented when a valid
analyte code has been provided.

*\[Rule Name\]* The name of the rule will be presented when a valid rule
has been provided.

Entry Fields:

*Analyte \[Code\]* In Change mode, the Analyte Code field and the
protected Analyte Name field will already be populated with the Analyte
Code and the Analyte Name based on which Analyte Level record was
selected for change. Both will be protected.

In Add mode, when the user enters the Analyte Code and tabs off the
field, the Analyte Code will be checked for validity. If it is not
valid, then the Analyte Maintenance List will be displayed in
single-select mode. If it is valid, the Analyte Code and the protected
Analyte Name fields will be populated.

Analyte will be a required field.

*Rule \[Code\]* Will denote the Rule Abbreviation field in the Rule
table.

In Change mode, the Rule Code field and the protected Rule Name field
will already be populated with the Rule Code and Rule Name based on
which Analyte Level record was selected for change. Both will be
protected.

In Add mode, when the user enters the Rule Code and tabs off the field,
the Rule Code will be checked for validity. If it is not valid, then the
Rule Selection List will be presented. If it is valid, the Rule Code and
protected Rule Name fields will be populated.

Rule will be a required field.

*Begin Date* Eight-character ANALYTE_LEVEL_RULE_ASSIGNMENT Begin Date,
which indicates the first date of effectiveness for the analyte and rule
assignment. In Change Mode, it will already be populated with the data
from the record that was selected for change.

Begin Date will be a required field.

*End Date* Eight-character ANALYTE_LEVEL_RULE_ASSIGNMENT End Date
representing the last date of effectiveness for the analyte and rule
assignment.

> The End Date field will be optional. If provided, it must be later or
> equal to the Begin Date. The error message will be **End Date must be
> greater than Begin Date.**

*Contaminant Level* Four-character ANALYTE_LEVEL_RULE_ASSIGNMENT
Threshold_Type_Code. Contaminant Level will be a conditionally mandatory
field. If the Detection Level field is valued, the Contaminant Level
field will be protected. The dropdown list will have the following
values:

(SPACES)

ACL Action Level

MCL Maximum Contaminant Level

MCLG Maximum Contaminant Level Goals

TRL Trigger Levels

URTH Unreasonable Risk to Health

*Detection Level* Four-character ANALYTE_LEVEL_RULE_ASSIGNMENT
Measure_Level_Type_Code. The Detection Level field will be conditionally
mandatory. If the Contaminant Level field is valued, the Detection Level
field will be protected. The dropdown list will have the following
values:

(SPACES)

PLR Performance Level Requirement

PQL Practical Quantitative Level

RMDL Regulated Minimum Detection Limit

MRDG Maximum Residual Disinfectant Level

MRDL Maximum Residual Disinfectant Level

Goals

*Measure* Sixteen-character ANALYTE_LEVEL_RULE_ASSIGNMENT Measure_Text.

Measure will be a required field.

*Measure Unit* Nine-character ANALYTE_LEVEL_RULE_ASSIGNMENT UOM_Code.
The dropdown list will have the following values:

(SPACES) %lum

Ug/l %pur

Mg/l Admiu

Count/100 ml Lang

Pci/l Lbs/gal

Cm-1 Lbs/cft

C Ct

F Su

Ntu Aggr

Mrem Mfl

Mremy Umho/cm

Ph Obsvns

Ng/l Count

Ftu Ratio

Ton Units

Cu L/MG-CM

NM (C.3.5.6.3.b) L/MG-M

Measure Unit will be an optional field.

*MCL Compliance*

*Method* Three-character ANALYTE_LEVEL_RULE_ASSIGNMENT
MCL_Compliance_Method. The dropdown list will have the following values:

(SPACES)

MPA\--Monitoring Period Average

RAA\--Running Annual Average

MCL Compliance Method will be an optional field.

[Buttons:]{.underline}

\[Analyte Code\]

**Go To** Will display the Analyte Maintenance List in single-select
mode.

\[Rule\]

**Go To** Will display the Rule Selection List.

**OK**

*Add Mode* Will invoke the following edit checks:

-   If Analyte Code has not been valued, then the following error
    message will be presented: **Analyte** **Code may not be left
    blank.**

-   If the Rule Abbreviation Code has not been valued, then the
    following error message will be presented: **Rule name may not be
    left blank.**

-   If the ANALYTE_LEVEL_RULE_ASSIGNMENT Begin Date has not been valued,
    then the following error message will be presented: **Begin Date
    must not be blank.**

```{=html}
<!-- -->
```
-   If both the ANALYTE_LEVEL_RULE_ASSIGNMENT Contaminant Level and
    Detection Level are not valued, then the following error message
    will be presented: **A Contaminant Level or Detection Level MUST be
    selected.**

-   If the ANALYTE_LEVEL_RULE_ASSIGNMENT Measure has not been valued,
    then the following error message will be presented: **Measure must
    not be blank.**

```{=html}
<!-- -->
```
-   Once these checks pass, the duplicate check will be conducted based
    on the Analyte and the ANALYTE_LEVEL_RULE_ASSIGNMENT
    Measure_Level_Type_Code.

> If a duplicate exists, then the Analyte Level Exists dialog box
> (Exhibit 3-36) will be presented.
>
> ![](media/image41.png){width="4.051388888888889in" height="2.0625in"}

[]{#__RefHeading___Toc139958933 .anchor}**Exhibit 3-36.** Analyte Level
Exists

> Clicking **OK** will invoke the Analyte Level Maintenance page.
>
> If no duplicate exists, then a record will be created in
> ANALYTE_LEVEL_RULE_ASSIGNMENT with the following details and the
> record will then be associated with the ANALYTE and the RULE tables:
> Threshold_Type_Code, Measure_Level_Type_Code, Measure, UOM_Code,
> Begin_Date, End_Date, D_Last_Updt_TS, D_Userid_Code, Measure_Text,
> MCL_Compliance_Method.

**OK**

*Change Mode* Will invoke the following edit checks:

-   If the ANALYTE_LEVEL_RULE_ASSIGNMENT Begin Date has not been valued,
    then the following error message will be presented: **Begin Date
    must not be blank.**

```{=html}
<!-- -->
```
-   If both the ANALYTE_LEVEL_RULE_ASSIGNMENT Contaminant Level and
    Detection Level are not valued, the following error message will be
    presented: **A Contaminant Level or Detection Level MUST be
    selected.**

```{=html}
<!-- -->
```
-   If either the ANALYTE_LEVEL_RULE_ASSIGNMENT Contaminant Level or the
    ANALYTE_LEVEL_RULE_ASSIGNMENT Detection Level changed, then a
    duplicate check will be conducted to see if a record with a
    duplicate Contaminant Level or Detection Level exists. If a
    duplicate exists, then the Analyte Level Exists dialog box (Exhibit
    3-36) will be presented.

> Clicking **Continue** will return the user to the Analyte Level
> Maintenance page.

-   If no duplicate exists, a record will be updated in
    ANALYTE_LEVEL_RULE_ASSIGNMENT.

**Cancel** If no data was changed, the page will close and return to the
maintenance list.

> If the data changed, the standard Cancel Confirm dialog box will be
> presented.

**Help** Will invoke online Help for this page.

### Standard Method

Standard Method has been relocated to the Laboratories and Methods
component. (R0059:A.3.4.7.a)

### Analyte Method Pairings

Analyte Method Pairing has been relocated to the Laboratories and
Methods component. (R0059:A.3.4.8.a)

## Enforcement Support 

### Model Changes for Action Types

No model changes are planned for this release.

### Action Types Page Flows

When the user selects **Enforcement Support/Action Types** from the
*System Administration* menu item on the *SDWIS/STATE Home Page*, the
Action Types Maintenance List page (Exhibit 3-37) will be presented. The
default will be to list action types which are not federally defined.
(Federally Defined = ACTION_TYPE location_type_code equal to 'E' or
'S.') When invoked as the selection list from the *Enforcement Actions*
components, the default will be to list all action types except the
federal types. (Federal Types = ACTION_TYPE location_type_code equal to
'E.')

####  Action Type Maintenance List

Exhibit 3-37 depicts the Action Type Maintenance List page.

  ----------------------------------------------------- -----------------------------------------------------
  ![](media/image42.png){width="1.5305555555555554in"   ![](media/image43.png){width="4.969444444444444in"
  height="5.502083333333333in"}                         height="3.1444444444444444in"}

  ----------------------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958934 .anchor}**Exhibit 3-37.** Action Type
Maintenance List

[List Columns:]{.underline}

Action Type, Rpt to FED as:, Name, Description.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add* Will present the Action Type Maintenance page in add mode.
>
> This item will be available regardless of a selection highlighted in
> the list area.
>
> *Change* Will present the Action Type Maintenance page in change mode
> with the selected action type displayed.
>
> This item will only be available when a selection is highlighted in
> the list area. A double-click on a row in the list area will function
> as this menu item.
>
> *Delete* If the action type is federally defined with a location type
> code of either 'E' or 'S', the error message will be **EPA-defined
> Action Types cannot be deleted.**
>
> If the action type is associated to an Enforcement Action or
> Assistance Action, the error message will be **The Action Type you
> want to delete is already in use by an Enforcement Action or
> Assistance Action and cannot be deleted.** (Exhibit 3-38).
>
> ![](media/image44.png){width="4.6875in" height="2.1666666666666665in"}

[]{#__RefHeading___Toc139958935 .anchor}**Exhibit 3-38.** Action Type
Deletion Conflict

> [Button:]{.underline}
>
> **OK** Will close the conflict and return to the maintenance list.
>
> If no conflicts found, will present the Confirm Action Type Delete
> (Exhibit 3-39).
>
> ![](media/image45.png){width="4.6875in" height="2.4375in"}

[]{#__RefHeading___Toc139958936 .anchor}**Exhibit 3-39.** Confirm Action
Type Delete

> [Buttons:]{.underline}
>
> **Yes** When successfully deleted, the ACTION_TYPE row will be removed
> from the database. The row will be removed from the list display.
>
> **No** The delete request will be aborted and the maintenance list
> displayed with no action taken.
>
> This item will only be available when a selection is highlighted in
> the list area.
>
> *Select* Will close the page and return the selected Action Type to
> the invoking page. When invoked in select-mode, the **Edit/Select**
> menu item will be the only menu item available under the **Edit**
> option for security reasons.

**View**

> *Filter By* Allows for filtering the displayed list to a particular
> Action Type, Rpt to FED As; value, or Name. After selecting the filter
> parameter, the standard filter parameter entry field will be presented
> for the specific data value.
>
> Use of this item will enable the Refresh menu item.
>
> *Refresh* Will remove the filter parameter and redisplay the complete
> list. The redisplay is influenced by the activation status of the
> **Show All** menu item.
>
> *Show All* Will present the Action Type Maintenance List with all
> action types presented, including the federally defined ones. The
> **Show All** menu item will be marked with a checkmark when it is
> active. Choose it again to inactive it which will remove the checkmark
> and return to the default list display, which is determined by the
> invoking process of either System Administration or Enforcement Action
> and is documented above.
>
> *Sort* Will present the standard sort order selection utilized to
> re-sort the displayed list on Action Type, Rpt to Fed As and Name.
> Three levels of sorting will be supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline} Action Type code ascending.

[Protected Fields:]{.underline}

*Number of rows*

*resulting from the*

*search criteria*

*entered:* This protected field will show the total number of rows that
met the search criteria.

*Number of Rows*

*Displayed:* This protected field will show the total number of rows
that displayed in the list that may be less than the number of rows that
met the search criteria.

####  Action Type Maintenance

Exhibit 3-40 depicts the Action Type Maintenance page.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image46.png){width="1.6395833333333334in"   ![](media/image47.png){width="4.172916666666667in"
  height="5.863194444444445in"}                         height="2.548611111111111in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958937 .anchor}**Exhibit 3-40.** Action Type
Maintenance

Action Types that are federally defined, indicated by an action type
beginning with "E" or "S," will be presented as view-only information in
change mode. All fields will be protected.

[Entry Fields:]{.underline}

*Action Type* The three-character code that identifies the action type.
The three characters represent the following information:

First Position Location Type Code

Second Position Formal Type Code

Third Position Subcategory Code

The location type code values of "E" and "S" are reserved for federally
defined action codes and cannot be used for state defined codes.

If the action type already exists in the database, the error message
will be **The Action Type already exists.**

Action Type is a required field.

*Name* The descriptive name assigned to the action type.

Name is a required field.

*Description* A free-form text area to describe the action type.

Description is an optional field.

*Federally Report as:* State-defined action types are useful for state
tracking purposes. In order for actions taken using a state-defined
action type to be included in federal reporting, the state-defined
action type should be associated to a federally-defined action type. The
Federally Report as field allows for the assignment of a state-defined
action type to a federally-defined action type. At federal reporting
time the state action type will be replaced with the selected federal
action type.

If a value is supplied that is not found to be a valid federally-defined
Action Type, the Action Type Maintenance List will be presented in
single-select mode.

This is an optional field.

[Buttons:]{.underline}

*\[Federally Report as:\]*

***Go To*** Will present the Action Type Maintenance List page in
single-select mode. The default is to list only action types beginning
with the 'S' location type code. A button, **Show All Types**, is
available to include the 'E' location type codes in the list.

**OK** If the Action Type field is blank, the error message will be **An
Action Type must be specified.**

If the Action Type field is less than three characters, the error
message will be **Action type MUST consist of 3 characters.**

If the Action Type field begins with "E" or "S," the error message will
be **State Defined Action Type code cannot start with S or E.**

If the Name field is left blank, the error message will be **Please
enter an Action Type Name.**

*Add-Mode* The ACTION_TYPE will be created with the information supplied
on the page. The page will close and return to the maintenance list.

*Change-Mode* If any of the action type (three-character) code, name, or
Report to SDWIS/FED as fields are being modified, the enforcement
actions and assistance actions will be checked. If a usage of the action
type is found by either of those actions, a confirmation dialog box
(Exhibit 3-41) will appear, notifying the user that **The Action Type is
used by an Enforcement Action or Assistance Action. Are you sure you
want to change this Action Type?**

> ![](media/image48.png){width="4.718055555555556in"
> height="2.1666666666666665in"}

[]{#__RefHeading___Toc139958938 .anchor}**Exhibit 3-41.** Confirm Action
Type Change

[Buttons:]{.underline}

> **Yes** Will proceed with the modification of the ACTION_TYPE,
> including the change to the action type code name.
>
> **No** Will abort the change request and return to the maintenance
> list page.

**Cancel** Will invoke the standard cancel confirmation dialog if
changes to entry fields were made, otherwise will return to maintenance
list.

**Help** Will invoke the system online Help facility.

### Model Changes for Activity Types

No model changes are planned for this release.

### Activity Type Page Flows

When the user selects **Enforcement Support/Activity Types** from the
*System Administration* menu *SDWIS/STATE Home Page*, the Activity Type
Maintenance List page (Exhibit 3-42) will be presented.

####  Activity Type Maintenance List

[List Columns:]{.underline}

\[Activity Type\] Name, Category Code, Vio Type and Violation \[Type\]
Name.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add* Will present the Activity Type Maintenance page in add mode.
>
> This item will be available regardless of a selection in the list
> area.
>
> *Change* Will present the Activity Type Maintenance page in change
> mode with the selected activity type displayed.
>
> This item will only be available when a selection is highlighted in
> the list area. A double-click on a row in the list area will function
> as this menu item.
>
> *Delete* If the activity type is associated to a Schedule Activity,
> Standard Response, or Public Notification activity, the error message
> (Exhibit 3-43) will be **The Activity Type you want to delete is
> already in use by a Standard Response or Public Notification activity
> and cannot be deleted.**

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image49.png){width="1.6618055555555555in"   ![](media/image50.png){width="4.186805555555556in"
  height="6.0in"}                                       height="2.6819444444444445in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958939 .anchor}**Exhibit 3-42.** Activity Type
Maintenance List

> ![](media/image51.png){width="4.197916666666667in"
> height="2.3333333333333335in"}

[]{#__RefHeading___Toc139958940 .anchor}**Exhibit 3-43.** Activity Type
Delete Conflict

> OR
>
> Exhibit 3-44 depicts the alternate message box.
>
> ![](media/image52.png){width="4.197916666666667in"
> height="2.3333333333333335in"}

[]{#__RefHeading___Toc139958941 .anchor}**Exhibit 3-44.** Alternative
Activity Type Delete Conflict

> [Buttons:]{.underline}
>
> **OK** Will close the conflict (on either window) and return to the
> maintenance list.
>
> When there are no conflicts, will present the Confirm Activity Type
> Delete (Exhibit 3-45).
>
> ![](media/image53.png){width="4.645833333333333in" height="2.375in"}

[]{#__RefHeading___Toc139958942 .anchor}**Exhibit 3-45.** Confirm
Activity Type Delete

> [Buttons:]{.underline}
>
> **Yes** Will delete the ACTIVITY_TYPE row from the database. The row
> will be removed from the list display.
>
> **No** The delete request will be aborted and the maintenance list
> displayed with no action taken.
>
> This item will only be available when a selection is highlighted in
> the list area.
>
> *Select* Will close the page and return the selected Activity Type to
> the invoking page.

**View**

> *Filter By* Allows for filtering the displayed list to a particular
> category. After selecting the filter parameter the standard filter
> parameter entry field will be presented for the specific data value.
> Violation Type will be added as a filter parameter.
>
> Use of this item will enable the Refresh menu item.
>
> *Refresh* Will remove the filter parameter and redisplay the complete
> list.
>
> *Sort* Will present the standard sort order selection utilized to
> re-sort the displayed list by Name, Category Code or Violation Type.
> Three levels of sorting will be supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline} Name ascending.

[Protected Fields]{.underline}:

*Number of Rows*

*Displayed* This protected field will show the total number of rows that
displayed in the list.

####  Activity Type Maintenance

Exhibit 3-46 depicts the Activity Type Maintenance page.

  ----------------------------------------------------- -----------------------------------------------------
  ![](media/image54.png){width="1.7340277777777777in"   ![](media/image55.png){width="4.0465277777777775in"
  height="6.125694444444444in"}                         height="2.4118055555555555in"}

  ----------------------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958943 .anchor}**Exhibit 3-46.** Activity Type
Maintenance

[Entry Fields]{.underline}:

*Name* The descriptive name assigned to the activity type. If the
provided name already exists in the database, the error message will be
**Activity Type Name not unique.**

Name is a required field.

*Description* A free-form text area to describe the activity type.

Description is an optional field.

*Category Code* A code used to categorize the usage of the activity
type. Permitted values are:

PN -- Activity Types used for Public Notification.

CMPL -- Activity Types used for Compliance Schedules.

This is an optional field. The permitted values presented in the
dropdown list will be retrieved from the CODE table, table_name = "
ACTYPCODE." The permitted value text_value should be concatenated with
the description for the display.

*Violation Type* A two-character code for the violation type to be used
as the default association when the activity type is used for a
compliance schedule. When a violation type is assigned to the Activity
Type, it will display as the default violation type in the Schedule
Activity Maintenance page described in Chapter 6.

Violation Type will be an optional field.

[Tab Sequence:]{.underline}

\[Activity Type\] Name, \[Activity Type\] Description, Category Code,
Violation Type, Violation Type **Go To** button, **OK**, **Cancel**, and
**Help**.

[Buttons:]{.underline}

*\[Violation Type:\]*

***Go To*** Will present the Violation Type Maintenance list in
single-select mode where a violation type may be selected and returned
to the maintenance page along with the name. The Violation Type
Maintenance List should list violation types with the following
characteristics:

-   All state-defined violation types (not = "HQ")

-   "HQ" defined violation types with:

> \- Contaminant Required Code = "MAY" or "NOT"
>
> \- Contaminant Required Code = "MUST" which also have an associated
> analyte

**OK** If the Name field is blank, the error message will be **Name is a
required field and must be entered.**

*Add-Mode* The ACTIVITY_TYPE will be created with the information
supplied on the page. If a Category Code was provided, the code value
will be marked as used. If a Violation Type was provided, the violation
type will be checked according to the following criteria:

-   A state-defined violation types (not = 'HQ')

-   An 'HQ' defined violation types with:

```{=html}
<!-- -->
```
-   Contaminant Required Code = "MAY" or "NOT"

-   Contaminant Required Code = "MUST" which also has an associated
    analyte

> If the violation type fails the above edit, the error message will be
> **Violation Type selected is invalid** and the add will be rejected
> until the invalid violation type is removed. When a valid violation
> type is provided it will be associated to the Activity Type.
>
> The page will close and return to the maintenance list.

*Change-Mode* If the activity type is used by a schedule activity, a
confirmation dialog (Exhibit 3-47) will appear notifying that **The
Activity Type is used by a Public Notice or Compliance Schedule. Are you
sure you want to change this Activity Type?**

> ![](media/image56.png){width="5.479166666666667in"
> height="2.2083333333333335in"}

[]{#__RefHeading___Toc139958944 .anchor}**Exhibit 3-47.** Confirm
Activity Type Change

[Buttons:]{.underline}

> **Yes** Will proceed with the modification of the ACTIVITY_TYPE.
> Changes to the category code will have no affect on the relationships
> already established using this activity type. Changes to the violation
> type will be recorded and the indicated violation type will be
> associated to this activity type. Reference add-mode for edits on the
> characteristics of the selected violation type.
>
> **No** Will abort the change request and return to the maintenance
> page.

**Cancel** Will invoke the standard cancel confirmation dialog.

**Help** Will invoke the system online Help facility.

### Model Changes for Violation Types

No model changes are planned for this release.

### Violation Type Page Flows

When the user selects **Enforcement Support/Violation Types** from the
*System Administration* menu item on the *SDWIS/STATE Home Page*, the
Violation Type Maintenance List page (Exhibit 3-48) will be presented.
The default will be to list only state-owned violation types.

#### Violation Type Maintenance List

Exhibit 3-48 depicts the Violation Type Maintenance List page.

  ---------------------------------------- ----------------------------------------------------
  ![](media/image57.png){width="1.625in"   ![](media/image58.png){width="4.172916666666667in"
  height="5.746527777777778in"}            height="2.473611111111111in"}

  ---------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958945 .anchor}**Exhibit 3-48.** Violation Type
Maintenance List

[List Columns]{.underline}:

Violation Type, Violation Name, Owner, Category, Sample Type, Severity
Level, Tier Level, Fed Rptg Per. Type, Red Rptbl Cont Code.

[Menu Items]{.underline}:

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add* Will present the Violation Type Maintenance page in add mode.
>
> This item will be available regardless of a selection in the list
> area.
>
> *Change* Will present the Violation Type Maintenance page in change
> mode with the selected action type displayed.
>
> This item will only be available when a selection is highlighted in
> the list area. A double-click on a row in the list area will function
> as this menu item.
>
> *Delete* This item will only be available when a selection is
> highlighted in the list area.
>
> If the violation type is associated to a violation, facility analyte
> level as either the monitoring and reporting or level violation type,
> an analyte, an activity type, schedule activity, site visit , or a
> rule, the request will be denied and the error message will be **The
> Violation Type you want to delete is already in use and cannot be
> deleted.** (Exhibit 3-49).
>
> ![](media/image59.png){width="4.197916666666667in"
> height="2.0833333333333335in"}

[]{#__RefHeading___Toc139958946 .anchor}**Exhibit 3-49.** Violation Type
Deletion Conflict

> If no conflict is found, will present the Confirm Violation Type
> Delete (Exhibit 3-50).
>
> ![](media/image60.png){width="4.052083333333333in" height="2.0625in"}

[]{#__RefHeading___Toc139958947 .anchor}**Exhibit 3-50.** Confirm
Violation Type Delete

> [Buttons:]{.underline}
>
> **Yes** The VIOLATION_TYPE row will be removed from the database. The
> row will be removed from the list display.
>
> **No** The delete request will be aborted and the maintenance list
> displayed with no action taken.
>
> *Select* Will close the page and return the selection to the invoking
> page.

**View**

> *Filter By* Allows for filtering the displayed list to a particular
> violation type, violation name, owner, category, sample type, severity
> level, tier level, or Fed Rptble Cont. Code. After selecting the
> filter parameter, the standard filter parameter entry field will be
> presented for the specific data value. This item will only be
> available if there are violation types in the list area.
>
> Use of this item will enable the Refresh menu item.
>
> *Refresh* Will remove the filter parameter and redisplay the complete
> list. The redisplay is influenced by the activation status of the
> **Show All** menu item.
>
> *Show All* Will present the Violation Type Maintenance List with all
> violation types presented, including the federally owned ones. The
> **Show All** menu item will be marked with a checkmark when it is
> active. Choose it again to inactivate it. This will remove the
> checkmark and display only state-owned violation types.
>
> *Sort* Will present the standard sort order selection utilized to
> re-sort the displayed list. This item will only be available if there
> are violation types in the list area. Three levels of sorting will be
> supported.
>
> **Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline} Violation Type (code) ascending.

####  Violation Type Maintenance

Federally-owned violation types cannot be modified and will be presented
for view-only in change mode with all fields protected. Exhibit 3-51
depicts the Violation Type Maintenance page.

SDWIS/STATE users will use SDWIS/FedRep to report data to EPA.

[Protected Fields:]{.underline}

The following two prompts and fields at the bottom of the "Fed" Group
Box will be valued if the Violation Type is federally owned (St_Code =
HQ). Neither prompt nor field should appear on the page when adding a
Violation Type (since only state-owned violation types may be added) or
modifying/displaying a state-owned violation type.

  ----------------------------------------------------- -----------------------------------------------------
  ![](media/image61.png){width="1.4222222222222223in"   ![](media/image62.png){width="4.420138888888889in"
  height="5.125in"}                                     height="3.560416666666667in"}

  ----------------------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958948 .anchor}**Exhibit 3-51.** Violation Type
Maintenance

*Federally Report Number of*

*Missing Samples?* Protected one-character field with either a Y or N.

*Federally Report Number of*

*Exceedences?* Protected one-character field with either a Y or N.

[Entry Fields:]{.underline}

*Violation Type* The two-character code for the violation.

> The violation type will be a required field. It must be unique and if
> it is not, the error message will be **The Violation Type has already
> been used. Please enter another code.**

*Violation Name* The name of the violation type used as a short
description.

> The violation name will be a required field. It must be unique and if
> it is not, the error message will be **The Violation Name has already
> been used. Please enter another name.**

*Violation Category* A classification of the violation type. Permitted
values will be:

(Spaces)

> MCL - Maximum Contaminant Level

MON - Monitoring

PN - Public Notice

RPT - Reporting

SS - Sanitary Survey

TT - Treatment Technique

V/E - Variance and Exemption

Violation Category will be an optional field.

*Severity Level* A code indicating the severity level of the violation
type. Permitted values will be:

*(*Spaces)

MJ - Major

MN - Minor

MX - Single Sample exceeds Maximum level

> 95 - 95% of all samples during the monitoring period should be within
> a desired level
>
> AC - Acute MRDL
>
> NC - Non-acute MRDL
>
> Severity Level will be an optional field.

*Sample Type* The sample type to which the violation type may be
defined. Permitted values will be:

> BO -- Both
>
> NO -- None
>
> RP -- Repeat
>
> RT -- Routine

(Spaces)

Sample Type will be an optional field.

*Tier Level Number* A number indicating the tier level of the violation
type. Permitted values will be 1, 2, 3 or spaces.

Tier Level Number will be an optional field.

*Federally Report Associated*

*Enforcement Actions* This checkbox will indicate if the enforcement
actions associated to violations of this violation type will be
federally reported using SDWIS/FEDREP. When the box is checked, they
will be reported. When unchecked, they will not be reported. The default
will be unchecked.

This is an optional field.

*Fed Reporting*

*Period Type* Describes the definition of the dates reported with
violations of this violation type. Permitted values will be:

> CP -- Compliance Period begin and end dates.
>
> VP -- Violation Period begin and end dates
>
> RA -- Running Annual Average period
>
> QT - Quarterly monitoring period begin and end dates.
>
> (SPACES)

*Fed Reportable*

*Contaminant Code* If violation type is state-owned, the user may
specify the Fed Reportable Contaminant Code (even though a violation
that references one of these is not federally reported). The user may
click the **Go To** button to invoke the Analyte Maintenance List in
single-select mode or may enter a value directly into Analyte Code. The
default sort for Analyte Maintenance List will be Analyte Code in
ascending alphabetical order. If the user enters a value in Code, on
tabbing off the field, the software will accept the specified Code if it
is an exact match (Analyte Code is what the user entered and Analyte
type is "RL") and populate the protected \[Analyte Name\] field. If the
value entered is not an exact match, the software will invoke the
Analyte Maintenance List page in single-select mode, sorted by ascending
Analyte Code, from where the user may select an analyte. If the user
specifies a partial string in this field, display the closest matching
analyte code at the top of the list. (Closest matching means a match
with the Analyte Code, sorted alphabetically, that starts with the same
text string as supplied.) If no match is possible, display the entire
list of rule-type analytes (TYPE_CODE = RL).

> If a federally owned Violation Type is not linked to a "Fed Reportable
> Contaminant Code" analyte, the software will display the string "**Use
> Analyte Code Stored with the Violation**" in the protected Analyte
> Name field.

[Buttons:]{.underline}

\[Fed Reportable

Contaminant Code\]

**Go To** Pressing this button will invoke the Analyte Maintenance List
in single-sort, sorted by Analyte Code in ascending alphabetical order,
showing only analytes of type "RL." This button will be protected if the
violation type is federally-owned.

**OK** If the violation type field is left blank, the error message will
be **Violation Type must not be blank.**

If the violation name field is left blank, the error message will be
**Violation Name must not be blank.**

Add mode Will create a VIOLATION_TYPE with a state code equal to the
primacy agency. Federally owned violation types may only be schema
migrated. If a Fed Reportable Contaminant Code was supplied, the new
VIOLATION_TYPE will be associated to the ANALYTE.

> When successful the page will close and return to the maintenance
> list. The contents of the list will be the state-owned violation
> types, including the newly added one, regardless of the status of the
> **Show All** menu item when invoking the maintenance activity.

Change mode If the violation type is already used for a violation, the
user will be asked to confirm the change by responding to the
notification (Exhibit 3-52): **This Violation Type is in use by a
Violation. Are you sure that you want to change this Violation Type?**

![](media/image63.png){width="4.520833333333333in"
height="2.0208333333333335in"}

[]{#__RefHeading___Toc139958949 .anchor}**Exhibit 3-52.** Confirm
Violation Type Change

[Buttons:]{.underline}

**Yes** Will proceed with the update.

**No** Will stop the change process and return to the maintenance list.

If the violation type is not in use by a violation or the user confirms
the change request, the VIOLATION_TYPE will be updated including
resetting the last update User ID and timestamp to current values.

If the Fed Reportable Contaminant Code was changed from spaces to a
valid analyte, the VIOLATION_TYPE will be associated to the ANALYTE. If
an existing analyte value was removed, the association between
VIOLATION_TYPE and ANALYTE will be removed. If a different analyte was
selected, the association will be removed from the old value and
associated to the new ANALYTE.

> When successful, the page will close and return to the maintenance
> list. The contents of the list will be determined by the status of the
> **Show All** menu item prior to invoke the maintenance activity.

**Cancel** If no changes have been made, will close the page and return
to the maintenance list.

If the value of any field has changed, the standard cancel confirmation
page will be presented.

**Help** Will invoke the system online Help facility.

### Model Changes for Standard Responses

No model changes are planned for this release.

### Standard Response Page Flows

When the user selects **Edit/Enforcement Support/Standard Responses**
from the *System Administration* menu item on the *SDWIS/STATE Home
Page*, the Standard Response Maintenance List page (Exhibit 3-53) will
be presented.

####  Standard Response Maintenance List

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image64.png){width="1.9361111111111111in"   ![](media/image65.png){width="4.480555555555555in"
  height="7.370833333333334in"}                         height="3.4659722222222222in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958950 .anchor}**Exhibit 3-53.** Standard
Response Maintenance List

[List Columns:]{.underline}

Standard Response (Name) and Type.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add/Violation Standard Response*
>
> Will present the Violation Standard Response Maintenance page in add
> mode.
>
> This item will be available regardless of a selection being
> highlighted in the list area.
>
> *Add/Deficiency Standard Response*
>
> Will present the Deficiency Standard Response Maintenance page in add
> mode.
>
> This item will be available regardless of a selection being
> highlighted in the list area.
>
> *Change* Will present the Violation Standard Response Maintenance page
> when type = "V" or the Deficiency Standard Response Maintenance page
> when type = "D" in change mode with the selected standard response
> displayed.
>
> This item will only be available when a selection is highlighted in
> the list area. A double-click on a row in the list area will function
> as this menu item.
>
> *Delete* Will present the Confirm Standard Response Delete (Exhibit
> 3-54). This item will only be available when a selection is
> highlighted in the list area.
>
> ![](media/image66.png){width="4.751388888888889in" height="2.5in"}

[]{#__RefHeading___Toc139958951 .anchor}**Exhibit 3-54.** Confirm
Standard Response Delete

> [Buttons:]{.underline}
>
> **Yes** When successfully deleted, the STANDARD_RESPONSE row will be
> removed from the database. The row will be removed from the list
> display.
>
> **No** The delete request will be aborted and the maintenance list
> displayed with no action taken.

**View**

> *Details* Will present the Violation Standard Response Maintenance
> page or the Deficiency Standard Response Maintenance in view mode with
> only the Cancel and Help buttons enabled. All other fields and buttons
> will be protected or disabled.
>
> This item will be available only when a single selection is
> highlighted in the list area.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline} Violation Type (name) ascending.

####  Violation Standard Response Maintenance

Exhibit 3-55 depicts the Violation Standard Response Maintenance page.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image64.png){width="1.9680555555555554in"   ![](media/image67.png){width="4.606944444444444in"
  height="7.501388888888889in"}                         height="3.2715277777777776in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958952 .anchor}**Exhibit 3-55.** Violation
Standard Response Maintenance

[Entry Fields:]{.underline}

*Standard Response*

*Name* A name that describes the standard response. The name must be
unique and if it is not, the error message will be **Standard Response
Name already exists. The name must be unique.**

The name will be a required field.

*Regulating Agency* The regulating agency for the standard response. The
default value will be the legal entity indicated as being the primacy
agency. If a value is provided that is not found in the LEGAL_ENTITY
table, the Legal Entity Maintenance List will be presented in
single-select mode displaying only government agency types. The Legal
Entity Maintenance List will list legal entities beginning with the
supplied value.

Regulating Agency will be a required field.

*Enforcement Actions* This list displays the
STANDARD_RESP_ACTION_TYPE_ASGMT and ACTION_TYPEs that are associated to
the STANDARD_RESPONSE and accommodates the maintenance of the
relationship. The list will contain a maximum of 100 action types sorted
in ascending action type order.

*Action Type* A three-character code that identifies the action type.

*Status Days* The number of days after the violation determination date
when the enforcement action should be taken.

*Status* The status code that should be assigned to the enforcement
action when it is created.

*PN Schedule*

*Activities* This list displays the STANDARD_RESP_ACTIVITY_TYPE_ASGMT
and ACTIVITY_TYPEs that are associated to the STANDARD_RESPONSE and
accommodates the maintenance of the relationship. The list will contain
a maximum of 100 activity types sorted in ascending name order.

*Name* The name of the activity type.

*PN Req Days* The number of days after the violation determination date
that a public notice is required.

*Proof of PN*

*Due Days* The number of days after the violation determination date
when the proof of a public notice is required.

[Buttons:]{.underline}

\[Regulating Agency\]

**Go To** Will present the Legal Entity Maintenance List in
single-select mode where a list of government agency type legal entities
will be presented in ascending name order.

\[Enforcement Actions\]

**Add** Will present the Violation Standard Response Enforcement Action
Type page in add mode.

This button will be enabled regardless of a selection being made in the
list.

**Change** Will present the Violation Standard Response Enforcement
Action Type page in change mode.

This button will be enabled only if a selection is made in the list. A
double-click on a list item will function as this button.

**Delete** Will remove the enforcement action from the list. The
database will not be impacted until the **OK** button is selected.

This button will be enabled only if a selection is made in the list.

\[PN Schedule Activities\]

**Add** Will present the Violation Standard Response PN Schedule
Activity Types page in add mode. If no enforcement action is displayed
of action type SIE or EIE, the error message will be **A standard
response must contain an SIE or EIE action type if activities exists**
and the maintenance page will not open.

This button will be enabled regardless of a selection being made in the
list.

**Change** Will present the Violation Standard Response PN Schedule
Activity Types page in change mode.

This button will be enabled only if a selection is made in the list. A
double-click on a list item will function as this button.

**Delete** Will remove the PN schedule activity from the list. The
database will not be impacted until the **OK** button is selected.

This button will be enabled only if a selection is made in the list.

**OK** If the Standard Response Name field is left blank, the error
message will be **Standard Response Name must not be blank.**

If the Regulating Agency name is left blank, the error message will be
**Regulating Agency must not be blank.**

If no Enforcement Action has been specified, the error message will be
**A standard response must contain at least one action type**.

If no enforcement action is displayed of action type SIE or EIE but a PN
Schedule Activity is displayed, the error message will be **A standard
response must contain an SIE or EIE action type if activities exists.**

*Add Mode* When successful, the STANDARD_RESPONSE will be created and
associated to the GOVERNMENT_AGENCY specified as the regulating agency.
The type_code will be set to "V," indicating a violation standard
response.

For each Enforcement Action specified, a STANDARD_RESP_ACTION_TYPE_ASGMT
will be created and associated to the STANDARD_RESPONSE and ACTION_TYPE.

For each PN Schedule Activity specified, a
STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be created and associated to the
STANDARD_RESPONSE and ACTIVITY_TYPE.

The page will close and return to the maintenance list.

*Change mode* If the standard response name or regulating agency has
changed, the STANDARD_RESPONSE will be updated with the new values.

If a new enforcement action was added, a STANDARD_RESP_ACTION_TYPE_ASGMT
will be created and associated to the STANDARD_RESPONSE and ACTION_TYPE.

If an enforcement action status days or status was changed, the
STANDARD_RESP_ACTION_TYPE_ASGMT will be updated.

If an enforcement action was deleted, the
STANDARD_RESP_ACTION_TYPE_ASGMT will be deleted.

> If a new PN_SCHEDULE_ACTIVITY was added, a
> STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be created and associated to
> the STANDARD_RESPONSE and ACTIVITY_TYPE.

If a PN_SCHEDULE_ACTIVITY PN Req Days or Proof of PN Due Days was
changed, the STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be updated.

If a PN_SCHEDULE_ACTIVITY was deleted, the
STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be deleted.

> The page will close and return to the maintenance list.

**Cancel** If any data of the Standard Response, Enforcement Actions, or
PN Schedule Activities has been modified, the standard cancel
confirmation page will be presented.

If no changes were made or the confirmation answer was No, the page will
close and return to the maintenance list with no changes made.

If the confirmation answer is Yes, the page will function as if the
**OK** button were chosen.

**Help** Will invoke the system online Help facility.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Violation Standard Response Enforcement Action Type

Exhibit 3-56 depicts the Violation Standard Response Enforcement Action
Type page.

[Entry Fields:]{.underline}

*Action Type* A three-character code that identifies the action type. If
a value is entered that is not found to be an existing action type
value, the Action Type Maintenance List will be presented in
single-select mode where a selection can be made.

This will be a required field.

![](media/image68.png){width="4.53125in" height="3.2083333333333335in"}

[]{#__RefHeading___Toc139958953 .anchor}**Exhibit 3-56.** Violation
Standard Response Enforcement Action Type

*Status Days* The number of days after the violation determination date
when the enforcement action should be taken. Negative numbers are
allowed.

This will be an optional field. The default value is 0. If the status
days field is greater than 999, the error message will be **Input must
match this pattern: -ZZ9.**

*Status* The status code that should be assigned to the enforcement
action when it is created.

This will be a required field. Permitted values will be:

> Taken (the default value)
>
> Potential

[Buttons:]{.underline}

\[Action Type\]

Go To Will present the Action Type Maintenance List in single-select
mode. The default will list only federally owned "S" type of enforcement
actions in ascending action type order.

**OK** If the Action Type specified already exists in the Enforcement
Actions list, the error message will be **Action type already exists in
this standard response.**

If the status days field is greater than 999, the error message will be
**Input must match this pattern: -ZZ9.**

When successful, the page will close and the change will be displayed in
the Enforcement Actions list area. Note that no database action has
occurred. All changes will be committed with the **OK** button is
selected on the Violation Standard Response Maintenance page.

**Cancel** Will abort the request and return to the Violation Standard
Response Maintenance page with no action taken.

**Help** Will invoke the system online Help facility.

####  Violation Standard Response PN Schedule Activity Types

Exhibit 3-57 depicts the Violation Standard Response PN Schedule
Activity Types page.

[Entry Fields:]{.underline}

*Name* The name of the activity type. If a value is entered that is not
found to be an existing activity type value, the Activity Type
Maintenance List will be presented in single-select mode where a
selection can be made.

This will be a required field.

*PN Req Days* The number of days after the violation determination date
that a public notice is required. Negative numbers are allowed.

![](media/image69.png){width="5.8125in" height="3.1875in"}

[]{#__RefHeading___Toc139958954 .anchor}**Exhibit 3-57.** Violation
Standard Response PN Schedule Activity Types

This will be a required field. The default will be 0. If the number is
greater than 999, the error message will be **Input must match this
pattern: -ZZ9.**

*Proof of PN*

*Due Days* The number of days after the violation determination date
when the proof of a public notice is required. Negative numbers are
allowed.

This will be a required field. The default will be 0. If the number is
greater than 999, the error message will be **Input must match this
pattern: -ZZ9.**

[Buttons:]{.underline}

\[Name\]

**Go To** Will present the Activity Type Maintenance List in
single-select mode.

**OK** If Name is left blank, the error message will be **Name is a
required field.** The Activity Type Selection List will be presented for
a selection to be made.

> If the Name specified already exists in the PN Schedule Activities
> list, the error message will be **Activity already exists in this
> standard response.**

If the PN Required Due Days field is greater than 999, the error message
will be **Input must match this pattern: -ZZ9.**

> If the Proof of PN Due Days field is greater than 999, the error
> message will be **Input must match this pattern: -ZZ9.**

When successful, the page will close and the change will be displayed in
the PN Schedule Activities list area. Note that no database action has
occurred. All changes will be committed when the **OK** button is
selected on the Violation Standard Response Maintenance page.

**Cancel** Will abort the request and return to the Violation Standard
Response Maintenance page with no action taken.

**Help** Will invoke the system online Help facility.

####  Deficiency Standard Response Maintenance

Exhibit 3-58 depicts the Deficiency Standard Response Maintenance page.

[Entry Fields:]{.underline}

*Standard Response*

*Name* A name that describes the standard response. The name must be
unique and if it is not, the error message will be **Standard Response
Name already exists. The name must be unique.**

The name will be a required field.

[]{.mark}

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image64.png){width="2.0805555555555557in"   ![](media/image70.png){width="4.352083333333334in"
  height="7.93125in"}                                   height="4.023611111111111in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958955 .anchor}**Exhibit 3-58.** Deficiency
Standard Response Maintenance

Compliance Schedule Values

*Regulating Agency* The regulating agency for the standard response. The
default value will be the legal entity indicated as being the primacy
agency. If a value is provided that is not found in the LEGAL_ENTITY
table, the Legal Entity Maintenance List will be presented in
single-select mode for a selection to be made. The Regulating Agency
Selection List will list legal entities beginning with the supplied
value.

Regulating Agency will be a required field.

*Compliance Schedule*

*Type* The type code that will be used to populate the Activity Type of
the Compliance Schedule that is associated to the Site Visit. Permitted
values listed in the dropdown are retrieved from the CODE table,
table_name of 'TENSCHD1."

This will be an optional field.

*Status* The status code that should be assigned to the standard
response. Permitted values will be:

> Final
>
> Proposed
>
> Superceded
>
> (Spaces)

Status will be an optional field.

*Effective Date*

*Days* The number of days after the deficiency water system notification
date that the state can use to calculate the compliance schedule
effective date that is associated to the site visit. If the site visit
has a water system notification date, it is used in the calculation. If
it does not, the water system notification date from the first selected
deficiency will be used, even if the deficiency has a water system
notification date from an earlier site visit.

This will be an optional field. The default will be 0.

*Schedule*

*Activities* This list displays the STANDARD_RESP_ACTIVITY_TYPE_ASGMT
and ACTIVITY_TYPEs that are associated to the STANDARD_RESPONSE and
accommodates the maintenance of the relationship. The list will contain
a maximum of 100 activity types sorted in ascending name order.

*Name* The name of the activity type.

*Due Date Days* The number of days that is added to the deficiency water
system notification date to calculate the deficiency schedule activity
due date.

*Projected Date Days* The number of days added to the deficiency water
system notification date to calculate the deficiency schedule activity
projected date.

[Buttons:]{.underline}

\[Regulating Agency\]

**Go To** Will present the Legal Entity Maintenance List in
single-select mode where a list of legal entities will be presented in
ascending name order.

\[Scheduled Activities\]

**Add** Will present the Deficiency Standard Response Activity Types
page in add mode.

This button will be enabled regardless of a selection being made in the
list.

**Change** Will present the Deficiency Standard Response Activity Types
page in change mode.

This button will be enabled only if a selection is made in the list. A
double-click on a list item will function as this button.

**Delete** Will remove the activity from the list. The database will not
be impacted until the **OK** button is selected.

This button will be enabled only if a selection is made in the list.

**OK** If the Standard Response Name field is left blank, the error
message will be **Standard Response Name must not be blank.**

If the Regulating Agency name is left blank, the error message will be
**Regulating Agency must not be blank.**

*Add Mode* When successful, the STANDARD_RESPONSE will be created and
associated to the GOVERNMENT_AGENCY specified as the regulating agency.
The type_code will be set to "D," indicating a deficiency standard
response.

For each Schedule Activities specified, a
STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be created and associated to the
STANDARD_RESPONSE and ACTIVITY_TYPE.

The page will close and return to the maintenance list.

*Change mode* If the standard response name, regulating agency,
compliance schedule type, status, or effective date days has changed,
the STANDARD_RESPONSE will be updated with the new values.

If a new SCHEDULE_ACTIVITY was added, a
STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be created and associated to the
STANDARD_RESPONSE and ACTIVITY_TYPE.

If a SCHEDULE_ACTIVITY Due Date Days or Projected Date Days was changed,
the STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be updated.

If a PN_SCHEDULE_ACTIVITY was deleted, the
STANDARD_RESP_ACTIVITY_TYPE_ASGMT will be deleted.

> The page will close and return to the maintenance list.

**Cancel** If any data of the Standard Response or Schedule Activities
has been modified, the standard cancel confirmation page will be
presented.

If no changes were made or the confirmation answer was "No," the page
will close and return to the maintenance list with no changes made.

If the confirmation answer is "Yes," the page will function as if the
**OK** button were chosen.

**Help** Will invoke the system online Help facility.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Deficiency Standard Response Activity Types

Exhibit 3-59 depicts the Deficiency Standard Response Activity Types
page.

![](media/image71.png){width="5.8125in" height="3.1875in"}

[]{#__RefHeading___Toc139958956 .anchor}**Exhibit 3-59.** Deficiency
Standard Response Activity Types

[Entry Fields:]{.underline}

*Name* The name of the activity type. If a value is entered that is not
found to be an existing activity type value, the Activity Type
Maintenance List will be presented in single-select mode where a
selection can be made.

This will be a required field.

*Due Date Days* The number of days added to the deficiency water system
notification date to calculate the deficiency schedule activity due
date. Negative numbers are allowed.

This will be a required field. The default will be 0. If the number is
greater than 999, the error message will be **Input must match this
pattern: -ZZ9.**

*Projected*

*Date Days* The number of days added to the deficiency water system
notification date to calculate the deficiency schedule activity
projected date. Negative numbers are allowed.

This will be a required field. The default will be 0. If the number is
greater than 999, the error message will be **Input must match this
pattern: -ZZ9.**

[Buttons:]{.underline}

\[Name\]

**Go To** Will present the Activity Type Maintenance List in
single-select mode.

**OK** If Name is left blank, the error message will be **Name is a
required field.** The Activity Type Selection List will be presented for
a selection to be made.

> If the Name specified already exists in the PN Schedule Activities
> list, the error message will be **Activity already exists in this
> standard response.**

If the Due Date Days field is greater than 999, the error message will
be **Input must match this pattern: -ZZ9.**

> If the Projected Date Days field is greater than 999, the error
> message will be **Input must match this pattern: -ZZ9.**

When successful, the page will close and the change will be displayed in
the Schedule Activities list area. Note that no database action has
occurred. All changes will be committed when the **OK** button is
selected on the Deficiency Standard Response Maintenance page.

**Cancel** Will abort the request and return to the Deficiency Standard
Response Maintenance page with no action taken.

**Help** Will invoke the system online Help facility.

## Permitted Values

### Model Changes for Permitted Values

Changes to CODE (TINCODE):

Resize attribute referencing_attribute_name from 30 to 100 characters.
(R0065:A.3.6.1.a)

Changes to PERMITTED_VALUE (TINPVALS):

-   Resize attribute description from 244 to 1000 characters.
    (R0107:A.3.6.1.b)

### Permitted Values Page Flows

When the user selects **Permitted Values** from the *System
Administration* menu item on the *SDWIS/STATE Home Page*, the Permitted
Value Code Search page (Exhibit 3-60) will be presented.

####  Code Search

Exhibit 3-60 depicts the Permitted Value Code Search page

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image72.png){width="1.6930555555555555in"   ![](media/image73.png){width="4.903472222222222in"
  height="5.215277777777778in"}                         height="3.490972222222222in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958957 .anchor}**Exhibit 3-60.** Permitted
Value Code Search

[Entry Fields:]{.underline}

*Search By*

*Code Name* The value to use on a match equal or greater than the name
field of the CODE table.

This field will be optional. A value in this field will disable the
*Search by Attribute Name* field*.*

*Search By Attribute*

*Name* The value to use on a match equal or greater than the referencing
attribute name field of the CODE table.

This field will be optional. A value in this field will disable the
*Search by Code Name* field*.*

[Buttons:]{.underline}

**Search** Will present the Code Selection List utilizing any provided
search by values.

**Cancel** Will return to the invoking page.

**Help** Will invoke the system online Help facility.

####  Code Selection List

Exhibit 3-61 depicts the Code Selection List page.

[List Columns:]{.underline}

Code Name, Referencing Attribute Name, Characteristic, Value Length,
Decimal Length, Deletion Rule, Description.

[Menu Items:]{.underline}

**File**

Exit Will return to the *SDWIS/STATE Home Page*.

**Edit**

> Values Will present the Code Permitted Value Maintenance List
> displaying the selection highlighted in the list area. This item will
> only be available when a selection has been made.
>
> **View**
>
> Filter By Will filter the list by a value specified for Code Name,
> Attribute Name, or Characteristic. Use of this item will enable the
> Refresh menu item.
>
> Refresh Will present the unfiltered list and then become disabled.

Search Will invoke the Code Search page. Prior values will be present.

> Sort By Will invoke the standard sort page where the list may be
> sorted by Code name, Attribute name, Characteristic, Value Length,
> Decimal Length, Delete Flag, or Description.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image74.png){width="1.538888888888889in"   ![](media/image75.png){width="4.294444444444444in"
  height="4.876388888888889in"}                        height="2.5625in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958958 .anchor}**Exhibit 3-61.** Code Selection
List

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Default Sort Order:]{.underline}

If a code value was entered, the default order is ascending code name.
If an attribute name was entered, the default order is ascending
referencing attribute name. If no search criteria were entered, the
default will be code name ascending.

[Protected Fields:]{.underline}

*Number of rows*

*resulting from the*

*search criteria*

*entered* This protected field will show the total number of rows that
met the search criteria.

*Number of Rows*

*Displayed* This protected field will show the total number of rows that
displayed in the list, that may be less than the number of rows that met
the search criteria.

####  Code Permitted Value Maintenance List

Exhibit 3-62 depicts the Code Permitted Value Maintenance List page.

[Protected Fields:]{.underline}

*Code* All fields in this Group Box describe the code field for which
the list of permitted values applies.

*Code Name* The name of the code. This is used in the application to
access the values.

*Attribute Name* The name of the attribute, usually in another table, to
which the value applies and will eventually be stored. Increase display
size to accommodate new field size. (R0065:A.3.6.2.3.a)

*Description* The description of the code.

*Characteristic* Indicates if the value must be numeric, date, or text.

*Value Length* Indicates the maximum length of the permitted value.

*\[List Area\]*

*Ownership* Indicates the owner of the value. Federally owned values may
not be modified or deleted.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image76.png){width="1.6222222222222222in"   ![](media/image77.png){width="4.170833333333333in"
  height="5.127777777777778in"}                         height="3.526388888888889in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958959 .anchor}**Exhibit 3-62.** Code Permitted
Value Maintenance List

*Values* The actual value and its description separated by a hyphen.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the Code Selection List.

**Edit**

*Add* Will present the Permitted Value Maintenance page in add mode.
This item will be enabled regardless of a selection having been made in
the list area.

*Change* If allowed, will present the Permitted Value Maintenance page
in change mode. This item will only be available if a value is
highlighted in the list area. A double-click in the list area will
function as this item.

If the value is indicated with ownership equals Federal, the error
message will be **This is a Federal (EPA) permitted value and may not be
changed or deleted.**

[Buttons:]{.underline}

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Permitted Value Maintenance

Exhibit 3-63 depicts the Permitted Value Maintenance page.

[Protected Fields:]{.underline}

*Code* All fields in this Group Box describe the code field for which
the list of permitted values apply.

*Code Name* The name of the code. This is used in the application to
access the values.

*Characteristic* Indicates if the value must be numeric, date, or text
format.

![](media/image78.png){width="5.999305555555556in"
height="6.192361111111111in"}

[]{#__RefHeading___Toc139958960 .anchor}**Exhibit 3-63.** Permitted
Value Maintenance

*Attribute Name* The name of the attribute, usually in another table, to
which the value applies and will eventually be stored.

*Description* The description of the code.

*Value Length* Indicates the maximum length of the permitted value.

*Decimal Length* Indicates how many places are to the right of the
decimal place if the characteristic is numeric. This field will not be
displayed for text or date codes.

[Entry Fields:]{.underline}

*Permitted Value* A value that will be allowed in the reference
attribute name. The value must follow the standards established by the
characteristic and value length components of the code. The value must
be unique for the code name and if it is found to exist, the error
message will be **Permitted value already exists.**

If the code characteristic is text and the permitted value is greater
than the code's value length, the error message will be **The value
entered is longer than the length defined for the code.**

If the code characteristic is numeric, the following edits are performed
on the permitted value:

-   The value must be numeric. When it is not, the error message will be
    **Non numeric value is entered in numeric field.**

-   If the value contains a decimal but no decimal places are defined in
    the decimal length field for the code, the error message will be
    **The value entered is not a valid numeric.**

-   If the number exceeds the value length defined, the error message
    will be **The numeric value entered is larger than the allowed
    length.**

-   If the number of decimal places exceeds the defined decimal length
    value, the error message will be **The value entered is to an
    accuracy larger than the allowed decimal length**

Permitted Value will be a required field.

*Description* A text description of the value. Useful if the value is an
encoded value. Increase display size to accommodate new field size.
(R0107:A.3.6.2.4.a)

Description will be an optional field but it is recommended one be
provided.

[Buttons:]{.underline}

**OK** If the permitted value field is left blank, the error message
will be **Permitted Value cannot be left blank.**

Add mode When successful, the PERMITTED_VALUE will be created and
associated to the CODE. The ownership will be set to "ST," indicating it
is controlled by the primacy agency. The referenced code is set to
spaces until the code is actually used. The page will close and return
to the maintenance list with the new values displayed.

Change mode If the permitted value has been referenced within the
application, the following advisory (Exhibit 3-64) will be presented.

> ![](media/image79.png){width="4.749305555555556in" height="2.3125in"}

[]{#__RefHeading___Toc139958961 .anchor}**Exhibit 3-64.** Referenced
Permitted Value Change Confirmation

> [Buttons:]{.underline}

**Yes** When successful, the PERMITTED_VALUE will be updated with the
new value or description. The page will close and return to the
maintenance list with the new values displayed. There will be no effect
on prior usages of the permitted value.

**No** Will cancel the change request.

**Help** Will invoke the system online Help facility.

**Cancel** Will return to the maintenance list with no action taken.

**Help** Will invoke the system online Help facility.

## Treatment

### Model Changes for Processes

No model changes are planned for this release.

### Processes Page Flows

When the user selects **Treatment/Processes** from the *System
Administration* menu item on the *SDWIS/STATE Home Page*, the Treatment
Process Maintenance List page (Exhibit 3-65) will be presented.

####  Treatment Process Maintenance List

  ----------------------------------------------------- -----------------------------------------------------
  ![](media/image80.png){width="1.7694444444444444in"   ![](media/image81.png){width="4.0465277777777775in"
  height="5.51875in"}                                   height="3.2729166666666667in"}

  ----------------------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958962 .anchor}**Exhibit 3-65.** Treatment
Process Maintenance List

[List Columns:]{.underline}

Code, Name, Ownership

[Protected Fields:]{.underline}

*Number of rows*

*Displayed:* The value in this protected field will indicate the number
of treatment processes available for viewing in the list box via the
vertical scroll bar.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the *SDWIS/STATE Home Page*.

**Edit**

> *Add* Will invoke the Treatment Process Maintenance page in add mode.
> This item will be regardless of the selection in the list area.
>
> *Delete* Will attempt to delete the selected treatment process.
> Federally owned treatment processes cannot be deleted. The error
> message will be **Delete of Federally owned treatment process is not
> allowed.**
>
> If the state owned treatment process is associated to an objective,
> the error message will be **The Treatment Process is paired to an
> objective. Cannot Delete Process.**
>
> If available for deletion, the Treatment Process Delete Confirmation
> (Exhibit 3-66) will be presented.
>
> ![](media/image82.png){width="4.666666666666667in"
> height="2.8541666666666665in"}

[]{#__RefHeading___Toc139958963 .anchor}**Exhibit 3-66.** Treatment
Process Delete Confirmation

> [Buttons:]{.underline}
>
> **Yes** Will delete the D_TREATMENT_PROCESS and return to the
> maintenance list with the selection removed.
>
> **No** Will abort the delete request and return to the maintenance
> list with no action taken.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Treatment Process Maintenance

Exhibit 3-67 depicts the Treatment Process Maintenance page.

![](media/image83.png){width="5.540972222222222in"
height="2.926388888888889in"}

[]{#__RefHeading___Toc139958964 .anchor}**Exhibit 3-67.** Treatment
Process Maintenance

[Entry Fields:]{.underline}

*Process Code* The code assigned to identify the treatment process.

Process Code will be a required field.

*Name* The name of the process.

Name will be a required field.

[Buttons:]{.underline}

**OK** If the Process Code is left blank, the error message will be
**The Treatment Process Code is required.** If it is not unique, the
error message will be **Treatment Process with that Code already
exists.**

If the Name is left blank, the error message will be **Treatment Process
Name is required.** If it is not unique, the error message will be
**Treatment Process with that Name already exists.**

When successful, a new D_TREATMENT_PROCESS row will be added with the
d_state_identification_code set to the primacy agency code. The page
will close and return to the maintenance list with the new treatment
process displayed in the list area as state owned.

**Cancel** Will close the page and return to the maintenance list with
no action taken.

**Help** Will invoke the system online Help facility.

### Model Changes for Pairings

No model changes are planned for this release.

### Pairings Page Flows

When the user selects **Treatment/Pairings** from the *System
Administration* menu item on the *SDWIS/STATE Home Page*, the Treatment
Objective Process Pairing Maintenance List page (Exhibit 3-68) will be
presented.

####  Treatment Objective Process Pairing Maintenance List

The Treatment Objective Process Pairing Maintenance List will present a
scrollable list of all treatment object process pairings. A highlighted
row may be selected for return to an invoking page or for deletion. New
associations can be added using the **Edit/Pair** menu item.

[Protected Fields:]{.underline}

*Number of rows resulting from*

*Search criteria entered:* The value in this protected field will show
the number of treatment objective process pairings available for
display.

*Number of rows displayed:* The value in this protected field will
indicate the number of rows available for viewing in the list box with
the vertical scroll bar. This count is influenced by the use of the
filter by menu option.

[List Columns:]{.underline}

*Treatment Objective*

*Code* The code of the treatment objective.

*Name* The name of the treatment objective.

*Treatment Process*

*Code* The code of the treatment process.

  ----------------------------------------- -----------------------------------------------------
  ![](media/image84.png){width="1.6375in"   ![](media/image85.png){width="4.1722222222222225in"
  height="5.499305555555556in"}             height="3.0555555555555554in"}

  ----------------------------------------- -----------------------------------------------------

[]{#__RefHeading___Toc139958965 .anchor}**Exhibit 3-68.** Treatment
Objective Process Pairing Maintenance List

*Name* The name of the treatment process.

*Ownership* The state or headquarter ownership of the pairing.

[Default Sort Order:]{.underline} Treatment Objective Code, ascending,
Treatment Process Code, ascending.

[Menu Items:]{.underline}

**File**

*Exit* Will close the page and return to the invoking page.

**Edit**

> *Pair* Will present the Treatment Objective Process Pairing page
> (Exhibit 3-69) where a new pairing can be created by choosing an
> objective and a process. This option will be available regardless of a
> selection having been made in the list area.
>
> *Select* Will close the page and return the selected pairing to the
> invoking page. This option will only be available when a selection has
> been highlighted in the list area.
>
> *Delete* Will present the pairing delete confirmation (Exhibit 3-69)
> if the pairing is state-owned. If the pairing is owned by
> headquarters, the error message will be **Pairing is not state-owned
> and cannot be deleted.**

![](media/image86.png){width="5.996527777777778in"
height="2.7916666666666665in"}

[]{#__RefHeading___Toc139958966 .anchor}**Exhibit 3-69.** Delete
Treatment Objective Process Pairing

> [Buttons:]{.underline}
>
> **OK** Will delete the d_valid_treat_obj_proc_asgmt record. The
> confirmation will close and the list will be presented with the
> pairing removed.
>
> **Cancel** The confirmation will close and return to the maintenance
> list.

**View**

> *Filter By* Will present the standard sort dialog box where the list
> may be filtered by any of the list columns.
>
> *Refresh* Will return to an unfiltered list. This item will only be
> available if a filter has been applied to the list using the *Filter
> By* option.
>
> *Sort* Will present the standard sort dialog box where the list may be
> sorted by any of the list columns. Three levels of sorting will be
> supported.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Treatment Objective Process Pairing

Exhibit 3-70 depicts the Treatment Objective Process Pairing page.

*Treatment Objectives* This list box contains the Code and Name for
treatment objectives listed in default ascending name order.

*Treatment Processes* This list box contains the Code and Name for
treatment processes listed in ascending code order.

[Buttons:]{.underline}

**\[Treatment Objectives\]**

**Sorted By** Will present the standard sort entry where the treatment
objectives list area can be resorted by code or name.

**\[Treatment Processes\]**

**Sorted By** Will present the standard sort entry where the treatment
processes list area can be resorted by code or name.

**Assign** Will create a new row in the D_VALID_TREAT_OBJ_PROC_ASGMT
table associated to the selected treatment objective and treatment
process. If an assignment between the two selections already exists, the
error message will be **Combination of process and objective already
exists.**

When successful, the two selections will remain highlighted.

This button will only be enabled when a selection has been highlighted
in each of the objectives and processes list area.

**Cancel** Will close the page and return to the menu.

**Help** Will invoke the system online Help facility.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image87.png){width="1.7465277777777777in"   ![](media/image88.png){width="4.048611111111111in"
  height="5.752777777777778in"}                         height="3.2888888888888888in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958967 .anchor}**Exhibit 3-70.** Treatment
Objective Process Pairing

## Monitoring Periods 

Monitoring Period Maintenance has been moved to a System Administration
function.

### Model Changes for Monitoring Periods

Changes to table MONITORING PERIODS (TMNMPRD):

-   Add permitted value of '2M' to type_code field. Description will be
    "Every 2 Months." (R3017:A.3.8.1.a)

-   Add permitted value of '2W' to type_code field. Description will be
    "Every 2 Weeks." (R2013:A.3.8.1.b)

### Monitoring Periods Page Flows

When selecting **Monitoring Periods** from the *System Administration/*
*Compliance Support* menu item on the *SDWIS/STATE Home Page*, the
Monitoring period Search page will be presented.

####  Monitoring Period Search

Exhibit 3-71 depicts the Monitoring Period Search page.

[Entry Fields:]{.underline} These two fields can be used together.

*Type* Will limit the resulting list of monitoring periods to only those
that match the selection. Valid selections are:

ALL TYPES

MN- Monthly WK- Weekly

QT- Quarterly NA- N/A

YR- Yearly 2Y- Every 2 Years

1T- One Time 5Y- Every 5 Years

4H- Every 4 Hours 6Y- Every 6 Years

6M- Every 6 Months 7Y- Every 7 Years

3Y- Every 3 Years 8Y- Every 8 Years

4Y- Every 4 Years 9Y- Every 9 Years

HR- Hourly 10Y- Every 10 years

> DL- Daily 18M -- Every 18 Months

2M- Every 2 Months 2W -- Every 2 Weeks

(R3017:A.3.8.2.1.a) (R2013:A.3.8.2.1.b)

*Begin Date* This is an optional field.

######## [Buttons:]{.underline} {#buttons .unnumbered}

**Search** Will apply the supplied search criteria and display the
resulting list on the Monitoring Period Maintenance List.

**Cancel** Will cancel the search request and return to the page from
which the search was invoked.

**Help** Will invoke the system online Help facility.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image89.png){width="1.7326388888888888in"   ![](media/image90.png){width="4.045138888888889in"
  height="5.502083333333333in"}                         height="2.332638888888889in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958968 .anchor}**Exhibit 3-71.** Monitoring
Period Search

####  Monitoring Period Maintenance List

Exhibit 3-72 depicts the Monitoring Period Maintenance List page.

[Default Sort Order:]{.underline} Descending begin date.

[List Items:]{.underline}

*Type* The monitoring period's type. Values are:

MN- Monthly WK- Weekly

QT- Quarterly NA- N/A

YR- Yearly 2Y- Every 2 Years

1T- One Time 5Y- Every 5 Years

4H- Every 4 Hours 6Y- Every 6 Years

6M- Every 6 Months 7Y- Every 7 Years

3Y- Every 3 Years 8Y- Every 8 Years

4Y- Every 4 Years 9Y- Every 9 Years

HR- Hourly 10Y- Every 10 years

> DL- Daily 18M -- Every 18 Months
>
> 2M- Every 2 Months 2W -- Every 2 Weeks
>
> (R3017:A.3.8.2.2.a) (R2013:A.3.8.2.2.b)

*Name* The name assigned to the monitoring period.

  ----------------------------------------------------- ----------------------------------------------------
  ![](media/image91.png){width="1.7944444444444445in"   ![](media/image92.png){width="4.049305555555556in"
  height="5.625in"}                                     height="2.9291666666666667in"}

  ----------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958969 .anchor}**Exhibit 3-72.** Monitoring
Period Maintenance List

*Begin Date* The date on which the monitoring period is first effective.

*End Date* The date on which the monitoring period is last in effective.

[Protected Items:]{.underline}

*Number of rows*

*resulting from search*

*criteria entered:* The value in this protected field will show the
number of monitoring periods that met the search criteria.

*Number of rows*

*Displayed*: The value in this protected field will indicate the number
of monitoring periods available for viewing in the list box via the
vertical scroll bar.

[Menu Items:]{.underline}

**File**

*Exit* Will return to the page that invoked the list.

**Edit**

> *Add* Will present the Monitoring Period Maintenance page in add mode.
> This item is available regardless of the selection highlighted in the
> list.
>
> *Change* Will present the Monitoring Period Maintenance page in change
> mode populated with the monitoring period selected from the list. This
> item is only available if a selection has been highlighted in the
> list. A double-click on the list box selection will function as an
> edit/change request.
>
> *Delete* Will attempt to delete the monitoring period from the
> database.

If the selected monitoring period has any of the following associations
the delete will be denied.

-   MCL Value. The error message will be **Monitoring Prd has asc to MCL
    Value and cannot be deleted.**

-   Monitoring Period Average. The error message will be **Monitoring
    Prd has asc to Mon Prd Avg and cannot be deleted.**

-   MDBP Summary. The error message will be **Monitoring Prd has asc to
    MDBP Summary and cannot be deleted.**

-   Sample Summary. The error message will be Monitoring Prd has asc to
    Sample Summary and cannot be deleted.

> If the selected monitoring period is associated to a water system, the
> delete will be denied. The Monitoring Period Association List will be
> displayed listing the water systems which are associated to the
> selected monitoring period via the WATER_PERIOD_MON_PER_ASGMT table.
>
> Exhibit 3-73 depicts the Monitoring Period Association List page.

![](media/image93.png){width="5.997916666666667in" height="5.4in"}

[]{#__RefHeading___Toc139958970 .anchor}**Exhibit 3-73.** Monitoring
Period Association List

> [Buttons:]{.underline}
>
> **OK** Will return to the Monitoring Period Maintenance List.
>
> **Help** Will invoke the system online Help facility.

If the monitoring period can be deleted, will present a confirmation
page (Exhibit 3-74) requiring the selection of **OK** or **Cancel**.

> ![](media/image94.png){width="5.405555555555556in" height="2.65625in"}

[]{#__RefHeading___Toc139958971 .anchor}**Exhibit 3-74.** Delete
Monitoring Period Confirmation

[Buttons:]{.underline}

> **OK** The following actions also occur:

-   Each Sample Schedule Monitoring Period Assignment (SSMPA) will be
    read.

-   The sample schedule associated to the SSMPA will have its

> d_last_update_timestamp set to the current date.

-   The sample analytical result associated to the SSMPA will have its
    d_last_update_timestamp updated with the current timestamp.

-   The SSMPA will be deleted.

-   The monitoring period will be deleted.

> **Cancel** Will abort the delete request and return to the maintenance
> page.
>
> *Select* Will return the selected monitoring period to the invoking
> page. When **Edit/Select** is available, no other options under the
> **Edit** option will be available for security reasons.

**View**

> *Search* Will present the Monitoring Period Search page described
> above. Prior search criteria will be present.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

####  Monitoring Period Maintenance

Exhibit 3-75 depicts the Monitoring Period Maintenance page.

  ---------------------------------------------------- --------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image95.png){width="4.05in"
  height="4.909027777777778in"}                        height="2.0930555555555554in"}

  ---------------------------------------------------- --------------------------------------------------

[]{#__RefHeading___Toc139958972 .anchor}**Exhibit 3-75.** Monitoring
Period Maintenance

[Input Fields:]{.underline} (In tab sequence)

*Duration* This field is presented on the two previous pages as the Type
field. It is a descriptor of the elapsed time period that this
monitoring period will cover. The valid selections are:

MN- Monthly WK- Weekly

QT- Quarterly NA- N/A

YR- Yearly 2Y- Every 2 Years

1T- One Time 5Y- Every 5 Years

4H- Every 4 Hours 6Y- Every 6 Years

6M- Every 6 Months 7Y- Every 7 Years

3Y- Every 3 Years 8Y- Every 8 Years

4Y- Every 4 Years 9Y- Every 9 Years

HR- Hourly 10Y- Every 10 years

> DL- Daily 18M- Every 18 Months 2M- Every 2 Months 2W - Every 2 Weeks
>
> (R3017:A.3.8.2.3.a) (R2013:A.3.8.2.3.b)
>
> This is a required field. If left blank, the error message is
> **Monitoring Period Type Code must not be left blank.**
>
> When a selection is made of spaces, the begin and end dates are reset
> to spaces from any value they may have contained.
>
> When a selection is made of other than spaces, one time, or N/A, and
> the begin date has a date value, the end date is calculated.

*Name* The name of the monitoring period, such as JULY97, 2Q97.

> This is a required field. The **OK** button will remain disabled until
> this field has a value.

*Begin Date* The date on which the monitoring period becomes effective.
Only valid dates are allowed. Invalid dates are removed and the
MM/DD/YYYY edit pattern returns in the field. The value may be typed in
entering only the numbers; the slashes will be supplied automatically,
or by utilizing the calendar function available with the entry field.

> This is a required field. The **OK** button will remain disabled until
> this field has a value.
>
> If the duration has a value of other than spaces, 1T (one time) or
> N/A, the end date will be automatically calculated using the duration
> and begin date field values.

*End Date* The last date on which the monitoring period is effective.
Only valid dates are allowed. Invalid dates are removed and the
MM/DD/YYYY edit pattern returns in the field. The value may be typed in
entering only the numbers; the slashes will be supplied automatically,
or by utilizing the calendar function available with the entry field.
The system will automatically supply this date in most cases by
calculating it using the duration and begin date fields.

> This is a required field. The **OK** button will remain disabled until
> this field has a value.
>
> If the duration has a value of other than spaces, one time or n/a, the
> begin date will be automatically calculated using the duration and end
> date field values.

[Buttons:]{.underline}

**OK** Prior to adding or changing the monitoring period, the following
edits are performed:

-   If begin date is on or before the end date, the error message is
    **The Begin Date must be on or before the End Date for the
    Monitoring Period.**

-   If the Duration is blank, the error message is **Monitoring Period
    Type Code must not be blank.**

-   A duplicate check is performed on the name and if one is found with
    an exact match, the error message is **A Monitoring Period with this
    name already exists.**

-   The duplicate criteria for Monitoring Period are: Duration, Begin
    Date, and End Date. If one is found with an exact match on all three
    fields, the error message is **Monitoring Period of same Duration
    and Dates already exists.**

> If all edits are successful, the monitoring period will be created or
> modified, the page will close and return to the Monitoring Period
> Maintenance list.

**Cancel** Will return to the Monitoring Period Maintenance List page.
If data has been entered or changed in the entry fields, the standard
Cancel Confirm page (Exhibit 3-76) will be presented, requiring the user
to select **Yes**, **No**, or **Cancel**.

![](media/image96.png){width="3.341666666666667in" height="1.55in"}

[]{#__RefHeading___Toc139958973 .anchor}**Exhibit 3-76.** Cancel Confirm

**Yes** Will function as if the **OK** button had been selected.

> **No** Will return to the maintenance list page with no action taken
> on the monitoring period.
>
> **Cancel** Will return to the maintenance page with all information
> intact.

**Help** Will invoke the system online Help facility.

## Monitoring Requirement Delete

Because deleting monitoring requirements has a significant impact on
schedules and other data that reference schedules, users requested that
the capability to delete a monitoring requirement be relocated from the
*Monitoring* component to the *System Administration* component, so that
only those with System Administration authority may delete these
records. (All other Monitoring Requirement maintenance activities remain
in *Monitoring*.)

####  Model Changes for Monitoring Requirement

Users should reference Chapter 7 (Monitoring) for Monitoring Requirement
model changes.

####  Monitoring Requirement Page Flows

In order to avoid duplication of the Monitoring Requirement Search and
Maintenance List functions, selecting **Monitoring Requirement Delete**
from the *System Administration/* *Compliance Support* menu item on the
*SDWIS/STATE Home Page* will present the Monitoring Requirement Search
page described in Chapter 7.

Following execution of the Monitoring Requirement Search web page, the
Monitoring Requirement Maintenance List will be presented where all
options under the **Edit** menu item (R0131:A.3.9.1.2.a) will be
enabled. The Monitoring Requirement Maintenance List will be supplied a
value to indicate that it was invoked from the *System Administration*
component; this is the *only* component in which the user may expect to
see the **Edit/Delete** option enabled on this list.

Selecting **Edit/Delete** on the Monitoring Requirement Maintenance List
will display a delete confirmation page for the selected monitoring
requirement record. This option will be enabled only when a monitoring
requirement record has been highlighted and the function has been
invoked from the *System Administration* component. Two edit checks will
be possible:

-   A monitoring requirement record cannot be deleted if it is a
    federally owned record. If a user tries to delete a federally owned
    monitoring requirement record, provide the following exit state
    error message: **This is a federally owned monitoring requirement
    record and cannot be deleted.** If the record is federally owned, do
    not execute the following reference check.

-   If the user selects for deletion a state-owned monitoring
    requirement, the software will display a delete confirmation page
    (Exhibit 3-77) for the selected Monitoring Requirement that says:
    *Are you sure you want to delete this Monitoring Requirement?
    Deleting it will also delete all Sample Schedules which reference
    it.* The page will have two buttons: **Yes** and **No**. The
    monitoring requirement cannot be deleted if it is referenced by an
    about-to-be-deleted schedule, which in turn is associated with a
    validated or preliminary violation (associated violation's
    D_CURRENT_STATUS_TYPE_CODE is "V" or "P"). If the software
    encounters this situation, it will invoke exit state error message:
    **Monitoring Rqt links to a schedule(s) that references a
    violation\--cannot delete*.***

![](media/image97.png){width="5.926388888888889in"
height="3.9159722222222224in"}

[]{#__RefHeading___Toc139958974 .anchor}**Exhibit 3-77.** Monitoring
Requirement Delete Confirmation

> \- If the user presses **Yes**, the software will delete the
> monitoring requirement, all sample schedules that may reference that
> monitoring requirement, and all SSMPAs that may reference the
> about-to-be-deleted schedule. Note that when an SSMPA is deleted, any
> Sub-SSMPA records that reference it will be automatically (cascade)
> deleted. Prior to deleting each SSMPA and Sub-SSMPA, the Last Update
> Timestamp field of each Sample Analytical Result that is associated
> with the SSMPA or Sub-SSMPA will be set to the current timestamp (so
> that these will be re-assessed by *CDS Setup* the next time it runs).
> Before deleting an associated Sample Schedule, delete any association
> between the Sample Schedule and a deleted or rejected Violation.
>
> \- If the user presses **No**, no action will be taken, the page will
> close, and return the user to the Monitoring Requirement Maintenance
> List.

## Non-TCR Schedule Template

Non-TCR Schedule Template is a function that allows a group of
monitoring requirements to be defined. This definition can then be used
in the *Monitoring* component to step through the creation of multiple
Non-TCR Schedules for each of the monitoring requirements defined in the
Template set. Reference Chapter 7 on the utilization of a Non-TCR
Schedule Template for creating new Non-TCR Schedules.

###  Model Changes for Non-TCR Schedule Template

No model changes are planned for this release.

###  Non-TCR Schedule Template Page Flows

When the user selects **Non-TCR Schedule Template** from the *System
Administration/Compliance Support* menu item on the *SDWIS/STATE Home
Page*, the Non-TCR Schedule Template Maintenance List page (Exhibit
3-78) will be presented.

Exhibit 3-78 depicts the Schedule Template List page.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image98.png){width="4.170138888888889in"
  height="4.909027777777778in"}                        height="3.048611111111111in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958975 .anchor}**Exhibit 3-78.** Schedule
Template List

[List Column:]{.underline} Template Name

[Default Sort Order:]{.underline} Template Name Ascending

[Menu Items:]{.underline}

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add* Will present the Non-TCR Schedule Template Maintenance page in
> add mode.
>
> *Change* Will present the Non-TCR Schedule Template Maintenance page
> in change mode with the selected template displayed. This item will
> only be available if a selection is made in the list area.
>
> *Delete* Will present the Non-TCR Schedule Template Delete
> confirmation page.
>
> [Buttons:]{.underline}
>
> **OK** Will remove the Non-TCR Schedule Template from the database and
> return to the Non-TCR Schedule Template Maintenance List with this
> template removed.
>
> **Cancel** Will abort the delete request and return to the Non-TCR
>
> Schedule Template Maintenance List
>
> *Select* Will close the page and return the selection to the invoking
> page. When the **Edit/Select** item is enabled no other items under
> **Edit** will be allowed for security reasons. This item will not be
> available when invoked from the *System Administration* component.

**Help** Will invoke the system online Help facility.

[Buttons:]{.underline}

**Menu Items** Will present the standard menu items dialog box.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

[Protected Fields:]{.underline}

*Number of rows*

*Displayed*: The value in this protected field will indicate the number
of Non-TCR Schedule Templates available for viewing in the list box via
the vertical scroll bar.

#### Schedule Template Maintenance 

Exhibit 3-79 depicts the Schedule Template Maintenance page.

  ---------------------------------------------------- ----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image99.png){width="4.159722222222222in"
  height="4.909027777777778in"}                        height="3.783333333333333in"}

  ---------------------------------------------------- ----------------------------------------------------

[]{#__RefHeading___Toc139958976 .anchor}**Exhibit 3-79.** Non-TCR
Schedule Template Maintenance

[Entry Fields:]{.underline}

*Template Name* The name of the Non-TCR Schedule template. It must be
unique among existing templates. When tabbing off or clicking outside of
this field, if the name is not unique, the error message will be
**Template Name must be unique.**

This will be a required field.

New Monitoring Requirement

Group Box This Group Box contains fields that are necessary to identify
a new requirement for inclusion in the template. Populating the fields
in this Group Box and then choosing the **Add** button will populate the
monitoring requirement into the list box below. When **OK** is pressed,
the list box will be processed and new monitoring requirements will be
associated to the Schedule Template.

*Analyte Code* The four-character analyte code for which the monitoring
requirement applies.

> This field will map to table TSAANLYT, column CODE. As the user enters
> data and tabs off this field or clicks out of it, the Analyte Group
> Code and **Go To** button will be protected. Conversely, clearing this
> field of data (that is, backspacing or deleting from the field), will
> enable the Analyte Group Code and **Go To** button. A value may be
> entered, selected from a list by clicking the **Go To** button, or
> left blank. If the user specifies a complete Analyte Code, the
> software will attempt an exact match. If an exact match is found, the
> software will retrieve the analyte and populate the protected Analyte
> Name field. If an exact match is not found or the user specifies a
> partial string in this field, the software will display the closest
> matching analyte code at the top of the Analyte Maintenance List
> presented in single-select mode. (Closest matching means a match with
> the Analyte Code, sorted alphabetically, that starts with the same
> text string as supplied.) If no match is possible, the software will
> display the entire list of analytes. The default sort for this search
> will be Analyte Code in ascending alphabetical order. Clicking the
> **Go To** button will display the Analyte Maintenance List in
> single-select mode (minus Analytes 3100, CU90, PB90, and any analytes
> of type "GC" and "OT") with the same default sort.
>
> This will be an optional field but either Analyte code or Analyte
> Group Code will be required to designate a monitoring requirement.

*Analyte Group Code* The four-character Analyte Group Code.

> This field will map to table TSAANGRP, column CODE. As the user enters
> data and tabs off this field, the Analyte Code and **Go To** button
> will be protected. Conversely, clearing this field of data (that is,
> backspacing or deleting from the field) will enable the Analyte Code
> and **Go To** button. A value may be entered, selected from a list by
> clicking the **Go To** button, or left blank. If the user specifies a
> complete Analyte Group Code, the software will attempt an exact match.
> If an exact match is found, the software will retrieve the analyte
> group and populate the protected Analyte Group Name field. If an exact
> match is not found or the user specifies a partial string in this
> field, the software will display the closest matching analyte group
> code at the top of the Analyte Group Maintenance List in single-select
> mode. (Closest matching means a match with the Analyte Group Code,
> sorted alphabetically, that starts with the same text string as
> supplied.) If no match is possible, the software will display the
> entire list of analyte groups. The default sort for this search will
> be Analyte Group Code, in ascending alphabetical order. Clicking the
> **Go To** button will display the Analyte Group Maintenance List in
> single-select mode with the same default sort.
>
> This will be an optional field, but either Analyte code or Analyte
> Group Code will be required to designate a monitoring requirement

*Sampling Frequency* A Group Box with the Monitoring Requirement fields.

*Samples Required* Specifies the number of samples to be taken.

This field will be required to designate a monitoring requirement for
inclusion in the template.

*\[Sample Type\]* Specifies the type of sample to be taken. This is a
standard, protected dropdown list box containing the following permitted
values:

> \<NONE\>
>
> TR Temporary Routine

CO Confirmation

RP Repeat

RT Routine

SP Special

> OT Other

This field will be required to designate a monitoring requirement for
inclusion in the template.

*\[Sampling Frequency*

*Sample Periodicity\]* Specifies the period of time in which the sample
is to be taken. This is a dropdown list box containing the following
permitted values:

\<NONE\>

HR Hourly

4H Every 4 Hours

DL Daily

WK Weekly

> 2W Every 2 Weeks

MN Monthly

> 2M Every 2 Months
>
> (R3017:A.3.10.2.2.a)

QT Quarterly

6M Every 6 Months

> YR Yearly

18M Every 18 Months

2Y Every 2 Years

3Y Every 3 Years

4Y Every 4 Years

5Y Every 5 Years

6Y Every 6 Years

7Y Every 7 Years

8Y Every 8 Years

9Y Every 9 Years

10Y Every 10 Years

1T One Time

This field will be required to designate a monitoring requirement for
inclusion in the template.

*M&R Violation*

*Type* The violation type used to report M&R noncompliance to this
monitoring requirement.

This field will be optional. Note that specification of this field is
important to the selection of the appropriate monitoring requirement and
is a component of the uniqueness criteria for monitoring requirements.
The absence of this field will indicate that the monitoring requirement
matching the other three sample frequency fields must NOT contain an M&R
Violation Type association.

[Template Contents]{.underline}

[List Items:]{.underline}

*Analyte Code* The analyte code (or analyte group code) of the
monitoring requirement.

*Frequency* The number of samples required by the monitoring
requirement.

*Type* The type of samples required by the monitoring requirement.

*Every* The unit of time in which the samples should be collected
specified by the monitoring requirement.

*M&R Violation*

*Type* The violation type code that will be issued for a monitoring and
reporting violation of the monitoring requirement.

[Tab Sequence:]{.underline}

Template Name, Analyte Code, Analyte Code **Go To** button, Analyte
Group Code, Analyte Group Code **Go To** button, Sampling Frequency
\[Sample Count, Sample Type, Sampling Frequency/Periodicity\], M&R
Violation Type Code, Monitoring Requirement **Go To** button, **Add**
button, Template Contents List box, **Remove** button, **OK** button,
**Cancel** button, **Help** button.

[Buttons:]{.underline}

\[Analyte Code\]

**Go To** Pressing this button will invoke the Analyte Maintenance List
in single-select mode. The default sort for Analyte Maintenance List is
Analyte Code in ascending alphabetical order. This list should not
include analytes of code 3100, CU90, PB90, or analytes of type "GC"
(group contaminant) or "OT" (other)*.*

\[Analyte Group

Code\] **Go To** Pressing this button will invoke the Analyte Group
Maintenance List in single-select mode. The default sort for Analyte
Group Maintenance List is Analyte Group Code, in ascending alphabetical
order. This list should not include any Analyte Group that contains an
analyte of code 3100, CU90, PB90, or an analyte of type "GC" (group
contaminant) or "OT" (other).

\[Monitoring Requirement\]

**Go To** Will present the Monitoring Requirement Maintenance list in
single-select mode. This button will only be enabled when a valid
analyte or analyte group code has been specified. The list of monitoring
requirements will display only those for the specified analyte or
analyte group code.

**Add** Will utilize the values specified in the New Monitoring
Requirement Group Box to identify an existing Monitoring Requirement. If
a single monitoring requirement can be found, the monitoring requirement
is added to the Template Contents List box below. No fields will be
reset. No database activity occurs at this point.

There is no restriction on a monitoring requirement being included
multiple times in the same template.

If a single monitoring requirement cannot be found, the error message
will be **A monitoring requirement could not be found with the specified
values.**

**Remove** Will remove a selected monitoring requirement from the list
box area and designate it for removal from the template when the **OK**
button is pressed. This item will only be available if a selection has
been made in the List box.

**OK** Will perform the following edits prior to processing:

-   Template Name must not be blank. If it is, the error message will
    be: **Template Name must not be blank.**

-   Template Name must be unique. If it is not, the error message will
    be: **Template Name must be unique.**

> Add Mode Will create a SCHEDULE_TEMPLATE row with the following data
> assignments:

-   Name = Template Name

-   d_initial_user_cd = current User ID

-   d_initial_timestamp = current timestamp

-   d_lastupdate_user_cd = current User ID

-   d_lastupdate_timestamp = current timestamp

-   tmnschtm_is_number from TINEISN

-   tmnschtm_st_code from primacy agency

> For each monitoring requirement in Template Contents, create a
> SCHEDULE_TEMPLATE_MON_REQ row setting D_Userid_Code and
> last_update_timestamp to current values and associate it to the
> SCHEDULE_TEMPLATE and MONITORING_REQUIREMENT. The tmnstmem_is_number
> will be incremented by 1 within the SCHEDULE_TEMPLATE.
>
> When successfully completed, close the page and return to the Non-TCR
> Schedule Template Maintenance List with the new template listed.
>
> Change Mode Will update the SCHEDULE_TEMPLATE with the new name and
> update the D_Userid_Code and last_update_timestamp to current values.
>
> For each monitoring requirement in the Template Contents that is
> marked for removal, delete the SCHEDULE_TEMPLATE_MON_REQ.
>
> For each new monitoring requirement in the Template Content, process
> according to the rules documented above in add mode.

**Cancel** If no changes have been made to either the name or the
Template Contents list box, the page will close and return to the
Non-TCR Schedule Template Maintenance List with no action taken. If a
change has been made, the standard cancel confirmation dialog box will
be presented.

**Help** Will invoke the system online Help facility.

## SDWIS Configuration Setup

This function is used to enable/disable processing controls within the
SDWIS/STATE application. The first implementation will be to control
enabling of Lab Certification edits for Sample Maintenance. (R2001,
R3001:A.3.11.a)

### Model Changes for SDWIS Configuration

Create new entity CONFIGURATION. (R2001, R3001:A.3.11.1.a)

Subject Area: Lookup_Tables

Description: This table serves as a \"configuration\" table for
SDWIS/STATE. Initially, this table primarily determines level of editing
for laboratory certification in sample/sample result maintenance. The
expectation is that in the future, this table will grow as
states/regions wish to add control on some other edit checks.

Physical name: TINCFG

Attributes:

> Cfg_Id (char, 10, mandatory). Configuration ID.
>
> Cfg_Desc (varchar, 2000, optional, case sensitive). A text description
> of the configuration.

Identifier: Cfg_Id.

Create new entity PARAMETER.

Subject Area: Lookup_Tables

Description: This table will contain the configuration parameters.

Physical name: TINPARAM

Attributes:

> Param_Value (varchar, 40, mandatory, case sensitive). Receives
> permitted values from the PERMITTED_VALUE table where the parent CODE
> table is associated to the PARAMETER table.
>
> D_Last_Updt_Ts (timestamp, mandatory) Description: The timestamp at
> the update of the record.
>
> D_Last_Updt_Userid (Text, 8, mandatory) Description: The User ID of
> the last person to modify this record.

D_Initial_Ts (timestamp, mandatory) Description: The timestamp at the
creation of the record.

> D_Initial_Userid (text, 8, mandatory) Description: The User ID of the
> creator of the record.

Relationship:

> Each PARAMETER always belongs to one CONFIGURATION (non transferable,
> disassociate).
>
> Each CONFIGURATION sometimes has one or more PARAMETER (non
> transferable, disallow delete).
>
> Each PARAMETER always records name in one CODE (non transferable,
> disassociate).

Each CODE sometimes is a name for one or more PARAMETER (non
transferable, disallow delete).

Identifier: Relationship (foreign key) from Configuration (TINCFG) and
relationship (foreign key) from Code (TINCODE

This section documents the table content changes and schema migration
needed to support SDWIS Configuration Setup.

Changes to CONFIGURATION (TINCFG):

New Configuration table row for Laboratory Certification.

  -----------------------------------------------------------------------
  **Column Name**               **Value**
  ----------------------------- -----------------------------------------
  Cfg_Id                        LABCERT

  Cfg_Desc                      Laboratory Certification
  -----------------------------------------------------------------------

Changes to PARAMETER (TINPARAM):

New Parameter table row for Laboratory Certification Edit Check.

  -----------------------------------------------------------------------
  **Column Name**               **Value**
  ----------------------------- -----------------------------------------
  (FK) Cfg_Id                   LABCERT

  (FK) Code_Name                LC_EDITCHK

  Param_Value                   ERROR

  D_Userid_Code                 SS2.0

  D_Last_Updt_Ts                1/1/2007

  D_Initial_Userid              SS2.0

  D_Initial_Ts                  1/1/2007
  -----------------------------------------------------------------------

Changes to CODE (TINCODE): (R2001, R3001:A.3.11.1.b)

New Code table row for Laboratory Certification Edit Check.

+----------------------------+-----------------------------------------+
| **Column Name**            | **Value**                               |
+============================+=========================================+
| Code_Name                  | LC_EDITCHK                              |
+----------------------------+-----------------------------------------+
| Cod_Characteristic         | T                                       |
+----------------------------+-----------------------------------------+
| Value_Length               | 6                                       |
+----------------------------+-----------------------------------------+
| Delete_Flag                | A                                       |
+----------------------------+-----------------------------------------+
| Ownership_Code             | ST                                      |
+----------------------------+-----------------------------------------+
| D_Userid_Code              | SS2.0                                   |
+----------------------------+-----------------------------------------+
| D_Last_Updt_Ts             | 1/1/2007                                |
+----------------------------+-----------------------------------------+
| Ref_Attribute_Name         | TINPARAM.Code_Name                      |
|                            |                                         |
|                            | (B.3.11.1.a)                            |
+----------------------------+-----------------------------------------+
| Description_of_Cod         | This parameter is used to control       |
|                            | laboratory certification editing.       |
+----------------------------+-----------------------------------------+

Changes to PERMITTED_VALUE (TINPVALS) (R2001, R3001:A.3.11.1.c)

New Permitted Value table rows for Laboratory Certification Edit Check.

  -----------------------------------------------------------------------
  **Column Name**               **Value**
  ----------------------------- -----------------------------------------
  Code_Name                     LC_EDITCHK

  Sequence_Number               *Incremented by +1 for each Text_Value
                                below.*

  Numeric_Value                 Null

  Date_Value                    Null

  Ownership_Code                ST

  D_Userid_Code                 SS2.0

  D_Last_Updt_Ts                1/1/2007
  -----------------------------------------------------------------------

Table of Text Values, Referenced Indicators, and Descriptions:

+-------------+-------------+-----------------------------------------+
| **Text\_**  | Ref\_       | **Description**                         |
|             |             |                                         |
| **Value**   | Indicator   |                                         |
+-------------+-------------+-----------------------------------------+
| ADVISE      | Spaces      | Perform laboratory certification edit   |
|             |             | but only generate an advisory           |
+-------------+-------------+-----------------------------------------+
| ERROR       | Y           | Perform laboratory certification edit   |
|             |             | but generate an error                   |
+-------------+-------------+-----------------------------------------+
| NOTIMP      | Spaces      | Do not perform laboratory certification |
|             |             | editing                                 |
+-------------+-------------+-----------------------------------------+

### SDWIS Configuration Setup Page Flow

From the *SDWIS/STATE Home Page* the user selects **System
Administration/SDWIS Configuration Setup** to invoke the SDWIS
Configuration Setup page (Exhibit 3-80).

#### SDWIS Configuration Setup

The SDWIS Configuration Setup (Exhibit 3-80), which will display a
maximum of 50 records, will list the parameter records available in
SDWIS/STATE. One selection may be made in the list.

Deletion and Addition of records will not be supported in this page.

The SDWIS Configuration Setup page is depicted below.

  ---------------------------------------------------- -----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image100.png){width="4.471527777777778in"
  height="4.909027777777778in"}                        height="4.2659722222222225in"}

  ---------------------------------------------------- -----------------------------------------------------

**Exhibit 3-80.** SDWIS Configuration Setup

\[Configuration List Box\]:

[List Column:]{.underline}

Configuration ID, Parameter Name, and Parameter Value.

[Default Sort Order:]{.underline}

The default sort order will be ascending Configuration ID and ascending
Parameter Name.

*Maintain Parameter*

*Group Box* When a selection is made in the list, the maintain parameter
fields will be populated with the values from the selected row. The
parameter value can be modified with a new value. The change will be
processed via the **OK** button.

If no selection is made in the list, these fields will be blank.

[Protected Fields]{.underline}:

*Number of rows*

*displayed:* Will show the total number of rows that are displayed in
the list.

*Configuration ID* Will be the Configuration ID of the selected record.

*Configuration*

*Description* Will be the text description of the Configuration ID.

*Parameter Name* Will be the name of the parameter.

*Parameter*

*Description* Will be the text description of the parameter.

*Record updated*

*by/on* The User ID and the timestamp from the last time the parameter
record was updated.

*Record created*

*by/on* The initial User ID and timestamp when the parameter record was
initially added to the database.

[Entry Fields:]{.underline}

*Parameter Value* A standard dropdown list with permitted values
controlled by the SDWIS/STATE Administrator using the Permitted Values
function. The permitted values available from the dropdown will be
retrieved from the TINPVALS table via the association of the parameter
(TINPARAM) to the code (TINCODE).

The Parameter Value field will be mandatory. It will be enabled when a
selection has been made in the list.

[Buttons:]{.underline}

**Exit** Will close the page and return to the *SDWIS/STATE Home page*
without saving any changes made to the parameter value.

**Scroll Buttons** Will scroll the list box in the direction of the
arrow displayed on the button.

**OK** If the parameter value field is left blank, the error message
will be **Parameter Value cannot be left blank.**

Will update the PARAMETER record when the parameter value field is
changed. The D_Userid_Code and D_Last_Updt_Ts will be set to current
values.

The page will be redisplayed with the selected record updated in the
list.

This button will be enabled when a selection has been made in the list.

**Cancel** Will disregard data entered without presenting the standard
Cancel Confirm dialog box. The page will be redisplayed with the
selected record still highlighted and the maintain parameter fields
populated with the selected record.

This button will be enabled when a selection has been made in the list.

[Tab Sequence:]{.underline}

**Exit,** Parameter Value, **OK**, and **Cancel**.

## Deficiency Types

This function is used to support the specification of Deficiency Type
Codes and default values for those Deficiency Types.

### Model Changes for Deficiency Types

Documented in Chapter 8 section on Deficiencies.

###  Deficiency Type Page Flow

The Deficiency Type page flows support the display, creation, and
maintenance of Deficiency Types. (R2014:A.3.13.2.1.a)

#### Deficiency Type Maintenance List

From the *SDWIS/STATE Home Page* the user selects **System
Administration/Compliance Support/Deficiency Types** to invoke the
Deficiency Types Maintenance List page (Exhibit 3-81).

  ---------------------------------------------------- -----------------------------------------------------
  ![](media/image1.png){width="1.9368055555555554in"   ![](media/image101.png){width="4.231944444444444in"
  height="4.909027777777778in"}                        height="4.89375in"}

  ---------------------------------------------------- -----------------------------------------------------

**Exhibit 3-81.** Deficiency Type Maintenance List

[List Column:]{.underline}

Type Code, Default Severity Code, Default Category Code, Description.

[Default Sort Order:]{.underline}

The default sort order will be ascending Type Code

[Menu Items]{.underline}

**File**

*Exit* Will return to the invoking page.

**Edit**

> *Add* Will invoke the Deficiency Type Maintenance page (Exhibit 3-82)
> in add mode.
>
> *Change* Will invoke the Deficiency Type Maintenance page (Exhibit
> 3-82) in change mode. Will remain disabled until a selection is
> highlighted in the list.
>
> *Select* Will return the selected Deficiency Type to the invoking
> page. Will remain disabled until a selection is highlighted in the
> list.

**View**

> *Filter By* Will present the standard Filter By dialog box where a
> value may be provided to filter the list area. Filter By options will
> be Type Code, Default Severity Code, and Default Category Code.
>
> *Refresh* Will remove the previously requested filtering criteria and
> return to the default list.
>
> *Sort* Will present the standard Sort dialog box where the list area
> can be sorted by Type Code, Default Severity Code, and/or Default
> Category Code.

[Protected Fields]{.underline}

*Number of Records*

*Displayed:* Displays a count of the number of rows presented in the
list area.

[Buttons]{.underline}

**Menu Items** Will present the standard Menu Items dialog box with
buttons representing each of the menu item options.

#### Deficiency Type Maintenance

Exhibit 3-82 depicts the Deficiency Type Maintenance page.

  ---------------------------------------------------- -----------------------------------------------------
  ![](media/image1.png){width="1.8756944444444446in"   ![](media/image102.png){width="4.153472222222222in"
  height="4.909027777777778in"}                        height="4.884722222222222in"}

  ---------------------------------------------------- -----------------------------------------------------

**Exhibit 3-82.** Deficiency Type Maintenance

[Protected Fields:]{.underline}

*Record Created* *By/on* Displays the User ID and timestamp of when the
Deficiency Type was created.

*Record* *Updated* *By/on* Displays the User ID and timestamp of when
the Deficiency Type was last updated.

[Entry Fields]{.underline}

*Type Code* A four-character type code. The type code must be unique. If
a Deficiency Type already exists with this type code the error will be
**Deficiency Type Code already exists.**

Type Code is a required field. If it is not provided the error message
will be **Deficiency Type Code cannot be left blank.**

*Default Severity Code* The default severity code is used to populate
the severity code on the Deficiency when this Deficiency Type is
selected. Permitted Values are:

\<NONE\>

\<spaces\>

MIN -- Minor

REC -- Recommendation

SIG -- Significant

Default Severity Code is an optional field.

*Default Category Code* The default category code is used to populate
the category code on the Deficiency when this Deficiency Type is
selected. Permitted Values are:

*\<spaces\>*

*\<NONE\>*

DS -- Distribution System

FI -- Financial

FW -- Finished Water

MR -- Monitoring and Reporting

OC -- Operator Compliance

OT -- Other

PU -- Pumping Facility

SE -- Security

SM -- System Management

SO -- Source

TR -- Treatment

UK - Unknown

Default Category Code is an optional field.

*Description* A free-form text area to describe the Type Code.

Description is an optional field.

[Buttons]{.underline}

**OK** If the Type Code is a unique value, a new Deficiency Type row
will be created. The tindftyp_is_number will be set from the TINEISN
table.

The page will close and the new Deficiency Type will be presented on the
Deficiency Type Maintenance List.

**Cancel** The page will close and return to the Deficiency Type
Maintenance List. No action will be taken on the Deficiency Type.

**Help** Will open the online Help facility for this page.