Region Viii Sedm Conference : April 16-18, 1991, Denver, Colorado.


ion Vlil SEDM Conference
April 16-18, 1991
Denver, Colorado
SEDM: Making sure the right hand knows
what the left hand is doing...

-------
Table of Contents
Ready IndexiM
AVERY Indexing System
1
INTRODUCTION
2
OVERVIEW
3
STATE
UPDATES
4
NATIONAL
DIRECTIONS
5
PROGRAM
UPDATES
6
TECHNOLOGY
TRANSFER
7
STRATEGIC
PLAN
8
CONCLUSION
9
CONFERENCE
HIGHLIGHTS
10
CONFERENCE
NOTES

-------

-------
State/EPA Data Management Program
Region VIII Overview
03/11/91
NORTH	SOUTH
COLORADO MONTANA	DAKOTA DAKOTA	UTAH	WYOMING
Connectivity
to NCC
X
X
X
. Intrastate
JY connection
' not in place
X
y Only Air
Ar Quality
' Division
Training
PCS —April *91
RCRIS—April '91
PCS —April'91
RCRIS—April '91
PCS —April'91
RCRIS—April '91
PCS —April'91
RCRIS—April '91
PCS —April '91
RCRIS—April '91
PCS —April '91
RCRIS—April '91
AIRS-AQ
X

X
t X

X
AFS
(Compliance)
1 Wi
jffn
X

X

I

AFS
(Emissions)
@/
©/
@/
No si
ibmissions since
1985
FRDS

X
::j:; Conversion to
FRDS II complete.
i V Will iransmii
when NCC line is
f fully implemented.
Conversion to
FRDS II complete.

X

GICS*
Af SRF Tracking
System April "91
X
X
X
X

11

