![](media/image1.jpeg){width="1.7361111111111112in"
height="0.6388888888888888in"}

Quality Assurance Plan for Ground-Water Activities

U.S. Geological Survey

Nebraska Water Science Center

######### **For Administrative Use Only** 

# 

# 

United States Department of the Interior

U.S. Geological Survey

Updated April 2005

Contents

[INTRODUCTION 4](#introduction)

[ORGANIZATION AND RESPONSIBILITIES
5](#organization-and-responsibilities)

[TRAINING 5](#training)

[PROJECT PLANNING AND REVIEW 5](#project-planning-and-review)

[Development of Work Plan 6](#development-of-work-plan)

[Project Reviews 7](#project-reviews)

[Data Collection 7](#data-collection)

[Documentation of Technical Procedures
8](#documentation-of-technical-procedures)

[Instrumentation 8](#instrumentation)

[DATA PROCESSING, REVIEW, AND STORAGE
9](#data-processing-review-and-storage)

[DATA ANALYSIS 9](#data-analysis)

[PUBLICATIONS 10](#publications)

[ARCHIVING 10](#archiving)

[AUDIT 11](#audit)

**Appendixes**

Quality Assurance Plan for Ground-Water Activities

# INTRODUCTION

This quality-assurance plan provides formal procedures for documentation
and review of policies, practices, and activities that are used by the
Nebraska Water Science Centerto assure the technical quality and
reliability of District ground-water products. The plan is based upon
the following principles:

District ground-water programs and projects will be planned efficiently
and effectively to provide information needed to evaluate National water
problems and local and State problems that are nationally relevant.
Technical and scientific activities will be performed in accordance with
applicable WRD practices and policies. Ground-water activities will be
accomplished by technically qualified personnel performing at a level
commensurate with their training and experience. All such activities and
projects will receive appropriate and timely review for completeness,
reliability, and credibility. Remedial actions will be taken to correct
any observed technical or project deficiency.

The intent of the ground-water quality-assurance program for
ground-water activities does not differ in any substantial way from
similar plans addressing water-quality and surface-water activities.
However, because of the greater emphasis on data synthesis and
interpretation in ground-water studies, and because of the limited
number of formal standards to govern the conduct of such studies, the
ground-water plan places greater emphasis on the technical review
process. For example, there is no single established technique used to
select \"correct\" values of storage coefficient or transmissivity for
use in a ground-water flow model or other publication. The formal
training, breadth of experience, and technical judgment of the Project
Chief, the Investigation Section Chiefs, and the District Ground-Water
Specialist contribute to the standards against which interpretive
products are compared.

Procedures for quality assurance generally conform to guidelines
presented in the report, \"A quality-assurance plan for district
ground-water activities of the U.S. Geological Survey\" (Brunett and
others, 1997). A copy of that document is included in Appendix A.

# ORGANIZATION AND RESPONSIBILITIES

Suggestions for the organization and responsibilities for conduct and
review of district ground-water projects, data collection, and other
activities are listed on pages 3 and 4 of the National Ground Water
Quality-Assurance Plan (Appendix A).

For the most part the Nebraska Water Science Centeremulates the National
plan in that The District Chief is ultimately responsible for
ground-water quality assurance in the Nebraska District; however, by
delegation the District Chief shares certain aspects of quality
assurance with the Field Office Chiefs, the District Section Chiefs, the
District Ground-Water Specialist, and all Project Chiefs. These
individuals, in turn, share their responsibility with every person in
the District who collects, stores, interprets, or disseminates these
data and interpretations of those data.

# TRAINING

The qualifications of project personnel relative to the technical
demands of the work will be determined by the Project Chief and the
District discipline specialists. Training to remedy deficiencies will be
recommended. Training, including that on the job, will be used to ensure
technical competence or to rectify inadequacies. The Hydrologic Studies
Section Chief, the Central Nebraska Basin NAWQA Chief, and the
Hydrologic Data Section Chief will develop annually a plan to provide
the required training for personnel under their supervision who engage
in ground-water activities. These plans will be presented to the
District Chief at the beginning of each fiscal year.

Training will be provided routinely to field personnel by appropriate
USGS or outside specialists to ensure uniformity in data-collection
procedures. In those activities that involve the use of
instrumentation\--pressure transducers, data loggers, flow meters,
geophysical equipment, etc.\--training of field personnel by the Field
Office Chiefs, the Hydrologic Studies Section Chief, or appropriate
District discipline specialist is essential. Field personnel are
expected to be familiar with the manuals on all instrumentation. These
manuals will be filed in the Hydrologic Data Section.

# PROJECT PLANNING AND REVIEW

Project planning includes project staffing and preparation of a
project-planning document (work plan). The District Chief has the
responsibility for the selection of the Project Chief, but the selection
will be made in consultation with the Chief of the Hydrologic Studies
Section, NAWQA, and the District discipline specialists as appropriate.
All projects will receive technical review at established times during
the life of the project.

##  Development of Work Plan

The development of a project work plan typically begins in discussions
with the cooperator or within the District staff, regarding a
ground-water problem or need. At this point a prospective Project Chief,
in consultation with appropriate District discipline specialists,
section or unit chiefs, and experienced ground-water personnel, develops
a project proposal. Generally, this proposal indicates the overall
purpose, scope, objectives, strategy, duration, relevance, general
personnel requirements, funding, and products of the study. The District
has adopted a project proposal review procedure, which is designed to
ensure that proposals meet the specifications established by Central
Region policy.

Following approval of the project proposal by Region, the Project Chief,
using the project proposal, writes a standard project description for
MIS, and this description and a preliminary budget are entered into
BASIS+. The Project Chief, if necessary, then develops a detailed work
plan and budget. The work plan summarizes data needs and clarifies
technical approaches, identifies work elements, itemizes costs, defines
total personnel needs, and provides deadlines for each work element
(Appendix B). A timeline chart is developed to illustrate the major
milestones and their intended deadlines. Requirements for work by
various support units in the District, by the cooperator, or by
contractors are clearly identified and scheduled.

A report plan is developed as an integral part of the project work plan.
The plan identifies the type, scope, and intended audience of all
planned reports. It also provides a preliminary outline of each report,
including a description of major illustrations and tables. Preparation
of the work plan will require the Project Chief to confer with the
appropriate Hydrologic Studies Section Chief, the District specialists,
cooperators, and any other persons, USGS or non-USGS, who may offer
guidance or insight into the problem being investigated.

The work plan and reports plan will meet the financial and temporal
limits already placed on the study and will schedule the submission of
the final report(s) so that Regional approval will be granted and
publication can occur prior to the conclusion of project funding. The
Hydrologic Data and Studies Section Chief, the appropriate District
discipline specialists, the District Reports Specialist, and the
District Chief will review the work plan and report plan. Review may
also be sought from Regional or Headquarters personnel, or from the
cooperating agency. The Project Chief will develop the final work plan
and report plan in response to the review comments.

If, during development of the work plan, it becomes clear that the
technology, funding, personnel, or time indicated in the original
project description are inadequate to meet project objectives, two
versions of the work plan will be completed. In one of these versions,
the objectives will be reduced to fit the originally estimated
resources; in the other version, the resources will be increased to meet
the original objectives. These two plans, after appropriate internal
review, will form the basis for further negotiations with the
cooperating agency and the District staff on modifications to the
original proposal. A final plan will be developed from the results of
these negotiations. The general personnel requirements of the project
will be determined in the early stages of project planning and modified
as the work plan is developed. As the need for each position on the
project staff is established, selection procedures will be initiated and
the staff assembled. This process will normally overlap the process of
developing the work plan.

## Project Reviews

All projects will receive technical review at established times during
the life of the project. All projects will be reviewed quarterly. Each
quarterly review will focus on a specific aspect of the project and the
Project Chief will complete a quarterly review form that will serve as
the documentation for the review. Reviews will be held in the first
month of each quarter of the fiscal year (October, January, April, and
July). In addition, ongoing and frequent, informal reviews are conducted
during team meetings and during discussions among project staff,
supervisors, discipline specialists, and others, as appropriate. The
Investigative Studies Section maintains notes and review forms from the
District project reviews.

## 

## Data Collection

The types of data collected, the standards governing the precision and
accuracy of these data, and the frequency with which data are collected
may differ among the various District ground-water projects, according
to the objectives of the studies. The Project Chief must clearly
document and provide to the project personnel instructions regarding
data collection so that the project\'s data needs are satisfied. Routine
and non-routine data-collection activities and procedures are documented
by project or support personnel and are recorded in appropriate field
notebooks. These notes are to be kept with project files and archived
upon project completion.

Supervision of field procedures and activities is an essential
responsibility of the Project Chief who must assure through personal
observation that field personnel are fully qualified. The District
ground-water specialist will review the data gathering activities of all
ground-water projects on a semi-annual basis during project reviews.
Training, including that on the job, will be used to ensure technical
competence or to rectify inadequacies.

Individual field practices are spot-checked by the Field Office Chiefs.
The frequency and intensity of these checks generally are matched with
each field person\'s individual capabilities and experience. However,
even the practices of the most experienced and capable field personnel
are checked on at least a biennial basis, with more frequent checks
reserved for personnel of lesser experience.

# Documentation of Technical Procedures

Procedures used for the collection of ground-water data are derived from
a series of technical procedure documents, in technical memoranda,
Techniques of Water-Resources Investigations reports (TWRIs), and a
number of other publications. The primary documentation of technical
procedures is discussed in Appendix C, District Technical-Procedures
Documents. In the event that a technical-procedures document is not
available, techniques of data collection and analysis are discussed in
the \"National Handbook of Recommended Methods for Water-Data
Acquisition, Chapter 2\--Ground Water.\" This document contains
discussions of all the major types of ground-water data collection,
together with extensive bibliographies relevant to each activity.
Standards for ground-water data collection will be based on the methods
outlined in that chapter, or in the references contained therein.

Techniques for the collection of ground-water samples are given in
TWRIs, memoranda issued by the Office of Water Quality and in
publications with technical guidance provided by the District
water-quality specialist. The District ground-water specialist will
ensure that full coordination is arranged, and when applicable, that
suitable training in water-quality procedures is provided.

# Instrumentation

Analog, and basic data recorders (BDRs) are used by the Nebraska Water
Science Center to collect continuous water-level data. The SUTRON models
8100 and 8400 are the principal BDR-type recorders used by the District.
Manuals on each of these recorders are on file in the District Office
and also are provided to all field personnel.

At each recorder well site, an information card is in an accessible
place in the recorder shelter, or inside the recorder if possible, to
provide information about the well and recorder, to assist anyone
inspecting and/or servicing the recorder. Information listed includes
well name, grid number (County, Township, Range, and Section) time scale
(if analog), water-level scale (if analog), land-surface datum, height
and description of the measuring point above land-surface datum, and an
example of the computation necessary for starting the data collection of
the recorder.

All recorders are serviced on a 4- to 6‑week basis with recorders
serviced monthly or quarterly by USGS personnel depending on the project
objectives and funding. Recorders are calibrated within 0.03 feet of the
value indicated by the tape-down or pressure measurement, and the
recorder clock time is recorded and checked for accuracy prior to
changing the calibration of a recorder instrument. The water-level or
pressure measurement that indicated a recalibration was necessary are
repeated and verified. Continuous data are examined in the field to
determine if any problems occurred since the previous site visit.
Water-level and timer errors are recorded on the analog chart, or
entered into the BDR digital data file. A record of recorder
instrumentation is maintained in the District Ground Water Information
Unit (GWIU) data log-in file. Information recorded in this file includes
well name and identification numbers, aquifer, and recorder serial
number. Changes in recorder instrumentation are documented in this file
by date, serial number, and type.

To service recorder installations, technicians are supplied tools, spare
recorders and timers, and batteries. It is the responsibility of the
technician to replace (or repair if possible) equipment within 1 week of
detection of damage or malfunction. Battery voltages should be checked
during each site visit and replaced when necessary. Rechargeable
batteries removed from the site are recharged for future use.
Non-rechargeable batteries that are replaced are disposed of properly.
In addition, routine inspection and lubrication of recorder instruments
is conducted during each site visit. If the recorder site is inoperative
due to vandalism or other serious damage, and major repairs are
indicated, the field office personnel will report in writing to
supervisor within working 3 days of detection. The report should include
a description of the damage and an estimate of cost and time of repair.
At random intervals, Field Office Chiefs will visit selected recorder
stations to check that the recorders are being serviced and maintained
properly, and that proper procedures are being used to assure acceptably
accurate water-level measurements and to minimize periods of lost
record.

# DATA PROCESSING, REVIEW, AND STORAGE

Nebraska Water Science Center policy and procedures for ground-water
data processing, review, and storage are contained in the District
Data-Management Plan (Appendix D). The plan is an all-encompassing plan
for data of all types, and ground-water data are an integral part of
this overall plan.

# DATA ANALYSIS

The Nebraska Water Science Center uses numerous methods and procedures
for analyzing the ground-water data collected in the field including
statistical manipulation, graphing, contouring, spatial-data display,
and numerical modeling. All analyses receive an interpretative review by
supervisors, discipline specialists, and colleagues prior to
publication. More rigorous review procedures are provided for analyses
involving non-routine statistical analyses, aquifer testing, and
numerical modeling.

For quality assurance statistical data analyses are always referenced in
the publication presenting the interpretation. Aquifer-test analyses and
documentation follow OGW policy and are reviewed and approved by the
Regional Ground-Water Specialist before they can be released to the
public. Ground-water flow and transport models are quality assured by an
extensive review process by numerous experts culminating with the review
and approval by the Regional Ground-Water Specialist. Documentation of
all models follows the guidelines described in OGW Memorandum 96.04. If
a data-analysis procedure is not one previously established and
documented by the USGS the procedure must be described, reviewed, and
approved by the appropriate discipline specialist and the District Chief
prior to its use. The description should include enough detail so that
reviewers can determine the validity of the analysis. Analyses that
require only a short description can be included in the report where the
data analysis is used. Longer descriptions must be stand-alone
documents. All documentation of new analyses will be kept in the
District discipline specialists- files. All reviews and their
documentation will be kept on file with the appropriate discipline
specialist for a minimum of 5 years.

# PUBLICATIONS

The Nebraska Water Science Center uses publications to disseminate its
work to the public. Selected ground-water data collected at data sites
that are part of the State ground-water network in any fiscal year are
published in the Annual Data Report by the following April. Water-level
data collected in the spring of any year are published in the State
Ground-Water Conditions Report in the following July. Ground-water data
collected as part of project work is published in a data report within 6
months of the end of the data-collection phase of the project, or in the
final interpretive report for that project. The quality and accuracy of
these publications is assured by the review process. All publications
produced by personnel of the Nebraska Water Science Center go through a
10-step (minimum) process before they are approved (non-interpretive) or
passed to the Central Region Reports Specialist for approval. These
steps are found in figure 1. There can be more than two colleague
reviewers, depending on the report complexity.

# ARCHIVING

Nebraska Water Science Center policy and procedures for archiving
ground-water data are also contained in the District GWSI database
(Appendix D). Archiving of ground-water models is documented in the
District Model Archiving plan (Appendix E) and follows the guidelines
set forth in OGW Technical Memorandum 93.01. Aquifer-test data and
results are archived in files controlled by the District Ground-Water
Specialist as prescribed by OGW Technical Memorandum 94.02 and 00.02 and
maintained by the Data Management Unit. Approved and unapproved
aquifer-test results are archived.

Archiving project information after a project has been completed is the
responsibility of the Project Chief. Information subject to archiving
includes (1) field notes that document physical observations about the
project area, (2) hydrologic, geologic, or chemical data obtained from
outside sources as a result of personal contacts, (3) field maps on
which observations, measurements, geologic features, and data site
locations were noted, and (4) measured data not stored in one of the
District databases. The information should be given to the Data
Management Unit for filing in the technical files organized by
hydrologic system. Technical procedures or new data-analysis methods
developed should be given to the District Ground-Water Specialist for
appropriate archiving.

# ![](media/image2.png){width="3.9451388888888888in" height="5.08125in"}

# ![](media/image3.png){width="4.252083333333333in" height="2.68125in"}

Figure 1.---Flowchart of the report review process for the U.S.
Geological Survey-Nebraska District, November 2003.

# AUDIT

Audits are designed to ensure that all tasks described in the GWQAP are
being performed. Audits will be performed during the Technical District
Reviews to determine compliance with the GWQAP and associated documents
and the effectiveness of their implementation. Audits also include
observing field data-collection activities and reviewing office
documentation. The following quality-assurance activities shall be
performed by the Office of Ground Water.

1.  Develop an Audit Plan to monitor compliance with the requirements of
    the GWQAP. Audits apply to all ground-water field and office
    activities. The Audit Plan identifies the activities to be audited,
    scope of the audit, requirements governing the audit organizations
    to be notified (if any), applicable documents, and tentative audit
    schedule. The audit shall, as a minimum, address the following
    questions: Do training plans, work plans, technical-procedure
    documents, calibration records, and maintenance logs exist, are they
    complete, and are the plans and technical-procedure documents being
    implemented? Do data-management and archiving plans exist, are they
    complete and up-to-date, and are they being implemented? Are project
    reviews being performed and documented according to the GWQAP?

2.  Conduct the audit during the technical review of the District
    program.

3.  Document all comments and recommendations in the technical review
    report.

4.  Send all comments and recommendations to the Regional Hydrologist
    and the District. The Region is responsible to see that all
    recommendations are addressed. The Office of Ground Water will
    receive copies of all correspondence between the District and the
    Regional Hydrologist relating to audits and audit plans.

APPENDIX A: A QUALITY-ASSURANCE PLAN FOR DISTRICT GROUND-WATER
ACTIVITIES OF THE U.S. GEOLOGICAL SURVEY

###### Contents Page

[ABSTRACT 3](#abstract)

[INTRODUCTION 3](#introduction-1)

[ORGANIZATION AND RESPONSIBILITIES
5](#organization-and-responsibilities-1)

[TRAINING 7](#training-1)

[PLANNING 8](#planning)

[Work plans 8](#work-plans)

[Project Reviews 9](#project-reviews-1)

[DATA COLLECTION 10](#data-collection-1)

[Documentation of Technical Procedures
10](#documentation-of-technical-procedures-1)

[Documentation of Non-Routine Activities
11](#documentation-of-non-routine-activities)

[Instrumentation 12](#instrumentation-1)

[Identification and Control of Samples 13](#__RefHeading___Toc522520670)

[DATA PROCESSING, REVIEW, AND STORAGE
14](#data-processing-review-and-storage-1)

[DATA ANALYSIS 16](#data-analysis-1)

[PUBLICATIONS 17](#publications-1)

[ARCHIVING 18](#archiving-1)

[AUDIT 18](#audit-1)

[SUMMARY 19](#summary)

[REFERENCES CITED 19](#references-cited)

# ABSTRACT

As the Nation\'s principal earth-science information agency, the U.S.
Geological Survey (USGS) is depended upon to collect data of the highest
quality. This document provides the framework for collecting, analyzing
and reporting ground-water data that are quality assured and quality
controlled.

# INTRODUCTION

The Water Resources Division (WRD) of the U.S. Geological Survey (USGS)
performs a wide variety of ground-water data-collection programs and
investigations to assess the status of the Nation\'s ground-water
resources. Results of these activities are used to aid the Nation in
developing, managing, and maintaining its ground-water resources.

As the Nation\'s principal earth-science information agency, the USGS is
depended upon to collect accurate data and produce factual and impartial
interpretive reports. Methods for data collection and analysis that were
developed by the USGS have become standard techniques used by numerous
Federal, State, and local agencies and by private enterprises. Data
collected by scientific organizations such as the USGS are being used
increasingly by the public to define and examine a variety of natural
resource and environmental problems. Many of these problems are
addressed through an open, public process. As a result, scientific
organizations are being challenged to demonstrate the credibility of
their data on the basis of objective evidence rather than on the
organization\'s history and reputation.

To address these demands and expectations, the WRD has implemented a
program designed to ensure that all scientific work done by or for the
WRD is conducted in accordance with a quality- assurance (QA) program.
The Office of Ground Water (OGW), in coordination with the Branch of
Technical Development and Quality Systems, has the responsibility to
develop, coordinate, and implement the quality-assurance program for
District ground-water activities. As part of that program, the OGW has
directed the preparation of a Ground-Water Quality-Assurance Plan
(GWQAP), which covers all ground-water activities by District offices of
the USGS. USGS Open-File Reports (OFR) 92-136 (Schroder and Shampine,
1992) and 92-162 (Shampine and others, 1992) outline the guidelines for
preparing District quality-assurance plans and integrating the quality
assurance into project work plans. Guidelines presented here are
intended to supplement these two reports and provide more specific
details related to ground-water activities.

A quality-assurance plan (QAP) can be defined as a formal document that
describes the management policies, objectives, principles,
organizational authority, responsibilities, accountability, and
implementation plan of a responsible organizational unit or group for
ensuring quality in its products. The implementation of a GWQAP will
enhance ground-water data collected by the USGS by providing for the
following:

-   **Consistency** (across projects, subdistricts, WRD, and so forth);

-   **Accountability** (to client, scientific community, and regulatory
    agencies);

-   **Comparability** (yields results of known quality);

-   **Traceability** (written record of how, who, and when work was
    performed, training, equipment, etc.);

-   **Repeatability** (documentation of technique that leads to the
    similar results time after time with the same accuracy).

This report is a quality-assurance plan for ground-water activities
conducted by the USGS and is meant to complement quality-assurance plans
for surface-water and water-quality activities and similar plans for
District and general project activities throughout the USGS.

The purpose of this GWQAP is to establish a minimum set of guidelines
and practices to be used by Districts to assure quality in ground-water
activities. Included within these practices are the assignment of
responsibilities for implementing quality-assurance activities in the
District and establishment of review procedures needed to ensure the
technical quality and reliability of the ground-water products.

This report presents quality-assurance policies pertaining to the
collection, processing, analysis, storage, review, and publication of
ground-water data. In addition, policies related to organizational
responsibilities, training, and project planning are presented. These
policies and practices pertain to all ground-water activities conducted
by or for the District offices of the USGS. Ground-water activities
include all tasks pertaining to data-collection programs, interpretive
and research projects, and data management.

# ORGANIZATION AND RESPONSIBILITIES

Though quality assurance is a personal responsibility of all employees
of the USGS, ultimate quality-assurance responsibility within each
District lies with the District Chief. Clear statements of specific
responsibilities promote an understanding of each person\'s role in the
overall process of assuring quality and can help to prevent errors and
deficiencies that may otherwise occur. Implementation and follow-up
responsibilities lie with data-collection staff, project chiefs, section
chiefs, discipline specialists, District Chiefs, regional specialists,
and others. Even if quality-assurance responsibilities are ancillary
duties for some employees, these functions are to be documented.

The following is a list of specific responsibilities of District
personnel for implementing the GWQAP for ground-water activities.

The **District Chief** is responsible for:

-   Managing and directing the District program, including all
    ground-water activities.

-   Ensuring that ground-water activities in the District meet the needs
    of cooperating agencies, including state and local agencies, the
    general public, and the Federal Government.

-   Ensuring that all aspects of this GWQAP are understood and followed
    by District personnel.

-   Providing final resolution of any conflicts or disputes related to
    ground-water activities within the District.

-   Keeping District staff briefed on procedural and technical
    communications from Region and Headquarters.

-   Ensuring that technical reviews of all ground-water activities are
    conducted.

-   Ensuring that all publications and other technical communications
    released by the District are accurate and are in accord with USGS
    policy.

-   Ensuring that ground-water training is incorporated into each
    employee\'s training plan, where appropriate.

The **Section Chief** is responsible for:

-   Managing and directing ground-water activities assigned to the
    section and ensuring that the stated objectives are met in a timely
    manner.

-   Reviewing the work plans for ground-water programs and projects.

-   Providing the project chief with technical and administrative
    support as needed.

-   Creating, with ground-water personnel in the section, a training
    plan for each employee, where appropriate.

-   Reviewing ground-water reports under his or her direction.

-   Monitoring progress of ground-water project chiefs in implementing
    the GWQAP for their respective projects.

The **Ground-Water Project Chief** is responsible for:

-   Directing and conducting the technical work of the project,
    including all phases of data collection, data review, data storage,
    data analysis, and report preparation according to appropriate
    procedures.

-   Communicating project plans, progress, and problems to supervisors
    by providing written progress reports at periodic reviews.

-   Preparing written work plans, documenting project activities, and
    ensuring that data are placed in the USGS National Water Information
    System (NWIS) database, as appropriate, prior to project
    termination.

-   Maintaining a project file containing memoranda, personal
    communications, technical-procedure documents used, original data,
    and other documentation.

-   Ensuring that project activities are carried out in a timely manner.

-   Creating, with the supervisor, a personal training plan.

-   Archiving of project files, at the completion of the project.

Some of the duties of the District Ground-Water Specialist may be
delegated to other personnel. For the remainder of this report,
\"District Ground-Water Specialist\" will refer to these individuals.
The District shall appoint a Ground-Water Specialist whose duties shall
include but not be limited to:

-   Maintaining current ground-water technical expertise for the
    District.

-   Maintaining the ground-water technical-procedure documents file.

-   Consulting with the District staff on ground-water technical
    matters.

-   Advising on training needs for employees engaged in ground-water
    activities.

-   Participating in technical reviews of ground-water activities.

-   Reviewing ground-water-related project proposals.

-   Reviewing ground-water-related project reports.

# TRAINING

Employee training is an investment that has short-term and long-term
benefits to District ground-water activities. The immediate benefits
permit confidence that the work is being performed correctly and
accurately. The long-term benefits provide for technically competent
employees that are of great value to the organization. Because all work
in the scientific arena is receiving increased scrutiny, the
qualifications of ground-water personnel relative to the technical
demands of the work to be performed must be well documented. Training
already received as well as current and planned training need to be
incorporated into a documented training plan for each employee. Periodic
reviews of these plans by District management will help determine
additional training needs.

The following quality-assurance activities shall be performed by the
District:

1.  A written, reviewed, and approved training plan shall be prepared
    for each employee (including observers and volunteers, as
    appropriate) performing technical tasks relating to ground water.

```{=html}
<!-- -->
```
a.  Each training plan shall include an individual\'s short-term
    training needs, such as the knowledge and skills needed to perform
    currently assigned tasks as well as long-term training needs, such
    as skills needed to perform future tasks and for career development.

b.  Training plans should be reviewed and updated at least annually.

```{=html}
<!-- -->
```
5.  Individuals shall receive appropriate training before assigned tasks
    are performed. Appropriate training includes new employee training,
    USGS National Training Center courses, mentoring, on-the-job
    training (OJT), vendor-provided training, and academic courses.

6.  Each training activity shall be documented according to existing
    policy. The District shall establish a training file to facilitate
    cross-referencing by critical task and individual training.
    Qualifications of contractors performing tasks shall be documented.
    Qualifications of cooperators (Federal, State, and local agencies)
    performing tasks shall be to the satisfaction of the District Chief.

# PLANNING

Districts routinely conduct technical ground-water projects and
data-collection programs. The success of these activities is dependent
on a careful, deliberate, and systematic planning process.
Quality-assurance requirements should be integrated into the project
proposal, if one is required for the ground-water activity. Whether a
ground-water program or project requires a separate quality-assurance
plan should be evaluated on the basis of the complexity of the work, the
needs of the District or cooperator, or other criteria as described by
Shampine and others (1992).

A work plan shall be developed for every ground-water program or
project. The work plan can be a part of the proposal or a stand-alone
document. The complexity of the program or project will determine the
detail of the work plan. The project proposal may satisfy the
requirement of a work plan where ground-water activities are routine or
highly standardized. The work plan shall include, as appropriate,
data-collection and storage plans, equipment and instrumentation needs,
data-analysis techniques, report plans, cost estimates, time schedules,
availability of personnel, training needs, and other elements, as
necessary. Without appropriate project planning (Green, 1991) and the
documentation of

individual project tasks, quality objectives and project deadlines may
not be reasonably known. Initial project/program planning can be guided
by a detailed work plan; continued planning can be guided by periodic
reviews.

## Work Plans

To quality assure work plans, the District shall perform the following
steps:

1.  Work plans for programs with ground-water activities should clearly
    state that the GWQAP will be implemented.

```{=html}
<!-- -->
```
7.  To the extent practicable, work plans should state data-quality
    objectives and describe the strategies to collect data to meet the
    intended use. When developing data-quality objectives, broader
    network needs should be considered as well as immediate objectives.
    Data-Quality Objectives are those qualitative and quantitative
    statements developed by data users to specify the quality of data
    needed from a particular data-collection activity. For example, in
    order to describe land subsidence in an area, ground-water levels
    need to be measured using a particular method, at a particular
    frequency, and to a particular accuracy.

8.  The work plan shall specify the means for cataloging and archiving
    all ground-water activities and files according to WRD policy
    (Hubbard, 1992).

Development of work plans might also include the following:

1.  A bibliographic search of available reports, articles, data, and
    other pertinent information.

```{=html}
<!-- -->
```
9.  Retrieval of relevant data from existing databases in order to
    determine the availability of and the need for additional data.
    Errors or inconsistencies in the database should be identified and
    corrected at this time.

10. Review of other USGS file (paper) data, such as field canvass
    sheets, water-level records, geophysical logs, lithologic logs,
    water-quality laboratory analytical sheets, or other original data.

## Project Reviews

Project reviews are conducted periodically by District management,
technical advisors, or discipline specialists to ensure that project
objectives are being met and to evaluate implementation of the GWQAP.
Project reviews are used to maintain consistency in data collection,
data analysis, and reporting. The following quality-assurance functions
related to project reviews shall be performed by the District:

1.  The District shall establish and implement a ground-water program
    and project review schedule that considers the technical development
    and progress of the endeavor. The District shall schedule regular,
    periodic reviews such as quarterly reviews, or at the 10-, 40-, and
    70-percent (10/40/70) milestones of the project. Regularly planned
    reviews shall ensure that the ground-water program or project is
    implemented and performed in a manner that results in a quality
    product done efficiently. Numerous Districts have used the 10/40/70
    review process successfully. In general, the 10-percent review
    ensures that the project begins properly, that no major technical
    item is overlooked in the planning, and that the objectives can be
    accomplished with the proposed approach. The 10-percent review is
    scheduled after initial reconnaissance, bibliographic and database
    searches, and before any systematic data collection. A topical
    outline and initial report writing are begun at this early stage. An
    annotated report outline, including draft illustrations, and a base
    map typically should be completed at this stage. At the 40-percent
    review, data collection is well underway, preliminary conclusions
    made, and any problems in achieving project objectives should be
    identified. The 40-percent review shall confirm that all the tasks
    are on track to meet the planned objectives. The purpose of the
    70-percent review is to ensure that all the data required to meet
    the objectives have been obtained, that the data-analysis process is
    on schedule and is yielding expected or reasonable results, and that
    the report is on schedule.

```{=html}
<!-- -->
```
11. The District shall develop a procedure for documenting project
    reviews. At a minimum the following information should be included
    in project review documentation:

-   Date of review.

-   Type of review (quarterly, 10/40/70, discipline).

-   Names of reviewers and/or attendees.

-   Response to recommended action items from the last review.

-   Status, plans, and problems with data collection, data analysis, and
    report writing.

-   Major findings.

-   Cooperator/customer contacts.

-   Training needs.

-   Recommended follow-up or action items.

-   Date for next review.

12. The District shall develop a procedure for archiving project review
    comments, addressing the presence or absence of project deficiencies
    and all actions to fix deficiencies or document why a fix cannot be
    made.

# DATA COLLECTION

## Documentation of Technical Procedures

Written records of exactly how data are collected are critical to
establishing the consistency, comparability, repeatability, and
traceability of scientific data. The methods used to collect a specific
data set shall be documented and the documentation shall be maintained
with the data. For routine field activities, technical-procedure
documents are a means of ensuring that detailed documentation is
generated prior to data collection

and shall be identified or prepared during the formal planning phase of
the project, as applicable. A technical-procedure document is a detailed
description of a sequence of actions to be used to collect data to
ensure repeatability of the work and comparability of results.

If it is necessary to deviate from the technical-procedure documents
when collecting data, then these deviations must be clearly described in
the project records. When data-collection methods are new or
experimental, a record of the conduct, progress, and results of these
methods shall be maintained in a procedures notebook.

The following quality-assurance activities shall be performed by the
District.

1.  Technical-procedure documents shall be prepared for routine field
    data collection that is performed in support of ground-water
    activities. The water-quality aspects of ground-water activities
    that are addressed in the quality-assurance plan for water quality
    need not be duplicated. Technical-procedure documents shall be in
    place prior to data collection and shall contain the following:

```{=html}
<!-- -->
```
a.  A cover sheet that indicates the technical-procedure document
    number, title, author or compiler, reviewer, approval, effective
    dates for the procedure, and identification number for any
    technical-procedure documents superseded by the current
    technical-procedure document.

```{=html}
<!-- -->
```
c.  Purpose of the technical procedure; for example, \"this procedure
    explains how to measure water levels within 0.01 ft (foot) by using
    a chalked steel tape.\"

d.  Identification of materials and instruments used to collect data.

e.  Quantitative statement of the accuracy of data collected using the
    procedure (for example, \"to the nearest 0.1 ft\") and limitations
    on the use of these data.

f.  Statements about the advantages, disadvantages, and assumptions of
    the procedure.

g.  Step-by-step instructions to collect data that would enable an
    independent, qualified person to repeat the work and produce
    comparable results.

h.  A description of how data collected by using the procedure are
    recorded and preserved.

i.  A description of samples to be collected or used, if applicable.

j.  A listing of technical references used to compile the
    technical-procedure document.

k.  Attachments (field forms, operator\'s manual, diagrams, and other
    pertinent supporting information).

```{=html}
<!-- -->
```
13. The technical procedure used to collect data shall be indicated on
    the field form.

14. The District shall establish and maintain a file of
    technical-procedure documents.

```{=html}
<!-- -->
```
a.  Technical-procedure documents shall be identified with a unique
    number and cataloged and indexed.

```{=html}
<!-- -->
```
l.  The file shall be maintained by the District Ground-Water Specialist
    or designee.

m.  The file shall contain all current and superseded versions of
    technical-procedure documents.

```{=html}
<!-- -->
```
15. Deviations from approved technical procedures shall be documented by
    the Project Chief and reviewed by the District Ground-Water
    Specialist to determine if a formal revision of the
    technical-procedure document is warranted.

16. New or revised technical-procedure documents shall be reviewed by an
    independent reviewer and approved by the District Ground-Water
    Specialist.

```{=html}
<!-- -->
```
a.  Reviews shall address the following:

```{=html}
<!-- -->
```
1.  Applicability and appropriateness of the selected methods for the
    intended purpose.

2.  Correctness of facts, figures, tables, and equations.

3.  Completeness and clarity of step-by-step instructions and technical
    content.

4.  Evaluation of the stated accuracy of the procedure.

```{=html}
<!-- -->
```
n.  Approval of technical-procedure documents used within the District
    will be the responsibility of the District Ground-Water Specialist.
    Upon approval, the technical-procedure document shall be placed in
    the District file and a copy of it forwarded to the Regional
    Ground-Water Specialist.

## Documentation of Non-Routine Activities

1.  When data-collection methods are new, non-routine, or research
    oriented and involve a high degree of professional judgment or
    trial-and-error, an active record of the conduct, progress, and
    results of the data collection shall be maintained in a procedures
    notebook. These records shall be prepared and maintained in
    accordance with the following:

```{=html}
<!-- -->
```
a.  Prior to use of a procedures notebook, the project chief shall
    consult with the District ground-water specialist concerning the
    appropriateness of a non-routine method for planned data collection.

```{=html}
<!-- -->
```
o.  Each procedures notebook entry shall include the names of the
    individuals performing the work, the date on which the work was
    performed, and the name of the individual making the entries.

p.  At the conclusion of the method development, procedures notebooks
    shall be placed in the project file.

```{=html}
<!-- -->
```
17. The results of the technique developed in the procedures notebook
    shall be reviewed by the District Ground-Water Specialist to ensure
    that work is proceeding in a technically appropriate and relevant
    manner.

18. If the technique that has been documented in the procedures notebook
    becomes a routine procedure for the District, then a
    technical-procedure document shall be developed.

## Instrumentation

All instruments, devices, and equipment (including steel tapes) used to
collect ground-water data are categorized as instruments. Because of the
complexity of some instruments, their effect on the quality of the data
may be unknown or unquantifiable. To ensure the consistency,
comparability, and repeatability of collected data, instruments must be
identified, calibrated, maintained, and operated in an appropriate
manner.

Calibration is the comparison of the output from an instrument to a
standard or to the output from another instrument or procedure of known
accuracy in order to detect, correlate, report, or eliminate by
adjustment variations in the accuracy of the instrument being evaluated.

The following quality-assurance activities shall be performed by the
District.

1.  Instruments used to collect data shall be identified with a unique
    identifier on the field form.

```{=html}
<!-- -->
```
19. Calibration procedures and schedules shall be established for each
    instrument based on the stability characteristics of the instrument,
    required accuracy, intended use, manufacturer\'s recommendation, and
    other conditions that may affect the quality of the data. The
    calibration procedure and schedule shall be documented in the
    technical-procedure document that requires use of the instrument, or
    in a stand-alone technical-procedure document if not satisfactorily
    documented in the user\'s manual for the instrument. Instruments
    shall be identified by type, manufacturer, and model. Calibration
    shall be performed whenever the accuracy of the instrument is
    suspect, regardless of the calibration schedule. Instruments
    consistently found to be out-of-calibration shall be repaired or
    replaced.

20. A log shall be maintained for each instrument requiring calibration.
    The log shall contain all information pertinent to calibration,
    whether performed by District staff or by an outside organization or
    vendor. Calibration documentation recorded in the log shall include:

```{=html}
<!-- -->
```
a.  Name of organization and individual performing the calibration.

```{=html}
<!-- -->
```
q.  Identification of the instrument by type, manufacturer, model,
    serial number, or other unique and permanent identifier.

r.  Identification of calibration standard, including the range and
    accuracy.

s.  Identification of the document that describes the calibration
    process.

t.  Date of current calibration and date or milestone for next scheduled
    calibration.

u.  Records of instrument readings before and after any calibration.

```{=html}
<!-- -->
```
21. Data collected with instruments found to be out-of-calibration shall
    be evaluated to determine the effect on the intended use of the
    data. Affected data shall be discarded or their limitations
    documented in the database and in any application of the data.

22. All instruments used to collect data shall be operated in accordance
    with the manufacturer\'s manual, unless otherwise documented.
    Modifications to the manufacturer\'s operating procedure shall be
    appended to the manufacturer\'s manual, which shall be kept with the
    equipment at all times. Duplicate manuals for all instruments shall
    also be kept on file. Operating procedures may be included in
    technical-procedure documents.

23. Instrument maintenance shall be performed in accordance with the
    manufacturer\'s recommendations. A log shall be used
    t[]{#__RefHeading___Toc522520670 .anchor}o record maintenance
    performed.

## Identification and Control of Samples

During the course of many ground-water investigations, samples of
various types of earth materials are collected to supplement field
observations or to allow laboratory tests, analyses, and measurements
that are not possible to perform in the field. Types of samples include
rock core, drill cuttings, soil, and outcrop. Because these samples can
be critical scientific evidence to support interpretations, samples must
be easily identifiable, handled and stored in a controlled manner, and
be traceable. The relation between samples and the data set they
represent must be maintained.

The following quality-assurance activities shall be performed by the
District.

1.  Develop a unique identifier which shall be placed on each individual
    sample or sample container using materials and methods that are
    clearly visible, legible, and durable.

```{=html}
<!-- -->
```
a.  The unique identifier, as well as other information that is critical
    for the intended use of a sample (such as orientation), shall be
    recorded on field forms and laboratory logbooks.

```{=html}
<!-- -->
```
v.  If a sample is subdivided for analysis, the sample identifier shall
    be transferred to each part of the sample, or its container.

```{=html}
<!-- -->
```
24. Establish a sample-control system to record information pertinent to
    each set of samples. This may be achieved by maintaining a logbook,
    a set of forms, or other appropriate documentation. The
    sample-control system shall contain the following information for
    each sample:

```{=html}
<!-- -->
```
a.  Unique identifier

```{=html}
<!-- -->
```
w.  Type of sample and general description

x.  Source location specifications (x, y, z)

y.  Date and time of collection

z.  Reference to technical-procedure document or procedures notebook
    describing sample collection, handling, preservation,
    transportation, and storage.

a.  Storage location

```{=html}
<!-- -->
```
25. Sample-control system documentation shall be placed in the project
    file.

# DATA PROCESSING, REVIEW, AND STORAGE

A data-management plan describes the procedures used for data
processing, review, and storage, and may also include archiving. After
ground-water data are collected, they often are processed using one or
more procedures, such as the application of time or datum corrections,
and then are stored in computerized or physical files. Descriptive
information on data-collection sites, such as well construction data and
location, also should be stored. In general, data are most accessible
and useful to the project chief and other District employees, as well as
to those outside the District office, if they are stored in a
computerized database. Storage in a single database also enables
interpretations to be more easily verified and repeated. All water data
collected as part of the routine data collection of the WRD, which are
all ground-water data collected by basic data programs and District
projects (OGW Technical Memorandum 93.03) (see appendix), must be stored
in computer files of the USGS National Water Information System (NWIS).
In addition, \"all data collected by others \-- such as cooperators,
universities, or consultants

\--that are used to support published USGS documents and not published
or archived elsewhere, shall be placed in NWIS\" (Hubbard, 1992).
Exceptions to these requirements are spatial data coverages and other
data for which appropriate database capabilities do not exist in NWIS.

A quality database is maintained by:

-   checking database files against original data files to ensure
    accuracy,

-   performing internal crosschecks of the data in the database to
    identify anomalous data, and maintaining the original data in paper
    or electronic archives to ensure integrity.

Original data are those data \-- from automated data-collection sites,
laboratories, outside sources, and non-automated field observations \--
unmodified as collected or received, once put into conventional units
(engineering units, generally with a decimal) (Hubbard, 1992).

The following quality-assurance activities shall be performed by the
District.

1.  All original data in paper form shall be placed in project or
    data-collection program files. Original data in electronic form
    shall be stored in NWIS. All original data shall be preserved
    unmodified as collected or received.

```{=html}
<!-- -->
```
26. All data collected as part of the routine data collection of the
    WRD, and all existing data collected by WRD and others that are used
    to support published USGS documents and not published or archived
    elsewhere, shall be placed in NWIS unless excluded under current WRD
    policy (Hubbard, 1992). Excluded data are spatial data coverages and
    other data that cannot be stored in NWIS

27. The District shall prepare and implement a District Data-Management
    Plan, which documents established policies, conventions, and
    responsibilities for data processing, data review, handling project
    and data-collection program files, and computerized databases. OFR
    94-61 (Martin and Cohen, 1994) offers an example of such a document.
    The District Data-Management Plans shall:

-   Describe the processing of each type of data through such steps as
    entry on a field form, data review, data entry, and filing of the
    original data. Data processing that is described in a
    technical-procedure document may be referenced.

-   Include descriptions of filing systems for site data and maps, local
    well-numbering systems, requirements for field-checking sites, and
    District-specific database management policies and practices.

-   Indicate how the District ensures that data are reviewed promptly
    after data collection. Data reviews shall verify that as data are
    collected, they are entered in the database and that the data in the
    database have been checked against the original data, including the
    processing of electronic data to original data, application of
    shifts and datums, correction of transducer drift, and so forth.
    Data reviews shall be documented during project reviews.

-   Document any databases external to NWIS. Documentation should
    include a description of data elements (data dictionary),
    information about the database table or file structure, copies of
    customized program code, and information about any algorithms used
    by the database to calculate results for storage or output. If the
    database is described in a separate report, the documentation may be
    referenced by the District Data-Management Plan and a copy of the
    documentation kept with the plan. Include a plan for performing
    periodic internal checks of ground-water data in NWIS and any other
    ground-water databases to identify and correct anomalous data.

28. Data shall be reviewed promptly after any data-processing procedure
    is completed to ensure that the procedure was correctly applied and
    that the results are consistent both internally to the data set and
    with other data for the same site. This review shall be performed
    prior to publication or other dissemination to the general public
    and prior to the technical review of publications that contain the
    data or that use the data in interpretations. The District shall
    establish a review schedule for data in addition to or in
    conjunction with other reviews. Reviews should be scheduled and
    implemented for data-collection programs as well as interpretive
    projects.

# DATA ANALYSIS

Analysis of ground-water data includes activities ranging from simple
statistical applications to the development and application of complex,
numerical models. Quality assurance of data analysis begins with a well
thought out and detailed work plan that describes methods and approaches
of data analyses. Analysis procedures shall be reviewed as part of the
proposal and work plan development, and during project reviews as
appropriate. The methods by which data, or the results of data analyses,
are \"interpreted,\" such as the insight involved in the interpolation
of water-level data to produce a potentiometric-surface map or the
interpretation of the results of model simulations, cannot be completely
documented. However such interpretations must be appropriately
qualified, including descriptions of model limitations and data
uncertainty.

Reviews of data-analysis procedures ensure that selected analysis
techniques are appropriate for meeting project objectives. Data-analysis
techniques are identified, at least preliminarily, during development of
the project work plan. During project reviews, at about 10 percent of
project completion, after a better understanding of the project is
developed, data-analysis procedures should be reviewed for suitability
in meeting the project\'s objectives. At about 40 percent of project
completion, data-analysis techniques should be reviewed to ensure that
preliminary analyses produce valid results. If modifications to
procedures are warranted, these modifications are documented in review
comments. At a point when data analysis is complete, at approximately 70
percent of project completion, all data that were collected for a
project, and the results of intermediate and final data analyses, are
assembled and reviewed. Original data, data analyses, and data that were
collected but not used in analysis, along with reasons for the
exclusion, are documented as a part of the project review and placed in
the project file.

The following quality-assurance activities shall be performed by the
District.

1.  Data-analysis procedures shall be referenced and new data-analysis
    procedures, including those implemented by software, shall be
    documented in a report released prior to, or as part of, the report
    giving the results of that technique. Documentation might include:

-   A description of the theoretical basis and computational procedure
    in sufficient detail to perform the analysis, all data requirements
    or options for the data-analysis procedure, and comparisons of the
    technique with known or accepted solutions.

Office of Ground Water Technical Memorandums 79.04, 91.04, and 96.04
(see appendix) have outlined documentation requirements for
data-analysis procedures implemented by software.

1.  The results of data analysis shall not be presented at a finer
    spatial or temporal resolution than supported by the input data. The
    results shall not be displayed with an accuracy that exceeds the
    capability of the analysis or the accuracy of the data-collection
    methods. Interpretations of data analysis shall be appropriately
    qualified, including descriptions of limitations and data
    uncertainty.

```{=html}
<!-- -->
```
29. Districts shall establish a written policy for reviewing
    data-analysis procedures and documenting the review. The results of
    any data analysis shall be reviewed, prior to release, to ensure
    that the analysis is valid. The reviewer shall be provided with any
    necessary background information to adequately perform the review.
    The District shall establish a procedure for resolving the
    reviewers\' concerns that ensures that the review comments are
    carefully considered and revisions made, if appropriate, and that
    direct interaction occurs between the project chief and the
    reviewer. The District also shall establish and implement an
    archiving process for the review documents.

# PUBLICATIONS

Disseminating information to Congress and the general public has been
required of the USGS, since its creation in the Organic Act of 1875. The
report review process ensures the quality of the written report, which
is the culmination and final result of the training, planning, data
collection, and data analysis. To satisfy national responsibilities and
to produce accurate and timely reports, the District shall perform the
following quality-assurance activities.

1.  All ground-water data collected in USGS data-collection programs and
    interpretive and research projects shall be published in a timely
    manner. Data in NWIS that have been reviewed and approved are
    available to the general public, and can be considered published.

```{=html}
<!-- -->
```
30. The District Chief in consultation with the Office of Ground Water
    shall approve, in writing, any exceptions to the requirement to
    publish all data, including data collected under an agreement of
    confidentiality.

31. Data furnished by sources other than WRD may be used for analysis
    and published if the source of the information approves and if
    (1) the data have been appropriately quality assured, or (2) the
    data have not been thoroughly quality-assured but are described in
    terms of appropriate qualifications and limitations. In either case,
    the source of the data must be acknowledged. Care should be taken to
    assure that data are published with the correct number of
    significant figures.

32. Reports shall be reviewed and approved according to current District
    and WRD policy.

# ARCHIVING

Archiving is the final step in the processes of data collection,
analysis, and interpretation. Although the report represents the summary
of the current work, the data and its interpretation should be available
for further analysis.

-   **Archiving** is the systematic process of storing data and
    information to protect it from change or loss, by providing the
    necessary security.

-   **Electronic archiving** is the systematic process of removing data
    from active, on-line computer storage and preserving it with the
    capability to recover the data.

To quality assure the archiving process, the following steps shall be
performed by the District:

1.  All data shall be archived as specified by current WRD policy.

```{=html}
<!-- -->
```
33. All model related computer files and appropriate simulation results
    shall be archived as outlined in OGW Technical Memorandum 93.01 (see
    appendix).

34. All aquifer-test data and results shall be archived as outlined in
    OGW Technical Memorandum 94.02 (see appendix).

35. An Archiving Plan for the District, which documents the disposition
    of all project information upon completion of District projects,
    shall be established. The Archiving Plan shall document the
    archiving process and the responsibilities of personnel assigned to
    archiving tasks. The disposition of technical-procedure documents
    and procedures notebooks developed for an individual project should
    be described in the Archiving Plan.

Internal California District policy (Instruction 1641.1A, July 9, 1991,
Ron Fogelman, California District, written communication) and Indiana
District data management and archival policies (Martin and Cohen, 1994)
are examples of archiving plans. Parts of the project files may be
incorporated into the District-wide file system, as appropriate.

# AUDIT

Audits are designed to ensure that all tasks described in the GWQAP are
being performed. Audits will be performed during the Technical District
Reviews. A more detail section is found in the Quality Assurance Plan
for Ground-Water Activities.

# SUMMARY

This report provides a plan to direct the quality assurance of
ground-water activities in District offices of the USGS, and presents
policies pertaining to training; planning; data collection, processing,
review, analysis, and storage; publications; archiving; and audits as
they relate to these activities. The implementation of a GWQAP will
enhance the consistency, accountability, comparability, traceability,
and repeatability of ground-water activities of the USGS.

# REFERENCES CITED

Green, J.H., 1991, WRD Project and Report Management Guide: U.S.
Geological Survey Open-File Report 91-224, 152 p.

Hubbard, E.F., compiler, 1992, Policy recommendations for management and
retention of hydrologic data of the U.S. Geological Survey: U.S.
Geological Survey Open-File Report 92-56, 32 p.

Martin, J.D., and Cohen, D.A., 1994, Policy and procedures for the
management and archival storage of data collected for hydrologic
investigations of the U.S. Geological Survey, Indiana District: U.S.
Geological Survey Open-File Report 94-61, 36 p.

Schroder, L.J., and Shampine, W.J., 1992, Guidelines for preparing a
quality assurance plan for district offices of the U.S. Geological
Survey: U.S. Geological Survey Open-File Report 92-136, 14 p.

Shampine, W.J., Pope, L.M., and Koterba, M.T., 1992, Integrating quality
assurance in project work plans of the U.S. Geological Survey: U.S.
Geological Survey Open-File Report 92-162, 12 p.

APPENDIX

Copies of the following policy memorandums are appended.

Office of Ground Water Technical Memorandums 79.04, 91.04, 93.01, 93.03,
94.02, 96.04.

QUALITY CONTROL \-- Documentation of computer programs used for aquifer
modeling

UNITED STATES DEPARTMENT OF THE INTERIOR

GEOLOGICAL SURVEY

RESTON VIRGINIA 22092

Code 4351 5016

February 26, 1979

GROUND WATER BRANCH TECHNICAL MEMORANDUM NO. 79.04

SUBJECT: QUALITY CONTROL \-- Documentation of computer programs

used for aquifer modeling

Significant modifications to existing models or newly devised

computer programs used to simulate aquifer processes should be

documented before the programs or interpretations based on them

are released. This memorandum amplifies earlier instructions

regarding the need to document modifications of existing computer

programs, and provides guidelines for documentation of new

computer programs.

Ground Water Branch Technical Memorandum No. 75.11 (a copy is

attached) provided guidelines for reporting and documenting

aquifer modeling analyses. Item #7 of that memo indicated, among

other things, that if the computer program used is \"substantially

different\" from a published version, the \"significant

modifications\" of the original program should be described in an

open file or published report. A \"significant modification\" to a

computer program means any change in the computational scheme that

can give computed results that may differ from those that would be

obtained using the published version of the program. Changes in

format of data input and/or output are not considered significant.

However, changes in the approximating equations and/or the

algorithm used to solve those equations are considered

significant. If the description of those modifications is

extensive or is believed to disrupt the continuity of the report,

those modifications can be described in an appendix to the report.

A newly developed program, representing a computational approach

that is different from published approaches, should be documented

in a report released prior to, or as a part of, the report giving

results of a hydrologic analysis using that program. The

documentation should precede, or be coincident with, release of

copies of the computer program for use outside of the Geological

Survey. The \"documentation\" of newly developed programs and major

program modifications should include at a minimum a description of

the computational procedure in sufficient detail to provide enough

information to independently develop an equivalent computer

program. However, if a newly developed program is intended for

widespread use in the U.S. Geological Survey, it would be

preferable for the documentation to include a generalized flow

chart, program listing, definitions of program variable,

instructions for the preparation of the data input, and a sample

of the output. These requirements are intended to assure that

adequate information on computer programs used to make hydrologic

analyses is released in a timely fashion.

\(s\) Gerald Meyer

Chief, Ground Water Branch

Attachment

WRD Distribution: A, B, S, FO, PO

Policy for the documentation of non-U.S. Geological Survey computer
programs used for analysis in ground-water projects

In Reply Refer To: August 14, 1991

Mail Stop 411

OFFICE OF GROUND WATER TECHNICAL MEMORANDUM NO. 91.04

SUBJECT: Policy for the documentation of non-U.S. Geological

Survey computer programs used for analysis in ground-

water projects

The purpose of this memorandum is to define policy for the

documentation of computer programs that will be used or cited in

ground-water project reports that receive Director\'s approval.

The long-standing policy of the U.S. Geological Survey (USGS) is

that a program written by USGS employees to perform other than

routine tasks must be documented (either in a separately

approved report or in a report that makes use of the program)

before it can be cited or used in a USGS report (see Office of

Ground Water Technical Memorandum No. 79.04). However, no clear

policy has been defined for required documentation of programs

written by outside sources. The proliferation of programs from

non-USGS sources makes it important that guidelines be

established for use of these programs in USGS investigations.

The two classifications for computer programs written outside of

USGS are: (1) public domain and (2) proprietary. Public-domain

programs are not copyrighted. Common sources of public-domain

programs are universities and other government agencies.

Proprietary programs are developed by businesses or

organizations in order to sell them to customers and are

copyrighted.

Public-domain programs are held to the same requirements as in-

house programs. The policy for use of a public-domain computer

programs is:

1\. The program must be documented in a published report.

2\. The documentation must describe both the theoretical basis

for the calculations performed by the program and the

implementation of the theory. This documentation should show

that the program functions as described, and if not shown,

independent checks must be undertaken by the user. The results

of any testing should be placed in the project files and made

available to reviewers of project reports.

3\. The source code for the program must be included in the

documentation or be available from a formal distribution center.

Proprietary computer programs cause policy difficulties due to

the secrecy that vendors require in order to protect their

products. Complete documentation as described above is

generally not provided for proprietary programs; in particular,

the source code is usually not available.

The broad purpose of the requirements for documentation of in-

house programs is to ensure a high probability that the programs

function correctly, ensure that the theoretical basis is

explained and defensible, allow others to learn from our work,

and allow others to reproduce and evaluate our work. In order

to attain the same purpose without requiring disclosure of

source code, the following policy has been adopted for the use

of proprietary computer programs in USGS reports.

1\. The proprietary program must be available for purchase by

anyone.

2\. The vendor must provide documentation with the program that

describes how to use the program and the theoretical basis for

calculations. If the standard documentation provided by the

vendor does not contain an adequate description of the

theoretical basis, then the user must contact the vendor to

obtain the theoretical basis and must reference or describe this

theory in the reports that use the program.

3\. The user of a proprietary program must make tests by

comparing results from the program to known solutions to show

that the program functions as claimed by the vendor and as used

in their project work. Users should retest new versions of a

program to make sure errors have not been introduced. The

results of the testing should be placed in the project files and

made available to reviewers of project reports.

This policy is intended to insure the reliability and

reproducibility of our work.

Any question regarding this policy and the applicability to

specific software should be clarified in the early stages of a

project by contacting the Office of Ground Water.

Thomas E. Reilly

Acting Chief, Office

Ground Water

Distribution: A, B, S, FO, PO

cc: OGW File/Chron\--MS 411

WGS:WRD:AWHarbaugh:ves:7/22/91

Dir: vestockd/harbaugh/10.doc

File Code: Tech MM. 91

***PROGRAMS AND PLANS\--Establishment of a National Policy to Archive
Ground-Water Flow and Transport Models***

In Reply Refert To: October 28, 1992

Mail Stop 411

OFFICE OF GROUND WATER TECHNICAL MEMORANDUM NO. 93.01

Subject: PROGRAMS AND PLANS\--Establishment of a National Policy

to Archive Ground-Water Flow and Transport Models

POLICY

Ground-water flow and transport models are an integral part of our
interpretive ground-water investigations, and the results of these
models form the basis for many of the conclusions published in U.S.
Geological Survey reports. The numerical data and related information
that comprise these models need to remain available to: (1) support and
validate the results in published reports, (2) assure that working
versions of all models are available for future scientific use, and (3)
assure that the data are available to the public when requested. The
appropriate model data and related information are to be stored in a
permanent, well- documented manner to ensure their continued
availability. Effective as of the date of this memorandum, a national
ground- water model archive is established. All ground-water flow and
transport models that are a significant part of ground-water
investigations with completion dates of October 1993 or later are to be
included in the archive. Where feasible, districts also should archive
models from completed investigations and from current projects to be
completed prior to October 1993. The Regional Ground Water Specialists
are to act on behalf of the Office of Ground Water to assure that all
required information is present in the archive. Status of the archives
also will be examined as a routine part of district ground-water
discipline reviews. Design and implementation requirements for the
archive are presented in Attachments 1 and 2 to this memorandum.

The archive is for internal Water Resources Division (WRD) access and
use and is to serve as the source of ground-water model data supplied to
the public upon request. The public release of specific information
contained in the archive is subject to compliance with any existing WRD
policies that may apply to the public release of such information.

The ground-water model archive does not relieve individual investigators
of theneed to fully describe and document model analyses in their
reports.

Joseph S. Rosenshein

Acting Chief, Office

of Ground Water

2 Attachments

WRD Distribution: A, B, S, FO, PO

ATTACHMENT 1

DESIGN AND IMPLEMENTATION OF DISTRICT GROUND WATER MODEL ARCHIVES

STRUCTURE AND CONTENTS:

The archive will consist of a main directory called GWMARCIV. A report
subdirectory, located directly below GWMARCIV, will be established for
each published report containing a ground-water flow or transport model
analysis. Each report subdirectory should be given a name that clearly
reflects the U.S. Geological Survey report number. The archive must
include the model source codes, input files, macros and operating files
such as JCL, CPL, and UNIX shell codes, and model output files for each
simulation described in the report.

These simulations will include (when applicable) the final calibrated
steady-state and transient results and any predictive results described
in the publication. Model results of minor importance, such as interim
calibration runs, should not be archived. Model output will be archived
for future verification that the input data files properly reproduce the
published results when the input files are rerun. The storage of
additional ancillary data is optional, but is strongly encouraged.
Examples of ancillary data that might be stored are pertinent pre- and
post-processor codes, related data, or other files directly related to
the model simulations.

A subdirectory named CONTENTS, located immediately below each report
directory, will include one or more files that contain:

\(1\) the full reference for the subject report; (2) descriptions of the

subdirectory structure and of the files contained in each subdirectory,
(3) descriptions of data file formats, when appropriate; (4) the
sequence of model runs; and (5) instructions for running simulations.
Attachment 2 shows one example of what an archive directory structure
might look like for a typical project.

When the input data of one model depends directly on output from another
model, both models are to be included in the archive. If the models are
documented in separate reports, a cross-reference between the reports
must be included in the CONTENTS directory of the archive entry for each
report.

Model input files must be stored in ASCII format to assure that they can
be processed in the future on virtually any computer without the need
for specialized or proprietary software. In cases where model input
files are derived from either proprietary or machine-dependent software,
ASCII versions of the model input files must be included in the archive.

IMPLEMENTATION:

Each district will set up an archive on a locally based computer. The
district staff is responsible for designing a subdirectory structure
that permits efficient and logical storage of the required information
for each specific model. Files will be accumulated and stored in the
on-line archive until the final interpretive report is approved, after
which time the files are to be moved to permanent storage.

For all studies with completion dates of October 1993 or later, the
appropriate model files must reside on-line in the district archive when
the report is submitted to the Region for approval. Verification of
compliance with this policy is the responsibility of the Regional Ground
Water Specialists. Reports returned to the district for revision that
require new or additional model simulations will require an archive
update.

Upon final approval of the interpretive report, the archive is to be
copied to permanent storage on an optical disk using WORM (write once,
read many) technology. A copy of the WORM disk will remain in the
originating district to service requests for data, and a duplicate copy
will be furnished to the Region for off-site backup. A WORM disk may
contain model data for one or more published reports provided the disk
is indexed appropriately. The archive may be transferred to tape as a
short-term storage option if the district does not have immediate access
to WORM disk production equipment. The period of interim storage on tape
should not exceed 1 year. The archive process is considered complete
only when a WORM disk has been produced. On-line storage of the archived
data may be discontinued at the discretion of the district following
transfer of the archive to WORM disk or to interim tape storage.

***Interim Policy Memorandum about Storing Data in the National Water
Information System***

In Reply Refer To: January 25, 1993

Mail Stop 411

OFFICE OF GROUND WATER TECHNICAL MEMORANDUM NO. 93.03

Subject: Interim Policy Memorandum about Storing Data in

the National Water Information System

The purpose of this memorandum is to restate and clarify existing

policy regarding the use of the National Water Information System

(NWIS) to store ground-water data collected by the U.S. Geological

Survey, Water Resources Division (WRD).

Problems and Concerns

Discipline reviews are finding that not all ground-water data

collected by WRD are being stored in NWIS. It appears that some

elements of policy detailed in WRD Memorandum Nos. 76.44, 77.136,

83.89, and 86.28 have been misunderstood and have not been

vigorously enforced at the Regional and Headquarters levels.

Clarification and Restatement of Policy

WRD Memorandum 92.59 has recently been released and states that

the recommendations made by the Data Policy Committee (Open-File

Report 92-56) have been accepted as official policy. That policy

includes the following:

\"The current policy in WRD is that all water data

collected as part of the routine data collection of the

WRD (both basic and project data) must be stored in the

computer files of the National Water Information System.

One purpose of this policy is to enable all WRD work to

be verifiable and repeatable to the greatest extent

possible at any time in the future.\"

The Office of Ground Water (OGW) interprets Rroutine data

collection of the WRDS to include all ground-water data collected

by WRD basic data programs and District projects. Any request for

exemption from this policy must be approved by OGW. The only

exceptions to this requirement are proprietary data, and data that

cannot be stored in NWIS because they do not functionally fit.

When the new version II of NWIS software is completed, it is

expected that many of the ground-water data that WRD collects will

functionally fit in NWIS, including many types of geophysical,

hydrogeological, and hydraulic test data.

Implementation of Policy

The OGW and the Regional Ground-Water Specialists will review

compliance with this policy during District technical and selected

project reviews and by actual interrogation of NWIS. Several

recent District reviews by OGW have included an additional person

on the review team for the purpose of examining data-related

issues. The OGW has added a staff person to specifically address

the issues of data and data bases. The OGW also has created the

Ground-Water Data Committee to develop recommendations about

issues of policy and management of ground-water data. Future

memorandums will address other aspects of ground-water data

policy.

William M. Alley

Acting Chief, Office

of Ground Water

WRD Distribution: A, B, S, FO, PO

Guidance for the preparation, approval, and archiving of aquifer-test
results

In Reply Refer To: June 2, 1994

Mail Stop 411

OFFICE OF GROUND WATER TECHNICAL MEMORANDUM 94.02

Subject: Guidance for the preparation, approval, and archiving

of aquifer-test results

Analyses of aquifer tests to define the hydraulic characteris-

tics of a specific aquifer or aquifer system are an integral

part of our interpretive ground-water investigations. The

results of these analyses are critical components of flow-system

or solute-transport analyses and important to conclusions

published in U.S. Geological Survey (USGS) reports. Conse-

quently, reported aquifer characteristics such as hydraulic

conductivity, transmissivity, storativity and other hydraulic

characteristics derived from aquifer-test analyses must be

clearly documented and technically defensible. The purpose of

this memorandum is to describe guidelines and procedures

necessary to obtain approval for the results of aquifer tests

analyzed by employees of the Water Resources Division (WRD) and

to provide guidelines for archival of the test results.

BACKGROUND

According to WRD Publications Guide (Article 11.01.2) \"\....calcu-

lated hydraulic characteristics such as transmissivity, hydrau-

lic conductivity, and storage coefficient, are interpretive and

must be approved by the Director, unless cited from a Director-

approved report.\" In a memorandum dated March 11, 1992, the

Assistant Chief Hydrologist, Scientific Information Management,

delegated authority to approve aquifer-test results to the

Regional Hydrologists. Approval is required for all calcula-

tions of aquifer-hydraulic characteristics to be released to the

general public, to cooperators, or published in or otherwise

used to support the results of investigations reported in

USGS-approved reports.

Estimates of aquifer-hydraulic characteristics commonly are

obtained from \"textbook\" or published values for various

lithologies. These are not considered calculations of aquifer

characteristics and do not require approval under the terms of

this memorandum. In addition, estimates of transmissivity

determined on the basis of specific-capacity measurements do not

require approval.

DOCUMENTATION, APPROVAL, AND ARCHIVAL OF AQUIFER-TEST RESULTS

While the USGS encourages the publication of aquifer-test

results, it is not feasible to publish the data and graphical results

for every test conducted. In all cases, either as part

of a formal report or as a separate packet, aquifer-test results

should be submitted to the Regional Ground-Water Specialist for

review and subsequent approval by the Regional Hydrologist. The

Regional Ground-Water Specialist reviews the report manuscript

or aquifer-test packet to assess (1) that the report or packet

contains the necessary data and related information to properly

analyze the subject test(s), and (2) that the analyses and

results are technically defensible.

Elements that typically should be submitted for review are

listed below. These elements assume an aquifer test comprising

a pumping well and one or more observation wells and should be

modified as appropriate for other types of tests such as a

single-well slug test. The eight elements are as follows.

1\. A brief description of the test (this can be neatly

hand written) which includes the purpose, date, test

procedures, and methods of analysis of the results.

Any unique or unusual features or problems related to

the test or to the collection and analysis of test

data should be described. A brief description of the

assumptions used in analyzing the test results also

should be included, as needed to clarify the test.

2\. A sketch of the test site showing the distances from

the pumped well to all observation wells and the

location of any boundaries, streams, springs, ditches,

pumping or flowing wells, or other features that

possibly could influence test results. Where the test

includes multiple wells, the sketch of the test site

should be drawn to scale.

3\. Description of test and observation well construction,

including screened and open interval(s), casing and

screen diameters, and location of filter pack and

grouted intervals.

4\. A description of the site hydrogeologic characteris-

tics, including sections that show the major water-

bearing and confining zones or units. The intervals

of the pumping and observation wells that are screened

or open should be depicted on the logs or sections.

5\. Time-discharge records of the pumped well (all

measurements, not just average discharge).

6\. Water-level records and hydrographs showing pre-test

trends and water levels during the pumping and

recovery phases.

7\. Description of methods and computations showing

adjustments to drawdown for pre-test trends,

adjustments of recovery for projected drawdown, or

adjustments to account for extraneous effects not

related to pumping or recovery, such as barometric and

tidal effects or other interferences.

8\. All plots of observed or adjusted drawdown or recovery

data used to determine hydraulic characteristics,

showing match points, when used, and computations.

It is recognized that in some cases it is not possible to

provide a complete description of these eight elements.

Investigators are encouraged to discuss their plans with the

Regional Ground-Water Specialist to determine the requirements

for a particular test packet or report before they forward it

for review and approval.

A transmittal memorandum, indicating that the test results have

been reviewed by the District or Area ground-water specialist or

his or her designee, should be included with the test packet or

report. This review should include at least some checking of

the field data and a verification that the test results are

appropriate, given the site hydrogeology, well construction, and

test conditions and that the test results have been reviewed

independently before being submitted for regional review and

approval.

Following approval by the Regional Hydrologist, the packet or

report will be returned to the originating District or Office

where the hydraulic characteristics and related site and well

data should be entered into the Ground-Water Site Inventory

System or National Water Information System (NWIS) and the

packet and associated information appropriately archived in a

District \"aquifer-test file.\" These archived aquifer-test files

should include the draft-report routing sheet or packet-review

transmittal memorandum. Districts also are encouraged to

archive test analyses and results completed prior to this

memorandum. The aquifer-test files will be reviewed as a

routine part of District ground-water discipline reviews.

If computer software is used in the aquifer-test analysis,

the policy outlined in Office of Ground Water Technical

Memorandum 91.04, dated August 14, 1991, must be followed. This

policy requires that the theoretical basis of the software be

documented and that it be demonstrated that a test-data set can

be correctly analyzed using the software. Submittal of a

computer-software analysis does not eliminate the need for the

information described in item element 8, above.

This memorandum discusses information needs in the context of

single- or multiple-well aquifer tests. Aquifer characteristics

also may be calculated by other methods, such as, determination

of aquifer diffusivity from attenuation of a tidal pulse or

flood wave through an aquifer, or using hydrograph-recession

characteristics. The same review procedures should be followed

for these types of analyses, and information in the report

manuscript or packet must be adequate to enable reviewers to

visualize the physical system, evaluate all data, verify all

calculations, and assess that the methods and results are

defensible.

Sincerely,

/s/ William M. Alley

Chief, Office of

Ground Water

Attachment

Distribution: A, B, S, FO, PO

PUBLICATIONS\--Policy on documenting the use of ground-water simulation
in project reports

To: \"File WRD Archive Reston, VA \"

Subject: OGW TechMM 96.04

Mime-Version: 1.0

Date: Thu, 25 Apr 1996 08:50:30 -0400

From: \"Velvie E Stockdale, Office Automation Assistant, Reston, VA \"

In Reply Refer To: April 24, 1996

Mail Stop 411

OFFICE OF GROUND WATER TECHNICAL MEMORANDUM NO. 96.04

Subject: PUBLICATIONS\--Policy on documenting the use of

ground-water simulation in project reports

It has been more than two decades since Ground Water Branch

Technical Memorandum No. 75.11 was released on the subject of

documenting the use of ground-water simulation in project

reports. Because of the time lapse, changes in modeling

techniques, and the frequency of problems found when reports are

reviewed, a revisit to policy on this subject is appropriate.

There is no rigid checklist or recipe for reporting on the use

of simulation in a ground-water study. The appropriate level

of documentation will vary depending on the project objectives

and the complexity of the simulations. The general structure of

a well-constructed report describing simulation is much the same

as that for any investigative study. It should present (1) the

objectives of the study, (2) a description of the work that

was done, (3) logical arguments to convince the reader that

the methods and analyses used in the study are valid, and

\(4\) results and conclusions.

Specific topics that should be addressed in reports that

describe studies in which simulation is used include the

following.

1\. Describe the purpose of the study and the role that

simulation plays in addressing that purpose.

The objective of the simulation must be clearly stated. The

model should be represented as a tool to help solve specific

problems or answer specific questions rather than as an end

product.

2\. Describe the hydrologic system under investigation.

The extent, nature of boundaries, transmitting properties,

storage properties, sources of water, discharge mechanisms and

other relevant components of the ground-water system should be

described as known or conceptualized. Usually this can be

accomplished in part by referencing previous works, but major

relevant system characteristics should be summarized in the

report that describes the simulation.

3\. Describe the mathematical methods used and their

appropriateness to the problem being solved.

In most cases, a reference to a readily available publication

will be sufficient to document mathematical details; however, it

will usually be desirable to briefly summarize the methods that

are used. For a well-documented computer program, this will

often require only a paragraph or two. If a documented computer

program is modified such that computed values are affected, the

modifications should be documented and evidence that the

modifications are correct should be supplied.

4\. Describe the hydrogeologic character of the boundary

conditions used in the simulation of the system.

In many cases, the model boundaries are placed where the aquifer

terminates against relatively impermeable rocks or is

intersected by a perennial stream whose head variation in time

and space is known. In other cases, the aquifer may be so

extensive relative to the area of interest that the modeled area

may need to extend beyond the project area to accurately

simulate the natural boundaries of the aquifer system. If the

modeled area is arbitrarily truncated at some distance from the

area of interest, it should be shown that the selection of the

arbitrary boundary condition does not materially affect the

ability of the model to simulate the system for the purposes of

the study. Internal boundaries such as streams, lakes, and

pinchouts of important hydrogeologic zones should be identified

and their representation in the model should be described in the

report. A clear, convincing argument of the appropriateness of

the boundary conditions used in the model to represent the

actual system should be made for the entire bounding surface of

the modeled volume or cross section, as well as for any internal

boundaries.

5\. If the method of simulation involves discretizing the system

(finite-difference and finite-element methods for example),

describe and justify the discretized network used.

The spacing and distribution of the blocks, elements, or

subregions should reflect, in part, the spatial variability of

the hydraulic parameters and the location of boundaries (for

example streams, lakes, bed pinchouts), human-made features (for

example wells and dams), and stresses. In most cases, a map

showing the discretized network superimposed on the study area

is required. Vertical discretization should be described and/or

shown on illustrations. The manner in which time is discretized

for transient models also should be described. If a steady-

state model is used to simulate an average or approximate steady-

state condition, discuss the errors that could be introduced in

the study results as a consequence of using a steady-state model.

6\. Describe the aquifer system properties that are modeled.

Explain whatever inferences are made from field data and

previous studies as to the spatial variation of hydraulic

properties of aquifers and confining beds and how discretized

values are computed throughout the simulated area. During model

calibration (see item 9), modeled values are often changed; the

final aquifer system properties that are modeled should be

described in the report. This can be through maps or

descriptions in the text. Lists of model arrays do not

generally provide much understanding of the model and

accordingly should not be included in the report unless it is

expected that readers will want to repeat the simulations. If

lists of arrays are included, they should usually be provided on

electronic media. Note that Office of Ground Water Technical

Memorandum No. 93.01 describes the separate requirement for

archiving the complete model data sets used in ground-water

projects.

7\. Describe all the stresses modeled such as pumpage,

evapotranspiration from ground water, recharge from

infiltration, river stage changes, leakage from other aquifers,

and source concentrations in transport models.

The relations between observed and modeled stresses should be

described. For example, it usually is desirable to provide a

representative sample of actual pumping histories and the

corresponding modeled pumping histories, although such

information would not necessarily be provided for every pumped

well. The manner in which stresses are averaged within the

discretized time and space scheme should also be described.

If a steady-state model is used to simulate an average or

approximate steady-state condition, describe how the average

stresses representing this system are calculated.

8\. For transient models, describe the initial conditions that

are used in the simulations.

Ideally, a transient simulation will start from a steady-state

condition, and the steady-state initial conditions will be

generated by a steady-state simulation using the same model. In

this case, the steady-state simulation must use the same

hydraulic and stress parameters that are used in the transient

simulation, except that the transient stresses are removed. In

situations where it is not possible to start a transient model

from a simulated steady-state condition, it is necessary to

describe how the initial conditions were derived. It is also

important to estimate the error in the derived values and the

possible impact on the model results.

9\. If a model is calibrated, present the calibration criteria,

procedure, and results.

Describe the source of the observed data to which model results

are compared. Explain the appropriateness of using these data

for model comparisons and the rationale for any adjustments made

to actual observations when making the comparisons. For

example, when steady-state models are used to simulate an

approximate steady-state condition, it is important to explain

to what extent the observations that have been made at specific

points in time correspond to the approximate steady-state

condition being simulated. Give a representative sample of the

actual comparisons used for calibration, and show the locations

of the observation points on maps. When the number of

observations is extensive, locations of representative points

can be shown. It is important to report and use as many types

of data as possible for calibration. For example, in a flow

model, both head and flow observations are desirable for use in

calibration.

10\. Discuss the limitations of the model\'s representation of the

actual system and the impact those limitations have on the

results and conclusions presented in the report.

Evaluating the sensitivity of the computed model responses to

changes in parameter values that reflect plausible parameter

uncertainty helps to assess the model reliability. If the model

is to be used to make specific projections, it is useful to

estimate the impacts of the uncertainty of parameter values on

the projections. In calibrated models, a concern is non-

uniqueness, which is the extent to which other combinations of

parameter values or configurations may result in an equally good

fit to the observed data. Discuss the extent to which

nonuniqueness may affect the use of the model in the study.

In summary, a report describing a study in which simulation is

used should address the above topics; however, there is

considerable flexibility in the form of such a report. The

report should describe the purpose of the simulation and

convince the reader that the use of simulation is credible. The

report should further describe the system being simulated, the

methods of simulation, and the data that are used.

William M. Alley

Chief, Office of Ground Water

Distribution: A, B, S, FO, PO

This memorandum supersedes Ground Water Branch Technical

Memorandum No. 75.11

APPENDIX B: Guidelines for Preparing the Project Planning Documents for
the Nebraska Water Science Center Workplan

The project-planning document is essentially an expansion of the project
proposal and a plan for how and when all the work will be done. In some
cases where a project proposal includes all the necessary elements, a
project-planning document may not be required. The Chief of the
Investigations Section will make that decision. In most cases the
project planning-document should be completed in the first 4 to 8 weeks
of the project (depending on project length). There is no set format,
but it must contain all the necessary elements outlined in the
Objectives.

## Objectives:

36. To describe the reason or necessity for the study, its purpose and
    scope, and its relevance to the USGS mission.

37. To describe the initial concept of the hydrologic system.

38. To list and describe all reports to be produced during the project.
    (Report Plan)

39. To summarize previous work done in the project area.

40. To describe the data collection needs and the technical procedures
    likely to be used in collecting these data.

41. To evaluate the existing data relevant to the study.

42. To determine the extent of effort required to correct and update the
    ground-water/water-quality database for the study area (GWSI &
    QWDATA).

43. To outline and describe proposed methods of analysis or
    interpretation.

44. To determine specific discipline knowledge that may be required,
    assess personnel availability, and to list potential training needs
    of all project personnel.

45. To create a timelines chart that details the approximate starting
    and ending dates for all primary work elements and as many secondary
    tasks as are practical.

46. To detail project costs, including those necessary to quality assure
    data collection and interpretation.

The Report Plan is part of the project planning document and should
include as much detail about the planned reports as possible ---
intended audience, publication type, when it is to be written and
published, and a detailed outline with list of figures and tables
planned. Some annotation after each heading and subheading will serve to
refresh your memory about what you intended for that section.

APPENDIX C:

NEBRASKA GROUND-WATER TECHNICAL PROCEDURES

APPENDIX C: NEBRASKA GROUND-WATER TECHNICAL PROCEDURES

###### CONTENTS 

[WATER-LEVEL MEASUREMENT USING GRADUATED STEEL TAPE
3](#water-level-measurement-using-graduated-steel-tape)

[GROUND-WATER SITE INVENTORY---WELL AND SPRING LOCATION
1](#ground-water-site-inventory-well-and-spring-location)

[USE OF THE PRECISION LIGHTWEIGHT GLOBAL POSITIONING SYSTEM RECEIVER
(PLGR) TO LOCATE A WELL
2](#use-of-the-precision-lightweight-global-positioning-system-receiver-plgr-to-locate-a-well)

[ENTRY OF SITE DATA INTO GWSI DATABASE
4](#entry-of-site-data-into-gwsi-database)

[ESTABLISHING A PERMANANT MEASURING POINT
7](#establishing-a-permanant-measuring-point)

[WATER-LEVEL MEASUREMENTS USING AN ELECTRICAL TAPE
9](#water-level-measurements-using-an-electrical-tape)

[OBTAINING PERMISSION TO INSTALL, MAINTAIN, AND USE A WELL ON PRIVATE
PROPERTY
13](#obtaining-permission-to-install-maintain-and-use-a-well-on-private-property)

[INSTALLING A PRESSURE TRANSDUCER AND ACTIVATING THE DATA RECORDING
DEVICE
16](#installing-a-pressure-transducer-and-activating-the-data-recording-device)

[RECOGNIZING AND REMOVING DEBRIS FROM A WELL
19](#recognizing-and-removing-debris-from-a-well)

[CONTINUOUS WATER-LEVEL MEASUREMENTS USING A FLOAT-ACTIVATED RECORDER
22](#continuous-water-level-measurements-using-a-float-activated-recorder)

[GUIDELINES FOR MONITORING DRILLING ACTIVITES AND HOW TO SAMPLE AND
IDENTIFY CORE
27](#guidelines-for-monitoring-drilling-activites-and-how-to-sample-and-identify-core)

[GUIDELINES FOR COLLECTION AND PACKAGING OF CORE SAMPLES FOR HYDRAULIC
ANALYSIS
31](#guidelines-for-collection-and-packaging-of-core-samples-for-hydraulic-analysis)

APPENDIX C: GROUND-WATER PROCEDURE DOCUMENT

# WATER-LEVEL MEASUREMENT USING GRADUATED STEEL TAPE

## PURPOSE 

To measure the depth to the water surface below a measuring point using
the graduated steel tape (wetted-tape) method.

## MATERIALS & INSTRUMENTS:

47. A steel tape graduated in feet, tenths and hundredths of feet. A
    break-away weight may be attached (when necessary) to the ring on
    the end of the tape with wire strong enough to hold the weight, but
    not as strong as the tape, so that if the weight becomes lodged in
    the well the tape can still be pulled free. The weight should be
    made of brass, stainless steel, or iron.

48. Blue carpenters chalk.

49. Clean rag.

50. Pencil and eraser.

51. Steel tape calibration and maintenance equipment log book (when
    higher accuracy required).

52. Water level measurements (Field) 9-1904-E (revised June 2003) (fig 1
    at the end of this section).

53. Two wrenches with adjustable jaws for removing well cap.

54. Common household chlorine bleach.

DATA ACCURACY & LIMITATIONS:

55. A graduated steel tape is commonly accurate to 0.01 foot.

56. The water level should be within 200 feet of the land surface.

57. The steel tape should be calibrated against another acceptable steel
    tape. An acceptable steel tape is one that is maintained, in the
    office, for use only for calibrating steel tapes.

58. If the well casing is angled, instead of vertical, the depth to
    water will have to be corrected.

59. When measuring deep water levels, tape expansion and stretch is an
    additional consideration (see Garber and Koopman, 1968).

ADVANTAGES:

60. The graduated steel tape method is considered to be the most
    accurate method for measuring the water level in nonflowing wells of
    moderate depth.

61. Easy to use.

DISADVANTAGES:

62. May be impossible to get reliable results if water is dripping into
    the well or condensing on the well casing.

63. Not recommended for measuring pumping levels in wells.

64. Unreliable when oil layer present in well.

ASSUMPTIONS:

65. An established measuring point (MP) exists. See ground-water
    procedure document (GWPD) for technical procedure document on
    establishing an MP.

66. The MP is clearly marked and described so that a person who has not
    measured the well will know where to measure from.

67. A water-level measurement taken during the last field visit is
    available to estimate the length of tape that should be lowered into
    the well.

68. The black sheen on the steel tape has been dulled so that the tape
    will retain the chalk.

69. The well is free of obstructions. Well obstructions, if present,
    could cause errors in the measurement if the obstructions affect the
    plumbness of the steel tape.

70. Field Form 9-1904-E is used to record water-level measurement data.

INSTRUCTIONS:

71. Chalk the lower few feet of the tape by pulling the tape across a
    piece of blue carpenter\'s chalk. The wetted chalk mark will
    identify that part of the tape that was submerged.

72. Lower the tape (and weight, if needed) into the well until the lower
    end of the tape is submerged below the water. The weight and tape
    should be lowered into the water slowly to prevent splashing.
    Continue to lower the end of the tape into the well until the next
    graduation (a whole foot mark) is opposite the MP; record this
    number in the \`HOLD\' (fig. 1) column of the water level
    measurements field form.

73. The tape is rapidly brought to the surface before the wetted chalk
    mark dries and becomes difficult to read. Record the number of the
    wetted chalk mark, referred to as the cut, in the \`CUT\' (fig. 1)
    column of the water level measurements field form.

74. Subtract the 'CUT' number from the 'HOLD' number, and record this
    number in the \`DEPTH BELOW MP\' (fig. 1) column of the water level
    measurements field form. This number is the "DEPTH BELOW MP."

75. Apply the MP correction to get the water level below the
    land-surface datum. If the MP is above land surface (fig. 1), the
    distance between the MP and land surface datum is subtracted from
    the 'DEPTH BELOW MP' to obtain the 'WATER LEVEL (BELOW LSD)' value.
    If the MP is below land surface precede the MP correction value with
    a minus (-) sign and subtract the distance between the MP and land
    surface datum from the depth to water from the MP to obtain the
    'WATER LEVEL (BELOW LSD)' value. Record this number in the \`WATER
    LEVEL (BELOW LSD)\' column of the water level measurements field
    form (fig. 1). If the water level is above LSD, record the value as
    a negative number.

76. Make a check measurement by repeating steps 1 through 5. The check
    measurement should be made using a different MP 'HOLD' value than
    that used for the original measurement. If the check measurement
    does not agree with the original measurement within 0.02 or 0.03 of
    a foot, continue to make check measurements until the reason for the
    lack of agreement is determined or until the results are shown to be
    reliable. If more than two readings are taken, record the average of
    all readings.

77. In areas of suspected contamination, disinfect the steel tape after
    completing the well measurement by pouring a small amount of common
    household chlorine bleach on a clean cloth and wiping down the part
    of the tape that was submerged below the water surface; this will
    avoid possible contamination of other wells.

78. Maintain the tape in good working condition by periodically
    physically checking the tape for breaks, kinks and possible stretch
    due to the suspended weight of the tape and the tape weight.

79. In some pumped wells, a layer of oil may float on the water surface.
    If the oil layer is a foot thick, read the tape at the top of the
    oil mark and use this data for the water-level measurement instead
    of the wetted chalk mark. The measurement will differ slightly from
    the water level that would be measured were the oil not present.
    However, if several feet of oil are present in the well, or if it is
    necessary to know the thickness of the oil layer, a commercially
    available water-detector paste can be used that will detect the
    presence of water in the oil. The paste is applied to the lower end
    of the tape and will show the top of the oil as a wet line, and the
    top of the water will show as a distinct color change. Since oil
    density is about three-quarters that of water, the water level can
    be estimated by adding the thickness of the oil layer times its
    density to the oil-water interface elevation.

## DATA RECORDING

In areas when high accuracy is required, such as waste-site evaluations,
a calibration log shall be maintained in which all calibration and
maintenance data associated with the steel tape being used are recorded.
All water-level data are recorded on the water level measurements field
form (Form 9-1904-A) to the nearest 0.01 foot.

## REFERENCES

1\. U.S. Geological Survey Level 1 training, ground-water field
techniques, 1994.

2\. United States, Office of Water Data Coordination, 1977 -, National
handbook of recommended methods for water-data acquisition: Office of
Water Data Coordination, Geological Survey, U.S. Department of the
Interior, Reston, Va., chap. 2, p. 1-149.

3\. GWPD, establishing a permanent measuring point
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

4\. Garber, M.S., and Koopman, F.C., 1968, Methods of measuring water
levels in deep wells: U.S. Geological Survey TWRI, book 8, chap. A1;
Washington, U.S. Government Printing Office, 23 p.

![](media/image4.png){width="9.002083333333333in"
height="5.572222222222222in"}

Figure 1.---Water-level measurement field form 9-1904-E (revised June
2003

# GROUND-WATER SITE INVENTORY ---WELL AND SPRING LOCATION

## PURPOSE

To specify procedures for well and spring site inventory (location) and
the minimum amount of information that should be collected during the
initial reconnaissance of an individual ground-water site.

MATERIALS & INSTRUMENTS:

80. A state highway map, county road map, and a USGS 7.5 minute
    topographic quadrangle map. When required, an aerial photograph, or
    a town plat/lot number map may also be used. If available, a Global
    Positioning System (GPS) instrument may be used to locate a well.

81. Water-level measurements (9-1904-E) and well schedule field form
    (9-1904-A) (figs. 1, and fig. 2 located at the end of this section).

82. Orienteering (transparent base) compass.

83. Steel tape graduated in feet, tenths, and hundredths of feet.

84. Electric tape graduated in feet, tenths, and hundredths of feet

85. Blue carpenters chalk and clean rag.

86. Pencil and eraser.

87. Two wrenches with adjustable jaws for gripping and removing well
    caps and other assorted tools.

88. Camera and film-35 mm. (optional)

## DATA ACCURACY & LIMITATIONS:

89. Latitude and longitude values determined with a USGS 7.5 minute
    latitude-longitude scale can be read to the nearest 0.5 second.
    Graphic digitizer\'s used to determine latitude and longitude are
    available with accuracy\'s as low as +/- 0.003 second. Latitude and
    longitude values determined using either of these methods in
    conjunction with a USGS 7.5 minute topographic quadrangle map should
    be rounded to the nearest second.

90. Well construction information obtained from the well driller or from
    geophysical logs is more reliable than information obtained verbally
    from the well owner.

91. Altitudes determined from topographic maps are accurate to within
    one half the map contour interval.

## ASSUMPTIONS:

92. A ground-water site is a single point, not a geographic area or
    property.

93. A USGS 7.5 minute topographic quadrangle map with a 1:24,000 scale
    will be used to locate the ground-water site.

94. The person locating the well or spring can accurately plot the
    location on the 7.5‑minute topographic quadrangle map.

95. Site information is recorded on form 9‑1904-A as it is collected and
    never documented from memory.

96. All field notes should be neat and readable, and leave no doubt
    about interpretation.

## INSTRUCTIONS:

97. By examining available data files and interviewing the well owner
    and/or driller compile the following ground-water site data in the
    field using form 9-1904-A (figs. 1).

```{=html}
<!-- -->
```
b.  Source of information\--Date of site visit and name of person
    conducting site visit.

c.  Geographic location\--name of 7.5-minute topographic map, sketch map
    of site location on the back of the field well schedule (Form
    9-1904-A).

d.  Political regimes\--state and county or town identification.

e.  Source identifiers\--Owner\'s name and address.

f.  Individual site characteristics\--Topographic setting, use of site,
    use of water.

g.  Well construction\--Name of driller, date drilled, type of well
    (drilled, bored, or dug), total depth, casing (type, depth, and
    diameter), finish (screen, open hole).

h.  Estimated yield (gpm) and notes pertaining to water quality, future
    access to the site, and any other pertinent well-site information
    should be recorded on the field well schedule.

```{=html}
<!-- -->
```
98. Locate the ground-water site in the field on a USGS 7.5 minute
    topographic quadrangle. If necessary, the site can also be plotted
    on an aerial photograph, or a town plat/lot number map. If
    available, use a GPS instrument to determine the latitude and
    longitude of the site.

99. Prepare a detailed sketch map of the site location on the last page
    of the ground-water site schedule (form 9-1904-A). Orient the
    ground-water site on the sketch map relative to north. The sketch
    map should contain enough detail so that the site can be found again
    by a person who has never visited the site. All distances should be
    made in feet from permanent landmarks, such as buildings, bridges,
    culverts, road centerline, and road intersection. In addition,
    detailed sketches of the well including the measuring point (MP),
    access ports for water level measurements, and sampling points
    should be drawn on the back of form 9-1904-A with the date recorded.
    This information is updated during each future site visit.

100. Record water level measurements and date measured on field Form
     9-1904-E. See GWPD 1 for making water-level measurements using a
     graduated steel tape, or GWPD 4 for making water-level measurements
     using an electric tape.

101. OPTIONAL\--Take at least two photographs of the well location from
     different views and indicate on each photograph the direction of
     view. File location photographs with the GWSI form 9-1904-A.

## DATA RECORDING

Data are recorded in the field on the field Well Schedule Form 9-1904-A.
Water levels are also recorded on the Water-Level Measurements
Form 9‑1904-E.

## REFERENCES

1\. U.S. Geological Survey, 1990, National water information system
user\'s manual, ground-water site inventory system: U.S. Geological
Survey Open-File Report 89-587, v. 2, chap. 4, (variously paged).

2\. United States, Office of Water Data Coordination, 1977-, National
Handbook of recommended methods for water-data acquisition: Office of
Water Data Coordination, U.S. Geological Survey, U.S. Department of the
Interior, chap. 2, 149 p.

3\. U.S. Geological Survey Level 1 training, Ground-water field
techniques, 1994.

4\. American Society for Testing and Materials, 1994, ASTM standards on
ground water and vadose zone investigations (2d ed.): Philadelphia, Pa.,
ASTM, p. 00-304.

5\. GWPD 1, Water-level measurement using graduated steel tape, 1997
(draft).

6\. GWPD 3, Establishing a permanent measuring point, 1997 (draft).

7\. GWPD 4, Water-level measurement using an electric tape, 1997
(draft).

8\. GWPD 5, Locating a well, 1997 (draft).

9\. Giovachino, Domenic, 1992, Graphic digitizer accuracy: ASPRS/ACSM/RT
92 technical papers, GIS and Cartography, v. 3, 4 p.

![](media/image5.png){width="5.513194444444444in"
height="7.111805555555556in"}

Figure 2. Ground-water site inventory (GWSI) system site schedule Form
9-1904-A (revised May 3002).

# USE OF THE PRECISION LIGHTWEIGHT GLOBAL POSITIONING SYSTEM RECEIVER (PLGR) TO LOCATE A WELL

## PURPOSE

To specify basic procedures for locating ground-water sites using a PLGR
(GPS).

## MATERIALS & INSTRUMENTS:

102. Pencil and field note book

103. Precision lightweight GPS receiver (PLGR)

104. Eight fresh AA batteries or external 12V/24V power source.

105. Ground-water site inventory (GWSI) system ground-water site
     schedule, Form 9‑1904-A (fig. 2).

## DATA ACCURACY & LIMITATIONS:

106. The instrument provides accuracy assessment of each reading.

107. Nearby high structures or topography may limit the number of
     satellite links, and thus, accuracy.

108. Military can scramble signals at will, thus preventing an accurate
     reading.

## ADVANTAGES:

109. Direct determination of latitude and longitude without need for a
     map.

110. Portable instrument.

111. Will work anywhere on the earth.

## DISADVANTAGES:

112. Subject to some inaccuracies if sufficient number of satellites
     cannot be contacted.

113. Must be protected because of National security issues.

114. Subject to unscheduled military decisions.

115. Use limited to permanent USGS employees.

## ASSUMPTIONS:

116. Operator has a security approval (security agreement has been
     signed).

117. Operator is trained in the operation of the instrument (has watched
     training video).

118. Operator has received instruction from Custodial Officer.

## INSTRUCTIONS:

119. Set instrument on a flat surface and open the antenna such that it
     is perpendicular to the ground surface.

120. Depress the 'ON' button or 1 second.

121. Wait 15 minutes, or until 'OLD' disappears from the upper
     right-hand corner of the screen. Generally the longer you wait the
     more accurate the position reading.

122. Record the latitude and longitude in the notebook and enter on the
     ground-water site schedule. Record other environmental information
     that could cause errors in the notebook (distance and bearing of
     high structures (buildings, hills, cliffs, etc.)

123. Record the estimate of error (upper right hand corner of the
     screen) in the notebook.

124. Depress the down arrow Ø to show position error, speed, and other
     parameters related to the reading. Record these if pertinent.

125. Depress the right arrow Æ until 'SETUP' is flashing.

126. Depress the down arrow 5 times ØØØØØ to go to the 'SETUP DTM:NAR'
     screen.

127. Record the datum information shown on the second line in the
     notebook and on the ground-water site schedule.

128. Depress the 'OFF' button 2 times.

## DATA RECORDING

All data required by NWIS on the ground-water site inventory form (fig.
2) should be entered at the site. All other pertinent information should
be recorded in your field notebook

## REFERENCES

None

# 

# 

# ENTRY OF SITE DATA INTO GWSI DATABASE 

## PURPOSE

To assure accurate entry of field site information into GWSI database.
The District Ground Water Information Unit (GWIU) is responsible for the
entry and quality control of all ground-water data input into the GWSI
database. When a project needs to input large quantities of data into
the system, the GWIU offers assistance to project personnel. This is
necessitated by the amount of time required to assure the accuracy of
the data entered into the system. To assure compliance with established
standards, several stages of checking are required before data are
entered into the system.

## MATERIALS & INSTRUMENTS: 

129. Well or spring site information recorded on field well schedule
     9-1904-A (fig. 2) and the location plotted on a 7.5‑minute
     topographic map.

130. USGS 7.5‑minute latitude-longitude scale.

131. USGS Hydrologic Unit Map for your state.

132. Ground-water site inventory (GWSI) system, ground-water site
     schedule, form 9‑1904-A (fig. 2)

## DATA ACCURACY & LIMITATIONS:

133. Latitude and longitude values determined with a USGS 7.5 minute
     latitude-longitude scale can be read to the nearest 0.5 second.
     Graphic digitizer\'s are available with accuracy\'s as low as +
     or - 0.003 second. Latitude and longitude values determined using
     either of these methods in conjunction with a USGS 7.5 minute
     quadrangle map should be rounded to the nearest second.

134. Altitudes determined from topographic maps are accurate to within
     one half the map contour interval.

INSTRUCTIONS:

A. General procedures for entering ground water site data into local
database

135. As each step of checking is completed, the person who completed the
     check will initial and date the GWSI data processing checklist on
     the front of the ground-water site schedule (fig. 2).

136. Geohydrologic unit designations for individual wells may be coded,
     but only if the designation is based on published data, or if the
     stratigraphy is generally recognized as representative of site
     geology. Assignment of codes is the responsibility of the project
     chief, District Ground-Water Specialist, and Chief of the GWIU.

B. Recording site data on Form 9‑1904-A (fig. 2):

137. The following data elements comprise the minimum amount of
     information needed to enter a ground-water site into GWSI. The GWSI
     component number (C#) is shown for each data element.

```{=html}
<!-- -->
```
i.  Geographic location\--Latitude (C9), longitude (C10),
    latitude-longitude accuracy (C11), sketch map of site location,
    altitude (C16), and altitude accuracy (C18).

j.  Political regimes\--District (C6), state (C7) and county or town
    identification (C8), and land-net location (C13).

k.  Source identifiers\--Owner\'s name (C161), source agency or company
    (C4), agency use (C803), date inventoried (C711), site
    identification number (C1), station name (C12), station type (C802),
    date of site visit (C187), and name of person conducting site visit
    (C188).

l.  Individual site characteristics\--Hydrologic unit code (C20),
    topographic setting (C19), type of ground-water site (C2), data
    reliability (C3), use of site (C23), use of water (C24), measuring
    point (MP) beginning date (C321), MP height (C323), MP remarks
    (C324), water level (C30), date water level measured (C31), and
    source of water-level data (C33).

```{=html}
<!-- -->
```
138. Transfer the location of the site from the field map to a USGS 7.5
     minute topographic quadrangle map. Determine the ground-water site
     latitude (C9) and longitude (C10) to the nearest second using a
     USGS 7.5 minute latitude-longitude scale or a digitizer, and record
     the latitude and longitude accuracy (C11) as one second. See GPWD 5
     for the technical procedure document on locating a well.

139. Determine the altitude (C16) of the land surface, in feet above the
     National Geodetic Vertical Datum of 1929, at the site using a USGS
     7.5 topographic quadrangle map. Record the altitude accuracy (C18).
     Altitudes determined from topographic maps are accurate to within
     one half of the contour interval of the map.

140. Record the district (C6) code in the first two positions of the
     field, and use the third position to identify the subdistrict
     office, if applicable. Next enter the FIPS numeric codes for the
     state (C7) and county or town identification (C8) in which the site
     is located. If applicable, enter the land-net location (C13), the
     legal description of the 10-acre tract in which the site is
     located.

141. Record the owner\'s name (C161).

142. Record the source agency (C4) that reports the data.

143. Record agency use (C803) as A (active), I (inactive), or O
     (inventory only).

144. Record the date the ground-water site was inventoried (C711).

145. Record the 15-digit site identification number (C1), which is
     formed initially from the latitude and longitude. The 14th and 15th
     digits are a sequence number used to distinguish between sites at
     the same location. The first sequence number assigned should be 01.

146. Record the station name (C12) for a ground-water site using the
     local well-numbering system supported by your district office.

147. Record the station type (C802) by placing a Y in the appropriate
     position. Position 1, stream; 2, lake or reservoir; 3, estuary; 4,
     unassigned; 5, spring; 6, well; or 7, meteorological station.

148. Record the date of the site visit (C187) and the name of the person
     conducting the site visit (C188). The date of the first site visit
     will be the same as the date the site was inventoried (C711).

149. Record the eight-digit hydrologic unit code (C20) for the Office of
     Water Data Coordination cataloging unit in which the site is
     located using the USGS Hydrologic Unit Map for your state.

150. Record the topographic setting (C19) from the field site schedule
     (form 9-1904-A) and verify the setting with the topographic map.
     Types of topographic settings are given under general site data on
     form 9-1904-A.

151. Record the type of ground-water site (C2) and the data reliability
     (C3). Codes for C2 and C3 are given under ground-water site data on
     form 9-1904-A.

152. Record the use of the site (C23) and the use of the water (C24).
     Codes for C23 and C24 are given under ground-water site data on
     form 9-1904-A.

153. Record the date the measuring point (MP) was established (C321) and
     the height of the MP (C323) above or below land surface datum
     (LSD). Values for measuring points below LSD should be preceded by
     a minus sign (-). Also record a detailed description of the MP
     (C324). See GWPD 3 for the technical procedure document on
     establishing an MP.

154. Record the water level (C30), the date of the water level
     measurement (C31), and the source of the water-level data (C33).
     Codes for C33 are given under ground-water site data on form
     9-1904-A. See technical procedure document GWPD 1 for making
     water-level measurements using a graduated steel tape, or GWPD 4
     for making water-level measurements using an electric tape.

## REFERENCES

NWIS User\'s Manual, v. 2, chap. 4. Ground-Water Site Inventory System

## 

# 

# ESTABLISHING A PERMANANT MEASURING POINT

## PURPOSE

To establish a permanent reference point from which all water levels are
measured in a particular well.

MATERIALS & INSTRUMENTS:

155. Ground-water site inventory site schedule, Form 9-1904-A.

156. Steel tape graduated in feet, tenths, and hundredths of feet.

157. Steel tape calibration and maintenance equipment log book.

158. Field notebook.

159. Pencil and eraser.

160. Pocket size tape measure graduated in feet, tenths, and hundredths
     of feet.

161. Two wrenches with adjustable jaws for removing well cap and
     assorted tools.

## DATA ACCURACY & LIMITATIONS

The accuracy with which the measuring point (MP) measurement is
established depends upon the accuracy of the water-level measurements
being made. If water levels are measured in hundredths of a foot, then
the MP should be established to an accuracy of 0.01 foot.

ASSUMPTIONS:

162. For comparability, water-level measurements must be referenced to
     the same datum (elevation).

163. Land surface datum (LSD) at the well was set by the person who made
     the initial water-level measurement in the well. LSD is an
     arbitrary plane chosen to be approximately equivalent to the
     average altitude of the ground around the well. Because LSD around
     a well may change over time, the distance between the MP and LSD
     should be checked periodically.

164. Measuring points change from time to time, especially on private
     wells.

INSTRUCTIONS:

165. Upon installation of a monitoring well, or when inventorying an
     existing well, establish a MP. The MP must be as permanent as
     possible, clearly defined, marked, and easily located.

166. The measuring point is measured in reference to land surface datum
     (LSD) and is the most convenient place to measure the water level
     in a well.

167. The top of the casing should be designated as the MP.

168. If possible, position the MP at a particular point on the casing
     where a leveling rod could be set on it directly over the well and
     the measuring tape can hang freely when it is in contact with the
     MP.

169. If possible clearly mark the MP.

170. The height of the MP is measured in feet above or below LSD
     (fig. 1) and is recorded on the site schedule (form 9-1904-A, fig.
     2). Values for measuring points below land surface (fig. 1) should
     be preceded by a minus sign (-). Also record the date the MP was
     established and a detailed description of the MP. Depending on the
     purpose of a study, it may be desirable to \"survey-in\" the LSD
     and the MP. See GWPD 3, which includes description of the minimum
     set of data elements needed to identify a ground-water site.

171. Make a detailed sketch of the MP on the back of the site schedule
     form 9-1904-A, and if you can, take a photograph. After the
     photograph is developed, mark the MP and draw an arrow to it. Date
     all sketches and photographs.

## DATA RECORDING

All calibration and maintenance data associated with the steel tape
being used are recorded in its calibration and maintenance equipment log
book (if applicable). MP data are recorded in a field notebook and on
the GWSI ground-water site schedule (Form 9‑1904-A).

## REFERENCES

1\. U.S. Geological Survey, 1990, National water information system
user\'s manual, ground-water site inventory system: U.S. Geological
Survey Open-File Report 89-587, v. 2, chap. 4.

2\. United States, Office of Water Data Coordination, 1977 -, National
handbook of recommended methods for water-data acquisition: Office of
Water Data Coordination, U.S. Geological Survey, U.S. Department of the
Interior, chap. 2, 149 p.

3\. U.S. Geological Survey, Level 1 training\--Ground-water field
techniques, 1994.

4\. GWPD 3, ground-water site inventory
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html)

# WATER-LEVEL MEASUREMENTS USING AN ELECTRICAL TAPE

## PURPOSE

To measure the depth to the water surface below a measuring point using
the electric tape method.

MATERIALS & INSTRUMENTS:

172. Electric water-level measurement device. Electric tapes are
     commonly mounted on a hand-cranked supply reel that contains space
     for the batteries and some device for signaling when the circuit is
     closed.

173. A steel measuring tape graduated in feet, tenths and hundredths of
     feet.

174. Electric tape calibration and maintenance equipment log book
     (required when high accuracy needed).

175. Pencil and eraser.

176. Water level measurements field form 9-1904-E (fig. 1).

177. Two wrenches with adjustable jaws for removing well cap.

178. Laboratory grade detergent such as alconox or liquinox (for
     washing). Do not use solvents, alcohols or acids.

DATA ACCURACY & LIMITATIONS:

179. Independent electric tape measurements of static water levels using
     the same tape should agree within + or - 0.04 foot for depths of
     less than about 200 feet.

180. For depths of about 500 feet, the maximum difference of independent
     measurements using the same tape should agree within + or - 0.1
     foot.

181. For depths in the 2,000 foot range, the repeatability of
     measurements using the same tape should agree within + or - 0.5
     foot (Garber and Koopman, 1968, p. 11).

ADVANTAGES:

182. Superior when water is dripping into the well or condensing on the
     inside casing walls which may make it impossible to get a good
     water mark on the chalked tape.

183. Superior in wells that are being pumped, particularly with
     large-discharge pumps, where the splashing of the water surface
     makes consistent results by the wetted-tape method impossible.

184. Superior when a series of measurements are needed in quick
     succession, such as in aquifer tests, because the electric tape
     does not have to be removed from the well for each reading.

185. Safer to use in pumping wells because the water is sensed as soon
     as the probe reaches the water surface and there is less danger of
     lowering the tape into the pump impellers.

DISADVANTAGES:

186. Gives slightly less accurate results than a steel tape. See data
     accuracy.

187. Harder to keep calibrated than a steel tape. Electric connections
     need to be maintained in good order.

ASSUMPTIONS:

188. An established measuring point (MP) exists and the distance from
     the MP to land-surface datum (LSD) is known (fig.1). See previous
     section for the technical procedure document on establishing a
     permanent MP.

189. The MP is clearly marked and described so that a person who has not
     measured the well will know where to measure from.

INSTRUCTIONS:

190. Before using an electric tape in the field, calibrate it by
     comparing the total length of the electric tape against the length
     of an acceptable steel tape. An acceptable steel tape is one that
     is maintained, in the office, for use only for calibrating tapes.
     Also, check the accuracy of the position of each 5-foot interval
     metal band to make sure that the bands have not moved. This is
     especially important if the electric tape has been used for a long
     time or after it has been pulled hard in attempting to free the
     line.

191. Check the circuitry of the electric tape before lowering the probe
     into the well by dipping the probe into water and observe if the
     indicator needle deflects, indicating that the circuit is closing.
     Note the position the indicator needle deflects during the
     circuitry check.

192. Make all readings using the same deflection point on the indicator
     scale so that water levels will be consistent between measurements.

193. Lower the electrode probe slowly into the well until contact with
     the water surface indicates that the circuit it closed. Place the
     nail of the index finger on the insulated wire at the MP when the
     indicator needle deflects to the point you chose during the
     circuitry testing.

194. Partly withdraw the electric tape from the well and record the foot
     mark of the nearest 5-foot tape band in the \`NEAREST 5-FOOT TAPE
     BAND\' column of the water level measurements field form (#2, table
     1).

195. Measure the distance from the MP mark on the insulated wire to the
     nearest 5-foot tape band with a graduated steel tape and record
     that distance in the \`DIFFERENCE BETWEEN MP MARK AND NEAREST
     5-FOOT TAPE MARK\' column of the water level measurements field
     form (#3, table 1).

196. To obtain the depth to water below the MP, subtract the distance
     between the MP mark and the next highest 5-foot tape band, or if
     the nearest 5-foot tape band is lower, add the distance to the MP
     mark to obtain the depth to water below the MP. Record this number
     in the \`DEPTH TO WATER FROM MP\' column of the water level
     measurements field form (#4, table 1).

197. Apply the MP correction to get the depth to water below or above
     LSD. If the MP is above land surface, its height is subtracted from
     the water level to obtain the depth to water below land surface. If
     the MP is below land surface precede the MP correction value with a
     minus (-) sign and subtract its height from the water level to
     obtain the depth to water below land surface. Subtract the MP
     correction (#5, table 1) from the depth to water from MP (#4,
     table 1) and record this number in the \`DEPTH TO WATER CORRECTED
     FOR LSD\' column of the water level measurements field form (#6,
     table 1). If the water level is above LSD, enter the water level in
     feet above land surface preceded by a minus sign (-)

198. Make a check measurement by repeating steps 4 through 8. If the
     check measurement does not agree with the original measurement
     within the accuracy given under data accuracy, continue to make
     check measurements until the reason for the lack of agreement is
     determined or until the results are shown to be reliable.

199. In areas of suspected contamination, disinfect the electric tape
     after completing the well measurement by cleansing the part of the
     tape that was submerged below the water surface using laboratory
     grade detergent; this will avoid possible contamination of other
     wells.

200. Maintain the tape in good working condition by periodically
     checking the tape for breaks, kinks, and possible stretch due to
     the suspended weight of the tape and the tape weight. Do not let
     the tape rub across the top of the casing because the 5-foot metal
     bands can become displaced; consequently, placement of the bands
     should be checked frequently with a steel tape.

## DATA RECORDING

In areas where high accuracy is required, such as waste-site
evaluations, a calibration log shall be maintained in which all
calibration and maintenance data associated with the electric tape are
recorded. All data are recorded in the Water-Level Measurements Field
Form 9-1904-E to the appropriate accuracy for the depth being measured.
See data accuracy and limitations.

## REFERENCES

1\. U.S. Geological Survey, Level 1 training\--Ground-water field
techniques, 1994.

2\. United States, Office of Water Data Coordination, 1977 -, National
handbook of recommended methods for water-data acquisition: Office of
Water Data Coordination, U.S. Geological Survey, U.S. Department of the
Interior, chap. 2, 149 p.

3\. Heath, Ralph C., 1983, Basic ground-water hydrology: U.S. Geological
Survey Water Supply Paper 2220, p. 72-73.

4\. Garber, M. S., and Koopman, F.C., 1968, Methods of measuring water
levels in deep wells: U.S. Geological Survey TWRI, book 8, chap. A1, p.
6-11.

5\. GWPD 4, establishing a permanent measuring point
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

# OBTAINING PERMISSION TO INSTALL, MAINTAIN, AND USE A WELL ON PRIVATE PROPERTY

## PURPOSE

To describe a procedure for properly obtaining permission to install,
maintain and use a well on private property, and to collect water
samples from a well on private property.

MATERIALS & INSTRUMENTS:

201. Form 9-1483, dated November 1993, Agreement for installation,
     maintenance, and use of a test hole and/or observation well on
     private property (fig. 3 at the end of this section).

202. Unnumbered form, Permission to collect water samples (fig. 4 at the
     end of this section).

203. Site location map.

204. Field notebook.

205. Pencil, eraser, and pen.

## DATA ACCURACY & LIMITATIONS

When public land is not suitable, the use of private property is
permitted if, prior to drilling operations, a signed agreement for
access to and installation, maintenance, and use of the test hole or
observation well is obtained from the property owner.

ASSUMPTIONS:

206. The person requesting permission to install, maintain, or use a
     well on private property is familiar with the legislation in WRD
     Memo 92.14 that describes the authority for conducting water
     resources investigations.

207. The requestor is also familiar with State law requirements to
     notify the local One Call Center (in some States referred to as,
     \"call before you dig\") before blasting, boring, digging,
     drilling, trenching, or other earth moving operations. The call
     before you dig system was created to promote public safety and
     avoid costly damage to underground facilities.

INSTRUCTIONS:

208. Permission to install, maintain, and use a well.

```{=html}
<!-- -->
```
m.  It is Water Resources Division policy to obtain written permission
    before drilling on private property, restricted public property, and
    leased Federal land.

n.  Test drilling preferably should be confined to public lands
    (federal, state, county, or municipally-owned) when the location
    will serve as well as one on privately owned land.

o.  However, if the information needed can only be obtained at a site on
    private property, that site may be used if permission to drill test
    wells and operate observation wells is obtained in advance.

p.  Permission to drill will be in the form of an agreement between the
    U.S. Geological Survey (USGS) and the owner (s) of the property
    (private or public) using Form 9‑1483.

q.  Each agreement is assigned a number consisting of the first four
    digits of your cost center, hyphen, a sequential number beginning
    with 01, and the year in which the agreement is processed. For
    example, 4060-0195, 4060-0295, etc. This number should be referenced
    on invoices submitted to the Office of Financial Management for
    payment to a property owner.

r.  Complete all the information on the agreement for installation,
    maintenance and use of a test hole and/or observation well shown in
    figure 3. Attach to the agreement, a site map showing the location
    of each proposed test hole and/or observation well. Form 9-1483 must
    be signed by the licensor (permitter), a USGS representative
    (preferably the Project Chief), and approved by the USGS District
    Chief.

```{=html}
<!-- -->
```
209. Permission to collect water samples from a well.

```{=html}
<!-- -->
```
s.  It is Water Resources Division policy to obtain oral or written
    permission before collecting water samples on private property,
    restricted public property, and leased Federal land.

t.  However, experience has shown that oral permission to collect water
    samples is easier to obtain, but written permission provides
    stronger legal protection.

u.  Water-quality sampling preferably should be confined to public lands
    (federal, state, county, or municipally-owned) when the location
    will serve as well as one on privately owned land.

v.  However, if the information needed can only be obtained at a site on
    private property, that site may be used if permission to collect
    water samples from wells is obtained in advance.

w.  Oral permission will be documented in a project field notebook.
    Record the site location, date, permitter, kind of sample, and name
    of the USGS personnel taking the sample.

x.  Written permission will be in the form of an agreement between the
    U.S. Geological Survey (USGS) and the owner (s) of the property
    (private or public) using the unnumbered form shown in figure 2. The
    unnumbered form must be signed by the permitter, and a USGS
    representative (preferably the Project Chief).

## DATA RECORDING

Permission details are recorded on the installation, maintenance, and
use of a test hole or observation well form\--Form 9‑1483 (fig. 1). If
water samples are to be collected, also complete the permission to
collect water samples using the unnumbered form (fig. 2).

## REFERENCES

Figure 3. Agreement for installation, maintenance and use of a test hole
and/or observatory well on private property\--Form 9-1483

Figure 4. Permission to Collect Water Samples\--Unnumbered form

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

![](media/image7.png){width="5.999305555555556in"
height="7.877083333333333in"}

# INSTALLING A PRESSURE TRANSDUCER AND ACTIVATING THE DATA RECORDING DEVICE

## PURPOSE

To describe a procedure for installing a pressure transducer in a well
or stream to measure and record a hydraulic head and assuring the
quality of the data.

## EXPLANATION

Pressure transducers and electronic data recording devices are one of
the most prevalent methods of collecting water-level data in wells and
stage data on streams. There are numerous manufacturers of these
instruments, and there are 2 basic types of units: (1) transducers and a
data recorder built into the same unit; everything is submerged, and
(2) transducers separate from the recording unit linked by a line; only
the transducer is submerged.

MATERIALS & INSTRUMENTS:

210. Transducer and electronic data recording device.

211. Steel tape for measuring water level to within ±0.01 ft

212. Media for electronic storage of downloaded data (disk, laptop
     computer, etc.)

213. Equipment for interrogating transducer.

214. Site location map.

215. Field notebook.

216. Pencil, eraser, and pen.

## LIMITATIONS

Pressure transducers are designed with different pressure ranges. For
example, the Design Analysis Assoc. instrument with a range of 0 to 5
pounds per square inch (psi) measures water level fluctuations in the
range of 0 to about 11.53 ft with an accuracy of ±0.0002 ft. If the
water-level fluctuation is expected to be greater, then an instrument
with a higher psi range should be used. The higher the psi range, the
less accurate the readings.

Older transducers that are connected to a data recording device at the
surface can be sensitive to instrument drift caused by air temperature
fluctuations. Newer instruments compensate for this drift automatically.

ASSUMPTIONS:

217. The site file and appropriate mandatory data has been established
     and is already in the NWIS database.

218. The probable maximum change in water level is known.

219. The probable minimum water level (lowest) is known.

220. The transducer cable already has the necessary junction box and
     appropriate connector installed.

221. The manufacturer's suggested setup procedure for the instrument is
     followed.

INSTRUCTIONS:

222. Perform any pre-calibration of the instrument suggested by the
     manufacturer's instructions. Record date, time, and results of
     calibration in the field notebook.

223. Measure and mark on the transducer cable the pre-determined depth
     to be submerged.

224. Lower the transducer into the well or stream until the mark on the
     cable just touches the water level or stage.

225. Connect a data recorder to the transducer cable.

226. Follow the instructions provided by the manufacturer in initially
     setting up the data-recording device.

227. If the transducer is to record altitude above mean sea level, depth
     below land surface, or any other number from an arbitrary datum,
     measure the water level or stream stage using a steel tape and
     record the number with respect to the chosen datum. Set the data
     recorder to this number. If water level change is the only output
     necessary, then set the data recorder to zero.

228. Adjust the recorder settings so that a rise in water level records
     as a number greater than the preset number and declines in water
     level record as numbers less than the preset number.

229. Raise or lower the transducer a known vertical distance and watch
     the recorder display to see if it shows the correct water-level
     change. If it does, proceed to step 9. If the change shown is not
     correct, go back to step 5.

230. Set the frequency of recording to that which is appropriate for the
     objectives. Typically, frequency can be even time increments,
     logarithmic increments, or can be based on a preset change in water
     level.

## RECORDING

Record all measurements taken during initial calibration of the
instrument in the Field notebook. Water levels measured as the
instrument is deployed in the field should be recorded in the Field
notebook and on the water-level sheet established for the site.

## REFERENCES

Each individual instrument is accompanied by its own manual and set of
instructions on calibration and setup.

# RECOGNIZING AND REMOVING DEBRIS FROM A WELL

## PURPOSE

To recognize when a well contains debris and what to do about removing
the debris from the well.

MATERIALS & INSTRUMENTS:

231. Steel tape graduated in feet, tenths and hundredths of feet, or an
     electric tape.

232. Blue carpenters chalk.

233. Clean rag.

234. Mirror

235. Flashlight.

236. Pencil and eraser.

237. Field notebook.

238. Water level measurements form 9-1904-E (fig. 1).

239. A grappling device with wire line, or heavy-duty treble fishing
     hook and rope.

DATA ACCURACY & LIMITATIONS:

240. A graduated steel tape is commonly accurate to 0.01 foot.

241. The water level should be within 200 feet of the land surface.

## ASSUMPTIONS

Individual has been trained to make water-level measurements with a
graduated steel tape and an electric tape.

## INSTRUCTIONS

The quality of water-level data from a well is directly related to well
maintenance. If debris is present in a well, it could cause errors in
water-level measurements if the debris affects the plumbness of the
tape.

242. Make a water-level measurement with a graduated steel tape or an
     electric tape. If there is a lack of agreement between the original
     water-level measurement and subsequent water-level check
     measurements it could indicate that the well contains debris.

243. When measuring the water level in the well, if the measuring tape
     goes slack as it is being slowly lowered into the well, the weight
     or probe has probably hit well debris.

244. To check for well debris on a sunny day, use a mirror to look into
     the well. The mirror is held in the hand and rotated back and forth
     until the proper angle is obtained to allow the sun to reflect off
     the mirror and down the well onto the water surface.

245. If the well is located in a dark enclosed area away from the sun,
     or the weather is overcast, use a flashlight to look down the well
     for debris.

246. To remove light to medium weight wood debris from a well, a simple
     inexpensive device to use is a heavy-duty treble fishing hook
     attached to a rope. Lower the heavy-duty treble hook down the well
     while using the mirror to see when the hook is below the debris. To
     remove the debris from the well, move the rope upward with a quick
     jerking motion until the wood debris becomes snagged on the treble
     hook. Slowly remove the rope and debris from the well. If the
     object is below the water surface where it cannot be seen, feel for
     the debris while trying to snag it.

247. To remove heavy wood or debris that cannot be snagged, use a
     grappling device similar to a pair of ice tongs. The device shown
     in figure 1 of GWPD 6 has been designed and effectively used to
     remove debris from wells and requires no special talent to operate.
     This type of device can be used to remove blocks of wood, stones,
     cans, bottles, pipes, and poles from wells. This type of grappling
     device can be constructed from the photographs show in figure 1.

248. To remove debris from a well, cock the device in the open position
     and lower into the well on a suspension cable that is fastened to a
     shackle. When the tripping rod strikes the debris in the well, the
     rod pushes upward on the locking bar, releasing it, and the spring
     opposite the locking bar pulls the arms together. The weight of the
     debris being lifted from the well holds the arms together. The
     heavier the object, the tighter the arms grip. In case the tripping
     rod will not close the arms, the arms can be closed from the
     surface by attaching a line at the pivot point of the locking bar.
     Lower the grappling device into the well and pull on the line
     connected to the locking bar when the arms are in the desired
     position. The arms will close around the debris without the aid of
     the tripping rod.

## DATA RECORDING

Data are recorded in a field notebook and the Water-Level Measurements
form 9-1904-E.

## REFERENCES

249. U.S. Geological Survey, 1965, Selected Techniques in Water
     Resources Investigations, compiled by G.N. Mesnier and E.B. Chase:
     U.S. Geological Survey Water-Paper 1822, p. 43-46.

250. U.S. Geological Survey Level 1 training, ground-water field
     techniques, 1994.

251. GWPD 1, water-level measurement using graduated steel tape
     (http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

252. GWPD 6, recognizing and removing debris from a well
     (http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

# CONTINUOUS WATER-LEVEL MEASUREMENTS USING A FLOAT-ACTIVATED RECORDER

## PURPOSE

To make continuous water-level measurements in a well using a
float-activated recorder.

MATERIALS & INSTRUMENTS:

253. Graphic recorder, digital recorder, data logger, or data collection
     platform (DCP).

254. Recorder chart, digital-recorder tape, data cartridge.

255. Battery, 12 volt, 8 and 26 amp hr, rechargeable, and spare
     batteries.

256. Recorder clock and spare clocks.

257. Float and counterweight.

258. Small diameter stranded cable or a flat steel tape.

259. A steel tape graduated in feet, tenths and hundredths of feet, blue
     carpenters chalk, and a clean rag.

260. Recorder shelter with lock.

261. Field notebook, pencil and eraser.

262. Water level measurements form 9-1904-E.

263. Laptop computer for collection of Basic Data Recorder records (when
     applicable).

264. Recorder well servicing log (fig. 1).

DATA ACCURACY & LIMITATIONS:

265. The initial water level setting for a float-activated recorder
     should be determined using a graduated steel tape, which is
     commonly accurate to 0.01 foot.

266. Each time a float-activated recorder is serviced, a calibration
     check water-level measurement should be made with a graduated steel
     tape.

267. Where depth to water is greater than a few feet below the top of
     the casing, special care should be taken to minimize friction
     between the float cable and the walls of the well. The float
     selected should be the largest diameter that can be accommodated by
     the well casing.

268. The recorder clock is the most susceptible part of the recorder to
     malfunction, and should be cleaned and adjusted periodically.

269. Float-activated recorders should be used in wells that are 3-inches
     in diameter or larger.

270. Float-activated recorders cannot be used in flowing wells, where
     the water level is above the top of the casing. However, if the
     well can be shut in a pressure recorder, a recorder can be used.

ADVANTAGES:

271. Graphic recorder

```{=html}
<!-- -->
```
y.  Simplest recording device.

z.  Recorder chart gives a continuous water level trace.

a.  Immediate visualization of water-level fluctuations.

b.  Accurate and reliable.

```{=html}
<!-- -->
```
272. Digital recorder

```{=html}
<!-- -->
```
c.  Longer data-collection time than a graphic recorder.

d.  Accurate and reliable.

```{=html}
<!-- -->
```
273. Data logger

```{=html}
<!-- -->
```
e.  Expandable data memory.

f.  Programmable.

g.  Accurate and reliable.

```{=html}
<!-- -->
```
274. DCP

```{=html}
<!-- -->
```
h.  Provides real-time data.

i.  Satellite transmittal of data.

j.  Accurate and reliable.

DISADVANTAGES:

275. 1\. Graphic recorder

```{=html}
<!-- -->
```
k.  Limited data-collection time, one month versus several months.

l.  Data must be determined manually.

m.  If the graphic recorder clock fails, data will be lost.

```{=html}
<!-- -->
```
276. Digital recorder

```{=html}
<!-- -->
```
n.  Rapidly changing water level peaks may be missed due to the limited
    preselected time intervals on the 16-channel paper tape.

o.  If the digital recorder clock fails, data will be lost.

p.  Becoming obsolete.

```{=html}
<!-- -->
```
277. Data logger

```{=html}
<!-- -->
```
q.  Rapidly changing water level peaks may be missed due to preselected
    time intervals.

r.  Most data loggers require a field computer or a digital interface to
    download data.

s.  If the memory backup battery fails, data may be lost.

```{=html}
<!-- -->
```
278. DCP

```{=html}
<!-- -->
```
t.  Transmittal of real-time data can be affected by computer downtime.

u.  Rapidly changing water level peaks may be missed due to pre-selected
    time intervals.

v.  Ice on the external antenna can interfere with data transmittal to
    the satellite.

w.  If the memory backup battery fails, data may be lost.

ASSUMPTIONS:

279. A permanent measuring point has been established as described in
     GWPD.

280. The user has been trained in making water-level measurements using
     the graduated steel-tape method as described in GWPD 1.

## INSTRUCTIONS

For some hydrogeologic studies, frequent and uninterrupted water-level
measurements may be needed to identify unique properties of the
ground-water flow system. In studies where a more complete picture of
water-level fluctuations is needed, automatic float-activated,
water-level recorders can be installed. Float-activated recorders sense
changes in water level by the movement of a weighted float that is
lowered into the well. A cable attached to the float passes over a
pulley on the recorder and a counterweight is attached to the other end
of the cable and hangs in the well. When the clearance between the float
and the well casing is small, the float cable should be setup so that
the counterweight does not have to pass the float, but is always above
or below the water level. If the counterweight is immersed below the
water level, a little extra weight should be added to offset the
water\'s buoyancy.

281. Types of float-activated recorders:

```{=html}
<!-- -->
```
x.  Chart or graphic recorder \-- This type of recorder (figure 1,
    GWPD 14) is the simplest device commonly in use. It consists on a
    drum chart that is actuated mechanically by a float that follows the
    water level. The graphic recorder provides a continuous trace of the
    water level on a chart, which is graduated to record both water
    level and time. Battery operated clocks for graphic recorders can be
    set to record a wide variety of intervals, ranging from a few hours
    to one month. The pulley is connected to the recorder drum by gears.
    A wide range of drum gears is available to set up the chart so that
    its rotation is proportional to the movement of the float. Figure 1
    (GWPD 14) shows a typical setup for a graphic water-level recorder
    using a guide pulley assembly in a small diameter well, as well as a
    standard position setup.

y.  Data logger \-- The Sutron-8400, the Campbell Scientific CR-10, and
    the BDR (basic data recorder) are the latest state-of-the-art
    recorders. The Sutron data logger, which does not require a field
    computer or a digital interface to download data, has become the
    data logger most commonly in use. Data are easily downloaded using a
    data-collection card. Each data card holds up to 64k bytes of data
    (approximately 32,000 readings), and is expandable to 128k, which
    translates into nearly two years of data for one reading recorded
    every 15 minutes. Preselected time intervals are programmed by the
    user. The standard CR-10 stores 300 data values and is expandable to
    29,900. The BDR operates similar to the CR-10, but has less memory.

z.  DCP \-- DCPs provide real-time data using the Geostationary Orbiting
    Environmental Satellite (GOES) system. Data are held until the
    satellite passes overhead when data are transmitted to the
    satellite. The satellite then transmits the data to a down receive
    site, which in turn transmits it to the District computer. Sutron
    data loggers equipped with a GOES radio setup are commonly used at
    DCP installations.

```{=html}
<!-- -->
```
282. Select a graphic recorder, a digital recorder, a data logger, or a
     data collection platform (DCP) setup, whichever best suits the
     water level collection needs of the project.

283. Install the float-activated recorder selected in a suitable locking
     shelter that is protected from the weather and vandalism. The
     recorder shelter should also be solidly anchored.

284. Measure the depth to water in the well using a graduated steel tape
     (wetted tape) to obtain an accurate water-level measurement with
     which to calibrate the recorder water level.

285. Set the initial time and water level for the recorder using the
     steel tape water-level measurement.

286. Each time the float-activated recorder is serviced, a calibration
     check water-level measurement should be made with a graduated steel
     tape.

287. Record the initial water-level measurement and all site-visit
     water-level measurements on the water-level measurement field form
     (fig. 1).

288. In small diameter wells (less than 3 inches) it is recommended that
     a pressure transducer be used for measuring water levels.

## DATA RECORDING

All data are recorded in the field notebook and in the water-level
measurements field form (Form 9-1904-E).

## REFERENCES

1\. U.S. Geological Survey Level 1 training, ground-water field
techniques, 1994.

2\. United States, Office of Water Data Coordination, 1977-, National
handbook of recommended methods for water-data acquisition: Office of
Water Data Coordination, Geological Survey, U.S. Department of the
Interior, Reston, Va., chap. 2, p. 1-149.

3\. GWPD 1, Water-level measurement using graduated steel tape
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

4\. GWPD 3, Establishing a permanent measuring point
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

5\. GWPD 14, Continuous water-level measurements using a float activated
recorder (http://water.usgs.gov/usgs/ogw/tech_proc/index.html)

6\. Garber, M.S., and Koopman, F.C., 1968, Methods of measuring water
levels in deep wells: U.S. Geological Survey TWRI, book 8, chap. A1:
Washington, U.S. Government Printing Office, 23 p.

# GUIDELINES FOR MONITORING DRILLING ACTIVITES AND HOW TO SAMPLE AND IDENTIFY CORE

## PURPOSE

To ensure compliance with contractual specifications, to record and
document drilling activities properly, and to provide guidelines of the
description and preservation of geologic samples.

MATERIALS & INSTRUMENTS:

HCL (10%) \[ \] Grain-size/shape chart \[ \] Insect Repellent \[ \]

Hand Lens \[ \] Core logging form \[ \] AAPG sample exam. manual \[ \]

Knife \[ \] Pencils \[ \] Drilling log book \[ \]

Color Chart \[ \] Water well handbook \[ \] Binocular microscope \[ \]

Camera \[ \] Film \[ \] Rain gear \[ \]

Sample bags \[ \] Saran wrap \[ \] Permanent marker pen \[ \]

Calculator \[ \] First aid kit \[ \] Snake bite kit \[ \]

Local Geology Site Location Map \[ \] Field Notebook \[ \]

References \[ \]

## DATA ACCURACY & LIMITATIONS

Reported well depths and sample intervals can be highly variable due to
washouts and errors on the part of drillers. It is important to keep
track of well depths by monitoring the number of drill stem inserted
into borehole. Borehole geophysical logs can be used to verify well
depths, within the accuracy limits of the geophysical equipment. Well
cuttings samples can be highly inaccurate regarding sampled interval and
core samples can be inaccurate when large sections of core are not
recovered (generally in sandy intervals or in cavernous zones).

INSTRUCTIONS:

289. Establish lines of communication with local emergency personnel
     (police) prior to commencement of drilling. Local police need to
     know your location, hours of operation, and the names of people in
     your work party (this will help them in patrolling your site). You
     need to know the location of the nearest emergency medical facility
     and to have an emergency plan in case of injury.

290. Always remember that the drillers are working for the USGS. For
     this reason, it is important to maintain a \"supervisor/employee\"
     relationship with the drill crew. To maintain such a relationship,
     the following suggestions may be helpful:

```{=html}
<!-- -->
```
a.  Limit socializing with the drillers during off hours (don\'t become
    \"one of the guys\"),

b.  Always behave in a professional manner when on site or after hours.

c.  Be helpful when on site, but don\'t do their work for them. They are
    being paid to do their job. Your job is to ensure that USGS is
    getting the products that we are paying for (and logging core),

d.  Don\'t get in the way of the drillers. They need to focus on the
    tasks at hand (which can be potentially dangerous) and they don\'t
    need you in their way when doing their work.

```{=html}
<!-- -->
```
291. Keep daily log of drilling activities (see Lapham and others,
     1997). This includes rig shutdowns and repairs. Keep in contact
     with head driller and ASK QUESTIONS. Sometimes a driller will try
     to take advantage of an inexperienced geologist on site, so it is
     very important to ask questions. Keep an eye on supplies\--if it
     looks to you like they are running low on an item remind the head
     driller. Keep track of prolonged absences of drillers and record
     times of arrival and departure.

292. Keep project HQ informed on a daily basis. Phone in during a break
     in drilling or at night. The project chief will provide you with
     home phone number.

293. Become familiar with the contract specifications. These are the
     guidelines that the drillers must follow. There may be some
     deviations from this, however they should be minimal and should be
     cleared with project HQ.

294. When installing well materials, keep account of the amount of
     materials used. This includes:

-   Casing: Measure length of sections, note type of material, and count
    the number of lengths put into drill hole.

-   Screen: Same as for casing, however you must also consider the size
    of the screen opening.

-   Grout: Compute the volume of grout required to set casing. See Water
    Well handbook for guidelines. Record amount of grout poured into
    hole.

-   Bentonite: Same as for grout.

295. A log of collected core samples needs to be kept using standard
     form (see Lapham and others, 1997). Become familiar with guidelines
     listed in AAPG sample examination manual. Information recorded
     includes:

-   Sample description, in following order (see AAPG manual):

296. Rock type.

297. Color (use GSA rock color chart).

298. Texture, including grain size, sorting, and roundness (see AAPG
     manual).

299. Cement and/or matrix materials. Use 10% HCL to test for carbonates.
     Be sure to limit use of HCL to small portions of the core sample.

300. Fossils and accessories.

301. Sedimentary structures.

302. Porosity

-   Percent recovery. Note how much core was recovered in a given sample
    run.

-   Drilling comments. Note how long it took to core a difficult
    interval, note caving zones, note cavernous zones.

303. Take a photograph of each core box. Use multipurpose film
     (slide/print). Take photograph of each group of 4 consecutive core
     boxes.

304. Sample storage. Each sample should be stored in a cardboard core
     box lined with saran wrap. Loosely wrap sample in this wrap.
     Separate core runs with small wooden blocks labeled with coring
     interval. Label outside of core box with information on well name,
     date collected, driller, interval in box, and box number (i.e. box
     1 of 8). If a sample is removed from the core box, indicate with a
     block of wood (or other divider) the amount and depth of sample,
     and the name of the person removing the sample (i.e. 450\', 3\",
     Phil Dert). Protect these samples! They are worth thousands of
     dollars and should be protected from elements. Keep core boxes off
     ground and covered with waterproof material. Do not leave unsecured
     overnight (to prevent possible vandalism).

305. Geophysical logging.\--Keep office informed of drilling progress so
     that geophysical logging can be scheduled for appropriate time.

306. Predicting depths of hydrogeologic units. Use structure contour and
     thickness maps found in references on local geology.

## DATA RECORDING

See #3, 7, 8, and 9, above.

## REFERENCES

1\. Lapham, W.W., Wilde, F.D., and Koterba, M.T., 1997, Guidelines and
standard procedures for studies of ground-water quality; selection and
installation of wells, and supporting documentation: U.S. Geological
Survey Water-Resource Investigations Report 96-4233, 110 p.

2\. Geological Society of America, 1991, Rock color chart: Boulder, Co.,
Geological Society of America, Denver, Co.

2\. Wentworth, C.K., 1922, A scale of grade and class terms for clastic
sediments: Journal of Geology, v. 30, p. 377-392.

3\. Dunham, R.J., 1962, Classification of carbonate rocks according to
depositional texture, in Classification of carbonate rocks, W.E. Ham,
\[ed.\]: American Association of Petroleum Geologists Memoir 1, p.
108-121.

4\. Driscoll, F. G., 1986, Groundwater and Wells, Johnson Filtration
Systems, Inc., St. Paul, Minnesota, ISBN 0-9616456-0-1, 1089 p.

5\. GWPD 2, Ground-water site inventory
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

6\. GWPD 5, Locating a well
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

7\. GWPD 3, Establishing a permanent measuring point
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

8\. Swanson, R.G., 1981, Sample examination manual, Methods in
exploration series, American Association of Petroleum Geologists, Tulsa,
OK, variously paged.

9\. Anderson, K.E., 1989, Water Well Handbook, Missouri Water Well and
Pump Contractors Association, Inc., Ballwin, MO, 281 p.

# GUIDELINES FOR COLLECTION AND PACKAGING OF CORE SAMPLES FOR HYDRAULIC ANALYSIS

## PURPOSE

Goal is to collect samples from confining units. Try to collect several
intervals within the confining unit, especially if lithologic changes
are observed.

MATERIALS & INSTRUMENTS:

307. Saran wrap.

308. Aluminum foil.

309. Ziploc bags.

310. Marker pens.

311. Packing materials\--boxes, popcorn foam, tape.

## DATA ACCURACY & LIMITATIONS

Reported well depths and sample intervals can be highly variable due to
washouts and errors on the part of drillers. It is important to keep
track of well depths by monitoring the number of drill stem inserted
into borehole. Borehole geophysical logs can be used to verify well
depths, within the accuracy limits of the geophysical equipment. Well
cuttings samples can be highly inaccurate regarding sampled interval and
core samples can be inaccurate when large sections of core are not
recovered (generally in sandy intervals or in cavernous zones).

INSTRUCTIONS:

312. Collect sample as soon as core is pulled from ground.

313. Wrap sample tightly with several layers of SARAN WRAP.

314. Wrap sample tightly with several layers of ALUMINUM FOIL.

315. Place sample into zip lock bag.

316. On each layer (saran wrap, foil, and bag), label interval (ft),
     date collected, and point toward the top with an arrow. Use
     permanent marker.

317. Pack samples into box and pack with popcorn/foam. Label package
     fragile.

318. For each box sent, label sample bags as follows:

-   Sample 1 of 10,

-   2 of 10,

-   3 of 10, etc.

319. Include list of samples included in box, keep copy for our records,
     i.e. Sample 1 101\' gray silty clay

320. Ship samples to core laboratory\--use overnight service.

## DATA RECORDING

See #5 and 8 above

## REFERENCES

1\. American Society for Testing and Materials, 1980, Laboratory
determination of water (moisture) content of soil, rock, and
soil-aggregate mixtures (ASTM-D-2216-80): Philadelphia, Pa., American
Society for Testing and Materials, 8 p.

2\. American Society for Testing and Materials, 1990, Standard test
method for measurement of hydraulic conductivity of saturated porous
materials using a flexible wall permeameter (ASTM-D-5084-90):
Philadelphia, Pa., American Society for Testing and Materials, 8 p.

3\. Driscoll, F. G., 1986, Groundwater and wells: Johnson Filtration
Systems, Inc., St. Paul, Minnesota, ISBN 0-9616456-0-1, 1089 p.

4\. GWPD 2, Ground-water site inventory
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

5\. GWPD 5, Locating a well
(http://water.usgs.gov/usgs/ogw/tech_proc/index.html).

6\. Swanson, R.G., 1981, Establishing a permanent measuring point (from
National GWPD 3). Sample examination manual, Methods in exploration
series: Tulsa, O.K., American Association of Petroleum Geologists,
variously paged.

APPENDIX D: Ground Water Site Inventory (GWSI) Database Management and
Quality Assurance Plan

###### Contents Page

[Introduction 3](#introduction-2)

[2.0 Organization and responsibilities
4](#organization-and-responsibilities-2)

[3.0 Training 7](#training-2)

[4.0 Data processing, review, and entry
8](#data-processing-review-and-entry)

[5.0 Storage and archiving 9](#storage-and-archiving)

[6.0 Appendices 10](#appendices)

[6.1 Required Data Elements for GWSI Form No. 9-1904-A, March 1999
version.
10](#required-data-elements-for-gwsi-form-no.-9-1904-a-may-2003-version.)

[If well site is field-checked or visited:
13](#if-well-site-is-field-checked-or-visited)

[Miscellaneous Visit Data 13](#miscellaneous-visit-data)

[If water-level measurements were performed:
13](#if-water-level-measurements-were-performed)

[Water-Level Data 13](#water-level-data)

[Miscellaneous Remarks 13](#miscellaneous-remarks)

[6.2 Data Review Checklist Followed by Review Personnel Prior to Data
Entry into GWSI.
14](#data-review-checklist-followed-by-review-personnel-prior-to-data-entry-into-gwsi.)

[6.3 GWSI Data Entry Checklist for Data Entry Personnel
15](#gwsi-data-entry-checklist-for-data-entry-personnel)

[7.0 Selected References 17](#selected-references)

# Introduction

The Water Resources Division (WRD) of the U.S. Geological Survey (USGS)
performs a wide variety of ground-water data-collection programs and
investigations to assess the status of the Nation's ground-water
resources. Results of these activities are used to aid the Nation in
develop­ing, managing, and maintaining its ground-water resources.

As the Nation's principle earth-science information agency, the USGS is
depended upon to collect accurate data and produce factual and impartial
interpretive reports. Methods for data collection and analysis that were
developed by the USGS have become standard techniques used by numer­ous
Federal, State, and local agencies and by private enterprises. Data
collected by scientific orga­nizations such as the USGS are being used
increasingly by the public to define and examine a variety of
natural-resource and environmental problems. Many of these problems are
addressed through an open, public process. As a result, scientific
organizations are being challenged to dem­onstrate the credibility of
their data on the basis of objective evidence rather than on the
organiza­tion's history and reputation.

To address these demands and expectations, the WRD has implemented a
program designed to ensure that all scientific work done by or for the
WRD is conducted in accordance with a quality- assurance (QA) program.
The Office of Ground Water (OGW), in coordination with the Branch of
Technical Development and Quality Systems, has the responsibility to
develop, coordinate, and implement the quality-assurance program for
District ground-water activities. As part of that pro­gram, the OGW has
directed the preparation of a Ground-Water Quality Assurance Plan
(GWQAP) which covers all ground-water activities by District offices of
the USGS. USGS Open-File Reports (OFR) 92-136 (Schroder and Shampine,
1992), 92-162 (Shampine and others, 1992), and 97-11 (Brunett and
others, 1997) outline the guidelines for preparing District
quality-assur­ance plans and integrating the quality assurance into
project work plans. The Nebraska Water Science Center GWSI database
management and quality assurance plan presented here is intended to
supplement the Nebraska Water Science Center Ground-Water Quality
Assurance Plan and provide more specific details related to the review,
entry, maintenance, storage, and archiving of ground water data.

This GWSI database management and quality-assurance plan provides formal
procedures for doc­umentation and review of the processing, storage, and
retrieval of ground-water data, including water-levels, water-quality
analyses, and geologic and geophysical logs, by the Nebraska Water
Science Center to assure the management, quality, and reliability of the
District GWSI database. The plan is based upon the following principles:

321. District GWSI database activities will be planned efficiently and
     effectively to provide information needed to evaluate local, State,
     and National water problems.

322. Technical and scientific activities will be performed in accordance
     with applicable WRD practices and policies.

323. GWSI database activities will be performed by technically qualified
     personnel performing at a level commensurate with their training
     and experience.

324. All such activities and projects will receive appropriate and
     timely review for complete­ness, reliability, and credibility.

325. Remedial actions will be taken to correct any observed technical or
     database deficiency.

# 2.0 Organization and responsibilities

Though quality assurance is a personal responsibility of all employees
of the USGS, ultimate quality-assurance responsibility within each
District lies with the District Chief. Clear statements of specific
responsibilities promote an understanding of each person's role in the
overall process of assuring quality and can help to prevent errors and
deficiencies that may otherwise occur. Implementation and follow-up
responsibilities lie with database administrators, data-collection
staff, project chiefs, Investigation Section Chiefs, discipline
specialists, District Chiefs, regional specialists, and others. Even if
quality-assurance responsibilities are ancillary duties for some
employees, these functions are to be documented.

The following is a list of specific responsibilities of District
personnel for implementing the GWSI database management and quality
assurance plan.

The **District Chief** is responsible for:

326. Ensuring the GWSI database activities in the District meet the
     needs of cooperating agen­cies, including state and local agencies,
     the general public, and the Federal Government.

327. Ensuring that all aspects of the GWSI database management and
     quality assurance plan are understood and followed by District
     personnel.

328. Providing final resolution of any conflicts or disputes related to
     GWSI database activities within the District.

329. Keeping District staff briefed on procedural and technical
     communications from Region and Headquarters

330. Ensuring that procedural and technical reviews of all GWSI
     activities are conducted.

331. Ensuring that all data retrievals and other technical
     communications released by the District are accurate and in accord
     with USGS policy.

332. Ensuring that GWSI training is incorporated into each employee's
     training plan, where appropriate.

The **Investigations Section Chief** is responsible for:

333. Managing and directing GWSI database activities assigned to the
     section and ensuring that the stated objectives are met in a timely
     manner.

334. Reviewing the GWSI database management and quality assurance plan
     and alterations made according to USGS and Nebraska Water Science
     Center policies and procedures.

335. Discussing and evaluating, in coordination with the District
     ground-water specialist, the policies and procedures pertaining to
     the data review, entry, and retrieval of the GWSI data­base.

336. Creating, with ground-water personnel in the section, a training
     plan for the GWSI database for each employee, where appropriate.

The **District Ground-Water Specialist** is responsible for:

337. Discussing and evaluating, in coordination with the Investigation
     Section Chief, the policies and proce­dures pertaining to the data
     review, entry, and retrieval of the GWSI database.

338. Reviewing the GWSI database management and quality assurance plan
     and alterations made according to USGS and Nebraska Water Science
     Center policies and procedures.

339. Providing the GWSI database administrator (DBA) with technical and
     administrative sup­port as needed.

340. Participating in the technical review of the GWSI database.

341. Reviewing ground water related projects for the collection of GWSI
     data according to the procedures and policies of the USGS and the
     Nebraska District.

The computer **System Administrator** is responsible for:

342. Directing and conducting the upgrades to the National Water
     Information System (NWIS), including the GWSI database.

343. Ensuring the checkpoint, backup, and optimization of the GWSI
     database and, if necessary, the recovery of the GWSI database.

344. Making available to all personnel the technical information for
     upgrades to the GWSI data­base.

345. Determining and setting access rights of personnel for the GWSI
     database.

The **GWSI Database Administrator** is responsible for:

346. Maintaining data integrity within the GWSI database.

347. Performing or assigning, to appropriately trained personnel, the
     checking of all data entered into the GWSI database, prior to
     entry, according to USGS and Nebraska Water Science Center policies
     and procedures.

348. Performing or assigning, to appropriately trained personnel, the
     entry and/or updating of all data entered into the GWSI database
     according to USGS and Nebraska Water Science Center policies and
     procedures.

349. Performing or assigning, to appropriately trained personnel, the
     retrieval of all data entered into the GWSI database according to
     USGS and Nebraska Water Science Center policies and procedures.

350. Ensuring that hard copies are returned to archives or project files
     upon completion of data checking, entry, and/or update.

351. Informing and discussing with the District ground-water specialist
     any data conflicting with/or altering Nebraska Water Science Center
     policies and procedures for the GWSI database.

352. Performing periodic maintenance checks and updates of data using
     OGW programs.

353. Understanding GWSI database upgrades through information relayed
     from the NWIS pro­gram and discussions with the Nebraska system
     administrator.

354. Training personnel in data checking, entry, updating, and retrieval
     of the GWSI database as assigned by the Investigation Section
     Chief.

355. Informing the Investigation Section Chief of potential necessities
     in training personnel for the GWSI database.

356. Writing and updating the GWSI database management and quality
     assurance plan in accordance with USGS and Nebraska Water Science
     Center policies and procedures.

357. Maintenance of a file and/or notebook documenting all data entry
     and updates within the GWSI database.

358. Discussing with the system administrator and/or the ground-water
     specialist and Investigation Section Chief the determination of
     personnel access rights for the GWSI database.

The **Project Chiefs** for ground water-related projects are responsible
for:

359. The collection and maintenance of ground-water data within project
     files according to USGS and Nebraska Water Science Center policies
     and procedures.

360. Ensuring the completion of appropriate ground-water data forms by
     field or project person­nel, prior to checking and entry of the data
     into the GWSI database, according to USGS and Nebraska Water
     Science Center policies and procedures.

361. Ensuring the proper archiving of ground-water data, upon completion
     of the project, according to USGS and Nebraska Water Science Center
     policies and procedures.

362. Providing the DBA with the data forms and original copy field data
     for checking and entry into the GWSI database.

The **data entry/update personnel** are responsible for:

363. Entering or updating data into the GWSI database according to USGS
     and Nebraska Water Science Center policies and procedures.

364. Data entering personnel will follow the data entry checklist,
     appendix 6.3.

The **data checking personnel** are responsible for:

365. Checking data for the GWSI database according to the data review
     checklist, appendix 6.2.

The **field personnel** are responsible for:

366. The collection of data according to USGS and Nebraska Water Science
     Center policies and procedures.

367. Where possible, completion of form no. 9-1904-A, September 1980
     version, of the required data elements, see appendix 6.1, at the
     field site.

368. Providing the original copy data field notes with the appropriate
     completed GWSI data forms for checking and entry/update into the
     GWSI database.

# 3.0 Training

Employee training is an investment that has short-term and long-term
benefits to District ground- water activities. The immediate benefits
permit confidence that the work is being performed cor­rectly and
accurately. The long-term benefits provide for technically competent
employees that are of great value to the organization. Because all work
in the scientific arena is receiving increased scrutiny, the
qualifications of ground-water personnel relative to the technical
demands of the work to be performed must be well-documented. Training
already received as well as cur­rent and planned training need to be
incorporated into a documented training plan for each employee. periodic
review of these plans by District management will help determine
additional training needs.

The training needs of personnel working with the GWSI database will be
determined by the Investigation Section Chief, in association with
information from the District ground-water specialist, project chiefs,
DBA, and individual personnel. Personnel being reviewed for training
should include: project chiefs, ground-water specialist, DBA, data
checking and entry personnel, and field per­sonnnel. The Investigation
Section Chief will determine, in conjunction with the District Chief,
whether the training will take place outside of the District, inside the
District by external personnel, or inside the District by the DBA or
other appropriate personnel.

# 4.0 Data processing, review, and entry

In general, data are most accessible and useful to the project chief and
other District employees, as well as to those outside the District
office, if they are stored in a computerized database. Stor­age in a
single database also enables interpretations to be more easily verified
and repeated. All water data collected as part of the routine data
collection of the WRD, which are all ground-water data collected by
basic data programs and District projects (OGW Technical Memorandum
93.03), must be stored in computer files of the USGS NWIS. In addition,
"all data collected by others \-- such as cooperators, universities, or
consultants \-- that are used to support published USGS documents and
not published or archived elsewhere, shall be placed in NWIS" (Hubbard,
1992). Exceptions to these requirements are spatial data coverages and
other data for which appropriate database capabilities do not exist in
NWIS.

A quality database is maintained by checking database files against
original data files to ensure accuracy; performing internal cross-checks
of the data in the database to identify anomalous data; and maintaining
the original data in paper or electronic archives to ensure integrity.

A data-management plan describes the procedures used for data
processing, review, storage, and archiving. After ground-water data are
collected, they often are processed using one or more pro­cedures, such
as the application of time or datum corrections, and then are stored in
computerized or physical files. Descriptive information on
data-collection sites, such as well-construction data and location also
should be stored.

The following quality-assurance activities are performed by the
District.

All original data in paper form is placed in project or data-collection
program files in the office where the study originated. Original data in
electronic form is stored in NWIS. All original data is preserved
unmodified as collected or received. Original data are those data \--
from automated data-collection sites, laboratories, outside sources, and
not-automated field observations \-- unmodified as collected or
received, once put into conventional units (engineering units, gener­ally
with a decimal)(Hubbard, 1992).

The original data, after processing, where appropriate, will be coded on
to the correct GWSI form(s), usually form no. 9-1904-A, May 2003
version. The required data elements for comple­tion of this form are in
appendix 6.1. Anyone coding a GWSI form is required to fill in the
"Coded by" element along with the date. If there isn't a location for
the "Coded by" element, the form should be initialed and dated at the
top. When possible, code all of the data on site in the field. When the
form(s) has been completed, the original data and form(s) are passed to
the project chief.

The project chief will review the original data and form(s) according to
the project plan. The project chief and DBA will determine the
appropriate time frame for data review and entry. The forms, along with
the original data, when appropriate, will be passed to the DBA.

The forms will be reviewed by the DBA, or assigned to trained checking
personnel, according to the review checklist, appendix 6.2. After the
data has been reviewed and approved, data entry into the GWSI can
proceed. Data entry will be performed by the DBA or assigned to trained
entry per­sonnel. Entry will proceed according to the data entry
checklist, appendix 6.3. Data is reviewed promptly after any
data-processing procedure is completed to ensure that the procedure was
cor­rectly applied and that the results are consistent both internally to
the data set and with other data for the same site. This review is
performed prior to publication or other dissemination to the gen­eral
public and prior to the technical review of publications that contain
the data or that use the data in interpretations.

Periodically, the DBA will perform internal checks of ground-water data
in the GWSI database. These data checks will identify anomalous sites
where data might be in error. These sites will be reviewed by the DBA
and discussed with the ground-water specialist and appropriate project
chiefs. After a corrective action has been determined the GWSI database
will be updated accord­ingly.

Records of all GWSI database entry, updates, and upgrades should be
maintained in a file and/or record book. This record book/file will be
maintained by the GWSI DBA and contain dated records of sites entered,
updated, and upgrades performed. Evidence and reasoning leading to
updates of previously entered data will be recorded in this book/file.
This record book/file will provide a hard copy record for quality
assurance of data entered into the GWSI database.

# 5.0 Storage and archiving

At the conclusion of a project, the paper file for each data-collection
site will be stored in the Dis­trict ground-water files. The District
ground-water files are divided into three areas; well files, log files,
and aquifer test files. Well files containing GWSI forms, driller's
logs, water quality analy­ses, water-level measurements, and maps will be
stored in the District well files. These files are stored by county and
station name (or local well id, determined from township and range,
section, and quarter-quarter-quarter location with sequence number) in
alphanumeric order. Logs are stored in the logs file. Logs are stored in
an envelope or file, labeled with county, station name (local well id),
date of logs, and type of logs. Log files are stored by county and
station name. Aquifer test data (pump test data) are stored after
approval by the Regional Hydrologist and com­pletion of the project.
Aquifer test files will be labeled by county and station name of the
pumping well. The minimum data the files should include are the results,
the pumping well station name, the observation wells station names, the
dates of the aquifer test, and the participants. The aquifer test files
will be stored by county and station name.

Archiving is the final step in the processes of data collection,
analysis, and interpretation. Although the report represents the summary
of the current work, the data and its interpretation should be available
for further analysis.

**Archiving** is the systematic process of storing data and information
to protect it from change or loss, by providing the necessary security.

**Electronic archiving** is the systematic process of removing data from
active, on-line computer storage and preserving it with the capability
to recover the data.

To assure the quality of the archiving process, the following steps
shall be performed by the District:

369. All data shall be archived as specified by current WRD policy.

370. All model related computer files and appropriate simulation results
     shall be archived as out­lined in OGW Technical Memorandum 93.01.

371. All aquifer-test data and results shall be archived as outlined in
     OGW Technical Memoran­dum 94.02

372. The District archiving plan will be established that will document
     the disposition of all project information upon completion of
     District projects. The archiving plan will document the archiving
     process and the responsibilities of personnel assigned to archiving
     tasks. The dispo­sition of technical-procedure documents and
     procedures notebooks developed for an individ­ual project should be
     described in the archiving plan.

# 6.0 Appendices

## 6.1 Required Data Elements for GWSI Form No. 9-1904-A, May 2003 version.

A listing of data elements, required by the Nebraska District, to be
collected or determined by field personnel in completing the minimum
necessary for establishing a well site in GWSI using the form no.
9-1904-A, revised March 1999. For convenience while filling out the
form, the ele­ments will be listed in the order of the form.

**Coded by**\--This is required. The personnel recording the field data
should be recording the data on the GWSI form by First, Middle Initial,
and Last Name.

**File Code**\--This is equivalent to the Station Name, C12; township
and range, section, quarter- quarter-quarter, and sequence number.

**Date**\--The date that the initial data is collected in the field or
from another source.

**C4-Agency Code**-Agency who collected the original data.

**C1-Site Id**\--15 digit number determined from the latitude,
longitude, and sequence number. If the latitude and longitude are
determined using a Global Positioning System (GPS) that is accu­rate to
tenths or hundreths of a second, the site id is determined by rounding
the latitude and lon­gitude to the nearest whole second.

**C5-Project**\--The nine digit project number. This number will
generally begin with 4631 fol­lowed by the five digit project code. Fill
in the complete nine digit code.

**C12-Station Name**\-- District policy, determined by the ground-water
specialist, is that the station name will be the township and range,
section number, quarter-quarter-quarter-quarter, and sequence num­ber
(with specific spaces noted by '\_' below). This location will be
determined by plotting the location from latitude and longitude or field
map on a 7.5' 1:24,000 quadrangle map. Example: the well is plotted on
the map at township 12 north, range 9 west, section 5, the northeast
quarter of the northeast quarter of the southwest quarter of the
southeast quar­ter, and is the only well in that quarter. This results in
a station name of \_12N_09W05DCAA1. This is NOT the data element for
project names or designations. Specific project names and designations
belong in element c190, Other Id.

**C9-Latitude**\--Determined in field with GPS unit. If GPS unit is
unavailable, latitude will be determined from a 7.5' 1:24,000 quadrangle
map.

**C10-Longitude**\--Determined in field with GPS unit. If GPS unit is
unavailable, longitude will be determined from a 7.5' 1:24,000
quadrangle map.

**C11-Lat-Long Accuracy**\--Accuracy of method determining latitude and
longitude.

**C35-Lat/Long Method**\--Method of determining latitude and longitude.

**C36-Lat/Long Datum**\--Determined by the method used for latitude and
longitude.

**C6--District**\--Nebraska Water Science Center is 31.

**C7-State**\--Nebraska State code is 31. If the well is not within the
Nebraska State borders, the state code is that in which the well is in,
not the state recording the data.

**County or Town**-Generally this is used for county.

**C8-County Code**\--Three digit county code, for Nebraska 001 to 185.
Other states will have dif­ferent county codes.

**C13-Land Net**\--This is the township and range, section number, and
quarter-quarter-quarter. This location will be determined by plotting
the location from latitude and longitude or field map on a 7.5' 1:24,000
quadrangle map. Example: the well is plotted on the map at township 12
north, range 9 west, section 5, the northeast quarter of the southwest
quarter of the southeast quarter; the land net is NESWSE S05 T12N R09W.

**C14-Map Location**\--Name of map, including state, that well is
located on to get latitude, lon­gitude, etc\...., District preference is
use of 7.5' 1:24,000 quadrangle map.

**C15-Map Scale**\--7.5' 1:24,000 quadrangle map is indicated by
assuming the 1: portion, writing only the remaining scale number, 24000.
A scale of 1:62,500 is recorded as 62500.

**C16-Altitude**\--Generally taken from a 7.5' 1:24,000 quadrangle map.
Other methods are avail­able.

**C18-Altitude Accuracy**\--Should be based on half the contour line
interval for a map.Other meth­ods will vary.

**C17-Altitude Method**\--How altitude is determined.

**C22-Altitude Datum**\--Dependent on method. Explanatory on form.

**C711-Date Inventoried**\--Date data for well was recorded, MMDDYYYY.

**C802-Station Type**\--For a well, a Y in the sixth position,
\_\_\_\_\_Y\_\_\_\_\_, a spring is in the fifth position.

**C804-Data Type**\--Place proper code in corresponding location .

**C39-National Water**\--Use code-Select appropriate two letter code
from bottom of form.

**C813-GMT Offset**\--In Nebraska, always equal to -6.

**C814-Local Standard Time Flag**\--Yes, equals Y.

**C32-Web-Ready Flag**\--Always P prior to data entry. Actually setting
will be determined later through discussion by project chief, District
ground-water specialist, and DBA.

**C3-Data Reliability**\--Method for delineating the quality of the
data.

**C2-Site Type**\--Explanatory on form.

**C714-Primary Aquifer**\--Determined upon return from field. Well depth
and altitude required. May need to consult publications or ground-water
specialist.

**C28-Well Depth**\--Necessary for primary aquifer code. If well depth
measured, type of pump should be noted.

**C29-Source of Depth Data**\--Explanatory on form.

**Field Map**\--Last page on form. Field map should be drawn from map in
field book or updated as necessary.

### If well site is field-checked or visited:

#### Miscellaneous Visit Data

**C187-Date of Visit**\--Date site was visited and data collected.

**C188-Name of Person**\--Name of person collecting data for site visit.

### If water-level measurements were performed:

#### Water-Level Data

**C235-Date Water Level Measured**\--MMDDYYYY

**C709-Time**\--Time of water level measurement.

**C237-Water Level**\--Water level measurement from Land Surface Datum
(LSD) to ground water surface.

**C239-Method of Water**\--Level Measurement-Explanatory on form.

**C244-Source of Water**\--Level Data-Explanatory on form.

Construction Measurement Point Data

**C323-M.P. Height**\--Measurement of measurement point height from LSD.

**C324-M.P. Remarks**\--Description of measurement point.

### Miscellaneous Remarks

**C184-Date of Remarks**\--Date of water-level measurement, MMDDYYYY.

**C185-Remarks**\--Description of pumping status at water-level
measurement time. Specifically note the time pump has been off or if
pump was off upon arrival on site.

## 6.2 Data Review Checklist Followed by Review Personnel Prior to Data Entry into GWSI.

373. 'Coded by', 'file code', and 'date' elements at top of form no
     9-1904-A, should have appropri­ate entries.

374. 'Checked by' element is presently entered with name of person
     performing review. If no place is preprinted for name, write
     'checked by' on top of page and date and initial.

375. Latitude (C9) and longitude (C10) should be entered from GPS or map
     location. The following elements are required to be filled from the
     latitude and longitude.

```{=html}
<!-- -->
```
e.  Site Id (C1)

f.  Station Name (C12) - Township and Range location

g.  Lat - Long Accuracy (C11)

h.  Lat/Long Method (C35)

i.  Lat/Long Datum (C36)

j.  Land Net (C13)

k.  Location Map (C14)

l.  Map Scale (C15)

m.  Altitude (C16)

n.  Altitude Accuracy (C18)

o.  Altitude Method (C17)

p.  Altitude Datum (C22)

```{=html}
<!-- -->
```
376. Check GWSI for uniqueness of:

```{=html}
<!-- -->
```
q.  Site Id number and sequence number

r.  Station Name and sequence number from township and range location

These two elements should be checked against well sites currently
entered into the GWSI data­base. If the Site Id element matches a site
already entered, the new well must be checked for a duplicate site.
Elements that will help determine duplicity are as follows: latitude,
longitude, alti­tude, well depth, aquifer code, construction date, and
owner name and date. Previous wells entered into GWSI may have errors in
the location. Review nearby wells for possible matching wells with
different Site Ids.

If a well is determined to match a well already entered into the
database, the site will need to be updated. Check hard copy well files
for that well site. Check that the agency code (C4) on the form matches
the site already in the database. If it does not match, correct the form
to match the site already entered. If well file exists, mark new
materials for updating. When review is com­pleted, new material is given
the Site Id from the previous material and inserted into well file and
relayed for updating.

If the Site Id does match a previous well and is not the same well as
within the database, the two-digit sequence number will need to be
increased to the next available number. A new well file is created and
marked for entry.

The station name might match a previously entered well. If there is a
matching station name, determine if the wells are matching or differing.
If the wells match, locate the well file, insert new material, and mark
for updating. If the wells do not match, the sequence number is
increased to the next unused sequence number for that quarter of the
section. A new well file is created and marked for entry.

If there isn't any matching well for either the Site Id or the Station
Name a new well file is cre­ated and marked for entry.

377. Check for entry of the elements GMT Offset (C813) = -6, Local
     Standard Time Flag (C814) = Y, and Web-Ready Flag (C32) = P.

378. Check well depth is less than or equal to hole depth. If well depth
     and altitude are available, check for primary aquifer (C714).

379. Check water level (C237) is not greater than well depth.

380. Under construction data, check casing and screen depths and
     diameters are not greater than the well depth, hole depth, or hole
     diameter.

381. If field measurement is made, check for miscellaneous visit data.

382. If water-level measurement is made, check for remark (C185)
     referring to the length of time pump was turned off.

383. Check for map on last page of GWSI sheet. Map should contain a
     north arrow, road names, distances, and a well-marked well
     location.

384. For wells new to GWSI, write 'New' at top of the first page of the
     GWSI form. For wells already in GWSI, write 'Update' at top of the
     page of the GWSI form. Photocopy first and last page, duplex form,
     and map if separate, of GWSI form for insertion into county wells
     field files.

385. If there are any difficulties or problems with data on the GWSI
     form, the form is to be returned to the field personnel and/or
     project for correction.

## 6.3 GWSI Data Entry Checklist for Data Entry Personnel

386. Check that each site of data has been reviewed by noting the name
     or date and initials at the 'check by' element on the front page.

387. Each well site data set to be entered should be labeled as 'new',
     'update', or have a water-level measurement for entry.

388. Enter GWSI; select Screen Entry. The District DBA suggests
     preferential use of the screen entry over the query entry unless
     the entry personnel are approved by DBA for query entry screen.

389. Enter the agency code (C4) and Site Id (C1). The screen should ask
     if this is a new site or state that it matches a previously entered
     site. This should match new written at the top of the form or
     update or water level written on the form. If it does not
     correlate, check entry of agency code and site id. If agency code
     and site id are correct abort this site and return to reviewer to
     have it rechecked. If it does correlate, continue with entry.

390. If GWSI entry will not accept an entry for a data element, check
     for error in data entered. If data entered matches data supplied on
     form, abort this site, note problem, and return to reviewer for
     recheck.

391. When individual well site entry is complete, return to step 4 and
     continue with next site.

392. When all well data is entered, exit Screen Entry program.

393. Run Edit GW Data program in GWSI for entry file created during
     entry. This program will check entry file for errors in entries.

394. Check error file created in Edit GW Data program. If error
     statement, correct accordingly in entry file. If unable to
     determine error, contact DBA for assistance. When file has been
     corrected return to step 8 and rerun Edit GW Data program. If no
     errors are shown, continue.

395. Run Update GW Data program in GWSI.

396. When Update GW Data is complete, retrieve data through GWSI GW
     Retrieval and check for errors.

397. Correct any errors. Retrieve data again and return files and
     retrieval printout to DBA for review.

# 7.0 Selected References

Brunett and others, 1997, Office of Ground Water, A Quality-Assurance
Plan for District Ground-Water Activities of the USGS: U.S. Geological
Survey, Open File Report 97-11, GWPD 5.

Hubbard, E. F., compiler, 1992, Policy Recommendations for Management
and Retention of Hydrologic Data of the U.S. Geological Survey: U.S.
Geological Survey Open-File Report 92-56, 32 p.

Martin, J.D., and Cohen, D.A., 1994, Policy and Procedures for the
Management and Archival Storage of Data Collected for Hydrologic
Investigations of the U.S. Geological Survey, Indiana District: U.S.
Geological Survey Open-File Report 94-61, 36 p.

Schroder, L.J., and Shampine, W.J., 1992, Guidelines for Preparing a
Quality Assurance Plan for District Offices of the U.S. Geological
Survey: U.S. Geological Survey Open-File Report 92-136, 14 p.

Shampine, W.J., Pope, L.M., and Koterba, M.T., 1992, Integrating Quality
Assurance in Project Work Plans of the U.S. Geological Survey: U.S.
Geological Survey Open-File Report 92-162, 12 p.

U.S. Geological Survey, 1981, Hydrologist's Guide to Records Safety:
U.S. Government Printing Office, p. 19.

\_\_\_\_\_ 1989, National Water Information System User's Manual, v. 2,
chap. 4. Ground- Water Site Inventory System: U.S. Geological Survey
Open-File Report 89-587.

\_\_\_\_\_ 1992, Programs and Plans \-- Establishment of a National
Policy to Archive Ground-Water Flow and Transport Models: Office of
Ground Water Technical Memorandum 93.01, 3 p.

\_\_\_\_\_ 1994, Guidance for the Preparation, Approval, and Archiving
of Aquifer-Test Results: Office of Ground Water Technical Memorandum
94.02, 3 p.

APPENDIX E: NEBRASKA WATER SCIENCE CENTER PROCEDURE FOR TEMPORARY AND
PERMANENT STORAGE OF FLOW, TRANSPORT, ENERGY-BALANCE, AND SALT-BALANCE
MODELS

###### Contents

[Introduction 3](#introduction-3)

[The Archiving Process - How, What, When?
3](#the-archiving-process---how-what-when)

[Temporary Storage 3](#temporary-storage)

[Permanent District On-Line Storage
3](#permanent-district-on-line-storage)

[Example of the Temporary Archive Structure for a Flow Model
3](#example-of-the-temporary-archive-structure-for-a-flow-model)

[Backup Storage 4](#backup-storage)

[Archiving Pre-1993 Models 4](#archiving-pre-1993-models)

[Updates of Older Models 4](#updates-of-older-models)

[Detailed Structure of the Archive
4](#detailed-structure-of-the-archive)

[Naming the Directory and Subdirectories for Permanent Archive
5](#naming-the-directory-and-subdirectories-for-permanent-archive)

[Who will do the archiving and subsequently provide copies on request?
9](#who-will-do-the-archiving-and-subsequently-provide-copies-on-request)

[Authors\'/Modelers\' Responsibility 9](#authorsmodelers-responsibility)

[Supervisors\' Responsibility 9](#supervisors-responsibility)

[Database Unit Responsibility 10](#database-unit-responsibility)

[Computer Unit Responsibility 10](#computer-unit-responsibility)

###### 

# Introduction

As of October 1993 all ground-water flow, solute transport, and other
models were permanently stored in District computer archives (Office of
Ground Water (OGW) Memorandum 93.01). As of April 2000 an update to the
1993 policy, Office of Ground

Water (OGW) Memorandum 00.02, requires that all models developed after
October 1993 be stored in an on-line archive, which is routinely backed
up. The purpose for creating and maintaining this archive is to make
available the results and the means for recreating simulations of
hydrologic systems documented in our published reports. Establishment of
these archives will greatly ease the task of finding and updating past
models, and retrieving model input when requested to do so by the
public.

# The Archiving Process - How, What, When?

## Temporary Storage

When a report is submitted to your supervisor at the beginning the
review process, the model documented in that report should be placed in
temporary on-line storage on the Nebraska District\'s server. The
temporary storage of the model provides reviewers the opportunity to
look at model input and output as they review the report documenting the
model. The author(s) of the report may need to update what is stored in
these temporary archives if the model is altered as a result of
resolving reviewer\'s comments on the report. If this happens, the
easiest procedure would be to delete what is currently stored in the
archive directory and replace it with the corrected versions of the
model files. The model that is archived when the report is submitted for
supervisory review should parallel that version of the report. The model
archived when the report is submitted for colleague or Regional review
also should parallel the documentation in those versions of the report.
If no changes are made to the model during review, the temporarily
stored model will not need updating.

## Permanent District On-Line Storage

After the report has undergone sufficient review to be approved by the
Regional Hydrologist and after the model has been altered for the final
time, and depending on the availability of appropriate computer
hardware, it will be placed in permanent on-line archive on a District
server. The model will remain in this on-line storage in perpetuity. The
permanent storage should not be initiated until all post-approval
changes have been made to the report and the model.

### Example of the Temporary Archive Structure for a Flow Model

The structure of the permanent on-line archive will be similar to that
of the temporary archive except for three changes--(1) The main archive
directory will be named GMARCHIVE; (2) subdirectories under this main
directory will be named for the report where the model is documented.
(3) the Contents subdirectory in the temporary storage will be pulled
out and additional files will be created. An example of the permanent
archive structure is illustrated below.

The files in the redone CONTENTS subdirectory and what they show is
listed in the following table:

File Name

What is in the file?

Reference

The full bibliographic reference of the report documenting the model.

Gloss

Description of the subdirectory structure and of the files contained in
each

subdirectory.

Format

Descriptions of the data-file formats--i.e. Ibound-56I2, Ending
heads-UNFORMATTED, Hcond-56F6.2, etc.

Sequence

List the sequence of model runs--Steady-state baseline, Steady-state

Alternative 1, Steady-State sensitivity runs, Transient run 1950-98,
etc.

Instruct

Explain how to run the simulations described.

### Backup Storage

Backup storage will be the routine system backups done by the Computer
Unit.

### Archiving Pre-1993 Models

Models from Nebraska projects completed and approved prior to FY93 will
be archived when resources are available to do so. Priority for
archiving will be determined by public demand and the time constraints
and/or availability of the author(s) or an appropriate substitute.

### Updates of Older Models

If a model of an area is updated, that update will be archived as a
separate model while retaining the original older model of the same
area. The read_me file of the update will indicate that there exists an
older version of a model for the same area and a reference to the older
report will be given. The disks of the old and the updated models should
be filed adjacent to one another.

### Detailed Structure of the Archive

The details of the structure of an archived model are shown in the
outline below. This follows the structure suggested in Attachment 2 of
OGW memo 93.01 and update memo 00.02. A separate set of subdirectories
and files should be created for each model presented in the same report
(not shown in outline). This would mean that an extra layer of
subdirectory naming would be inserted under the report# directory. The
second level of subdirectories should reflect the type of model used.
For example if a single report includes a flow and transport model, then
appropriate naming of the second-level subdirectories would be GWFLOW
and GWTRANSPORT.

### Naming the Directory and Subdirectories for Permanent Archive

Subdirectories should be the standard names suggested by the Office of
Ground Water regardless of whether the archive is temporary or
permanent. These suggested names are: Contents, Source, Input, Output,
and Ancillary. As previously stated, these subdirectories will reside
under the same directory in the Temporary archive, but under the
Permanent archive Contents will be supplemented and will be one level
higher in the structure than the others (Source, Input, Output, &
Ancillary), which will be under the Model Data subdirectory. Use your
own judgment when naming lower-level subdirectories and files.

Make them short and clearly understandable by anyone. Try to use the
same terminology that a reader would find in your report documenting the
model. The attached outline provides an example.

Contents of files and subdirectories

/GMARCHIVE/\[report#\]/contents/ (subdirectory 1)

Directory should contain five files:

398. /\[report#\]/contents/reference (file)

Complete bibliographic reference for the report that documents the model

399. /\[report#\]/contents/gloss (file)

Outline of directories and files in the archive. Should resemble a table
of contents without the page numbers. Example:

Subdirectory 1

Subdirectory A

File 1

File 2

Subdirectory B

File 1

File 2

400. /\[report#\]/contents/format (file)

List of data file formats. Example-

IBND --- 40I2

STRT --- 10F8.2

head.ss - UNFORMATTED

401. /\[report#\]/contents/sequence (file)

Sequence of model runs documented. Example:

1.Steady-state baseline

2.Steady-state alternative 1

3.Steady-state alternative 2

4.Steady-state sensitivity to hydraulic conductivity of layer 1

5.Transient period 1950-98

402. /\[report#\]/contents/instruct (file)

The run instructions for the models in the archive. This should include
reference to the point in the file structure from where the model should
be run, and to where in the structure the model output is ported.
Third-party software required to run the model should be listed.

/GMARCHIVE/\[report#\]/model_data/ (subdirectory 2)

Directory should contain four subdirectories if a ground-water-flow
model is being archived. Other types of models such as salt balance,
energy balance, or solute transport may require a slightly different
subdirectory structure. The structure outlined below is for a
ground-water-flow model.

403. /\[report#\]/model_data/source/ (subdirectory A)

Subdirectory should contain a compiled and an uncompiled version of the
model code used in running the simulations. If third-party software was
used the file compatible with opening that application should be
included.

404. /\[report#\]/model_data/input/ (subdirectory B)

Subdirectory should contain subdirectories holding for each
steady-state, transient-state, and projection simulation presented in
the report. Also should contain a data subdirectory that contains all
input data common to all model simulations:

5.  /\[model_data\]/input/steady/ (subdirectory i)

Separate subdirectory under this directory for each steady-state
simulation presented in the report. Naming convention should be
\[report#\]/input/steady/ss \[yr\]

\- Each subdirectory must contain all input files required to run the
steady-state model.

\- The shell script to run the steady-state model. The shell is included
so USGS reviewers can easily run the model.

The shell will not be part of the permanent archive.

6.  /\[model_data\]/input/trans/ (subdirectory ii)

Separate subdirectory under this directory for each transient-state
simulation presented in the report. Naming convention should be
\[report#\]/input/trans/tr \[period\].

\- Each subdirectory must contain all input files required to run the
specific model.

\- The shell script to run the transient-state model. The shell is
included so USGS reviewers can easily run the model. The shell will not
be part of the permanent archive.

7.  /\[model_data\]/input/project/ (subdirectory iii)

Separate subdirectory under this directory for each projection
simulation presented in the report. Naming convention should be
\[report#\]/input/steady/proj \[#\]

\- Each subdirectory must contain all input files required to run the
specific model.

\- The shell script to run the projections. The shell is included so
USGS reviewers can easily run the model. The shell will not be part of
the permanent archive.

8.  /\[model_data\]/input/data/ (subdirectory iv)

Directory with all data files that are common to both steady-state and
transient-state simulations. Possible examples for MODFLOW simulations
would be the arrays defining hydrologic properties (except storage),
geometry of the system, or fixed recharge and discharge quantities,
boundary delineations, top and bottom of layers, transmissivity,
vertical conductance, hydraulic conductivity, areal recharge,
evapotranspiration, drain and river conductances, etc. A data
subdirectory is included in the archive to save memory space.

\[report#\]/model_data/output/ (subdirectory C)

Directory should contain output files for each of the model simulations
described in the report and saved in the INPUT subdirectory. Appropriate
subdirectories should be created if more than one steady-state or
transient-state simulation is present. A project directory similar to
that used in the INPUT subdirectory may also be needed:

The output file should be ASCII and contain the volumetric budget and
heads for the end of each stress period.

Heads should be printed for each layer. Output files are required so
that future model users can check their outputs against the original
outputs and verify that the model is running correctly. Output files
should be created in the archive directory by running the model with the
archive information. This is a check to determine if all information
necessary to run the model is in the archive.

\[report#\]/model_data/ancillary/ (subdirectory D)

Directory should contain files of other information required to run the
model:

Only files of source and object codes of programs required to run the
model are archived. If specific areas or zones are referenced in the
report, then ZONEBUD source, object, and input files delineating the
zones should be included. Object code is included during the temporary
storage stage and will no be part of the permanent archive.

Ancillary directory should contain material and programs, not including
the model, that are needed to recreate specific model information
presented in the report. All files in the ancillary directory must be
completely identified in the \[report#\]/contents/gloss file.
Explanation of programs and input files are not required if the programs
are referenced in the \[report#\]/read-me file.

# Who will do the archiving and subsequently provide copies on request?

## Authors\'/Modelers\' Responsibility

The final responsibility for archiving a model is ultimately that of the
author of that model (much the same as writing and getting a report
published is the responsibility of the author). Just as authors receive
help from reviewers, technical editors, and illustrators, modelers will
receive help with archiving from their supervisor and personnel in the
Computer Unit. When a report is completed and, in the author\'s opinion,
ready for supervisory review, the model should also be ready for review.
The modeler should first clean up the directories where the model files
reside. This means that all files in that directory that are not
directly related to running the model should be moved elsewhere or
deleted. The modeler should create a directory and file structure like
that shown in the example under Detail Structure of the Archive. Use
**mkdir** to create the appropriate subdirectories named **Contents,
Source, Input, Output,** and **Ancillary**. Create the **read_me**
**file** in the top-level directory. Create the **Run_Instructions** and
**File_Structure** files within the **Contents** subdirectory. Move
model files, source codes, and other necessary files into the
appropriate subdirectories. You do not need to copy the source code you
used into the Source subdirectory until your report is ready for
colleague review.

After the author has created the appropriate structure of directories,
subdirectories, and files, the entire model subdirectory can be moved
(mv) or copied (cp) to the temporary archive area on the server. The
author now has the responsibility of updating these files during the
review and approval process if changes to the model are made as a result
of the review.

Authors should assure that all pathnames to allow access to the model
are given to the reviewers in the transmittal letter for the manuscript
being reviewed. When the report is approved at Region and the author
deems the model is in its final form, the Site Administrator should be
informed and asked that the model be copied to permanent on-line storage
and deleted from temporary on-line storage.

## Supervisors\' Responsibility

The supervisor\'s responsibility is to look at the model file structure
created by the author to determine if all the necessary files are
present, and to assure that subsequent reviewers will be able to easily
understand how the model can be run. Supervisors should also confirm
with the author(s) that the model is complete before the model files are
put into permanent archive.

## Database Unit Responsibility

The Database Unit will have the responsibility of handling future
requests for the model from the public. Database Unit personnel should
know how the permanent archive library is structured, where the library
resides, and how to make the requested copies of the model. Database
Unit personnel should be able inform a requester of the type of media
the District can provide and what the associated cost for producing that
media will be.

## Computer Unit Responsibility

The Computer Unit has the responsibility of maintaining the temporary
and permanent on-line storage space (approximately 750,000 blocks) on
the District\'s servers, and for creating and maintaining routine
backups as part of the District-wide backups created.