+------------------------+---------------------------------------------+
| ![](media/image1.png)  | ![](medi                                    |
|                        | a/image3.jpeg){width="1.4583333333333333in" |
| United States          | height="0.7916666666666666in"}**Updated     |
| Environmental          | SDWIS/STATE 2.0 Requirements Document**     |
| Protection Agency      |                                             |
|                        |                                             |
| Office of Ground Water |                                             |
| and Drinking Water     |                                             |
|                        |                                             |
| Contract No. BPA       |                                             |
| OARMSC-SYS-04          |                                             |
|                        |                                             |
| SDWIS Project          |                                             |
|                        |                                             |
| Product Control No.    |                                             |
|                        |                                             |
| S                      |                                             |
| ystalex-SDWIS-01-9.d1a |                                             |
|                        |                                             |
| Deliverable No. 9.d1   |                                             |
|                        |                                             |
| November 21, 2006      |                                             |
+------------------------+---------------------------------------------+

**UPDATED SDWIS/STATE 2.0**

**REQUIREMENTS DOCUMENT**

**CONTRACT NO. BPA OARMSC-SYS-04**

**SDWIS PROJECT**

**Prepared for:**

**United States Environmental Protection Agency**

**Office of Ground Water and Drinking Water**

**Drinking Water Protection Division**

**1200 Pennsylvania Ave., NW**

**Washington, DC 20460**

**Contracting Officer Representative**

**Edward Cottrill**

**Prepared by:**

**SAIC Solutions Delivery Center**

**Science Applications International Corporation**

**6565 Arlington Boulevard**

**Falls Church, VA 22042**

**CONTENTS**