HWDMS/
RCRIS
: &JT Test Mode in.
fy . 2nd Quarter FY 91
Conversion in--.
/f 2nd Quarter FY 91
. jfUr Test Mode in
Vjj> 2nd Quarter FY 91
[0
; SI
x
PCS

X
Industrial l/
t * Municipal
X
X

6F
—i

STORET
~
XIX
X
. @/

i
6


xzxmsaaai&ar-msjnraHBKH?






Data Integration
Projects
Rocky Flats,
Kleros, and Sand
Creek systems in
: progress
Clark Fork GIS
in progress at
State Library
LIMS Study


"
IIMS customization
in progress

Equipment
Funding provided
for Kleros'
terminals, etc.

!
|
i
Prime 2755 and
modems (Jan '91)
j Upgrade to Prime
4050 (Feb.'90)
Prime from the
WIC
IRMA boards and
modems to connect
to NCC
Planning
CDH long-range
information
strategy developed



Began 5-year
ADP Plan
(Feb.'90)

Implementation
Plans & MOUs
Impl. Plan • Final
MOU - Draft in
progress
Impl. Plan - Final
MOU - Draft in
progress
Impl. Plan - Final
MOU - Draft in
progress
Impl. Plan - Final
MOU - Draft in
progress
Impl. Plan - Final
MOU - Draft in
progress
Impl. Plan - Final
MOU - Draft in
progress
* Direct Trtzv mixi ion	Q * Diskcoe Trimfe*	MipiclicTapc Transfer	¦ Piper Transfer	¦ Not Delefiilcd
* Slate Optional System is available, but not in use by Region VIII States.
Headquarters is developing a national SRF tracking system.

-------
03/11/91
State/EPA Data Management Program
Region VIII Overview of Deliverables
SEDM	SEDM
SEDM Research Daia Needs Needs Analysis and Options Implementation ADP Strategic	Status
Report	Assessment System Concept Analysis	Plans	Plans	News Bulletins Briefings
EPA
REGION VIII
Decenmcr, May,
and November
Reviewed
COLORADO
Harvard
Rocky Flats
Rocky Flats
MONTANA
W LIMS
LI MS
NORTH
DAKOTA
SOUTH
DAKOTA
UTAH
LAN
WYOMING

= DRAFT
= FINAL

-------
State/] Data Management Program §
Region V	la Quality Worksheet
NORTH	SOUTH
COLORADO	MONTANA	DAKOTA	DAKOTA	UTAH	WYOMING
Completeness
State Goal:
EPA Requirement:
Mclhod of Assessing
Completeness
(e.g., ft of sites, U offlags, etc.)
Known Problems/Commenls






p .' (Excellent, Good, Fair,
S Poor, Not Applicable)






Accuracy
Stale Goal:
EPA Requirement:
Mclhod of Assessing
Accuracy
(e.g., known method of
collection, known QAIQC
procedures, etc.)
Known Problems/Comments






P .. (Excellent, Good, Fair,
Kal,n8 Poor. Not Applicable)






Timeliness
Slalc Goal:
EPA Requirement:
Mclhod of Assessing
Timeliness
(e.g., date of last update,
average frequency of
updates, etc.)
Known Probicms/Commcnts
¦ ' '





Ralino {Excellent. Good, Fair,
® Poor, Hot Applicable)






Overall (Excellent, Good, Fair,
Rating Poor. Not Applicable)





i
.
Completed By:
Agency:	
Phone W:

-------
03/08/91
State/EPA Data Management Program
Region VIII Overview of Data Quality
COLORADO
MONTANA
NORTH
DAKOTA
SOUTH
DAKOTA
UTAH
WYOMING
HWDMS/
RCRIS
AFS	AFS
A1RS-AQ (Compliance) (Emissions)
FRDS
STORET
^Evaluation
by KPA
State
Evaluation^
Ratings Categories:
A = Excellent
B = Good
C = Fair
D = Poor
N/A = Not Applicable

-------
Region VIII
State/EPA Data Management Program
1989 National Conference
Breakout Session
KEY TOPICS:
• Ongoing training for data managers, program managers, and ADP staff is a continuing
need in the states.
• Region Vm, with the cooperation of the states, needs to review existing databases and data
elements to determine how and why data is used. The assumption is that more data is
collected from the States than is necessary. Region VIII will first observe a similar effort
underway in Region X before embarking on its own program to remove unused data.
• All states have received or are planning to receive technical assistance from EPA Region
VIE through the State/EPA Data Management (SEDM) Program. The states approve of
continuing this assistance through Phase II: Data Integration.
• EPA, both its Region VIII office and Headquarters, must improve communications and
coordination with the states to inform them of developing data, software, and hardware
standards, fiscal trends, and impending program regulations within the Agency. Without
this information, the states cannot set and adhere to long-term ADP strategies.
• All states agreed that a formal long-term (three- to five-year) ADP plan is needed. EPA will
provide contractor assistance to accomplish the development of the plans and the setting of
priorities.
• To help develop and implement an ADP plan and to improve coordination with EPA
management and EPA and State program staff, State managers need to create an IRM
(information resources management) steering committee. Such committees are in existence
within EPA and have been very successful.
• EPA wishes to continue its role as a "convenor '' of meetings such as this national SEDM
conference to air concerns and share information.
• Each state should begin to identify data integration projects, such as GIS applications,
expert systems, or integrated facilities management systems, so that EPA can determine
what resources it can provide under Phase II of the SEDM Program.
ACTION ITEMS:
• EPA will distribute a newsletter in eariy December which will describe conference events.
• EPA will continue the data needs assessments and options analyses (including those for the
Rocky Flats Program Unit) according to schedule.
• EPA will begin planning a regional SEDM conference for next spring.

-------
MEMORANDUM OF UNDERSTANDING
BETWEEN
U.S. ENVIRONMENTAL PROTECTION AGENCY
AND
[STATE ENVIRONMENTAL AGENCY]
(DRAFT)
STATE/EPA DATA MANAGEMENT PROGRAM
During 1988 and 1989, the U.S. EPA and [STATE ENVIRONMENTAL AGENCY]
conducted a data needs assessment which focused on the utilization of both Federal and State
information management resources in a cost effective, efficient, and coordinated manner. Earlier
pilot programs have demonstrated that it is possible to combine both sets of resources in such a
manner that data quality is assured, productivity and efficiency benefits accrue to both
organizations, and that more timely production of data for environmental decision making occurs.
In order to convert the status of the State/EPA Data Management Program from a theoretical
to operational mode, it is necessary to further clarify the roles and responsibilities of EPA and
[STATE ENVIRONMENTAL AGENCY] by this Memorandum of Understanding (MOU) which
will cover the following EPA national program management systems:
•	Aerometric Information Retrieval System-Air Quality Subsystem (AIRS-AQ)
•	Aerometric Information Retrieval System-AIRS Facility Subsystem (AIRS-AFS)
•	Federal Reporting Data System (FRDS)
•	Grants Information Control System (GICS)
•	Permit Compliance System (PCS)
•	Resource Conservation and Recovery Information System (RCRIS)
•	Storage and Retrieval of Water Quality Information (STORET)
- 1 -

-------
PRINCIPLES OF AGREEMENT
EPA and [STATE ENVIRONMENTAL AGENCY] agree to manage and use the covered EPA
national program management systems under the following principles:
1.	[STATE ENVIRONMENTAL AGENCY] agrees to use the EPA systems for the purpose of
entering [STATE] environmental data and for the retrieval of reports for use in environmental
decision making in [STATE]. [STATE ENVIRONMENTAL AGENCY] will assume
responsibility for the [STATE] data they enter in the EPA systems, and EPA Region VTII will
assume an oversight role. EPA and [STATE ENVIRONMENTAL AGENCY] will each
assign a system administrator for each EPA system covered by this MOU.
2.	EPA is ultimately responsible for the quality, timeliness, and accuracy of all data contained in
the EPA systems. [STATE ENVIRONMENTAL AGENCY'S] system administrator for each
EPA system will be responsible for assuring that [STATE] data entered by [STATE
ENVIRONMENTAL AGENCY] in the system is complete, accurate, and timely.
3.	Since [STATE ENVIRONMENTAL AGENCY] is responsible for the quality of the [STATE]
data entered by [STATE ENVIRONMENTAL AGENCY] into the EPA systems, EPA Region
VIQ agrees not to enter new data or change existing data affecting [STATE
ENVIRONMENTAL AGENCY] entries without consulting the appropriate [STATE
ENVIRONMENTAL AGENCY] system administrator. Disagreements between EPA and
[STATE ENVIRONMENTAL AGENCY] system administrators will be elevated to
successive management levels and, if necessary, ending with the EPA and [STATE
ENVIRONMENTAL AGENCY] Branch Chiefs who will make the final decision on the
disagreement
4.	In response to the joint EPA/[STATE ENVIRONMENTAL AGENCY] objective of
eliminating paper reporting, EPA and [STATE ENVIRONMENTAL AGENCY] agree that
[STATE ENVIRONMENTAL AGENCY] will use EPA systems for reporting [STATE
ENVIRONMENTAL AGENCY] program activity to the degree possible under the fiscal year
reporting requirements of EPA.
5.	EPA will be responsible for data concerning EPA activities and operations, entering and
retrieving such data at any time, provided such actions do not result in the changing of the
[STATE] environmental data entered by [STATE ENVIRONMENTAL AGENCY] , unless
such changes have been consulted upon per Principle #3.
6.	As encouraged under the national State/EPA Data Management Program, Region VIQ will
work to include [STATE ENVIRONMENTAL AGENCY] staff in systems development and
enhancement activities to ensure that State perspectives and day-to-day operational
requirements are considered.
7.	EPA and [STATE ENVIRONMENTAL AGENCY] technical ADP organizations will maintain
close working relationships to ensure that data processing operations and telecommunications
function as required to support program operations.
8.	Recognizing the differences among EPA's national systems, system specific principles will
become appendices to this MOU and will specify the procedures and responsibilities for day-
to-day operations and EPA system oversight. These principles will also specify those
responsibilities that must be retained by EPA because of national policy. There are appendices
(Appendix I to X) for [EPA DATA SYSTEMS]; other appendices may be added when
necessary.

-------
9.	EPA will continue to perform its oversight function as stipulated in the annual State-EPA
program and operating grant agreements. Reports will be extracted from the EPA systems as
needed by EPA to evaluate State performance of the delegated programs.
10.	EPA and [STATE ENVIRONMENTAL AGENCY] agree that this Memorandum of
Understanding can be amended by letter to add additional EPA systems when available in the
future.
Signed:
for: U.S. Environmental Protection Agency
		Date:
James J. Scherer
Regional Administrator
for: [STATE ENVIRONMENTAL AGENCY]
		Date:
(Signature)
- 3 -

-------
EPA Region VIII
SEDM Implementation Plans Summary
(Results as of April 1, 1991)
Overview
In order to effectively and efficiently track and respond to the many state requests for
assistance from EPA, the State/EPA Data Management (SEDM) Program developed the SEDM
Implementation Plans. The goal of the plans is to ensure that no requests "fall through the cracks."
These plans cover all programs, as well as non-program-specific requests.
The initial version of the implementation plans was developed from data needs assessments
conducted for the SEDM program. Now requests for assistance are entered into spreadsheets
which are updated by the state SEDM coordinators. Attachment A shows one page of a typical
plan. Table 1 below summarizes the amount and types of requests received to date.

Table 1:

Numbers of
Outstanding Requests
by the
States
of EPA

m
MI
ND
£D
HE
WY
Equipment
20
2
10
2
2

Funding
5

Training
11
6
6
7

Staffing
6
3

Management Issues
10
1
12
3

Technical Issues
34
7

12
4
]
Planning Issues
4
1
2
1
1

Other

TOTALS
90
20
30
25
7
1 =173
The State of Wyoming elected not to request assistance through the SEDM program
because of the likely "strings attached." Their single request was for a point of contact for GIS
within the Region. In addition, no needs assessment was conducted for the State of Utah, and,
therefore, their requests for assistance lacked program-specific items.
Findings
• Equipment — By far, the majority of requests were for computer equipment. Estimated
costs are shown on next page. Requests are sorted by media, state, and priority. [Note:
All cost estimates were given by the states, and only approved and/or non-funded requests
are shown. South DaJcota requests for equipment will be satisfied with the procuremenr :f
a GIS workstation.]
1

-------
State Requests for Computer Equipment
Media: Waste
State
CO
CO
MT
ND
Item #
Equip 4
Equip 7
Equip 1
Equip 11
Item Description
1 PC-386/25 - HWDMS/RCRIS
3 PC-286 - haz mat and waste
1 high-speed printer - RCRIS
1 PC-486 - groundwater and landfill analysis
SUBTOTAL
Media: Air
Item # Item Description
CO
CO
CO
CO
CO
ND
ND
ND
ND
Equip 29
Equip 30
Equip 31
Equip 1
Equip 32
Equip 1
Equip 3
Equip 2
Equip 9
1 PC-386SX - data conversion to Kleros
1 PC-386SX - implementation of Kleros
1 laser printer
1 PC-386SX - mobile sources
4 PC-386SX - modeling and connect to AIRS
GIS hardware (includes 3 workstations)
Data acquisition equipment
1 PC-486 - air quality modeling
1 plotter
1 PC-486 - statistical & graphical reports
SUBTOTAL
Media: Water
Item # Item Description
CO Equip 5
CO
CO
ND
ND
Equip 6
Equip 3
Equip 4
Equip 10
1 PC-386 - PCS
1 laser printer - PCS
5 PC-286 - PCS
1 PC-386SX - FRDS
1 PC-486 statistical analysis
1 PC-486 - PCS
SUBTOTAL
Media: General/Other
State Item # Item Description
CO Equip 27 LAN hardware/software - Rocky Rats Unit
CO Equip 28 6 PC-386/software -Rocky Flats Unit
CO Equip 10 1 PC-386SX - Answers system
CO Equip 11 GIS hardware (modem, terminal, map printer)
CO Equip 9 1 PC-386SX - OHEP project management
ND Equip 7 LAN file server/Netware software
ND Equip 6 Upgrade 17 LAN connection cards
ND Equip 8 Bridge to enhance connectivity to NCC
UT Equip 2 CASE tools for developing Oracle applications
UT Equip 1 LAN for Director, radiation, and drinldng water
SUBTOTAL
TOTAL ESTIMATED COST
Priori rv
Cost
High
$10,624
High
$7,500
Low
-$950
Low
$6,640

$25,714
Priority
Cost
High
$4,084
High
$4,084
High
$2,214
High
$4,084
Medium
$16,336
Low
$100,000
High
$16,035
Medium
$18,598
Medium
$2,920
Medium
$12,660

$181,015
Priority
Cost
High
$4,350
High
$2,214
Medium
$12,500
Medium
$4,084
High
$13,762
Low
$5,332

$42,242
Priority
Cost
High
$8,000
High
$63,378
High
$4,084
Medium
$+++
Low
$4,084
High
$32,396
Medium
$10,166
Low
$5,000
High
$75,500
Medium
$178,335

$380,943+
$629,913+
(verifying cost)
2

-------
Findings, cont'd
° Technical Support — Many of the states requested improved quality and amount of
technical support from Region VIH— both programmatic and computer-related support
• Communications — All states would like more and regular contact with Regional, HQ, and
RTP— not just when there is a problem. Many Regional program staff requested EPA e-
mail accounts for their state contacts in order to facilitate communications.
0 Training — There is a major disparity between the extent of training needs identified by the
states and those identified by the Region. Most Regional program staff believe that training
has been adequate; however, the states requested more training in most areas.
ISSUES
• Coordination — The implementation plans need to be coordinated with MOUs and SEAs to
ensure that appropriate requests are addressed and to avoid duplication of effort. Since all
of the states are interested in GIS, more coordination is also needed between EPA and the
states with regards to GIS planning and support. Lastly, more coordination is needed
between program and administrative staff— both in the state and the Region.
° Funding Non-Program-Specific Requests — The Region needs to develop a mechanism
for funding non-program-specific requests for assistance from the states. Requests that
affect large portions of the state's environmental agency can be worthwhile to all the
programs and should be addressed.
° STORET Support — In order to improve the STORET technical support to the states, EPA
needs to designate a person whose primary responsibility is to provide this support.
° Implementation Plan Updates — How often can or should the states be expected to update
their implementation plans? Must all requests be approved at the Division Director level?
Next Steps
States are expecting some resolution on major funding items soon and are very likely to be
raising the issue at the Region VIII SEDM Conference (April 16-18th). Approval or disapproval
of requests is needed ASAPf If items are approved, timeframes for fulfilling the requests are also
needed.
Other issues, such as technical support, training, and coordination, need high-level
awareness and commitment to affect a positive change.
3

-------
EPA Region VIII SEDM Program
Financial Assistance Program
Implementation. Methodology
The following procedures will be used within Region VIII to evaluate and rank the technical merit of applications
for SEDM financial assistance:
NOTIFICATION:
The SEDM Financial Assistance Program has been
included in the Catalog of Federal Domestic Assis-
tance as entry #66.925. The program has also been
publicly announced through a Federal Register notice
(OIRM-FR-3870-6, December 18, 1990).
DISTRIBUTION OF APPLICATION
PACKAGES:
Application kits are available upon request from the
Region VIII Grants Management Branch.
RECEIPT OF APPLICATIONS:
SEDM financial assistance are due to the EPA Region
VIII Grants Management Branch by April 30, 1991.
For funding of new awards in fiscal years beyond
FY91, applications must be submitted according to the
dates established by the Region VIII Office. As
applications are received, they will be logged in and
entered into GICS (Grants'Information Control
System).
SCREENING:
The Region VIII Grants Management Branch will
review the applications to ensure that they are
completed correctly, contain all the required docu-
ments, comply with statutory/regulatory requirements
and that administrative deficiencies are resolved.
REQUESTS FOR MORE INFORMATION:
If, during the technical evaluation, an application
package contains insufficient information to address
all the evaJuators' questions, requests for additional
information may be made of the applicants.
a Tra;>:»r.g
ReauireoReporting sr
STEP 9
STEPS
STEP 7
STEPS
STEP 5
STEP 4
STEP 3
STEP 2
STEP 1
ce:
Screening
neceiDt of Atsiicsi'.cns
Distncjticnof ADSiicato Packages
8
Notification
TECHNICAL EVALUATION:
Using the attached worksheet, a panel convened
within Region VIII will review and rank the applica-
tions against the technical evaluation criteria/
subcriteria and document their decisions.
RECOMMENDATIONS FOR FUNDING:
Upon completion of the individual technical evalua-
tions, the Region VIII panel will reach a consensus on
recommendations for funding.
AWARDS:
Using the staff recommendations for guidance, the
Region VIII SEDM Program Manager will make a
final decision regarding which projects will be funded
under the SEDM Financial Assistance Program.
REQUIRED REPORTING AND TRACKING:
Recipients of funds will be subject to the basic record-
keeping and financial requirements (as stated in 40
CFR Part 30 and 31). The requirements include a
final project report, final financial status report,
quarterly progress reports, and monthly telephone
conference calls.

-------
EPA Region VIII SEDM Program
Financial Assistance Program
Evaluation Worksheet
Proposal Title:		
Submitted by:	.	
Evaluator:	 Date:	
The main program objectives for SEDM Financial Assistance Program projects are: (1) to build and maintain the infrastructure
needed for effective Siate/EPA data management and sharing; and (2) to integrate data across media and programs so
environmental managers can target their efforts on environmental results. In awarding these funds to eligible applicants, EPA
hopes to improve the management and use of environmental data at all levels of government and, thereby, improve environmental
decision-making and risk reduction throughout the United States.
In order to assess whether proposed projects arc suitable for funding under the SEDM Financial Assistance Program, five
criteria of equal value have been recommended to evaluate and rank the proposals.
This worksheet was developed to assist in the evaluation process. Please complete a separate worksheet (both sides) for each
proposal.
1. Appropriateness to the SEDM Program

Proposals under this assistance program must be appropriate to the goals and objectives of the
SEDM Program.

a.	Appropriate to National SEDM goals (10 points)
b.	Appropriate to EPA Region VIII SEDM goals (10 points)



Total la-lb (20 points possible)


i
2. Integrated/Multimedia Approach
The evaluation should consider whether the projects are multimedia in approach and will advance
the goals of integrating information from diverse sources to support sound environmental decision-
making. However, particularly innovative or strong proposals involving a single medium or data
source should be given fair consideration if they are most appropriate for addressing a State's or
Indian Tribe's priority concerns. The degree of coordination and cooperation among various
involved agencies should be considered where relevant to the project.
a.	Multimedia project with diverse data sources (5 points)
b.	Use of innovative or new technology (5 points)
c.	Provides tools to support sound environmental		
decision-making (5 points)		
d.	Degree of coordination/cooperation by involved				
agencies (5 points)	jQ[a] 2a_2(J (2Q poims possibie)	I

-------
[3. Potential Benefit


The evaluation should consider the degree to which proposed projects may improve data sharing
andlor data integration benveen EPA and States or Federally recognized Indian Tribes, and the ^
likelihood that the proposed activities will succeed in achieving those goals.
Note: Each criteria below should be weighed against cost.


a. Improvement in data sharing/integration (5 points)

1
b. Supports EPA's and/or applicant's priorities (5 points)


c. Meets documented needs (5 points)

l
d. Likelihood of success (5 points)

1
Total 3a-3d (20 points possible)

1
1
; . J



4. Technical Soundness and Feasibility of Implementation
The evaluation should consider the technical soundness of the proposal and the feasibility of	I
implementation. Areas of consideration include: competency of proposed staff, appropriateness j
of proposed project period and budget, and whether the proposed project has been clearly defined j
with measurable success factors.
Note: Each criteria below should be weighed against cost.
1
a.	Competency of proposed staff (5 points)		
b.	Appropriateness of proposed schedule and budget (5 points)
c.	Clearly defined project with measurable success factors
and products (5 points)
d.	Appropriateness of proposed hardware and software (5 points) 	 ; 	j
Total 4a-4d (20 points possible)	r		'
5. Technology Transfer Plans


The evaluation should consider the degree to which the applicant proposes technology transfer
plans to facilitate the transfers of project products (e.g., software applications, handbooks,
workshops, etc.), data, approaches, ideas and findings to other interested parties.
a.	Flexibility/adaptability to other situations (7 points)
b.	Extent of technology being transferred (7 points)




c. Clearly defined method of transfer (6 points)


Total 5a-5c (20 points possible)


Grand Total 1-5 (100 points possible)

-------

-------
Rocky Mountain
rogram
EPA Region VIII
by Marce Osterholt
Region VIII SEDM Program Manager
April 16, 1991

-------
The survey (to be explained later) is still in progress and
results will he presented at the Region H SI'.DM conference
in April 16-18th.
- f* ¦ i .
. v
->v m
Overview
¦ Background
•Accomplish menta
•Currant Inltlatlvaa
•Survey Raaulta
•Next Stapa
. 7 - 3* ,v- "®-
• *.«- . " • ^ •
* * * r
We in Region 8 found that the successes of the Georgia
pilot uere not easily transferable to our 6 states
tC«»l«irado. Montana, North Dakota, South Dakota, Utah,
and Wyoming).
We are committed, however, to the ideas of data sharing
and data integration (i.e., the SliDM program).
We believe that in order to achieve the objectives of (he
S|-|>M program, we must first establish effective data
management programs in each of our states. This is the
Its. ux •»! our many regional initiatives.
Background
¦Utah waa tha pilot atata In 1986
-Tha atataa In Region VIII lack:
•	full management aupport
- exteneive or integrated ADP
•	IRM planning
•	resourcee
Background, cont'd
In Region K, we do have one advantage, however, in
that the Regional SLDM lYogram Manager reports
dire* tly to the ARA for Policy and IfevelopmcnL His
support i% \ ital to our current and future progress.
Iiurwa^ingly, the role of the Region X SI: DM 1'rogram
Manager requires coordinating with many agencies and
• •rt-ani/aiions (e.g., our CIS l\:nter for l .xcellence, state
ta>k fortes for CIS, and the I'SCiS) in order to achieve

-------
Accomplishments
Telecommunication* lines
Slate data needs assessments
News bulletins
Accomplishment!, cont'd
•Pilot studiss:
•	Rocky Flats
- Options analysis for a Prims
•	IRM strategic plan
•	Telecommunication lines were insulted in the remaining
two states (SD and YVY) in Region 8.
•	Data needs assessments were conducted fur CO. MT,
ND. SD, and WY. These assessments were needed to
analy/e the status of data management programs in these
states and identify areas for improvement
•	News bulletins are used to communicate progress and
inform stales of data standards, changes in policies, etc.

EPA Region VIII
»l*U«4 studies are a learning tool... we try to share the
learned with our other states.
-	We worked with CO to define an information system
ft* monitoring data collected at the Rocky Flats nuclear
weapons plant.
We w«vkcd with SD to identify the requirements for a
hum minicomputer and investigated other hardware
OftMMIS-
-	We worked with Utah to identify needed changes in
the* data management program and to lay a foundation
f«« future strategic planning.
Current Initiatives
•Implementation plans
•MOUs
•Mora pilot studies (UMS, GIS,...)
•Survey
•Miscellaneous (training, computers,
•«c)		
•	I mpU mentation plans are our tool for tracking and
o««diruting states' requests for assistance from LP A.
•	\fol' * iusing the fiPA/Georgia MOU as a template) are
K-aig drafted to respond to issues of data integrity.
•	In • study for MT we are looking at using a I.IMS to
Lab data in electronic form and transmit it to state
pngrants and fcPA. In ND we will develop a
rmth»Hinl»»gy and criteria for selecting a GIS pilot.
•	Ilk survey was used to evaluate our program and assess
• naff •nlh-jJl tools.
•	Vint of our funds are also used to buy or upgrade
t •nipuier equipment, train stale program staff, etc.

-------


Currant Initiativaa, cont'd
A COORDINATION POLICY and ®rocedcree
ere aiso under development
& A



9A 'W
¦re«rMM B
>

» •
EPA Region VIII

In ihc past, state programs communicated directly with
l-PA programs to request new computer hardware and
software. They may or may not have notified slate
adininisirai(»rs ol iheir plans... As a result, state ADP is
more often than not a mix which makes data sharing and
integrate*! difficult
Now, when a request for ADP arrives from the states, it
is forw arded to the Regional SliDM Program Manager,
who calls the Slate coordinator for approval.
In the future, with (he implementation of our SI .DM
coordination policy, programs will work with their SI-1DM
coordinators IIRST!
4 M,	. i'- ts- ;
(The statistical results are in the conference binders |
• I hen: were not as many respondents as expected (44 total):
-	\V Y sent in a collective response
-	Only 2 from CO and 4 from LT
-	Only 12 completed surveys from RK
•By far, most respondents felt little involvement in the
program. Most receive information directly from the
Regional or State Coordinators.
•Most tell that national SI-.DM goals (not Region 8 goals
which are yet lo he defined) are unclear. (May be due to
lack of involvement )
•liad news is that impact is small... (iood news is thai, over,
lime, the program will have more impact.
Survey Findings
Most respondents had minimal
Involvemsnt in th« program
•SEDM goals ara undaar
•Current impact ot program ia small
•Potential impact is iarga
EPA Rrg on VIII
Findlngi
It, cont'd
•Resource* could ba uaad battar
•Main obstacle ia lack of raaourcoa
•Stataa hava not baan convincad to uaa
EPA data ayatama
¦Coordinatora ara doing a good Job.




EPA Rrj on VIII
•I'nfortunatcly, the survey docs not spell out how
resources could be used more effectively.
•I.ack of SSS is especially a problem, but so is lack of
manpower for pilot projecLs, duties for coordinators, etc
•IJolh state and l:PA respondents acknowledged that l:PA
data systems are still not fully nsfonsive to slate needs—
though they are improving.
•RK >iatl and stale coordinators reviewed Marce,
remainder rev»ewed stale coordinators

-------
Survey Conclusions
•Mora outreach ia needed
•SEDM program necda mora resourcaa
•EPA ayatama need to ba mora
responaiva
•SEDM program la atill In It* Infancy.
•Not enough people know about or understand the
program especially within the Regional office.
•The program is ambitious, and it will need stable
funding if it is to succeed.
•More needs to be done to provide training, technical
support, and state-supported enhancements to EPA
systems.
' ' ^ • i" -¦
• The survey resulLs are not surprising for a new
program. It shows that we still have a LOT of work
ahead of us.
One of the greatest challenges of implementing the
SbDM Financial Assistance Program will be to form a
panel and evaluation criteria which are fair... and will not
discourage in the future proposals for our limited funds.
We plan to distribute the evaluation criteria and
decisions to those who sent in proposals, as well as to the
state SfcDM coordinators, so that everyone will understand
our decisionmaking process.
'Financial Aaalatanca Program:
-	Receive propoaala
-	Develop evaluation criteria
-	Form panel
-	Follow up with program $$?
• Evaluate auccaaa of program
We are formalizing a strategic plan which covers:
•	Strategic planning 3-year plans (MT? and ND?) and
data integration pilot projects.
•	Organizations - defining roles and responsibilities for
coordinators, steering committees, technical advisory
groups, etc.
•	Data identifying opportunities for improvement (e.g..
management, user support, data base design, equipment
and telecommunications.. )
•	Policies and Procedures— such as the coordination
policy, MOL's, and the implementation plans
•	Communications data lines and user accounts, news
bulletins, conferences, etc.
•	Technical Transfer LANs. CilS, IJMS, workstations,
centralized facility tracking. GPS...

-------
Next Steps, cont'd
-State 5-year IRM plant?
•Regional directory?
Regional clearinghouse?
Depending on the interest of our states, we may also
develop:
•	Strategic plans for the remaining 4 states,
•	A Regional directory of contacts, and
•	A Regional clearinghouse of SF.DM information (that is,
a listing of reports, presentations, etc. of interest to the
SEDM program)
? . •
/¦ :>

In conclusion...
The SI DM program is making progress in Region 8
because of the many I-.PA and state people committed to
the ideas of data sharing and data integration.

Table 1:

Numbers of
Outstand
ng Requests
by the
States
of EPA

£0.
MI
NT)
SD
in
WY
Equipment
20
2
10
2
2

Funding
5

Training
11
6
6
7

Staffing
6
3

Management Issues
10
1
12
3

Technical Issues
34
7

12
4
1
Planning Issues
4
1
2
1
1

Other

TOTALS
90
20
30
25 .
7
1 = 173
The State of Wyoming elected not to request assistance through the SEDM program
because of the likely "strings attached." Their single request was for a point of contact for GIS
within the Region. In addition, no needs assessment was conducted for the State of Utah, and,
therefore, their requests for assistance lacked program-specific items.
Findings
• Equipment — By far, the majority of requests were for computer equipment. Estimated
costs are shown on next page. Requests are sorted by media, state, and priority. [Note:
All cost estimates were given by the states, and only approved and/or non-funded requests
are shown. South Dakota requests for equipment will be satisfied with the procuremen; ~f
a GIS workstation.]
1

-------
State Requests for Computer Equipment
Media:
Waste
State
Item #
CO
Equip 4
CO
Equip 7
MT
Equip 1
ND
Equip 11
Item Description
1 PC-3S6/25 - HWDMS/RCRIS
3 PC-286 - haz mat and waste
1 high-speed printer - RCRJS
1 PC-486 - eroundwater and landfill analysis
SUBTOTAL
Media: Air
Item # Item Description
CO Equip 29 1 PC-386SX - data conversion to Kleros
CO Equip 30 1 PC-386SX - implementation of Kleros
1 laser printer
CO Equip 31 1 PC-386SX - mobile sources
CO Equip 1 4 PC-386SX - modeling and connect to AERS
CO Equip 32 GIS hardware (includes 3 workstations)
NT) Equip 1 Data acquisition equipment
ND Equip 3 1 PC-486 - air quality modeling
ND Equip 2 1 plotter
ND Equip 9 1 PC-486 - statistical & graphical reports
SUBTOTAL
Media; Water
Item # Item Description
CO Equip 5 1 PC-386 - PCS
1 laser printer - PCS
CO Equip 6 5 PC-286 - PCS
CO Equip 3 1 PC-386SX - FRDS
ND Equip 4 1 PC-486 statistical analysis
ND Equip 10 1 PC-486 - PCS
SUBTOTAL
Media; General/Other
State
Item #
CO
Equip 27
CO
Equip 28
CO
Equip 10
CO
Equip 11
CO
Equip 9
ND
Equip 7
ND
Equip 6
ND
Equip 8
UT
Equip 2
UT
Equip 1
Item Description
LAN hardware/software - Rocky Flats Unit
6 PC-386/sofrware -Rocky Flats Unit
1 PC-386SX - Answers system
GIS hardware (modem, terminal, map printer)
1 PC-386SX - OHEP project management
LAN file server/Netware software
Upgrade 17 LAN connection cards
Bridge to enhance connectivity to NCC
CASE tools for developing Oracle applications
LAN for Director, radiation, and drinldng water
SUBTOTAL
Priori rv
Cost
High
Sl0,624
High
S7.500
Low
-S950
Low
S6.640

525,714
Prioritv
Cost
High
54,084
Hish
54,084
High
52,214
High
S4,0S4
Medium
SI 6.336
Low
SI 00.000
High
SI 6.035
Medium
SIS,598
Medium
S2,920
Medium
SI 2.660

5181,015
Prioritv
Cost
High
54,350
High
S2,214
Medium
512,500
Medium
S4.084
High
S 13,762
Low
S5.332

S42,242
Prioritv
Cost
High
58,000
High
$63,378
High
54,084
Medium
$+++
Low
54,084
High
$32,396
Medium
$10,166
Low
55,000
High
$75,500
Medium
5178.335
(verifying cost)
5380,943+
TOTAL ESTIMATED COST
$629,913 +
2

-------
Findings, cont'd
Technical Support — Many of the states requested improved quality and amount of
technical support from Region VIII— both programmatic and computer-related support.
Communications — All states would like more and regular contact with Regional, HQ, and
RTP— not just when there is a problem. Many Regional program staff requested EPA e-
mail accounts for their state contacts in order to facilitate communications.
• Training — There is a major disparity between the extent of training needs identified by the
states and those identified by the Region. Most Regional program staff believe that .training
has been adequate; however, the states requested more training in most areas.
Issues
• Coordination—The implementation plans need to be coordinated with MOUs and SEAs to
ensure that appropriate requests are addressed and to avoid duplication of effort. Since all
of the states are interested in GIS, more coordination is also needed between EPA and the
states with regards to GIS planning and support. Lastly, more coordination is needed
between program and administrative staff— both in the state and the Region.
• Funding Non-Program-Specific Requests — The Region needs to develop a mechanism
for funding non-program-specific requests for assistance from the states. Requests that
affect large portions of the state's environmental agency can be worthwhile to all the
programs and should be addressed.
• STORET Support — In order to improve the STORET technical support to the states, EPA
needs to designate a person whose primary responsibility is to provide this support.
• Implementation Plan Updates — How often can or should the states be expected to update
their implementation plans? Must all requests be approved at the Division Director level?
Next Steps
States are expecting some resolution on major funding items soon and are very likely to be
raising the issue at the Region VM SEDM Conference (April 16-18th). Approval or disapproval
of requests is needed ASAP! If items are approved, timeframes for fulfilling the requests are also
needed.
Other issues, such as technical support, training, and coordination, need high-level
awareness and commitment to affect a positive change.
-3

-------
3

-------
EPA Region VIII
State/EPA Data Management Conference
Colorado
Department of Health
Office of Health and Environmental Protection
(OHEP)
State Update
by Gerard Bulanowski
April 16, 1991

-------
Notes
°F
SEDM in Colorado
Overview

Background
Slaiua
AoeamptUhfnania
Currant Initially*
IUUM
RoJa of S£OM Program
Nut Stapa
at
m
ra	=m
^	SEDM in Colorado	^
Background
Slnoo tha last Rag km VIII SEDM Confaranoa, tha Oflloa of HmJM
and Envirermerital Protection (OHEP):
•	Craatad an IRM Group to ooordlnaia all aapocta ol
environmental data Integration
•	Craatad (he Klaroa f acilMea manegamant ayatam and
oorraa ponding Klaroa Jaara Group
« Conductad Klaroa wortpim, ay lam equipment tn»antortea and
data naada aiaMvn«tt>
•	Completed Rodiy Flats Data Syatam needa aaanamant and
optlona anaiyaia
•	Submitted EPA SEDU atraleglo plan hlormatlon
•	Completed OHEP GtS rtaada asaeeemant and opitona anatyaha.
ILJ
SEDM in Colorado
Status
Klaroa (a.Colorado'a raaponaa to (he SEDM program and to
tagiaialhMi mandate to pwiui data Integration
Klaroa ta ail but opandenal:
Data oon vera Ion
Planning
Traofcbtg
Equipment botog aoqukad
Continuing dlacuaalone with Region VIB
EPA databaae aooaaa
EPA program/atata program eommuntoeilone
Sand Cf*k frvrpJamantaiion.
m

-------
Notes
W
SEOM in Colorado
KLEROS

Uaana in Grtafc 1o	In lh« prof^ct"
lntag/B(*t dcta or\ fmcilillaa rtguktad h Colorado
Modalad aftar (ha JIWS dayfopart in Gaecgta
WIN link to EPA ndtoivl data «y»tama
Sin* ajMndktg authority for
naar Macs* ywr tsaurad.
m=

SEDM in Colorado
KLEROS Concept

Pwrnte:-:;;]'

Camofiancw''
«id
Enlcrpaniant
k

' rAud*y-K
Master File
St
Comaxt:
Cllani ProoaaaJng	Syatam Adminlatradw Functions
Monftorfcng Errforcamanl	Syafam CaWidar M«n*g*mant
IrtapacMr Schadullng	Syatam GlS Uanagamvil
Uanagamant Raporta Processing
m
SEDM in Colorado
Accomplishments
Ktaro* llto atiuctura «id data atamants daftoad
Klaroa has oonvaetad with Softwara AO (or
davaiopmani/product tor pfcaaa
GtS workstations to air, aratar, and vasts
Sand C raa* GtS oparatlona*.
is
•n

-------
SF
SEDM in Colorado
Sand Creek
=s
m=
Joint Enforcement Pile* W EPA 3»gio*i VI!l
Muh9e« Ftci ntet — R«9uUI«« hms
Many ;oii« — orolocols, maro** data ooll«cil an.
wr-o aria
: i
?ra|«d
JaWit Tjjr ?ptc* D«qari I9W
W-vh Ptar c0mplal«d
Wlkbe eoco^P'tshed wfinM
•elating r«ourM
Apprpjibtal#^ 18-fnonih |lf«»©an.
=m

SEDM rn Colorado
Current Initiatives
• Svattfla piamlnf edntlnuM ter «mrlrenffl«ai data ^tigiallon
• Preys" •quipnartf acquisition g
-------
Notes
SEOM in Colorado
Technical Troubles

W* ourrwttfy u**;
. i*.ng
mfnloomouiw*
• \ OEC VAX
rptntoornoutar
- rh«Stc(*J8«
ma in bam*
• Th.EPAIBU
mabifrwn*
• LAN*
• a«.

SEDM in Colorado
Fragmented Funding

KLER09 Roc*y Ftett S««d Cr«*
imm « »ffim
at
SEDM In Colorado
Communications and Coordination
-------
htarfen anforcwn*
tradklng «ytt«m
Equlpmwit neede
CIS,
Notes
SF
SEDM In Colorado
"I want it NOW!"
=0
m=
m
Ct y,
"*• SEDM in Colorado
Role of SEDM Program
« Provlda graalar coordination bwwwn EPA arogram*
Mat* progrmma
• AnwigotMfotoaJMatoana*
« Prarido 9«atar dotation and goaJ *aOtog
• Sam m eatttytt tor ^noro^tng dal* atamant
uona htmfoaflvantfm
¦ toftpvev*«oo^ln>tian wftfc EPA CIS program.
ts "ifi
SEDM In Colorado
SEDM is an important link to
Colorado, but not exclusive
\JLy
Ctamnr ftwtt '
PoiMkmi CttnM*
m
-------
Notes
SEDM in Colorado
Next Steps
KWo*
3n coriv*r*k>n oUna
L*til*WUy* d*oi»ion nam*
ComptoUon el $«nd Cf «*fc pro'pct
LAM eenelepmwil
CS inweofr.«nl
m=
m
SEDM in Colorado
Next Steps, Cont'd
'II «• had to start wtr, m would.
* C*t MrPy support from manag«m«nt «id progrvna
« Avoid oantuaing KLEflOS «• • *y«tam wilt* th» definhten of
Vtt*gr«iad Envfrermmtd Uwiag«n«nt
• Start from Vm
« Coorillnste EPA'» Inweh—n«wt wviiw h *h» pffiniH,
m=
M
-------
EPA Region VIII
State/EPA Data Management Conference
Montana
Department of Health
and Environmental Sciences
(DHES)
State Update
by Abe Horpestad
April 16, 1991
-------
Notes
SEDM in Montana
My role in SEDM
SEDM in Montana
Overview
Background
Status
Accomplishment*
Currant AetlvttUa
taauM
SEDM in Montana
Organization
-------
Notes
SEDM in Montana

Computer Support Personnel
Orainlutlon
Support
flUlfi
£nvronrn«nul ScWio«« DJvision
6 FTf
i:io*
Cwtral S«rvle*» DWIttan
1 PTE

Strvlo** Dlvbton
(contra Clad)

8 FTE~

•primarily r*»pon«Ibk for (Mimical duttas in Individual programs
"*0*partm«nt o4 Administration has • pool ol •available*
p*rtonr*l for technical a»»bt*nc«

SEDM in Montana
Status: The Big Picture
t
hT
SEDM in Montana
Status: The Little Picture
-------
Notes
lb 3
SEDM in Montana
SEDM-Related Accomplishments
OHES Data Na«da Aaaaasmant
• OHES tmplamanlatlon Plan
UMS Raqulramanta Analyaia
• UMS Opllona Analyaia
• OHES Sanction and Rafinamant of LIMS Option
• Grant Application.
SEDM in Montana
Current Activities
Analyaia of raplaoamant walar quality data ayatama
— Uuftt Ineluda historical data
— Muat Includa aaay to uaa manipulatlona
Purault of "Hard Copy Onty" data to our ayatam
— Eaay an try a raqukamant
— Will try to raqulra that our oontradora and olhar
aourcaa aubmtl competlbla data
Purault of "Hard Copy Only" data tram other aourcaa
— Swaat talk?
— Forca???
SEOM in Montana
Is Rational "Global" Data
Management Possible?
Probably not
• Funding raitrktiona
Lagal raatrlctlona
Soma Improvamanta ara poasbla
CIS holds prom bo
SEOM can hatp on at) front*, and tt may ba too
aarty to oono«ntrala SEOM affon on any on*
approach.
TX
-------
EPA Region VIII
State/EPA Data Management Conference
North Dakota
Department of Health
and Consolidated Laboratories
Environmental Health Section
(EHS)
State Update
by Allen Johnson
April 16, 1991
-------
NORTH DAKOTA STATE DEPARTMENT OF HEALTH
AND CONSOLIDATED LABORATORIES
January 1, 1991
STATE HEALTH OFFICER
Robert U Weoli. U D . U.P.H.
GOVERNOR
George A. Sinnei
MUNCIPAL FACILITIES
Jack Long
STATE HEALTH COUNCIL
Lowoll Heriindahl
Chairman
WATER OUALITY
Dennis Fowleii
WASTE MANAGEMENT
Martin Scftocfc
ENVIRONMENTAL
ENGINEERING
Dana Uuua]
EMERGENCY HEALTH
SERVICES
Timothy Wiediich
COMMUNITY HEALTH NURSING
LaVeine Lm
MATERNAL AND CHILD
HEALTH
Dave Cunningham
HEALTH RESOURCES
ANALYSIS
hoi GUddsn
MICROBIOLOGY
Jim Artdan
CONSUMER
PROTECTION
Peri Dura
HEALTH PROMOTION
AND EOUCATON
Sandy Adam*
FORENSIC SCIENCE
Aaron Rath
VITAL RECORDS
Beveily Wiiman
HEALTH FACILITIES
Fied Gladden
HEALTH RESOURCES
SEC1ION
Fied Gladden
DISEASE CONTROL
Fled Hear
PERSONNEL OFFICE
PREVENTIVE HEALTH
SECTION
Sieve McDonough, U.D.
CONSOLIDATED
LABORATORIES
BRANCH
Jame* Peareon. Oi. P H.
ADMINISTRATIVE SERVICES
SECTION
Robert A. Bainoa
ENVIRONMENTAL HEALTH
SECTION
Francb Schwindi
OFFICE OF
ENVIRONMENTAL
ENFORCEMENT
Bdl Delmoie
-------
<)Yi:UYIi:W:
#i
The SEDM organization in NortJ|
Francis J. Schwindl ?'
Chief, Environmental 1 Icullti Section 5j
•*./»/ •'iK'".: >x;v;wr'v:: >:•* :r:r::r*:r::
Charles D. Rydell
North Dakota SEDM Coordinator
i
I Marce Oslerholt |
¦ EPA Kegion VIII SEDM {
I Coordinator |s

Information Services
Division (ISD)
Allen Johnson
Data Processing Coordinator
r~j
ji
c
0
5
C g
1 j
.§
CO
a
oc
u.
%»
*

c
"3
5 "5

Q
O
VJ
a.
'< :
P * u
uj at £
i O
>5 r? 1~
< C c/)
-------
EL Background
A. Data processing was performed on mainframe
computers (3190 and 4381).
1. Air Quality Modeling
2. Air Quality Data Handling System
3. Emissions Inventory
4. Oil and Gas Production Inventory
B. Leased line to NCC in the spring of 1986
Online with AIRS
C. Installed a Novell PC Local Area Network in June
of 1987.
Automated our data collection for 6 continuous air
monitoring stations using Western Telecomputing
DAS.
D. In 1987 we converted all of the Division of Water
Quality's and Division of Municipal Facilities' data
from their Apple II systems to the Novell network
of IBM compatible PCs.
£. Name and emphasis change - Central Data
Processing to Information Services Division.
Move from centralized application development to
divisional application development. ISD now acts
as a resource and facilitator.
-------
IIL Status
A. Division of Water Quality
1. PCS — Data is entered online for major
dischargers. Negotiations underway for
increasing the number of facilities reported,
types of data reported.
2. STORET -- Water chemistry data is sent
from our chemistry lab to us via floppy disk
in STORET format. Data is QA'd and
uploaded to NCC. Submitted as batch.
-------
IEL Status continued
B. Division of Municipal Facilities
1. FRDS - Inventory and compliance data are
entered into a PC database. Updates to
FRDS are uploaded to NCC quarterly and
submitted as batch updates. We were the
second state program in the nation, behind
Illinois, to submit FRDS II drinking water
data electronically to EPA using the FRDS II
Data Transfer Format.
2. GICS - Grant data is tracked using a
spreadsheet. Data is entered into GICS
online.
-------
HL Status continued
C. Division of Environmental Engineering
1. AIRS - Air quality data is collected in the
field using a Western Telecomputing DAS.
Data on floppy disk is transferred into our
PC air quality database. Data is
manipulated in house using PC SAS. Data
is then converted to AIRS format and
uploaded into an AIRS screening file for
update.
We will be changing our PC air quality
database to directly support AIRS format.
Presently we store data in a variant of the
SAROAD format called AQDHS.
2. AFS - Compliance and emissions data are
entered online.
a. Our compliance person likes the new
system. He received training in June of
1990.
b. Our emissions person was trained in
January of 1991. He has just started to
use AFS.
-------
ID. Status continued
D. Division of Waste Management
1. RCRIS - We have had one person trained in
RCR1S. She has just begun to use the new
system.
2. UST - UST data is stored on a PC using the
CRM and Associates UST database
management system.
-------
IV- Recent Accomplishments
A. Completed the joint BLM and NDSHDCL air
quality modeling study.
1. All modeling done on a PC at a cost of
$125,000.
2. Estimated cost if done on the mainframe
$500,000.
-------
Recent Accomplishments continued
B. Installed a second Novell LAN for word
processing. Replaced our aging NBI word
processing system.
1. Done in conjunction with the installation of
new digital phone system.
2. Rewired our office building with shielded
twisted pair cabling. This provides the
groundwork for a much higher performance
local area network.
-------
IV. Recent Accomplishments continued
C. Established state GIS Technical and
Management Steering Committees.
1. Contain representatives from several state
agencies and universities to explore
hardware, software, and data implementation
options.
2. Technical Committee Recommendations
a. Base Map Standard : USGS 1:24,000
quad maps.
b. Adopted USGS National Map Accuracy
Standards as a goal for map accuracy
standards.
c. Require verification of data quality
before the data can be distributed.
d. Establish an electronic inventory of
available digital data.
-------
Current Initiatives/Next Steps
A. Replace our current file server with a "super server".
B. Replace our aging air quality data acquisition system
hardware and convert the database to native AIRS format.
C. Purchase a state of the art PC for air quality modeling.
1. Bring the long range transport models and datasets
down from the mainframe and conduct Class II area
impact modeling using the PC.
2. Conduct more detailed modeling of oil fields in western
ND as a followup to the BLM study.
D. Purchase additional personal computers for the Water
Quality, Municipal Facilities and Waste Management
divisions.
E. Upgrade our token ring NICs to support 16 Mb/sec
transmission speeds.
F. Enhance our connectivity to NCC by installing a gateway on
our PC network.
G. Obtain training for NCC systems and PC software.
H. Establish a more formalized data processing structure with
increased funding and staffing.
I. Develop a long term data processing strategy.
-------
VL issues
A. EHS is currently using videotape training
courses under a contract that NCC Training had
with Applied Learning. We would urgently
request that this contract be renewed. We would
also encourage the development of videotape
based training courses for NCC mainframe
database systems like PCS, FRDS, GICS,
RCRIS, STORET and AIRS.
B. The Waste Management Division has been
approached about the feasibility of a
groundwater data base for RCRA. We were
unaware that EPA Headquarters has been
defining a minimum data element set for
groundwater data in STORET. If the
groundwater data is put in STORET, then the
Division will need STORET training.
C. More information is needed regarding the SEDM
grant process, particularly as it relates to the
allocation of dollars to Indian tribes within the
state.
D. Information is needed on the disposition of
monies and technical support from EPA Region
VIII to support the state's SEDM
implementation plan.
-------
VII. Role of SEDM Program
A. Coordinate training of state personnel in the use
of EPA national database systems.
B. Assist in the development of a long term data
processing strategy.
C. $$$$
-------
EPA Region VIII
State/EPA Data Management Conference
South Dakota
Department of Water and Natural Resources
(DWNR)
State Update
by Ron Woodburn
April 16, 1991
-------
-------
DENR ORGANIZATIONAL CHART
-------
DENR LAN

SD STATE
MAINFRAME
ftlBERTORJIC
KffSjyBA'eKBONE
... . ~N p,/:j
aWotlK'tUJU^'iaiSHilJil B Wmil'dmi nlW.HWlWUMM
gLV.rg.uu
ran
l§@

S t/rj^
•7; tt-v? rr^MTmrT^ri

cl
&%
il Jj • O^V-it
s j% ^ -t .-.r- r. »
4:3^1
£ •!»' •"". -T^n—.^
denr
CONNECTIVITY
-------
AT LAST!!!
|g^SinS8EB
K^iars:-Vd

-------
CURRENT STATUS OF
SEDM PROGRAMS
GICS
PCS
FRDS
AIRS
RCRIS
STORET
-------
SEDM INITIATIVES
GICS
PCS
FRDS
AIRS
RCRIS
STORET
-------
GEOGRAPHIC
INFORMATION
SYSTEM

&>: W*&S&* M&'. ?
-------
RS6000 WORKSTATION
32 MB RAM
1.2 GB DISK STORAGE
X.25 ADAPTER
CD ROM DRIVE
1/4" TAPE DRIVE
TOKEN RING ADAPTER
11 n.-iiM
M

saVs«&e«Ji..> •£ r AaS^ifovY.uj.M,

mmmm*1
-------
SEDM ISSU
RCRIS IMPLEMENTATION
GICS WORKSTATION
TRAINING
- GIS
- SEDM PROGRAMS
OTHER
-------
EPA Region VIII
State/EPA Data Management Conference
Utah
Department of Health
Divison of Environmental Health
(DEH)
State Update
by Robert Shipman
April 16, 1991
-------
DIVISION OF ENVIRONMENTAL HEALTH
PRESENTATION OVERVIEW
• Organization
• Status - Phase I
• Status - Phase II
• Accomplishments
• SEDM Issues
• Conclusions
-------
DIVISION OF ENVIRONMENTAL HEALTH
ORGANIZATION
Department of Environmental Quality Created
Effective July 1, 1991
Six Program Divisions
Water Pollution Control
Drinking Water
Radiation Control
Environmental Response & Remediation
Solid & Hazardous Waste Management
Air Quality
Office of Human Resource Management
Office of Planning and Policy
Office of Administrative Services
-------
DIVISION OF ENVIRONMENTAL HEALTH
OFFICE OF ADMINSTRATIVE SERVICES
• Data Processing Coordination/Services
SEDM Coordinator
• Financial Services
• Budgetary Services
• General Services
• Purchasing Services
-------
DIVISION OF ENVIRONMENTAL HEALTH
DATA PROCESSING FUNCTION
• Office of Administrative Services
SEDM Coordinator
Programmer/Analysts (3)
Application Development
Application Support
System Support
• Program Divisions
Local Area Network Administrators
Application Development
Application Support
-------
DIVISION OF ENVIRONMENTAL HEALTH
PHASE I - STATUS
• Air Quality
CDS - Online Data Entry
AIRS - Tape Transfer
• Water Pollution Control
PCS - Online Data Entry
STORET - Tape Transfer
GICS - Online Data Entry
• Drinking Water
FRDS - Electronic Transfer via Network
• Hazardous Waste
RCRIS - Planning Phase
-------
DIVISION OF ENVIRONMENTAL HEALTH
STATUS - PHASE II
• EPA Management Study
Review the Strategic Plan Process
Report Status of Data Management
Review Key Decisions Needed
Set Agenda for Future Planning
• Recommendations
Establish IRM Steering Committee
Establish IRM Technical Advisory Committee
Use Regional Information Resources Management
Organization Model to Plan DP Organization
Complete Concise Five Year DP Management Plan
Balance DP Management Between Division and Bureaus
Establish DP Standards
-------
DIVISION OF ENVIRONMENTAL HEALTH
ACCOMPLISHMENTS
• Data Processing Steering Committee Established
Comprised of Bureau Directors
• Data Processing Technical Committee Established
Comprised of Representative of Each Bureau
• Accomplishments
Data Processing Standards Established
Database Management Software
Software Standards
Hardware Standards
Geographical Software
Minimum Data Standards
Out Standing Issues
Data Processing Organization
Data Processing Staffing Levels
-------
DIVISION OF ENVIRONMENTAL HEALTH
ACCOMPLISHMENTS
• Data Integration Initiatives
Integrated Information Management System
Title III Integration Project
Minimum Data Standards
Water Pollution Program Integration
• Geographic Information Systems
Salt Lake County Demonstration
DRASTIC Project
Title III Project
-------
DIVISION OF ENVIRONMENTAL HEALTH
DATA PROCESSING ISSUES
• Technology
• Organization
• Resources
-------
DIVISION OF ENVIRONMENTAL HEALTH
TECHNOLOGY ISSUES
Technology Advances
• Users of Technology
Environmental Engineers
Environmental Scientist
Program Managers
Administrators
-------
DIVISION OF ENVIRONMENTAL HEALTH
ORGANIZATIONAL ISSUES
Air
Programs
Water
Programs
Waste
Programs
• Support Services - Data Processing
i
-------
DIVISION OF ENVIRONMENTAL HEALTH
ORGANIZATIONAL ISSUES
Water
Programs
Waste
Programs
Air
Programs
SEDM
Programs
Support Services - Data Processing
-------
DIVISION OF ENVIRONMENTAL HEALTH
ORGANIZATIONAL ISSUES
Air Water
Programs Programs
Waste
Programs
fovcntoty
RCRIS
SEDM
Programs
Toxic*
Support Services - Data Processing
-------
DIVISION OF ENVIRONMENTAL HEALTH
ORGANIZATIONAL ISSUES
Air
Programs
Water
Programs
Waste
Programs
Inventory
RCRIS
SEDM
Programs
CERCUS
Support Services - Data Processing
Information Resource Management
-------
DIVISION OF ENVIRONMENTAL HEALTH
WHAT IS SEDM
• Support of Environmental Programs
• Vertical Environmental Program
• Integration of Environmental Data
-------
DIVISION OF ENVIRONMENTAL HEALTH
SEDM AS SUPPORT
• Role is Passive
• Orientation is Single Issue
• Staff are Technicians
-------
DIVISION OF ENVIRONMENTAL HEALTH
SEDM AS VERTICAL PROGRAM
• Equal Footing with Media Programs
• Limited Funding Available
• Ability to Actively Set Goals
• Limited Impact Across Media Program
-------
DIVISION OF ENVIRONMENTAL HEALTH
INTEGRATION OF ENVIRONMENTAL DATA
• Pro-active Role in Information Management
• Ability to Interact Across Media Programs
• Ability to Provide Data Integration
• Greater Funding Available
-------
DIVISION OF ENVIRONMENTAL HEALTH
ISSUES - RESOURCES
Environmental Professional Data Processing Professional
Post High School Education
Work Experience
Professional Acknowledgments
Expertise Required
-------
DIVISION OF ENVIRONMENTAL HEALTH
CONCLUSION
• SEDM is Environmental Data Integration
• EPA and States Must Examine
Organizations
Data Processing Resources
Utilization of Technologies
• State/EPA Partnership
-------
EPA Region VIII
State/EPA Data Management Conference
Wyoming
Department of Environmental Quality
(DEQ)
State Update
by James Uzzell
April 16, 1991
-------
<
a
-------
STATE OF WYOMING
DEPARTMENT'OF ENIRONMENTAL QUALITY
DrasUr

OOUVTBHGIfr

(menu
*1
—d
mur
Uad
r

Abudoml
IteUada
•4-Wta
- uc
3
r 1
M
- iAZ«un
- AML
- AM. HUB
- MANMMDrrOOMCB
- OKIKCTS
- CUNTS
- BUDGETS

1991 SEDM CONFERENCE

-------
PRIME COMPUTER NO
NEEDS ASSESSMENT NO
,i
i
EPA DATA BASES NO
HIGH SPEED DATA LINE
-------
EPA AND WYOMING
EPA SERVES A FREE PIECE OF PIE
DATA
INPUT
EPA
DATA BASES
HIGH SPEED
DATA LINE
NEEDS
ASSESSMENT
PRIME
COMPUTER
1991 SEDM Conference
J
-------
EPA AND WYOMING
Ain't no such thing as a free lunch!
STATE
$'DOLLARS
1991SEDM Conference
-------
DATA MANAGEMENT &: DEQ
80's and 90's
V«ndor Dependent File 9*i•~•r
MlddCt
TP k D«U Bwes
Vendor Dependent File Senrer
UU8
-------
-------
Findings and Recommendations of the '
Locational Accuracy Task Force
By
Jack McGraw
April 16, 1991
1
-------
BACKGROUND
The layout of this briefing is:
•Background
•Findings
•Conclusions and recommendations
•Next steps

Location* I Accuracy Taak Foroa
Purpose
"/ V
(agl
tha MM 9taartof Commlttaa www:
What should he #>a roqukad minhnom lava! at accuracy *
ad tha Agency1* tooabonai data?
How ahouid tha Aganoy Implamant ihla raqulramant?
What aotlana naad to be takan, by wham, and by what dal
EPA Laoattanai Accuracy Taak Foroa
This information is taken from
the charter of the LATF.
Introduction
Tha Laoattanai Accuracy Taak Foroa (LATF):
• Had ever 40 members from 9 atalae, tte U«Q«, v>d afl af EPA
• OMded HaaM Ma two oammNtaaa: laahrdeai and managamant
• Rapraaantad: no alandard, a r»laiid standard, and a tight
Uaad Total Quality Man^wnanf (TQM) too* and toahrdpuaa ta
(ft
gi
To identify the spatiaJ data accuracy
requirements of the Agency, the Location^
Accuracy Task Force (LATF) was formed as a
sub- committee of the IRM Steering Committee.
The 3 states represented in the LATF were
Oregon, Indiana, and Minnesota.
-------
LATF Activities
• Juna moating in Las Vagaa
• Raaoarah proven
• Nowtnbw m»ellng In D«nw
In the initial June meeting in Las Vegas, the LATF
discussed the program malic requirements for a spatiaJ
accuracy standard and the implications of such a
standard on the Agency's major information systems.
A research project was conducted using mapping
equipment in the field in order to identify the accuracies
and associated costs of 6 geocoding methods.
At the final meeting in Denver in November, the LATF
evaluated the many options and associated costs and
benefits of an accuracy standard. A consensus was
reached on the best strategy for the Agency.
Other studies conducted by the LATF included surveys of
the acceptability of a standard to States and EPA
programs, and a study of financial and informational
incentives to encourage implementation of the standard.
Need for an Accuracy Standard
Iflajar CPA data bM« contain kooot tonal data dartvod tram:
prop arty parlmatara
outfalls, alp.
Aa a raoult, anvkonmantai atamanta may ba found ki arronooua
rokttva pooMona, wrong poHttool juriadtctiona, wrong drakwga
kaatna, and k» soma ooaaa, #»a wrong ttato!

EPA Looot tonal Aoouraoy Taak Foroa
This is a particularly significant problem for FINDS
(Facility INDex System), the Agency's main repository
of facility data. Approximately two thirds of the
500,000 records in FINDS (Facility INDex System)
contain no locational coordinate data at all.
NOTE: No policy currently exists within the Agency
for how to treat polygons as a point. OIRM, however,
is currently developing guidance on this issue.
Benefits of an Accuracy Standard
rtafc managamant c
¦ a. i •• * ¦
nprew im '¦¦Diwf on
» a vtaten for tta futuro.

EPA Looaltonol Aoouraoy Taak Foroa
By allowing data to be integrated based upon location,
the Agency:
•Promotes the use of EPA's extensive data resources for
cross-media environmental analyses and management
decisions
•Enhances EPA's ability to to manage risk by associating
pollution sources with their potential impact on
vulnerable sites such as nesting areas
•Improves the reliability and acceptability of decisions
based upon locational data because the relationships
among data points will be correct.
•Coordinates the Agency's resources toward a common
goal and provides a vision for the future.
-------
FINDINGS
EPA Loeoti
lonat Aoouracy Task Foroa
Status of the Agency and States
• rUgion 3 Km ha awn accuracy standard
• Raglan 7 haa a workgroup to took into a afraf agy
• Tharo la UttJa ant>ualaam from EPA program uffloaa
• Tha RCAA and TR1 program a and t>a OW minkman groun^aalar
data atamant aal ara aoOktg tha r«r>d
• Tha majority of aHaa lack aoourata apatiol data
• Statao quootlon If additional manlaaarMfcaprovMorf.araurrant

EPA Loootlonal Aoouracy Taak Foroa
'^quires ±15 seconds (375 meters) and has
t7 5 seconds (187.5 m) in the future
a workgroup to look into (he
. constraints, and limitauons of a national
• rW > '> « -ai the program s response to an accuracy
v«Moaa*« o aaoad Acceptability Report: Program Offices
u d ;* programs already require ± 1 second (25
*»^vbp dp mm nave a strong need for multi-media
»*» p^aoa • n Systems. Suuus ai
pmme
m a p"«a aO *odwaca this same report states that "EPA officials
r»unmm Jai IB this fiscal year covers funding for GIS
rtardwwo md ***+ arc purchases, GIS activities at the Agency s GIS
i man d I uvArau and regional offices, and purchases of dau from
( ,A< )
-------
Geocoding Methods
1 — Usee automated tooia to match or Interpolate
to ooordinetee »uon ea iot>tud*1ongitud«.
MM ^¦rnotetlon — Uaee U9GS 7.S minute topographic mapa to
pinpoint looatione.
- Offloo-Baaad — Interpetetion dona later In tie office.
Ractlfted — Photographe ere overlaid on mape to
help determine tie location.
¦ ^
EPA Looeilenel Aeouraoy Taek Faroe
Geocd$Vng Methods (cont'd)
3 ?0 minutes This* will yw^d longitude, latitude,
and elevation coordinates for a point
GPS td»Hcfcn|htt mode) Uses u second receiver
or fiaed base station to help correct error*
CPA Location a I Accuracy Taek Foroa
Actually, only 3 satellites are needed to
obtain 2-D coordinates, but the 4th satellite
also improves the accuracy of the readings,
as wdl.
In June 1992. 3-D coordinates will be
available 24 hours per day.
Problems and Constraints
• DtMlcuty aih rural ad^aea matching
• Outdated mapa and photographe
• Selective av^laPMry (tA)
• SateJMo +\*U
• Radio frequency Interference, high phyaioaJ reiief (e.g.
•In rural areas, approximately 40% of attempted matches
are unsuccessful with office-based methods, particularly
address matching.
•The majority of the USGS quad maps are older than
1975, and most have not been revised. Photographs may
also be outdated, making the comparison of man-made
features difficult.
•The Department of Defense, For reasons of national
security, may at any time choose to shift satellites or
downgrade the accuracy of signals to 100 meterv This is
called selective availability or HSA.H
•High physical relief may block signals from satellites,
particularly in urban areas.
IIPA Laotiana< Accuracy Tea* Ferae
-------
Accuracies and Costs*
OEOCOQINO METHOD ACCURACY
Addraaa Matohhg 80 • 500 m
Map hterpoietien
Olflo^Baaad
FM4»Baaad
foot Mod Photograph
OPS (Autonomous - SA)
OPS (DMfarantid Mod*)
"W
SO* 1000m
25-200 m
10 - 300 m
100 - 200 m
18-100 m
COSTreitfT
17 -10 (wider)
$30 • 30 (kvhouaa)
*30 •«-
$20 * 40
940-60
$40 • 00
$70 * 170
B*M en • LATF rttfy d 91 Mft»
EPA local tonal Aoouraoy Taak Fore*
Four sites (San Gabrid, CA, Chattanooga,
TN, Nashua, MI, and Old Southington, CT)
and a total of 27 points were analyzed
against a control or known location. In the
case of the San Gabriel Basin, G PS was the
control and other methods were compared
to it for accuracy.
These findings were extracted from the
Current Findings of the LATF Technical
Working Group (draft).
Total Costs of
Locational Accuracy*
Tottl tlttt • 1,900,000
New •!(« par ym - \ 13,000
For oxbtfng attaa to ha*o accurst* tooatlonal daU, *»a ooota
eouM ba wall ovar $S0 million
For mm attaa, tha total oo«t • $6 mUUon par yaar (0 $8$ par
point).
This information was extracted from white
paper #5, entitled Economics of the Situation:
• Item I assumes no cross regulation.
• Item 2 — not all costs were measured in
dollars; some costs to the Agency were
burdened hours.
USSJ EPA Local tonal Aoouraoy Talk Foroa
-------
Conclusions
• TV>« luajra hodda *v« graatoot promt oo for OPfi technology
• ftlgndkoont stapo towards • atandard hava bo«r takan
• A otaor god for looattonai accuracy la noodad
ConbnjMi
M) EPA Local Ion a i Accuracy Teak Foroo 17
•More research needs to be done to determine the
accuracy and costs of geocoding methods, yet it is clear
that the future holds the greatest promise for GPS
technology
•To achieve cross-media integration, some EPA
programs, regions, states, and other Federal agencies
have already taken significant steps to develop a
location a! accuracy policy
•Unless a clear goal is stated, the data in the Agency's
data bases will continue to be a "mixed bag."
-
-------
Recommendation #1:
Establish a 25 meter goal
New data it considered that which it
collected after the policy it enacted and
would include data collected by tite visits,
supplied by facilities or collected to support
special programmatic needs.
Recommendation #2:
Set GPS as the standard
The Agency should concentrate on the
large scale acquisition of equipment and on
providing training.
Recommendation #3:
Define a deviation process
Using the Data Quality Objective* (DQO)
process, programs obtain a waiver from either
the latitude/longitude policy itself, the accuracy
target, the method of data collection, and/or the
time schedule by applying to the IRM Steering
Committee or some other decision official or
body.
-------
Recommendation #4:
Pursue incentives
Th« Aganoy ahouW puraua inoantiwaa ratbar »»an mlofonrwrt
Alan a to ¦oftliw* the tmrgmt moaurw&f
THm LATF hM MMlM •
~anthrea v>4 1
Irttermatien krteantivae tar tile
W
EPA Laaaitanal Aaauraoy Taak Faroa
The financial incentives proposed are:
• resource "reserve pools"
• "Lapping" resources
• new grant conditions
• Hani year carryover funds
• supplemental funds
• fees for data use
• SEDM grants
• stale grants
In form alios incentives proposed are:
SUiWEPA data sharing
pubtic/privale partnerships
coaaaoa ground with regulated facilities
Recommendation #5:
Upgrade FINDS
T>»a Aganoy ahauM
ipfaia RNM, uatof
aaWaaa matching la
The ooat ef t>a affarl la aatlmatsd at tola ttma la toe S3 rniWan.
Ttoa accuracy of the locationaJ data in
n>DS asaU improve as individual programs
• data base.
TWa cost of the effort is very preliminary at
EPA sfcould also pursue the "gateway"
Is allow FINDS to link with program
( 3B ' EPA Laoattanal Assures? Taak Faroe
Next Steps
Pursue leeuaa af:
"w
EPA « mmwf TmH Farta
•portflraly, Ihe Agency ihould:
l • ArMcfj to communicate the location*!
mtcmrmy to affected mem ben of the
¦ itrMMUl community, especially the Uatea
1 begun by OIRM on guidance for
¦g l)i« policy
•Dei 4m • lo revisit the location al accuracy issue
is U ¦ I* BKMlh*.
-------
EPA Region VIII
State/EPA Data Management Conference
Local Area Network Directions
by Steve Stoneman
April 18,1991
-------
ENVIRONMENTAL PROTECTION AGENCY
LOCAL AREA NETWORK DIRECTIONS
• EPA CURRENT LAN STATUS
• EPA CURRENT AND FUTURE PROJECTS
• LAN INDUSTRY TRENDS
-------
EPA CURRENT LAN STATUS
STANDARDS
NOVELL NETWARE 286 AND 386 O.S.
IBM PS/2 MOD 80 FILE SERVERS
IBM TOKEN RING (SOME ETHERNET)
-------
EPA CURRENT LAN STATUS
INSTALLATIONS
• APPROX 7,000 WORKSTATIONS NETWORKED
• 147 FILE SERVERS
• LAN / WAN CONNECTIVITY PILOT
WASHINGTON <4—~ RTP Mr—^ ATLANTA
-------
EPA CURRENT LAN STATUS
TYPE OF USAGE
• FILE / RESOURCE SHARING
• OFFICE AUTOMATION
• NATIONAL APPLICATIONS
• MAINFRAME ACCESS
-------
EPA CURRENT AND FUTURE PROJECTS
VALUE ADDED BACKBONE SERVICES (VABS)
LAN'S AS APPLICATION PLATFORMS
SEAMLESS CONNECTIVITY
MAINFRAME AS A FILE SERVER
-------
EPA CURRENT AND FUTURE PROJECTS
• MULTIPLE PROTOCOLS / INTEROPERABILITY
• NETWORK MANAGEMENT
• NATIONAL INFORMATION
DISTRIBUTION SERVICES (NIDS)
• GRAPHICAL USER INTERFACE
-------
LAN INDUSTRY TRENDS
PRICE/PERFORMANCE 10 YEAR TREND
COMPONENT INCREASE
• PC POWER 33 TIMES
• DISK SPEED 5 TIMES
• DISK SIZE 100,000 TIMES
• PC MODEM SPEED 32 TIMES
• LAN BANDWIDTH 10 TIMES
-------
LAN INDUSTRY TRENDS
GRAPHICAL USER INTERFACE
INTUITIVE USER INTERFACES
LAN'S AS APPLICATION PLATFORMS
DATABASE ENGINES
COOPERATIVE / DISTRIBUTED APPLICATIONS
CLIENT / SERVER ARCHITECTURE
-------
LAN INDUSTRY TRENDS
• SEAMLESS CONNECTIVITY
• MULTIMEDIA
TEXT
FILES
GRAPHICS
FAX
VOICE
VIDEO
• MULTIPLE PROTOCOL ROUTING
• NETWORK MANAGEMENT
• BACKUP / FAULT TOLERANCE
-------
5

-------
EPA Region VIII
State/EPA Data Management Conference
Aerometric Information Retrieval System -
Air Quality Subsystem
(AIRS-AQS)
Program Update
by Marlin Helming
April 17,1991
-------
Notes
i

AIRS-AQS
Overview
• Background
•Current Issues
•Impact ot the SEDM Program
•Next Steps

J?
AIRS-AQS
Past:
SAROAD
Two database*
(State and
EPA) —
not equal
AIRS-AOS
Future:
AIRS-AQS a
(EPA,
Slat*, ate.)
Goal: One
database —
complete and
accurate
-------
Notes
AIRS-AOS
System Organization
s
AIRS-AOS
Enhancements/Changes
PARS Integration Into AIRS-AOS
— July 1, 1991
— PC dlakette In April 1991
Timeframe* lor aubmlning data into AIRS-AOS:
— GO days for oontknuous monitoring data
— 90 day* lor manual monitoring data.
%
/

AIRS-AOS
Current Issues

State* need to update (correct) information h AIRS-AOS
•fte filee
Stale* need to review paat data In SAROAD and oorrecl
vTora tn AIRS-AOS
• Olaoontlnue dual ayateme
• Aaaure completeness of current data by retrieving and
reviewing reports Irom AIRS
• Utah mual begin to aubmh data electronically because
. . region can no longer reed tape*. .
-------
Notes
AIRS-AOS
Impact of SEDM Program
Connacllvtty aaubllahad lor South Dakota and
Wyoming
Entura compatibility of futura •qutpmanl purcKai
for tuita wHh ADP goals In tha atataa
knprova data tlmallnaaa.
AIRS-AOS
Next Steps
RTP & Haadquartar* will contlnua Imp tenanting
ui«^*quMt*d anhanoomanta
Rag Ion VIII A Haadqua/tara will oontlnwa providing
usar aupport
Tha National AIRS Confaranea fa achodulad to bo
ha Id Dacambar 2,1991 In Orlando, Florida.
-------
AIRS-AQS Update Procedures
>- UPDATE SOURCES
Screening File Steps Performed by AIRS USERS
Update Steps Performed by NADB (and MRB)
ALL REGIONAL OFFICES
CORRECTED FILE
State currently
ONLINE with AIRS
State NOT currently
ONLINE with AIRS
MESSAGE
File Shows
DATA
UPDATE
Status
TABLE
File
Shows
DATA
Input
Status
UPDATE
WITH DATA
FROM
SCREENING
FILES
UPDATE
CYCLE IS
COMPLETE
MRB/NAMS Coordinates data review
'ADBA" RECEIVES FILE UPDATE REQUEST
SCAN DATA to start update process
LOAD DATA
INTO
SCREENING
FILE
NOTIFY
•ADBA" THAT
FILE IS
READY FOR
INPUT
CONDUCT
EDIT OF
SCREENING
FILE
VIEW FILE
and
CORRECT
ERRORS
DATA DOES NOT
LOOK OK, data is
excluded from update,
notify Regions & States
of errors
DATA LOOKS
Include in file
Update
-------
EPA Region VIII
State/EPA Data Management Conference
j
i
i
Aerometric Information Retrieval System -
Air Facility Subsystem
(AIRS-AFS)
Program Update
by Bev Rios
April 17, 1991
-------
Notes
AIRS-AFS
Overview
•Background
• 1990 Accomplishments
•Current Issues
•Future Activities

AIRS-AFS
Overview of AIRS
GEO' Air OuaGty
COMMON Subtvatam
Subayaiam (AuS)
AIRS Facility
Subavatam
• (aVsj
AIRS-AFS
Accomplishments for 1990
AFS w«nt Into production In AprU 11SO
Rag Ion VIII bacama • DtP£CT u—t In Juna 1990
NEDS A COS data w«r* oonvartad to AF8
Montana k Colorado v ourrartfy updating and converting
thak EtS data
National AIRS Confaranea waa hald In Oanvar h Novambar
1990
Training aaaalon In Montana for 17 uaara from 4 atataa
Suta cMlca vlafta
A oompllanoa data antry to*m waa davalopad by Raglon VIU.
1
-------
AIRS-AFS
Data in AFS
Data currently In AFS:
• National Emlsalona Data Syatam (NEDS) — amissions data
from various sourcaa, plants, highways, and form fit as
• Compliance Data Systsm (COS) — oompllanea atatua and
pollutant , anforcamant, Impaction data
• Continuous Emission Monftorlng Syatam Subaaf (CEMSS) —
oontlnuoua amissions data and monitor Information
AIRS-AFS
User Support
AFS vaar access
(Mutt alraady hava NCC 10 and AIRS Account)
Training for staiaa and Rag Ion VUI
Communications with atata and EPA paraonnal
Data antry forms provldad
Raport davalopmanL
AIRS-AFS
Future Activities in Region VIII
Nonattainmanl Invantorks will ba oollaciad and raportad by
aach stata and antarad Into AFS by batch or orvlina
Complata davalopmant of an acronym Uat aagragatad by usai
Davatop an amissions Invantory data arrtry form
AFS will ba tha official rapoahory lor Stata fen p lam ant all on
Plan (SIP) amission invantory data.
-------
Goal
Uy god It to ivv* AFS u««r» to th» bast of my abllhy. I
otlif support In training naw uaars, AFS eonoarna, report
consultation and davalopmarvL
Who do you call for AFS Information?
EUv Riot (303) 294-7664 oonvnarclaj
-------
<$
-------
AIRS-AFS
Development Objectives
GO
Integrate
NEDS
CDS
EIS
Handle
"Common"
Data
Screens
Be
perceived
as ONE
SYSTEM
BE EASY
TO USE

Handle
post-87 SIP
Emissions
Inventory
Require.

Provide
at least
current
features
Satisfy
STATES'
Require-
ments
BE
FLEXIBLE
Be able to
retrieve
by CAS
Number
Store any
level of
emissions
Be able
to store
TOXIC
DATA
Provide
true
interactive
processing
Visiting
Generate
Workfiles
Handle
"CEM"
Subset
Require.
Handle
the
•'NARS"
Require.
Provide
CDS'
"Flexible
Report"
Go to
Jail
Just
_
J
f

-------
AIRS-AFS
Air Facility Subsystem:
AFS contains emission and compliance data
Collected at individual facilities
Monitored by EPA and state agencies
Over 400 data fields pertaining to plant, stack, point and segment level information
One plant can have many point records in which pollutant and emissions data are
maintained.
Structure Levels
Plant
Stack
Point
Segment
Physical location of plant or facility
(Contains data associated with the plant as a whole)
Stack or vent with emissions into the air
(Pertains to physical places within a plant)
Physical point that results in pollutant emissions
(Pertains to physical places within a plant)
Components of a process that are used in computation of emissions (fuel type)
(Deals with data for a support of point)
Capabilities
Update Edit, add and change data
Browse Look at all data
Report Default and ad hoc report features
Utility System maintenance, deletes, archives, swaps, print table data, etc.
Meets Federally Reportable Data Commitments
Supports national air pollution control and monitoring programs for:
SIP State Implementation Plans
NSPS New Source Performance Standards
NESHAP National Emissions Standards for Hazardous Air Pollutants
PSD Prevention of Significant Deterioration
NSR New Source Review
-------
AFS ROAD MAP: UPDATE
308
asbestos
CONiSACTOB
303
AIR PROGRAM
pollutant
310
ASBESTOS
performance
33 4"
3J
3 •
HON
TOR
EXCESS EMISSION
REPORTING
309
ASBESTOS
UNDFUL
332
337
CUmENf
•HON 1 TOR-
337
3
32
AIR Pf
-PL/
tOGRAH
wu-
Alfl PROGRAM
-P0IN1-
COMHtNl
-EX. LM1S. RPT-
-O-
307
cow n r
-PLANT-
ACTION
-PLANI-
COWirNf
-ACT10N-
337
COMMENT
-POINt-
337
COMMENT
-ACTION-
PLANI GENERAL
305
MAILING LABEL
304
FCC v
CERTIFICATION
301
POL I U1 AN I
-Pi AMI-
SIACK GENERAL
322

321
C UMMlMI
-SIACK-
PUI 1 U 1 AIII
-SIACK-

330
POINT GENERAL
33 S
TANK
3
16
ACT
-PO
ON
NT-
pollutant
-POINT-
340
SCGMLNI GENERAL
1
i

343

3 42

341
COMMENT

CHLMlCAl

not liii aiif
-SEGMENT-

-segment-
T?C
TRC Bnvironmmntal Comuhontt, Inc.
-------
EPA Region VIII
State/EPA Data Management Conference
Federal Reporting Data System
(FRDS)
Program Update
by Rich Gomez
April 17, 1991
-------
Notes
18
FRDS
Status FRDS-II
Compliance tracking eystsms:
CO — Modifying Region Will's system
MT — Modified Alaska's system
NO — Revising thefr own previously developed system
SO — Developing their own »y*tem
UT — Revising thair own previously developed system
WY/kidlane — Completed thdr own system.
FRDS
FRDS Issues
SWTR/TCR Rules ara oomplei and difficult to Interpret
Phase li/Laad Rula will require a larga amount of reeourcea
Revised Raportlng Requirements will ba effective
Oooamber 1991.
todhrtduaJ programs have varying data technology naada:
PC vareua mainframe eupport
Programming support
Procurement of AOP equipment.
FRDS
Role of SEDM
High level EPA managers working with State managara
Aaaiatlng tha atataa with now technology: hardware,
software, and communication*
Assisting stales wtlh training In now technology
Completing communication hock Hi pa (Wide Area
Networks)
• To Raglan VUI
• ToNCC
Networking the various programs— Orinkkig Water with
Suparlund, AIRS, NPDES, RCRA, LUST, eta
-------
STATUS FRDS-II
CO HAS BEEN PROVIDED WITH THE REGION VIII COMPLIANCE TRACKING
SYSTEM AND IS CURRENTLY REVISING THE SOFTWARE TO MEET THEIR
OWN SPECIFIC REQUIREMENTS.
MT HAS MODIFIED THE ALASKA COMPLIANCE TRACKING SYSTEM TO MEET
THEIR OWN PROGRAM NEEDS.
ND WAS THE FIRST STATE IN REGION VIII TO DEVELOP THEIR OWN
COMPLIANCE' TRACKING SYSTEM' AND IS ON TRACK- FOR REVISING
THEIR SOFTWARE TO MEET THE NEW SWTR/TCR RULES.
SD HAS COMPLETED DEVELOPING THE INVENTORY PORTION OF THEIR
COMPLIANCE TRACKING SYSTEM AND WILL MEET THE DEADLINE OF
DECEMBER 1991 FOR DEVELOPMENT OF THE VIOLATIONS/ENFORCEMENT
PORTIONS
UT WAS THE SECOND STATE IN REGION VIII TO DEVELOP THEIR OWN
COMPLIANCE TRACKING SYSTEM AND IS ON TRACK FOR REVISING
THEIR SOFTWARE TO MEET THE NEW SWTR/TCR RULES.
WY/INDIANS HAS COMPLETED THEIR COMPLIANCE TRACKING SYSTEM AND
WILL REPORT TO FRDS IN THE NEW FORMAT IN THE NEXT
REPORTING PERIOD
* ALL MODIFICATIONS REFERRED TO ARE TO ACCOMMODATE THE NEW
FRDS-II FORMAT AND REQUIREMENTS.
APRIL 1991
1
-------
FRDS ISSUES
ISSUES
o SWTR/TCR RULES: EFFECTIVE JANUARY 1991, THESE TWO
RULES ARE VERY COMPLEX AND THE STATES HAD DIFFICULTY
INTERPETING THE RULES DURING DEVELOPMENT OF THEIR
SOFTWARE TO REPORT THIS DATA. WE EXPECT THIS DATA TO
BE INCLUDED DURING THE MAY 199 1 REPORTING PERIOD.
O PHASE 11/LEAD RULE: . THE.. STATE. ADMINISTRATIVE. TRACKING . .
REQUIREMENTS ARE GOING TO REQUIRE A LARGE AMOUNT OF
RESOURCES AND THE STATES WILL NEED TO INCREASE THEIR
RESOURCE COMMITMENTS.
O RRR: THE REVISED REPORTING REQUIREMENTS EFFECTIVE DATE
IS DECEMBER 1991. PER A RECENT ODW MEMORANDUM, SIX
STATES HAVE BEEN IDENTIFIED THAT WILL NOT BE ABLE TO
MEET THE DEADLINE DATE. NONE ARE IN REGION VIII.
o TECHNOLOGY: STATE MANAGERS NEED TO BE AWARE OF
INDIVIDUAL PROGRAM NEEDS IN THE AREA OF DATA
TECHNOLOGY.
A STATE ADP FACILITY MAY BE CONCERNED WITH A MAINFRAME
ENVIRONMENT, WHEREAS, AN INDIVIDUAL PROGRAM MAY BE PC
ORIENTED WITH NO NEED FOR THE MAINFRAME.
INDIVIDUAL PROGRAMS MAY NOT HAVE THE TECHNICAL SUPPORT
REQUIRED TO PROGRAM SOFTWARE. SOME STATE ADP SHOPS
HAVE THE PROGRAMMING EXPERTISE, BUT REFUSE TO RECOGNIZE
OTHER NEEDS OUTSIDE OF THEIR SHOP.
STATE PROCUREMENT OF ADP EQUIPMENT IS AN ISSUE OF
CONCERN. STATES SHOULD REVIEW THEIR PROCUREMENT
PRACTICES TO ASSURE THEY ARE OPEN TO NEW TECHNOLOGY AND
VARYING PROGRAM NEEDS.
APRIL 1991
1
-------
SEDM ROLE
o HIGH LEVEL EPA MANAGERS WORKING WITH STATE MANAGERS
o ASSISTING THE STATES WITH NEW TECHNOLOGY
HARDWARE/SOFTWARE/COMMUNICATIONS
O ASSISTING STATES WITH TRAINING IN NEW TECHNOLOGY
o COMPLETING COMMUNICATION HOOK-UP's (WIDE AREA NETWORKS)
TO REGION VIII
TO NCC
o NETWORKING THE VARIOUS PROGRAMS
DRINKING WATER WITH SUPERFUND, AIRS, NPDES,
RCRA, LUST.
APRIL 1991
1
-------
Federal Reporting Data System (FRDS-H)
Data Element Dictionary
Section I
FRDS-ll Data Base Definition
-------
1.1 Typical FRDS Information Flow
The illustration presents the many ways transactions entered into FRDS-DE can be
relayed to the mainframe at FRDS-M. After the transactions are entered they can be
transmitted directly to Research Triangle Park (RTP) via telecommunications, or they
can be loaded onto floppy disks and sent to the appropriate Regional Office. Very large
transaction files can be sent via disk to FRDS-II User Support and transmitted to RTP via
9-track tape.
Optional
Flow
Multiple
Diskettes
Magnetic
Tape
NM
FRDS-DE
D skettes
AK
TX
SAMPLE FRDS-DE INFORMATION FLOW
(Using States of Region VI)
Exhibit 1
I- 2
-------
Federal Reporting Data System (FRDS-II)
Structure Chart
as of October 1« 1989
evel 0
uvel 2
evel 3
PMS-SE-TREATMENT-
LEGEND
evel
CI 350 9
HON
COMPLIANCE
PROFILE
NCP-
C1200 a
LIIIK TO
VIOLATION
CI 180 7
LINK TO
ENFORCEMENT
VIO-LINK-
C3000 10
VARIANCE
EXEMPTION
DATA
VE-
C1000 7-9
NON
COMPLIANCE
DATA
NCO-
C600
SERVICE
AREAS
PWS-SERV-
C400 2
SOURCE
ENTITY
INFO
PWS-SE-
C300
ADDRESS
DATA
C900
PWS-IIIST-
HISTORY
C4000 11
STATE
DISCRETION-
ARY DATA
SOD-
DBA
OBA-
PHS-VISIT-
C700 I
ON-SITE
VISITS
C500 3
GEOGRAPHIC
AREAS
SERVED
PWS-GA-
CO
STATE
SUMMARY
ST-
1-12
C1200 8
ENFORCEMENT
DATA
C1100 7
VIOLATION
DATA
VIO-
C100 1-12
PUS
SUMMARY
PWS-
C1300 9
NCP
C0N1R0L
NODE
ll/A
VE-SCHED-
C3100 10
SCHEDULE
Record Number
Faraily
Record
Contents
Onto Element Prefix
Effective Data: 10/01/89
Release Number: 1.00
Pago: I - 1
-------
III. FRDS-II DATABASE CONCEPTS
FRDS-II has been designed to increase the flexibility of FRDS to
meet the present and future information demands envisioned by the
PWSS program. The neu system will accommodate five major
modifications in addition to the incorporation of many neu features.
The major modifications include: Database Integration; Non-
compliance tracking; SHC Identification and Tracking; Historical
Data Retention, and Storage of State Discretionary Data.
A. Database Integration
As noted in Section II, the original FRDS concept uas to
generate a totally neu, . and separate FRDS database for each
submission of data from primacy agencies. This has resulted in the
generation of 12 different FRDS databases, each containing similar
information on inventory and a.summary of each fiscal year's actions
(violations, variances £ exemptions and enforcement actions). In
contrast, upon implementation FRDS-II will contain a single
inventory representing BOTH the most recent inventory submission by
primacy agencies (henceforth referred to as the "Current" inventory)
and all of the prior year inventories ("Historical" inventory) uhich.
are not included in the CURRENT inventory, plus all of the actions
dating back to FY80 (Chemical and Radiological contaminant relate"1'
actions will be retained for 20 Years). This "continuum" databasj
will then maintain approximately 8 years of actions (except as note
in the preceding sentence) uith neu quarterly reported actions being
added, and old actions (reported more than 8 years prior to any
FRDS-II update) being archived.
1. Generating the Continuum Database
Over the past feu years, tuo major options for database
integration have been analyzed; a) matching on Public Water System
Identification Number (PUS-ID)* and b) a more complex matching on
substantive values (including PUS Name, Address, etc.). The results
of this analysis vary some from one primacy agency to another,
however, utilizing either method, approximately 852 of the
"historical" information appears to match correctly uith the latest
inventory submission. Therefore the simpler PWS-ID match method for
integrating, databases uill be used in all cases. Primacy agencies
should be mindful of this procedure and, in cases uhere PUS uere re-
numbered, or PUS-IDs reused for different PUS(s), they should
provide EPA uith a machine readable conversion table for each fiscal
year in uhich the re-numbering occurred.
ffective Date: 10/01/89
Release number: 1.00
Page: VII - 62
-------
During the period from February-July, 1989, 10 separate
Regional FRDS-II Training databases uill be created using the method
described herein. During this period primacy agencies uill have an
opportunity to review and evaluate their states data and make any
appropriate changes the the FRDS 1.S databases or provide EPA with
an appropriate PWS-ID conversion table.
a. Inventory Integration
Initially, all corresponding inventory data from
the most current FRDS 1.5 database uill be
converted to the FRDS-II database format and
loaded into the FRDS-II database. Then proceeding
backwards, a fiscal year at • a time, each preceding
FRDS 1.5 fiscal year database uill be read and
matched by PWS-ID Kumber with the data already in
the FRDS-II database. Any PWS record found in a
FRDS 1.S database and HOT found in the FRDS-II
database uill be: converted to FRDS-II database
format and inserted into the FRDS-II database.
However, it uill be assigned an "Historical"
PWS-STATUS (see FRDS-II Data Element Dictionary)
code to indicate that the PWS is no longer
considered part of the current, most recently
submitted inventory. Inventory which DOES match
on PWS-ID Number will retain the most recently
submitted PWS names, address and locations, source
information, geographic areas served and service
areas. Further, these PWSs uill maintain a- record
of major changes is data element values (e.g.
PWS-SYSTEM NAME, Population Served, etc) and a
history of any time the PWS was identified as a
SNC. PWSs in FRDS 1.5 databases which indicated
having a turbidity limit greater than 1.1 will
have a turbidity waiver action generated for the
FRDS-II database. Also, a record of all prior
On-site visits (Date of Last Sanitary Survey) will
be retained as well as a record of when and what
significant inventory changes were reported (e.g.,
in 1984 a PWS changed from being a surface water
PWS to a ground water PWS). Lastly, the reader
should note that because of the similarity of data
collected on Sources and Entry Points, these
database records will be combined into a single
record type during - the- inventory conversion
process.
effective Dates 10/01/89
Release number2 1.00
Page: vil - 63
-------
b. Actions Integration
All unique actions (violations, variances £
exemptions and enforcement actions) from the 10
prior years of data will be converted and merged,
by PUS-ID Humber, into the FRDS-II database.
Occasionally duplicate actions have appeared in
the same, or different, FRDS 1.5 database(s). In
those cases where duplication is obvious, only the
most recently reported action will be inserted
into the FRDS-II database. Each FRDS 1.5 action
to be inserted into FRDS-II will have its action
identification number (violation ID, V£E ID, or
Enforcment ID) prefixed with a 2 digit fiscal year
code representing the FRDS 1.5 fiscal year
database in which the original action appeared
(e.g., violation ID number V0003 in the fiscal
year 1983 database uould appear as 83V0003 in the
FRDS-II database).
Further, a fiscal year and insert date
representing the. fiscal year in which the action
appeared and the first day of the fiscal year
respectively, will be added to each action record
inserted into the FRDS-II database-.
In addition to inserting unique actions into FRDS
II, the conversion software will attempt to
establish the correct relationship between 1) a
violation and it's related enforcement actions,
and 2) an enforcement action with its related
violations.
2. Value Conversion
During the database integration process, any code value
conversion (e.g., new enforcement action codes, pws-owner type, PUS
Service Area Characteristics, etc.) will be performed automatically
where possible. The FRDS-II Data Element Dictionary, Section V £
VI, provides more specific information, concerning value conversion.
3. Role of the Primacy Agencies
Primacy agencies should take special note to inform
FRDS-II User Assistance of any changes which have been made to the
PWS-ID numbers over the past 10 year period and provide a machine
readable conversion table depicting the old PUS-ID to new PWS-ID
conversion. Attention to this detail is CRITICAL to insure t]
FRDS-II correctly merges all inventory and compliance related d;
into the continuum database.
Effective Date: 10/01/89
Release number: 1.00
Page: VII - 6
-------
During "the Regional training period each primacy agency
will be requested to review the results of the FRDS-II database
integration process for their respective States to identify, on a
PWS specific basis, if any integration of inventory or actions took
place incorrectly. This effort is absolutely critical to the
successful completion of the conversion process. It is recommended
that Primacy agencies initially focus their attention on validating
the FY88-FY89 conversion/integration process and the correct
integration of all Chemical and Radiological violations from FY86-
FY89 .
Some information contained in FRDS 1.5 databases uill
not be incorporated in the FRDS-II database. However, primacy
agencies may request in writing to FRDS-II User Assistance that
specific data elements be included in FRDS-II as State Discretionary
Data. This list of data elements slated for deletion from FRDS-II
(which existed in FRDS 1.S) is detailed in Table Sb of the
aforementioned Water Supply Guidance V-2.
B. Non-Compliance Tracking
The Non-Compliance Profile (NCP) database records generated
by FRDS-II constitute a major neu feature of FRDS-II. These
database records are generated by FRDS-II and require no additional
input from primacy agencies or EPA Regions. The automatic
generation of the database records provides a capability for
multiple and/or overlapping, views of non-compliance related events
covering multiple time periods per PWS. Because this document
principally addresses data conversion issues, and NCP records will
be generated from existing data within FRDS-II, a more comprehensive
discussion of this capability is included in the FRDS-II System
Concept Guide .
C. SNC/AO/Exception Tracking
FRDS-II is being developed to support an automatic
determination of Significant Non-Compliers (SNCs) in accordance with
whatever guidance ODM has in effect at the time that SNCs are to be
determined. Although not currently implemented, FRDS-II has the
capability to maintain (separate and apart from primacy agency
submitted data) PWS•specific information pertaining to EPA issued
enforcement actions, administrative orders (AOs) and PWSs which
have been identified as exceptions.
As in the case with the NCP tracking noted in Section III,
B above, this capability was unavailable in FRDS 1.S and therefore
is covered in the Systems Concept Guide.
Effective Dates 10/01/89
Release number: 1.00
Page: VII - 65
-------
D. Historical Data Retention
1. FRDS 1.5 Databases
During the Regional training period each EPA Region may
request that a maximum of 2 States data be maintained concurrently
with the FRDS-II database during the Regional training period.
However, upon completion of the Regional .training period a total
conversion to FRDS-II will be performed again from the FRDS 1.5
databases. Three months after the total conversion to FRDS-II, all
FRDS 1.5 databases and system software Mill be archived, and
retained indefinitely to assure access to the original FRDS 1.5 data
and databases.
2. FRDS-II Database
As noted earlier, uhenever significant changes to the
integrated FRDS-II inventory are detected, historical records uill
be inserted into the FRDS—II database highlighting the nature and
date of change. This creation of an historical audit trail of major
inventory changes uill take place both during the- database
integration period# and, as a function of normal operations uhei
FRDS-II becomes the database of record. Section III-B of the FRDS-'
II Data Element Dictionary (DED) contains the current list of data
elements for which a value change will automatically trigger the
insertion of an historical record for the affected PWS in FRDS-II.
:fective Date: 10/01/89
Release number? 1.00
Page-' VII - 66
-------
FEDERAL REPORTING DATA SYSTEM
I. OVERVIEW
The Federal Reporting Data System (FRDS) is a
management information system administered by the EPA Office of
Drinking Water (ODW). Its purpose is twofold: 1 ) to collect data
pertaining to Public Water Systems (PWS) serving a population of
25+ in this country and annually report to Congress on the
compliance rate of PWS1s in regard to federal drinking water
regulations; and, 2) to be used as a management tool by EPA to
provide oversight of each States Drinking Water Program to
improve the rate of compliance within each state.
II. History
FRDS was developed as the second step in a two-part
program administered by the EPA ODW to monitor state compliance
with the Safe Drinking Water Act (SDWA) of 1974 . The first step
involved the development of the Model State Information System
(MSIS), an automated system mad aviailable to the States and EPA
Regional Offices, which satisfied the Federal reporting
requirements under the SDWA. The system underwent a major
modification in FY90 and brought on line in FY91 as FRDS-II, this
version of the system was not distributed down to the State(s)
level. A Data Entry Package was developed for both Regional and
State use for transferring FRDS update data in an acceptable
format.
The FRDS User Community includes the following:
o EPA Office of Drinking Water
o FRDS National Data Base Administrator (NDBA)
o FRDS Production Control, Planning Research
Corporation (FRDS Contractor)
o FRDS Regional Data Base Administrator
o EPA Regional Users
o States
. Each FRDS user may perform one or more.functions within -
FRDS, as designated by the NDBA.
III. DATA ORGANIZATION
FRDS provides EPA with a centralized data base of
public water information together with data edits, data base
1
-------
updates, and standard reporting capabilities. The data base is
organized under the System 2000 data base management system
(DBMS) which, in addition to providing a structure for the data
base, provides the FRDS user with an English language retrieval
system and an ad hoc reporting generator.
FRDS operates on an IBM mainframe computer system located at
EPA National Computer Center (NCC) in Research Triangle Park,
North Carolina. The System accepts public water system (PWS)
data in two formats:
o PC floppy disk(s ) 3. 1/2 or 5 1/4 inch High Density -
mailed to the Region VIII DBA for transmission to
the National Computer Center.
o Direct electronic transmission by the individual
State(s) to the National Computer Center (NCC) IBM
mainframe or to the Region VIII Prime mini
computer.
Five types of data are collected for input to FRDS or
generated by FRDS:
o Inventory - includes PWS identification, source
and geographical data.
o Violations - includes data that apply to a
violation of the Safe Drinking Water Act by a
Public Water Supply System.
o Enforcement Actions - State and/or Federal actions
taken against a PWS for violation of the Safe
Drinking Water Act.
o Variance and Exemption - this is information that
applies to EPA authorized exceptions to the
standards which are granted to a PWS.
In addition, summary statistics for each state are generated
and maintained within the FRDS data base. The FRDS user manuals
contain all the necessary information to enable a user to input
data to the FRDS system in the proper DTF format, perform
required editing, and generate standard and ad-hoc reports.
The FRDS NDBA and FRDS Production Control Group perform the
necessary data base maintenance functions, including updates,
backup, and archiving/restoring data. The FRDS NDBA also
provides assistance to the user in accessing the FRDS system and
in resolving any problems or discrepancies encountered.
2
-------
IV. RETRIEVAL CAPABILITIES
o The System produces standard reports required for
analysis of program oversight and other related uses.
Additionally, through System 2000, an ad hoc report
generation capability is provided.
o There are currently 14 standard reports that can be
obtained. Please refer to the handouts for a few
examples of these reports.
o Additionally, the system has an on-line interactive
function in which the user can supply selection
criteria and obtain information through several post
processing options.
V. SYSTEM PROBLEMS
o The system is currently written in System 2000 (S2K)
applications software which is no longer supported by
the Agency and likely will be removed within 2 years.
o Because of the implementation of FRDS-II in FY90, the
States have had a difficult time in re-tooling their
own Compliance Tracking Systems to meet the new Revised
Reporting Requirements and new Surface Water Treatment
and Total Coliform rules adopted under SDWA authority.
o Of the seven States (including Indian Lands) in Region
VIII, only three of the States are reporting
Enforcement Actions, and a few of the States are not
reporting Turbidity, Chemical, and Radiological
violations on a quarterly basis.
o Inability to create flat files to download to Regional
PC's for further data manipulation, graphical displays
of data, etc.
VI. FUTURE ENHANCEMENTS
o A Needs Assessment Group is currently being organized
to provide a clear direction in identifying ODW's real
information needs. Also this group will identify the
applications software that will be used for replacement
of the S2K DBMS when FRDS III system development
begins. It is estimated that the.whole, process through
implementation will take approximately 40 months.
o A Data Entry System for PC's was developed for the
States and Regional offices to assist them in providing
quarterly data in the proper input format until their
new Compliance Tracking Systems are on line.
3
-------
o With the development of the new Compliance Tracking
Systems and a more refined Data Verification (Audit)
process, the problem of non-reporting of violations and
enforcement actions will be taken care of through
attrition.
o A Capability to download files to a PC is being
developed.
o Interaction with other EPA databases (and eventually
non-Agency databases) -will enable a- sharing of
information that may be enlightening and beneficial to
all programs involved.
VII. Contact Person
For information regarding the FRDS process, contact Rich
Gomez, DBA, Drinking Water Branch at ( 303) 293-1409, (FTS) 330-
1409 or 1-800-759-4372, ext. 1409.
April 1991
4
-------
EPA Region VIII
State/EPA Data Management Conference
Grant Information and Control System
(G1CS)
Program Update
by Minnie Adams
April 17, 1991
-------
UNITED STATES ENVIRONMENTAL PROTECTION AGENCY
WASHINGTON, D.C. 20460
MAR I 9 1991
OFriCc OF-WATE3
MEMORANDUM
SUBJECT: 1991 GICS User Group Meeting
FROM: James A. Hanion, Director
Municipal Construction Division
TO: Municipal Construction Program Managers
Reaions l-X s
I
I am pleased to announce that the 1991 GICS User Group Meeting will be
held July 17 and 18 at the Holiday Inn/Union Square in San Francisco.
California. There will also be a GICS Executive Committee meeting held on
Tuesday, July 16 for Executive Committee members only at the same hotel. Also
End User Training (Report Writer etc.) is scheduled for Monday, July 15 at the-
Region IX office. Additional meetings held will be the Regional GICS Coordinators
meeting at the Region IX office on July 15 and the State Caucus meeting on
July 16. The hotel is in an excellent location in downtown San Francisco.
The meeting will provide an interesting look at the implementation of the State
Revolving Fund (SRF) program in GICS both at the national and state levels. A
preliminary agenda is attached for your information. Also attached is the concurrent
sessions registration form to FAX directly to the contractor staff.
In addition, hotel reservations must be made directly by calling the Holiday
Inn/Union Square at (415) 398-8900. The single room rate per night is $78 with the
use of a government or state issued credit card or $86.58 (single) including tax.
However, room tax will not be charged if you use a government or state issued
credit card. In making your reservation, please indicate that you will be attending the
EPA GICS User Group Meeting. Please make your hotel reservations by
June 8.
.WH-547
Printed on n~-:, £lj-j
-------
-2-
A registration form is attached to provide our conference contractor with your
registration information. Please return this form by mail or FAX to 202-646-62i0.
There will be a registration fee of S40 payable at the meeting. This includes the
luncheon on July 17 and Federal employees are reminded that seven dollars for tms
luncheon should be deducted from their per diem. If you have any questions,
please contact Sandra Duncan of my staff at (202) 382-7272.
I look forward to seeing you in San Francisco.
Attachments
cc: Program Management Coordinators
GICS Coordinators
GICS Executive Committee Members
SRF Coordinators
State Representatives
-------
3/5/91 EPA GICS USER GROUP MEETING DRAFT
JULY 15-16, 1991
The EPA Regional Office
75 Hawthorne Street
San Francisco, CA 94105
GICS REPORT WRITER TRAINING will be conducted by the Office of Information Resources
Management (OIRM) staff at the EPA Region IX Office.
[NOTE: The GICS Report Writer Training will be conducted in the morning and afternoon.
You need only attend ONE session. Each session can accommodate 18 persons (two per
terminal). The Regional GICS Coordinators will be contacted at a later date to determine
the attendee list for each session.]
COURSE DESCRIPTION: The GICS Report Writer provides end-users with the automated
capability to generate GICS reports without having programming expertise. The Report
Writer enables users to create online or batch reports using a series of input screens. The
user supplies sort, select, and output criteria to efficiently produce reports.
PREREQUISITE: Attendee should be familiar with the Construction Grants/State Revolving
Fund Program data elements, mainframe logon procedures and have a userid for Natural 2.
If you do not have a userid, please contact the Regional GICS Coordinator or
Connie Dvvyer for assistance at 202-382-5300.
Monday, July 15. 1991
9:00 - 12:00 GICS Report Writer Region IX, Information Center
Session 1 13th Floor
1:30 - 4:30 GICS Report Writer Region IX, Information Center
Session 2 13th Floor
REGIONAL GICS COORDINATOR MEETING
9:00 - 1:00 GICS Coordinators' Meeting Region IX Conference Rooms
American Samoa/Guam Rooms, 1st Floor
[Contact Maryane Tremaine at 8-276-7430 for information.]
STATE CAUCUS MEETING
Tuesday. July 16. 1991
1:30 - 5:30 State Caucus Meeting Region IX Conference Rooms
American Samoa/Guam Rooms, 1st Floor
[Contact Pam Robinson/Janice Carter (South Carolina) at 803-734-5223 for information.]
-------
3/5/9).
TIME
TOPIC
EPA ANNUAL GICS USER GROUP MEETING
JULY 17-18, 1991
THE HOLIDAY INN/UNION SQUARE
480 Sutter Street
San Francisco, CJX 94102
PRELIMINARY AGENDA
LEADER(S)
DRAFT
Wednesday. July 17 -- Union Square Ballroom/Mezzanine Level
8:00 - 8:45 Registration
8:45 - 9:00 Introductory Remarks/Meeting Overview
9:00 ¦ 9:10 Welcome to San Francisco
9:10 • 9:30 Office of Water Priorities
9:30 ¦ 10:00 State Caucus Summary
10:00 - 10:15 BREAK
10:15 - 11:45 State SRF Program Management
11:45 - 12:15 Summary of Ff 1991 Executive Committee Actions
Grant & Loan Operations Workgroup
Systems Issues & Data Quality Workgroup
Reports & Select Logic Workgroup
12:30 - 2:00 LUNCHEON - Union Square Ballroom
Introduction of Speaker
TO BE ANNOUNCED
Division DirectorlMCD
Region IX Representative
Office DirectoriOMPC
Pam Robinson/South Carolina
SRF Staff
State SRF Managers
Jannie Latla
Susanne Mann
Virginia Jones
Maryane Tremaine
Division DirectorlMCD
To Be Announced
2:00 • 3:15 Concurrent Sessions
Sutter I A1. SRFIGICS Information Awareness Seminar
• Data Entry & Payment Screens
Cable Car B1. GICS On-site Training Center
Union Square C1. To Be Announced
3:15 - 3:30 BREAK
3:30 - 4:45 Concurrent Sessions
Sutter I A2. SRFIGICS Information Awareness Seminar
• Data Entry & Payment Screens
Cable Car B2. GICS On-site Training Center
Union Square C2. To Be Announced
4:45 Adjourn
SRF/PMB/OIRM Staffs
ADP Staff
To Be Announced
SRF/PMB/OIRM Staffs
ADP Staff
To Be Announced
-------
3/5191
TIME
TOPIC
EPA ANNUAL GICS USER GROUP MEETING
JULY 17-18, 1991
THE HOLIDAY INN/UNION SQUARE
430 Sutter Street
San Francisco, CA 94102
PRELIMINARY AGENDA
UEADER(S)
DRAFT
Thursday. Jutv 13 -- Union Square Ballroom/Mezzanine Level
3:30 - 9:00
9:00 - 10:00
10:00 ¦ 10:15
10:15 - 11:15
Cable Car
Sutter I
Union Square
11:15 - 12:30
Cable Car
Sutter I
Union Square
12:30 ¦ 1:30
1:30 - 2:00
2:00 - 3:30
3:30 - 4:00
OIRM/EPA ADP Initiatives
NOPO ADP Initiatives
- Telecommunications/System Status
- AD ABAS! Natural 2 Enhancements
- IBM Mainframe Enhancements
GICS Modernization Overview .
¦ GICS Status
BREAK
Concurrent Sessions
B3: GICS On-Site Training Center
D1: Prototype of SRF Workstation Demo
El: CompletionlCloseout Strategy
Concurrent Sessions
B4: GICS On-Site Training Center
D2: Prototype of SRF Workstation Demo
E2: Completion/Closeout Strategy
LUNCH (OUT)
GICS Information Systems
Management Council Activities
Pollution Prevention Program lor Region IX
Permit Compliance System (PCS)
To Be Announced
Jim Obenschain
Central Data Base Administrator. OARM
Connie DwyeriOIRM
ADP Staff
Connie DwyeriOIRM/Colorado
Branch Chief/Operations Br.,MCD
ADP Staff
Connie Dwyer/OIRMlColorado
Branch Chief/Operations Br.:MCD
Harvey Pippen
Director, Grants Admin. Division
Region IX Representatives
Steve Martin. Chief
Compliance Information and Evaluation Branch
Enforcement Division
4:00
Conclusion
Division Dlrector/MCD
-------
Schedule ol Events
Wednesday, July 17, 1991
Time
General
Session
Luncheon
Concurrent
Session A
Concurrent
Session 13
Concurrent
Session C
8:00-12:30

x (all)

12:30-2:00

X (all)

2:00-3:15
3:30-4:45

A1: SRF/GICS
Information
Awareness Seminar
A 2: SRF/GICS
Information
Awareness Seminar
B1: GICS On-site
Training Center
B2: GICS On-site
Training Center
C t:To Be
Announced
C2:To Be
Announced
Thursday, July 18, 1991
Time
General
Session
Luncheon
Concurrent
Session B
Concurrent
Session D
Concurrent
Session E
8:30-10:00
10:15:11:15

X (all)

B3: GICS On-Site
Training Center
D1: Prototype of
SRF Workstation
Demo
E1: Completion/
Closeout
Strategy
11:15-12:30.
12:30-1:30

X (On your own)
B4: GICS Oil-Site
Training Center
D2: Prototype ol
SRF Workstation
Demo
E2: Completion/
Closeout
Strategy
1:30-4:00

X(all)

-------

aim arim
GICS ON-SITE TRAINING AND DEMO CENTER
GICS USER GROUP'MEETING In San Francisco, California
Cable Car Room, Mezzanine, Holiday Inn/Union Square
2:00-3:15 and 3:30-4:30 Wednesday, July 17, 1991
PC1 TM1 TM2
SRF Data Base
Information
OMPC/Delegation Br.
Kit Farber
SRF & CG Data Entry
Screen
OIRM Stall
Report Writer
OIRM Stall
TM3
SRF & CG
National Reports
MCD Staff
TM4
"M5
To Be Announced
GICS Questions and
Answers
OIRM Stall
- inrrafrnrwrr

» ....
-------
GICS ON-SITE TRAINING AND DEMO CENTER
GICS USER GROUP MEETING In San Francisco, California
Cable Car Room, Mezzanine, Holiday Inn/Union Square
10:15-1 1:15 and 11:15-12:30 Thursday. July 10, 1991
PCI IM1 TM2
GIRD
Dictionary
Ross Hardier
SRF & C-G Data Entry
Screen
OIRM Stall
Report Writer
OIRM Stall
TM3
TM4
TM5
SRF& CG
National Reports
MCD Staff
To Be Announced
GICS Questions and
Answeis
OIRM Stall

-------
Registration Form
GICS Annual User Group Meeting
July 17-18, 1991
Holiday Inn/Union Square
San Francisco, California
I
. i
P'92s8 crirr csrsfuHv: f
i.
i. Name: !
2. Full Position Title:
3. Affiliation:
4. Mailing Address:
5. City:
6. State: 7. Zip:
3. Telephone:
9. Concurrent Sessions Attending:
1. 2.
3.
To Prereaister FAX this form to 202-6^6-6210 or mail to:
Karen Cowden, Roy F. Weston, Inc.
955 L'Enfant Plaza Sixth Floor
Washington, D.C. 2002^
For Hotel reservations olease call the Holiday Inn/Union Square at ^15-398-3-900 no
later than June 8. 199'.
If vou have any questions, olease call Sandra Duncan at 202-382-7272.
-------
COLORADO DEPARTMENT OF HEALTH
OFFICE OF HEALTH AND ENVIRONMENTAL PROTECTION
OHEP DISCUSSION PAPER
MARCH 1991
KLEROS SYSTEM CONCEPTS
PURPOSE
Kleros is an integrated environmental data management system designed to handle the basic tracking
functions of permitting, billing, Inspection, compliance and enforcement. The system will provide direct links
to EPA national data bases. The long range goal Is the have a comprehensive environmental data base for
all regulated entitles In the state, structured in a relational data Case as part of an OHEP GIS. The Kleros
system is one aspect of Integrated environmental data management.
DATA SHARING SYSTEM
-- Centralized location for information on facilities and regulated entities.
-- Provide Input and output on facility permit, licensing data ano fees.
Where appropriate, Kleros supports permit processing.
-- Provide compliance and enforcement tracking,
-- Allow Integrated environmental analysis and allow cross media/cross program planning and management
through data sharing with state and SPA systems.
- Allow OHEP programs to obtain and enter timely, accurate, and complete information In SPA national data
bases.
Primary goal Is to avoid duplicative data entry, allowing information to be entered only once and have the
data integrated with appropriate EPA or Kleros file.
•• Transmit data to EPA, existing state systems and other external groups.
SYSTEM PRODUCTS
-- Facility compliance status reports.
-- Permitting and permit tracking activities.
-- Fee generation reports.
Custom reports based on Kleros master files, ownership files, and permit files.
STRUCTURE
The system Is based on a single Master File containing casic name/address information of the facility,
person, or business a permit Is issued to. The attached system structure represents the Sand Creek system.
Sand Creek emulates the Kleros structure and reflects the link to GiS applications.
Kleros Is structured to:
retrieve data for subsequent processing '
provide timely access to facility Information
provide a link to EPA and existing state systems
It Is necessary that development of related non-Kleros systems wire,in OHEP be designed with key elements
to index to Kleros. Consequently, the OHEP IRM Group plays 3 critical role in coordinating OHEP ADP
equipment acquisition and system development.
-------
COLORADO DEPARTMENT OF HEALTH
OFFICE OF HEALTH AND ENVIRONMENTAL PROTECTION
CHARTER
OHEP INFORMATION RESOURCES MANAGEMENT (IRM) GROUP
PURPOSE
Coordinate development and Implementation of a comprehensive environmental data base for all regulated
entitles in the state and provide overall coordination for environmental data Integration In OHEP.
RESPONSIBILITIES
Establish goals and policies of environmental data integration.
Develop financing strategy and plan for support of environmental data initiatives.
Coordinate environmental data system development.
Establish priorities for environmental data Integration.
Oversee Implementation of Kleros system development and Implementation.
Oversee development and Implementation of OHEP environmental data Integration.
Define management needs for environmental data integration.
Evaluate data needs end applications in support of environmental management.
Provide leadership/direction.to Kleros users Group.
STRUCTURE
Representation from Air Pollution Control, Hazardous Materials and Waste Management, Disease Control,
Consumer Protection, Water Quality Control, Rocky Flats Program Unit, Data Services, Laboratory, and
OHEP. The group Is chaired by OHEP.
-------
EPA Region VIII
State/EPA Data Management Conference
Permit Compliance System
(PCS)
Program Update
by Debra Griffin
April 17, 1991
-------
STATE EPA DATA MANAGEMENT CONFERENCE
PERMIT COMPLIANCE SYSTEM
A System for the Users, by the Users and of the Users
I. OVERVIEW
The Permit Compliance System (PCS) is the national database
used to track compliance and permit activities for the
National Pollution Discharge Elimination System (NPDES).
This system was initially developed in 1980 by the Office of
Water Enforcement and.Permits. PCS has grown over the years
and is second only to the IRS database in size. It resides
at the National Computer Center in Research Triangle Park.
II. Background
PCS was converted to ADABAS in 1984. The first Steering
Committee meeting was held that summer in Alexandria,
Virginia. EPA Branch Chiefs from all ten Regions made up
this committee. At that time I was working at headquarters
and participated in the meeting. Having been a user
previously in Region 6 when the original version of the
system was released, I recognized the need to have input
from other users in Regions and States if additional
enhancements were going to be made to PCS. Thus the PCS
User Group was born. .The first meeting was held in November
of 1984 in Washington D.C. Representatives from all Regions
and New York, New Jersey, Kentucky, Minnesota, Illinois,
Michigan, Arkansas, Texas and Nebraska attended the first
meeting. One of the highlights of that meeting was the
establishment of the. PCS Work Groups. The purpose of these
Work Groups were to define problems and needs of Regional
and State Users, and recommend solutions to the Steering
Committee. The .Users meet twice each year to work on new
program initiatives, develop new products, and vote on
upcoming enhancements to PCS. State participation has
increased from 9 to between 35 and 40 states who are active
participants at the User Group meetings and have played a
key role in helping to identify state needs. The end result
is national system developed by the users instead of by EPA
headquarters.
III. Status
Currently, I am Chairperson of the General Retrieval
Generator Work Group. Mike Pasichnyk of Montana also serves
as a member of this Work Group. The purpose of the Work
Group is to make the PCS retrieval package more user
friendly. Included in your packet you will find the
requirements analysis and the proposed prototype.
1
-------
IV. Accomplishments
Some of the system enhancements that have resulted from the
PCS Work Groups are:
Managers Inquiry
PCS PAL
Automated QNCR and Coordinators QNCR
Quality Assurance Retrieval Enhancement
Seasonal Limits at the Outfall and Limits Level
Sequential File Extract
Quick File Extract
PCS Policy Statement
Group Menu to Support Regions and States
Data Entry Methods Study;
Optical Character Readers
PC Entry Package
PCSADE
PCS Graphics
Violation and Enforcement Action Tracking
Inspection Scheduling
Pretreatment Enforcement Tracking
Unpermitted Discharge Tracking
General Permit Tracking
Sludge Tracking System Feasibility Study
Permit Writing Kits
PCS PC Storyboard Training for New PCS Users
V. Issues
PCS is certainly getting ready for data integration. The
biggest issues our states face right now are equipment and
staffing. We are working with the Regional SEDM Coordinator
and Headquarters Office of Water Enforcement and Permits to
resolve these issues.
VI. Role of SEDM
Our regional SEDM Coordinator has already procured equipment
for South Dakota and assisted in getting telecommunications
links for Wyoming and the National Computer Center.
Equipment, staffing and training needs have already been
identified and solutions are being worked on.
VII. Next Steps
This year Colorado, Montana, South Dakota and Utah
participated in the PCS User Group and Steering Committee
Meeting held last week in New Orleans, Louisiana. Next year
we would like to see all Region 8 states in attendance.
Equipment and staffing are high on our agenda for the
upcoming months. Wyoming needs additional staff in order to
take on PCS. North Dakota is currently supporting PCS with
one PC for five staff members. Colorado is also in need of
2
-------
additional equipment to support PCS. Establish clear goals
to complete Phase I of the SEDM project.
3
-------
Contents
Chapter 1. CsTRODUCTION 1-1
1.1 Background 1-1
1.2 Scope 1-1
Chapter 2. SCREEN DESIGNS 2-1
2.1 Create Retrieval 2-2
2.1.1 Quick Look Report 2-3
2.1.2 Milestone Report 2-9
2.1.3 Quick File/Sequential File Extracts 2-10
2.1.4 Fixed Format Reports 2-11
2.2 Modify Retrieval 2-22
2.3 Delete Retrieval 2-23
2.4 Submit Retrieval 2-23
Chapter 3. SPECIAL FEATURES 3-1
3.1. Acronym Assistance 3-1
3.2 On-Line Validation 3-3
3.3 Help Functions 3-3
Chapter 4. IMPLEMENTATION PLAN 4-1
Contents IV
-------
Figures
2-1. PCS Retrieval Generator - Main Menu 2-1
2-2. PCS Retrieval Generator - Report Selection Menu 2-2
2-3. PCS Retrieval Generator - Quick Look Report 2-3
2-4. PCS Retrieval Generator - Facility Criteria Selection 2-4
2-5. PCS Retrieval Generator - Additional Facility Criteria Selection (1/5) 2-5
2-6. PCS Retrieval Generator - Quick Look Display Criteria Screen 2-6
2-7. PCS Retrieval Generator - Additional Display Criteria Screen 2-7
2-8. PCS Retrieval Generator - Report Submission Screen 2-8
2-9. PCS Retrieval Generator - Milestone Report Options 2-9
2-10. PCS Retrieval Generator - Quickfile/'Sequential File 2-10
2-11. PCS Retrieval Generator - Fixed Format Reports 2-11
2-12. PCS Retrieval Generator - Facility Report 2-12
2-13. PCS Retrieval Generator - Administrative Penalty Order Report 2-13
2-14. PCS Retrieval Generator - Moving Base Report 2-14
2-15. PCS Retrieval Generator - Semi-Annual Statistical Report 2-15
2-16. PCS Retrieval Generator - Violations Recognition Report 2-16
2-17. PCS Retrieval Generator - DMR Administrative Reports 2-17
2-18. PCS Retrieval Generator - Quarterly Noncompliance Reports 2-18
2-19. PCS Retrieval Generator - Industrial User/POTW Reports 2-19
2-20. PCS Retrieval Generator - Limitation Summary Reports 2-20
2-21. PCS Retrieval Generator - Compliance Forecast Reports 2-21
2-22. PCS Retrieval Generator - Library Index 2-22
3-1. PCS Retrieval Generator - Acronym Assistance Screen 1 3-1
3-2. PCS Retrieval Generator - Acronym Assistance Screen 2 3-2
Figures V
-------
Tables
1-1. Revision Summary
4-1. PCS Retrieval Generator Implementation Plan
-------
PCS-GEN91-1.01 (April 1, 1991)
Chapter 1. INTRODUCTION
1.1 Background
The procedures necessary to produce a hard copy retrieval of information from the Permit Compliance
System (PCS) require a certain amount of computer knowledge and expertise. An understanding of TSO,
ISPF, JCL and PCS retrieval logic are currently required to produce a report from PCS. It was decided that
the process should be made more user friendly so that non-technical personnel could produce reports from
PCS without assistance.
In order to determine the requirements necessary to develop an on-line batch retrieval generator for PCS,
research was conducted to review the current retrieval capabilities of existing EPA systems. A report of our
findings was presented to the PCS User Group during the March 1990 user conference held in Philadelphia,
PA.
During the March conference, it was decided that a work group should be formed to assist Headquarters
with the task of developing a general design for a new PCS Retrieval generator.
1.2 Scope
The scope of this project consists of the development of a prototype for an enhanced front-end for the PCS
Generalized Retrieval System. The purpose of designing an on-line retrieval generator for PCS is to aid the
new PCS user who has had PCS training but may not be familiar with ISPF and JCL. It is anticipated that
the retrieval generator will provide a more user-friendly interface for new users through the use of menu-
driven retrieval creation screens.
Due to limited resources this prototype will be developed in-house and made available to PCS users for a 6
month evaluation period. After the evaluation period, a user survey will be conducted to determine whether
the prototype system should be retained. If the results of the survey are in favor of an on-line retrieval
generator, enhancements to the system will be considered at that time.
The retrieval generator will provide:
• On-line syntax checking of PCS retrieval statements.
• A help screen with table look-up capabilities to provide assistance with acronym selection.
• Library functions to create, save, modify and delete retrieval data sets.
• On-line help screens for assistance with entry procedures and available options.
AH existing PCS output, including the quick look, quick file, milestone and pre-formatted reports, will be
available through the new on-line retrieval generator. There will be no enhancements to the format of
output reports with the development of the PCS Retrieval Generator.
Chapter 1. INTRODUCTION 1-1
-------
PCS-GEN91-1.01 (April I, 1991)
Chapter 2. SCREEN DESIGNS
From the Main Menu, options may be selected to create a new retrieval criteria set, modify an already
existing criteria set, delete a criteria set or submit a retrieval for batch processing. These processing options
will be described in detail in separate sections in this document.
Available function keys along with their associated commands, which can be keyed in at the command line
above the screens, have been placed at the bottom of each screen design. New function keys will be
explained as they appear throughout this document.
(

PCS ON-LINE RETRIEVAL GENERATOR

MAIN MENU

1 - CREATE RETRIEVAL

2 - MODIFY RETRIEVAL

3 - DELETE RETRIEVAL

4 - SUBMIT RETRIEVAL

5 - QUIT

ENTER A MENU OPTION OR.'HELP' (PF1) FOR ASSISTANCE

HELP/PF1 END/PF3

J
Figure 2-1. PCS Retrieval Generator - Main Menu
Chapter 2. SCREEN DESIGNS 2-1
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1 Create Retrieval
Upon selecting Main Menu Item 1, Create Retrieval, the Report Selection Menu will appear. This menu
presents four different report formats for selection.
PCS RETRIEVAL GENERATOR
REPORT SELECTION
1 - QUICK LOOK
2 - MILESTONE
3 - QUICK/SEQUENTIAL
FILE EXTRACTS
4 - FIXED FORMAT
ENTER A REPORT TYPE OR 'HELP' (PF1) FOR ASSISTANCE
HELP/PF1 END/PF3 MAIN/PF4
Figure 2-2. PCS Retrieval Generator - Report Selection Menu
Chapter 2. SCREEN DESIGNS 2-2
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.1 Quick Look Report
The first report option, Quick Look Report, is a flexible format report which allows the user to specify their
own selection, sort and display criteria. Upon selection of the Quick Look Report, the Title/Order/ Options
screen will appear. This screen allows the user to enter a 5 line report title, the order in which the data
should be sorted and display options. Function keys at the bottom of the screen are defined as follows:
HELP/PF1 Access the on-line Help screens for assistance with data entry procedures, etc.
END/PF3 Exit the System
MAIN/PF4 Return to the Main Menu
REPORTS/PF5 Return to the Report Selection Menu
ACRO/PF6 Access the Acronym Assistance screens
See Special Features for more information on the Acronym Help function key.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
QUICK LOOK REPORT
REPORT TITLE:
REPORT ORDER:
A=Ascendi ng
(Default)
D=0escendi ng
ACRO A/D
1.
4.
7.
ACRO A/D ACRO
2. _ 3.
5. _ 6.
8. _ 9.
A/D
DISPLAY OPTIONS:
_ RESTRICT
SUPPRESS
Enter Y (Default is N) to select options
unless otherwise indicated in parenthesis.
BREAK _ ARCH _ GHOST _ SKIP (1-3)
EXPAND _ TOP _ HIER _ HEADERS (L/S)
HELP/PF1 END/PF3 MAIN/PF4 REP0RTS/PF5 ACR0/PF6 < CR > CONTINUE
Figure 2-3. PCS Retrieval Generator - Quick Look Report
Chapter 2. SCREEN DESIGNS 2-3
-------
PCS-GEN91-1.01 (April 1, 1991)
Upon pressing the Enter or Carriage Return key (CR) the next screen to appear is the Facility Criteria
Selection Screen. This screen prompts the user to enter all necessary selection criteria in order to extract the
needed information from PCS. ACRO, COND and VALUE are the only mandatory fields on this screen.
The WITH/OR fields are optional and are used to indicate 1 of 2 available functions:
WITH By entering WITH as the value in this field the user may qualify the facility selection criteria
by narrowing the scope of available search criteria.
OR By entering 'OR' as the value in this field the user may set up a series of selection criteria
that are exclusive of each other. When setting up a series of OR statements, the ACRO,
COND and VALUE fields on the same line where OR has been entered must be left blank.
PCS RETRIEVAL GENERATOR
FACILITY CRITERIA SELECTION
WITH/OR ACRO COND VALUE
** Enter ACRO or PF6 for assistance with acronym selection
** Enter MORE or PF7 for additional criteria selection screens
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6 M0RE/PF7 < CR > CON TINUE
Figure 2-4. PCS Retrieval Generator - Facility Criteria Selection
Chapter 2. SCREEN DESIGNS 2-4
-------
PCS-GEN91-1.01 (April 1, 1991)
By entering 'MORE' at the command line or pressing PF7, additional selection screens can be accessed if
needed.
PCS RETRIEVAL GENERATOR
ADDITIONAL FACILITY CRITERIA SELECTION
WITH/OR ACRO COND VALUE
** Enter ACRO or PF6 for assistance with acronym selection
** Enter MORE or PF7 for additional criteria selection screens
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6 M0RE/PF7 < CR > CONTINUE
Figure 2-5. PCS Retrieval Generator - Additional Facility Criteria Selection (1/5)
Chapter 2. SCREEN DESIGNS 2-
-------
PCS-GEN91 -1.01 (April 1, 1991)
Upon completing facility selection criteria for a report, the Display Criteria Selection screen will appear.
This screen is used to specify what types of information should appear on the report. Up to five separate
lines of information may be specified.
On the lower half of the screen, restricted display criteria may be entered to qualify each display line. The
line # from the display lines above must be entered in order to specify which display Line is being qualified.
PCS RETRIEVAL GENERATOR
DISPLAY CRITERIA SELECTION
DISPLAY CRITERIA:
LINE 1:
LINE 2
LINE 3
LINE 4
LINE 5
Enter acronyms for report display leaving blank
space between each acronym.
RESTRICTED DISPLAY CRITERIA: Enter criteria to restrict display
lines above.
LINE # ACRO COND VALUE
Enter MORE or PF7 for additional restricted display selection
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6 M0RE/PF7 < CR > Continue
Figure 2-6. PCS Retrieval Generator - Quick Look Display Criteria Screen
Chapter 2. SCREEN DESIGNS 2-
-------
PCS-GEN91-1.01 (April 1, 1991)
Additional restricted display criteria may be specified by entering 'MORE' at the command line or by
pressing PF7.
PCS RETRIEVAL GENERATOR
ADDITIONAL RESTRICTED DISPLAY CRITERIA SELECTION
RESTRICTED DISPLAY CRITERIA: Enter criteria to restrict report
display.
LINE # ACRO COND VALUE
Enter MORE or PF7 for additional selection screens - Page 2 of 5
HELP/PF1 END/PF3 MAIN/PF4 ACR0/PF6 M0RE/PF7 BACK/PFd < CR > CONTINUE
Figure 2-7. PCS Retrieval Generator - Additional Display Criteria Screen
Chapter 2. SCREEN DESIGNS
-------
PCS-GEN91-1.01 (April 1, 1991)
Once all the applicable Quick Look screens have been completed and validated, the Report Submission
screen will appear. At the top of the screen, a user defined data set name may be entered in order to save
the retrieval criteria set you have created for future use. Entering a data set name is optional.
The JCL, or Job Control Language, parameters will be retained after being entered the first time, so that
with subsequent retrievals the parameters will not have to be completely re-entered. These parameters are
necessary in order for the requested PCS report to be processed properly and routed to the correct destina-
tion. By entering HELP at the command line or by pressing PF 1, each parameter and its possible values
will be discussed.
Upon pressing the Enter < CR > key the report will be submitted as a batch retrieval and a job number
assigned. The processing of the report may then be monitored via SDSF. The user will then be returned to
the Main Menu.

REPORT DESCRIPTION:
The entry of Report Name and Description is optional. If you
wish to save the report created for future use, then an 8 character
member name must be entered. Report Description will allow a 40
character entry for future identification purposes.
JCL PARAMETERS:
PCS RETRIEVAL GENERATOR
REPORT SUBMISSION
REPORT NAME
<
>
JOB Name
Account Code/UID
Time (xxM,xxS)
Pri ori ty
Number of copies
Form Number
Room/Bin Number
Remote
6351
MXXX
255
TEST
A040/PCSYP
Q5M
2
1
Press Enter to submit a batch retrieval
HELP/PF1 END/PF3 MAIN/PF4 REP0RTS/PF5
Figure 2-8. PCS Retrieval Generator - Report Submission Screen
Chapter 2. SCREEN DESIGNS 2-8
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.2 Milestone Report
The Milestone Report provides the user with a tally in matrix format of the number of occurrences of dif-
ferent data values for any two data elements.
Upon selecting the Milestone Report from the Report Selection Menu, the Title/Order/Options Screen will
appear. This screen allows the user to enter a five line report title and to specify row and column acronyms
and values with which to compile the matrix.
Upon pressing the Enter key < CR > , the screen will be validated and the Facility Criteria Selection Screen
will appear (See Figure 2-4 on page 2-4). Selection statements would be entered here to define the range of
data required for the milestone report.
After completing this screen and successful validation, the Report Submission Screen (See Figure 2-8 on
page 2-8) will appear to allow submittal of the retrieval for batch processing.
REPORT TITLE:
ROW
COLUMN:
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
MILESTONE REPORT
BREAK:
Enter 'Y1 for page break.
'N1 is Default
VALUE
SPAM
(")
VALUE Enter 'ALL' for
all Values
1.
3.
5.
7.
2.
4.
6.
HELP/PF1 EN0/PF3 MAIN/PF4 REP0RTS/PF5 ACR0/PF6 < CR > Continue
Figure 2-9. PCS Retrieval Generator - Milestone Report Options
Chapter 2. SCREEN DESIGNS 2-9
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.3 Quick File/Sequential File Extracts
A Quick File Extract is used to create a user-defined set of information from a PCS data family as a sequen-
tial file on disk at NCC. A Sequential File Extract produces a "dump" of information relating to facilities
specified by the user on tape. Both of these retrieval types create data sets which can be used as input for
other programs.
When 'QF' is selected as the Extract Type, after completion of all necessary fields and pressing Enter
< CR > , the Facility Criteria Screen will appear (See Figure 2-4 on page 2-4). Upon successful validation
of this screen, the Report Submission Screen will appear to process the retrieval.
When the extract type selected is 'DU' for Sequential File, after completion of this screen and validation, the
Report Submission screen will appear. The only facility selection criteria allowed with this retrieval is
Region/State which appears on the TITLE/ORDER/OPTIONS Screen.
^
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
QUICK FILE/SEQUENTIAL FILE EXTRACTS
TITLE
EXTRACT TYPE:
Enter QF or OU Complete applicable section.
QUICK FILE EXTRACT (QF) Press PF1 for assistance and list of values
Default = NO
CARD :
RESTRICT :
GHOST :
ARCH :
DATASET NAME:
DISP:
SORT :
SEQUENTIAL FILE EXTRACT (OU)
REGION/STATE: _ DATASET NAME:
OISP :
FILES:
Press PF1 for list of valid codes for
selection of data types.
HELP/PF1 END/PF3 MAIN/PF4 REP0RTS/PF5 ACR0/PF6 < CR > CONTI UE
Figure 2-10. PCS Retrieval Generator - Quickfile/Sequeniial File
Chapter 2. SCREEN DESIGNS 2-10
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4 Fixed Format Reports
PCS Fixed Format Reports differ from the Flexible Format reports Ln that the output format and content
has been pre-defined. Each Fixed Format report has a separate purpose and their own array of options and
restrictions.
From the Main Menu in the figure below, the user may select a particular type of report by entering the
associated number to the left of each report name in the field at the top of the screen. Information about
the function of each report or set of reports is available by entering 'HELP' at the command line or pressing
PF1.
\
PCS RETRIEVAL GENERATOR
FIXED FORMAT REPORTS
MAIN MENU
Select a report or category of reports by entering the number:
1
FACILITY
(FA)
7
QNCR
(QN)

SELECTIVE QNCR
(OR)
2
ADMINISTRATIVE PENALTY
(AP)

MANAGER'S QNCR
(QM)

COORDINATOR'S QNCR
(QC)
3
MOVING BASE
(MB)

8
IU COMPLIANCE
(PT)
4
SEMI-ANNUAL STATISTICAL
(SS)

POTW IMPLEMENT. COMP.
(PT)

POTW ENFORCEMENT ACTION

5 •
VIOLATIONS RECOGNITION
(VR)

SUMMARY
(PT)
6
DMR ADMINISTRATIVE
(DA)
9
LIMITATIONS SUMMARY
(LS

OMR ADMINISTRATIVE

LIMIT SUMMARY W/VIOL.
(LV)

BY PARAMETER
(DP)

DMR SUMMARY
(DS)
10
COMPLIANCE FORECAST
(CP)

DMR NON-RECEIPT
(DF)

COMP. FORECAST W/VIOL.
(CV)
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5
I. )
Figure 2-11. PCS Retrieval Generator - Fixed Format Reports
Chapter 2. SCREEN DESIGNS 2-11
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.1 PCS Facility Report
The Facility Report provides a comprehensive look at individual facilities. Specific types of data may be
requested by entering the associated Section letter from the list below or by entering 'A' to indicate all
Sections. Facility selection criteria are allowed with this report. After validation of the Title/Order/Options
screen, the Facility Criteria Selection Screen (See Figure 2-4 on page 2-4) will appear.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
FACILITY REPORT
REPORT TITLE:
REPORT ORDER: (Facility Level Sort)
SECTIONS: ARCH (Y/N): GHOST (Y/N):
Select a letter or combination of letters from the data types listed
below to indicate which sections to appear on the Facility Report:
A - A11 Sections M - Measurement Violation Data
C - Compliance Schedule N - Pretreatment Inspection Data
E - Enforcement Action Data 0 - Pipe (Outfall) Schedule Data
G - Grant Data P - Permit Event Data
H - Evidentiary Hearing Data R - Inspection Scheduling Data a
I - Inspection Data S - Single Event Violation Data ta
L - Parameter Limits Data X - Pretreatment Summary Oata
HELP/PF1 END/PF3 MAIN/PF4 REPORT/Pf5 ACR0/PF6 < CR > CONTINUE
Figure 2-12. PCS Retrieval Generator - Facility Report
Chapter 2. SCREEN DESIGNS 2-12
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.2 Administrative Penalty Order Report
The Administrative Penalty Order Report provides a listing of selected facilities that have assessed penalties
through enforcement actions.
Facility selection criteria are allowed. After validation of the Title/Order/Options Screen, the Facility Cri-
teria Selection Screen (See Figure 2-4 on page 2-4) will appear.
s

PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
ADMINISTRATIVE PENALTY ORDER REPORT

REPORT
TITLE:

BREAK:
REGN/STTE/SU8R

SUBR:
_ Y/N

DETAIL:
NPID/FNMS

Enter a
APFO
APFO
date range for APO Final Orders (Default is current.FY):
GT/GE DATE - MMDDYY
LE/LT OATE - MMDDYY

*HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6 < CR > CONTINUE
V

Figure 2-13. PCS Retrieval Generator - Administrative Penalty Order Report
Chapter 2. SCREEN DESIGNS 2-13
-------
PCS-GEN91-1.0I (April 1, 1991)
2.1.4.3 Moving Base Report
The Strategic Targeting Activities for Results System (STARS) Moving Base Report provides quantitative
measurements of facilities that are in significant non-compliance (SNC) with their schedule or monitoring
requirements. A report title may not be specified with this report.
Facility criteria selection is allowed and will be entered via the Facility Criteria Selection Screen (See
Figure 2-4 on page 2-4).
c

PCS RETRIEVAL GENERATOR

TITLE/ORDER/OPTIONS

MOVING BASE REPORT

REGION: Enter EPA Region Code

OETAIL: Enter
a level of data or combination from list:

B = Subregion

R = Region

S = State

Enter violation date
(VDAT) range:

VDAT GE/GT _
DATE - MMDDYY

VDAT LE/LT _
DATE - MMDDYY

HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6 < CR > CONTINUE

Figure 2-14. PCS Retrieval Generator - Moving Base Report
Chapter 2. SCREEN DESIGNS 2-14
-------
PCS-GEN91-].01 (April I, 1991)
2.1.4.4 Semi-Annual Statistical Report
The Semi-Annual Statistical Summary Report presents information on facilities in noncompliance with
monthly average effluent limits. No facility criteria selection is allowed with this report. Upon screen vali-
dation, the Report Submission Screen (See Figure 2-8 on page 2-8) will appear.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
SEMI-ANNUAL STATISTICAL REPORT
REPORT
TITLE:
REGION/ Enter Region No. or State abbreviation
STATE:
HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6 < CR > CONTINUE
Figure 2-15. PCS Retrieval Generator - Semi-Annual Statistical Report
Chapter 2. SCREEN DESIGNS 2-
-------
PCS-GEN9M.01 (April 1, 1991)
2.1.4.5 Violations Recognition Report
The Violations Recognition Report provides a listing of selected permitted facilities with reporting or
numeric effluent violations. Facility criteria selection will be allowed from the Facility Criteria Screen.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
VIOLATIONS RECOGNITION REPORT
REPORT
TITLE:
PAGE BREAK ON PERMIT NO.: _ Y/N Oefault is N
Enter monitoring period date range (MVOT):
MVDT GE/GT _ DATE - MMDDYY
MVOT LT/LE _ DATE - MMDDYY
Enter parameter code(s) (VPRM) for violations:
VPRM EQ/AL _ PARAMETER
REPORT ORDER:
(Facility level sort only)
HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6 < CR > CONTINUE
Figure 2-16. PCS Retrieval Generator - Violations Recognition Report
Chapter 2. SCREEN DESIGNS 2-16
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.6 DMR Administrative Reports
There are four different reports to choose from on this screen. AH of these reports are associated with the
receipt or non-receipt of discharge monitoring reports (dmrs). Facility selection will be entered via the
Facility Criteria Selection Screen (See Figure 2-4 on page 2-4).
REPORT TITLE:
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
DMR ADMINISTRATIVE REPORTS
REPORT TYPE:
Select a report type and enter abbreviation:
DA - DMR Administrative DS - DMR Summary
DP - OMR Admin, by parameter DF - DMR Non-Receipt
REPORT OPTIONS: ERROR _ (Y/H) ORDER
DF REPORT ONLY: LEVEL
_ (FACI/PIPE/PRAM) DETAIL
Enter a date range to indicate when DMRs are due:
ACRO C0ND VALUE
(SUDU/SUDS/SUDB) (GT/GE/LT/LE) (Date - MMODYY)
(PIPE)
HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6
< CR > CONTINUE
Figure 2-17. PCS Retrieval Generator - DMR Administrative Reports
Chapter 2. SCREEN DESIGNS 2-17
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.7 Quarterly Noncompliance Reports
There are four separate Quarterly Noncompliance Reports (QNCR) available for selection from this screen.
Facility criteria selection is allowed for all reports except the regular QNCR (QN). If 'QN' is selected as
Report Type, the Report Submission Screen will appear upon validation of the Title/Order/Options screen.
For all other report type selections, the Facility Criteria Selection Screen will appear upon validation of this
screen.
REPORT
TITLE
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
QUARTERLY NONCOMPLIANCE REPORTS
REPORT
TYPE:
VIOLATION
TYPE:
REGION/
STATE:
QN - QNCR QR - Selective QNCR
QM - Manager's QNCR QC - Coordinator's QNCR
Select 1 or multiple violation types:
E - Effluent Violations (including non-receipt)
C - Compliance Schedule Violations
S - Single Event Violations
Enter a Region No. or State Abbr. for QN report only
Coordinator's QNCR VIOL: ALL/NO COMP: _ (Y/N) BREAK:
Optional Enforcement Action date range selection:
ENDT _ GT/GE DATE - MMODYY
ENOT _ LT/LE DATE - MMODYY
(Y/N)
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6
CR > CONTINUE
Figure 2-18. PCS Retrieval Generator - Quarterly Noncompliance Reports
Chapter 2. SCREEN DESIGNS 2-18
-------
PCS-GEN91-1.01 (April 1. 1991)
2.1.4.8 Industrial User/POTW Reports
The Industrial User (IU) and POTW Pretreatment reports provide Lnformation on Significant Industrial
Users (S1U) in Significant Noncompliance (SNC). There are four report types available for selection from
this screen. Available with the PT report type are:
1. IUC = Industrial User Compliance Report
2. PIC = POTW Implementation Compliance Report
3. ENF = POTW Enforcement Action Summary Report
The fourth report is the Pretreatment Hierarchy Report (PH). Upon validation of screen entries, the Facility
Criteria Selection Screen will appear. Facility criteria selection is valid for each of the four IU/POTW report
types.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
IU/POTW REPORTS
REPORT TITLE:
REPORT TYPE: _ (PT/PH) PT REPORT TYPE: (IUC/PIC/ENF)
PT REPORT OPT IONS *************************************************
SPLIT: (REGN/STTE/SUBR) SUBR: (Y/N)
DETAIL: (REGN/STTE/SUBR/NPID/FNMS)
Enter a date range for the PCS Audit Date (DTIA):
DTIA GT/GE _ DATE - MMDDYY
DTIA LT/LE _ DATE - MMDDYY
Enter a date range for the Summary Pretreatment End Date (PSED):
(Not Valid for the ENF report type)
PSED GT/GE _ DATE - MMDDYY
PSED GT/GE _ DATE - MMDDYY
PH REPORT OPTIONS *************************************************
DETAIL: (NPID/FNMS) BREAK: (YES/NO) (No is default)
HELP/PF1 END/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6 < CR > CONTINUE
^ . )
Figure 2-19. PCS Retrieval Generator - Industrial User/POTW Reports
Chapter 2. SCREEN DESIGNS 2-19
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.9 Limitations Summary and Summary w/Violations Reports
The Limitations Summary provides information on pipe schedules and their related parameter limits. The
Limitations Summary with Violations report also includes information on measurement violations. After
system validation of entries made to this screen, the Facility Criteria Selection Screen (See Figure 2-4 on
page 2-4) will appear.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPTIONS
LIMITATIONS SUMMARY REPORTS
REPORT TITLE:
REPORT TYPE:
REPORT OPTIONS
CURRENT:
ORDER:
LS - Limitations Summary Report
LV - Limitations Summary w/Violations Report
YES/MMDDYY
REQUIRED FOR LV REPORT ONLY: MVDT
MVDT _ LT/LE
RESTRICTED DISPLAY CRITERIA:
ACRO COND VALUE ACRO COND
ARCH:. _ Y/N GHOST: _ Y/N
(Facility level sort only)
GT/GE MMDDYY
MMDDYY
VALUE
HELP/PF1 EN0/PF3 MAIN/PF4 REPORT/PF5 ACR0/PF6
< CR > CONTINUE
Figure 2-20. PCS Retrieval Generator - Limitation Summary Reports
Chapter 2. SCREEN DESIGNS 2-20
-------
PCS-GEN91-1.01 (April 1, 1991)
2.1.4.10 Compliance Forecast Reports
The Compliance Forecast Report (CP) lists those compliance schedule events which are scheduled or have
been achieved within a specified time period. The Compliance Forecast with Violations Report (CV) also
includes compliance schedule violations. Upon screen validation, the Facility Criteria Selection Screen (See
Figure 2-4 on page 2-4) will appear.
PCS RETRIEVAL GENERATOR
TITLE/ORDER/OPT IONS
COMPLIANCE FORECAST REPORTS
REPORT TITLE:
REPORT TYPE: _ (CP/CV)
REPORT ORDER: (Facility sort only)
Compliance Forecast (CP): Scheduled (DTSC) or Achieved (DTAC) Dates
ACRO COND VALUE
(DTSC/DTAC) (GT/GE/LT/LE) (Date - MMDDYY)
Compliance Forecast w/Violations (CV): Compliance Violation (CVDT)
ACRO COND VALUE
(GT/GE/LT/LE) (Date - MMDDYY)
CVDT _
CVDT _
HELP/PF1 END/PF3 MAIN/PF4 REP0RT/PF5 ACR0/PF6 < CR > CONTINUE
Figure 2-21. PCS Retrieval Generator - Compliance Forecast Reports
Chapter 2. SCREEN DESIGNS 2-21
-------
PCS-GEN91-I.01 (April 1, 1991)
2.2 Modify Retrieval
The second menu item on the Retrieval Generator Main Menu is Modify Retrieval. Upon selection of this
item, the Library Index Screen will appear for the specified User ID. From this screen the user may select a
specific member from their retrieval Library by entering 'M' in the first position of the field to the left of the
Member name they wish to modify.
After a selection is made the appropriate TITLE/ORDER/OPTIONS Screen will appear containing the ori-
ginal selection criteria. After entering any necessary changes to this screen, press the Enter key < CR > and
the screen will be validated. The FACILITY CRITERIA SELECTION screen (See Figure 2-4 on
page 2-4) will appear next if the original retrieval criteria set contained facility selection information. The
DISPLAY CRITERIA screen (See Figure 2-6 on page 2-6) will display next, unless the report being modi-
fied is a fixed format report, when the REPORT SUBMISSION screen (See Figure 2-8 on page 2-8) will
Upon submission of the modified report, the Retrieval Library Index screen will return to modify another
report.
appear.
PCS RETRIEVAL GENERATOR
RETRIEVAL LIBRARY INDEX
User 10:
Account No:
Line Commands: (S)ubmit (M)odify (O)elete (C)opy
Member Name Description
Date Created Type
M"1 HQSTAT
REG IV
AZTEST
5NC01
WVDF
4th Qtr Stats
Region IV Majors
AZ00201134
Region 1 Investigation
OMR Non-receipt for WV
02/15/91 MS
02/21/91 QL
02/22/91 FA
02/22/91 QL
03/02/91 OF
HELP/PF1 END/PF3 MAIN/PF4
Figure 2-22. PCS Retrieval Generator - Library Index
Chapter 2.
SCREEN DESIGNS 2-22
-------
PCS-GEN91-1.01 (April 1, 1991)
2.3 Delete Retrieval
As a necessary part of good computer housekeeping, it may be required from time to time to delete a
retrieval criteria set that may no longer be needed. From the Main Menu, select Option 3 - Delete
Retrieval- and the Retrieval Library index (See Figure 2-22 on page 2-22) will appear. Retrieval criteria sets
may be deleted by entering a 'D' to the left of the member name.
2.4 Submit Retrieval
Upon selection of Main Menu Item 4- Submit Retrieval- the Retrieval Library Index (See Figure 2-22 on
page 2-22) will appear on the screen. In order to submit a retrieval without modification to the existing
logic, the user would enter an 'S' to the left of the member name. The Report Submission Screen (See
Figure 2-8 on page 2-8) would then appear to allow modification to any of the JCL parameters prior to
submitting the report for batch processing.
After report submission is complete, the system will return to the Retrieval Library Index screen to allow the
submission of another report or any other processing option available from this screen. At completion of
activity with this screen, the user may enter 'END' at the command line (or PF3) to exit the PCS Retrieval
Generator System or enter 'MAIN' (or PF4) to return to the Main Menu.
Chapter 2. SCREEN DESIGNS 2-22
-------
PCS-GEN91-1.01 (April 1, 1991)
Chapter 3. SPECIAL FEATURES
There are three special features to be developed for the retrieval generator that should provide greater ease of
use for the PCS user:
• Acronym Assistance
• On-line Validation
• Help Functions
3.1 Acronym Assistance
Entering ACRO' at the command line of any retrieval generator screen or pressing PF6 will prompt the
system to present the Acronym Assistance screens. The sample screens in the figures below provide exam-
ples of this function.
PCS FAMILY TYPE:
01 - Faci1i ty
04 - Pretreatment
07 - Permit Event
PCS DATA TYPE:
PCS RETRIEVAL GENERATOR
ACRONYM ASSISTANCE SCREEN 1
Select a corresponding number from the list of
families below:
02 - Effluent
05 - Inspection
08 - Grants
03 - Compliance Schedule
06 - Enforcement Actions
09 - Evidentiary Hearing
Select a corresponding
data types below:
letter from the list of
A - Pipe Schedule G
B - Parameter Limits H
C - Measurement Violation I
D - Compliance Schedule J
E - Compliance Schedule Vio. K
F - Enforcement Action
Enforcement Action Keys
Single Event Violations
Inspection Schedule
Inspection Data
PCI/Audit Data
SEARCH STRING
acronym search.
Enter descriptive criteria for
HELP/PF1 END/PF3 MAIN/PF4 REP0RTS/PF5 Continue
Figure 3-1. PCS Retrieval Generator - Acronym Assistance Screen 1
Chapter 3. SPECIAL FEATURES 3-1
-------
PCS-GEN91-1.01 (April I, 199!)
If the PCS Family Type field was entered with '06' Inspection, and the Search String field was entered with
'SIU', Acronym Assistance Screen 2 would appear with this sample output.
Upon entering the 'END' command or pressing PF3, the system will return to the screen from which
Acronym Assistance was requested.
_
PCS RETRIEVAL GENERATOR
ACRONYM ASSISTANCE SCREEN 2
ACRONYM
REPORT HEADING DESCRIPTION
MSNC
NINF
NO CM
NO IN
NOPT
PSNC
RSNC
SIUS
SHIN
SIUS IN SNC W/SELF-MON
SIUS NOT INSP/SAMP AT REQ FREQ
SIUS VJ/0 CNTRL MECH
SIUS NOT I (ISP/SAMPLED
% OF SIUS NOT INSTALLED PT
SIUS IN SNC W/STD & RPT
SIUS IN SNC W/RPTG
SIGNIFICANT INDUSTRIAL USERS
SIUS IN SNC W/SELF-HOM NOT INSP
HELP/PF1 END/PF3 ACR0/PF6
CONTINUE
J
Figure 3-2. PCS Retrieval Generator - Acronym Assistance Screen 2
Chapter 3. SPECIAL FEATURES 3-2
-------
PCS-GEN91-1.01 (April 1, 1991)
3.2 On-Line Validation
The current batch retrieval process of validation requires submission of the retrieval after which validation of
acronyms, syntax and format occurs. If any errors are discovered, the retrieval logic criteria must be modi-
fied and the job resubmitted. This process can be very time consuming, especially if the retrieval is run to
print and not to hold first so that any errors can be reviewed, corrected and resubmitted.
The PCS Retrieval Generator will validate every screen as the information is entered. Errors in syntax,
spelling, display line and report order restrictions on length, will be pointed to and described by the vali-
dation program. These errors can then be immediately corrected prior to submitting the retrieval criteria set
for batch processing.
3.3 Help Functions
From every processing screen within the PCS Retrieval Generator System it will be possible to access Help
screens which will provide assistance to the user in the following areas:
• Explanation of fields on the particular screen from which help is requested.
• Explanation of various report types including information to aid the user in the decision as to which
type of report might better suit their needs.
• Description of default values.
• Listing of field values not specified on the screen.
• More in depth explanation of errors discovered during screen validation processing.
It is hoped that the Help Functions will eventually be extensive enough so that referral to hard copy system
documentation will not be necessary. An on-line tutorial to provide an overview of the Retrieval Generator
System and its functions is also planned.
Chapter 3. SPECIAL FEATURES
3-3
-------
PCS-GEN91-1.0! (April 1, 1991)
Chapter 4. IMPLEMENTATION PLAN
Please forward all comments regarding the general design to Linda Walker via U.V1AIL (User ID: WLL) or
NOTEPAD by April 29, 1991.
Once all user comments have been received and incorporated into the general design, the following develop-
ment schedule will be implemented:
TASK
SCHEDULED COMPLETION DATE
Complete DetaiJ Design
6/30/91
Programmine/T esting
12/30/91
In-house Testing
01/15/92
Beta Testing in Regions
02/15/92
Implement Phase 1 system
03/01/92
Six month user evaluation
09/01/92
Conduct user survey
10/01/92
Determination of system enhancements
11/01/92
Table 4-1. PCS Retrieval Generator Implementation Plan
Chapter 4.
IMPLEMENTATION PLAN 4-1
-------
EPA Region VIII
State/EPA Data Management Conference
Resource Conservation and Recovery
Information System
(RCRIS)
Program Update
by Terry Anderson
April 17, 1991
-------
AN INTRODUCTION TO RCRIS
RCRIS, the Resource Conservation and Recovery
Information System, is EPA's new computerized man-
agement information system for managing the hazard-
ous waste program mandated by the Resources Conser-
vation and Recovery Act (RCRA).
RCRIS is the result of an extensive and continuing
development effort whose goal is to meet the information
management needs of both EPA and the states in carry-
ing out RCRA.
RCRA requires EPA to administer a national program to
control hazardous waste. However, it was the intent of
Congress that, where possible, the states assume re-
sponsibility for controlling such waste within their bor-
ders, with federal financial and technical assistance. The
success of RCRA in regulating hazardous waste dis-
posal activities therefore depends largely upon the close
cooperation of EPA and the states.
RCRIS is being designed through a cooperative effort
between EPA and the states to support state and EPA
hazardous waste activities. It will do so by providing a
system that is both broad and flexible, and thereby able
to meet both EPA's and the states' individual and shared
information processing requirements.
This executive summary presents an overview of
RCRIS, including:
• RCRIS objectives
• Key RCRIS features and functions
• Major RCRIS software modules
• EPA/State cooperation in RCRIS's development
• RCRIS installation cost information
• Implementation approach and schedule
1
-------
RCRIS OBJECTIVES
The overall goal of this new system is to help EPA and
the states carry out the RCRA program more effectively
by providing:
• Capability to respond to the diverse information track-
ing requirements of EPA headquarters, EPA regions,
and the states;
• A mechanism for ensuring highly accurate data;
• A user friendly system;
• A system that can be modified to carry out future
changes in RCRA; and
• Access to information in other related EPA data
bases.
RCRIS FEATURES AND
FUNCTIONS
RCRIS will offer its users an impressive array of features
and functions. The most significant of these are:
• Two Levels of Information Tracking. RCRIS is
designed to meet the information requirements of two
levels of management, those associated with the day-
to-day implementer activities of carrying out RCRA,
and those needed to support the broader oversight
responsibilities of the EPA regions and headquarters.
This design is referred to as the "Two-Domain
2
-------
Concept" in RCRIS, and is described more fully in the
next section. It enables RCRIS to meet state, EPA
regional, and EPA headquarters RCRA information
management needs.
• Compatibility with Mainframes and PCs. RCRIS is
designed to run on either mainframes or PCs that
have FOCUS software installed. This flexibility will
allow RCRIS to be used by states or state offices that
prefer PC to mainframe systems.
• Compatibility with IBM Equipment. RCRIS is
implemented in a single data base (FOCUS) lan-
guage, and can be installed on most IBM or IBM-
compatible PCs and mainframes.
• Compatibility with Non-IBM/Non-RCRIS Systems.
States committed to non-IBM hardware or non-
RCRIS software can continue to use those systems.
These states would use a special software program
to convert or "translate" non-RCRIS data into the
proper format for monthly transfers of data to the
RCRIS system at the EPA regional offices.
• Tracks a Broad Range of Information. RCRIS
contains seven major modules that track a variety of
RCRA-related information, including Handler Identifi-
cation (basic information about hazardous waste
generators, transporters and treatment, storage and
disposal facilities), Compliance Monitoring and En-
forcement (which tracks inspections, violations, and
enforcement actions) and Permitting (the status of
actions on a hazardous waste facility permit applica-
tion). Other modules address corrective action, facil-
ity management planning, and program management.
3
-------
TWO DOMAINS
The Concept. The Two-Domain Concept is the pre-
eminent design feature of RCRIS. It:
• Reflects the RCRA program partnership between two
levels of government-state and federal EPA;
• Allows those who generate the data to own that data
and be responsible for the quality of that data; and
• Accommodates both day-to-day RCRA (implementer)
information and management-level oversight informa-
tion.
The premise of the two-domain concept is that in order
to run the RCRA program, there is a need for common
data among those who carry out and manage the every-
day activities of the RCRA program, and those who are
responsible for reviewing the performance and effective-
ness of the RCRA program. Therefore, administration of
the program must rest on a data-sharing partnership be-
tween these two levels, or domains. At the same time,
each domain has unique information needs that must be
satisfied. The two RCRIS domains are:
• Implementer Domain. This domain is designed to
collect, enter, track and report day-to-day RCRIS in-
formation, involving such activities as handler identifi-
cation, permitting, inspections, and enforcement ac-
tions. Both states and EPA regions, in their imple-
menter capacity, will use the RCRIS implementer
domain functions.
• Oversight Domain. This domain is designed to track
and report management information required to re-
view the RCRA program implementation. It is also
4
-------
designed to provide information needed to develop
program management and budgetary strategies. EPA
regions and headquarters, in their oversight capacity,
will use the RCRIS oversight functions.
States will also be able to use these functions for
state-level oversight activities. This is possible be-
cause oversight data is merely a subset of implemen-
ter data that the states maintain.
The Benefits. The two-domain design offers a number
of important benefits to both EPA and the states which
are not available from the existing hazardous waste
information systems. It:
• Facilitates Closer Cooperation Between EPA and
the Slates. Through the data-sharing partnership
that RCRIS is built upon, EPA and the states both
benefit from working together to achieve the common
goals of data quality and timeliness.
• Ensures Higher Data Quality. By providing data
ownership and control to those who generate and
maintain RCRIS data, the two-domain design ensures
more accurate and complete data for both EPA and
the states.
• Provides Greater Accessibility to Information.
Because all of the implementer information resides
where it is generated and used, states will have im-
mediate access to the information they require.
• Reduces Volume of Data Maintained by EPA.
Because EPA requires only a subset of the large
body of implementer data maintained by the states,
its information storage requirements are reduced.
5
-------
• Enables States to Carry Out RCRA More
Effectively. The two-domain design provides states
that adept RCRIS with a complete in-house RCRA
management information system that will enable
them to carry out the RCRA program more effectively.
The Responsibilities. Accompanying the benefits of
RCRIS are new responsibilities for both EPA and the
states, and new or enhanced software tools to help fulfill
those responsibilities:
• Maintenance of Data. As owners of the data that
they generate, the states and EPA regions (ip their
capacity as implementers), will be responsible for
storing and maintaining that data. The RCRIS soft-
ware provides a complete system for maintaining a
large quantity of detailed information about hazardous
waste generators, transporters and treatment, stor-
age and disposal facilities.
• Quality of Data. As implementers, states and EPA
regions will be responsible for ensuring the accuracy
and completeness of the data that they maintain.
RCRIS provides software tools to assist in this
process.
• Timeliness of Data. As implementers, states and
EPA regions will be required to meet the deadlines for
transferring high quality data to the EPA oversight
domain. States will also be required to respond in a
timely fashion to EPA requests for special reports.
RCRIS provides software tools to quickly and easily
produce such reports.
6
-------
• Cooperation in Resolving Data Differences.
EPA regions and the states will be responsible for
working together to reconcile data differences regard-
ing particular hazardous waste firms. RCRIS soft-
ware identifies data that require attention.
RCRIS OFFERS CHOICES
The two-domain design and other key features of RCRIS
contribute to a system that provides each state with
several choices in implementing RCRIS.
The Manual Option. Implementers with RCRA
programs that manage a very small amount of data
may opt to continue maintaining manual records. These
states would simply furnish paper records containing
RCRIS information to the EPA Regions.
The PC Option. Implementers may choose to adopt the
PC version of RCRIS by purchasing a single or multiple
IBM or IBM-compatible PC AT system(s) with PC FO-
CUS software, depending on the size of their database.
The Mainframe Option. Implementers also have the
option of adopting the mainframe version of RCRIS
using an in-house mainframe system with mainframe
FOCUS software.
The Translator Option. In addition to accommodating
small or large amounts of data, RCRIS also allows states
to retain their existing hardware and software and still
provide information needed by RCRIS. This is accom-
plished by furnishing data that has been translated into
RCRIS format. The translation will be performed elec-
tronically, using a special translator function that must be
7
-------
added to the state's existing software. The transfer to the
EPA region of the resulting oversight data will be done
monthly.
Note: EPA is also currently investigating the ability to
implement RCRIS on a focal area network.
RCRIS CONTAINS SEVEN MAJOR
MODULES
RCRIS tracks a wide range of information related to
firms that generate, transport, and/or treat, store, and
dispose of hazardous waste. This information is man-
aged by RCRIS' seven major modules, or applications
(see Figure 1):
• Handler Identification (HID). Tracks and maintains
descriptive information on regulated hazardous waste
facilities, generators, and transporters.
• Permitting, Closure, Post-Closure (PMT/CL/PC).
Tracks information on the status of permit
applications for hazardous waste facilities.
• Compliance Monitoring & Enforcement (CM&E).
Tracks and maintains data for handler compliance
evaluations, violations, enforcement actions, and
return to compliance.
• Data Quality/Data Management (DQ/DM).
Provides automated software controls to ensure the
accuracy of data.
• Corrective Action (CA). Supports the permit-writing
and program-enforcement coordination necessary for
an effective corrective action program.
8
-------
THE SEVEN RCRIS MODULES
PERMITTING/
CLOSURE/
POST-CLOSURE
DATA .
QUALITY/
DATA
MANAGEMENT
HANDLER
IDENTIFICATION
COMPLIANCE
MONITORING
AND
ENFORCEMENT
RCRIS
ACTON
PROGRAM
MANAGEMENT
FACILITY
MANAGEMENT
PLANNING

Figure 1 - The Seven RCRIS Modules
9
-------
• Program Management (PM). Supports the state,
regional, and national management and evaluation
needs of the RCRA program.
• Facility Management Planning (FMP). Supports
the development and analysis of facility management
plans.
RCRIS EMBODIES EPA/STATE
COOPERATION
One of the key attributes of RCRIS is that it responds to
the RCRA information management requirements of
both EPA and the states. This has been realized
through the high degree of EPA/State cooperation during
the development of the system:
• RCRIS Resource Group. Both EPA and state repre-
sentatives have been involved in the RCRIS design
process (via a Resource Group made up of 5 state, 5
headquarters, and 5 regional representatives), includ-
ing the development, testing, and evaluation of the 7
RCRIS modules.
• National Governors Association. State
representation has been both coordinated and aug-
mented by the National Governors Association and its
RCRIS State Advisory Council.
10
-------
DRAFT
4/11/91
REGION VIII RCRIS IMPLEMENTATION SCHEDULE
Final
State MOU Signing Conversion HWDMS Off STARS in RCRIS
WY N/A Done April 30 3rd Q Pull
MT Done April 30 June 30 3rd Q Pull
ND Done April 30 June 30 3rd Q Pull
CO by April 30 June 30 Sept 30 4th Q Pull
SD* by June 30 July 30 Sept 30 4th Q Pull
UT* by June 30 July 30 Sept 30 4th Q Pull
*Note: hands-on training for South Dakota and Utah is scheduled
for 6/25-6/27 in Salt Lake City, UT.
-------
RCRIS
RCRIS
NATIONAL IMPLEMENTATION
SCHEDULE
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec
Region 1
Region 2
Region 3
Region 4
Region 5
Region 6
Region 7
Region 8
Region 9
Region 10

Draft - March 27,1991.
-------
EPA Region VIII
State/EPA Data Management Conference
Geographic Information Systems
(GIS)
Program Update
by William Murray
April 17, 1991
-------
-------
EPA Region VIII
State/EPA Data Management Conference
Region VIII Computer Support Services
Summary
by Brenda Combs
April 18, 1991
-------
SERVICES PROVIDED
BY
THE INFORMATION & COMPUTER MANAGEMENT BRANCH
I. Mainframe Assistance
o Timeshare Accounts & Userid's
o Mainframe Applications
o Database Design and Security
o System Mauals & Documentation
o Training
II- Communications
o Lan
o Connectivity to the Mainframe at RTP
o Tailor Communictions to Your Specific Needs
o Software Support
III. Electronic Mail
o Process Request Forms
o Training
-------
EPA APR IBM & VAX ACCOUNT AND USER REGISTRATION
THIS REQUEST:
~ Establishes a New Account
~ Adds. Deletes, or Changes Users(s) on Existing
Account No,
(See NDPD policy 4.5(F). Specify disposition of RACF profiles:
Delete7 Ves ~ No If Wo, specify new Owner-ID
(Noie: Form n 251 must be completed to modily information other than user data on an existing account.)
TRSMSHSFONLY
Date Received:
HARDWARE fCHECK ONI V ONE)
~ ISM 3090 , ~ IBM 4331 Washington, DC
~ NCC VAX Cluster Model VAX
~ Other (Specify)
SOURCE OF TIMFSHARE FUNDS (CHECK ONI V ONE)
~ U.S. EPA ~ Interagency/lntergovernmental Agreement (IAG)
To Be Completed by EPA IAG Coordinator:
Is account to be charged IAG 10% surcharge''
~ Yes ~ No
(EPA IAG Coordinators Signature)
PURPOSE Or ACCOUNT OR BRIEF DESCRIPTION OF ACTIVITY ACCOUNT WILL SUPPORT
EPA Organization Cooe (8-digit code)
FMSCode (10-digit code)
Account Title (Limit: 60 characters, including spaces)
Account Manager's Name (Last, First, M.I.). Must be EPA employee.
To b« « user on ihi* account. Account Manager must be Included on reverse tide.
Phone
FTS
or
Phone (include area code)
( )
Reference
initials
(TSSMS-
assigned)
Mail Code (or room)
Office or Location
Address (Street or P. O. Box}
City
State
Zip Code
EPA ADP Coordinator's Name (please print or type)
Phone
EPA ADP Coordinator's Signature (required)
Email ID
Date
USER INITIALS COOE
(TSSMS-Assigned)
(Supply if known)
COOES USED IN ASSIGNING USERS ON REVERSE SIDE
SPECIAI FEATURES CODF
(Check lor each user listed.)
T TSO Access
"TURN FORM TO'
1 Environmental Protection Agency
nonal Data Processing Division
rSSMS Office (MD-34C)
79 Alexander Drive. Building 4501
Research Triangle Park, NC 27711
TSSMS USE ONLY
USER TYPE CODFS
(Check one for each user listed.)
E • EPA Employee
C • Contractor/Commericial
F - Federal Non-EPA
S - State or Local Government
U ¦ University
O • Other
(SEE REVERSE SIDE FOR ASSIGNING USERS TO ACCOUNT)
N 253 (PAGE 1)
-------
USERS ASSIGNED TO ACCOUNT
(Please Print or Type)
USER
NAME (Last, First. M.I.)
Phone
User Initials
TSSMS-Assigned
TffSMS USEONLil

(i-iaj
or
Phone (1
area cod
( )

I
Mail Code (or room) Office and/or Company
nclude
*)
Special
Feature
~ TSO
User Type
~ C ~ U
= F ~ 0
~E ~ S
Address (Street or P. 0. Box) City
State
Zip Code
Update Action _ Add User l_ Delete User' ~ Change user information as listed above. |
"When deletina user SDecitv riisoosition of RACF Drofiles. Delete orofiles? D Yes C No (Soecifv new Owner-ID: i 8
USER
NAME (Last, First, M.l.)
Phone
User Initials
TSSMS-Assigned
1 ISP ONI yi

(M1.J
or
nclude
e)

Mail Code (or room) Office and,'or Company
Phone (
area coc
( )
Special
Feature
~ TSO
User Type
~ C ~ U
~ F DO
~ E ~ S
Adoress (Street or P. 0. Box) City
Stale
Zip Code
Update Action _ Add User _ Delete User' _ Change user information as listed above. jj
"When deleting user, specify disposition ot RACF profiles. Delete profiles? C Yes ~ No (Specify new Owner-ID: ) |
USER j NAME {Last, First, Ml)
Phone
(FTS)
or
nciuae
e)
User Initials
TSSMS-Assigned
T5§ySU5E
-------
United States Environmental Protection Agency
Email Mailbox Application
Complete this form to request an EPA Email Mailbox. Send the completed form to your Email Coordinator (or review and
approval. Be sure to answer all the questions and to include a phone number.
Requestor's full name
Date
Phone number FTS or area code { )
Affiliation EPA Employes Contractor State Affiliate Other
Complete the appropriate section below for additional required information.
EPA Employee Information
Job title or description
Branch/Oiv/Ofc/Org or Reg
Contractor/State Affiliate/Other
Information
Organization name
Job title or description
EPA Project Officer or sponsor
Phone number or Email box
Group Box Information If the request is for a Group Box, give a Group Box name and a brief description.
Consider organization, region, branch, division, or office.
Group Box name
Box description
Email System Justification Briefly describe how you will use the Email services. Consider: Who will you com-
municate with? What types of documents?Frequency of use? etc.
Distribution Lists List the names of public distribution lists, if any, your new mailbox should be
included in.
Special Requirements
Briefly describe special requirements for your mailbox. If necessary, the EPA Email
Technical Manager will contact you to discuss your special requirements.
-------
TELEPHONE NUMBERS
COMMUNICATIONS: GERRY HUNT 293-1682
RUDY MARTINEZ 293-1783
MAINFRAME, DOCUMENTATION,
COMMUNICATIONS SOFTWARE,
TRAINING: BRENDA COMBS 293-1786
EMAIL BOX REQUESTS:
GAYE FINNEGAN 293-1848
-------
357/001C
IBM Mainframe Seminar
ARBITER
svEPA
NCC IBM Mainframe Seminars
-------
IBM Mainframe Seminar
ARBITER
Prepared by
NCC Training
November 28, 1988
Revised June 6, 1989
Revised November 30, 1989
Contract No. 68-01-7437
U.S. ENVIRONMENTAL PROTECTION AGENCY
NATIONAL DATA PROCESSING DIVISION
RESEARCH TRIANGLE PARK, NORTH CAROLINA
-------
ARBITER
ii
Preface
This manual introduces ARBITER, the micro-to-
mainframe product released in January 1989.
The manual introduces the basic components of
ARBITER, explains how ARBITER is used, and
lists the advantages of using ARBITER over
other software.
For further information about ARBITER,
contact:
user support (FTS) 629-7862
(919) 541-7862
(800) 334-2405
-------
ARBITER
Table of Contents
THE MICRO-MAINFRAME LINK (MML)
Objective ....
1
1
A COMMUNICATIONS ALTERNATIVE
PC/Mainframe Interface .
2
2
WHAT IS IT? .
Architectual Overview .
Software Components
ARBITER Components
Remote Disk Environment
Why Use RDE?
External File Interface
Why Use EFI?
Mainframe Extractions
Interactive Session Relay
Why Use ISR?
3
3
4
4
5
7
7
9
10
10
HOW DO YOU USE ARBITER?
Easy to Use, Easy to Learn
Menus ....
Commands
12
12
12
12
USING ARBITER
Establishing an ARBITER Session
Remote Disk Environment
RDE Assignment .
RDE List Free Space .
RDE Create
RDE Mount ....
External File Interface (EFI)
EFI Transfers
Predefined Extractions
Data Base Transfers .
FOCUS Data Base Extraction
Interface Session Relay (ISR)
13
13
18
19
19
20
22
24
24
24
29
30
31
-------
ARBITER
iv
Table of Contents (Cont.)
6
ADVANTAGES . . . . . . . . .33
Uses Current Knowledge . . . . . . . .33
Comparable with Hardware and Software . . . . .33
Easy to Use, Easy to Learn ....... 34
Operates as a VTAM Application . . . . . .34
API's for Software Developers . . . . . .35
Integrated with Security and Accounting . . . .35
-------
ARBITER
1
THE MICRO-MAINFRAME LINK (MML)
OBJECTIVE This seminar introduces ARBITER, the micro-to-
mainframe product released in January, 1989.
We will look at the basic components of
ARBITER, how it is used, and the advantages of
using ARBITER over other software.
-------
ARBITER
2
A COMMUNICATIONS ALTERNATIVE
PC/MAINFRAME ARBITER creates an interface between. the
INTERFACE mainframe and the PC that combines them into
a single information processing area. PC's and
mainframes access data and perform tasks
cooperatively. Mainframe users and micro users
can work with the same data using their "own"
tools. Very little additional training is
needed.
ARBITER provides an easy means to access and
convert files into PC-compatible formats. It
allows the PC to have access to mainframe disk
space and mainframe applications. It stan-
dardizes the PC-to-mainframe communication,
eliminates data integrity problems, and
resolves security issues. ARBITER also allows
users to utilize the PC and host concurrently.
-------
ARBITER
3
WHAT IS IT?
ARCHITECTURAL ARBITER is a software subsystem that provides
OVERVIEW complete data communications services for
microcomputers and mainframes with total
commitment to IBM and SNA compatibility.
ARBITER is a standalone VTAM subsystem, not a
VTAM application. The benefits of the ARBITER
architecture as a VTAM subsystem are:
o Host security protection,
o Controlled environment,
o Monitored system use.
o Efficient use of host resources,
o Optimal transfer rates.
o Support for hundreds of simultaneous users.
ARBITER runs on the mainframe at the same level
as TSO and CICS and communicates directly with
VTAM. ARBITER is a multiuser single address
space subsystem and can support large numbers
of users.
ARBITER consists of software that executes on
both the mainframe and the PC. The mainframe
and the PC cooperate to provide services for
each component. ARBITER end user presentation
services are independent of the communication
method used to connect the PC to the mainframe.
For the user, this means that ARBITER functions
the same on all machines.
ARBITER supports PC's using the following types
of mainframe communications connections:
o Coax adapters,
o Asynchronous,
o Token ring.
Device support is available for many kinds of
LU2 Type 2 and SDLC communications adapters.
Among those supported are IBM, DCA, IRMA, CXI,
Attachmate, and Forte.
In an asynchronous environment, ARBITER PC code
emulates a VT100 terminal.
SOFTWARE
COMPONENTS
-------
ARBITER
4
Token ring is supported through 3174 and 37X5
connections.
ARBITER ARBITER has three components:
COMPONENTS
1. Remote Disk Environment (RDE).
2. External File Interface (EFI).
3. Interactive Session Relay (ISR).
These software components interact with each
other and the operating system on the mainframe
and PC to accomplish the following:
o Increase the storage and backup space
available to the PC.
o Use other mainframe applications, such as
TSO and CICS.
o Transfer data between the mainframe and the
PC.
REMOTE DISK The Remote Disk Environment (RDE) lets you
ENVIRONMENT create remote disks on the mainframe and mount
them on virtual drives so that you can use
mainframe disk space like you use your PC's
hard and floppy disks.
Remote Disk. A remote disk is part of a
mainframe computer's disk space and your PC
can read from and write to this disk. An
unlimited number of remote disks can be
created, ranging from 16 kilobytes to 32
megabytes. Each remote disk is identified by
a unique name and description. RACF data set
profiles can be placed on RDE space to control
access at levels such as ALTER, CONTROL,
UPDATE, READ, or NONE (for no access) to any
other user on the system.
-------
ARBITER
5
Virtual Drive. A virtual drive is a program
that emulates the function of your PC's disk
drives. A virtual disk drive is labeled with
DOS device drive ID'S (e.g., D:, E:, F:, and
so on). A remote disk is used by mounting it
on a virtual drive. The remote disks are
mounted in the same manner as you would mount
a disk in a floppy drive and, for all intents
and purposes, appears to DOS as though it were
physically attached. Remote disks are
compatible with the Agency's PC application
software - a remote disk can be used trans-
parently.
Why Use RDE? Data Base Subsets. RDE provides a repository
for mainframe data extracted from host files.
The data can be extracted by canned extraction
routines, translated to formats usable by PC
application software, and used directly from
the remote disks.
Software Upgrades. The remote disks can be
used to store and forward software upgrades.
A central source provides software integrity
and spreads out the workload to the users for
software upgrades.
Backups. The remote disks can be used for
routing backup of local disks. This has the
advantages of ease of operation, access
control, automatic mainframe backup, and
archiving or migrating.
Public Domain Library. Data pertinent to all
PC users, such as information bulletins and
public domain software can be stored on a
central repository for access by all. A Public
Domain Library can provide ready access to new
software fixes and software reviews.
Transaction Staging. Through RDE, the remote
disks can serve as a staging area for mainframe
transactions and, thus, be a source of data
base transactions.
DOS Files. The remote disks are mounted in the
same manner as a disk in a floppy drive, and
appear to DOS as though they were physically
attached. Remote disks can be used transpa-
rently.
-------
ARBITER
6
Virtual PC. A PC's complete hard disk can be
copied from the local disk to the remote disk
to provide access from non-work locations when
on business trips and at home after work hours-
-------
ARBITER
7
EXTERNAL PILE External File Interface (EFI) allows data to
INTERFACE be transferred between a PC or remote disk and
the mainframe while converting that data in the
files to the proper format. Data is translated
automatically (EBCDIC to ASCII and ASCII to
EBCDIC).
Why Use EFI? Access Host Files. For mainframe application
developers, ARBITER provides both Third Party
Program Interfaces (TPPI's) for FOCUS and SAS
and Application Program Interfaces (API's) for
COBOL, FORTRAN, and Assembler. Developers can
create applications to access virtually any
host data.
Transfer between Data Base and PC. Output from
predefined extractions can be transferred
directly to a remote disk. Conversion to
specific PC application program formats enable
immediate use of the data at the PC.
Transfer between Data Base and Remote Disk.
Transfer of PC data from local disks to remote
disks is transparent. DOS I/O commands, such
as COPY, are intercepted and ARBITER performs
the data transfer and stores the information
on the remote disk in the PC format.
Submit Batch Jobs (SAS Extracts). The program
managers provide canned extraction procedures
for use by Agency users through ARBITER'S EFI.
The user simply specifies the extraction
routine's name from a PC menu or supplies the
name on DOS command. The mainframe extraction
runs in batch and the user has the option of
being notified upon its completion. After the
mainframe extraction has been completed, the
PC user can access the extracted data from
either the PC local disk or from the virtual
disk, depending upon the request. The data
will be translated to the format specified and
is available for the standard PC applications
to process.
-------
ARBITER
8
Other mainframe data can be transferred between
mainframe Physical Sequential (PS) and
Partitioned Organization (PO) flat files using
EFICOPY. EFICOPY provides a plethora of
optional parameters to control disparate
sequential files, including CRLF, FIXED,
RECLEN, SKIPCC, APPEND, P2HGENR, etc. This
last parameter specifies conversion from PC
print format to host print format; H2PGENR
specifies the reverse.
Capture Data with Existing Tools. Through EFI,
host file information is extracted and
transferred to either local disks on the PC or
remote disks on the mainframe. As an Agency
user, you would use existing tools to select
and capture the mainframe data, and ARBITER'S
EFI to transform and transfer data to local or
remote disks. SAS, FOCUS, COBOL, FORTRAN,
Assembler, and other existing software extrac-
tions can be used unchanged.
-------
ARBITER
9
MAINFRAME Sometimes data on the mainframe is not in
EXTRACTIONS simple text form. Specific programs are needed
to access mainframe data bases and extract data
from them. The steps involved are:
1. A programmer writes a program on the
mainframe that extracts a defined subset
from a data base.
2. An ARBITER System Administrator writes a
description of the extract and lists it as
being available for use.
3. The user issues a command to indicate that
a particular extraction is to be performed.
4. The data is transferred to the remote disk
and formatted as specified.
Example: ACCOUNT.BUDGET.MONTHLY could be
the name of a Predefined Extraction for
selecting the names of all employees in a
sales department with gross sales for the
week exceeding $50,000.
-------
ARBITER
10
INTERACTIVE Interactive Session Relay (ISR) is an ARBITER
SESSION component that allows an ISR3270 mainframe
RELAY session to be held on the PC.
ISR3270 enables a user to log on to a mainframe
subsystem (TSO, CICS) while maintaining an
ARBITER session. ISR emulates a 3278-type
terminal regardless of whether the PC is using
an asynchronous communications connection or
an LU2 communications connection.
ISR can be invoked in three ways:
1. Selected from the main ARBITER menu.
2. Called with DOS command $ISR.
3. Invoked with Alt-F2 from any ARBITER screen.
Why Use ISR? 3270 Emulation. ISR provides the facility to
log on to mainframe sessions and print
mainframe data at the PC. ISR 3270 sessions
let your PC function as a terminal connected
to the mainframe while RDE and EFI remain
active. The 3270 keyboard is emulated
regardless of the type of communications
connection being used.
TSO. CICS. and Other MF Subsystems. ISR is
used when you want to use TSO, CICS, or some
other mainframe applications directly. For
example:
1. Log on to TSO.
2. Create and run a COBOL program that creates
a sequential data set.
3. Invoke EFI.
4.
Transfer data set to a file on the remote
disk.
-------
ARBITER
11
5. Return to DOS.
6. Load the file into LOTUS 1-2-3.
Hot Key between Sessions. Once the ISR3270
session is established, the PC user may hot key
into or out of the session. For example, if
the user is working in LOTUS 1-2-3, by pressing
the hot key (ALT keypad +), the user jumps to
the 3270 window. The PC application is
suspended while ISR3270 is being used.
Pressing the hot key again returns the user to
the PC application.
-------
ARBITER
12
HOW DO YOU USE ARBITER?
EASY TO USE, When used from the PC, ARBITER utilizes pull-
EASY TO LEARN down menus, PC Program Function (PF) keys, and
DOS type commands.
Mainframe users can continue to use mainframe
tools with which they are familiar. ARBITER
provides 3270 emulation on the PC.
PC users can continue to use PC tools with
which they are familiar. Use of virtual disks
data extracted by program personnel is
available at the PC in formats specific to the
PC applications.
MENUS ARBITER uses a hierarchical pull-down menu
system.
ARBITER screens prompt the user and verify
entries on menus.
Erroneous data is flagged and an error message
appears. Correct information remains as is.
On-line context sensitive help is available.
COMMANDS As experience with ARBITER is gained, menus can
be bypassed.
ARBITER functions can be invoked with DOS
commands.
-------
ARBITER
13
USING ARBITER
ESTABLISHING
AN ARBITER
SESSION
ARBITER is always running on the mainframe and
must be started on the PC before it can be
used. To start ARBITER, type a dollar sign ($)
at the DOS prompt and press ENTER.
C:\>$
ARBITER responds to the dollar command by
emulating a mainframe terminal.
The following menu appears:
WELCIK TO TX
U.S. ENVIROM-CWTAL PROTECTION AGlNCt
TELECOfTLINICATIONS NCTVuORK
ENTER COr-tWC OB M FOB CENU
-------
ARBITER
14
The mainframe logon procedure must now be
initiated.
At the EPA Telecommunications Network menu,
type ARB,ARBITER or press PF10,
US. EPA TELECOrriLNICATIONS KCTVORX MEM)
15 20 Tuesday August 23. 1988
TERM
T260624
HOOEL 2
NATIONAL COMPUTER CENTER
LOGICAL i-iaikframe
PF KEY
SELECTION SERVICE
PfKEY
SELECTION SERVICE
PF13
PCICS
ClCS-Pnxxiction
PFI5
NY
Tso-New YorK LHF
PF 11
DCICS
CICS-Develooment
Pf 16
Dv
TS0-Der*er NEIC Lrf
Pf 19
TSO
TSO-NCC
PF 1 7
wic
TSO-wasn info Center
PF8
Email
EMail ACCESS
PF20
SE
TSO-Seattle LMF
Pf 10
ARSITES
Aroiter
PF2I
AT
TSO-Atlar.ia U"lF

PF22
OA
TSS-Dailas LrF

PF23
KC
TSO-Kansas Cltv LTF

PF24
PH
TSO-Pnilaaeltnia Lr.F

PF7
CI
TSO-Cincinnatl LnF

PF3
BN
TSO-Soston LHF

PF4
CH
TSO-Chicago LMF

PF5
SF
TSO-San Francisco LTf
HIT PfKEY OR ENTER SELECTION
After the logon procedure has been entered,
ARBITER displays the following message:
MO021 - Initialization in Progress.
-------
ARBITER
15
ARBITER responds to the mainframe logon by
displaying the Host Signon data entry panel.
Following are the steps necessary to sign on
to ARBITER:
1. Enter a USERID.
2. Enter a password.
3. Enter a RACF group ID.
4. Skip accounting information. Not required.
5. Press F10.
1
~ Arbiter —
Host Signon 11-21-68
-E* I - I
userio I password I new password
JUCA
RaCF woup

Accounting information

ArDiter (H) Cooyrignt (C) 19B6. 1987. 1988 Dy Tangmm Systems Corooration.
Cary NC. USA The ooject ocoe arc all macnine-readaote distrioutlon
materials are oroteetea inder trie coDyrignt laws m anirouoilsned work
All riyits reserved Use oermisslDle Ov license only
Prooertv of Tangram Systems Corooration Aroiter Is a registered traoemar*
of Tangram S/stms Corooration. Cary. NC. USA
F10-Sl7vyi Esc-Carcel Signon
V
-------
ARBITER
16
When ARBITER accepts the signon, it will
display any ARBITER system news. If there is
no Signon News, then the main services panel
will be displayed.

"" ATOiter ~
Signon News
11-21-ea

11/21/88
welcome to trie new EPa m. SYSTEM
Full Aroiter Oocv/nentatlon and PC software online'
For Moint
Docimentatlon —> PUBllCJUSD aRBDOCS ;
Software —> PUBllCJUSQDiSTRIB
If you line auestlons aoout APBlTER olease contact eitner
GARY hfJTCHISON for tecmlcal assistance or
CAflOLYN CHAna.EE for contractual aiestions
¦End of NEWS Oata'
ESC-E*it use t to scroll News Oata
V
-------
ARBITER
17
ARBITER displays the Main Services Selection
Menu illustrated below. The lower right-hand
corner of the screen displays the current
version and release number of ARBITER (Vx.xx),
the node name currently logged on, and the PC's
logical unit name (LUNAME).
•" -Aroiter ""
Main Serv ices Select ton Menu
I
FWCF 5IGN0N TO p*P6ITEB FRCM LU-T2606J16 COMPLETED FCP USEB1D-.EA
¦ temcte Di* Environment Services
¦ Exteottl File interface Services
¦ mtei-active Session Belay Terminal
Signofr from Host broiler
V I 42
ARBITER
T2606216
F l -Help F2-nsgs F3-nain
FiO-Se(ect
E5C-Ouit A/2-I5R AF3-D05
AFIO-Terminate
o The node name is how ARBITER is identified
on the mainframe.
o The LU name identifies the PC to the
mainframe.
Once the ARBITER main Services Selection Menu
is displayed, the user may begin using RDE,
EFI, and ISR by moving the highlighted bar
cursor from one item to the next and selecting
the item desired.
NOTE: If the menu system is not desired,
ARBITER offers DOS commands as an alternative.
-------
ARBITER
18
REMOTE DISK Remote Disk Environment (RDE) allows access to
ENVIRONMENT the mainframe's Direct Access Storage Devices
(DASD) to store data that is directly acces-
sible to a PC. Selecting RDE from the Main
Services Selection Menu presents the user with
the Remote Disk Environment Services selection
panel.
Aroiter
Remote Disk Environment Services
11-21-88
¦ Mount a remote aisk on a virtual Onvt
¦ Dlsrrxxrt a remote cisk from a virtual ixive
¦ Create ana format a new remote aisk on tne host
¦ Delete a remote ai* from the nost
¦ Alter aata for remote flisfc on Most
¦ Pirge Cache for a virutal arlve
¦ List free soace for a remote Olsk Grouo
Fl-Helo F2-flsgs F3-Maln
ESC-Oult AF2-ISB AF3-D0S
F to-Select
-------
ARBITER
19
RDE Each PC user's assignment to an ARBITER group
Assignment is equivalent to the RACF group assigned on the
mainframe. The System Administrator may also
create other groups (i.e., group Public) for
all users to access and share information.
ARBITER groups are collections of disk space
on the mainframe where remote disks are stored.
There is no limit to the number of groups a
user may have security access to, however,
users may only create remote disks in the
groups that they are allowed to access. PC
users must know to which group(s) they have
access authority.
Remote disk names follow a three-level naming
convention. The following example shows a
remote disk name:
PUBLIC.JDCA.TEST1
In this remote disk name, PUBLIC is the group
ID, JUCA is the owner (or RACF group) ID, and
TEST1 is the disk name.
RDE List The PC user may want to know how much free
Free Space space is available in the group(s) in which
he will be creating remote disks. By selecting
"List free space for a remote disk Group" in
the Remote Disk Environment Services menu, the
total amount of space available in the group
and the five largest regions (called "extents")
of available space will be listed. The largest
remote disk that can be created can be no
larger than the largest extent.
-------
ARBITER
20
Aroiter —
ROE List Free Soace
11-21-88
PUBLIC
GrOLO
Soace Statistics for Groio

lotal Free Soace
242Hb
Extents I.
219-B
2
2 ire
3.
360KB
4
36CKD
5
34SK0
Fl-Help F2-ttsgs F3-«ain F^-ROE FlO-€xec ESC-Ouit AF2-ISR AF3-D05
F9-VI ew
RDE Create The "Create and format a new remote disk on the
host" selection from the Remote Disk Environ-
ment Services main menu will create and format
a remote disk using an RDE space defined for
that group. RDE spaces are areas of mainframe
disk space (VSAM relative record data sets)
reserved for remote disks. Creating a remote
disk on the host is like formatting a floppy
disk with the DOS FORMAT command. The host's
disk space is formatted so that it is com-
patible with PC DOS and MS-DOS.
-------
ARBITER
21
When creating a remote disk, the following
characteristics must be specified:
o Name and description.
o Size and format (size can range from 16K to
32MB).
o Root entries.
o DOS volume ID.
The creation of remote disks should follow the
naming convention of GROUPID.USERID.DISKNAME.
Users whose user ID'S do not match the user ID
portion of the remote disk name must specify
passwords when the disk is created. If PUBLIC
is specified, then anyone can access that
remote disk. If a remote disk is created with
a user ID in the user ID portion of the remote
disk name and no passwords are specified, then
that user ID is the only one who can access
that remote disk.
ATDHer —

BD£ Create
I :-2>-aS
Remote Dish Name
Create Parameters
puElC
JUCa
TEST 1
Gtojo
use'io
Name
20n

v»;
Size
Bool
vol tact.
Dos 3
test ois* to loac Umegnie
Description
Remote Disk Passwo'85

READ
lafllTE
ALTER
Fi-Klo F2-risgs FJ-ftain F4-RDE Fi0-E»ec ESC-Ouit Afl-iSR *T3-D0S
F9-view
V
-------
ARBITER
22
RDE Mount After the remote disk is created and before the
PC user can use normal DOS commands, the remote
disk must be mounted. The mount command
associates a remote disk with a virtual drive.
Mounting a remote disk is like inserting a
floppy disk into a disk drive.
When mounting a remote disk, the following must
be specified:
o Name of the remote disk.
o Virtual drive on which to mount the remote
disk.
o Type of access.
• Aroiter ~
ROenouit
I 1-21-63
Bemote 01* Name
PUBLIC
JUCA
TEST 1
Groixj
User id
Name
0
PEaO
Orwe
Access
Pas sworn
Mont
Status
Fl-Helo F2-ttsgs F3-rtain
F4-R0E no-Exec ESC-Quit a/2-iSR
F^-View
Af 3-OOS
-------
ARBITER
23
• Aroiter "
ROE noint
lt-21-88
Mount
Status
0
fleac
F

Bl 101 - i-Vxrit comoietea for virtual arive 0:
Remote Disk Name
PUBLIC
juCa
TEST 1
Orou)
userio
Name
E.
READ

Drive
Access
Password
Fl-Helo F2-fljgs F3-ttain F4-R0E FlO-€*ee ESC-Ouit AF2-ISR AF3-D0S
F9-Vlew
Other commands serve the following functions:
DISMOUNT
ALTER
DELETE
Disassociates a remote disk from
a virtual drive.
Alters user ID, name, descrip-
tion, and passwords of remote
disks.
Deletes a remote disk from the
host and releases the host disk
space for use by another remote
disk.
PURGE
Purges the cache for a virtual
drive.
-------
ARBITER
ARBITER can allocate memory to serve as a cache
for a virtual drive. When used, RDE cache
reads clusters of data from a remote disk and
buffers all sectors. Using RDE cache can
improve ARBITER performance when using remote
disks. The Purge command allows the user to
purge the cache. Subsequent requests for data
will cause ARBITER to go to the host to read
the data.
EXTERNAL
FILE
INTERFACE (EFI)
EFI Transfers External File Interface (EFI) allows file
transfers between a PC and the host or between
remote disks and the host. A PC user can
specify how the data in the files should be
processed during the transfer. EFI commands
are used to initiate file transfers.
Arotter ~
Main Services Select ion Menu
11-21-68
¦ Remote 01* Environment Services
¦ External file interface Services
¦ Interactive Session Relay Terminal
¦ Slgnoff from Host >rt>lter
VI 42
ARBITER
T2606216
Fl-Helo F2-mgs F3-Maln
FlO-Select
ESC-Oult A/2-ISR AF3-OOS
AFIO-Terminate
-------
ARBITER
25
— ATOiltr —
External File interface Services
11-21-63
File Transfer
¦
SEND
PC file —» Host
¦
RECV
Host --» PC File
¦
SENOR
Remote Disk —>> Host
¦
RECVB
Host •>> Remote Disk
Otner EFI Services
¦
SELECT
Preoefinec Extraction
¦
06XFEB
DataBase Transfer
¦
SU0HIT
Suxnit joe to Host
Fl-nelD F2-rtsgs F3-ttain
F lO-Selec
ESC-Ouit AF2-ISB aFJ-OOS
One example of an EFI transfer is the RECVR
command.
The RECVR command initiates an interactive or
batch file transfer from the host to a remote
disk. The following information must be
supplied:
o Name of the source host data set.
o Name of the remote disk,
o Name of the receiving PC file,
o Processing mode (interactive or batch).
o Replace option.
-------
ARBITER
26
Host —» Remote Olsfc
~ Arotter ~
File Transfer
l1-21-88
public
juC—
TEST i
Gnxc
User
Disk name

TExT
TEXT
FIXREC
Binary
fas sworo
Transfer Tyce
Front
Host DSN IjEAJUCA AR9ITERDATA
rfcmogr (TEST2 ) |
To
I FllePatn IaRBTEST
|Reolace | no| J£atc^08^NoJ
FI-HelD F2-l"lsgs F3-Hain F4-R0E FIO-Exec ESC-Ouit AF2-ISR AF3-OOS
F9-VI«w
If YES was specified in the "BatchJob" field,
the name of the mainframe job under which the
transfer is to execute must be entered. A
default job name may be used by pressing ENTER.
Current job card information can be displayed
by pressing F9. The job card information
displayed here can be left as is, changed for
the current transfer only, or changed for all
following transfers. The PC user also has the
option of being notified when the transfer has
completed.
Other options available are:
SEND initiates an interactive file transfer
from the PC to the host.
RECV initiates an interactive file transfer
from the host to the PC.
SENDR initiates an interactive or batch file
transfer from a remote disk to the host.
-------
ARBITER
27
Predefined A predefined extraction is a mainframe task
Extractions that PC users can select from the EFI Prede-
fined Extraction panel.
Aroiter
External File interface Services
n-21-88
File Trsisfer
¦
SEND
PC rile —>> Most
¦
RECV
Most ••»> PC File
¦
SENOft
Remote Disk —» Host
¦
RECVR
Host •>> Remote Disk
Otfter EFI Services
¦
SELECT
Predefined Extract Ion
¦
CSXFEB
DataBase Transfer
¦
SUBMIT
Suomit Jooto Host
Fl-Helo F2-nsgs F3-Main
FlO-Selec
ESC-Ouit AF2-ISB AF3-OOS
ARBITER stores predefined extraction programs
as separate members of an EFI Partitioned Data
Set (PDS) . The EFI PDS is logically associated
with a group by the use of the EFI PDS
statement contained in the parameter library's
group member. Predefined extractions must be
written by a programmer before a PC user can
access them. A predefined extraction can be
any batch job stored on the mainframe in an EFI
PDS and identified to one or more ARBITER
users. Once a predefined extraction has been
created and a PC user selects it from a panel
or with a command, ARBITER assembles all of the
JCL and control information necessary to
complete the transfer.
The SELECT command initiates a predefined
extraction from a mainframe data base and
transfers the data to the remote disk speci-
-------
ARBITER
28
fied. A PC user can select the extraction
desired from a list and transfer data to the
remote disk specified in the format specified.
The following information is required:
o Name of the extraction.
o Destination remote disk name.
o Name of the receiving PC file.
o PC format of the data (used only for
predefined extractions that use ARBITER'S
SAS interface).
o Mainframe batch job under which the
extraction is to execute.
~ Arbiter ~
Predefines Entractton 01-26-89
PUBLIC
JUCA
FOCSaS

WKI
WK 1
DBF
pen

GrouO
User
Oukname

Passworo

format

Extract
GrouO
PUBLIC
Category aRSSahPi.
| Name SaS
Samp
To
FilePatn | /SaSSaTawki
GrKOCO
Yes

jcxjname
soti'y
Fl-Heto F2-Msgs- F3-Mam F4-EFI FlO-E*ec ESC-Ouit AF2-ISS aH-DCS
F9- view
V

-------
ARBITER
29
Data Base A PC user may copy a whole SAS data base to a
Transfers remote disk for access by a PC application.
Data base transfers may only be executed in
mainframe batch mode.
An entire SAS data base may be copied to a
remote disk by selecting DBXFER Data Base
Transfer from the External File Interface
Services menu (Page 27). The following
information is specified:
o Destination remote disk name,
o Name of the receiving PC file,
o PC format of the data.
o OS data set name of the SAS data library,
o Name of the SAS data set in that library,
o Mainframe batch job.
ArDlter
SAS Oats Base Transfer
01-26-09
PUBLIC
JU5D
private
Gnxo
User
Oiswiame
Passwcra
DBF
DBF
pn-i
Format
CSV
SaS is a registered traoemar* of SAS institute, inc. Car/, nc. USA

SASUB
5YS2 SaS V l R5fi 16 MAPS
SaSDS
COUNTIES
To

r uefatn
/iAhLNi r ijtoi-

GhkSa,-.0
Yes
jooname
Notify
STANDARD
Trans, ator
STANDARD
KERMlT
INDJFII.E
F 1-Helo F2-MSQS FVMain F4-ESI MO-txee ESC-Ouit AF2-ISR AF3-OOS
F9-view
-------
ARBITER
30
FOCUS
Data Base
Extraction
A FOCUS data base extraction is similar to a
SAS data base transfer.

•* Aroiter ••
Stancalone FOCUS GataDase extraction

Enter your destination Remote Olstt Password
FOCUS Is a registered trademark of information Builders inc. New York. NY USA
aRSITER
&-K

'U6LIC
JUCA
FOCSAS
-
Node
User 10
Password
jrouo
Owner 10
Disk
Passwonj
master
JlDS FOCUS MASTER Data
EnPlOYEE |0aia0SN | JIOS FOCUS EMPLOYEE QaTaBaSE
OataOO
Oos Patn /F0CDATAD6F
06F
Format
D6F
WKS
WKI
Yes
Replace
Yes
Acoend
No
Yea
Titles
OKEnPT
Yes
Joocard
Notify
Fl-HelD FlO-SuOmit ESC-AOanooo Tao-Next
-------
ARBITER
31
INTERFACE ISR is an optional component that enables a PC
SESSION to log on to another subsystem (e.g., TSO,
RELAY (ISR) CICS) while maintaining an ARBITER session.

U.S. EPa TE1JEC0MTLNICATIO6 NETWORK MEMJ
.15.20 Tuesoay August 23. 1986
TERM
T260624
MOOEL 2
NATIONAL COTWiTTER CENTER
LOGICAL MAI*FRam£
Pf KEY
SaCTlON SERVICE
PT
-------
ARBITER
32
At the EPA Telecommunications Network Menu, the
user selects TSO or CICS and proceeds to log
on.
-------
ARBITER
33
ADVANTAGES
USES CURRENT
KNOWLEDGE
Users can use ARBITER with their current
knowledge base. Mainframe users can use
ARBITER without any training, as can PC
users. Each group can continue to use the
EPA systems as they are presently doing.
A mainframe user can log on to the mainframe
through ARBITER* s ISR.
A PC user can use remote disks by simply
"mounting" the appropriate ARBITER Remote
Disk ID.
Execution of standard PC applications
software (e.g., LOTUS 1-2-3 and dBASE)
permit the use of the remote disk trans-
parent to the user other than the mount
command and specification of the DOS path
to the disk.
Through ARBITER, the program manager can
select, retrieve, and convert data from all
Agency mainframe data bases (FOCUS, SAS,
ADABAS) . He can transfer the retrieved data
to virtual disks residing on the mainframe
or directly to the PC's local disk.
COMPARABLE WITH
HARDWARE AND
SOFTWARE
ARBITER supports Agency asynchronous and
synchronous links. It provides CRC error
checking, data compression, and retrans-
mission requests.
ARBITER is compatible with all existing
Agency communications adapters, such as
Forte, DCA, IBM, and CXI 3278/79 emulation
boards.
o All DOS commands except FORMAT, DISKCOPY,
and CHKDSK operate with the PC's virtual
disks on the mainframe in the same way as
the commands operate on the personal
computer.
-------
ARBITER
34
o ARBITER is compatible with the Agency's
mainframe and microprocessor software
applications, Local Area Networks (LAN's),
and gateways.
o ARBITER is compatible with LOTUS 1-2-3,
dBASE III, and WordStar.
o ARBITER is compatible with SIDEKICK,
Advanced NetWare, and QuadMaster.
EASY TO USE/ o Agency users will find ARBITER'S pull-down
EASY TO LEARN menus, command structure, and on-line help
familiar and easy to use.
o Users can continue to use the tools they are
now familiar with for information processing
tasks.
o Adapting to ARBITER is nearly effortless.
ARBITER performs exhaustive error checking
and automatically provides information on
screens prompting the user for entries.
o With experience, users will bypass menus and
execute ARBITER commands as DOS commands.
OPERATES AS A o ARBITER is a VTAM application, much like
VTAM APPLICATION CICS and TSO. Since ARBITER is a VTAM
solution, it requires less overhead than
normal CICS solutions and will support an
unlimited number of users.
o With fewer layers of software between the
PC user and the information, ARBITER saves
processor overhead.
o Less overhead results in better response
time.
o Hundreds of users can access mainframe
resources simultaneously — as many as the
mainframe systems can handle.
-------
ARBITER
35
ARBITER uses the network more efficiently.
An advanced data compression scheme
streamlines bulky 3270 screens from the
terminal emulation board, decreasing
transmission time and maximizing network
resources.
API'S FOR
SOFTWARE
DEVELOPERS
ARBITER provides application program
interfaces so that application developers
can create information solutions and write
their own transfer programs in PL/I, COBOL,
C, Assembler, FORTRAN, or PASCAL.
Mainframe applications can be offloaded to
the PC's; subsets of mainframe data can be
stored on DASD by organization or user group
to provide regional processing of corporate
data.
INTEGRATED WITH
SECURITY AND
ACCOUNTING
o ARBITER as a VTAM subsystem fully supports
the RACF security package.
o The Agency does not have to program any
exits or make other coding changes to
install ARBITER.
o The security already in place controls
access to the mainframe data.
o ARBITER leaves a detailed audit trail when
a PC accesses data on the host.
The PC now has unlimited virtual storage on
the mainframe (controlled by a System
Administrator) and access to the mainframe
print facilities. Access, rights, and usage
of facilities can be controlled through
interfaces to RACF and CA-JARS, the security
and accounting systems.
-------
GIS Program Development:
Lessons from the Montana
Natural Resource Information System
Allan Cox
GIS Coordinator
— Montana
=NRIS Natural Resource Information System
Montana Statt Library (*06) 444-S354
ISIS l*$t tlh iwfiut. flriiwa. tfoniana S3S20
-------
Natural Resource
Information System
Montana State Library
Helena, Montana
Montana Natural Resource Index
A geographic and subject indexing system for natural resource information
Montana Natural Heritage Program
Computer-assisted inventory of Montana's biological resources,
emphasizing rare, threatened, or endangered plant and animal species and
biological communities
Montana Water Information System
Provides data on surface water, groundwater, water quality, riparian
areas, water rights, climate data, and more..
Geographic Information System
An automated system for the input, management, analyses, and output of
spatial data
-------
WHAT IS A GIS ?
An automated Geographic Information System (GIS) is a
tool for managing geographic feature location data and
data related to those features. In a GIS, the map data
are separated into common thematic data layers. These
layers are manipulated to derive new data, to perform
complex spatial analyses, and generate maps.
Roads
Common GIS Applications
Water quality monitoring
Timber stand management
Wildlife habitat research
Facility management
Emergency planning
Transportation planning
Legislative apportionment
' Lit nil Use
Topography
Hydrography
-------
NRIS GEOGRAPHIC INFORMATION SYSTEM
The Geographic Information System program was established
in the fall of 1987 as a program of the Natural Resource
Information System at the Montana State Library. The NRIS
supports GIS development in a variety of ways:
¦ GIS Production Services
¦ GIS Development
¦ State-wide GIS Coordination Support
. Montana GIS News
. Montana GIS User's Group
. Montana GIS Activities Directory
• Montana GIS Data Inventory
. Montana Interagency GIS Technical Working Group
. Montana Interagency GIS Steering Committee
. USGS State Mapping Advisory Committee.
-------
Montana Geographic Information System provides
digital mapping and analytical services as well as
technical assistance to agencies developing in-house GIS
capability.
Current Projects:
• Clark Fork Superfund GIS Support
• Clark Fork Nutrient Assessment GIS
• Powder River Basin Coal & Water Resources
Monitoring GIS
• Northwest Energy Generating Resource GIS
• U. S. Forest Service Land Classification GIS Project
-------
Superfund uIS
Project
Upper Clark Fork Basin
Provide G1S support and
services to the Montana
DHES and the EPA pertaining
to Superfund sites in the
upper Clark Fork.
- GIS management
- Spatial analysis k
map production
- Training/technical
assistance
-------
Missoula
Clark Fork River
Superfund Sites
Uilltovn * 200
'V1V ¦* V
s-nLv-
m,v
MiWown
Reservoir
i 1~90
Clinton '»rlifc-v.
/ >>\ • v * « ^ % Beormour^x •,
Drummond
«V
Goldcreek
>>|IDeer lodge
Philips burg
Worm Springs \
Opportunity Ponds \ ^vl'yjt
\
r*JKr
Worm Springs
Ponds
Berkeley
,Pit ..
( S « /¦> ,'x >
v*"AVX Rocker «o
V
Study area of the
Silver Bow Creek site
15 Miles
Prepared by: Montano Stole librory
Clork fork CIS Project
Anaconda
Anoconda site
Silver Bdvj Creek
Ramsey ' jf "
Montana Pole site Buiie
-------
BACKGROUND
• Mining has been the primary industry for the past 100
years within the upper Clark Fork River watershed.
• Widespread contamination has occurred as a result of
these mining and related activities.
• Four sites-comprising the largest Superfund area in the
nation-in the area are currently in the National Priority
List
• Each site presents a highly complex series of human
health and environmental problems.
• The sites are interrelated to the extent that actions taken
at one of the upstream sites can impact a downstream
site.
-------
USER BASE
The Clark Fork GIS serves a large user base:
• Environmental Protection Agency
• Montana Department of Health and Environmental
Sciences
• Contractors
• Potentially Responsible Parties
• PRP Contractors
-------
USER SERVICES
• MAP PRODUCTION
Data Presentation
Planning
Public Meetings/Briefings
- Field Work
Work Plan Documentation
Report Illustration
• DATA INPUT
• SPATIAL ANALYSIS
• TECHNICAL ASSISTANCE
Data Interpretation
Work Plan Preparation Assistance
Data Administration/Management
Data Sampling Plan Design
• GIS TRAINING
-------
APPLICATIONS
• The GIS is geared to respond to project manager
requests.
• One strength of the GIS is the ability to remain
flexible in response to demands and requests.
• Two methods of response:
Rapid response for data, analysis,
graphics, and reports
Long-term products and analytical
applications
-------
APPLICATION EXAMPLES
• Population Estimation per 36 Priority Soils Sites
• Volumetric Calculations for 25 Waste Source Areas
• Estimations of "True" Surface Area for Each Land
Use Category in Each Basin
• Waste Repository Siting Support
• Soil Sample Classifications (Arsenic/Lead)
• Management of Site/Operable Unit Activities
-------
WHAT WORKS
• Integration among other GIS projects and NRIS
programs (e.g., WQB, BPA, Water Information
System, Heritage, etc.)
• Establishment of a Technical Working Group and
Steering Committees
• Broad and easily applied set of access guidelines
• Blanket access for certain contractors
• Ease of user requests:
Usually by phone
No paperwork for user
-------
WHAT WORKS
• Ability to work with and exchange data with PRPs
and their contractors
• In-house data conversions.
• Contracting our data input (digitizing, photo
interpretation)
• Mixing large scale & small scale
• Remaining flexible in project plans and applications
• Being creative, inventive, imaginative
-------
WHAT WORKS
• High level of dedication, creativity, and
enthusiasm among the GIS staff
• Taking the lead:
Demonstrating what GIS can do
Testing potential applications
• Production tool development
(e.g, COMPTRAK, IMP, GRIDGEN, GNIS,
MSLDIG, and TXT ARC/INFO AMLs, etc.)
• Service bureau mentality
• Meeting deadlines
-------
WHAT WORKS
• Giving more than the users ask for
• Suggesting uses
• Rapid response to project managers
• Authority of GIS coordinator to schedule work load
(Uses guidelines established by the TWG)
• Being located in the Library (NRIS) allows us to
serve a varied user group
-------
WHAT DOESN'T WORK
• Project managers and other users will not be
hands-on users
• Data validation is difficult:
Data come from a variety of sources
Data history is not always available
Sometimes the collection agency no longer
exists
Sometimes access is denied to the data history
• Data input by our shop:
No image processing
Very little digitizing
• Education of system users has to be done often due
to staff changes
-------
WHAT DOESN'T WORK
• Project plans change often ("Applications Come and
Go") as a result of:
Negotiations
Changes in project managers
Alterations in sites/operable units
Changes in funding (loss or gain)
Changes in contractors
Inability to obtain data in a timely fashion
-------
BPA/DNRC Gio Project
3

' ' >'s > * .j^ >'
vftvvM'
Nfl.VT&ViQ&Vi
mW&im
Entire State
Participate in the planning
and construction of the
Northwest Energy/Environmental
Resource Digital Data Base.
-------
Control Frame Draw
Simple forest
Ut i ium For ««i
0«(«lI for«it
R««
-------
OccumocM »f
PlethodoD idahoensis
(C«v fUmi hliautr)
ts ModUm

(Z UlmmAm ^
-------
The Status of Land Ownership and Species Protection
in
The Blackfoot River Stady Area
3K I?' It

Cl.1»0 II
WimM

III.Ul tl

I.(Ill II

'$e JRi—¦
lliliili
Ml.d
'-MM
wm&,
MIS Vw4 >»^i» *!*¦
tnxtSm~*M
-------
Department of State Lands
Coal and Uranium Bureau
NRIS GIS Support
• Assistance in Project Plan Development
• Project Plan Work Tasks
- Hardware/Software Acquisition/Installation
- Database Installation
- Data Identification/Evaluation
- ARC/INFO User Interface Development
- GIS Production Services (Analyses, Maps,
Reports, etc.)
- Technical Assistance/Training
-------
MONTANA
EXPLANATION
POWDER RIVER COAL
REGION OF SOUTH-
EASTERN MONTANA
Powder
River
• irucluroi
basin
Bozeman
WYOMING
I-

cus
ER
>¦
A-1*-
•i K
¦ U),
fr-r. .
1 INDIA
jHEYENNttr
its EftVatic n^-.j
NATfONAL
W\Q
r<
——-1 4S®.
101" 12 30
0 10 20 30 MILES
1 I '—I 1 ' 1
0 10 20 30 KILOMETERS
Figure 1.--Location of the study area.
2
-------
Department of State Lands
Coal and Uranium Bureau
GIS Data Layers
• Abandoned Mine Lands
• Areas of Potential
Alluvial-valley Floors
• Aquifers
• Boundaries
• Climate
• Coal Stratigraphy
• Flood Plains
• Geology
• Hydrography
• Landuse
• Mine Spoils
• Ownership
• Permit Sites
• Public Land Survey
• Railroads
• Roads
• Saturated Pastes
• Soils
• Streamflow
• Utilities
• Water Quality
• Wells
-------
Watei
Bureau G
SVT. , " "p^ Develop a Gi
management
V.
Clark Fork Basin
G1S for the
and analyses
Ofcf of water quality data
for the Clark Fork basin.
- Data base construction
- User interlace program
- Training/technical
assistance
- Spatial analysis k
map production
-------
Host | Water Quality Data | Draw | QuerO Other Data | &dal 4 | Help | Quit |
Water Quality S List
Highway
Uojor Stream
Slreom Which Has
Fisheries Dota
Water Ouditr
Monitoring Slalicn
Notural Heritage
Site
Histxic Preservation Sites
No. i
-------
Clark Fork Basin
Nutrient Source Assessment
Sampling Locations
&0 K 1 k N k
Scale = 1:1632934
Y///A.
Jilutl lonrtt
111 UmUn SnUa
ni«u 5Uii liiftry
zzzza
50 Miles
>
Lake
Peni
Oreille
Flathe

5
oof
March, 1991
Project: WQB91-6
~ liainstem station (Clarlt Pork River)
~ Tributary station
0 Wastewater discharge station
Hydrologic unit boundary
-------
State-wide GIS
Coordination
Montana Interagency GIS
Steering Committee
To identify possible interagency projects
and provide direction to the TWG.
-------
State-wide GIS
Coordination
Montana Interagency GIS
Technical Working Group
Tasks:
Develop Data Documentation Standards
Develop Data Standards
Develop and Test Transfer Methods
Interagency Project Administration
-------
What makes the TWG work?
• Memorandum of Understanding
• High Cost of GIS Development
• NRIS Administrative Support
• Agency Commitment
-------
State-wide GIS
Coordination
Montana GIS User's Group
A statewide consortium of Montana
governmental agencies and businesses
-------

cucia

f
¦roil
IMMD32M99

mew
ciscm
~DDDDQaDDD
tuiui
rets in cuix
riLioi

mm
IIDiSlitll
M.DM »*ILH
Mil 104C
. . • M* « 8
UVilU
jcrruao*
saoaar
(ill. Tit
cit:a
aaaaDapMggg

MONTANA
USCS Digital Line Graph Coverage
7/Zi/U
|| VmIiu HiIi LiWtry
G»»k F.rfc CO
o fofelic l*fi4 S«rtv/t ~ Im4i rod tr»»U
~ fcutdtrirs O ttilrotdi
* Bjdn>jr»pbj O Pip* iiid Tnoiaijiicn Ltoet
-------
Montana Data Directory
Natural Resource Information System
DIRECTORY NEED
¦ No one agency was/is responsible for state-
wide GIS database
¦ Database development occurs as a
"patchwork"
¦ Need to coordinate this decentralized
approach
-------
Montana Data Directory
Natural Resource Information System
THE DIRECTORY SERVES TWO MAIN
FUNCTIONS:
¦ A tool to identify data available from other
agencies
¦ A data documentation management program
for in-house GIS data
-------
Montana Data Directory
Natural Resource Information System
THE MONTANA DATA DIRECTORY IS A
COMPUTERIZED INVENTORY OF:
" GIS Applicable Data
¦ GIS Users and Projects
¦ Current Natural Resource Projects
-------
Montana Data Directory
Natural Resource Information System
THE DIRECTORY IS PRODUCED BY THE
NATURAL RESOURCE INFORMATION
SYSTEM (NRIS) AT THE MONTANA STATE
LIBRARY.
¦ Distributed on computer disks
¦ NRIS provides updates on an annual basis
¦ Disks will be collected from participating
agencies and re-distributed by NRIS
¦ Program is distributed free by NRIS
-------
Natural Resource Information System
11/28/1990
Montana Data Directory
Data Sources Report
DATA THEME:
Theme Description: USGS Digital Line Graph Data, Roads & Trails
Data Fields: DLG Codes - Feature Types
Keywords: roads; transportation; DLG
Region Covered: Upper Clark Fork Basin
DATA FORMAT: Map and ARC/INFO Coverage
DATA QUALITY: Good
DATA COLLECTION/ACCESS:
Date Collected: 01/01/1800
Collected by (Agency): USGS
Availability : Public
Through NRIS : Full Access
On-line access: No Access
Status: Complete
Cost: cost of tape or disk
USER DOCUMENTATION: None.
SPATIAL COMPONENT:
Scale: 1:100000
Projection: UTM Zone 12
Coordinates: Meters
Feature Type: Arc
Documentation: Attribute: Extensive Coordinate: Extensive
Accuracy: Attribute: Good Coordinate: Good
COMMENTS: None.
CONTACT:
Organization: Natural Resource Information System
Department: Geographic Information System
Contact: Cox, Allan, GIS Coordinator Phone: (406) 444-5357
1515 East Sixth Avenue
Helena, MT 59620
- Ongoing
Through Agency: Full Access
Update Freguency: Unknown
Resolution:
Serial No: 173
User ID: 45
-------
Montana GIS News
Natural Resource Information System—Montana State Library
Montana CIS Meeting Set jor
Hillings
MARK YOUU CALENDARS,
TODAY! Q a s c d oil a n
overwhelming response 10 ttic
rc:ulcr survey in ilie first issue 01'
Monta 11 ;i CIS News, a Montana
GIS Conference is now in the
works. Over tlie last six weeks, a
volunteer conference planning
committee lias put together a
strong group of speakers ready to
address some very pertinent
topics (see preliminary agenda,
enclosed).
Rased on feedback from readers,
early December dates (6th and
7ili) were preferred. The
conference will be in Billings,
primarily due to the gracious
offer of Ceoflesearch, Inc. (of
Mings) to serve as host and the
|i so nablc accommodations
irovided by the Sheraton. The
committee was also intent on
moving the conference each year;
the GIS/TlGFIl workshop was in
Helena last year; this year's event
will be in Uillings; next year --
the committee is looking for a
host and a host city!
The day and a half conference
will cost $30 (before 11/15; $*40
after 11/15), including con fere nee
materials, two lunches, coffee at
breaks, and two free drinks
during the poster session.
'CIS User Directory' and 'CIS
Data Inventory' Taking Shape
After some unexpected delays,
drafts of the first editions of the
Montana CIS User Directory and
the Montana CIS Data Inventory
arc now complete. In
mid-October, NR.1S will send
"Review and Approval" Data
sheets to each contributor;
pending any needed corrections,
the first editions of the Directory
and InviMititry will be distributed
at the Montana CIS Conference
in December.
If you haven't taken the time to
fill out the forms to be included
in the Directory or get your data
in the Inventory (remember the
Form A/Form 13 survey in the
April), there's still time left. If
you have questions or need
forms, or simply want to convey
the needed information over the
phone, please call NR1S (4-M-
535't).
State Mapping Advisory Committee
Update
As planned, the State Mapping
Advisory Committee (SMAC) met
on August 17 to get Montana's
mapping priorities to the USGS
for their consideration in the
FY 1000 workplan. Willi input
from several agencies, first and
second priorities were established
for four map types: I) 1:24,000
topographic revisions; 2)
1:100,000 revisions; 3) digital
data both digital line graphs and
digital elevation models; and 4)
land-use and land-cover maps
(1:250,000).
After some cordial discussion, all
SMAC members agreed to line
priorities. Subsequently, SMAC
Chair, Don Cromer, Department
of Highways, prepared and
submitted the Montana's input to
Lee Aggers at the USGS in
Denver. Aggers has informed us
that there is a very good chance
Montana's priorities will be
worked on this year.
Volume 1, Number 2, Fall 1089
Thanks io all who participated in
the "A-16 process". There will be
a formal briefing and poster
display of the USGS mapping
activities at the conference in
December.
Montana CIS News
The Montana CIS News is written
for anyone interested in mapping
and using GIS. It 'contains
material of interest to planners,
foresters, scientists,
cartographers, academicians,
geographers, engineers, and other
professionals that use spatial
information. Montana GIS News,
published quarterly by the
Natural Resource Information
System (NR.IS) at the Montana
State Library in Helena, is
distributed at no charge.
We need your input! Many
people have contacted NRIS
asking us to get the word out on
new ile vclopmeius in Montana
regarding ihe use of GIS. !i is
important that everyone share-
ideas and their experiences on
current projects. If you have any
items or stories to include in this
newsletter, please contact at (406)
'l'M-5354, or write to the Montana
State Library, GlS News, 1515 F.
Sixth Avenue, Helena, MT 50620.
The Montana CIS News is
designed to serve you and your
need for current information.
Your active participation will
make it a useful publication.
Mark your calendars today, anil
plan oil joining us at the Montana
CIS Conference in December!
Montana GIS User Newsletter
-------
EPA Region VIII
State/EPA Data Management Conference
Toxic Release Inventory
by Dianne Groh
April 18,1991
-------
f \
TOXIC RELEASE INVENTORY
• MANUFACTURERS ( SIC 2000 - 3999 )
¦ EQUIVALENT OF 10 EMPLOYEES
• MAKE OR IMPORT 25.000 LBS.
• INCORPORATE 25.000 LBS. INTO
PRODUCT
' USE 10.000 LBS. IN ANCILLARY MANNER
• MUST REPORT RELEASES * OFFSITE
TRANSFERS ANNUALLY
IS JJ
/\
TOXIC RELEASE INVENTORY
IMPORTANT BECAUSE:
PUBLICLY AVAILABLE
MULTIMEDIA
COMMON DATA ELEMENTS
DRIVING DATABASE INTEGRATION
r \
TOXIC RELEASE INVENTORY
POTENTIAL USES OF TRI DATA:
LAND DISPOSAL SITES AS OVERLAY TO
GROUNDWATER AQUIFERS USED FOR
DRINKING WATER
STUDY WASTE COMING INTO STATE VS
WASTE SHIPPED OUT-OF-STATE
IDENTIFY TOXICS-IMPAIRED WATER
BODIES" UNDER CLEAN WATER ACT
FACILITY SITING / LAND USE PLANNPK^/JJ
-------
/\
TOXIC RELEASE INVENTORY
S
' MAP PES'G
REGION vm & STATE MAPS :
RELEASES & OFFSITE TRANSFERS
BV COUNTY
METROPOLITAN DENVER .
FACILITY LOCATIONS & RELEASES
AIR RELEASES ( 3D )
WASATCH FRONT. UTAH : ( UN 1991 )
TOXIC RELEASE INVENTORY
f TRI ACCOUNT USERS IN REGION 8 STATE§\
COLORADO: PAM HARLEY
JUDY WADDtLL
SCOTT PIRATT
MONTANA; TOM ELLERHOFF
GEORGE CHRISTENSEN (CHRIS)
N. DAKOTA: DEAN MONTIETH
ALLEN JOHNSON
S. DAKOTA: CLARK HABERMAN
TIM ROGERS
UTAH: NEIL TAYLOR
BOB SHIP MAN
V^WYOMING: (ED USUI)
A
V
r \
TOXIC RELEASE INVENTORY
TO GET YOUR USER ID AUTHORIZED
FOR ACCESS TO TRIS:
SEND A LETTER WITH :
* YOUR IBM 3090 USER ID
* NAME AND MAIL CODE
• FULL MAILING ADDRESS & PHONE
• PROGRAM YOU WORK IN
TO: DIANNE GROH 8AT-TS
EPA REGION Vm
999 18TH STREET. SUITE 5O0
DENVER. COLORADO 80202

-------
Information Access and Integration Initiatives
-------
§ mmmmm

i • >ys'\»:y.i
If
t
Information Access and Integration
Index Systems
iocalional
:1. >' . r ¦ :
FINPS
CAS
!

J
NEEDS
ERCLIS
STORET
Custom
Analytical Tools
SAS

jSHs; »;¦ >>* ms*<•«»»o*•>••>m»*•>»v-***»i
.,'K' '> - 4 •'-
-------

<*«>&*i i •?v— .
Goals
Facilitate access to EPA data.
Enable integrated analysis of EPA data.
Provide tools for targeting resources.

-------
FINDS: Facility INdex Data System
-------

FINDS Provides a Common Index
FINDS
K
J
msm
EPAI.D
EPA I.D.
EPA I.D
EPA I.D.
EPA I.D
EPA .D.
EPA I.D.
EPA I.D.
NEEDS
STORET
CERCLIS
HWDMS

¦ *< S^-i r''*»"¦> -fenfV'

. 1; .<¦ fv-l »#!
»V'*5-
-------
The OIRM Commitment
1. Perform reconciliations of Priority 1 systems
with FINDS by end of 1990.
% '
I
<•
2. Link FINDS with Dun and Bradstreet file by
March 31,1991.
3. Determine method to keep FINDS synchronized
with program systems.
4. Redesign FINDS to accommodate synchronized
updating and D&B linkage.
-------
What is FINDS?
The Facility INDex System is an EPA data base of
facilities regulated by EPA, with:
• Basic identification information -- a minimal
amount of descriptive information to help users
identify and distinguish regulated facilities,
organized by EPA Facility ID code
• Data source references -- listings of all the
program systems which contain more detailed
data about each facility, including the local or
"source" ID code used within the program
system
-------
i
What does FINDS look like today?
MdtMMNMHtl

IACII.ITY INDI'.X SYSTI'M
I'.I'A II) NiiiiiIkt: . _ 1££E111111112
l uciliiy Nuiiic: UI!AVI1K CRI1I1K
Aililicss: 171 llPAVRH CRF-P.K
Ciiy: I TWAYNI'. Slale: 1£J Zip OkIc: . Jl&fiQ
('imuly: Cong Disl: ......
Owner Ty|>c: < >|iciiili* IVl*:
I hIiIihIc: I 3l/l -oug Simnc:
I ilinIc: I nl/1 x>iig Acumu y:
SK CinIcs:
Imliiui IjiiuI tj
DUNS #
Ictlcial lacilily

l ACll I I Y INDUX SYS'll'M
IN I 11II11119 IlliA VIvK cki:i:k
li t hi•:avi:k STUi-.in
I I WAYNli IN 40660
St
ULLKX LHiAiBAM SXS1LM
OSW Sdl III WAS'I'I- IIWIIMS
Ciwiir WAIIIHUNI' IVS
OAH AIHAMAI) (IKS
OI'IS IIIHA'ISCA I'ATI-S
OliHR SlU'liHI UNI) CliHCIJS
OI'.CM liNI1 A (.'OMI'l. IXtCKKI'
UllW ItHINKINC WAT HIHS
niXIC Mill INV tlt.lS
LAQLI1X IDS USiilliiX
SU URCli I RiXi SiS
iisrr 11111111 •>
iNckKim
ini
3S32S3

F • I • N • D - S
Facility INDox Syslom
rr^g,
-------
How is a "facility defined by EPA?
EPA Facility Identification Data Standard (excerpt)
"A 'FACILITY' is a locational entity, deliberately
established as a site for designated activities, but not
primarily for habitation (even though on-site habitation
may be necessary to the execution of the primary
activities). Examples include a factory, a military base,
a college, hospital, national park, office building, or
prison..."
BU
BE
EPA Facility IDs will be generally assigned to the most
comprehensive level of a complex
-------
"EPA Facility ID Standard" and "Lat/Long Policy"
Facility Identification Data Standard - Requires
assignment to and maintenance of EPA Facility ID
code for all facilities regulated under Federal
environmental law in all data collections where data
exists for a facility.
Locational Data Policy - Requires collection and
documentation of latitude/longitude coordinates and
supporting attributes of the coordinates (method,
description, and accuracy) for entities such as facilities
and monitoring points.
-------

Definition of a Facility Under
Facility Data Standard
POTW
Highway
1
RCRA Pils
lacks
ullcills
«*>w
< *4>htv>; / - <2f..
T^SS^l^??^JS5555S5*!S^B5'^S3S5?^i

^w
-------

;::::f:-:*%.-r•s:;' mv - ¦: •:>•¦ ,;r

Priority Systems
System
Office
s
•?
HWDMS/RCRIS
TR1S
Priority 1 cercus
' DOCKET
} AIRS
FF1S
PCS Majors
I
RCRA
OTS
OSWER
OECM
AIR
Federal Facil.
Water Enf.
I CICIS
1 cus
f FRDS
Priority 2 fits m™ ncdb
FATES
! PCS Minors
| Corporate Linkage Implementation
OTS
OTS
Water
OCM
OCM
Water Enf.

—W"

,KJr" —»+
-------

Catch up Reconciliation Status
HWDMS/RCRIS
(including RCRA SQG's)
TRIS
CERCLIS
DOCKET
AIRS
FFIS
PCS Majors
D& B linkage
Completed July 90 (ongoing)
Completed Oct 90
Completed Aug 90 (ongoing)
Ongoing Updates
Reconcilable records completed Jan 1991
17,185 records unreconcilable
Completed
Completed Feb 90
Started Jan 15
Scheduled completion April 15

-------

Updated Reconcilation of
Priority 1 Systems During 1991
PCS Majors
IRIS
AIRS
April
May
June
FFIS
CERCLIS
D& B Update
HWDMS
DOCKET
July
Ongoing Updates
Sept
Ongoing Updates
(including quality audits)

-------
Objoctive:
Redesign I INUS/I AC IS U) allow implementation
ol facility Identification Dala Slandaid ami lo
cllecl inlogialioii ol lacilily inlormation across
agency program systems.
i'lojecl Spuusuis
OlliCU Ul l;Ml0IC0ll!0Ut
Ollico ol Water
Region V
Accomplislimcn 15
Redesign Ellods.
Mar 90 Completed linhancomunl Needs Analysis
Aug 90 Complelnd Synchronized Updalo Options Analysis
Sep 90 Selected synchronized update option
Dec 90 Completed flNDS/FACIS Redesign I ogic Design
Document
IMiysical Design in Progress
Updalo Efloils
Dec 90 Updated all 1'iioiily I systems 111 I INDS
Corporate linkage with D8.B in progress (-l/l!) comp )
Next Ste&s
Redesign and Implementation Ll/oils:
A|)r9l Physical I )e:;ign
Nov 91 Detailed Systems Design
Dec 91 ADABAS/Nahual Code
f:eb 92 User I est and Acceptance
Jun 92 Conversion and Impleineiilation into I'loductiori
Project leader
Ingiid Meyei, ()ll IM
Updalo Efforts:
FY9I All piioiily II systems
PY9I Repeal updates ol piioiily I system:;
5YSIRMS DEVELOPMENT CEHIi:il
CliNIEM OF E3 ENCE
-------
What will the new FINDS data base structure be?
F • I • N • D • S
Master File
EPA ID: ND1234567890
Name: ABC Chemical
Company
Address: 123 W. Main
St.
City: Fargo
County: Dizmark
Stole: ND
ZIP: 56123
SIC: 2012
DUNS#: 1234567890
•
etc.
Alias File
Program
System
Source
ID
Name
Address
City
County
Slalo
ZIP
PCS
ND000070
ABC Chem
Co.
123. W. Main
St.
Fargo
Mont
ND
5G123
AIRS
14234567
ABC
Chemical
123 Main
Fargo
Moul
North
Dakota
5GI23
STATE
WM123
Windsor
Chemical Co.
123 W. Main
si.
Forgo
Mont
ND
56132
Etc.
Etc.
Etc.
Elc.
Etc.
Etc.
Elc.
Etc.
-------
FACTORS FOR SUCCESS
Facility ID Standard Implementation plans for
each program office/system must be in place
-based on OIRM Implementation Guidance
-based on detailed facility data analysis
with FINDS providing context and
coordination
Memorandum of Understanding between OIRM
and the Program Offices to formalize
commitments
Complete FINDS redesign and implement
sychronized updating as soon as possible
-------
EXAMPLES OF DATA QUALITY PROBLEMS
FINDS provided "dummy" numbers to program offices, states,
regions. In many cases these were used as temporary numbers,
but ultimate reconciliation with FINDS never happened.
Occasional "break-down" of manual reconciliation
procedures between program systems and FINDS
Program systems make changes to their source ID numbers
without retaining previous numbers. Linkage with FINDS is thereby
destroyed and has to be totally redone (TRIS)
Inadequate or conflicting address information resulting in
"duplicate" records in FINDS or "merging" of two different
facilities under one EPA ID number
Conflicting RCRA data handling procedures across
regions - no RCRA HQ control - no single source
of program mediation for data management issues.
FINDS can only be as good as program systems !
Campaign to improve their facility data quality is required.
-------
FINDS / Program System Matches
System
AIRS
DOCKET
FFIS
HWDMS
PCS
TR1S
CERCLIS
total
records
111,748
13,051
5,815
340,662
143,971
27,850
38,080
total
matched
82.5%
99.9%
59.8%
92.4%
11.4%
86.5%
98.2%
unreconcilable
17,784
2,172
135,461
possible
matches
completed
98.2%
99.9%
95.5%
92.4%
90.3%
86.5%
98.2%
remarks
missing adequate
name / address info
missing adequate
name / address info
Minors with mailing
addresses only
-------
GIS: Geographic Information Systems
ssaan
a
-------
¦WJ

GIS Integrates Data Based on Location
CERCLIS
Lai/Long
Lat/Long
Lat/Long
¦1 i
wdlO
1

¦
r—
¦

HWDMS

PCS

STORET

BIOS

NEEDS

Elc.

Lai/Long

Lat/Long

Lai/Long
GIS

. \.. v.. « ¦-: , >i- | m- }••.>¦¦"
-------
GIS as the Spatial Integration Tool
Geographic Information Systems (GIS) provide data entry, storage,
manipulation, analysis, and display capabilities for geographic,
environmental, cultural, statistical, and political data in a common
spatial framework.
Land Cover
Soil Types
Transportation
Hydrology
Topography
-------
Program Goal:
Provide leadership and support to decision makers for
identifying and evaluating environmental conditions
through the development and promotion of GIS
applications and tools. These applications and tools
will enable Agency decision makers to integrate and
visualize our rich existing base of environmental data.
Program Objectives:
- Spatial Data Management (Base Geographic Data)
- Locational Data Administration {Program Systems Data)
- Risk-Based Applications and Tools
- Outreach and Education
Program Leaders:
- Thomas G. Dewald, Manager
- Jeffrey T. Booth
- David R. Wolf
Program Clients:
- EPA Regions. Labs, Special Programs (CBP, GLNPO)
- EPA I teadquarters
- Federal Departments and Agencies
- SlateyLocal and International Governments
Accomplishments:
- Regional Installations and Support Teams
- National Mapping Requirements Program
- Census Bureau Demographic Data MOU
- OW Reach File Preparation for GIS
- Geographic Resources Information and
Data System (GRIDS) as Central Repository
- Locational Data Policy and Locational
Accuracy Task Force
- GIS Software Contract
Next Steps:
- Headquarters Support Team
- Agency-Wide Spatial Data Management Plan
o Needs Assessment
o Acquisition and Leases
o Preparation
o Delivery
o Modifications and Archiving
o Research and Development
- GIS Hardware Contract
- Retooling Regional/Headquarters Hardwaro
- PC-Based GIS Guidance
- Risk-Based Methodologies and Communication
- Locational Data Policy Implementation Guidance
- GPS Implementation Plan
WW*
\v
£
SYSTEMS DEVELOPS ZENTER
CENTER OF EXC zNCE

-------
Building the Infrastructure:
Data
o Environmental Monitoring Data
- Describes location of monitoring sites and other EPA
regulated entities as a single "point"
- Required by New Locational Data Policy
EPA
or
Submitters
National Environmental
Systems
PCS
GIS Map Layer
Gateway
OIRM
?
-------

Building the Infrastructure:
Data (continued)
o Base Geographic Data
- Stream Networks, Political Boundaries, Demographic ...
Issues: Spatial Data Management Plan including needs,
preparation, delivery, remote sensing, QA/QC
Office
of Water
OIRM
Designated
Lead Federal
Agency
OIRM
(58,000 Map Sheets)
(Stream Network)
-------
GATEWAY
-------
The Gateway as
the Common User Interface
User
T
Gateway

3
D&B
CERCLI5
HWDMS
D&B
PCS
STORET
BIOS
NEEDS
Etc.
jjfr .ttfUKtjjttf,*- 'Wv
>• " .V-'-kfikVA- •'•
-------
Gateway Development
Retreat
[Gateway Concept I
1 I
Rcquircmcnls
GIS
Users
DATA BASUS
STANDARDS
INIO
MEEDS
AUDIUNC8

GATEWAY
User
Interface
fC?u 4V
ei nn
OPERATIONS & MAINTENANCE
onihH
"¦fr
Program Systems
rma unmmnmr r^TTr
-------
STORET
THE
RIGHT ANSWER
( STORET
-------
What is STORET?
A computerized information management system residing
on EPA's main frame in RTP, North Carolina
Under its umbrella are three sub-systems: Water
Quality System (WQS), Biological System (BIOS),
and Daily Flow System (DFS)
It is made up of software modules allowing the user
to store, retrieve, and using its analytical packages,
to analyze water quality information
( STORET )
J
-------
What is in STORET?
Location information for over 700,00 sampling sites
which are situated in both groundwater and all types of
surface water (lakes, streams, estuary, etc.)
Each site has information for EPA's minimum set of data
elements including: Agency Code (Who Owns the Data)
Station ID, State and County Codes, Latitude/Longitude,
USGS Hydrologic Unit Code, and a brief narrative about the
site's location
Optional identifiers are: EPA basin codes, EPA's Reach
Segment Number, Aquifier Codes, Ecoregion ID, Station
Elevation, Depth of Water, and More Narrative Information
( STORET
j
-------
What is in STORET?
/? v%::
•• ffi: ;¦
For the 700,000 sampling sites, there are over 180 million
observations
Each observation is identified by: Agency Code, Station ID,
Date, and EPA Parameter Code
Optional identifiers: Sample Depth, Time of Sample,
Composite Qualifiers, Special Codes for Special Projects,
e.g., Special Groundwater Identifiers
STORET has over 11,000 parameter codes which identify
the constituent being measured, the medium being
sampled, phase, and its units
V
STORET ")
J
-------
Who Uses STORET?
In any one year, over 400 different people access STORET
either to store data or to extract data
Even though EPA acts as the steward of the system, the data
are owned by the users
The data users and contributors include: 46 States, the
USGS, the US Forest Service, US Bureau of Reclamation,
Corps of Engineers, Interstate Agencies, e.g., River Basin
commissions, and other Federal Agencies
As can be seen, the prime attribute of STORET is the
availability and sharing of data
V.
STORET )
j
-------
How is STORET Used?
Detecting changes in pollution levels
Demonstrating the effects of pollution abatement programs
Assisting in basin planning and management
preparing data for permit processing
meeting reporting requirements
Checking water quality against established
criteria
Repository for toxic monitoring data
( STORET )
-------
Why Use STORET?
Well established system (developed in 1964)
Widely available (States, Regions, and Other FEDS)
Data from many sources
Versatile (many output types and easily portable)
Well established user support group
Training availability
STORET
-------
How is Data Presented?
Tabular lists of the data
Comparison of curent and historical data
Built in statistical capabilities
Graphical representations
Locational and analytical maps
Easily passed to other statistical packages
Down-loadable to floppy diskettes
Transportable via tape to other mainframes
( STORET
-------
Where is STORET Today?
New user friendly retrieval interface via menus
New user friendly storage menus being tested
On-line inter-active help and documentation through menus
New training media being developed
New reference documentation being developed
New user support procedures being implemented
Systems documentation being written
Modernization effort initiated
( STORET )
-------
Why Modernize STORET?
Ensure STORET's usefulness and viability for the future
by following EPA's modernization goals
Reduce dependence on customized software and hardware
to support data base management tool
Reduce personnel/resource dependent systems functions
Increase system's ability to evolve with EPA's
water program
STORET
-------
Status of STORET Modernization
Chosen as one of the modernization projects of
the Systems Development Center
Developing project work plan for the modernization
effort
Conducting STORET symposium in Fall to
communicate with and involve users in the
modernization process
A needs assessment analysis being planned
v*
( STORET
j
-------
Results of Modernization
Easier system to maintain
Standardize retrieval procedures
Ease data integration
Incorporate data quality indicators
Reduce long term costs of system
Utilize new technologies
Impart institutional knowledge
STORET )
-------
Overview of EPA's Systems Development
and Information Integration Initiatives
Briefing for the
Region VIIISEDM Meeting:
Denver, Colorado
April 17,1991
U.S. EPA, Program Systems Division
-------

Objectives & Approach to Briefing
Objective: Establish a Basis for a Continuing Dialogue on:
- Systems Development & Data Integration Projects
- between OIRM, State, and Regional staff
Approach: (1) Describe EPA's IRM Environment,
Culture, and OIRM's Role in It;
(2) Describe PSD's Functions & Projects
(3) Listen to Your Comments & Questions
Program Systems Division
-------
EPA's IRM Environment & OIRM, PSD
Phil P.
A Futuristic View of Data Management
Video
Data Integration Initiatives
Phil L.
STORET Modernization
Louie H.
STORET Demonstration
Louie H.
v
Program Systems Division
-------
OFFICE OF
ADMIN. &
RESOURCES
MANAGEMENT
-> OIRM
-> NDPD
-> Budget
Program Systems Division
Administrator
OFFICE OF
PESTICIDES
& TOXIC
SUBSTANCES
OFFICE
OF
WATER
OFFICE OF
RESEARCH &
DEVELOPMENT
OFFICE OF
ENFORCEMT&
COMPLIANCE
MONITORING
OFFICE OF
SOLID WASTE
& EMERGENCY
RESPONSE
REGIONAL
OFFICES &
LABORATORY
PROGRAMS
OFFICE
OF
AIR AND
RADIATION
OFFICE OF
POLICY,
PLANNING &
EVALUATION
EPA Organization Chart
-------
EPA's IRM Culture
EPA is a highly decentralized organization,
with each major office being led by a strong
Assistant Administrator.
Aggressive, knowledgeable, and independently
minded Regional Offices.
1 Generally speaking, decisions at Headquarter's arc
made by consensus - not dictate; and sometimes
the process is slow.
Program Systems Division
\
-------
¦ Myth about OIRM: OIRM is a well-financed gorilla capable
of easily stopping or controlling a program office's systems
development projects either by mandate or financially.
In reality. OIRM's approach is more support-oriented and
consultative in nature.
In the future. OIRM's MOSES (Mission-Oriented Systems
Engineering Services) contract will put greater emphasis
on quality systems development practices and use/adherence
to Agency systems and data standards.
Program Systems Division
-------
EPA's Information Environment

WATER
PCS, STORET
WASTE
RCRIS
TOXICS
TRIS
OFFICE OF INFORMATION RESOURCES
MANAGEMENT (OIRM)
Roles:
OIRM:
- Support development agency wide
- Provide leadership on data integration
- Develop data standards
- Build systems development infrastructure
Program Offices:
- Develop national program systems
- Operate & maintain data systems
- Implement standards in systems
- Modernize & enhance systems
E
Program Systems Division
-------
r
OIRM's Two Environmental Information Divisions

Office of Information Resources Management
(OIRM)

A1 Pesachowitz, Director
Paul Wohlleben, Deputy Dir.

Program Systems Division (PSD)
Abby J. Pirnie, Director
Rick Martin, Deputy Dir.
C
Client Services Branch
Phil Lindenstruth, Chief
C
C
Systems Development Branch
Joe Sierra, Chief
Systems Planning & Analysis
Bill Stuart, Chief
rn
I Br
Technology Branch
Barbara Jarvis, Chief
>
>
DH
C
Information Integration Branch
Jeff Byron, Chief
Information Management & Services *
Daiva Balkus, Director (IMSD)
Vacant, Deputy Dir.
Information Management Branch :
Sieve l lufford, Chief ¦ ¦
V - ¦:v;:" f--' J
r
.... Infomiation Acci
;ms; Branch
Brigid Rapp, Chi
V .
cf:; : .
¦ J
1 nformation Sharing Branch ;
Michele Zenon, Acting Chief

Program Systems Division
-------
Lead:
Support/Assistance:
- Modernizing Systems Develop-
ment Infrastructure (SDC)
- Information Engineering/CASE
- MOSES Contract
- Data Integration Strategy
- National GIS Program
- FINDS Development/O & M
- GATEWAY Development
- GRIDS
- Relational DBMS Workgroups
-Global Positioning Systems
-LATF Implementation
-Facility Identification Std. Implmtn.
-National Mapping Requirements Prgm.
-EPA National Systems Managers Mtg.
-Systems Modernization Fund (SMF)
Projects:
-AIRS: Area & Mobile Source Subsystem
-Image Processing Pilot for Prcmanf. notices
-Public Access to Permit Compliance System
Program Systems Division

-------
PSD Functions
Build systems development infrastructure, or 'Center of
Excellence', for modernizing EPA's environmental data
systems (Systems Development Center - SDC)
Modernize key mission critical systems (e.g., STORET)
Support development and implementation of IRM policies
and standards (e.g., LATF)
Develop and support integrated data systems (e.g., FINDS)
and tools for cross-media analysis (e.g., GIS)

Program Systems Division
-------
Background: States and Regions want greater involvement/
interactions with HQ on systems development projects, and
greater access to data integration tools. (SEDM Forum, Harvard)
• OIRM/PSD Perspective: Meeting this need will require
initiative, commitment, and resources from not only
Headquarter's (HQ), but also from the IRM and program
operations of the States & Regions.
Program Systems Division
-------

Future Challenges for Headquarter's
Challenges:
(1) Keep States & Regions better informed of HQ activities;
(2) need to better understand how States & Regions use and
manage information;
(3) need to better understand how HQ/Regions/States currently
interact on development and data integration projects; and
(4) identify 'process' mechanisms for improving or increasing the
quality of those interactions.

Program Systems Division
-------

State /Regional IRM Challenges
Challenges:
(1) Educate HQ on how your programs currently operate
(e.g., SEDM & Regional program office interactions);
(2) consider what projects you want more information on, greater
involvement with HQ on, and what level of involvement you are
seeking in specific terms;
(3) organize yourselves, articulate your interests, and offer 'process'
solutions for improving HQ's, Regional, and State coordination
efforts (e.g., lead regions or state for a project or issue)
Program Systems Division

-------

r >
Projects and Initiatives

1. Systems Modernization Initiative (Handout)

2. Public Access To EPA Databases (Handout)

3. Data Integration Initiatives: (Phil L.)

•FINDS

•GIS

• Gateway

4. Modernization of STORET (Louie H.)
i

-L Program Systems Division

J
-------

Systems Modernization Initiative (SMI)
Systems Development Center (SDC)
Systems Modernization Fund (SMF)
EPA IRM Steering Committee
PSD Client Services Staff
Program Systems Division

-------
\
Systems Development Center (SDC)
/
Today:
- Staff within Program Systems Division focusing on improving how
EPA develops environmental data systems
- EPA staff co-located with contractor staff on contractor's site
- Focusing on developing a modern systems development infrastructure
~ information engineering to improve systems quality and consistency
~ Computer Aided Systems Engineering (CASE) tools to assist developers
— project management standards for better scheduling and cost estimation
- Educating IRM community on standards, technology & development issues
- Developing a new systems development contract to replace EPA's
existing General Programming (GP) contract
Program Systems Division
-------
Tomorrow (Fall,' 91):
- The General Programming Contract will be replaced by MOSES
(Mission Oriented Systems Engineering Services) contract
- MOSES will be the prime contract for systems development at EPA;
the potential term or life of contract is 7-years
- Requires contractor to establish a facility to be called the Systems
Development Center (SDC)
- Facility would have to accomodate EPA staff for purposes of managing
the contract; contract includes an award fee, based on performance
- Contractor would adopt an "EPA Way of Doing Business" as prescribed
by PSD (e.g., information engineering, CASE, and project management)
Program Systems Division
-------

Systems Modernization Fund (SMF)
Features:
• Fund of approximately $4 million per year
• Purpose is to provide funding assistance to "projects" to
develop or enhance important EPA data systems
• SMF is a strategic tool for motivating modernization
• Projects done in partnership with SDC and program offices
• Eight systems development projects funded last year
based on a competitive process
• PSD is currently considering and evaluating new approaches
to managing the Fund
Program Systems Division
-------

Projects:
Sponsor:
Status:
l.
AIRS - Area & Mobile Sources Subsystems
Office of Air & Radiation
Completion in 92
2.
OTS - Image Processing System
Office of Toxic Substances
Pilot test system 9-91
3.
LANs as a Platform for a National System
Superfund program
Completed study
4.
Labor and Sample Tracking System (LAST)
Region VII
Inactive
5.
STORET Modernization
Office of Water
Very Active
6.
Public Access to Permit Compliance System
Office of Water
Start-up
7.
Easy Access to TRI (Toxic Release Inventory)
Office of Toxic Substances
Folded into Gateway
8.
GATEWAY and Data Integration Initiative
OIRM
Strategic and action
planning underway
Program Systems Division
\
J
-------

EPA IRM Steering Committee
Committee of State, Regional and Headquarter's Senior
Managers appointed by the Deputy Administrator
Advises EPA on Information Policy and Resource
Management Issues
Meets twice a year and is chaired by A1 Pesachowitz

Program Systems Division
-------
Public Access
Draft Policy: It is EPA policy that all official Agency
information shall be created, collected,
maintained, and managed in a manner
which will promote access to and dissemination
of that information to the public.
Headquarter's Debbie Ross, IMSD
Contact: National Public Access Program Manager
(202) 475-7705

Program Systems Division
J
-------
f

f ^
Public Access

Systems-Level Projects and Other Initiatives:
• Toxic Release Inventory/Title III

• Program-Specific Activities
- OW's Compendium of Water Data
- PCS Public Access

• Center for Environmental Statistics (OPPE)

• GATEWAY To EPA Information (PSD/OIRM)

1
-L Program Systems Division
V

J
-------
¦>
Functions and Goals:
Present analyses of environmental conditions and trends
Prepare and publish reports on a regular basis
Perform functions to improve quality of environmental
data and analyses
Considering publication of a directory of environmental
databases
Program Systems Division
V
-------
-------
Overview of the State/EPA Data Management (SEDM) Program
Environmental protection depends on effectively managing, interpreting, and presenting vast amounts of data. To meet these challenges,
EPA recognizes that it must be responsive to State and local governments that collect most environmental data and make most
environmental protection decisions. The Agency's State/EPA Data Management (SEDM) Program, with its associated financial
assistance program, represents one of EPA's responses to this challenge.
The SEDM Program is implemented through the EPA Regional Offices under the guidance of the Office of Information Resources
Management (OIRM) in EPA Headquarters. It is divided into two phases— Phase I: Data Sharing, and Phase II: Data Integration.
Phase I seeks to establish a reliable flow of regulatory and compliance data between EPA and the delegated States. Phase II focuses on
assisting States and Regions in integrating data across programs and media to maximize environmental results.
NATIONAL GOALS:
Phase I:
• Provide a direct communication link between the States and the EPA data network;
• Provide States with direct access to data in EPA's national data systems; and
• Establish policy statements on data integrity and protocols.
Phase II:
• Provide the States and EPA with the data, methods, and technology required to conduct integrated environmental
analyses and to plan and manage cross-media programs; and
• Build effective long-lasting aiTangements for sharing data and technology among environmental agencies at all
levels of government.
The specific benefits of the SEDM Program include:
• Efficiencies in data collection which will result in significant gains in data handling and routine program operations;
• Enhanced data quality to guide programmatic decisions and support program oversight;
• Improved data integration to more effectively target regulatory and compliance activities based on risk reduction and to enhance
the capability to manage for environmental results; and
• A more productive working relationship between EPA and the States to focus on environmental management and minimize data
disputes.
This program is of strategic importance to EPA's overall efforts to enhance vital data resources and move toward more productive State
and Federal roles in environmental protection.
- 1 -
-------
I
I
I
Name
Region viii
State/EPA Data Management (SEDM) Program
Strategic Plan Worksheet (Draft— 316191)
REGIONAL GOAL:
It is the goal of the State/EPA Data Management (SEDM) program in Region VIII to lay a foundation for effective data
management within its six states to ensure more effective sharing and integration of data with the Region VIII office.
There is a strong conviction within Region VIII that the need for high quality and easily accessible data cuts across all EPA and state
environmental programs. Furthermore, the future of environmental management points increasingly towards cross-media, cross-
programmatic, and inter-agency analysis of environmental data.
Region VIII also believes that, in order to conduct sophisticated environmental analyses, attention must first be paid to improving
existing data and data management practices within its regional office and six states (Colorado, Montana, North Dakota, South Dakota,
Utah, and Wyoming).
To that end, the initial objectives of the Region VIII SEDM program are to provide its states with the basic tools, organization, policies,
etc. needed to enable sharing and integration of environmental data in the future.
1989-94 OBJECTIVES:
In a five-year timeframe, the Region VIII SEDM Program shall attempt to achieve the following six objectives:
Priority
(High/
Mai' Objectives and Initiatives (edit as necessary):
Low):
1. COMMUNICATIONS — Improve communications and the working relationship between EPA and the Region VIII states by:
• Installing a direct telecommunications link to a single point of presence in each state;
• Working with state programs to provide a linkage between the SEDM program and state strategic plans and to identify
obstacles to greater participation in the SEDM program;
-2-
-------
• Creating a clearinghouse of information relating to data management activities within EPA and the states;
• Publishing a newsletter of SEDM activities within the region;
• Creating a regional directory of state and EPA contacts and SEDM resources;
• Establishing contacts with other national, international, and state agencies (e.g., USGS, BLM, and DOE) for the purposes of
environmental data sharing;
• Hosting regional SEDM conferences to create a forum for information sharing and strategic planning;
• Encouraging participation in national work groups and conferences; and
• Distributing guides, brochures, and other information about the SEDM program.
2. ORGANIZATIONS — Form organizations which facilitate data sharing and integration, in particular:
• Identifying a coordinator for the SEDM program in each state;
Organizing in each state a steering committee composed of senior-level representatives from each program to address long-
term data management issues;
• Forming a technical advisory committee to recommend to the steering committee solutions to technical problems;
• Defining roles and responsibilities for data management service organizations; and
Working with state representatives to define a data management career track, training opportunities, and other incentives to
encourage longevity for data management professionals within state organizations.
3. TECHNOLOGY TRANSFER — Provide for the transfer of technologies important to data sharing and integration by:
• Investing in current technologies which have been demonstrated to be effective in environmental management, in particular:
•• Local Area Networks (LANs);
•• Geographical Information Systems (GIS);
•• Laboratory Information Management Systems (LIMS);
~~ workstation technology;
•• centralized, easy-to-use menus and transparent interfaces to environmental systems; and
•• centralized facility permitting, compliance, and enforcement systems.
-------
• Investigating newer technologies as they become available and sharing this information with other Region VIII states,
including such technologies as:
•• expert systems and other artificial intelligence tools;
•• optical disk (WORM and CD-ROM) and other mass data storage technologies; and
•• Geographic Positioning Systems (GPS).
• Educating state staff to identify opportunities to introduce new technologies into their organizations through the development
of methodologies and evaluation criteria;
• Providing technical assistance to state staff to use new technologies effectively; and
• Assisting state and local governments, Indian tribes, and universities in achieving funding objectives for data integration
projects, particularly through the SEDM financial assistance program.
4. POLICIES AND PROCEDURES — Develop policies and procedures to improve coordination between EPA and the
states, specifically:
• Defining and implementing a SEDM coordination policy and protocols;
• Developing Memoranda of Understanding (MOUs) to resolve data integrity issues; and
• Creating and updating the state SEDM implementation plans to ensure that requests for EPA assistance are promptly
addressed.
5. DATA — Improve the quality (i.e., completeness, timeliness, and comprehensiveness) of environmental data submitted to
key EPA data systems (AIRS, AFS, FRDS, GICS, PCS, RCRIS, and STORET) by:
• Identifying deficiencies or inconsistencies in:
•• the above EPA data systems and other EPA and state data systems, as applicable,
•• state and/or EPA data collecting and handling procedures, and
•• types or amounts of data collected;
• Ensuring that states acquire new computer equipment, or upgrades to existing equipment, as necessary to facilitate the
collection, manipulation, and reporting of data to EPA;
• Providing states with the training and technical support necessary to use EPA systems effectively and efficiently;
• Providing states with the resources (e.g., timesharing dollars) and capabilities (e.g., user accounts) for direct access to data in
key EPA data systems; and
-4-
-------
More effectively coordinating the administration of data with state priorities and strategic plans, SEAs, program MOUs, and
JAGs.
. STRATEGIC PLANNING — Develop a long-term strategy for data integration within each state by:
Assisting each state in developing a 5-year data management strategic plan with tics to individual program strategics and
State/EPA Agreements. This plan would involve:
•• identifying appropriate data applications for ADP platforms,
•• integrating existing computers and networks, and
•• setting standards for hardware and software.
Identifying and conducting data integration pilot projects to pinpoint environmental problems; and
Achieving top-down and bottom-up support for data management initiatives.
-------
8
i
-------
UNITED STATES ENVIRONMENTAL PROTECTION AGENCY
REGION VIII
999 18th STREET - SUITE 500
DENVER, COLORADO 80202-2405
APR I 8 i99l
Ref: 8 PM-ARA
1991 Region VIII State/EPA Data Management Conference
Dear Participants:
By the time you read this, you will have just completed
nearly three full days of presentations, demonstrations, breakout
sessions, and consensus building activities. I hope, at this
point, that you feel we have accomplished our two main goals for
the conference: developing a strategic plan for the program and
sharing information vital to improved data management.
I very much appreciate your participation in the conference.
Thank you for coming and have a safe trip back!
Region VIII Program Manager
State/EPA Data Management
-------
=:::
. : ; .-xvL^jHfc-E3*25§E3i:
¦£i:::JSm» / V - "f" ?>S.j. V
g^s«|JBBj(^io«viii ^ ¦- v
:!=¦¦•'- ' ^ ^ca?>> vx
/..
"Making sure the right hand knows what the left hand is doing."
Region VIII SEDM Conference
Feedback Form
April 16-18,1991
Please leave with the conference staff Before Leaving
These feedback forms will be used when planning future Region VIII SEDM Conference to ensure that any necessary
improvements are made. We would appreciate your input! Results will remain confidential.
1. How informative and useful were the presentations on:
a. Regional and state overviews (Circle one)
1
2
3
4
5
Major waste
of time
Poor
Fair
Good
Incredibly
Enlightening
National initiatives? (Circle one)
1
2
3
4
5
Major waste
of time
Poor
Fair
Good
Incredibly
Enlightening
Program Updates? (Circle one)
1
2
3
4
5
Major waste
of time
Poor
Fair
Good
Incredibly j
Enlightening
i
Technology Transfer? (Circle one)
1
2
3
4
5
Major waste
of time
Poor
Fair
Good
Incredibly
Enlightening
[Please complete both sides]
-------
What impact do you think the strategic planning sessions will have on the SEDM Program
in Region VIII? (Circle one)
12 3 4
5
It will never Smalt Moderate Large
change impact impact impact
We have set THE
plan for SEDM
How would you rate the organization/logistics of the conference? (Circle one)
12 3 4
5
Complete Confused Adequate Good
chaos
Flawless
Overall, how would you rate the SEDM conference? (Circle one)
1 2 3 4
5
Major waste Poor Fair Good
of time
Incredibly
Enlightening
Would you come to another SEDM conference [for state people, even if you had to pay your
own way]? (Circle one)
v 1 ' 2 . 3 4
5
Never If there were Maybe Probably
again some changes
You couldn't
keep me away
6. What would you like to see done differently at the next SEDM Conference?
7. Any other comments or suggestions?
Name (Optional)
Thank you for coming to the Conference!
-------
EPA Region VIII
State/EPA Data Management Conference
Registration List
April 16-18, 1991
EPA REGION VIII
Kerrigan G. Clough - Assistant Regional Administrator
Nola Y. Cooke - Director, Office of External Affairs
Irwin L. Dickstein - Director, Air and Toxics Division
Max H. Dodson - Director, Water Management Division
Robert L. Duprey - Director, Hazardous Waste Management Division
Jack W. McGraw - Deputy Regional Administrator
James J. Scherer - Regional Administrator
Thomas A. Speicher - Regional Counsel
Jon Yeagley - Acting Director, Environmental Services Division
POLICY AND MANAGEMENT
Kathleen Anderson, Program Analyst
Joyce Brame, Grants Specialists - Grants Management Branch
Sharon Childs, Program Analyst
Brenda Combs, Programmer Analyst
William Gillespie, Director - Office of Strategic Integration
Beverly Goodsell, Grants Specialist - Grants Management Branch
Gerald Hunt, Programmer Analyst
Jerry Jones, ORD Regional Scientist
Brad Lundock, LAN Administrator
Rudy Martinez, Communications Specialist
William Murray, Section Chief - Data Integration Office
Martha Nicodemus, Branch Chief - Grants Management Branch
Marcella Osterholt - Region VIII SEDM Program Manager
Pat Porter, LAN Administrator
Paul Riederer - Deputy Director, Policy and Management
Carole Vandenberg, Regional Enforcement Coordinator
Alfred Vigil, Branch Chief - Information and Computer Management
Barbara Wagner, Regional Librarian
Linda Walters, Grants Management Branch
AIR AND TOXICS DIVISION
Mark Aguilar, Environmental Engineer
Dianne Groh, Section 313 (TRI) Program Manager
Robert Harding, Section Chief Toxics
Bev Rios, AIRS-AFS SEDM Program Coordinator
1
-------
ENVIRONMENTAL SERVICES DIVISION
Marvin Frye, Laboratory Section Chief
Marlin Helming, AIRS-AQS SEDM Program Coordinator
Gordon MacRae, Environmental Scientist
Deanna Peterson, Quality Assurance Management Section Chief
Marshall Payne, Technical Operations Branch Chief
HAZARDOUS WASTE DIVISION
Terry Anderson, RCRA Implementation Branch Chief
Pat Godsil, Deputy Director - Hazardous Waste Division
Bob Kinkel, Federal Facilities Compliance Analyst
Clint Lemmons, Environmental Protection Specialist
WATER MANAGEMENT DIVISION
Alicia Aalto, NPDES Permits Section Chief
Minnie Adams, GICS SEDM Program Coordinator
Steve Burkett, NPDES Compliance Branch Chief
Jim Dunn, Groundwater Branch Chief
Rich Gomez, Public Water Supply Database Administrator
Debra Griffin, PCS SEDM Program Coordinator
Toney Ott, Project Officer
Chester Pauls, UIC Program & Enforcement Section Chief
Michael Reed, NPDES Compliance Assurance Section Chief
Doris Sanders, Public Water Supply Program Section Chief
David Schmidt, FRDS SEDM Program Coordinator
EPA HEADQUARTERS
Louis Hoelman, Systems Analyst - OIRM STORET
Philip Lindenstruth, Chief - Client Services Branch
Phillip Paparodis, Director for Outreach
Alvin Pesachowitz, Director - Office of Information Resources Management
Donna Ventriss, National SEDM Program
EPA NATIONAL COMPUTER CENTER fNCO
Donald F. Fulford, Director - National Data Processing Division
Lonnie Haines, CSC, Telecommunications Specialist
John Stevenson, UNISYS, Technical Director
Steve Stoneman, UNISYS, LANSYS Group
2
-------
STATES
COLORADO
John Aaron, Hazardous Materials and Waste Management Division
Steve Arnold, Program Manager
Rick Barrett, Principal Air Pollution Control Specialist
Kevin Briggs, Air Pollution Specialist
Gerard Bulanowski, SEDM Coordinator
Roy Doyle, Air Pollution Control Specialist
Daniel Ely, Air Specialist
Rosa Erlich, Engineering Aide
Steve Fine, Industrial Hygienist
Bob Graves, Air Pollution Specialist Sr.
Susan Harman, Administrative Officer
Bill Hague, Air Specialist
Mark Kendra, Engineering Aide
Lynne Keilman, Administrative Officer
Jim King, Senior Air Pollution Specialist
Tom Looby, Assistant Director OHEP
Jonathan Love, Senior Professional Engineer, CO Rocky Flats Program
Bev Lynn, Systems Manager, Data Services
Barbara MacRae, Air Pollution Specialist C
Dennis Myers, Public Health Engineer
Lloyd Nicholson, Principal Electronic Specialist
Dan Ondrejko, Data Services
Robert Osterburg, Air Specialist
Gordon Pierce, Air Specialist
Patrick Reddy, Air Pollution Specialist
Scott Swanson, Senior Electric Specialist
Thomas Tayon, Asbestos Certification Coordinator
Candy Thomson, Hazardous Materials and Waste Management Division
Abe Vasquez, Engineer
MONTANA
Allan Cox, GIS Coordinator for NRIS (State Library)
Pamela Dale, Information System Specialist (Water Quality Bureau)
Abe Horpestad, SEDM Coordinator
Don Mittelstaedt, Environmental Specialist (Water Quality Bureau)
Steven L. Pilcher, Administrator - Environmental Sciences Division
Jim Stimson, Water Information Specialist for NRIS (State Library)
NORTH DAKOTA
Francis (Fritz) Schwindt, Chief - Environmental Health Section
Allen Johnson, Data Processing Coordinator
3
-------
SOUTH DAKOTA
Perry Delzer, Computer Support Specialist
Patrick Rice, Director - Technical & Support Services
Robert E. Roberts, Secretary - Department of Water and Natural Resources
Ron Woodburn, SEDM Coordinator
UTAH
Kenneth L. Alkema, Director - Division of Environmental Health
Bumell Cordner, Director - Bureau of Air Quality
Robert Shipman, SEDM Coordinator
Gayle Smith, Director - Bureau of Drinking Water Sanitation
WYOMING
Robert Gumtow, Planning Analyst - Water Quality
Dennis Hemmer, Director - Department of Environmental Quality
James Uzzell, SEDM Coordinator
others
Miguel Flores, Chief Monitoring - National Park Service - Air
Pat Kluck, Colorado Center for Environmental Management
Ron Lupinski, Booz*Allen & Hamilton
Sandy Lutovsky, Booz*Allen & Hamilton
Patricia O'Sullivan, Booz*Allen & Hamilton
Ron Salerno, Tri County Health
Karen Smith, Environmental Engineer - Argonne National Laboratory
Terry Taylor, Colorado Information Management Commission
4
-------
9
-------
10

-------
MARCELLA (MARCE) OSTERHOLT
Program Manager, State/EPA Data
Sharing
&EPA
U.S. ENVIRONMENTAL PROTECTION AGENCY
Region VIII
999 18th Street Suite 500
Denver, Colorado 80202-2405
(303) 293-1505
-------