[1.0 INTRODUCTION 1](#introduction)

[1.1 Purpose 1](#purpose)

[1.2 Assumptions and Constraints 1](#assumptions-and-constraints)

[1.3 Joint Requirements Planning (JRP) Process
2](#joint-requirements-planning-jrp-process)

[2.0 References 3](#references)

[3.0 software certification environment
3](#software-certification-environment)

[4.0 User - Requested requirements 4](#user---requested-requirements)

[4.1 Requirements in Scope 4](#requirements-in-scope)

[4.2 Requirements Submitted but Deferred for Future Release
8](#requirements-submitted-but-deferred-for-future-release)

[5.0 Rule requirements 8](#rule-requirements)

[5.1 Long Term 2 Enhanced Surface Water Treatment Rule
9](#long-term-2-enhanced-surface-water-treatment-rule)

[5.2 Stage 2 D/DBP Rule 12](#stage-2-ddbp-rule)

[5.3 Groundwater Rule (GWR) 14](#groundwater-rule-gwr)

[6.0 system maintenance requirements
16](#system-maintenance-requirements)

[7.0 sdwis/xml sampling requirements
17](#sdwisxml-sampling-requirements)

[8.0 REQUIREMENTS TRACEABILITY 18](#requirements-traceability)

**APPENDIX A** SDWIS/STATE 2.0 JRP Participants

**APPENDIX B** Requirements Deferred to Future Release

**APPENDIX C** SDWIS/STATE 2.0 Requirements Traceability Matrix

**EXHIBITS**

[**Exhibit 1.** Long Term 2 Enhanced Surface Water Treatment Rule
Provision Implementation Phases 10](#__RefHeading___Toc151798477)

[**Exhibit 2.** Stage 2 D/DBP Rule Subpart Implementation Phases
13](#__RefHeading___Toc151798478)

This page is intentionally left blank.

# INTRODUCTION

The Environmental Protection Agency's (EPA) Office of Ground Water and
Drinking Water (OGWDW) is responsible for implementing the Public Water
System Supervision (PWSS) Program established under the auspices of the
Safe Drinking Water Act (SDWA) of 1974, Public Law 93-523, and the 1986
and 1996 amendments to SDWA.

EPA developed Safe Drinking Water Information System (SDWIS)/STATE to
help the states and other drinking water primacy agencies manage their
drinking water information, improve data quality, and to facilitate the
transfer of federally reportable data to the national database.
SDWIS/STATE is a primarily browser-based web application.

## Purpose

This document records the requirements that the SDWIS/STATE 2.0 software
must satisfy to fulfill the requested functionality and to define the
scope of work to be performed. It provides a means to identify, trace,
and evaluate requirements statements to ensure that each statement is
complete, unambiguous, consistent, verifiable, and traceable. This
document will be used as a roadmap for system development activities.
EPA and other stakeholders may use this document to verify that the
requirements are stated accurately and completely identify the physical
and functional characteristics of the system.

Please note that it is EPA policy that the Long Term 2 Surface Water
Treatment /Stage 2 Disinfectant/Disinfection By-Products Data Collection
and Tracking System (LT2/Stage 2 DCTS) be used as the official database
of record for the early implementation of Long Term 2 Enhanced Surface
Water Treatment and Stage 2 Disinfectant/Disinfection By-Products Rules.

## Assumptions and Constraints

The following list contains the assumptions and constraints that have
been made in developing the requirements for SDWIS/STATE 2.0.

-   The preponderance of the changes are triggered by:

```{=html}
<!-- -->
```
-   Modifications to the Compliance Decision Support (CDS) modules and
    other SDWIS/STATE components based on the requirements of the
    following rules:

> \-- Long Term 2 Enhanced Surface Water Treatment Rule.
>
> \-- Stage 2 of the Disinfectant/Disinfection By-Products (D/DBP) Rule.
>
> \-- Groundwater Rule.

-   Modernization efforts to complete the web-enablement of SDWIS/STATE.

```{=html}
<!-- -->
```
-   The SDWIS/STATE 2.0 business functionality and design will be
    largely the same as that delivered with SDWIS/STATE Web Release 1,
    except as noted and documented in Sections 4.0, 5.0, 6.0, and 7.0 of
    this document.

```{=html}
<!-- -->
```
-   Where the requirements in this document trigger changes to the
    existing design, the existing design (SDWIS/STATE Web Release 1.0
    Design Document) will be updated. This is a function of the design
    phase of development.

-   To the degree that changes to table structures and content occur, a
    Schema Migration Table Instruction Matrix and schema migration
    scripts will need to be developed to accommodate the changes. This
    is a function of the design phase of development.

```{=html}
<!-- -->
```
-   Final reporting guidance for the Long Term 2, Stage 2 D/DBP, and
    Groundwater Rules is not yet available; the requirements for these
    rules specified in this document are based on available guidance.

```{=html}
<!-- -->
```
-   SDWIS/STATE 2.0 will be a primacy agency (not national) instance,
    i.e., the database will be hosted locally on each primacy agency's
    intranet. SDWIS/STATE 2.0 will not be a national instance within
    which several primacy agencies can simultaneously maintain their
    drinking water data.

```{=html}
<!-- -->
```
-   SDWIS/STATE 2.0 will continue to target the same databases as those
    currently targeted by SDWIS/STATE Web Release 1. Specific
    information regarding product release levels and other hardware and
    software components will be documented in another deliverable, the
    SDWIS/STATE 2.0 Hardware and Software Certification Environment.

-   SDWIS/STATE 2.0 will be developed primarily (though not exclusively)
    using Computer Associate's® AllFusion*™ Gen* toolset.

## Joint Requirements Planning (JRP) Process

The requirements gathering for SDWIS/STATE 2.0 was conducted through a
facilitated Joint Requirements Planning (JRP) session, attended by
SDWIS/STATE stakeholders, including personnel from the Information
Management Branch (IMB) of OGWDW at EPA Headquarters, EPA Regional
staff, State representatives, and Science Application International
Corporation (SAIC) Solutions Development Center (SDC) staff. A complete
roster of SDWIS/STATE 2.0 JRP participants is included as Appendix A.

The SDWIS/STATE 2.0 JRP was conducted April 21 and 22, 2005 at the
SDWIS/STATE Users Group meeting in New Orleans, Louisiana. The goal of
this session was to verify (or amend) proposed SDWIS/STATE 2.0
requirements, capture new SDWIS/STATE 2.0 requirements, and begin to
gather some preliminary design guidance in preparation for the upcoming
Joint Application Design (JAD) sessions.

The content of the JRP sessions was gathered from input provided to the
SDWIS User Support Hotline and upon direction from the OGWDW staff at
EPA Headquarters. Following the JRP, a request for additional
requirements was solicited through the SDWIS/STATE User Conference calls
with instruction to provide those requirements to the SDWIS User Support
Hotline by January 10, 2006.

# References

-   Stage 2 of the Disinfectant/Disinfections ByProducts Rule,
    promulgated

January 4, 2006.

-   Long Term 2 Enhanced Surface Water Treatment Rule, promulgated
    January 5, 2006.

-   Ground Water Rule as finalized November 8, 2006.

```{=html}
<!-- -->
```
-   SDWIS/STATE 2.0 JRP Materials, GSA-SDWIS-01-2.WIP30, April 21, 2005.

-   Joint Requirements Planning (JRP) session conducted April 21 and 22,
    2005 at the SDWIS/STATE Users Group meeting in New Orleans,
    Louisiana.

# software certification environment

SDWIS/STATE 2.0 will be primarily developed using Computer Associate's®
*AllFusion™ Gen 6.5* development and web-enabling tool (recently renamed
from *Advantage:Gen*). SDWIS/STATE 2.0 will continue to target the
following three databases:

-   Oracle 9i.

```{=html}
<!-- -->
```
-   SQL Server™ 2000.

```{=html}
<!-- -->
```
-   DB2 8.2.

The version of *MS Access* to be used is assumed to be at least *MS
Access 2003*, however, the SDWIS/STATE user community\'s preference will
be polled with a decision to be made closer to the commencement of
development on *MS Access* components. Note that with modernization
efforts, the use of MS Access will be greatly reduced in the
architecture of SDWIS/STATE 2.0.

The following list of software is not a recommendation. A more detailed
report of software/hardware that may be needed by a primacy agency to
deploy SDWIS/STATE 2.0 will be published at a later date. The
*AllFusion™ Gen 6.5* toolset requires that SDWIS/STATE 2.0 be deployed
on an application server that conforms to the J2EE standards and
supports the JSP 1.2 specification. Development and certification
environment will use Apache Tomcat.

Options for web server software include:

-   Apache Tomcat v5.0.28

-   IBM Websphere 5.0.2.

-   JBOSS 3.0.7.

-   BEA Web Logic 6.1.

-   Jrun 4.

The consensus of the SDWIS/STATE user community for SDWIS/STATE Web
Release 1.0 was to standardize development and certification using *MS*
*Internet Explorer*. This assumption will be carried forward to
SDWIS/STATE 2.0.

# User - Requested requirements

The following two sections describe requirements identified by users for
SDWIS/STATE 2.0. Some were sent in through SDWIS User Support; others
were identified during the SDWIS/STATE 2.0 JRP. User requested
requirements within the scope of SDWIS/STATE 2.0 are included where
development time is not significant and/or where modifications related
to a rule are already identified.

## Requirements in Scope 

R0004: Include replacement samples in collected samples count when
determining compliance.

R0005: Provide functionality to delete or expire treatment objective
process pairings.

R0008: Update the CFR Table to include newest Code of Federal Regulation
references (change to HQ rows).

R0010: Add a new permitted value of "Not Applicable" for each of the
Category Evaluation Summaries on the Site Visit Maintenance page and
make it the default.

R0011: Site Visit maintenance page -- advisory for discrepancy of
category and severity.

Add an edit check between Category Evaluation Summary and Deficiencies,
for instance if a deficiency is added of category Source Water and
severity Minor, check the Source Water category in Category Evaluation
Summary. If severity is not of Minor or higher, give the user a warning
that there is a discrepancy and option of automatically updating the
category evaluation summary or leaving unchanged.

R0013: Non-TCR Schedule Maintenance - presentation of application
periods and gap periods.

Enable users to see the Applicable Periods and Gap Periods for a
schedule by adding a button to the Non-TCR Sample Schedule Maintenance
window. The displayed list should include the four date attributes,
APPLICABLE_PERIOD_BEGIN_DATE, APP_PER_GAP_BEGIN_DATE,
APP_PER_GAP_END_DATE, and APPLICABLE_PERIOD_END_DATE in that order.
These are all from SAMP_SCHEDULE_MNTRG_PERIOD_ASGMT. The default sort
should be by APPLICABLE_PERIOD_BEGIN_DATE, ascending. Users should be
able to toggle between view all Applicable Periods and view current and
future Applicable Periods with the first being the default.

R0016: Provide an advisory to user if packaged violations are not
duplicate by data (duplicate check in this case should be Water System,
Type Code for the Violation Type, or Fed Violation Period Begin Dates,
and Federal Reportable Cont. Code (note that WSF was intentionally
omitted)). This advisory could be added to the online software and MTS.
This is needed because, as is, a state could easily improperly package
violations and not report some that should be federally reported.

R0021: Add Ratio as a UOM code on the violation maintenance page.

R0029: Improve presentation of violations that are individual violation
components of a violation group. With the present SDWIS/STATE software,
a state can set up a \"Group Violation\" for an \"Analyte Group\" which
contains individual violations with individual violation IDs and
individual analyte codes. If a SDWIS/STATE user has the desire to view
the individual Analyte Code associated with the individual Violation ID
number, it appears that this viewing is not straightforward. Add an
option to view (for group violations) the individual Violation ID number
related to its individual Analyte Code.

R0033: Add Advisory when inactivating a water system that sample
schedules will be closed.

If a user inadvertently inactivated a water system when the intent was
to inactivate a facility, the result is that *CDS Setup* closed
approximately 6,500 sample schedules.

When a small inadvertent change can do this kind of damage, we need a
warning message to remind the user of the consequences of the change.

R0036: Request to expand the permitted value for the State
Classification Code from three characters to four; that way the codes
can be set to match the analyte group codes.

R0037: The drop-down list for "Seller Treatment" in the Receiving
Facility/Water Purchase Maintenance page does not have the code
preceding the text description.

R0045: Request to make the blue navigation panel either sizeable or to
be minimized.

R0053: On the facility maintenance page, the "More" button should appear
at the top of the screen as well as the bottom. If a person wants to
skip over the main facility page, they can do so quickly.

R0054: Line up and size field blanks consistently where possible. It
makes screens look neat and less cluttered. For example, looking at the
Coliform sample screen, field blanks could be better justified and sized
the same so they appear more like columns of data.

(**Note**: This requirement is in scope but will be addressed only as
another modification is made to the web page. It will not be addressed
globally for this release.)

R0059: Please provide a lab certification module.

Request a lab certification module where method detection limit (MDL)
can be optionally entered by the state at the laboratory level. These
levels would then be used to provide warnings when labs reported MDL
different that the value designated by the state or when the lab has not
been approved to use the reported method.

Functions of a lab certification module include:

-   Ability to record the methods and result analysis that a lab is
    certified to perform. Use of these certified methods during sample
    input.

-   Certification of the lab's approved methods must be time-sensitive
    to allow for certification to expire and be re-instated.

-   Certification data requirements should include information regarding
    the written application, on-site inspections and audits, performance
    evaluations, and certification approvers. This includes the ability
    to schedule inspections and audits.

-   Certification may include the identification of specific persons
    approved to perform the analysis.

-   Ability to record reporting limits for the specific analytes and
    methods for which a laboratory is certified. Use these reporting
    limits during sample input to automatically fill information. This
    limits should be time-sensitive.

-   Ability to record Performance Evaluation (PE) samples and results
    for use in auditing and inspecting the lab.

-   Inclusion of certification information when entering samples. The
    extent of certification in advising and editing will be determined
    in the design phase.

R0065: Need to expand the length of attribute name REF_ATTRIBUTE_NAME in
the Code Table (TINCODE) from 30 to 50 characters.

R0073: Add a message that notifies the user of impending removal of the
Total Coliform and Acute Speciation Result values, if any had been
provided when the sample is rejected.

R0074: There are three ways in which permitted values are recorded in
SDWIS/STATE: (a) Hard-coded, (b) in the TINCODE plus TINPVALS tables,
(c) in tables like TSAOSAPM (Other Sample Measures Tables). The ODD for
SSWr1 only supports the first two. The third method needs to be
incorporated so that, for example, when a user selects the Other Sample
Measures table within the ODD and picks any of the attributes and
selects permitted values, a report showing all the records in the table
should be displayed.

These tables can be added as local tables to the ODD for this purpose:

TCDSPMSG TMNCOR TMNMNCON TMNMPD\
TMNMRCA TMNMRLOC TMNRULE TMNSTAT\
TMNVDCR TMNVPRDR TMNVTAA TMNVTRA\
TSACVCR TSAOSAPM TSAOSPM TSASAMT\
TSASMMT TSASRSC TSASRSR TSAUOM\
\
Additionally add a report that shows the TCR Monitoring Conditions. The
best would be to have a link to the three tables used to establish these
in replacement of the locally-imported tables for TMNMNR, TMNMRCA, and
TMNMNCON.

R0082: The Review Reports Log and Reports should be sorted by Report
Type as well as Run Time. Right now it only sorted by Report Type.

R0088: 01 MCL Violations and 02 MCL Violations processing in *CDS
Setup.*

First, need to modify *CDS Setup* to delete 01 candidate if a matching
02 candidate is determined. Matching here involves all the same criteria
as matching standard matching, except violation type will not match
(i.e., same PWS, same WSF -- if supplied, same analyte, same State Begin
Date).

Second, need to modify the *CDS Setup* process that looks for an
existing R, P, or V violation in TMNVIOL before creating a candidate
violation to: look for a matching R, P, or V, type 01 violation when a
candidate 02 has been determined. However, in this case, *CDS Setup*
should still create the candidate 02 and then, here is the new part, it
should create an advisory. Normally, in this situation, the user will go
and delete the existing 01 violation and migrate the candidate 02.

R0094: The Results Averages function of the Sampling Component provides
monitoring period and running annual average numbers in the screen for
individual monitoring periods and the maintenance list for all
monitoring periods for a specific analyte schedule. While the monitoring
period average provides averages that show several places after the
decimal point, the running annual average -- at least for 2456 and 2950-
show just two places after the decimal point. This results in the reader
not being able to tell if the RAA exceeds the MCL for the analyte. For
example, if a RAA for HAA5 (2456) is shown as 0.060 mg/L, it is unclear
whether the RAA is really 0.064 and exceeds the MCL, of if it is 0.060
mg/L. It would be a good idea to extend the numbers to at least four
places to the right of the decimal point.

R0100: Re-architect *CDS Setup* to execute on the web environment.
(Requires identification of new reporting technology.)

R0101: Re-architect CDS Reports (including EBS Reports) to execute on
the web environment. (Requires identification of new reporting
technology.)

R0107: Increase size of the description text on the permitted values
(TINPVALS) table.

R0123: For instances where the violation was rejected due to a waiver,
would like to be able to record that reason with the rejected violation.
These reasons should be controlled by the System Administrator.

R0127: Modify the TCR Compliance report to include the previously issued
TCR violations for a water system, to reduce white space, and to present
more water systems per page, thus reducing the overall number of pages
for the report.

R0128: Provide Link from Candidate Violation Migration into Violation
Maintenance. Request to add the ability to flow directly to the
Violation Maintenance List after migrating candidate violations so that
a user can complete the processing of the candidate violations. This
function could ask the user, after clicking on one of the "Migrate as
Preliminary/Validated/Rejected" functions if the user wants to go to the
Violation Maintenance List to further process the violations. If the
answer is yes, flow to the maintenance list with the violations listed
that the user just migrated. From here then, the user could finish
processing using existing capabilities.

## Requirements Submitted but Deferred for Future Release

Many good suggestions emerged during the SDWIS/STATE 2.0 requirements
gathering phase. While all the user requirements have been captured,
they cannot all be included in SDWIS/STATE 2.0. The decision to defer a
requirement is based the relatively short turn-around time for
delivering this release. All requirements that were submitted but cannot
be accommodated in SDWIS/STATE 2.0 are listed in Appendix B. These
requirements will be carried forward in the SDWIS Event Tracking System
(ETS) for consideration in the next release.

# Rule requirements

Requirements for implementation of new rules are based on EPA's final
rule documents and federal reporting guidance for each rule. These
requirements also include primacy agency needs in response to EPA
reporting requirements (e.g., the need that primacy agencies have to
track the same information in their information system as is reported to
EPA).

Generally, the definitions and criteria that EPA sets for a violation
type are considered requirements for SDWIS/STATE. If, for instance, EPA
specifies only certain contaminants/ analytes to be appropriate for a
given violation type, that requirement is enforced in SDWIS/STATE.
However, sometimes primacy agencies need to store information about a
violation in a different manner from how EPA requires the data to be
reported. In these cases, SDWIS/STATE implements both the EPA
requirement and the primacy agency requirement. Examples of this include
the ability to store the actual analyte/contaminant involved in a
violation when EPA only wants the rule code reported (e.g., violation
type 36, a SWTR monitoring violation, may be incurred because a water
system failed to collect turbidity or chlorine samples -- EPA only wants
the rule code (0200) for these while primacy agencies want the analyte,
so SDWIS/STATE enables both).

The completeness of rule implementation for this and any release is also
driven on the timing of the function as identified in the EPA guidance.
Only functionality that is understood to be necessary during the
implementation span of this release will be developed. Functionality
that is not needed until a future date will be deferred to a later
release. It is assumed that the EPA requirement will be satisfied in the
SDWIS/STATE 2.0 software unless otherwise indicated. If primacy agencies
have different requirements, these will be explicitly stated.

## Long Term 2 Enhanced Surface Water Treatment Rule

R2000: Implement the processes and supporting data to automate
compliance determination in accordance with the Long Term 2 rule. This
broad business requirement is broken down into smaller requirements as
they apply to the SDWIS/STATE application.

The scope of this requirement is constrained to the provisions due to
take effect during the anticipated implementation life span of
SDWIS/STATE 2.0.

+----------------------+---------+------------+------------------------+
| **Regulatory         | **Pop   | **Initial  | **SDWIS/STATE          |
| Sections and         | ulation | Impact     | Release**              |
| Requirement**        | S       | Date**[^1] |                        |
|                      | erved** |            |                        |
+======================+=========+============+========================+
| § 141.701 Source     | \>9,999 | April 2006 | Sample Collection      |
| water monitoring.    |         |            | SDWIS/STATE Web        |
|                      |         |            | Release 1              |
|                      |         |            |                        |
|                      |         |            | Compliance             |
|                      |         |            |                        |
|                      |         |            | SDWIS/STATE Release    |
|                      |         |            | 2.0                    |
+----------------------+---------+------------+------------------------+
|                      | \       | April      |                        |
|                      | <10,000 | 2008[^2]   |                        |
+----------------------+---------+------------+------------------------+
| § 141.702 Sampling   | \>9,999 | January    | Plan Submittal         |
| Plans                |         | 2006       |                        |
|                      |         |            | SDWIS/STATE Web        |
|                      |         |            | Release 1              |
|                      |         |            |                        |
|                      |         |            | Plan Compliance        |
|                      |         |            |                        |
|                      |         |            | SDWIS/STATE Release    |
|                      |         |            | 2.0                    |
+----------------------+---------+------------+------------------------+
|                      | \       | January    |                        |
|                      | <10,000 | 2008       |                        |
+----------------------+---------+------------+------------------------+
| § 141.708            | \>9,999 | April 2008 | SDWIS/STATE Web        |
| Disinfection         |         |            | Release 1              |
| Profiles             |         |            |                        |
+----------------------+---------+------------+------------------------+
|                      | \       | April 2009 |                        |
|                      | <10,000 |            |                        |
+----------------------+---------+------------+------------------------+
| § 141.710 BIN        | \>9,999 | April 2008 | SDWIS/STATE Release    |
| Determination        |         |            | 2.0                    |
+----------------------+---------+------------+------------------------+
|                      | \       | April 2009 |                        |
|                      | <10,000 |            |                        |
+----------------------+---------+------------+------------------------+
| § 141.714 Uncovered  |         | October    | SDWIS/STATE Web        |
| Storage              |         | 2008       | Release 1              |
+----------------------+---------+------------+------------------------+
| § 141.715 Microbial  | \>      | October    | After SDWIS/STATE      |
| Toolbox              | 100,000 | 2010       | Release 2.0            |
+----------------------+---------+------------+------------------------+
| § 141.723 Sanitary   | \>9,999 | January    | SDWIS/STATE Release    |
| Survey               |         | 2002       | 2.0                    |
+----------------------+---------+------------+------------------------+
|                      | \       | January    |                        |
|                      | <10,000 | 2005       |                        |
+----------------------+---------+------------+------------------------+

[]{#__RefHeading___Toc151798477 .anchor}**Exhibit 1.** Long Term 2
Enhanced Surface Water Treatment Rule Provision Implementation Phases

Summary of the Requirement Impact organized by SDWIS/STATE Component:

-   Sampling Component

```{=html}
<!-- -->
```
-   R2001-Edits for sample results submitted by labs certified for the
    required method.

```{=html}
<!-- -->
```
-   Compliance Components

```{=html}
<!-- -->
```
-   R2002-Increase/Decrease Monitoring Report to include evaluation of
    Cryptosporidium monitoring based on *E. coli* mean.

-   R2003-Identification of candidate violations\* for:

> \-- Sample collections taken outside of the sampling plan
> specification.
>
> \-- Treatment Technique violations.

-   R2004-Determination of *E. coli* and Cryptosporidium means based
    upon quantities for:

> \-- The monitoring period
>
> \-- Running annual average

-   R2005-Determine BIN and status (based upon verification
    12-consecutive months of monitoring).

-   R2006-Add Treatment Technique Compliance Report.

-   R2013-Support compliance for sampling periodicity frequency of every
    two weeks.

```{=html}
<!-- -->
```
-   Enforcement Action Component

```{=html}
<!-- -->
```
-   R2007-Create new returned-to-compliance enforcement action for
    resolved deficiencies.

```{=html}
<!-- -->
```
-   Site Visit

```{=html}
<!-- -->
```
-   R2008-Ability to assign system administrator-controlled roles to the
    parties present at the Site Visit.

-   R2009-Add Due Date (separate from the completed date) and ability to
    list Site Visits with due date within a user-specified date range,
    specified regulating agency, and/or specified role.

-   R2010-Display a list of all Deficiencies for a Water System and the
    violations associated to each deficiency.

-   R2011-Provide access to the maintenance of the
    Deficiency-to-Violation associations from the deficiency side.
    (Currently this maintenance is only available from the violation
    side.)

-   R2012- Increase the description length of a Deficiency.

-   R2014-Enhance Deficiency maintenance page to populate severity and
    evaluation category based upon the deficiency type selected.

```{=html}
<!-- -->
```
-   System Administration

```{=html}
<!-- -->
```
-   R2015-Ability to associate a deficiency type to a severity level and
    also to a site visit evaluation category.

\*The current guidance on violation reporting proposes significant
changes from previous violation reporting. These changes impact the
complexity of implementing violation reporting for this rule. For
example:

-   The proposal uses inventory data such as population count or federal
    primary source water type to determine the applicable begin date of
    the violation. There are currently no other violations that use
    inventory information to derive the violation begin date. Procedures
    will need to be developed in SDWIS/STATE, SDWIS/FedRep and SDWIS/ODS
    to provide derivation and validation of violation begin dates based
    on inventory information.

-   Type 03 monitoring violations are divided into two categories,
    complete failure to monitor and failure to monitor with the correct
    method and/or location. Currently, samples that are not taken
    appropriately are marked as rejected samples. Compliance processes
    to not consider rejected samples in determination of violations that
    will most often result in a failure to monitor violation. To
    additionally determine that the failure to monitor was due to
    defective sampling procedures, is increasing the scope of violation
    reporting for this rule.

A more mainstream and consistent application of previous violation
reporting methodology would be more cost-effective and less error-prone.
Discussions regarding this topic are ongoing at the publication time of
this document.

## Stage 2 D/DBP Rule

R3000: Implement the processes and supporting data to automate
compliance determination in accordance with the Stage 2 D/DBP rule. This
broad business requirement is broken down into smaller requirements as
they apply to the SDWIS/STATE application.

The scope of this requirement is constrained to the sub-part provisions
due to take effect during the anticipated implementation life span of
the SDWIS/STATE 2.0 product.

+----------------------+--------------+-------------+------------------+
| **Regulatory         | **Regulation | **Initial   | SDWIS/STATE      |
| Requirement**        | Sections     | SD          | Release          |
|                      | Included**   | WIS/STATE** |                  |
|                      |              |             |                  |
|                      |              | **Impact    |                  |
|                      |              | Date**      |                  |
+----------------------+--------------+-------------+------------------+
| Subpart L Revisions  | 141.64(b)(1) | October     | SDWIS/STATE      |
|                      |              | 2005        | Release 2.0      |
| Stage 1 Requirements | 141.131 -    |             |                  |
| for Stage 2 D/DBP    | 141.135      |             |                  |
+----------------------+--------------+-------------+------------------+
| Subpart O Revisions  | 141.151 --   | April 2007  | SDWIS/STATE      |
|                      | 141.155      |             | Release 2.0      |
| Consumer Confidence  |              |             |                  |
| Reports              |              |             |                  |
+----------------------+--------------+-------------+------------------+
| Subpart U            | 141.600 -    | October     | SDWIS/STATE      |
|                      | 141.606      | 2006        | Release 2.0      |
| Initial Distribution |              |             |                  |
| System Evaluations   |              |             |                  |
| (IDSE)               |              |             |                  |
+----------------------+--------------+-------------+------------------+
| Subpart V            | 141.64(b)    | October     | After            |
|                      |              | 2011        | SDWIS/STATE      |
| LRAA Requirements    | 141.620 -    |             | Release 2.0      |
| for Stage 2 D/DBP    | 141.630      |             |                  |
+----------------------+--------------+-------------+------------------+

[]{#__RefHeading___Toc151798478 .anchor}**Exhibit 2.** Stage 2 D/DBP
Rule Subpart Implementation Phases

Summary of the Requirement Impact organized by SDWIS/STATE Component:

-   Sampling Component

```{=html}
<!-- -->
```
-   R3001-Edits for sample results submitted by labs certified for the
    method.

```{=html}
<!-- -->
```
-   Monitoring Component

```{=html}
<!-- -->
```
-   R3002-Record sample collection interval.

-   R3003-Ability to schedule monitoring for the same analyte at
    different frequencies.

-   R3004-Maintenance of violations per the reporting guidance.

-   R3005-Add periodicity of every 2 months for monitoring.

-   R3006-Flexibility to indicate need for Locational Running Annual
    Average calculation.

-   R3007-Integration of Sampling Plans with Non-TCR Sample schedules to
    generate sub-schedules.

-   R3008-Enhance Sampling Plans to distinguish between IDSE and Subpart
    V.

-   R3009-Functionality to support analyte level specification for
    sampling points.

```{=html}
<!-- -->
```
-   Enforcement Action Component

```{=html}
<!-- -->
```
-   R3010-Support recording of a water system's compliance decisions
    such as a 40/30 certification.

```{=html}
<!-- -->
```
-   Compliance Components

```{=html}
<!-- -->
```
-   R3011-Increase/Decrease Monitoring Report to include TThm, HAA5,
    Bromate.

-   R3012-Identification of candidate violations\* for:

> \-- Sample collections taken inside the specified collection interval.
>
> \-- Failure to conduct required IDSE monitoring.
>
> \-- Failure to submit required IDSE Report.

-   R3013-Creation of Locational Running Annual Average.

-   R3014-Check for TTHM and HAA5 dual sample collection on same day.

-   R3015-Enhance association of SAR to SSMPA to disallow "double
    dipping" of the SAR for satisfying both an IDSE Sample schedule AND
    a Stage 1 Sample Schedule collected at the same sampling point.

-   R3016-Use of new Sampling Point level in compliance determination.

```{=html}
<!-- -->
```
-   System Administration Component

```{=html}
<!-- -->
```
-   R3017-Support for 2-month monitoring periods.

-   R3018-Add the new analyte reporting levels.

```{=html}
<!-- -->
```
-   Inventory Component

```{=html}
<!-- -->
```
-   R3019-Record designation of sampling points, such as High HAA and
    High PHM.

```{=html}
<!-- -->
```
-   CCRWriter

```{=html}
<!-- -->
```
-   R3020-Include IDSE results for TThm and HAA5.

```{=html}
<!-- -->
```
-   Reporting

```{=html}
<!-- -->
```
-   R3021-Report to list all TThm results and all HAA5 results for each
    treatment plant subject to IDSE monitoring.

[]{.mark}

\* The current guidance on violation reporting proposes significant
changes from previous violation reporting. These changes impact the
complexity of implementing reporting for this rule. For example:

Type 03 monitoring violations for complete failure to monitor are to be
reported with a static begin date 33 months after rule promulgation and
end date of end of return to compliance. Concerns with a violation
period begin date of 33 months after rule promulgation (Jan 2006)
indicates that the violations would have a begin date of October 2008.
For violations identified in 2006 they may return to compliance prior to
the begin date of the violation. Typically the begin date of the
violation is relative to the sampling period in which the violation
occurred.

A more mainstream and consistent application of previous violation
reporting methodology would be more cost-effective and less error-prone.
Discussions regarding this are ongoing at the publication time of this
document.

## Groundwater Rule (GWR)

R4000: Implement the processes and supporting data to automate
compliance determination in accordance with the Groundwater Rule. This
broad business requirement is broken down into smaller requirements as
they apply to the SDWIS/STATE application.

The Ground Water Rule was finalized November 8, 2006. The following
requirements have been added and or modified. EPA has requested that
SDWIS/STATE 2.0 provide decision support functionality in order to
assist in preparation for full GWR compliance activities, which are well
into the future. More robust functionality will be considered with a
future release of SDWIS/STATE.

Summary of the Requirement Impact organized by SDWIS/STATE Component:

-   Sampling Component

```{=html}
<!-- -->
```
-   R4014: In support of the treatment effectiveness and reliability
    monitoring requirement of the GWR regulation, existing functionality
    provided for MDBP Summary can be reused. No change is needed to the
    FANL area.

```{=html}
<!-- -->
```
-   Compliance Component

```{=html}
<!-- -->
```
-   R4001: Determine candidate violations in compliance determination
    for Ongoing Viral Monitoring reporting. (Note: Reporting Guidance
    has not yet been finalized. SDWIS/STATE 2.0 will assume no changes
    in the manner of M&R reporting.)

```{=html}
<!-- -->
```
-   R4008: Modify the TCR Compliance Report to list *E.* *coli*
    triggered GW source water monitoring results collected during the
    TCR Repeat sample collection period. This is to support the GWR's
    specification that small systems may be allowed to count these
    results as one of the required TCR Repeat samples.

-   R4009: Add new report to list the water system and source facilities
    that may require a triggered GW source water sample schedule based
    upon the occurrence of a positive TCR sample. This is in support of
    triggered source water monitoring requirements in GWR.

-   R4010: In support of the treatment effectiveness and reliability
    monitoring requirement of the GWR regulation, existing functionality
    provided for Surface Water Treatment Rule (SWTR) can be reused by
    renaming the Surface Water Treatment Compliance Report to Water
    Treatment Compliance Report (including changing titles and labels to
    more generic terms such as 'Water Treatment Summary').

```{=html}
<!-- -->
```
-   Laboratory Component

    -   R4011: Add new analyte method pairing associations allowed for
        the three fecal indicators.

-   System Administration Component

```{=html}
<!-- -->
```
-   R4002: Ability to maintain the schedule result substitute conditions
    tables for specifying the analytes allowed to satisfy groundwater
    rule monitoring. This requirement is withdrawn from the scope of
    this release.

-   R4012: Update the GWR in the Rule table with the final status and
    date.

-   R4013: Create new standard responses that are meaningful and useful
    in the management of compliance activities related to the
    installation of treatment techniques.

```{=html}
<!-- -->
```
-   Site Visit Component

```{=html}
<!-- -->
```
-   R4003: Ability to assign system administrator-controlled roles to
    the parties present at the Site Visit.

-   R4004: Add Due Date (separate from the completed dated) and ability
    to list Site Visits with due date within a user-specified date
    range, specified regulating agency, and/or specified role.

-   R4005: Display a list of all Deficiencies for a Water System and the
    violations associated to each deficiency.

-   R4006: Provide access to the maintenance of the
    Deficiency-to-Violation associations from the deficiency side.
    (Currently this maintenance is only available from the violation
    side.)

-   R4007: Increase the description length of a Deficiency.

# system maintenance requirements

R0055: Re-key the CDS tables to concatenate User ID, jobrun, date, or
some other element with the IS numbers to mitigate risk of reaching
upper limit of the IS number.

R0057: The Violation Selection lists (all, not just chem/rad) display
only 500 rows. When there are more, need a way to access them.

R0064: Correct Country Code abbreviations to concur with SDWIS/ODS

The discrepancies are:

[FED Codes and Description]{.underline} [SDWIS/STATE and
Description]{.underline}\
AL-ALBANIA AL-AZERBAIJAN\
TC-UNITED ARAB EMIRATES TC-TRINIDAD AND TOBAGO\
AJ-AZERBAIJAN AL-AZERBAIJAN\
FO-FAROE ISLANDS FQ-FAROE ISLANDS\
TD-TRINIDAD AND TOBAGO TC-TRINIDAD AND TOBAGO

R0066: We should add a USERID and LAST_UPDATE_TIMESTAMP to the TMNVPRDR
and TMNVDCR tables. All records should be initially set with SSWR1 and
1/1/2005.

R0072: Need to increase the size of the TINWSF external system number.
Some primacy agencies are hitting the max.

R0076: In SDWIS/STATE 8.0, an attribute in SAR was used to tell *CDS
Setup* whether to use the directly linked MP to control the SSMPA
connection. SSWr1 removed that attribute's involvement and replaced it
with logic that says if a MP is directly linked to a SAR, it should be
used instead of the collection date when linking to SSMPAs. This change
presented new problems that need to be redesigned in the next release.
Options are to revert back to the SDWIS/STATE 8.0 design or change *CDS
Setup* so that it never makes a direct link - i.e., only a user can make
a direct link so that it is clear that the direct link is truly a user
override.

R0080: There are still \"unknown\" MAD codes for locational data in
SDWIS/STATE look up tables (TINPVALS).\
\
TINLOC1-HZ_COLLECT_METH_CD-027-Unknown\
TINLOC3-SOURCE_MAP_SCALE-U-Unknown\
TINLOC4-REFERENCE_POINT_CD-001-Unknown\
TINLOC4-REFERENCE_POINT_CD-003-Other\
TINLOC7-VERIF_METHOD_CD-010-Verified, unknown method\
TINLOC8-VER_COL_METH_CD-008-Other, Unspecified\
TINLOC9-VERT_REF_DATUM_CD-U-Unknown

R0084: There\'s not enough room in the method number field to add the
method number - QuikChem 10-204-00-1-X, Distillation/
Spectrophotometric.

R0085: When entering a new TCR schedule, the Initial MP Begin Date
should be defaulted to NULL if no value is provided.

# sdwis/xml sampling requirements

The following in-scope requirements target changes to *SDWIS/XML
Sampling*.

R0061: If the email could be set up like that of SDWIS/FedRep where the
user has the option to enter an email address at time of submission. One
problem that I can see states running into is that there may be many
people running in sample data and if all of their names are entered,
then they will be getting email about data submissions for other people,
whereas if the property file just contained a default email address then
that would be used for batch runs, but if a user is manually kicking off
SDWIS/XML then they could change it so that only the default email
address and themselves received the email, versus having to add
everybody to the default email list.

R0067: The display of errors should include the error number next to its
description. We should add the number of each error next to its text.

R0068: The links should always be available for users to click on, no
matter which page they are on. For example when I clicked on (View Job
Details by Date or View System Property Files or View Log Files), that
link disappeared. You should leave it in the navigation bar or at least
disable it.

R0069: The links on the left navigation bar and their corresponding
titles on each page should match and be consistent. For example for:
View Job Details by Date link the page title should say: Job Details by
Date, for link: View all Jobs the page title should say: All Jobs, and
so on. Also, the font style and size should be consistent in all the
pages.

R0070: On the Job Detail Page, add a new column for Total Records
Submitted.

R0098: XML Sampling should automate the determination of the Home
Variable.

R0099: XML Sampling should re-use the online maintenance page of the
system variable file developed for SDWIS/FedRep.

R0126: Provide a printable format of the Job Output, Details, and Errors
pages.

# REQUIREMENTS TRACEABILITY

The initial version of the SDWIS/STATE 2.0 Requirements Traceability
Matrix (RTM) is included as Appendix C. The SDWIS/STATE 2.0 RTM
identifies each requirement and cites a reference back to the Event
Tracking System (ETS) for origin of the requirement. Once design is
underway, identification of the expected design area or areas impacted
by the requirement will be added to the matrix. Once the design is
completed, references to the SDWIS/STATE 2.0 Design Document design
requirement numbers that satisfy each requirement will be added as well.
Finally, the test cases and/or test procedures that validate each of the
specified requirements will be included, completing the matrix.

**APPENDIX A**

SDWIS/STATE 2.0 JRP Participants

This page is intentionally left blank.

**SDWIS/STATE 2.0 JRP PARTICIPANTS**

  ----------------------------------- -----------------------------------
  **[Persons Attending]{.underline}** **[Representing]{.underline}**

  Benny Laughlin                      Alabama

  Maria Ridgway                       Alaska

  Wayne Hood                          Arizona

  Jim Stites                          California

  Lori Gerzina                        Colorado

  Sean Lieske                         

  Tom Reed                            Connecticut

  Christopher Roy                     

  Anta Beckel                         Delaware

  Brad Addison                        Georgia

  Doug Davenport                      

  Mike Weiman                         Iowa

  Hal Frank                           

  Don Lee                             Idaho

  Curtis Stoehr                       

  Sandy Frank                         Illinois EPA

  April Swift                         Indiana

  Darrel Plummer                      Kansas

  Jonathan Haynes                     

  Steve Poreda                        Kentucky

  Jerry Pike                          

  Les LeMon                           Louisiana

  Kate Gilmore                        

  Effie Michalo                       

  Brandon Taylor                      

  Bob Peterson                        Maine

  Kris Philip                         Michigan

  Karen Walters                       Mississippi

  Melissa Parker                      

  Randall Smith                       

  Darrell Osterhouldt                 Missouri

  Tom Adams                           

  Deon Olson                          Montana

  Roy Duefler                         

                                      

  Eugene Pizzine                      

  Andrea Vickory                      

  Laura Hardesty                      Nebraska

  Judy Neubert                        Nevada

  Richard Asbury                      New Mexico

  Tom Hart                            New York

  Michele White                       

  Martha Fillinger                    North Carolina

  Eric Chia                           

  Anne Kreel                          

  Barrett Brown                       North Dakota

  Mike Harrell                        Oklahoma

  Steven Wright                       

  Michele Doris                       

  Jamie Henson                        

  Kay Coffey                          

  Daryl Snow                          

  Chris Monk                          

  Robert Mullins                      

  Michele Welsh                       

  Diane Stockton                      Oregon

  George Waun                         

  Deb LaFleur                         Rhode Island

  Elizabeth Florm                     South Carolina

  Ken Bousfield                       Utah

  Bob Shipman                         

  Elizabeth Hunt                      Vermont

  Joanne Vivas                        Virginia

  David Escue                         West Virginia

  Charles Robinette                   

  Paul Ladd                           Region 4

  Charles O'Donnell                   

  Brian Thames                        

  Thao Nguyen                         Region 5

                                      

  Shirley Mlachak                     Region 6

  Carolyn Mithcell                    Region 7

  Dean McGinnis                       R8/ Wyoming

  Rich Gomez                           

  Janet LaCombe                        

  Karl Banks                          Region 9

  Brian Smith                         

  Jane Schuster                       Region 10

  Karen Wirth                         Guam

  Juliana De la Rosa                  Mariana Islands

  Jeffe Kennedy                       Cadmus

  Jon Dahl                            GEC

  Kate Dahl                           

  Jesse Dahl                          

  Mike Corbin                         

  Howard Woods                        

  Clint Lemmons                       EPA

  Ed Cottrill                         

  Roger Howard                        

  Jeff Bryan                          

  Elin Warn-S2                        

  Sarah Bahrman-S2                    

  Sharon Gonder-LT2                   

  Sean Conley-LT2                     

  Phil Oshida-Deputy Division         
  Director                            

  Kerri Biachett                      CSC

  Donna Hickling                      SAIC

  Julie Bruns                         

  Terrie Sutch                        

  Leslie Flagler                      

  Scott Peterson                      

  Dianna Heaberlin                    
  ----------------------------------- -----------------------------------

This page is intentionally left blank.

**APPENDIX B**

Requirements Deferred to Future Release

This page is intentionally left blank.

**Requirements Deferred to Future Release**

+--------+--------------+----------------------------------------------+
| *      | **Summary**  | **Description**                              |
| *Requi |              |                                              |
| rement |              |                                              |
| Nu     |              |                                              |
| mber** |              |                                              |
+========+==============+==============================================+
| R0001  | Assignment   | Need to record, by Sample Schedule record,   |
|        | of Lab to a  | which lab will do the analysis of samples    |
|        | sample       | used to satisfy the schedule.                |
|        | schedule to  |                                              |
|        | indicate     |                                              |
|        | authorized   |                                              |
|        | analysis for |                                              |
|        | samples.     |                                              |
+--------+--------------+----------------------------------------------+
| R0002  | Transfer     | Support ability to transfer a sampling point |
|        | Sampling     | from one WSF to another and maintain related |
|        | Points       | objects.                                     |
+--------+--------------+----------------------------------------------+
| R0009  | TCR Sample   | Requesting the ability to indicate whether   |
|        | Schedules -  | to create a repeat schedule or not based on  |
|        | request      | the sample type and the WSF type of the      |
|        | ability to   | positive result (if positive is a repeat do  |
|        | control      | not create a repeat but if it a routine      |
|        | creation of  | collected at a DS, then do create a repeat   |
|        | repeat       | schedule).                                   |
|        | schedules    |                                              |
|        | based upon   | The ability to set different defaults for    |
|        | sample type  | the proposed repeat schedules (currently the |
|        | and WSF type | software has hard coded 1 and 15 days after  |
|        | when         | the collection date of the positive as the   |
|        | validating   | default begin and end date of the repeat     |
|        | positives.   | schedule.                                    |
+--------+--------------+----------------------------------------------+
| R0012  | Legal Entity | Expand all Individual list windows to        |
|        | Maintenance  | include Employer ID No.                      |
|        | List         |                                              |
+--------+--------------+----------------------------------------------+
| R0014  | Non-TCR      | Expand the State Seasonal Period for Non-TCR |
|        | Sample       | Sample Schedules to enable to schedule       |
|        | Schedule     | sampling by week number. So a user could say |
|        | M            | that samples should be collected the first   |
|        | aintenance - | week of the first month of each quarter for  |
|        | expand state | example.                                     |
|        | seasonal     |                                              |
|        | period to    |                                              |
|        | allow a week |                                              |
|        | number       |                                              |
+--------+--------------+----------------------------------------------+
| R0015  | Non-TCR      | -   Need to enable users to see which        |
|        | Schedule     |     schedules are packaged. Perhaps all of   |
|        | Maintenance  |     the following changes would be           |
|        | List/        |     sufficient:\\                            |
|        | M            |                                              |
|        | aintenance - | -   Add Package Number field to the          |
|        | add          |     Maintenance window (if a schedule is not |
|        | packaging    |     packaged, instead of have nothing behind |
|        | indicator    |     the label, have a message that says "Not |
|        |              |     packaged"                                |
|        |              |                                              |
|        |              | ```{=html}                                   |
|        |              | <!-- -->                                     |
|        |              | ```                                          |
|        |              | -   Add Package Number field to the Non-TCR  |
|        |              |     Sample Schedule Maintenance List window  |
|        |              |                                              |
|        |              | -   Add ability to filter so that only       |
|        |              |     schedules that are packaged are          |
|        |              |     displayed - this would be a little       |
|        |              |     different that the normal filter         |
|        |              |     capability because users would want to   |
|        |              |     see all that have a package number not   |
|        |              |     those that have a specific package       |
|        |              |     number. So add a menu item to the        |
|        |              |     Maintenance List window that says        |
|        |              |     View/Filter by\...All Packaged           |
|        |              |     Schedules. When a user invokes this      |
|        |              |     filter, the default sort order should be |
|        |              |     Package Number ascending, Water System   |
|        |              |     Number, WSF State Asgn ID.               |
|        |              |                                              |
|        |              | -   Add Package Number as a field to sort    |
|        |              |     on.                                      |
+--------+--------------+----------------------------------------------+
| R0017  | Provide CFR  | Provide Code of Federal Regulations (CFR)    |
|        | crosswalk    | Table Crosswalk for CFR with Violation Type  |
|        | for CFR with | and Analyte and add attribute for State      |
|        | violation    | Regulation in System Administration. This    |
|        | type and     | would require a System Administration        |
|        | analyte      | function to maintain the CFR table.          |
+--------+--------------+----------------------------------------------+
| R0018  | Violation    | Default the CFR to the one associated to the |
|        | Maintenance  | violation type in System Administration. Add |
|        | -enhancement | attribute for state regulation code and      |
|        | to support   | default to the one associated to the         |
|        | defaulting   | violation type in System Administration.     |
|        | the CFR      |                                              |
|        | association. |                                              |
+--------+--------------+----------------------------------------------+
| R0019  | Edit Check - | Add an edit check that would advise a user   |
|        | Inventory    | when entering a Water Type for a CC or NP    |
|        | Primary      | that was inconsistent with the primary       |
|        | Source Type  | source type of the seller.                   |
|        | for CC and   |                                              |
|        | NP           |                                              |
|        | facilities   |                                              |
+--------+--------------+----------------------------------------------+
| R0022  | Support for  | Need ability to record trip blanks, which do |
|        | Trip Blanks  | not comply with the current requirements for |
|        |              | recording a sample.                          |
+--------+--------------+----------------------------------------------+
| R0023  | Service Area | In the Service Area Characteristics          |
|        | Cha          | selection in Inventory, is it possible to    |
|        | racteristics | have the service areas sorted in a more      |
|        | sort order   | efficient manner? As it is right now, there  |
|        |              | seems to be no particular sort order, but    |
|        |              | when service areas are added under the       |
|        |              | Administrator\'s icon, they appear in        |
|        |              | alphabetical order. We would like to have    |
|        |              | the service areas sorted first by code       |
|        |              | (i.e., NC, NTNC) and then, if possible, by   |
|        |              | service area name.\                          |
|        |              | \                                            |
|        |              | The sort order that we think would be easier |
|        |              | to navigate through the Service Area         |
|        |              | Characteristic maintenance window is as      |
|        |              | follows:\                                    |
|        |              | \                                            |
|        |              | 1) Classification Code\                      |
|        |              | 2) Name Code\                                |
|        |              | 3) Primary Service Area                      |
+--------+--------------+----------------------------------------------+
| R0024  | All          | User requests the ability to run CDS         |
|        | Compliance   | Compliance Reports by either Monitoring      |
|        | Report       | Period or Applicable Period End Date Range.  |
|        | windows      | Currently can only run CDS Compliance        |
|        |              | Reports by the latter.                       |
+--------+--------------+----------------------------------------------+
| R0025  | Violation    | Adding violations can become quite confusing |
|        | Data Entry   | due to all the specific rules.\              |
|        | Redesign     | \                                            |
|        |              | I would suggest a new screen that would      |
|        |              | appear when adding a violation that would    |
|        |              | navigate to the rule first (TCR, Stage 1     |
|        |              | D/DBP, etc.) and then, when a rule is        |
|        |              | picked, display a second screen with the     |
|        |              | appropriate violations.\                     |
|        |              | \                                            |
|        |              | The second screen would also include the     |
|        |              | contaminant codes, major minor flags, etc.   |
|        |              | for selection. Upon selection, the Violation |
|        |              | Maintenance screen would appear with the     |
|        |              | contaminant code, rule, major minor flag,    |
|        |              | etc. already set.\                           |
|        |              | \                                            |
|        |              | This is somewhat analogous to Sample Data    |
|        |              | Entry where one must navigate through the    |
|        |              | analyte groups to get to the result data     |
|        |              | entry. This would help us cut down on errors |
|        |              | during data entry, especially with the Stage |
|        |              | 1 D/DBP.\                                    |
|        |              | \                                            |
|        |              | Also, has any thought been given to          |
|        |              | expanding the descriptions of the violations |
|        |              | to be contaminant or rule specific? I have   |
|        |              | attached (see SDWIS/STATE e-mail account) a  |
|        |              | spreadsheet provided by Region 2 that        |
|        |              | illustrates how the description of a         |
|        |              | violation is dependent on not just the       |
|        |              | violation type, but the rule and analyte as  |
|        |              | well.                                        |
+--------+--------------+----------------------------------------------+
| R0030  | Presentation | Display Code Name in parenthesis next to any |
|        | of Code      | field whose PVs are controlled from Sys      |
|        | Table Name   | Admin                                        |
|        | on web pages |                                              |
|        | where values |                                              |
|        | are Sys      |                                              |
|        | Admin        |                                              |
|        | controlled.  |                                              |
+--------+--------------+----------------------------------------------+
| R0031  | Dynamic      | Add Primary Source categories of - PURCHASED |
|        | Group        | ALL (GWP + GUP + SWP) and NON-PURCHASED ALL  |
|        | Maintenance  | (GW + SW + GU).\                             |
|        |              | \                                            |
|        |              | It would be useful to include other options, |
|        |              | such as analyte or analyte group schedule,   |
|        |              | the existence of accepted sample results, or |
|        |              | sample result or sample averages with the    |
|        |              | user specifying the period of time and the   |
|        |              | cut-off sample result value. Tied to that,   |
|        |              | we would want to be then able to close       |
|        |              | existing schedules and open new schedules    |
|        |              | using the changes in water system groups. It |
|        |              | would also be nice to automatically generate |
|        |              | specified FANLs for each system in a water   |
|        |              | system group.\                               |
|        |              | \                                            |
|        |              | Would like to use some other criteria for    |
|        |              | water system group creation, such as         |
|        |              | increased/decreased monitoring.\             |
|        |              | \                                            |
|        |              | Would like functionality to support          |
|        |              | user-defined SQL to be used in defining a    |
|        |              | dynamic water system group.                  |
+--------+--------------+----------------------------------------------+
| R0032  | Print WS     | Add the population that is being served to   |
|        | Details      | the Population Served section.               |
+--------+--------------+----------------------------------------------+
| R0034  | Sampling     | These two tables should use the relationship |
|        | Point        | to sample schedule (TMNSASCH) and group      |
|        | Subschedule  | schedule (TMNSPSCG) as part of the           |
|        | and Sampling | identifier (similar to legal entity          |
|        | Point Group  | communication).                              |
|        | S            |                                              |
|        | ubschedule - |                                              |
|        | change to    |                                              |
|        | table        |                                              |
|        | identifier   |                                              |
+--------+--------------+----------------------------------------------+
| R0035  | Need ability | At times, results for the same sample are    |
|        | to designate | analyzed at different laboratories. Users    |
|        | the          | need to be able to indicate this. Currently  |
|        | laboratory   | laboratory is associated to a Sample.        |
|        | for the      |                                              |
|        | sample       |                                              |
|        | result       |                                              |
+--------+--------------+----------------------------------------------+
| R0038  | State        | Provide the ability to add a state-defined   |
|        | Defined      | treatment objective. The state-defined       |
|        | Treatment    | treatment objectives will be extracted from  |
|        | Objectives   | SDWIS/STATE and transformed to an \"other\"  |
|        |              | treatment objective for reporting to EPA     |
|        |              | (using SDWIS/FedRep).                        |
+--------+--------------+----------------------------------------------+
| R0039  | Allow Sys    | Allow Sys Admin control over legal entity    |
|        | Admin        | type codes.                                  |
|        | control over |                                              |
|        | legal entity |                                              |
|        | type codes   |                                              |
+--------+--------------+----------------------------------------------+
| R0042  | Redesign the | Redesign the Notification of TCR Schedule    |
|        | Notification | change function and reinstate in the next    |
|        | of TCR       | release.                                     |
|        | Schedule     |                                              |
|        | change       |                                              |
|        | function.    |                                              |
+--------+--------------+----------------------------------------------+
| R0044  | Function to  | Would like XML Sampling needs to enable a    |
|        | back out a   | user to back out processed Samples and       |
|        | batch of     | Results on a batch basis. It would also be   |
|        | samples      | useful if XML Sampling could back out        |
|        |              | Samples and Results that meet user defined   |
|        |              | criteria (e.g., result for TThm with         |
|        |              | detection limit = 4 ug/l associated to a     |
|        |              | sample collected between 1/1/2005 and        |
|        |              | 5/12/2005 analyte at laboratory number       |
|        |              | 0030).                                       |
+--------+--------------+----------------------------------------------+
| R0046  | Enable User  | Occasionally, when a PWS collects an overdue |
|        | to Associate | sample, the lab or PWS fails to report the   |
|        | a SOX to     | results for every regulated contaminant in a |
|        | Some but Not | group. When this happens, only the           |
|        | All          | monitoring violations issues for the         |
|        | Violations   | contaminants that were measured should be    |
|        | in a Group   | returned to compliance but SDWIS/STATE does  |
|        | Violation    | not enable a user to return only a portion   |
|        |              | of the violation to compliance. It needs to  |
|        |              | enable this.                                 |
+--------+--------------+----------------------------------------------+
| R0047  | Provide      | A sample address/location field should be    |
|        | sample       | provided on the sample entry/maintenance     |
|        | collection   | screen. For those that use a generic sample  |
|        | address      | point, but wish to reference the collection  |
|        |              | address, the lack of this field is           |
|        |              | detrimental.                                 |
+--------+--------------+----------------------------------------------+
| R0048  | Present      | Display number of required TCR samples on    |
|        | required TCR | the TCR maintenance list.                    |
|        | Samples on   |                                              |
|        | the TCR      |                                              |
|        | sample       |                                              |
|        | schedule     |                                              |
|        | maintenance  |                                              |
|        | list         |                                              |
+--------+--------------+----------------------------------------------+
| R0049  | Filter       | Activity Types Selection List should display |
|        | Activity     | only those activities with activity category |
|        | Type         | type equal to schedule type. Add "Show All"  |
|        | selection    | button to display entire list sorted by      |
|        | list to only | activity category type ascending and         |
|        | activities   | activity name ascending.                     |
|        | with         |                                              |
|        | matching     |                                              |
|        | category.    |                                              |
+--------+--------------+----------------------------------------------+
| R0050  | Provide more | Provide more empty buckets or allow state to |
|        | user-defined | control field labels. It is bad practice to  |
|        | fields.      | use unused fields for purposes other than    |
|        |              | intended. Staff cannot remember the proper   |
|        |              | use. For example, we are considering using   |
|        |              | the "Other" category on the Site Visit       |
|        |              | screen to provide our overall determination  |
|        |              | of the water system's status. If most people |
|        |              | use this correctly, but one or two folks     |
|        |              | forget and actually use it for assessing     |
|        |              | some "other" category, the data will not be  |
|        |              | useful.                                      |
+--------+--------------+----------------------------------------------+
| R0051  | Provide more | Allow state to set whether items in          |
|        | user         | pick-lists will display. It is bad to have   |
|        | flexibility  | available options you do not want staff to   |
|        | over         | consider. People interpret things            |
|        | presentation | differently and the fewer choices, the less  |
|        | of pick-list | room for misunderstanding. Not to mention,   |
|        | items.       | it is more user friendly to look at a useful |
|        |              | short list than a long list full of          |
|        |              | irrelevant choices.                          |
+--------+--------------+----------------------------------------------+
| R0052  | A            | Have SDWIS auto-total wholesale population   |
|        | utomatically | for a system that sells water. Have it look  |
|        | total the    | through the purchase chain and total all the |
|        | wholesale    | residential populations to get the total     |
|        | population.  | wholesale population served by a seller. Or  |
|        |              | at least supply a query that displays the    |
|        |              | buy-sell chain.                              |
+--------+--------------+----------------------------------------------+
| R0056  | TCR          | Re-write TCR Compliance to use same design   |
|        | Compliance   | as other compliance functions. Such as using |
|        | Re-write     | SSMPA, etc.                                  |
+--------+--------------+----------------------------------------------+
| R0058  | Enhance      | Include in all the Compliance Determination  |
|        | Compliance   | processes, the annual operating period of    |
|        | process to   | the water system, and the annual operating   |
|        | use the      | period of the water system facility (WSF)    |
|        | annual       | when determining compliance. The software    |
|        | operating    | should first look at the Sample Schedule's   |
|        | periods for  | Seasonal Period. If it exists, should use it |
|        | the water    | to determine compliance. If a Sample         |
|        | system and   | Schedule Seasonal Period does not exist, the |
|        | WSF          | software should look at the WSF and WS AOP.  |
|        |              | If only one of them has an AOP, then use     |
|        |              | that AOP when determining compliance (use it |
|        |              | the same way Seasonal Period is used). If    |
|        |              | both the WSF and WS have AOPs, use the       |
|        |              | overlap period of the two to determine       |
|        |              | compliance. Again use this "AOP Overlap      |
|        |              | Period" the same way Seasonal Period is      |
|        |              | currently used.                              |
+--------+--------------+----------------------------------------------+
| R0060  | Legal        | Would like to see a field that might         |
|        | Entities -   | identify legal entities in our system that,  |
|        | need a       | for whatever reason, are no longer are valid |
|        | status       | (moved or deceased). Staff will often look   |
|        |              | up a person through Legal Entities and       |
|        |              | receive out dated information. That person   |
|        |              | is marked as inactive if you look up Points  |
|        |              | of Contact through Inventory but nothing in  |
|        |              | the Legal Entity record for that individual  |
|        |              | indicates they are inactive.                 |
+--------+--------------+----------------------------------------------+
| R0062  | Violation    | Because the PN response varies by PWS Type   |
|        | Maintenance  | and you can apply a Standard Response from   |
|        | List         | the Violation Maintenance page (when one     |
|        | Enhancement  | validates violations), we need to allow      |
|        | to sort and  | sorting and filtering of violations by PWS   |
|        | filter based | Type. It would also be useful to include PWS |
|        | upon PWS     | Type as a column on the Violation            |
|        | Type and add | Maintenance List page. Also, we need to add  |
|        | a select all | a Select All that will select all records to |
|        | feature.     | which the user has filtered.                 |
+--------+--------------+----------------------------------------------+
| R0071  | Prompt to    | Request a feature that would prompt you to   |
|        | delete       | automatically delete all non-TCR sample      |
|        | non-TCR      | schedules when you inactivate a POE, instead |
|        | schedules    | of going through and deleted one by one.     |
|        | when a POE   |                                              |
|        | is           |                                              |
|        | inactivated  |                                              |
+--------+--------------+----------------------------------------------+
| R0077  | Add ability  | Add functionality for determining            |
|        | to determine | Significant Excursion / Operational          |
|        | significant  | Evaluation.                                  |
|        | excursion    |                                              |
|        | /operational |                                              |
|        | evaluation   |                                              |
+--------+--------------+----------------------------------------------+
| R0079  | Redesign the | I would like to suggest we have a            |
|        | Enforcement  | user-friendly Enforcement Module - when      |
|        | Web          | entering Compliance Schedules you have to    |
|        | Pages-       | come out and go back in - let's change that  |
|        | particularly | so you can continue moving along without     |
|        | compliance   | exiting first. Also, can we have the         |
|        | schedules.   | Compliance Schedules all listed on one page  |
|        |              | instead of layers of pages?                  |
+--------+--------------+----------------------------------------------+
| R0083  | Support a    | Allow users to associate a compliance        |
|        | compliance   | schedule to multiple deficiencies from       |
|        | schedule     | multiple site visits. Would suggest to       |
|        | assignment   | simply present the deficiency list in select |
|        | to multiple  | only with all unresolved deficiencies        |
|        | deficiencies | listed.                                      |
|        | (across site |                                              |
|        | visits)      |                                              |
+--------+--------------+----------------------------------------------+
| R0087  | Enhance the  | We need to enhance the current high results  |
|        | current high | alert in *CDS Setup* to look for:\           |
|        | results      | \                                            |
|        | alert in     | · high nitrate and nitrite results, i.e.,    |
|        | *CDS Setup*  | 1038, 1040 and 1041 and\                     |
|        |              | · high chlorite and chlorine dioxide entry   |
|        |              | point results (this one would need to look   |
|        |              | at MDBP Summaries for these two and report   |
|        |              | any where the \"Number of Samples Exceeded\" |
|        |              | (SMPLS_BYND_MEA_LVL) is \> 0\                |
|        |              | \                                            |
|        |              | Adding these will result in *CDS Setup*      |
|        |              | looking for results above MCLs or MRDLs for  |
|        |              | all acute related contaminants (it already   |
|        |              | looks for chlorite and chlorine dioxide      |
|        |              | individual results above their MCL/MRDL).    |
+--------+--------------+----------------------------------------------+
| R0089  | DBP          | SDWIS/STATE needs to allow schedules with    |
|        | Schedules -  | different frequencies for TThm and HAA to    |
|        | overlapping  | exist as the same time and to average        |
|        | TThm and HAA | results collected for the two to be averaged |
|        | should be    | together. This situation requirement this is |
|        | allowed and  | a PWS with one or more treatment plants that |
|        | averaged     | disinfect SW (and thus requiring quarterly   |
|        |              | monitoring in the DS for TThm and HAA) and   |
|        |              | one or more that disinfect GW (and thus      |
|        |              | requiring annual monitoring for smaller      |
|        |              | systems).                                    |
+--------+--------------+----------------------------------------------+
| R0092  | Sample Data  | It is useful to provide template windows for |
|        | Entry        | entering sample results. However, it would   |
|        |              | be nice to have the option to enter sample   |
|        |              | results directly into a template in the form |
|        |              | of a table where each row is a separate      |
|        |              | sample report, with columns for items such   |
|        |              | as lab report number, sample date, analyte,  |
|        |              | sample result, and unit of measure. This     |
|        |              | would offer a way to avoid clicking through  |
|        |              | several screens when entering multiple       |
|        |              | results for the same water system.           |
+--------+--------------+----------------------------------------------+
| R0094  | Running      | The Results Averages function of the         |
|        | Annual       | Sampling Component provides monitoring       |
|        | Average      | period and running annual average numbers in |
|        | (RAA) need   | the screen for individual monitoring periods |
|        | expanding to | and the maintenance list for all monitoring  |
|        | four decimal | periods for a specific analyte schedule.     |
|        | places       | While the monitoring period average provides |
|        |              | averages that show several places after the  |
|        |              | decimal point, the running annual average -- |
|        |              | at least for 2456 and 2950- show just two    |
|        |              | places after the decimal point. This results |
|        |              | in the reader not being able to tell if the  |
|        |              | RAA exceeds the MCL for the analyte. For     |
|        |              | example, if a RAA for HAA5 (2456) is shown   |
|        |              | as 0.060 mg/L, it is unclear whether the RAA |
|        |              | is really 0.064 and exceeds the MCL, of if   |
|        |              | it is 0.060 mg/L. It would be a good idea to |
|        |              | extend the numbers to at least four places   |
|        |              | to the right of the decimal point.           |
+--------+--------------+----------------------------------------------+
| R0095  | Automatic    | It would be useful to automatically generate |
|        | SOX          | a SOX action for failure-to-monitor          |
|        | Generation   | violations during CDS Set-Up immediately     |
|        |              | following the time a sample result is        |
|        |              | entered for the same monitoring period (late |
|        |              | report) or for a subsequent monitoring       |
|        |              | period. It would be useful to automatically  |
|        |              | generate a SOX action for MCL violations     |
|        |              | during CDS Set-Up immediately following the  |
|        |              | time a sample result or RAA computation      |
|        |              | falls below the MCL for that analyte and     |
|        |              | associated rule.                             |
+--------+--------------+----------------------------------------------+
| R0097  | Non TCR      | From the Sys Admin component, when flowing   |
|        | Schedule     | to monitoring requirement selection list     |
|        | Template     | from Non-TCR Schedule Template Maintenance,  |
|        | Maintenanc   | should be able to add a new monitoring       |
|        | e/Monitoring | requirement.                                 |
|        | Requirement  |                                              |
|        | Mainte       |                                              |
|        | nance-enable |                                              |
|        | Add function |                                              |
+--------+--------------+----------------------------------------------+
| R0105  | Deficiency   | Request the ability to associate a           |
|        | Mainten      | deficiency to a state-defined regulation.    |
|        | ance-support |                                              |
|        | association  |                                              |
|        | to           |                                              |
|        | s            |                                              |
|        | tate-defined |                                              |
|        | regulations. |                                              |
+--------+--------------+----------------------------------------------+
| R0106  | Consider     | Implement the use of waivers in the          |
|        | Waivers to   | compliance components so that candidate      |
|        | avoid        | violations are not created if a waiver is in |
|        | candidate    | place.\                                      |
|        | violations   | \                                            |
|        |              | Enhance waivers to have analyte exceptions   |
|        |              | and the monitoring requirement being waived, |
|        |              | and then use that in coordination with the   |
|        |              | sample schedules in the compliance           |
|        |              | components.\                                 |
|        |              | \                                            |
|        |              | Allow a waiver to be issued for a rule and   |
|        |              | not only by an analyte.                      |
+--------+--------------+----------------------------------------------+
| R0108  | Treatment    | Need to be able to indicate that a           |
|        | unit         | chlorinator was inoperable for a temporary   |
|        | maintenance  | period of time. This affects Stage 1 and     |
|        |              | Stage 2 D/DBP monitoring requirement.        |
+--------+--------------+----------------------------------------------+
| R0109  | New Operator | Would like a functionality to support        |
|        | C            | Operator Certification.                      |
|        | ertification |                                              |
|        | component    |                                              |
+--------+--------------+----------------------------------------------+
| R0110  | Water system | Several primacy agencies would like support  |
|        | acquisitions | for water system acquisitions.               |
+--------+--------------+----------------------------------------------+
| R0111  | Red Flag     | Would like to develop a visual notification  |
|        | warning      | on the water system to red-flag if it is     |
|        | indicator    | under certain enforcement actions.           |
|        | for water    |                                              |
|        | systems that |                                              |
|        | are under    |                                              |
|        | enforcement  |                                              |
|        | action       |                                              |
+--------+--------------+----------------------------------------------+
| R0114  | Temporarily  | Need ability to make a WSF non-operational   |
|        | inactive WSF | for a temporary period of time and thus      |
|        |              | exempt it from monitoring WITHOUT having to  |
|        |              | close the schedules.                         |
+--------+--------------+----------------------------------------------+
| R0115  | Request for  | Would like to be able to generate a federal  |
|        | ability to   | violation for a seasonal collection time.    |
|        | generate a   |                                              |
|        | federal      |                                              |
|        | violation    |                                              |
|        | for a        |                                              |
|        | seasonal     |                                              |
|        | collection   |                                              |
|        | time         |                                              |
+--------+--------------+----------------------------------------------+
| R0116  | Request for  | Some states would want to categorize these   |
|        | comment      | comments for review and retrieval.           |
|        | d            |                                              |
|        | ocumentation |                                              |
|        | component    |                                              |
|        | for water    |                                              |
|        | system       |                                              |
+--------+--------------+----------------------------------------------+
| R0117  | Non TCR      | Change the State Notification Date label to  |
|        | sample       | be the Primacy Received Date.                |
|        | schedule     |                                              |
+--------+--------------+----------------------------------------------+
| R0118  | Maintain     | Would like to see support of VIEWS in the    |
|        | views on the | DBMS to support add-on applications.         |
|        | DBMS in      |                                              |
|        | support of   |                                              |
|        | add-on       |                                              |
|        | applications |                                              |
+--------+--------------+----------------------------------------------+
| R0120  | TCR sample   | 1\. Allow creation of non-acute TCR MCL to   |
|        | validation - | be optional.\                                |
|        | optional     | \                                            |
|        | creation of  | 2. Provide for a non-acute TCR MCL to be     |
|        | violations.  | created when the validated positive RPs were |
|        |              | not collected within the prescribed time.    |
+--------+--------------+----------------------------------------------+
| R0122  | Enhance      | Allow a waiver to be issued for a rule and   |
|        | Waivers to   | not only by an analyte.                      |
|        | be recorded  |                                              |
|        | by rule      |                                              |
+--------+--------------+----------------------------------------------+
| R0124  | Relocate the | Pulling mailing lists is difficult since the |
|        | address      | address information is spread among the      |
|        | information, | multiple physical legal entity tables.       |
|        | perhaps with | Perhaps it could be pulled out and shared in |
|        | the other    | the say way the phone numbers and emails     |
|        | c            | have been with SSWr1.                        |
|        | ommunication |                                              |
|        | elements     |                                              |
+--------+--------------+----------------------------------------------+
| R0125  | Provide      | In the same manner as *CDS Setup*, provide   |
|        | ability to   | the ability to schedule CDS Reports to be    |
|        | schedule CDS | run in a background job schedule             |
|        | Reports      | environment.                                 |
+--------+--------------+----------------------------------------------+
| R0129  | Modify MRDL  | Request to modify the MRDL Summary page by   |
|        | Summary to   | having the user have the option of selecting |
|        | facility     | the quarter and then, on the page enable the |
|        | input of     | user to enter the monthly values for the 3   |
|        | quarterly    | months in the quarter and then calculate the |
|        | results      | quarterly average and running annual         |
|        |              | average.                                     |
+--------+--------------+----------------------------------------------+

**APPENDIX C**

SDWIS/STATE 2.0 Requirements Traceability Matrix

This page is intentionally left blank.

**SDWIS/STATE 2.0 Requirements Traceability Matrix**

+------+-------------------+-------------------------+----+-----+-----+
| *    | **Summary**       | **Description**         | ** | **  | **T |
| *Req |                   |                         | Af | Des | est |
| uire |                   |                         | fe | ign | C   |
| ment |                   |                         | ct | Do  | ase |
| Numb |                   |                         | ed | cum | /** |
| er** |                   |                         | De | ent |     |
|      |                   |                         | si | Re  | **P |
|      |                   |                         | gn | fer | roc |
|      |                   |                         | Ar | enc | Re  |
|      |                   |                         | ea | e** | fer |
|      |                   |                         | ** |     | enc |
|      |                   |                         |    |     | e** |
+======+===================+=========================+====+=====+=====+
| R    | Replacement       | Compliance processes    |    |     |     |
| 0004 | Samples should be | should include          |    |     |     |
|      | included in the   | replacement samples     |    |     |     |
|      | count of          | when counting collected |    |     |     |
|      | collected         | samples.                |    |     |     |
|      | samples. (tcr and |                         |    |     |     |
|      | non tcr)          |                         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Deleting          | Provide functionality   |    |     |     |
| 0005 | Treatment         | to delete treatment     |    |     |     |
|      | Objective Process | objective process       |    |     |     |
|      | Pairings          | pairings.\              |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Need ability to delete  |    |     |     |
|      |                   | or at least expire      |    |     |     |
|      |                   | method pairings.        |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Update the CFR    | Update the CFR Table to |    |     |     |
| 0008 | Table to include  | include newest Code of  |    |     |     |
|      | new CFRs          | Federal Regulation      |    |     |     |
|      |                   | references (change to   |    |     |     |
|      |                   | HQ rows).               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Site Visit        | Add a new permitted     |    |     |     |
| 0010 | Maintenance       | value for each of the   |    |     |     |
|      |                   | Category Evaluation     |    |     |     |
|      |                   | Summaries (on the Site  |    |     |     |
|      |                   | Visit maintenance       |    |     |     |
|      |                   | window) and make it the |    |     |     |
|      |                   | default: "Not           |    |     |     |
|      |                   | applicable."            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Site Visit        | Add an edit check       |    |     |     |
| 0011 | Maintenance -     | between Category        |    |     |     |
|      | advisory for      | Evaluation Summary and  |    |     |     |
|      | discrepancy of    | Deficiencies, for       |    |     |     |
|      | category and      | instance if a           |    |     |     |
|      | severity          | deficiency is added of  |    |     |     |
|      |                   | category SW and         |    |     |     |
|      |                   | severity Minor check    |    |     |     |
|      |                   | the Source Water        |    |     |     |
|      |                   | category in Category    |    |     |     |
|      |                   | Evaluation Summary. If  |    |     |     |
|      |                   | it is not of Minor or   |    |     |     |
|      |                   | higher give user a      |    |     |     |
|      |                   | warning that there is   |    |     |     |
|      |                   | discrepancy and option  |    |     |     |
|      |                   | of automatically        |    |     |     |
|      |                   | updating the category   |    |     |     |
|      |                   | evaluation summary or   |    |     |     |
|      |                   | leaving unchanged. Note |    |     |     |
|      |                   | when update the         |    |     |     |
|      |                   | category evaluation     |    |     |     |
|      |                   | summary check the       |    |     |     |
|      |                   | Highest Deficiency      |    |     |     |
|      |                   | Severity and if         |    |     |     |
|      |                   | necessary update it.    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | non-TCR Schedule  | Enable users to see the |    |     |     |
| 0013 | Maintenance -     | Applicable Periods and  |    |     |     |
|      | presentation of   | Gap Periods for a       |    |     |     |
|      | application       | schedule by adding a    |    |     |     |
|      | periods and gap   | button to the Non-TCR   |    |     |     |
|      | periods           | Sample Schedule         |    |     |     |
|      |                   | Maintenance window. The |    |     |     |
|      |                   | list that is displayed  |    |     |     |
|      |                   | should include the four |    |     |     |
|      |                   | date attributes         |    |     |     |
|      |                   | APPLIC                  |    |     |     |
|      |                   | ABLE_PERIOD_BEGIN_DATE, |    |     |     |
|      |                   | APP_PER_GAP_BEGIN_DATE, |    |     |     |
|      |                   | APP_PER_GAP_END_DATE,   |    |     |     |
|      |                   | and                     |    |     |     |
|      |                   | APP                     |    |     |     |
|      |                   | LICABLE_PERIOD_END_DATE |    |     |     |
|      |                   | in that order. These    |    |     |     |
|      |                   | are all from            |    |     |     |
|      |                   | SAMP_SCHED              |    |     |     |
|      |                   | ULE_MNTRG_PERIOD_ASGMT. |    |     |     |
|      |                   | The default sort should |    |     |     |
|      |                   | be by                   |    |     |     |
|      |                   | APPLI                   |    |     |     |
|      |                   | CABLE_PERIOD_BEGIN_DATE |    |     |     |
|      |                   | ascending. Users should |    |     |     |
|      |                   | be able to toggle       |    |     |     |
|      |                   | between view all        |    |     |     |
|      |                   | Applicable Periods and  |    |     |     |
|      |                   | view current and future |    |     |     |
|      |                   | Applicable Periods with |    |     |     |
|      |                   | the first being the     |    |     |     |
|      |                   | default.                |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Violation         | Provide an advisory to  |    |     |     |
| 0016 | Maintenance -     | user if packaged        |    |     |     |
|      | warning when      | violations are not      |    |     |     |
|      | packaging         | duplicate by data       |    |     |     |
|      | violations that   | (duplicate check in     |    |     |     |
|      | are not duplicate | this case should be     |    |     |     |
|      | (by data)         | Water System, Violation |    |     |     |
|      |                   | Type Type Code, or Fed  |    |     |     |
|      |                   | Violation Period Begin  |    |     |     |
|      |                   | Dates, and Federal      |    |     |     |
|      |                   | Reportable Cont. Code   |    |     |     |
|      |                   | (note that WSF was      |    |     |     |
|      |                   | intentionally omitted). |    |     |     |
|      |                   | This advisory could be  |    |     |     |
|      |                   | added to the online     |    |     |     |
|      |                   | software. This is       |    |     |     |
|      |                   | needed because, as is,  |    |     |     |
|      |                   | a state could easily    |    |     |     |
|      |                   | improperly package      |    |     |     |
|      |                   | violations and not      |    |     |     |
|      |                   | report some that should |    |     |     |
|      |                   | be federally reported.  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Violation         | Add Ratio as a uom code |    |     |     |
| 0021 | Maintenance -     | on the violation        |    |     |     |
|      | needs Ratio       | maintenance page.       |    |     |     |
|      | option for UOM    |                         |    |     |     |
|      | field             |                         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Improve           | It is my understanding  |    |     |     |
| 0029 | presentation      | that with the present   |    |     |     |
|      | violations that   | SDWIS/STATE software, a |    |     |     |
|      | are individual    | state can set up a      |    |     |     |
|      | violation         | \"Group Violation\" for |    |     |     |
|      | components of a   | an \"Analyte Group\"    |    |     |     |
|      | group violation   | which contains          |    |     |     |
|      |                   | individual violations   |    |     |     |
|      |                   | with individual         |    |     |     |
|      |                   | violation IDs and       |    |     |     |
|      |                   | individual analyte      |    |     |     |
|      |                   | codes. If a SDWIS/STATE |    |     |     |
|      |                   | user (other than the    |    |     |     |
|      |                   | administrator) has the  |    |     |     |
|      |                   | desire to view the      |    |     |     |
|      |                   | individual Analyte Code |    |     |     |
|      |                   | associated with the     |    |     |     |
|      |                   | individual Violation ID |    |     |     |
|      |                   | number, it appears that |    |     |     |
|      |                   | this viewing is not as  |    |     |     |
|      |                   | straightforward as one  |    |     |     |
|      |                   | might desire (e.g. a    |    |     |     |
|      |                   | work around query would |    |     |     |
|      |                   | have to be set up to    |    |     |     |
|      |                   | view the individual     |    |     |     |
|      |                   | analyte code when one   |    |     |     |
|      |                   | knows the individual    |    |     |     |
|      |                   | Violation ID number).\  |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Presently, the          |    |     |     |
|      |                   | Violation Maintenance   |    |     |     |
|      |                   | List window shows (for  |    |     |     |
|      |                   | group violations) the   |    |     |     |
|      |                   | violation Type,         |    |     |     |
|      |                   | Compliance Period Begin |    |     |     |
|      |                   | Date, Compliance Period |    |     |     |
|      |                   | End Date, Status, etc., |    |     |     |
|      |                   | but does not list the   |    |     |     |
|      |                   | internal parts of a     |    |     |     |
|      |                   | group violation (i.e.   |    |     |     |
|      |                   | the individual          |    |     |     |
|      |                   | Violation Analyte code  |    |     |     |
|      |                   | related to the          |    |     |     |
|      |                   | individual Violation ID |    |     |     |
|      |                   | number). Add a view     |    |     |     |
|      |                   | (for group violations)  |    |     |     |
|      |                   | for the individual      |    |     |     |
|      |                   | Violation ID number     |    |     |     |
|      |                   | related to its          |    |     |     |
|      |                   | individual Analyte      |    |     |     |
|      |                   | Code.                   |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Add advisory when | We had a user           |    |     |     |
| 0033 | inactivating a    | inadvertently           |    |     |     |
|      | water system that | inactivate a water      |    |     |     |
|      | sample schedules  | system when the intent  |    |     |     |
|      | will be closed.   | was to inactivate a     |    |     |     |
|      |                   | facility. The result    |    |     |     |
|      |                   | was that *CDS Setup*    |    |     |     |
|      |                   | closed approximately    |    |     |     |
|      |                   | 6,500 sample            |    |     |     |
|      |                   | schedules.\             |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | When a small            |    |     |     |
|      |                   | inadvertent change can  |    |     |     |
|      |                   | do this kind of damage, |    |     |     |
|      |                   | we need a warning       |    |     |     |
|      |                   | message to remind the   |    |     |     |
|      |                   | user of the             |    |     |     |
|      |                   | consequences of the     |    |     |     |
|      |                   | change.                 |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Expand State      | Request to expand the   |    |     |     |
| 0036 | Classification    | permitted value for the |    |     |     |
|      | Code from 3 to 4  | State Classification    |    |     |     |
|      | characters        | Code from 3 characters  |    |     |     |
|      |                   | to 4, that way the      |    |     |     |
|      |                   | codes can be set to     |    |     |     |
|      |                   | match the analyte group |    |     |     |
|      |                   | codes.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | WSF Purchases     | The drop-down list for  |    |     |     |
| 0037 | page drop down    | "Seller Treatment" in   |    |     |     |
|      | for seller        | the Receiving           |    |     |     |
|      | treatment needs   | Facility/Water Purchase |    |     |     |
|      | standardized      | Maintenance page does   |    |     |     |
|      | code-description  | not have the code       |    |     |     |
|      | format            | preceding the text      |    |     |     |
|      |                   | description.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Resizable Menu    | Request to make the     |    |     |     |
| 0045 | Navigation panel  | blue navigation panel   |    |     |     |
|      |                   | either sizeable or to   |    |     |     |
|      |                   | be minimized.           |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | WSF Maintenance   | On the facility         |    |     |     |
| 0053 | Page-add More     | maintenance screen in   |    |     |     |
|      | button to top of  | SSWr1, the "More"       |    |     |     |
|      | page too.         | button should appear at |    |     |     |
|      |                   | the top of the screen   |    |     |     |
|      |                   | as well as the bottom.  |    |     |     |
|      |                   | If a person wants to    |    |     |     |
|      |                   | skip over the main      |    |     |     |
|      |                   | facility page, they can |    |     |     |
|      |                   | do so quickly.          |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | General Page      | Line up and size field  |    |     |     |
| 0054 | Layout-line up    | blanks consistently     |    |     |     |
|      | and size fields   | where possible. It      |    |     |     |
|      |                   | makes screens look neat |    |     |     |
|      |                   | and less cluttered. For |    |     |     |
|      |                   | example, looking at the |    |     |     |
|      |                   | coliform sample screen, |    |     |     |
|      |                   | field blanks could be   |    |     |     |
|      |                   | better justified and    |    |     |     |
|      |                   | sized the same so they  |    |     |     |
|      |                   | appear more like        |    |     |     |
|      |                   | columns of data.        |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | CDS Table         | Re-key the CDS tables   |    |     |     |
| 0055 | Identifiers       | to concatenate User ID, |    |     |     |
|      |                   | jobrun, date, or some   |    |     |     |
|      |                   | other element with the  |    |     |     |
|      |                   | IS numbers to mitigate  |    |     |     |
|      |                   | risk of reaching upper  |    |     |     |
|      |                   | limit of the IS number. |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Violation         | The Violation Selection |    |     |     |
| 0057 | Chem/Rad          | lists (all, not just    |    |     |     |
|      | Selection List    | chem/rad) display only  |    |     |     |
|      |                   | 500 rows. When there    |    |     |     |
|      |                   | are more, need a way to |    |     |     |
|      |                   | access them.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Lab Certification | Please provide a lab    |    |     |     |
| 0059 | Module            | certification module.\  |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Request a lab           |    |     |     |
|      |                   | certification module    |    |     |     |
|      |                   | where MDL can be        |    |     |     |
|      |                   | entered by the state at |    |     |     |
|      |                   | the laboratory level.   |    |     |     |
|      |                   | These levels would then |    |     |     |
|      |                   | be used to provide      |    |     |     |
|      |                   | warnings when labs      |    |     |     |
|      |                   | reported MDL different  |    |     |     |
|      |                   | that the value          |    |     |     |
|      |                   | designated by the       |    |     |     |
|      |                   | state.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Allow entry of    | If the email could be   |    |     |     |
| 0061 | email at time of  | set up like that of     |    |     |     |
|      | submission for    | SDWIS/FedRep where the  |    |     |     |
|      | the XML/Sampling  | user has the option to  |    |     |     |
|      | job.              | enter an email address  |    |     |     |
|      |                   | at time of submission.  |    |     |     |
|      |                   | One problem that I can  |    |     |     |
|      |                   | see states running into |    |     |     |
|      |                   | is that there may be    |    |     |     |
|      |                   | many people running in  |    |     |     |
|      |                   | sample data and if all  |    |     |     |
|      |                   | of their names are      |    |     |     |
|      |                   | entered then they will  |    |     |     |
|      |                   | be getting email about  |    |     |     |
|      |                   | data submissions for    |    |     |     |
|      |                   | other people, whereas   |    |     |     |
|      |                   | if the property file    |    |     |     |
|      |                   | just contained a        |    |     |     |
|      |                   | default email address   |    |     |     |
|      |                   | then that would be used |    |     |     |
|      |                   | for batch runs, but if  |    |     |     |
|      |                   | a user is manually      |    |     |     |
|      |                   | kicking off SDWIS/XML   |    |     |     |
|      |                   | then they could change  |    |     |     |
|      |                   | it so that only the     |    |     |     |
|      |                   | default email address   |    |     |     |
|      |                   | and themselves received |    |     |     |
|      |                   | the email, versus       |    |     |     |
|      |                   | having to add everybody |    |     |     |
|      |                   | to the default email    |    |     |     |
|      |                   | list.                   |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Correct Country   | FED Codes- FED          |    |     |     |
| 0064 | Code              | DESCRIPTION/            |    |     |     |
|      | abbreviations     | SDWIS/STATE Codes-      |    |     |     |
|      |                   | SDWIS/STATE             |    |     |     |
|      |                   | DescriptionAL-ALBANIA   |    |     |     |
|      |                   | /AL-AZERBAIJANTC-UNITED |    |     |     |
|      |                   | ARAB                    |    |     |     |
|      |                   | EMIRATES/TC-TRINIDAD    |    |     |     |
|      |                   | AND                     |    |     |     |
|      |                   | TOBAGOAJ-AZERBAIJA      |    |     |     |
|      |                   | N/AL-AZERBAIJANFO-FAROE |    |     |     |
|      |                   | ISLANDS/FQ-FAROE        |    |     |     |
|      |                   | ISLANDSTD-TRINIDAD AND  |    |     |     |
|      |                   | TOBAGO/TC-TRINIDAD AND  |    |     |     |
|      |                   | TOBAGO                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | TINCODE.REF       | Please expand length of |    |     |     |
| 0065 | _ATTRIBUTE_NAME - | attribute name          |    |     |     |
|      | please expand     | REF_ATTRIBUTE_NAME from |    |     |     |
|      | length to 50      | 30 to 50 characters.    |    |     |     |
|      | characters        |                         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | TMNVPRDR and      | We should add a USERID  |    |     |     |
| 0066 | TMNVDCR need      | and                     |    |     |     |
|      | userid and last   | LAST_UPDATE_TIMESTAMP   |    |     |     |
|      | update timestamp  | to the TMNVPRDR and     |    |     |     |
|      |                   | TMNVDCR tables. All     |    |     |     |
|      |                   | records should be       |    |     |     |
|      |                   | initially set with      |    |     |     |
|      |                   | SSWR1 and 1/1/2005.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | XML/Sampling      | The display of errors   |    |     |     |
| 0067 | Errors Display    | should include the      |    |     |     |
|      | should include    | error number next to    |    |     |     |
|      | their Numbers     | its description. We     |    |     |     |
|      |                   | should add the number   |    |     |     |
|      |                   | of each error next to   |    |     |     |
|      |                   | its text.               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | XML/Sampling      | The links should always |    |     |     |
| 0068 | pages should      | be available for users  |    |     |     |
|      | always display    | to click on, no matter  |    |     |     |
|      | the links in Left | which page they are on. |    |     |     |
|      | Navigation Bar    | For example when I      |    |     |     |
|      |                   | clicked on (View Job    |    |     |     |
|      |                   | Details by Date or View |    |     |     |
|      |                   | System Property Files   |    |     |     |
|      |                   | or View Log Files) that |    |     |     |
|      |                   | link disappeared. You   |    |     |     |
|      |                   | should leave it in the  |    |     |     |
|      |                   | navigation bar or at    |    |     |     |
|      |                   | least disable it.       |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Consistency       | The links on the left   |    |     |     |
| 0069 | Between Links on  | navigation bar and      |    |     |     |
|      | Left Navigation   | their corresponding     |    |     |     |
|      | Bar and their     | titles on each page     |    |     |     |
|      | Corresponding     | should match and be     |    |     |     |
|      | Titles on each    | consistent. For example |    |     |     |
|      | Page (xml         | for: View Job Details   |    |     |     |
|      | sampling)         | by Date link the page   |    |     |     |
|      |                   | title should say: Job   |    |     |     |
|      |                   | Details by Date, for    |    |     |     |
|      |                   | link: View all Jobs the |    |     |     |
|      |                   | page title should say:  |    |     |     |
|      |                   | All Jobs, and so on.\   |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Also, the font style    |    |     |     |
|      |                   | and size should be      |    |     |     |
|      |                   | consistent in all the   |    |     |     |
|      |                   | pages.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Job Detail Page   | Add a new column for    |    |     |     |
| 0070 | \-- Adding New    | the total records       |    |     |     |
|      | Column for Total  | submitted.              |    |     |     |
|      | Records Submitted |                         |    |     |     |
|      | (xml sampling)    |                         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Expand size of    | Need to increase the    |    |     |     |
| 0072 | the TINWSF        | size of the TINWSF      |    |     |     |
|      | external system   | external system number. |    |     |     |
|      | number            | Some primacy agencies   |    |     |     |
|      |                   | are hitting the max.    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Notify users of   | Add a message that      |    |     |     |
| 0073 | Removal of Total  | notifies the user of    |    |     |     |
|      | Coliform and      | impending removal of    |    |     |     |
|      | Acute Speciation  | the Total Coliform and  |    |     |     |
|      | Result when it    | Acute Speciation Result |    |     |     |
|      | will be           | values, if any had been |    |     |     |
|      | automatically     | provided. (For example  |    |     |     |
|      | removed due to a  | , if a sample had       |    |     |     |
|      | sample status     | Speciation and then,    |    |     |     |
|      | change.           | the record is changed   |    |     |     |
|      |                   | to include a Rejection  |    |     |     |
|      |                   | Reason, the speciation  |    |     |     |
|      |                   | is cleared, add an      |    |     |     |
|      |                   | advisory)               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | ODD needs to      | There are three ways    |    |     |     |
| 0074 | Display Permitted | permitted values are    |    |     |     |
|      | Values from       | recorded in SSWr1:      |    |     |     |
|      | TSAOSAPM and      | Hard-coded, in the      |    |     |     |
|      | Similar Tables    | TINCODE plus TINPVALS   |    |     |     |
|      |                   | tables and in new       |    |     |     |
|      |                   | tables like TSAOSAPM    |    |     |     |
|      |                   | (Other Sample Measures  |    |     |     |
|      |                   | Tables). The ODD for    |    |     |     |
|      |                   | SSWr1 only accounts for |    |     |     |
|      |                   | the first two. The      |    |     |     |
|      |                   | third method needs to   |    |     |     |
|      |                   | be incorporated so      |    |     |     |
|      |                   | that, for example, when |    |     |     |
|      |                   | a user selects the      |    |     |     |
|      |                   | Other Sample Measures   |    |     |     |
|      |                   | table within the ODD    |    |     |     |
|      |                   | and picks any of the    |    |     |     |
|      |                   | attributes and selects  |    |     |     |
|      |                   | permitted values, a     |    |     |     |
|      |                   | report showing all the  |    |     |     |
|      |                   | records in the table    |    |     |     |
|      |                   | should be displayed.\   |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | These tables can be     |    |     |     |
|      |                   | added as local tables   |    |     |     |
|      |                   | to the ODD for this     |    |     |     |
|      |                   | purpose:\               |    |     |     |
|      |                   | TCDSPMSG\               |    |     |     |
|      |                   | TMNCOR\                 |    |     |     |
|      |                   | TMNMNCON\               |    |     |     |
|      |                   | TMNMPD\                 |    |     |     |
|      |                   | TMNMRCA\                |    |     |     |
|      |                   | TMNMRLOC\               |    |     |     |
|      |                   | TMNRULE\                |    |     |     |
|      |                   | TMNSTAT\                |    |     |     |
|      |                   | TMNVDCR\                |    |     |     |
|      |                   | TMNVPRDR\               |    |     |     |
|      |                   | TMNVTAA\                |    |     |     |
|      |                   | TMNVTRA\                |    |     |     |
|      |                   | TSACVCR\                |    |     |     |
|      |                   | TSAOSAPM\               |    |     |     |
|      |                   | TSAOSPM\                |    |     |     |
|      |                   | TSASAMT\                |    |     |     |
|      |                   | TSASMMT\                |    |     |     |
|      |                   | TSASRSC\                |    |     |     |
|      |                   | TSASRSR\                |    |     |     |
|      |                   | TSAUOM\                 |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Additionally add a      |    |     |     |
|      |                   | report that shows the   |    |     |     |
|      |                   | TCR Monitoring          |    |     |     |
|      |                   | Conditions. The best    |    |     |     |
|      |                   | would be to have a link |    |     |     |
|      |                   | to the three tables     |    |     |     |
|      |                   | used to establish these |    |     |     |
|      |                   | in replacement of the   |    |     |     |
|      |                   | locally imported tables |    |     |     |
|      |                   | for TMNMNR, TMNMRCA,    |    |     |     |
|      |                   | and TMNMNCON.           |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | *CDS Setup* needs | In SDWIS/STATE Release  |    |     |     |
| 0076 | clarification on  | 8, an attribute in SAR  |    |     |     |
|      | when to use the   | is used to tell *CDS    |    |     |     |
|      | direct SAR to MP  | Setup* whether to use   |    |     |     |
|      | relationship to   | the directly linked MP  |    |     |     |
|      | control the SSMPA | to control the SSMPA    |    |     |     |
|      | connection.       | connection or not. We   |    |     |     |
|      |                   | removed that attributes |    |     |     |
|      |                   | involvement in SSWr1    |    |     |     |
|      |                   | and replaced it with    |    |     |     |
|      |                   | logic that says if a MP |    |     |     |
|      |                   | is directly linked to a |    |     |     |
|      |                   | SAR, it should be used  |    |     |     |
|      |                   | instead of the          |    |     |     |
|      |                   | collection date when    |    |     |     |
|      |                   | linking to SSMPAs.\     |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Near the end of the     |    |     |     |
|      |                   | release, we determined  |    |     |     |
|      |                   | that this change in     |    |     |     |
|      |                   | logic presented some    |    |     |     |
|      |                   | new problems. However,  |    |     |     |
|      |                   | it was decided that it  |    |     |     |
|      |                   | was too risky to        |    |     |     |
|      |                   | correct in SSWr1.\      |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | We should either go     |    |     |     |
|      |                   | back to the way Release |    |     |     |
|      |                   | 8 did it or change *CDS |    |     |     |
|      |                   | Setup* so that it never |    |     |     |
|      |                   | makes a direct link -   |    |     |     |
|      |                   | i.e., only a user can   |    |     |     |
|      |                   | make a direct link.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Locational MAD    | There are still         |    |     |     |
| 0080 | codes to be       | \"unknown\" MAD codes   |    |     |     |
|      | removed from      | for locational data in  |    |     |     |
|      | SDWIS/STATE       | SDWIS/STATE look up     |    |     |     |
|      |                   | tables (TINPVALS).\     |    |     |     |
|      |                   | TINLOC1-HZ_COLLE        |    |     |     |
|      |                   | CT_METH_CD-027-Unknown\ |    |     |     |
|      |                   | TINLOC3-SOUR            |    |     |     |
|      |                   | CE_MAP_SCALE-U-Unknown\ |    |     |     |
|      |                   | TINLOC4-REFERENC        |    |     |     |
|      |                   | E_POINT_CD-001-Unknown\ |    |     |     |
|      |                   | TINLOC4-REFERE          |    |     |     |
|      |                   | NCE_POINT_CD-003-Other\ |    |     |     |
|      |                   | TINLOC7-VERIF_          |    |     |     |
|      |                   | METHOD_CD-010-Verified, |    |     |     |
|      |                   | unknown method\         |    |     |     |
|      |                   | TINLOC8-VER             |    |     |     |
|      |                   | _COL_METH_CD-008-Other, |    |     |     |
|      |                   | Unspecified\            |    |     |     |
|      |                   | TINLOC9-VERT            |    |     |     |
|      |                   | _REF_DATUM_CD-U-Unknown |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Review CDS        | The Review Reports Log  |    |     |     |
| 0082 | Reports Log and   | and Reports should be   |    |     |     |
|      | Reports - allow   | sorted by Report Type   |    |     |     |
|      | sort options      | as well as Run Time.    |    |     |     |
|      |                   | Right now it is only    |    |     |     |
|      |                   | sorted by Report Type.  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Expand method     | There\'s not enough     |    |     |     |
| 0084 | number field      | room in the method      |    |     |     |
|      | length.           | number field to add the |    |     |     |
|      |                   | method number -         |    |     |     |
|      |                   | QuikChem 10-204-00-1-X, |    |     |     |
|      |                   | Distillation/           |    |     |     |
|      |                   | Spectrophotometric.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Initial MP Begin  | When entering a new TCR |    |     |     |
| 0085 | Date for TCR      | schedule, the Initial   |    |     |     |
|      | Schedule should   | MP Begin Date should be |    |     |     |
|      | be set to null.   | defaulted to NULL if no |    |     |     |
|      |                   | value is provided.      |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | 01 MCL Violations | First, need to modify   |    |     |     |
| 0088 | and 02 MCL        | *CDS Setup* to delete   |    |     |     |
|      | Violations        | 01 candidate if a       |    |     |     |
|      | processing in     | matching 02 candidate   |    |     |     |
|      | *CDS Setup*       | is determined. Matching |    |     |     |
|      |                   | here involves all the   |    |     |     |
|      |                   | same criteria as        |    |     |     |
|      |                   | matching standard       |    |     |     |
|      |                   | matching except         |    |     |     |
|      |                   | violation type will not |    |     |     |
|      |                   | match (i.e., same PWS,  |    |     |     |
|      |                   | same WSF -- if          |    |     |     |
|      |                   | supplied, same analyte, |    |     |     |
|      |                   | same State Begin        |    |     |     |
|      |                   | Date).\                 |    |     |     |
|      |                   | \                       |    |     |     |
|      |                   | Second, need to modify  |    |     |     |
|      |                   | the *CDS Setup* process |    |     |     |
|      |                   | that looks for an       |    |     |     |
|      |                   | existing R, P, or V     |    |     |     |
|      |                   | violation in TMNVIOL    |    |     |     |
|      |                   | before creating a       |    |     |     |
|      |                   | candidate violation to: |    |     |     |
|      |                   | look for a matching R,  |    |     |     |
|      |                   | P, or V, type 01        |    |     |     |
|      |                   | violation when a        |    |     |     |
|      |                   | candidate 02 has been   |    |     |     |
|      |                   | determined.             |    |     |     |
|      |                   |                         |    |     |     |
|      |                   | However, in this case,  |    |     |     |
|      |                   | *CDS Setup* should      |    |     |     |
|      |                   | still create the        |    |     |     |
|      |                   | candidate 02 and then,  |    |     |     |
|      |                   | here is the new part,   |    |     |     |
|      |                   | it should create an     |    |     |     |
|      |                   | advisory. Normally, in  |    |     |     |
|      |                   | this situation, the     |    |     |     |
|      |                   | user will go and delete |    |     |     |
|      |                   | the existing 01         |    |     |     |
|      |                   | violation and migrate   |    |     |     |
|      |                   | the candidate 02.       |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Eliminate the     | SDWIS/FedRep has        |    |     |     |
| 0098 | Home Variable in  | automated the           |    |     |     |
|      | XML/Sampling      | determination of this   |    |     |     |
|      | system-properties | parameter. The same     |    |     |     |
|      | file.             | should be done in XML   |    |     |     |
|      |                   | Sampling.               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Online support of | SDWIS/FedRep is         |    |     |     |
| 0099 | system variable   | developing an online    |    |     |     |
|      | file and auto     | maintenance page of the |    |     |     |
|      | execution of      | system variable file.   |    |     |     |
|      | schemautility.bat | Same should be          |    |     |     |
|      | in XML Sampling   | implemented in XML      |    |     |     |
|      |                   | Sampling.               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Web Enable *CDS   | Re-architect *CDS       |    |     |     |
| 0100 | Setup*            | Setup* to execute on    |    |     |     |
|      |                   | the web environment.    |    |     |     |
|      |                   | (Requires               |    |     |     |
|      |                   | identification of new   |    |     |     |
|      |                   | reporting technology.)  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Web Enable CDS    | Re-architect CDS        |    |     |     |
| 0101 | Report            | Reports (including EBS  |    |     |     |
|      |                   | Reports) to execute on  |    |     |     |
|      |                   | the web environment.    |    |     |     |
|      |                   | (Requires               |    |     |     |
|      |                   | identification of new   |    |     |     |
|      |                   | reporting technology.)  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Permitted Values  | Increase size of the    |    |     |     |
| 0107 | Maintenance -     | description text on the |    |     |     |
|      | increase length   | pv table.               |    |     |     |
|      | of description    |                         |    |     |     |
|      | text.             |                         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Provide ability   | For instances where the |    |     |     |
| 0123 | to record why a   | violation was rejected  |    |     |     |
|      | violation may     | due to a waiver, would  |    |     |     |
|      | have been         | like to be able to      |    |     |     |
|      | rejected          | record that reason with |    |     |     |
|      |                   | the rejected violation. |    |     |     |
|      |                   | These reasons should be |    |     |     |
|      |                   | controlled by the       |    |     |     |
|      |                   | system administrator.   |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | The job and       | The job and detail      |    |     |     |
| 0126 | detail pages for  | pages truncate data     |    |     |     |
|      | XML Sampling      | when printed. The pages |    |     |     |
|      | output should be  | offer a printable       |    |     |     |
|      | printable.        | format.                 |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Re-design the TCR | The TCR Compliance      |    |     |     |
| 0127 | Compliance Report | Report was modified for |    |     |     |
|      | back to 8.0       | SSWr1 release and would |    |     |     |
|      | version           | like it back to release |    |     |     |
|      |                   | 8.0 design.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Provide Link from | Request to add the      |    |     |     |
| 0128 | Candidate         | ability to flow         |    |     |     |
|      | Violation         | directly to the         |    |     |     |
|      | Migration into    | Violation Maintenance   |    |     |     |
|      | Violation         | List after migrating    |    |     |     |
|      | Maintenance       | candidate violations so |    |     |     |
|      |                   | that a user can         |    |     |     |
|      |                   | complete the processing |    |     |     |
|      |                   | of the candidate        |    |     |     |
|      |                   | violations. This        |    |     |     |
|      |                   | function could ask the  |    |     |     |
|      |                   | user, after clicking on |    |     |     |
|      |                   | one of the "Migrate as  |    |     |     |
|      |                   | Prelimin                |    |     |     |
|      |                   | ary/Validated/Rejected" |    |     |     |
|      |                   | functions if the user   |    |     |     |
|      |                   | wants to go to the      |    |     |     |
|      |                   | Violation Maintenance   |    |     |     |
|      |                   | List to further process |    |     |     |
|      |                   | the violations. If the  |    |     |     |
|      |                   | answer is yes, flow to  |    |     |     |
|      |                   | the maintenance list    |    |     |     |
|      |                   | with the violations     |    |     |     |
|      |                   | listed that the user    |    |     |     |
|      |                   | just migrated. From     |    |     |     |
|      |                   | here then, the user     |    |     |     |
|      |                   | could finish processing |    |     |     |
|      |                   | using existing          |    |     |     |
|      |                   | capabilities.           |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Implement         | Implement the processes |    |     |     |
| 2000 | compliance        | and supporting data to  |    |     |     |
|      | support for Long  | automate compliance     |    |     |     |
|      | Term 2 Rule       | determination in        |    |     |     |
|      |                   | accordance with the     |    |     |     |
|      |                   | Long Term 2 rule. This  |    |     |     |
|      |                   | general business        |    |     |     |
|      |                   | requirement is          |    |     |     |
|      |                   | supported by            |    |     |     |
|      |                   | component-specific      |    |     |     |
|      |                   | requirements numbered   |    |     |     |
|      |                   | as R2001 through R2015. |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Provide edits for       |    |     |     |
| 2001 | LT2,              | sample results          |    |     |     |
|      |                   | submitted by labs       |    |     |     |
|      |                   | certified for the       |    |     |     |
|      |                   | method.                 |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Increase/Decrease       |    |     |     |
| 2002 | LT2,              | Monitoring Report to    |    |     |     |
|      |                   | include evaluation of   |    |     |     |
|      |                   | Cryptosporidium         |    |     |     |
|      |                   | monitoring based on *E. |    |     |     |
|      |                   | coli* mean.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Identification of       |    |     |     |
| 2003 | LT2,              | candidate violations    |    |     |     |
|      |                   | for Sample collections  |    |     |     |
|      |                   | taken outside of the    |    |     |     |
|      |                   | sampling plan           |    |     |     |
|      |                   | specification and       |    |     |     |
|      |                   | Treatment Technique     |    |     |     |
|      |                   | violations.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Determination of *E.    |    |     |     |
| 2004 | LT2,              | coli* and               |    |     |     |
|      |                   | Cryptosprodium means    |    |     |     |
|      |                   | based upon quantities   |    |     |     |
|      |                   | for the monitoring      |    |     |     |
|      |                   | period and the running  |    |     |     |
|      |                   | annual average.         |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Determine BIN number    |    |     |     |
| 2005 | LT2,              | and status based upon   |    |     |     |
|      |                   | verification 12         |    |     |     |
|      |                   | consecutive months of   |    |     |     |
|      |                   | monitoring.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Add Treatment Technique |    |     |     |
| 2006 | LT2,              | Compliance Report.      |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Create new              |    |     |     |
| 2007 | LT2,              | returned-to-compliance  |    |     |     |
|      |                   | enforcement action for  |    |     |     |
|      |                   | resolved deficiencies.  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Add ability to assign   |    |     |     |
| 2008 | LT2,              | system                  |    |     |     |
|      |                   | a                       |    |     |     |
|      |                   | dministrator-controlled |    |     |     |
|      |                   | roles to the parties    |    |     |     |
|      |                   | present at the site     |    |     |     |
|      |                   | visit.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Add Site Visit Due Date |    |     |     |
| 2009 | LT2,              | (separate from the      |    |     |     |
|      |                   | completed date) and the |    |     |     |
|      |                   | ability to list Site    |    |     |     |
|      |                   | Visits with due dates   |    |     |     |
|      |                   | within a user-specified |    |     |     |
|      |                   | date range, regulating  |    |     |     |
|      |                   | agency and/or role.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Display a list of all   |    |     |     |
| 2010 | LT2,              | deficiencies for a      |    |     |     |
|      |                   | water system and the    |    |     |     |
|      |                   | violations associated   |    |     |     |
|      |                   | to each deficiency.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Provide access to the   |    |     |     |
| 2011 | LT2,              | maintenance of the      |    |     |     |
|      |                   | deficiency-to-violation |    |     |     |
|      |                   | associations from the   |    |     |     |
|      |                   | deficiency side.        |    |     |     |
|      |                   | (Currently this         |    |     |     |
|      |                   | maintenance function is |    |     |     |
|      |                   | only accessible from    |    |     |     |
|      |                   | the violation side.)    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Increase the            |    |     |     |
| 2012 | LT2,              | description length of a |    |     |     |
|      |                   | deficiency.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Support compliance for  |    |     |     |
| 2013 | LT2,              | sampling periodicity    |    |     |     |
|      |                   | frequency of every 2    |    |     |     |
|      |                   | weeks.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Enhance Deficiency      |    |     |     |
| 2014 | LT2,              | maintenance page to     |    |     |     |
|      |                   | populate severity and   |    |     |     |
|      |                   | evaluation category     |    |     |     |
|      |                   | based upon the          |    |     |     |
|      |                   | deficiency type         |    |     |     |
|      |                   | selected.               |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Provide System          |    |     |     |
| 2015 | LT2,              | Administrators the      |    |     |     |
|      |                   | ability to associate a  |    |     |     |
|      |                   | deficiency type to a    |    |     |     |
|      |                   | severity level and also |    |     |     |
|      |                   | to a site visit         |    |     |     |
|      |                   | evaluation category.    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Implement         | Implement the processes |    |     |     |
| 3000 | Compliance        | and supporting data to  |    |     |     |
|      | support for Stage | automate compliance     |    |     |     |
|      | 2 Rule            | determination in        |    |     |     |
|      |                   | accordance with the     |    |     |     |
|      |                   | Stage 2 rule. This      |    |     |     |
|      |                   | general business        |    |     |     |
|      |                   | requirement is          |    |     |     |
|      |                   | supported by            |    |     |     |
|      |                   | component-specific      |    |     |     |
|      |                   | requirements numbered   |    |     |     |
|      |                   | as R3001 through R3021. |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Provide edits for       |    |     |     |
| 3001 | Stage 2,          | sample results          |    |     |     |
|      |                   | submitted by labs       |    |     |     |
|      |                   | certified for the       |    |     |     |
|      |                   | method.                 |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R3   | In support of     | Addition of new analyte |    |     |     |
| 0018 | Stage 2,          | reporting levels.       |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Record sample           |    |     |     |
| 3002 | Stage 2,          | collection interval.    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Ability to schedule     |    |     |     |
| 3003 | Stage 2,          | monitoring for the same |    |     |     |
|      |                   | analyte at different    |    |     |     |
|      |                   | frequencies.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Maintenance of          |    |     |     |
| 3004 | Stage 2,          | violations per the      |    |     |     |
|      |                   | reporting guidance.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Add periodicity of      |    |     |     |
| 3005 | Stage 2,          | every 2 months for      |    |     |     |
|      |                   | monitoring.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Flexibility to indicate |    |     |     |
| 3006 | Stage 2,          | need for Locational     |    |     |     |
|      |                   | Running Annual Average  |    |     |     |
|      |                   | calculation.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Integration of Sampling |    |     |     |
| 3007 | Stage 2,          | Plans with Non-TCR      |    |     |     |
|      |                   | Sample Schedules to     |    |     |     |
|      |                   | generate sub-schedules. |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Enhance Sampling Plans  |    |     |     |
| 3008 | Stage 2,          | to distinguish between  |    |     |     |
|      |                   | IDSE and Subpart V.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Functionality to        |    |     |     |
| 3009 | Stage 2,          | support analyte level   |    |     |     |
|      |                   | specifications for      |    |     |     |
|      |                   | sampling points.        |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Support the recording   |    |     |     |
| 3010 | Stage 2,          | of a water system\'s    |    |     |     |
|      |                   | compliance decisions    |    |     |     |
|      |                   | such as a 40/30         |    |     |     |
|      |                   | certification.          |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Increase/Decrease       |    |     |     |
| 3011 | Stage 2,          | Monitoring Report to    |    |     |     |
|      |                   | include TThm, HAA5, and |    |     |     |
|      |                   | Bromate.                |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Identification of       |    |     |     |
| 3012 | Stage 2,          | candidate violations    |    |     |     |
|      |                   | for sample collections  |    |     |     |
|      |                   | taken inside the        |    |     |     |
|      |                   | specified collection    |    |     |     |
|      |                   | interval, failure to    |    |     |     |
|      |                   | conduct required IDSE   |    |     |     |
|      |                   | monitoring, and failure |    |     |     |
|      |                   | to submit required IDSE |    |     |     |
|      |                   | report.                 |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | *CDS Setup* should      |    |     |     |
| 3013 | Stage 2,          | create a locational     |    |     |     |
|      |                   | running annual average, |    |     |     |
|      |                   | if specified as         |    |     |     |
|      |                   | necessary.              |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Check for TTHM and HAA5 |    |     |     |
| 3014 | Stage 2,          | dual sample collection  |    |     |     |
|      |                   | on same day.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Enhance association of  |    |     |     |
| 3015 | Stage 2,          | SAR to SSMPA to         |    |     |     |
|      |                   | disallow \'double       |    |     |     |
|      |                   | dipping\' of the SAR    |    |     |     |
|      |                   | for satisfying both an  |    |     |     |
|      |                   | IDSE Sample schedule    |    |     |     |
|      |                   | AND a Stage 1 Sample    |    |     |     |
|      |                   | scheduled collected at  |    |     |     |
|      |                   | the same sampling       |    |     |     |
|      |                   | point.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Use of new sampling     |    |     |     |
| 3016 | Stage 2,          | point analyte levels in |    |     |     |
|      |                   | compliance              |    |     |     |
|      |                   | determination.          |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Support for 2-month     |    |     |     |
| 3017 | Stage 2,          | monitoring period       |    |     |     |
|      |                   | maintenance.            |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Record the designation  |    |     |     |
| 3019 | Stage 2,          | of sampling points such |    |     |     |
|      |                   | as High HAA and High    |    |     |     |
|      |                   | PHM.                    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Include IDSE results    |    |     |     |
| 3020 | Stage 2,          | for TThm and HAA5 in    |    |     |     |
|      |                   | the CCRWriter.          |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Report to list all TThm |    |     |     |
| 3021 | Stage 2,          | results and all HAA5    |    |     |     |
|      |                   | results for each        |    |     |     |
|      |                   | treatment plant subject |    |     |     |
|      |                   | to IDSE monitoring.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | Implement         | Implement the processes |    |     |     |
| 4000 | compliance        | and supporting data to  |    |     |     |
|      | support for       | automate compliance     |    |     |     |
|      | Ground water Rule | determination in        |    |     |     |
|      |                   | accordance with the     |    |     |     |
|      |                   | Groundwater Rule. This  |    |     |     |
|      |                   | general business        |    |     |     |
|      |                   | requirement is          |    |     |     |
|      |                   | supported by            |    |     |     |
|      |                   | component-specific      |    |     |     |
|      |                   | requirements numbered   |    |     |     |
|      |                   | as R4001 through R4007. |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Determine candidate     |    |     |     |
| 4001 | Groundwater Rule, | violations in           |    |     |     |
|      |                   | compliance              |    |     |     |
|      |                   | determination for       |    |     |     |
|      |                   | Ongoing Viral           |    |     |     |
|      |                   | Monitoring reporting.   |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Ability to maintain the |    |     |     |
| 4002 | Groundwater Rule, | schedule result         |    |     |     |
|      |                   | substitute conditions   |    |     |     |
|      |                   | tables for specifying   |    |     |     |
|      |                   | the analytes allowed to |    |     |     |
|      |                   | satisfy groundwater     |    |     |     |
|      |                   | rule monitoring (i.e.   |    |     |     |
|      |                   | the crosswalk table).   |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Ability to assign       |    |     |     |
| 4003 | Groundwater Rule, | system                  |    |     |     |
|      |                   | a                       |    |     |     |
|      |                   | dministrator-controlled |    |     |     |
|      |                   | roles to the parties    |    |     |     |
|      |                   | present at the site     |    |     |     |
|      |                   | visit.                  |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Add Site Visit Due Date |    |     |     |
| 4004 | Groundwater Rule, | (separate from the      |    |     |     |
|      |                   | completed date) and the |    |     |     |
|      |                   | ability to list Site    |    |     |     |
|      |                   | Visits with due dates   |    |     |     |
|      |                   | within a user-specified |    |     |     |
|      |                   | date range, regulating  |    |     |     |
|      |                   | agency and/or role.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Display a list of all   |    |     |     |
| 4005 | Groundwater Rule, | deficiencies for a      |    |     |     |
|      |                   | water system and the    |    |     |     |
|      |                   | violations associated   |    |     |     |
|      |                   | to each deficiency.     |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Provide access to the   |    |     |     |
| 4006 | Groundwater Rule, | maintenance of the      |    |     |     |
|      |                   | deficiency-to-violation |    |     |     |
|      |                   | associations from the   |    |     |     |
|      |                   | deficiency side.        |    |     |     |
|      |                   | (Currently this         |    |     |     |
|      |                   | maintenance function is |    |     |     |
|      |                   | only accessible from    |    |     |     |
|      |                   | the violation side.)    |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+
| R    | In support of     | Increase the            |    |     |     |
| 4007 | Groundwater Rule, | description length of a |    |     |     |
|      |                   | deficiency.             |    |     |     |
+------+-------------------+-------------------------+----+-----+-----+

This page is intentionally left blank.

[^1]: Impact dates assume rule publication in October 2005.

[^2]: []{.mark}