EPA-456\B-95-001
AFS User's Guide
AF3
AFS Data Storage
Version 8.1
U.S. Environmental Protection Agency
Office of Enforcement and Compliance Assurance
Enforcement Planning, Targeting and Data Division
Washington, DC 20460
November 2008
-------
AFS User's Guide
AF3 AFS Data Storage
TABLE OF CONTENTS
SECTION PAGE
1.0 Introduction 1-1
1.1 The Purpose of AFS 1-1
1.2 The Organization of AFS 1-1
1.3 AFS Data Storage Overview 1-2
1.3.1 AIRS Subsystems 1-2
1.4 AFS User Support 1-4
1.5 AFS Logon Procedures 1-4
1.5.1 TCP Logon 1-4
1.5.2 CICS Logon Procedures 1-8
1.6 AFS Logoff Procedures 1-13
1.6.1 CICS Logoff 1-13
1.6.2 TCP Disconnect 1-14
1.7 Function keys 1-15
1.7.1 Other Special Keys 1-16
1.8 AFS Security 1-17
1.8.1 AFS Security Profile 1-17
1.8.2 Access Levels 1-17
1.8.3 Data Ownership 1-18
1.8.4 Sensitive Data 1-20
1.8.5 State and Federal Private Data 1-22
1.9 Update Techniques 1-23
1.9.1 Online Update - Repetitive Data Entry 1-23
1.10 AFS Data Relationships 1-25
1.10.1 AFS System Files 1-25
1.11 Key Data Screens and Detail Data Screens 1-29
1.12 Mandatory Data 1-29
1.13 Non-modifiable data fields 1-36
1.14 On-line Help 1-36
1.15 Error and Informational Messages 1-36
1.16 Screen Feature 1-36
1.17 Aggregation of Emissions Values (Bubbling) 1-37
1.17.1 Example of Bubbleup 1-39
1.17.2 Units Conversion 1-39
1.18 Emissions, Process Rate and Control Equipment Efficiency Calculations 1-39
1.19 Utilities 1-42
1.20 Toggle Feature 1-43
1.21 Year 2000 - Guidelines for Dates in AFS 1-46
2.0 On-Line Updating 2-1
2.1 Accessing On-Line Update 2-1
2.2 Plant Identification 2-2
2.3 AFS Update Menu 2-7
2.3.1 AFS Plant Update Menu 2-8
2.3.1.1 Plant General 2-9
2.3.1.2 Plant Pollutant 2-14
November 2003 i Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
2.3.1.3 Plant Air Programs 2-16
2.3.1.4 Plant Pollutant Air Program 2-19
2.3.1.5 Permit Administration 2-21
2.3.1.6 Plant Mailing Label 2-31
2.3.1.7 Plant Actions 2-32
2.3.1.8 Plant Comments 2-38
2.3.1.9 Plant Asbestos Information 2-40
2.3.1.10 Plant High Priority Violator Utility 2-44.1
2..3.1.11 Compliance Monitoring Strategy (CMS) 2-46
2.3.2 AFS Stack Update Menu 2-47
2.3.2.1 Stack General 2-48
2.3.2.2 Stack Pollutant 2-50
2.3.2.3 Stack Comment 2-52
2.3.3 AFS Point Level Update Menu 2-54
2.3.3.1 Point General 2-55
2.3.3.2 Point Pollutant 2-60
2.3.3.3 Point Air Program 2-62
2.3.3.4 Point Monitor 2-65
2.3.3.5 Point Continuous Emissions 2-67
2.3.3.6 Point Tank 2-71
2.3.3.7 Point Action 2-73
2.3.3.8 Point Comments 2-78
2.3.4 AFS Segment Level Update Menu 2-80
2.3.4.1 Segment General 2-81
2.3.4.2 Segment Pollutant 2-84
2.3.4.3 Segment Chemical 2-87
2.3.4.4 Segment Projected Pollutant 2-89
2.3.4.5 Segment Comments 2-92
3.0 Batch Updating 3-1
3.1 Introduction 3-1
3.2 Update Transactions 3-1
3.2.1 Transaction Formats 3-1
3.2.2 General Format of AFS and AFX Batch Transactions 3-2
3.2.3 General Coding Instructions 3-5
3.2.4 Year of Emission Inventory Processing 3-6
3.2.5 General Edits 3-7
3.2.6 Add Transactions 3-7
3.2.7 Change Transactions 3-10
3.2.8 Delete Transactions 3-11
3.2.9 Error Reporting 3-11
3.2.10 Accept and Reject Files 3-12
3.3 AFS Compare Submittal 3-13
3.4 Batch Edit/Update Process 3-26
3.4.1 Introduction 3-26
3.4.1.1 What Has Changed 3-26
3.4.1.2 Edit WorkGroup Recommendations Added 3-27
3.4.1.3 Overview 3-27
3.4.2 Invoking the New AFS Batch Update Processes 3-31
3.4.3 Submitting an Edit Job 3-35
3.4.4 Edit/Update Output Reports 3-44
3.4.5 Submitting an Update Job 3-47
3.4.6 Notification 3-52
November 2003 ii Table of Contents
-------
AFS User's Guide
AF3
AFS Data Storage
3.4.6.1 Copying Reports to Another User 3-52
3.4.6.2 Notifying Other Users by State Code 3-52
3.4.7 Submitting Utility Transactions 3-58
3.4.8 Edit/Update Processing Details 3-63
3.4.9 Resource Access Control Facility (RACF) 3-69
4.0 AFS Utilities 4-1
4.1 Accessing Utilities 4-1
4.2 Utility - Merge Plants (Association) 4-4
4.3 Utility - Merge Points 4-8
4.4 Utility - Unmerge Plants 4-11
4.5 Utility - Delete 4-14
4.5.1 Plant Level Delete 4-16
4.5.2 Stack Level Delete 4-19
4.5.3 Point Level Delete 4-21
4.5.4 Segment Level Delete 4-22
4.5.5 Inventory Delete 4-23
4.5.6 Contractor Delete 4-25
4.5.7 Landfill Delete 4-26
4.5.8 Permit Administration Delete 4-27
4.6 Utility - Undelete 4-32
4.7 Compliance History 4-35
4.8 Source/Point Swap 4-37
4.9 Archive 4-40
4.10 Dearchive 4-42
4.11 User JCL Parameters 4-43
4.12 Table File Lookup Utility 4-45
4.13 SIP Inventory Utility 4-51
4.14 Update AFS Plant ID 4-53
4.15 Submit Current Utility File 4-55
APPENDIX A AFS Batch Transaction Formats
APPENDIX B AFS Generate Unknown Compliance Utility Flowcharts
November 2003
Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
LIST OF ILLUSTRATIONS
FIGURE 1-1 AIRS SUBSYSTEMS AND RELEVANT USER'S GUIDE VOLUMES 1-3
FIGURE 1-2 TCP LOGON SCREEN (WHEN SIGN-ON CHARACTER IS KNOWN]
USER RESPONSES ARE UNDERLINED 1-5
FIGURE 1-3 TCP LOGON SESSION (WHEN SIGN-ON CHARACTER IS UNKNOWN)
USER RESPONSES ARE UNDERLINED 1-6
FIGURE 1-4 EPA WELCOME SCREEN 1-7
FIGURE 1-5 CICS LOGON SCREEN 1-7
FIGURE 1-6 EPA MENU SYSTEM SCREEN 1-8
FIGURE 1-7 CICS LOGON SCREEN 1-9
FIGURE 1-8 EPA2 TSO/E LOGON SCREEN 1-10
FIGURE 1-9 AFS MAIN MENU SCREEN 1-11
FIGURE 1-10 AFS MAIN MENU SCREEN 1-12
FIGURE 1-11 EPA CICS MENU SYSTEM SCREEN 1-13
FIGURE 1-12 EPA MENU SYSTEM SCREEN 1-14
FIGURE 1-13 AFS SECURITY PROFILE FORM 1-19
FIGURE 1-14 AFS UPDATE ROAD MAP 1-27
FIGURE 1-15 AFS BROWSE ROAD MAP 1-28
FIGURE 2-1 AFS MAIN MENU SCREEN 2-1
FIGURE 2-2 IDENTIFICATION SCREEN 2-2
FIGURE 2-3 CONFIRMATION TO ADD A NEW FACILITY 2-3
FIGURE 2-4 NEGATIVE ANSWER TO CONFIRMATION SCREEN 2-4
FIGURE 2-5 AFS RESPONSE TO NEGATIVE ANSWER ON CONFIRMATION SCREEN 2-5
FIGURE 2-6 PLANT NAME SEARCH SCREEN 2-6
FIGURE 2-7 AFS UPDATE MENU 2-7
FIGURE 2-8 AFS PLANT LEVEL UPDATE MENU 2-8
FIGURE 2-9 GENERAL INFORMATION FOR PLANT GENERAL SCREEN 2-10
FIGURE 2-10 COMPLIANCE 'PAGE' OF PLANT GENERAL SCREEN 2-10
FIGURE 2-11 EMISSIONS 'PAGE' OF PLANT GENERAL SCREEN 2-12
FIGURE 2-11.1 MACT DETERMINATION 'PAGE'OF PLANT GENERAL SCREEN 2-13
FIGURE 2-12 CONFIRMATION TO CHANGE MAILING LABEL INFORMATION 2-15
FIGURE 2-13 PLANT POLLUTANT KEY DATA SCREEN 2-15
FIGURE 2-14 PLANT POLLUTANT UPDATE SCREEN 2-15
FIGURE 2-15 AFS PLANT AIR PROGRAMS KEY DATA SCREEN 2-16
FIGURE 2-16 AFS PLANT AIR PROGRAMS UPDATE 2-17
FIGURE 2-16.1 SUBPARTS 'PAGE' OF PLANT AIR PROGRAMS 2-18
FIGURE 2-17 PLANT POLLUTANT AIR PROGRAMS KEY DATA SCREEN 2-19
FIGURE 2-18 PLANT POLLUTANT AIR PROGRAM UPDATE SCREEN 2-20
FIGURE 2-19 PERMIT ADMINISTRATION UPDATE MENU 2-22
FIGURE 2-20 PERMIT APPLICATIONS UPDATE SCREEN 2-23
FIGURE 2-21 GENERAL INFORMATION - DRAFT PERMIT UPDATE SCREEN 2-24
FIGURE 2-22 APPLICATION ASSOCIATIONS - DRAFT PERMIT MENU SCREEN 2-25
FIGURE 2-23 APPLICATION ASSOCIATIONS - DRAFT PERMIT UPDATE SCREEN 2-26
FIGURE 2-24 PLANT PERMIT COMMENTS UPDATE SCREEN 2-27
FIGURE 2-25 EVENT TRACKING ACTIONS UPDATE SCREEN 2-28
FIGURE 2-26 EVENT TRACKING ACTION COMMENTS UPDATE SCREEN 2-29
FIGURE 2-27 FEE UPDATE SCREEN 2-30
FIGURE 2-27.1 HPV UPDATE SCREEN 2-45
November 2003 iv Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 2-28 PLANT MAILING LABEL UPDATE SCREEN 2-31
FIGURE 2-29 PLANT ACTION KEY DATA SCREEN 2-32
FIGURE 2-30 PLANT ACTION UPDATE SCREEN 2-33
FIGURE 2-31 PLANT ACTION - CONSENT DECREE/ADMINISTRATIVE ORDER
PATHWAY UPDATE SCREEN 2-34
FIGURE 2-32 PLANT ACTION - VIOLATIONS PATHWAY
UPDATE SCREEN 2-35
FIGURE 2-33 PLANT ACTION - ADMINISTRATIVE PENALTY PATHWAY
UPDATE SCREEN 2-36
FIGURE 2-33A PLANT ACTION - FCE PATHWAY UPDATE SCREEN
2-36.1
FIGURE 2-34 PLANT COMMENTS KEY DATA SCREEN 2-37
FIGURE 2-35 PLANT COMMENTS UPDATE SCREEN 2-38
FIGURE 2-36 PLANT ASBESTOS UPDATE MENU 2-39
FIGURE 2-37 ASBESTOS CONTRACTOR KEY DATA SCREEN 2-40
FIGURE 2-38 ASBESTOS CONTRACTOR UPDATE SCREEN 2-41
FIGURE 2-39 ASBESTOS LANDFILL KEY DATA SCREEN 2-42
FIGURE 2-40 ASBESTOS LANDFILL UPDATE SCREEN 2-43
FIGURE 2-41 ASBESTOS PERFORMANCE KEY DATA SCREEN 2-44
FIGURE 2-42 ASBESTOS PERFORMANCE UPDATE SCREEN 2-45
FIGURE 2-42.1 PLANT HIGH PRIORITY VIOLATOR UPDATE UTILITY SCREEN 2-44.1
FIGURE 2-42.2 PLANT COMPLIANCE MONITORING STRATEGY UPDATE SCREEN 2-46
FIGURE 2-43 AFS STACK LEVEL UPDATE MENU 2-47
FIGURE 2-44 AFS STACK KEY DATA SCREEN 2-48
FIGURE 2-45 AFS STACK GENERAL UPDATE SCREEN 2-49
FIGURE 2-46 AFS STACK POLLUTANT KEY DATA SCREEN 2-50
FIGURE 2-47 AFS STACK POLLUTANT DATA UPDATE SCREEN 2-51
FIGURE 2-48 AFS STACK COMMENT KEY DATA SCREEN 2-52
FIGURE 2-49 AFS STACK COMMENT UPDATE SCREEN 2-53
FIGURE 2-50 AFS POINT LEVEL UPDATE MENU 2-54
FIGURE 2-51 AFS POINT GENERAL KEY DATA SCREEN 2-55
FIGURE 2-52 AFS POINT GENERAL UPDATE SCREEN
COMPLIANCE POINT 2-56
FIGURE 2-53 AFS POINT GENERAL UPDATE SCREEN
EMISSIONS POINT 2-57
FIGURE 2-54 AFS POINT GENERAL UPDATE SCREEN
MERGED POINT 2-58
FIGURE 2-55 AFS POINT GENERAL UPDATE SCREEN
'EMISSIONS PAGE 2' 2-59
FIGURE 2-56 POINT POLLUTANT KEY DATA SCREEN 2-60
FIGURE 2-57 POINT POLLUTANT UPDATE SCREEN 2-61
FIGURE 2-58 POINT AIR PROGRAMS KEY DATA SCREEN 2-62
FIGURE 2-59 POINT AIR PROGRAMS UPDATE SCREEN 2-63
FIGURE 2-59.1 SUBPARTS 'PAGE' OF POINT AIR PROGRAMS 2-64
FIGURE 2-60 POINT MONITOR KEY DATA SCREEN 2-65
FIGURE 2-61 POINT MONITOR UPDATE SCREEN 2-66
FIGURE 2-62 CONTINUOUS EMISSIONS KEY DATA SCREEN 2-67
FIGURE 2-63 CONTINUOUS EMISSIONS UPDATE SCREEN - 1ST PAGE 2-68
FIGURE 2-64 CONTINUOUS EMISSIONS UPDATE SCREEN - 2ND PAGE 2-69
FIGURE 2-65 POINT TANK KEY DATA SCREEN 2-70
FIGURE 2-66 POINT TANK UPDATE SCREEN 2-71
FIGURE 2-67 POINT ACTION KEY DATA SCREEN 2-72
FIGURE 2-68 POINT ACTION UPDATE SCREEN 2-73
November 2003 v Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 2-69 POINT ACTION UPDATE SCREEN FOR
CONSENT DECREE/ADMINISTRATIVE ORDER PATHWAY 2-74
FIGURE 2-70 POINT ACTION UPDATE SCREEN FOR
ADMINISTRATIVE PENALTY PATHWAY 2-75
FIGURE 2-71 POINT ACTION UPDATE SCREEN FOR VIOLATION PATHWAY 2-76
FIGURE 2-72 POINT COMMENT KEY DATA SCREEN 2-77
FIGURE 2-73 POINT COMMENT UPDATE SCREEN 2-78
FIGURE 2-76 AFS SEGMENT LEVEL UPDATE MENU 2-79
FIGURE 2-77 SEGMENT GENERAL KEY DATA SCREEN 2-80
FIGURE 2-78 SEGMENT GENERAL UPDATE SCREEN 2-81
FIGURE 2-79 PAGE - SEGMENT GENERAL UPDATE SCREEN 2-82
FIGURE 2-80 SEGMENT POLLUTANT KEY DATA SCREEN 2-83
FIGURE 2-81 SEGMENT POLLUTANT UPDATE SCREEN 2-84
FIGURE 2-82 2ND PAGE - SEGMENT POLLUTANT UPDATE SCREEN 2-85
FIGURE 2-83 SEGMENT CHEMICAL KEY DATA SCREEN 2-86
FIGURE 2-84 SEGMENT CHEMICAL UPDATE SCREEN 2-87
FIGURE 2-85 SEGMENT PROJECTED POLLUTANT KEY DATA SCREEN 2-88
FIGURE 2-86 SEGMENT PROJECTED POLLUTANT UPDATE SCREEN 2-89
FIGURE 2-87 2ND PAGE - SEGMENT PROJECTED POLLUTANT UPDATE SCREEN 2-90
FIGURE 2-88 SEGMENT COMMENTS KEY DATA SCREEN 2-91
FIGURE 2-89 SEGMENT COMMENT UPDATE SCREEN FOR 'E1 AND 'C1 COMMENTS 2-92
FIGURE 2-89.1 SEGMENT COMMENT UPDATE SCREEN FOR 'P1 COMMENTS 2-93
Figure 3-1 AFS BATCH TRANSACTION HIERARCHY 3-4
Figure 3-2 COMPARE SUBMITTAL SCREEN 3-13
Figure 3-3 COMPARE SUBMITTAL JCL PARAMETERS SCREEN 3-15
Figure 3-4 AFS COMPARISON AUDIT REPORT 3-18
Figure 3-5 AFS BEFORE - AFTER COMPARISON REPORT - NON PERMIT TRANSACTIONS 3-19
Figure 3-6 AFS BEFORE - AFTER COMPARISON REPORT - PERMIT TRANSACTIONS 3-20
Figure 3-7 AFS COMPARE TRANSACTION STATUS REPORT - NON PERMIT TRANSACTIONS
3-21
Figure 3-8 AFS COMPARE TRANSACTION STATUS REPORT - PERMIT TRANSACTIONS 3-22
Figure 3-9 AFX COMPARISON AUDIT REPORT 3-23
Figure 3-10 AFX BEFORE - AFTER COMPARISON REPORT 3-24
Figure 3-11 AFX COMPARE TRANSACTION STATUS REPORT 3-25
Figure 3-12 AFS MAIN MENU 3-31
Figure 3-13 AFS MAIN MENU 3-32
Figure 3-14 AFS UPDATE MENU 3-33
Figure 3-15 AFS BATCH UPDATE MENU 3-34
Figure 3-16 AFS BATCH EDIT SCREEN 3-35
Figure 3-17 EDIT SUBMITTAL (YEAR OF RECORD) SCREEN 3-39
Figure 3-18 BATCH SUBMITTAL (JCL Parameters) SCREEN 3-40
Figure 3-19 BATCH SUBMITTAL (Confirmation) SCREEN 3-43
Figure 3-20 EDIT ERROR REPORT 3-45
Figure 3-21 EDIT SUMMARY REPORT 3-46
Figure 3-22 UPDATE SUBMITTAL SCREEN 3-47
Figure 3-23 UPDATE SUBMITTAL (YEAR OF RECORD) SCREEN 3-50
Figure 3-24 NOTIFICATION SCREEN 3-53
Figure 3-25 TRANSACTION SUMMARY SCREEN 3-56
Figure 3-26 ERROR SUMMARY SCREEN 3-57
Figure 3-27 AFS MAIN MENU 3-58
Figure 3-28 UTILITY SELECTION MENU 3-59
Figure 3-29 UTILITY FILE NAME (User-specified Option) SCREEN 3-61
November 2003 vi Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
Figure 3-30 UTILITY FILE NAME (System Default Option) SCREEN 3-62
Figure 3-31 TSO LOGON MENU 3-70
Figure 3-32 ISPF LOGON MENU 3-71
Figure 3-33 ISPF PRIMARY OPTION MENU 3-72
Figure 3-34 EPA / NCC OPTION MENU 3-73
Figure 3-35 RACF INFORMATION SCREEN 3-74
Figure 3-36 RACF - SERVICES OPTION MENU 3-75
Figure 3-37 RACF - DATA SET PROFILE SERVICES SCREEN 3-76
Figure 3-38 RACF - DATA SET PROFILE SERVICES - ADD SCREEN 3-77
Figure 3-39 RACF - ADD DATA SET PROFILE (Optional Information) SCREEN 3-78
Figure 3-40 RACF - ADD DATA SET PROFILE (ACCESS LIST) SCREEN 3-79
Figure 3-41 RACF - MAINTAIN DATA SET ACCESS LIST SCREEN 3-80
Figure 3-42 RACF - MAINTAIN DATA SET ACCESS LIST-ADD SCREEN 3-81
Figure 3-43 RACF - MAINTAIN DATA SET ACCESS LIST-ADD SCREEN 3-82
Figure 3-44 RACF - DATA SET PROFILE SERVICES SCREEN (Confirmation) 3-83
FIGURE 4-1 AFS MAIN MENU SCREEN 4-1
FIGURE 4-2 AFS UTILITY MENU SCREEN 4-2
FIGURE 4-3 UTILITY MERGE PLANTS SCREEN 4-4
FIGURE 4-4 UTILITY MERGE POINTS SCREEN 4-8
FIGURE 4-5 UTILITY UNMERGE PLANT SCREEN 4-11
FIGURE 4-6 UTILITY DELETE MENU SCREEN 4-14
FIGURE 4-7 PLANT LEVEL DELETE SCREEN 4-16
FIGURE 4-8 DELETE ENTIRE PLANT CONFIRMATION SCREEN 4-17
FIGURE 4-9 STACK LEVEL DELETE SCREEN 4-19
FIGURE 4-10 POINT LEVEL DELETE SCREEN 4-21
FIGURE 4-11 SEGMENT LEVEL DELETE SCREEN 4-23
FIGURE 4-12 SIP INVENTORY DELETE SCREEN 4-25
FIGURE 4-13 ASBESTOS CONTRACTOR DELETE SCREEN 4-27
FIGURE 4-14 ASBESTOS LANDFILL DELETE SCREEN 4-28
FIGURE 4-15 PERMIT ADMINISTRATION DELETE MENU 4-29
FIGURE 4-16 APPLICATION DELETE SCREEN 4-30
FIGURE 4-17 ASSOCIATION DELETE SCREEN 4-31
FIGURE 4-18 DELETE PERMIT SCREEN 4-32
FIGURE 4-19 UNDELETE MENU SCREEN 4-34
FIGURE 4-20 CANCEL UNPROCESSED DELETES SCREEN 4-35
FIGURE 4-21 CANCEL DELETION INFORMATION SCREEN 4-36
FIGURE 4-22 COMPLIANCE HISTORY SCREEN 4-37
FIGURE 4-23 SOURCE/POINT SWAP SCREEN 4-39
FIGURE 4-24 ARCHIVE SCREEN 4-43
FIGURE 4-25 DEARCHIVE SCREEN 4-45
FIGURE 4-26 USER JCL PARAMETERS SCREEN 4-46
FIGURE 4-27 TABLE FILE LOOKUP MENU 4-48
FIGURE 4-28 Page 1 - ACTION OPTION of TABLE FILE LOOKUP 4-49
FIGURE 4-29 Page 2 - ACTION OPTION of TABLE FILE LOOKUP 4-50
FIGURE 4-30 Page 3 - ACTION OPTION of TABLE FILE LOOKUP 4-51
FIGURE 4-31 BROWSING ACTION TABLE 4-52
FIGURE 4-32 LISTING ACTION TABLE 4-53
FIGURE 4-33 SIP INVENTORY SELECTION MENU 4-54
FIGURE 4-34 SIP INVENTORY KEY DATA SCREEN 4-55
FIGURE 4-35 SIP INVENTORY DATA SCREEN 4-56
FIGURE 4-36 UPDATE AFS PLANT ID SCREEN 4-57
November 2003 vii Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
LIST OF CHARTS
Chart 3-1 Batch Edit/Update Screen Flow 3-29
Chart 3-2 Utility Transaction Screen Flow 3-30
November 2003 viii Table of Contents
-------
AFS User's Guide
AF3 AFS Data Storage
1.0 Introduction
This volume describes the use of the AFS Facility System (AFS) for the storage and modification
of compliance, emissions and operating permit data. AFS is a computer-based system for
handling the storage and retrieval of information about emissions and compliance data of
individual facilities, area and mobile source data, and ambient air quality monitoring data. AFS is
the system managing facility data. It is administered by the U. S. Environmental Protection
Agency, Office of Enforcement and Compliance Assurance, Enforcement Planning, Targeting and
Data Division, located in Washington DC. AFS is installed on the IBM computer system at EPA's
National Computer Center in Research Triangle Park, North Carolina. AFS employs the ADABAS
database management system to manage its data files and the CICS teleprocessing monitor to
provide the interface between users and programs.
1.1 The Purpose of AFS
The purpose of this volume is to describe the operation of AFS relating to the entry and
modification of data.
1.2 The Organization of AFS
In addition to this introductory section, this volume contains the following sections describing the
methods of data entry and modification of data relating to the AFS:
Section 2.0: On-Line Updating
Section 3.0: Batch Updating
Section 4.0: Utilities
April 2003
1-1 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.3 AFS Data Storage Overview
1.3.1 AFS System
There are 3 related systems:
Geographic, Common, and Maintenance Subsystem (Geo-Common) (GCS)
Air Quality Subsystem (AQS)
Area and Mobile Source Subsystem (AMS)
Figure 1-1 illustrates the relationships among the AFS system and identifies the relevant volumes
of the User's Guide.
The Geo-Common Subsystem consists mostly of reference data used by the other subsystems,
such as Federal Information Processing Standard (FIPS) state codes and pollutants. It is maintained
by the AFS database administrator. Users can browse and generate reports of Geo-Common data
but cannot alter its data.
The Air Quality Subsystem (AQS) manages ambient air pollution measurement data collected at
thousands of monitoring stations in the United States, its possessions, and trust territories. The Air
Quality data include descriptions of air monitoring sites and monitoring equipment, measured
concentrations of air pollutants and related parameters, and calculated summary and statistical
information.
The Area and Mobile Source Subsystem (AMS) contains emission inventories for sources of area
and mobile air pollution for the United States, its possessions, and trust territories.
The AFS Facility System (AFS) contains emission inventory and regulatory compliance data
collected at individual facilities in the United States, its possessions, and trust territories. The data
include general information about the emitting site, such as location and type, compliance activity
and the emissions levels of pollutants.
AFS data are updated interactively through on-line access or batch updating. This volume explains
how to update AFS data using On-line Updating, Batch Updating and Utilities.
April 2003
1-2 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
AA1
Introduction
Air Quality Subsystem
AQ1: Data Dictionary
AQ2: Coding of Data
AQ3: Data Storage
AQ4: Data Retrieval
AQ5: Ad Hoc Retrieval
Geographic, Common,
and Maintenance
(Geo-Common)
Subsystem
GC1: Data Dictionary
GC2: Codes and Values
GC3: Data Storage
GC4: Data Retrieval
Air Facility
System
Aerometric Mobile and
Source Subsystem
AM1: Data Dictionary
AM2: Coding of Data
AM3: Data Storage
AM4: Data Retrieval
AF1
Data Dictionary
AF2
Coding of Data
AFS
Data
Storage
AF4
Data
Retrieval
AF5
Ad Hoc
and
Milestone
Reporting
FIGURE 1-1 AFS SYSTEM AND RELEVANT USER'S GUIDE VOLUMES
April 2003
1-3
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.4 AFS User Support
A toll-free HELPLINE is provided for user support. Users that may be experiencing problems with
AFS or may simply have a question concerning the operation of AFS may contact the HELPLINE at
1-800-367-1044.
1.5 AFS Logon Procedures
This section explains how to begin an AFS terminal session. To use AFS you need the equivalent
of an IBM 3270 Model 2 Terminal connected to the NCC-IBM computer system through the EPA
telecommunications network. The optimal configuration is a 3270-type terminal or a personal
computer with a 3270-type emulation card and a high speed communications line. An alternative
is the National Computer Center's protocol converter, called the "TCP", which provides 3270
emulation for many brands of asynchronous terminals. The minimum acceptable
telecommunications speed is 1200 bps. Higher speeds of 2400 bps or 9600 bps are preferable.
Section 1.5.1 TCP Logon provides step by step instructions for AFS access for the "TCP" protocol
converter. Section 1.5.2 provides step by step AFS access instructions for the IBM Mainframe
(CICS) Logon.
1.5.1 TCP Logon
The following instructions are for using the protocol converter, or "TCP", to simulate a 3270-type
terminal. If you are using a 3270-type terminal, skip this section and proceed to Section 1.5.2.
1. Prepare your equipment for use by turning on power, adjusting terminal settings,
executing your PC's communications program, or any other necessary preliminaries. If
you do not already know what communications parameter to use, contact the National
Computer Center for assistance at 1-800-334-2405.
2. Dial the appropriate phone number and establish connection with the EPA
telecommunications network. The phone number varies by location. Contact the National
Computer Center at 1-800-334-2405 for the phone number or any other assistance needed
with this step.
3. Once the connection has been made, press the key once or twice until the
message "Welcome to the Environmental Protection Agency National Computer Center..."
is displayed on your terminal. The complete text of the message is shown in Figure 1-2.
4. Type "TCP" to choose the 3270 emulation option and press the key. The
message "Connected" will appear on the screen (Figure 1-2).
April 2003
1-4 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
Welcome to the Environmental Protection Agency National Computer Center
Please enter one of the following selections:
IBMPSI for IBM
TCP for 3270 EMULATION
VAXA for VAX SYS A
VAXB for VAX SYS B
MAIL for ALL-IN-1
Enter selection: tcp
Connected.
FIGURE 1-2 TCP LOGON SCREEN (WHEN SIGN-ON CHARACTER IS KNOWN)
USER RESPONSES ARE UNDERLINED
5. If you know the "initial sign-on character of your terminal, type it three or four times at half-
second intervals until the TCP responds by clearing the screen and displaying a message.
Type only the sign-on character; do not press the key. Typical sign-on
characters are "m" for a DEC VT-100 terminal and "]" for a Televideo 950 terminal. Proceed
to Step 6.
If you do not know the "initial sign-on character" for your terminal, press the
key three or four times at half-second intervals until the TCP responds with the message
"»COMMTEX Cx-80 DATA EXCHANGE«" and follow the instructions displayed on the
screen. Figure 1-3 shows an example of this procedure.
April 2003
1-5
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
» COMMTEX Cx-80 DATA EXCHANGE »
ENTER YOUR TERMINAL'S CX-80 DEVICE TYPE IF YOU
ALREADY KNOW IT. IF NOT, TYPE 'H' FOR HELP.
?h
ENTER K IF USING A KEYBOARD/DISPLAY TERMINAL,
T IF USING A TELEPRINTER, OR
C IF USING A MICRO COMPUTER.
?k
PLEASE ENTER THE FIRST LETTER OF THE NAME OF THE COMPANY THAT
MANUFACTURES YOUR KEYBOARD/DISPLAY.
?d
ENTER Y FOR YES, N FOR NO. IS IT:
DATA GENERAL? n
DATAGRAPHIX?n
DATAMEDIA?n
DATAPOINT?n
IS IT A MODEL:
VT52?n
VT100 WITHOUT ADVANCED VIDEO OPTION? y
THE Cx-80'S DEVICE TYPE FOR THE VT100 WITHOUT ADVANCED VIDEO OPTION
IS THE NUMBER '20'. FOR FASTER SIGN-ONS, RESPOND WITH THIS NUMBER TO THE INITIAL Cx-80 DEVICE T'
PROMPT.
TYPE 'R' TO RESTART YOUR SIGN-ON, ANY OTHER KEY
FIGURE 1-3 TCP LOGON SESSION (WHEN SIGN-ON CHARACTER IS UNKNOWN)
USER RESPONSES ARE UNDERLINED.
April 2003
1-6
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
6. When Step 5 is completed, the TCP knows the kind of terminal you are using and
responds by displaying the message "** Cx-80 VER 04.83 ** ". The version number may
change as the TCP is updated. Don't do anything while this message is displayed; just
wait patiently. After a few seconds, you will see the "WELCOME" screen appear shown in
Figure 1-4. Your terminal is now effectively a 3270-type and procedures from this point on
are the same as for a 3270 terminal. Type "AFS" at the cursor and press the
key. The CICS Logon screen (Figure 1-5) will appear. Go to step 5 of Section 1.5.2 to
continue the logon process.
WELCOME TO THE
U.S. ENVIRONMENTAL PROTECTION AGENCY
TELECOMMUNICATIONS NETWORK
TERMINAL ID: T2410920
ENTER COMMAND TO LOGON
FIGURE 1-4 EPA WELCOME SCREEN
U.S. Environmental Protection Agency
PRODUCTION CICS logon
Date:
Time:
Enter USERID and PASSWORD and then press ENTER.
USERID ===>
PASSWORD ===> NEW PASSWORD ===>
Change other logon parameters (Y/N) ===> N Cancel (Y/N) ===> N
FIGURE 1-5 CICS LOGON SCREEN
April 2003
1-7
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
1.5.2 CICS Logon Procedures
This section explains how to gain access to the AFS system.
BEFORE LOGGING ONTO AFS, PLEASE NOTE:
If you are entering through the TCP, execute Steps 5 through 8.
If you are not entering through the TCP and this is the first time for you to log onto AFS, execute
Step 1 and Steps 4 through 8.
If you are not entering through the TCP and have previously established a connection to AFS,
execute Steps 1 through 4 and Steps 7 and 8.
On the EPA Menu System screen (Figure 1-6):
1. At the Command = = = > prompt, type "AIRS".
2. At the USERID = = = > prompt, type your three character User ID.
3. At the PASSWORD = = = > prompt, type the password that is associated with your User
ID.
4. Press the key.
Environmental Protection Agency
Menu System
Date: 09/08/92
Time: 13:15:48
Terminal: T060055
Logmode: S3278R2
Please enter selection or command and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
4. APPLICATIONS EPA Applications Menu
5. INTER-AGENCY Inter-Agency Applications Menu
6. PUBLIC Public Access Applications Menu
WARNING: The use of this computer is for official Government business only.
Unauthorized use of this computer is a criminal offense under Title 18
United States Code, Section 641, and may subject violators to a fine of
up to $10,000, or imprisonment of up to 10 years, or both.
Command ===> AIRS
Optional Quick Logon - USERID ===>
PASSWORD ===>
Fl/F13=Help F5/F17=Refresh F12/F24=Cancel
FIGURE 1-6 EPA MENU SYSTEM SCREEN
April 2003
1-8
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
On the CICS Logon screen (Figure 1-7):
5. At the USERID = = = > prompt, type your three character User ID.
6. At the PASSWORD = = = > prompt, type the password that is associated with your User
ID.
If you are a first time user or your password is due to expire (passwords expire every 90
days):
You will need to change your password. Enter the original or expiring
password at the PASSWORD prompt and a new password that you create
at the NEW PASSWORD prompt. After you press the key, the
system will ask you to verify the new password. Re-key your new
password at the NEW PASSWORD prompt and press the key.
Your new password must consist of at least six digits and not more than
eight digits. It must contain at least one alphanumeric character and one
numeric character.
U.S. Environmental Protection Agency
PRODUCTION CICS logon
Date: 09/08/92
Time: 14:32:21
Enter USERID and PASSWORD and then press ENTER.
USERID ===>
PASSWORD ===> NEW PASSWORD ===>
Change other logon parameters (Y/N) ===> N Cancel (Y/N) ==
Command ===>
Fl/F13=Help F3/F15=Exit
FIGURE 1-7 CICS LOGON SCREEN
April 2003
1-9
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
If you are a first time user: You will receive the EPA2 TSO/E LOGON screen (Figure 1-8) that
requests you to provide the system with accounting information. Enter the information and press
the key. If you do not know what data to provide for the prompts on the screen,
contact your Regional Office AFS contact.
If you are not a first time user and would like to change your accounting information or report
output information, enter a "Y" (yes) to the "change other logon parameters(Y/N = = = >)" prompt.
You will be presented with the EPA2 TSO/E LOGON screen (Figure 1-8).
ZZSNLNG U.S. Environmental Protection Agency
Production 330 CICS sign-on
Date: 10/10/94
Time: 08:30:36
Enter USERID and PASSWORD and then press ENTER.
USERID ===>
PASSWORD ===> NEW PASSWORD ===>
ACCT ID ===>
FIMAS ===>
GROUP IDENT ===>
INITIAL TRANS =>
BIN NUMBER ===>
PRINT DEST ===>
NOTIFY MSGS ===>
Command ===>
Fl/F13=Help F3/F15=Exit
FIGURE 1-8 EPA2 TSO/E LOGON SCREEN
April 2003
1-10
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
On the AIRS Main Menu screen (Figure 1-9):
7. Enter "2" for Facility (AFS) at the PLEASE ENTER SELECTION prompt.
8. Press the key.
06/14/94
PF3=end
Aerometric Information Retrieval System
Main Menu
1. Air Quality (AQS)
2. Facility (AFS)
3. Area Mobile Source (AMS)
4. Geographic/Common (GCS)
5. AIRS Graphics (AG)
Please Enter Selection: 2
PF5=terminate
FIGURE 1-9 AFS MAIN MENU SCREEN
April 2003
1-11
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
The AFS Main Menu (Figure 1-10) will appear. Instructions on using the UPDATE THE
DATABASE feature are found in Section 2 of this manual. Instructions on using the SELECT A
UTILITY feature are found in Section 4 of this manual.
09/08/92
AIRS FACILITY SUBSYSTEM
MAIN MENU
PGM: AFPOOO
MAP: AFM0001
1 UPDATE THE DATABASE
2 BROWSE THE DATABASE
3 SELECT A REPORT
4 SELECT A UTILITY
ENTER MENU SELECTION:
NEED ASSISTANCE? CALL THE AFS HELPLINE AT 1-800-367-1044
PF3=END PF4=SUBSYSTEM MENU PF5=TERMINATE
FIGURE 1-10 AFS MAIN MENU SCREEN
April 2003
1-12
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
1.6 AFS Logoff Procedures
The AFS logoff procedures are explained for both CICS (Section 1.6.1) and TCP (Section 1.6.2). If
you are a TCP user, you must execute a CICS logoff prior to disconnecting from TCP.
1.6.1 CICS Logoff
When you are ready to end your AFS session, press the key to terminate the AFS system.
You will receive the EPA CICS Menu System screen shown in Figure 1-11. Type "4" at the
Command prompt to exit. You will receive the EPA Menu System screen (Figure 1-12). You have
effectively disconnected your CICS connection.
U.S. Environmental Protection Agency
Production CICS Menu System
XX XX XXXXXX XXXXXX XX XXXXXX XXXXX
XXX XX XXXXXXXX XXXXXXXX XX XXXXXXXX XXXXX
XXXX XX XXX XXX XX XXX XXX
XX XX XX XXX XXX XX XXX XXX
XX XX XX XXX XXX XX XXX XXX
XX XXXX XXX XXX XX XXX XXX
XX XXX XXXXXXXX XXXXXXXX XX XXXXXXXX XXXXX
XX XX XXXXXX XXXXXX XX XXXXXX XXXXX
Please enter selection or command and then press ENTER.
Date: 09/08/92
Time: 14:31:45
Terminal: T060055
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
XXXXXX
XXXXXX
XXXXXXXX
XXX
XXX
XXX
XXX
XXXXXXXX
XXXXXX
1. INFORMATION News Alerts and User Memos
2. SIGN-ON Change CICS Sign-on Parameters
3. APPLICATIONS EPA Applications Menu for CICS
4. EXIT Exit CICS and return to EPA Menu System
Command = = = > 4
Fl/F13=Help F3/F15=Exit F10/F22=Lock
F12/F24=CICS
FIGURE 1-11 EPA CICS MENU SYSTEM SCREEN
April 2003
1-13
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
Environmental Protection Agency
Menu System
Date: 09/08/92
Time: 13:15:48
Terminal: T060055
Logmode: S3278R2
Please enter selection or command and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
4 . APPLICATIONS EPA Applications Menu
5. INTER-AGENCY Inter-Agency Applications Menu
6. PUBLIC Public Access Applications Menu
WARNING: The use of this computer is for official Government business only.
Unauthorized use of this computer is a criminal offense under Title 18
United States Code, Section 641, and may subject violators to a fine of
up to $10,000, or imprisonment of up to 10 years, or both.
Command ===>
Optional Quick Logon - USERID ===>
PASSWORD ===>
FIGURE 1-12 EPA MENU SYSTEM SCREEN
1.6.2 TCP Disconnect
If you are using the TCP (protocol converter) to simulate a 3270-type terminal, you should
disconnect from the protocol converter when you have ended your CICS session which is
explained in Section 1.6.1.
The TCP has a limited number of ports, when you disconnect your terminal, the port you have
been using becomes available to other users. To disconnect from the TCP, hold down the
CONTROL key and press the Y key. The TCP clears the screen and displays the message "*Cx-80
DISCONNECT*", and disconnects from the telecommunications line.
April 2003
1-14
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
1.7 Function keys
In the AFS, several standard functions are controlled through the use of PF (program function)
keys and special keys. The following descriptions apply to 3270-type terminals. Users employing
the "TCP" protocol should contact NCC for information if not familiar with the comparable keys on
a terminal, or if an attempt to use a PF key causes it to perform improperly. REMEMBER, IF YOU
USE A PF KEY WHILE UPDATING DATA IN AFS, UNLESS YOU'VE "ENTERED" THE RECORD,
THE DATA ON THE SCREEN WHEN YOU EXIT VIA THE PF COMMAND WILL NOT BE
ADDED TO THE DATABASE. The only exception to this rule is the PF key for repetitive data
entry (PF9). To "enter" data, press the key until you view a menu screen rather than a
data screen.
All AFS screens employ function keys to assist users in the operation of the screens. Similarly,
logging off of AFS is performed with the use of PF keys.
Depending on the screen, different function keys operations are available. Function key definitions
for AFS update and browse screens are as follows:
PF1 = HELP
PF3=END
PF4=MAIN
PF5=TERM
PF6=PGUP
PF7 = PREV
PF8=NEXT
PF9=DUPL
PF10=SCRN
PF12=UPDT/BRWS
The PF1 key displays descriptive information about the current
screen.
The PF3 key terminates the current function and returns you to
the previous key input screen or preceding menu option screen.
The PF4 key terminates the current function and returns you to
the AFS Main Menu. If you are already at the AFS Main Menu,
the PF4 key returns you to the AIRS Main Menu.
The PF5 key terminates your AFS session and returns you to the
Production CICS screen.
The PF6 key returns you to the previous page of a multiple page
screen.
The PF7 key returns you to the preceding sequential record.
The PF8 key forwards you to the next sequential record.
The PF9 key is used for repetitive data entry.
The PF10 key moves the cursor to the SCREEN field on the
screen.
The PF12 key toggles you between browse and update.
April 2003
1-15
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.7.1 Other Special Keys
Four other special keys on a 3270-type keyboard are important for AFS.
The ENTER key causes the information on the screen to be passed to the AFS program for
processing. After processing the information, the program may re-display the same screen or a
different screen. In essence, the ENTER key tells a program to process the current screen and then
do the next thing in logical sequence.
The TAB and TAB keys are used to move the cursor through the fields displayed on the
screen. Pressing the TAB key will move the cursor to the next entry field and TAB will
move the cursor to the previous field. If the end of the fields is reached pressing TAB will move
the cursor to the first field and if the cursor is at the first field pressing TAB will move
the cursor to the last field.
The RESET key is used when keyboard entry processing has been disrupted. Data entry is
prohibited until the keyboard is reset. Symbols and keyboard keys vary by computer
configuration. A common symbol indicating that Reset is required is ? + . Common keys used to
perform the Reset function are: the Reset Key; PF10 and Alt 0. Contact your resident computer
expert for the Reset key(s) specific to your computer installation.
April 2003
1-16 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.8 AFS Security
1.8.1 AFS Security Profile
In order to access AFS, users must have an NCC account and ID, and also have their ID registered
with NATURAL security. In addition to NATURAL security, AFS requires a security profile for users
updating AFS data base information (Figure 1-13). Users may retrieve public data without a user
profile. The security profile specifies the type of authorization a user has for updating or retrieving
(reading) data. It is the responsibility of the AFS Data Base Administer to register each user under
NATURAL security and establish a User's security profile.
Included in each security profile are the following data:
NCC IBM User ID
User Classification: identifies EPA National, Regional, State agency, County agency or
general public affiliation
Compliance Read Access: identifies the compliance data you may read
Compliance Update Access: identifies the compliance data you may update
Emissions Read Access: identifies the emissions data you may read
Emissions Update Access: identifies the emissions data you may update
SIP Inventory Read Access: identifies the SIP inventory data you may read
SIP Inventory Update Access: identifies the SIP Inventory data you may update
1.8.2 Access Levels
Every AFS User will be assigned separate read and update security levels for compliance,
emissions, and SIP data. The security levels for read access are:
0 - Read access for non-sensitive data
1 - Read access for both non-sensitive and sensitive information
The security levels for update access are:
0 - No update access
1 - Update access to only non-sensitive information
2 - Update access to both non-sensitive and sensitive information
April 2003
1-17 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
AFS users will be classified by the security profiling system as members of Headquarters EPA,
Regional EPA, State agency, County/local agency, or general public. In addition to the
classification type, the geographic area for which the user is responsible will also be included in
the profile, as well as the designation of the user as compliance, emissions, SIP, or a combined
data user.
Certain data elements within the database may only be updated by users possessing a particular
user security profile. Users identified as EPA personnel (Regional and Headquarters) will be given
sole update access, in their geographic areas, to the following data elements:
Data Element Where Found
EPA Pollutant Classification Plant Pollutant Air Programs
EPA Pollutant Compliance Status Plant Pollutant Air Programs
EPA Attainment/Non-Attainment Indicator Plant Pollutant Air Programs
EPA Compliance Status Point Air Programs
Headquarters EPA personnel will be given sole update access to the following data element:
Data Element Where Found
Priority Code Plant General
The definition and attributes of these data elements are contained in AFS USERS GUIDE - AF1
(AFS Data Dictionary).
1.8.3 Data Ownership
Each data element in AFS has an ownership designation of emissions, compliance, SIP or
commonly owned by multiple communities of users. Consequently, user data update capability is
determined by comparing the security profile of the user - such as compliance, emission, or both -
to the ownership of the data element. Only those users specified as owners of a data element may
update that element. Update for a specific piece of data is available to all users with the
appropriate security profile. Certain emissions data elements will require additional SIP access
when the facility is included in a SIP Inventory.
April 2003
1-18 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 1-13 AFS SECURITY PROFILE FORM
April 2003
1-19 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.8.4 Sensitive Data
Sensitive data are particular elements within a facility that have restricted access. Disclosure of
this information to the public could hinder enforcement activities and/or reveal facility equipment
design and operation secrets. Sensitive information is available only to authorized personnel.
Access authorization to this data is contained in the User profile, and controlled by the AFS
security system. Section 1.8.2 states how sensitive and non-sensitive data access are determined.
The terms "Enforcement Sensitive" and "State Sensitive" are used to further classify the sensitive
data elements. The security access requirements are the same for all sensitive data elements.
The following compliance data elements are always defined as sensitive in AFS. A user cannot
designate these data elements non-sensitive. Users must have compliance read sensitive access
to retrieve these data elements and compliance update sensitive access to add, change or delete
these data elements.
Data Element Where Found
Facility Capacity Plant General
Facility Capacity Units Plant General
Prospective actions and Plant/Point Action
associated comments Comments
Enforcement Actions involving Civil Referrals and Plant/Point Action
associated comments Comments
Even Inspection Frequency Plant Air Programs
Even Inspection Strategy Plant Air Programs
Even Year of Inspection Frequency Plant Air Programs
Odd Inspection Frequency Plant Air Programs
Odd Inspection Strategy Plant Air Programs
Odd Year of Inspection Frequency Plant Air Programs
Compliance users with update sensitive access may designate all other compliance comments, not
referenced above, enforcement sensitive by placing a "Y" in the Enforcement Sensitive Indicator on
the comment record. Compliance read sensitive access is required to retrieve enforcement
sensitive comments. Sensitive access is not needed to retrieve comments that have an
Enforcement Sensitive Indicator value of "N" or blank.
Certain compliance data elements may be designated as state sensitive by a user with update
sensitive access. The sensitive status is determined by the value of State Sensitive Indicator
located on the Point General record.
Some action types associated with certification received (State or Federal) have been flagged as
non-enforcement sensitive on the AFS Action Table, regardless of the date scheduled associated
with the action.
Users with compliance update sensitive access may designate the following compliance data
elements on Point General to be state sensitive by placing a "Y" in the State Sensitive Indicator
data element available on the record. Compliance read sensitive access is required to retrieve
these data elements when they are designated state sensitive. A value of "N" or blank in the State
Sensitive Indicator signifies that these data elements are not sensitive.
1-20
-------
AFS User's Guide
AF3 AFS Data Storage
November 2003
Introduction
April 2003
1-21 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
The following compliance data elements can be designated state sensitive on Point General:
Design Capacity (for unmerged compliance points) Point General
Design Capacity Units (for unmerged compliance pointlibint General
Certain emissions data elements may be designated as state sensitive by a user with update
sensitive access. The sensitive status is determined by the value of State Sensitive Indicators
located on the Point General and Segment General records.
Users with emissions update sensitive access may designate the following emissions data
elements on Point General and/or Segment General to be state sensitive by placing a "Y" in the
State Sensitive Indicator data element available on each record. Emissions read sensitive access
is required to retrieve these data elements when they are designated state sensitive. A value of "N"
or blank in the State Sensitive Indicator signifies that these data elements are not state sensitive.
The following emissions data elements can be designated state sensitive on Point General:
Design Capacity
Design Capacity Units
Space Heat (Percent)
The following emissions data elements can be designated state sensitive on Segment General:
Annual Estimated Emissions Method Code (on the Segment Pollutant Record)
Annual Fuel Process Rate
Maximum Operation Rate per Hour
* - Peak CO Season Daily Process Rate
* - Peak Ozone Season Daily Process Rate
* Additional SIP Update Sensitive access is required to update these data elements when
they are being reported for a SIP inventory.
For merged points, the Point General State Sensitive Indicator from the emissions point will take
precedence in the designation of state sensitive information. So, compliance point Design
Capacity designated as state sensitive would no longer be state sensitive if the compliance point
was merged with an emission point where the emission point state sensitive indicator was "N" or
blank.
The definition and attributes of these data elements are contained in AFS USERS GUIDE - AF1
(AFS Data Dictionary).
April 2003
1-22 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.8.5 State and Federal Private Data
State Private
Authorized State and County users of AFS may define as State-Private applicable plants and
associated records. Examples of these include non-federally reportable plants tracked by the State
solely in response to a State regulatory program. For federally reportable plants, the data
associated with the following record types may be defined as State-Private:
Pollutant: plant, stack, point and segment levels unless the pollutant is nationally
reportable. These pollutants are: CO, S02, N02, VOC, PT and PB.
Chemical
Fee certification
Action: plant and point levels for those actions with an action type that does not
correspond to a valid Regional Action Type.
Comment: Plant, stack, point and segment levels if the comment is not associated with an
action that has a valid Regional Action Type.
Only users with security profiles identifying them as State or County personnel can create, update
or retrieve State-Private records for their State or County.
Federal Private
Only users with security profiles identifying them as Regional or National personnel can update or
retrieve Federal Private records for their region or the country respectively.
Certain administrative penalty action types are defined on the AFS Action Table to be Federal
Private. These action types are also defined to be confidential. All comments associated with
actions of these types are automatically Federal Private.
Authorized users may make any plant or point comment Federal Private by entering an "F" in the
Private Indicator field.
April 2003
1-23 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.9 Update Techniques
AFS offers updating in two modes: on-line and batch.
In the on-line mode, users apply additions or changes to data directly onto the database in a real-
time fashion via update screens. Upon successful completion of an on-line update screen, the
information is immediately added or changed on the AFS database. Deleting or blanking out of an
individual data element can also be achieved through the use of on-line screens. However, if an
entire record needs to be deleted, the user must use the Delete function on the AFS Utility menu.
The users request for the deletion will be processed as a batch transaction and data will not be
deleted until the AFS nightly update. Section 2.0 of this manual is devoted to On-line updating of
AFS.
In batch updating, AFS data are formatted into 80-character transactions. The user then submits
these transactions for processing via the AFS Utility Menu. The transactions are processed during
the night. AFS is updated nightly with any batch transactions which have been submitted during
that days activity. It is important to remember that batch updating doesn't impact the database
until the time of the nightly AFS update. Adding, changing and deleting of AFS data can all be
performed using the batch method of updating AFS data. Section 3.0 of this manual is devoted to
batch updating of AFS.
1.9.1 Online Update - Repetitive Data Entry
Purpose: Users wanted to ADD AFS consecutive online transactions in a repetitive fashion in
order to circumvent the retyping of data that is common to all records being added.
In order to perform a REPEAT function, the user is required to either input the initial values on the
data screen for the first add or use the values previously stored on an existing record for the new
one. Then, if he wants to update another record, he presses PF9. The user then replaces only
those values he needs to change and again either presses enter to update the database or the PF9
key to update the database and retrieve the data back for the next update.
What can and cannot be repeated: In most cases, the PF9 key can be repeatedly invoked to add
several new records consecutively. However, the repeat key can only be invoked once for adding
record types which require the addition of more than one record type to be complete.
1) The addition of an air program necessitates the need for an 'add' of a air program
pollutant. The system 'automatically' takes the user from the air program data
screen to the air program pollutant screen upon hitting ENTER. Therefore, the
PF9 key will not be present or operational on the new air program's input screen,
because the air program's pollutant has not been entered yet. If the user presses
PF9 by mistake, he will receive a message saying 'requested function key not
allocated'.
2) The addition of an emissions point will automatically require the addition of a
segment general record. The repeat will not be available on the new point's input
screen because the segment information has not been entered yet.
3) A repeat key will not be allowed on the addition of the plant general, mailing or
fee information because there can not be multiple records of this type. In
April 2003
1-24 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
addition, for compliance plants, an air program and an air program pollutant
record are required for a compliance plant, entailing the situation outlined in item
1 above.
4) If there are multiple data screens, the Repeat function will exist on the last of the
series of screens. If the user presses PF9 prior to the last screen, he will receive a
message saying 'requested function key not allocated'.
Some fields must be blanked out during the duplication of the existing records, values will be
BLANKED OUT for the following conditions:
1) The update screens displayed for the new record are different than for the original
occurrence of the record. For example, if compliance point 001 is used as a
template for emissions point 002, the compliance-only fields must be blanked out
before the emissions point is generated.
2) The user's security profile does not allow update to data elements which are filled
in on the initial record. The user cannot be allowed to store information which he
is not allowed to enter himself.
3) Emissions were generated and stored on the original record. For example, if the
user is entering a new stack pollutant, the new pollutant should not have
estimated emissions filled in. The bubbled up estimated emissions for the original
record will not be valid for the new stack pollutant. The correct emissions value
for the stack will be bubbled up for the new pollutant.
4) The emissions were generated for the record by method code '8' or '9'. For
example, if segment pollutant 001e/01/CO has a method code of '8' for estimated
emissions and the pollutant is used as a template for segment pollutant
002e/02/CO, the emissions must be recalculated. The emissions factors used for
computing the estimated emissions for the original record do not apply to the new
segment pollutant record, and the value must be recalculated from the correct
source classification code/pollutant combination.
5) Compliance information is bubbled up and stored. For example, when general
point information for point 001 c, the last inspection date and type must be
blanked out. The inspection date and type reflect the values attached to point 001
c and not the new one being added.
6) The record being added contains fields with generated numbers. For example, if
at point general we have requested a 'repeat' on point 001 e and we are adding
emissions point 002e, we must blank out the internally stored highest segment,
comment and action number. If it is not blanked out, we would be allowing the
system to generate the next available segment number based on the previous
point's values.
7) Fields which are used in the generation/calculation of other fields. For instance, if
Point O01's detail data indicates that it's operating schedule is 24 hours a day, 7
days a wee, 365 days a year, and Point 002 is operating 24 hours a day, 7 days a
week, but only from December through February; the user must indicate that
seasonal change on the operating schedule. If this minor detail is overlooked, the
trend analysis for the emissions on that plant could be false. For Point General,the
April 2003
1-25 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
Percentage-Annual-Thruput-Group and the Normal-Operating-Group will be
blanked out upon a repeat. For Segment General, the Annual-Fuel-Process-Rate-
Units and Heat-Content will be blanked out upon a repeat.
NOTE: If the user chooses to create a new record from an existing record's information, the
existing record would have the appearance of being updated since it would carry the user id and
date stamp of the new record. This would happen although a true update did not occur for the
existing record.
1.10 AFS Data Relationships
To understand how AFS is organized, and to best utilize the variety of features the system has to
offer, it's important to first understand how the data in the system is arranged. To do this, you
need no experience with data base architecture or design.
A helpful analogy when considering the structure of AFS data is to think of a family tree. On a
chart of a family, parents are related to offspring, who in turn may produce offspring. Family trees
can be viewed at different levels of interest; the entire family, sides of the family, one group of
parents and children, a group of brothers and sisters, or individual family members.
AFS data is stored in logical groupings similar to the families that together make up a clan.
Generally, AFS data is maintained in one-to-many relationships, meaning one group of data can
have many related offspring. The basic linkage in AFS is between one plant and its associated
subparts. For example, one plant can have several point records in which pollutant and emission
data are maintained. These points may in turn be related to their own stacks or actions. In AFS,
therefore, one is associated to many, each of which in turn can be associated with many.
Knowledge of the database structure is necessary to ensure the correct data is updated. The data
on the AFS database are structured into four hierarchical levels:
PLANT The facility for which regulatory compliance or emissions data are
recorded
STACK The place within a facility where emissions enter the atmosphere, basically a
stack, vent or location of fugitive emissions
POINT A process location or tank within the facility at which pollutants are
produced
SEGMENT The components of a process, including physical and operating
parameters, that produces emissions
For each level, there exists many files, each containing a different type of data. These files
together form a comprehensive picture of an individual facility.
1.10.1 AFS System Files
The system files for each level in AFS and their corresponding Update and Browse screen
numbers are listed below to facilitate navigation through the AFS hierarchy. Refer to the AFS
Roadmaps in Figure 1-14 and Figure 1-15 to visualize these system files. The screen numbers are
also noted in the top of each file box in the roadmaps. Additional information pertaining to system
April 2003
1-26 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
navigation using screen numbers is located in section 1
Level Files
Plant Plant General
Plant Pollutants
Plant Air Programs
Plant Pollutant Air Programs
Plant Permit Application
Draft Permit General Information
Draft Permit Application Association
Permit Actions
Permit Comments
Permit Action Comments
Plant Mailing Label
Plant Actions
Plant Comments
Plant Asbestos Information
Plant High Priority Violator
Compliance Monitoring Strategy
.16 - Screen Feature.
Screen Number:
Update/Browse
300 / 500
301 / 501
302 / 502
303 / 503
350 / 550
351 / 551
360 / 553
353 / 554
364 / N/A
365 / N/A
305 / 506
306 / 507
307 / 508
042 / 052
314 / 514
315 / 516
Stack
Point
Segment
Stack General
Stack Pollutants
Stack Comments
Point General
Point Pollutants
Point Air Programs
Point Monitor
Point Continuous Emission
Point Tank
Point Actions
Point Comments
Segment General
Segment Pollutants
Segment Chemical
Segment Projected Pollutants
Segment Comments
320 / 520
321 / 521
322 / 522
330 / 530
331 / 531
332 / 532
333 / 533
334 / 534
335 / 535
336 / 536
337 / 537
340 / 540
341 / 541
342 / 542
344 / 544
343 / 543
April 2003
1-27
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 1-14 AFS UPDATE ROAD MAP
April 2003
1-28 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 1-15 AFS BROWSE ROAD MAP
April 2003
1-29 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.11 Key Data Screens and Detail Data Screens
When you are using the AFS system to enter or change data you will see two types of screens:
Key Data Screens and Detail Data Screens. Key data screens (also referred to as Identification
screens) are used to identify the record that you wish to operate on and detail data screens are
used to enter or modify data associated with a particular record. When you supply key data
information using the key data screen for a pre-existing record and press ENTER the appropriate
detail data screen will appear with the data values associated with the selected record. If the key
data you supplied does not match an existing record a fresh detail data screen will be presented to
add a new record.
If your intention was not to add a new record, press PF3 to specify different key data.
1.12 Mandatory Data
MANDATORY data are data records and elements designated by EPA as the minimum level of
information needed when maintaining an AFS record in support of a federal program. For
example, EPA requires all emissions inventory facilities tracked in AFS to possess at a minimum
plant name, address, standard industrial classification data and inventory year. AFS does not
require these data to track the record itself, as it does with key data, but the mandatory data are
required to support minimum EPA emissions inventory program standards. As with key data,
mandatory data elements must be provided by the user - either online through the use of update
screens, or in each batch transaction- or the record will not be successfully updated to the AFS
database.
Mandatory Records
There are minimum data requirements that require the submittal of more than one transaction
type/sequence set to successfully add records in AFS. These requirements apply to adding a
compliance facility, an air program, an emissions facility, an emissions point, an associated facility
and segment pollutant emissions. The transactions required for each are identified below.
The mandatory transaction type/sequences for adding a compliance facility are Plant General
(transaction type 10, sequence 1,2,3 and 4), an Air Program (transaction type 12) and an Air
Program Pollutant (transaction type 13). This combination identifies at least one pollutant being
tracked for each regulatory air program at the facility.
The mandatory transaction type for adding an air program (transaction type 12) is an air program
pollutant (transaction type 13).
The mandatory transaction type/sequences for adding an emissions facility are Plant General
(transaction type 10, sequence 1,2,3 and 6).
The mandatory transaction type/sequence for adding an emissions point (transaction type 30
sequence 3 or 4) is a segment general (transaction type 40, sequence 1). At least one Segment
General record must be added for each emissions Point General record. This combination
identifies at least one process or process component (segment) for a process location (emissions
point).
April 2003
1-30 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
You must supply both the compliance and emissions facility transactions when adding an
associated facility. To add an associated facility you must supply the compliance plant ID as the
base ID (columns 6-10) and the emissions plant ID in the associated plant ID (columns 56-60). Do
not enter an emissions year of record on the transaction or the Batch Submittal Utility screen. The
Year of Emissions Increment (columns 16-17) on the transaction type 10/sequence 6 will be used
to establish the Emissions Inventory Year of Record.
To ensure that an annual plant pollutant estimated emissions total can be determined based on
complete segment pollutant emissions information the following requirements are enforced for
adding segment pollutant information. Either Estimated Emissions Without Rule Effectiveness
(emission type ESTI) or Estimated Emissions With Rule Effectiveness (emission type ESTW) is
required. Which emission type is required is dependent on which emission types exist at the plant
level. If neither or both ESTI or ESTW exist at the plant level, either or both ESTI or ESTW may be
entered. If only ESTI exists at the plant level then ESTI is required. If only ESTW exists at the plant
level then ESTW is required. The required emission type on segment pollutant transaction
type/sequence 41/1 is submitted with an Update code of A (Add), a update code of C (change)
must be used for all other emission types for the same segment pollutant.
Mandatory Data Elements
As you enter data into the AFS screens, you will encounter fields that are required. This type of
data is called MANDATORY. You MUST supply values for these fields in order to continue.
Failure to do so will result in an error message stating the required field and the screen will be
presented again to the user for entry. Mandatory data items are preceded with an asterisk "*" on
the screens. Exceptions to this rule are identified in the list below.
Batch users must also provide these values for each batch transactions, or the transaction will be
rejected during the nightly batch processing cycle.
In addition to the federal reporting requirements, each state and local agency has its own set of
data reporting requirements. The federal reporting requirements are minimal. The following data
are mandatory in AFS when a record is supplied. This does not mean that each of these types of
data is required in AFS. For example, AFS does not require that a Stack General or Point Action
record be submitted to AFS. If AFS is the state or locals primary system it is likely that the
compliance and emission inventories will be more comprehensive to meet their own
requirements.
April 2003
1-31 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
FILE
SCREEN/TRANSACTION TYPE-
SEQUENCE
MANDATORY
DATA
Plant General
300
Pollutant Plant
Air Pgm Plant
Air Pgm Pollutant
301
302
303
Plant Mail
305
Action Plant
306
10-1
10-2
10-2 or 10-3
10-3 or 10-4
10-4
10-6
11-1
12-1
13-1
15-1
15-2
15-2
15-2
15-3
16-1
16-1
16-1
Plant Name
Plant Street Address
City Code or Plant City
Primary Industrial Class Code or
NAICS Code
Governmental Facility Code1
Year of Emission Inventory2
At least one complete set of
emissions (value decimal units
and method code if applicable)
Air Program Status
State Pollutant Compliance
Status *when the pollutant
entered is VOC, 'S02, 'PT1,
'PM10" or 'PM2.5 ' and the air
program is not '8' then the State
Pollutant Classification and State
Attainment-Non Attainment
Indicator are mandatory as well
Mailing Plant Name
Mailing Street Address
Mailing City Name
Mailing State
Mailing Zip Code
Air Program Code
Action Type
Date Scheduled or Date
Achieved
High Priority Violator
314
HPVFlag
HPV Effective Date
Stack General
Pollutant Stack
Point General
320
321 21-1
330
20-1
May 2008
Introduction
30-1
Stack Height and Stack Diameter
and/or Plume Height
At least one complete set of emissions
(value, decimal, units and method code
if applicable)
Point Description1
(See Footnote C)
1-32
-------
AFS User's Guide
AF3
AFS Data Storage
FILE
SCREEN/TRANSACTION TYPE-
SEQUENCE
MANDATORY
DATA
Pollutant Point
331
Air Program Point
Cont Emis Monitor
Con Emis EER
Action Point
Segment General
Pollutant Segment
Pollutant Chemical
Asbestos Contractor
Asbestos Landfill
332
333
334
336
340
341
344
308
309
31-1 or
31-2 or
31-3
32-1
32-1
33-1
34-1
34-1
36-1
36-1
36-1
40-1
41-1
43-1 or 43-2
50-1
50-2
50-3
50-3
50-3
51-1
51-2
51-3
51-3
51-3
At least one complete set of emissions
(value, decimal, units and method
code if applicable)
State Regulation Number1 or
Emission Limitation Description2
State Compliance Status
Air Program Status
Monitor Requirement Code
Air Program Code
Time Period Code
Air Program Code
Action Type
Date Scheduled or Date
Achieved
Source Classification Code
At least one complete set of
emissions (value, decimal, units
and method code if applicable)1.
At least one complete set of
emissions (value, decimal, units
and method code if applicable)
or Emission Limitation
Description
Contractor Name
Contractor Street Address
Contractor City
Contractor State
Contractor Zip Code
Landfill Name
Landfill Street Address
Landfill City
Landfill State
Landfill Zip Code
Either Estimated Emissions with or without rule effectiveness is required. The online and batch sections
provide the requirements.
April 2003
1-33
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
FILE SCREEN/TRANSACTION TYPE-
SEQUENCE
AFS Application 350 A1-1,2,3,4,5
A1- 1,2,3,4,5
A1- 1,2,3,4,5
A1- 1,2,3,4,5
A1-1
AFS General Info - 351 A2-1,2,3,4,5
Draft Permit A2-1,2,3,4,5
A2-1
A2-1
AFS Applic. Assoc. - 360 A7-1
Draft Permit A7-1
A7-1
MANDATORY DATA
Plant State Code
County Code
(AFS) Plant ID
Application
Application Category
Permit State Code
Permit
Permit Category
State Private Indicator
Plant State Code
County Code
Permit
AFS Permit Action
353 A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-1,2,3,4,5,6,7,8
A8-8
A8-2
Plant State Code
County Code (required for
permit actions that track
application completeness)
(AFS) Plant ID (required for
permit action that track
application completeness)
Application (required for permit
actions that track application
completeness)
Permit (required for permit
actions that track the review and
approval of a permit and for
permit actions that track events
for an issued permit)
Permit Action Type
Permit Action Number
EPA Agency Notified or Agency
State Notified or Agency State
Notified and Local Control
Region Notified
Permit Date Achieved or Permit
Date Scheduled
April 2003
1-34
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
FILE
AFS Plant Permit
Comment
AFS Permit Action
Comment
SCREEN/TRANSACTION TYPE-
SEQUENCE
364 89-1,2,3,4
89-1,2,3,4
A7-1
89-1,2,3,4
89-1,2,3,4
89-1,2,3,4
89-1,2,3,4
89-1
365 C1-1,2,3,4,5,6,7,8,9
C1-1,2,3,4,5,6,7,8,9
C1-1,2,3,4,5,6,7,8,9
C1-1,2,3,4,5,6,7,8,9
C1-1,2,3,4,5,6,7,8,9
MANDATORY DATA
Plant State Code
County Code (required for
comments for a plant specific
permit)
(AFS) Plant ID
(AFS) Plant ID (required for
comments for a plant specific
permit)
Permit
Permit Comment Number
Permit Comment
Owner Private
Plant State Code
County Code (required for
comments on permit actions
that track application
completeness)
(AFS) Plant ID (required for
comments on permit actions
that track application
completeness)
Application (required for
comments on permit actions
that track application
completeness)
Permit (required for comments
on permit actions that track the
review and approval of a permit
and for comments on permit
actions that track events for an
issued permit)
April 2003
1-35
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
FILE SCREEN/TRANSACTION TYPE- MANDATORY DATA
SEQUENCE
AFS Plant Permit 365 01-1,2,3,4,5,6,7,8,9 Permit Action Type
Comment 01-1,2,3,4,5,6,7,8,9 Permit Action Number
01-1,2,3,4,5,6,7,8,9 Permit Comment number
C1-1 Owner Private
A When adding a compliance facility (transaction type 10) air program (transaction type 12) and an
air program pollutant (transaction type 13) are also mandatory.
B When adding air program (transaction type 12), an air program pollutant (transaction type 13) is
also mandatory.
C When adding an emissions point (transaction type 30, sequence 3 or 4) a segment general
(transaction type 40) is mandatory.
Compliance
Emissions
April 2003
1-36 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.13 Non-modifiable data fields
The three types of non-modifiable fields in AFS are generated fields, sensitive fields and Frozen
SIP Inventory fields. In online mode, the cursor skips over non-modifiable fields.
AFS contains some fields which are not user input. They are generated by AFS and can not be
changed or deleted by the user. Several examples are EPA and State Plant Compliance Status,
Operating Status, Estimated Emissions at plant, stack and point levels, and Year of Emissions (on
all records except Plant General).
Sensitive data are not modifiable by users without update sensitive access. If the user has read
sensitive access, the data values will be displayed, otherwise the data values will be blank.
Another type of non-modifiable data is Draft SIP Inventory data. A number of fields become
"frozen" while the Inventory is undergoing review. Once approved by EPA Headquarters these
fields are permanently locked and any modifications to them must go through the ADBA.
1.14 On-line Help
As you navigate through the AFS screens entering data, you have access to an online Help feature
that can provide screen level help as well as individual field level help. Screen HELP provides a
descriptive purpose of the screen Field Help provides a definition of the field (data element) and
possible values where applicable. To activate screen HELP, press the PF1 key. To activate on-line
HELP for a particular field, type a question mark "?" in the first position of the field and press
ENTER. Do not enter spaces or any other value next to the "?". For some data elements you will
receive more extensive help which when presented prompts you to choose from a list of possible
data values. If you select a value and press ENTER you will be returned to the original screen with
the value entered into the appropriate field.
1.15 Error and Informational Messages
When you enter invalid data into a field or omit mandatory data elements an appropriate error or
informational message will be displayed in the upper left corner of the screen. In the case of one
or more data entry errors occurring simultaneously the cursor will be placed at the beginning of
the first erroneous data element.
1.16 Screen Feature
AFS is a menu driven system. In order to create or update a desired record, the user chooses a
selection from a menu. After you have become familiar with AFS you may often want to bypass
the menu system. The SCREEN feature provides a way to do this.
All AFS Data screens are identified with a screen number which can be found in the upper left-
hand corner of the screen. The Update screens use a "300" number series (Figure 1-14), while the
BROWSE screens use a "500" series number (Figure 1-15). If you wish to avoid the AFS menus,
you may direct yourself through a facility by identifying the screen numbers. SCREEN will be
displayed in the lower right hand corner of the screen. TAB to this field or use the PF10 key to
position the cursor and enter the number of the screen desired. After you press the ENTER key the
system takes over and will bring up the desired screen if it is both a valid screen and you are
April 2003
1-37 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
authorized to access the data elements on that screen.
If you are on an update data screen when you enter a screen number to go to, the current data
screen will be validated. All errors must be corrected and data updated prior to providing the
SCREEN specified.
You may switch between update and browse using the SCREEN feature. Upon entering browse
the first time you will be asked security questions pertaining to security sensitive data. Your
responses will remain in effect for the duration of your AFS session.
1.17 Aggregation of Emissions Values (Bubbling)
Aggregating emissions, often referred to as Bubbling, is the automatic summation of pollutant
emissions values to a higher level.
The automated aggregation process is performed for specific emission types:
ESTI - Estimated Emissions Without Rule Effectiveness
ESTW - Estimated Emissions With Rule Effectiveness
CODA - Peak CO Season Daily Emissions Without Rule Effectiveness
CODW - Peak CO Season Daily Emissions With Rule Effectiveness
03DA - Peak Ozone Season Daily Emissions Without Rule Effectiveness
03DW - Peak Ozone Season Daily Emissions With Rule Effectiveness
ACTU - Actual Uncontrolled
POTU - Potential Uncontrolled
POTC - Potential Controlled
Bubble Up activity is triggered when
a user enters or modifies segment pollutant emissions for the following emission
types: Estimated With/Without Rule Effectiveness, Peak CO Season Daily
With/Without Rule Effectiveness, Peak Ozone Season Daily With/Without Rule
Effectiveness, Potential Uncontrolled, Potential Controlled, or Actual Uncontrolled,
or
a user enters or modifies emissions for Potential Uncontrolled, Potential
Controlled, or Actual Uncontrolled at the point pollutant, or
a user requests a system generated calculation/recalculation of segment pollutant
emissions for the following emission types: Estimated With/Without Rule
Effectiveness, Peak CO Season Daily With/Without Rule Effectiveness, Peak Ozone
Season Daily With/Without Rule Effectiveness or Actual Uncontrolled emissions.
When Actual Uncontrolled emissions are entered at the plant pollutant, stack pollutant, point
pollutant, or segment pollutant a method code must also be entered. Valid values are '2' (user
calculated emission value) and '3' (user estimate because no emission data is available). The user
may request system generated Actual Uncontrolled emissions by entering a method code of '1'.
When a method code of '1' (system generated) is entered (at any level), the emission value with
units are not allowed to be entered because the system generates a value from the Estimated
Emissions Without Rule Effectiveness.
April 2003
1-38 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
When Potential Uncontrolled or Potential Controlled emissions are entered at the plant pollutant,
stack pollutant, point pollutant, and/or segment pollutant, the method code must be blank and an
emission value with units must be supplied.
Estimated With/Without Rule Effectiveness, Peak CO Season Daily With/Without Rule
Effectiveness, and Peak Ozone Season Daily With/Without Rule Effectiveness emissions may only
be entered at the segment pollutant. A method code is required. Method Code of '8' or '9' will
cause the system to generate the emission value. All other method codes ('1' through 7') are user
calculated and the emission value with units must be supplied.
Actual Uncontrolled Emissions (ACTU)
When Actual Uncontrolled emissions are entered, modified or system calculated/recalculated at
the segment pollutant, the Actual Uncontrolled segment pollutant emissions are bubbled to the
point and stack levels if the Actual Uncontrolled does not exist at the target level or the Actual
Uncontrolled exists at the target level with a method code of '1'. When Actual Uncontrolled
emissions are entered, modified or bubbled at the point pollutant, the Actual Uncontrolled point
pollutant emissions are bubbled to the plant level if the Actual Uncontrolled does not exist at the
plant pollutant or the Actual Uncontrolled exists at the plant pollutant with a method code of '1'.
If there are no Actual Uncontrolled emissions at the segment pollutant and an Actual Uncontrolled
emission type with method code of '1' was entered at the stack or point level, the Actual
Uncontrolled is stored with a method code of '1' with no emission value or units at the level it was
entered. Then, when Actual Uncontrolled emissions are entered at the segment pollutant with any
method code or is system calculated/recalculated, the bubble up process is invoked and the
bubbled value is stored at the stack pollutant and/or point pollutant as described above. If an
Actual Uncontrolled emissions type with method code of '1' was entered at the plant level, the
Actual Uncontrolled is stored with a method code of 'V with no emission value or units. Then,
when Actual Uncontrolled emissions are entered at the point pollutant with any method code or
are bubbled/re-bubbled to the point pollutant, the bubble up process is invoked and the bubbled
value is stored at the plant pollutant as described above.
The bubbled value is stored with a method code of '1' (indicating system generated).
Potential Uncontrolled Emissions (POTU) / Potential Controlled Emissions (POTC)
When Potential Uncontrolled or Potential Controlled emissions are entered or modified at the
segment pollutant, the emissions are bubbled to the point and stack levels if the Potential
Uncontrolled / Potential Controlled does not exist at the level or the Potential Uncontrolled /
Potential Controlled exists at the target level with a method code of '1'. When Potential
Uncontrolled / Potential Controlled emissions are entered, modified or bubbled at the point
pollutant, the emissions are bubbled to the plant level if the Potential Uncontrolled / Potential
Controlled does not exist at the plant pollutant or the Potential Uncontrolled / Potential Controlled
exists at the plant pollutant with a method code of 'V.
The bubbled value is stored at each level with a method code of '1' (indicating system generated).
Estimated Emissions With/Without Rule Effectiveness (ESTI/ESTW), Peak CO Season Daily
With/Without Rule Effectiveness (CODW/CODA), Peak Ozone Season Daily With/Without Rule
Effectiveness (03DW/03DA)
April 2003
1-39 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
Annual and Daily Estimated Emissions values with and without rule effectiveness can be input
directly by users after the emissions are calculated externally to AFS or calculated by AFS. These
emissions are only entered or calculated at the segment pollutant level. The aggregation will only
populate the point, stack and plant level emissions values if all the segments have emissions
values for the pollutant and the type being aggregated. Each emission type is aggregated
independently. AFS ensures that a plant pollutant emissions value exist for either ESTI - Estimated
Emissions Without Rule Effectiveness OR ESTW - Estimated Emissions With Rule Effectiveness if
emissions are reported for a pollutant.
The bubbled up value is stored at each target level with a method code of blank.
1.17.1 Example of Bubbleup
The following is an example of an aggregation (bubble-up) based on a facility that has 3 segment
pollutant records for VOC. Note that all of these records have Estimated Emissions without rule
effectiveness (ESTI) so they meet the requirement that all segments for a pollutant must have the
same emission type emissions value populated. The third segment has Estimated Emissions with
rule effectiveness. The only level that gets bubbled for the emission type "ESTW" is point. Point
002 E will contain the ESTW segment emissions value since it is the only VOC segment for the
point. Plant and Stack level will not contain ESTW.
Stack
Point
Segment
Pollutant
ESTI
001
001 E
01
VOC
20 TY
Stack
Point
Segment
Pollutant
ESTI
002
001 E
02
VOC
10 TY
Stack
Point
Segment
Pollutant
ESTI
ESTW
001
002 E
01
VOC
40 TY
50 TY
The aggregation (bubble-up) of these 3 segment pollutant records for the same facility would
produce the following results:
Point Pollutant ESTI emissions for Point 001 E =
Point Pollutant ESTI emissions for Point 002 E =
Stack Pollutant ESTI emissions for Stack 001 =
Stack Pollutant ESTI emissions for Stack 002 =
Plant Pollutant ESTI emissions
Point Pollutant ESTW emissions for Point 002 E=
30 TY of VOC
40 TY of VOC
60 TY of VOC
10TYofVOC
70 TY of VOC
50 TY of VOC
1.17.2 Units Conversion
Every time an emissions value changes, AFS aggregates the other levels anew. Though emissions
values may be entered in a variety of units, AFS converts all emissions to a standard unit of
tons/year (TY) at the aggregated levels. Segment emission values which are entered in hourly
units are aggregated using an assumed 24 hour operation schedule (8760 hours). This must be
considered when entering the hourly values in order to ensure aggregations equal expected point,
stack and plant values. AFS converts emissions values less than 1 ton/year (TY) to pounds/year
(PY) by multiplying the emissions value times 2000.
April 2003
1-40
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.18 Emissions, Process Rate and Control Equipment Efficiency Calculations
Annual and Daily Estimated Emissions values with and without rule effectiveness are
calculated by AFS using standard equations when the emissions method code is equal to '8' or '9'.
The method of calculation is indicated in the emissions method code. The emission types
representing these emissions types are:
ESTI - Estimated Emissions Without Rule Effectiveness
ESTW - Estimated Emissions With Rule Effectiveness
CODA - Peak CO Season Daily Emissions Without Rule Effectiveness
CODW - Peak CO Season Daily Emissions With Rule Effectiveness
03DA - Peak Ozone Season Daily Emissions Without Rule Effectiveness
03DW - Peak Ozone Season Daily Emissions With Rule Effectiveness
One of the variables in the algorithm is the emission factor. A method code of '8' directs AFS to
use the AP-42 emissions factors maintained in AFS. A method code of '9' directs AFS to use the
emission factor supplied by the user. Distinguishing which emission factor to use is the only
difference between the two calculation methods. The calculations are the same. If the Rule
Effectiveness data element is not valued, a default of 100 is used in the calculation so that Rule
Effectiveness has no impact on the result. These emissions are only calculated at the segment
pollutant level. Each emission type is aggregated to the point, stack and plant levels (see section
1.17).
Peak CO Season Daily Process Rate and/or Peak Ozone Season Daily Process Rate will be
calculated automatically if a value has not been supplied and Peak CO Season Daily Emissions
and/or Peak Ozone Season Daily Emissions have been requested to be calculated using method
code '8' or '9'.
Actual Uncontrolled Emissions, emission type ACTU, is calculated at the segment pollutant level
when no user-supplied (method code of '2' or '3') value exists and the point is a merged point. The
calculation is based on the most recent year of inventory annual estimated emissions and control
efficiency. It is also calculated / re-calculated when an Estimated Emissions Without Rule
Effectiveness is entered or modified.
The Control Equipment Efficiency for PM10 is calculated when the user enters a 'C' in the control
equipment efficiency method code. AFS searches GEOCOMMON tables established to support
this activity. The control equipment efficiency is based on either:
1. SCC Specific - Pollutant/SCC/Primary and/or Secondary Control Equipment OR
2. Generic - SCC-specific uncontrolled particle size distribution data and
typical (not SCC-specific) control device efficiency.
If the data in AFS matches the first SCC-specific table data in the first data comparison, the
resulting control equipment efficiency will be supplied with a method code of 'S' - SCC Specific
algorithm. If the first data comparison fails, the second algorithm is performed using the more
generic data. The resulting control equipment efficiency will be supplied with a method code of
'G' - Generic Algorithm.
The specific calculations for each emissions type, daily process rate and control equipment
efficiency are depicted in the Training Workbook. The following is a list of the calculations and the
April 2003
1-41 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
data elements that comprise the calculation. When one or more of these data elements is
modified, the calculations that use them are performed again and the new resulting emissions are
stored and aggregated.
Estimated Emissions Calculation
Recalculated when updated Where found
Source Classification Code (SCC) (Method code = 8) Segment General
Annual Fuel Process Rate Segment General
Ash or Sulfur Content Segment General
Ash, Sulfur, Trace Code Segment Pollutant
Trace Element Percent Segment Pollutant
Control Equipment Efficiency Segment Pollutant
Emission Factor and/or Decimal (method code = 9) Segment Pollutant
Rule Effectiveness Percent Segment Pollutant
Estimated Emissions Method Code to 8 or 9 Segment Pollutant
Peak CO Season Daily Emissions Calculation
Recalculated when updated Where found
Source Classification Code (SCC) (Method code = 8) Segment General
Peak CO Season Daily Process Rate Segment General
Ash or Sulfur Content Segment General
Ash, Sulfur, Trace Code Segment Pollutant
Trace Element Percent Segment Pollutant
Control Equipment Efficiency Segment Pollutant
Emission Factor and/or Decimal (Method code = 9) Segment Pollutant
Rule Effectiveness Percent Segment Pollutant
Peak Co Season Daily Emissions Method Code to 8 or Segment Pollutant
April 2003
1-42 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
Peak Ozone Season Daily Emissions Calculation
Recalculated when updated Where found
Source Classification Code (SCC) (Method code = 8) Segment General
Peak Ozone Season Daily Process Rate Segment General
Ash or Sulfur Content Segment General
Ash, Sulfur, Trace Code Segment Pollutant
Trace Element Percent Segment Pollutant
Control Equipment Efficiency Segment Pollutant
Emission Factor and/or Decimal Segment Pollutant
Rule Effectiveness Percent Segment Pollutant
Peak Ozone Season Daily Emissions Method Code to 8 or 9 Segment Pollutant
Peak CO Season Daily Process Rate Calculation
Recalculated when updated Where found
DEC-FEB Percent Annual Thruput Point General
Hours Per Day Point General
Days Per Week Point General
Hours Per Year Point General
Annual Fuel Process Rate Segment General
Peak CO Season Daily Emissions Method Code to 8 or Segment Pollutant
Peak Ozone Season Daily Process Rate Calculation
Recalculated when updated Where found
JUN-AUG Percent Annual Thruput Point General
Hours Per Day Point General
Days Per Week Point General
Hours Per Year Point General
Annual Fuel Process Rate Segment General
Peak Ozone Season Daily Emissions Method Code to 8 or 9 Segment Pollutant
Actual Uncontrolled Emissions Calculation
Recalculated when updated Where found
Estimated Emissions Value Decimal, and/or units Segment Pollutant
Actual Uncontrolled Emissions Method code to 1 Segment Pollutant
Control Equipment Efficiency % Segment Pollutant
Control Equipment Efficiency Calculation
Recalculated when updated Where found
If Control Equipment Efficiency Method Code = S or G:
SCC code Segment General
Control Equipment Segment Pollutant
Control Equipment Efficiency Method Code to C Segment Pollutant
April 2003
1-43 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.19 Utilities
The Utility function of AFS provides AFS data management, file maintenance, and miscellaneous
system processes. Section 4.0 of this manual describes the UTILITY screens and functionality in
detail.
1.20 Toggle Feature
The "Toggle" feature allows you to switch between Browse and Update and vice versa while
working within a plant. This feature is available on any screen that displays the PF12 key.
The three toggle scenarios are described:
1) You can toggle from a Browse data screen to its counterpart Update key screen.
This action initiates an "active" toggle, meaning that the system remembers the
browse data that you were viewing. When you return to Browse from Update on
the toggle, the first Browse data screen of the record that you were viewing is re-
displayed.
2) You can toggle from an Update menu to its Browse counterpart menu.
This is called an "inactive" toggle since you cannot toggle directly back to the
Update menu from Browse.
3) You can toggle from an Update data screen to its counterpart Browse data
selection screen.
This is called an "inactive" toggle since you cannot toggle directly back to the
Update date screen from Browse.
An "active" toggle is broken anytime you go to the Main Menu or use the "Next Screen" function
going from an Update program to a Browse program or a Browse program to an Update program.
This means that the current "active" toggle no longer exists.
An example of a toggle follows:
April 2003
1-44 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
PF12 is pressed on the browse data screen.
DATE : 04/25/97 AIRS FACILITY SUBSYSTEM - BROWSE PGM: AFP521
SCREEN: 521 STACK POLLUTANT INFORMATION MAP: AFM5212
TX 355 00001 UNITED PACKAGING CORPORATION INV YEAR: 90
STACK: 001 POLLUTANT CODE: PT CHEMICAL ABSTRACT #:
( SUSPENDED PARTICULATE (TSP) )
MEASURED
ALLOWABLE
POTENTIAL CONTROLLED
POTENTIAL UNCONTROLLED
PF1=HELP PF3=END PF4=MAIN PF5=TERM
( 97/04/16 - DDD )
EMISSIONS UNITS METHOD
: 0001124. TONS/YEAR 2
: 0000012. TONS/YEAR
: 0000011. TONS/YEAR
: 0000002. TONS/MONTH
PRIVATE (Y/N) : N
SCREEN: 054
PF7=PREV PF8=NEXT PF12=UPDT
The respective counterpart Update key screen is displayed with the fields set from the record that
was being browsed. The toggle has now become "active".
DATE : 04/25/97
SCREEN: 321
AIRS FACILITY SUBSYSTEM - UPDATE
STACK POLLUTANT INFORMATION
PGM: AFP321
MAP: AFM3211
TX 355 00001
*STACK: 001
UNITED PACKAGING CORPORATION INV YEAR: 90
POLLUTANT CODE: PT CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
April 2003
1-45
Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
PF12 is pressed on an Update screen. The toggle is "active", therefore the Browse is a "restart".
DATE : 04/29/97
SCREEN: 321
AIRS FACILITY SUBSYSTEM - UPDATE
STACK POLLUTANT INFORMATION
PGM: AFP321
MAP: AFM3212
TX 355 00001
*STACK: 001
UNITED PACKAGING CORPORATION INV YEAR: 90
POLLUTANT CODE: PT CHEMICAL ABSTRACT #:
EMISSIONS
TYPE VALUE
UNIT METHOD
MEAS 1124_
POTC 11
TY
TY
EMISSIONS
TYPE VALUE
UNIT METHOD
ALLW
POTU
TY
TM
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 044
The first Browse data screen for the record that was displayed when the toggle was made "active"
is redisplayed.
DATE : 04/25/97 AIRS FACILITY SUBSYSTEM - BROWSE PGM: AFP521
SCREEN: 521 STACK POLLUTANT INFORMATION MAP: AFM5212
TX 355 00001 UNITED PACKAGING CORPORATION INV YEAR: 90
STACK: 001 POLLUTANT CODE: PT CHEMICAL ABSTRACT #:
( SUSPENDED PARTICULATE (TSP) )
MEASURED
ALLOWABLE
POTENTIAL CONTROLLED
POTENTIAL UNCONTROLLED
PF1=HELP PF3=END PF4=MAIN PF5=TERM
( 97/04/25 - DDD )
EMISSIONS UNITS METHOD
: 0001124. TONS/YEAR 2
: 0000012. TONS/YEAR
: 0000011. TONS/YEAR
: 0000002. TONS/MONTH
PRIVATE (Y/N) : N
SCREEN: 054
PF7=PREV PF8=NEXT PF12=UPDT
April 2003
1-46
Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
1.21 Year 2000 - Guidelines for Dates in AFS
A new EPA date standard has been adopted for data processing applications which requires that
all EPA systems be Year 2000 compliant by providing for a 4 digit year numeric representation of
dates as CCYYMMDD. Modifying AFS solely to be compliant with the new EPA date standard is
not cost-effective at this time. The re-engineered AFS will adhere to the new EPA date standard.
In the interim, a simpler solution has been implemented to resolve the Year 2000 problem in AFS.
AFS will retain its current 2 digit year externally (in online screens, retrievals, batch transaction
formats, etc...) but internally recognize the century to provide the proper date computation and
sorting. The AFS system will apply the following rule when evaluating years:
If the 2 digit year is greater than 50, assume the century is 19, otherwise, assume the
century is 20. This is referred to as the '50' rule.
The '50' rule is applied to all 2 digit year dates discussed in this manual.
April 2003
1-47 Introduction
-------
AFS User's Guide
AF3 AFS Data Storage
April 2003
1-48 Introduction
-------
AFS User's Guide
AF3
AFS Data Storage
2.0 On-Line Updating
AFS is a menu driven system. All activities, from choosing AFS at the AIRS Main Menu (Figure 1-9)
to updating segment level emissions data are initiated through a menu selection.
In the following section, on-line updating will be described in detail. Each description will include
sample figures of the actual on-line update screens. Included in the sample screens will be both the
key data screen (or identification screen) and the detail data screen.
2.1 Accessing On-Line Update
During the logon procedure outlined in Section 1.5, you logged onto AFS (Figure 1-9) and received
the AIRS Facility System Main Menu (Figure 1-10). Updating AFS using the On-line method is
accessed through this menu by selecting option 1, entitled 'UPDATE THE DATABASE' and
pressing as shown in Figure 2-1.
AIRS FACILITY SUBSYSTEM
MAIN MENU
1 UPDATE THE DATABASE
2 BROWSE THE DATABASE
3 SELECT A REPORT
4 SELECT A UTILITY
ENTER MENU SELECTION: 1
NEED ASSISTANCE? CALL THE AFS HELPLINE AT 1-800-367-1044
PF1=HELP PF3=END PF4=SUBSYSTEM MENU PF5=TERM
UPDATE:
BROWSE:
REPORTS:
UTILITY:
FIGURE 2-1 AFS MAIN MENU SCREEN
Allows you to add or change AFS data through the use of online screens (Provided
your user profile has update authority).
Provides on-line viewing of AFS data.
Allows you to develop standard Fixed Format or user-defined Ad-Hoc reports.
Provides AFS data management, file maintenance, and miscellaneous system
processes.
Your AFS User Profile must be defined for Update access in order to proceed any further. If AFS
Security determines that the appropriate access authority is not defined, admission to UPDATE THE
April 2003
2-1
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATABASE will be denied and an error message will be displayed in the upper left corner of this
screen.
When the proper Update access is confirmed, the Identification screen (Figure 2-2) will be displayed.
2.2
Plant Identification
The IDENTIFICATION screen requires you to identify a plant, asbestos renovation/demolition
contractor, or landfill when updating or browsing the database.
DATE : 03/30/94
SCREEN: 000
AIRS FACILITY SUBSYSTEM
IDENTIFICATION
PGM: AFN00001
MAP: AFM0002
PLEASE ENTER (ONE) PLANT IDENTIFICATION:
AFS PLANT ID (STATE/COUNTY/PLANT) ..
CDS PLANT ID (STATE/COUNTY/PLANT) ..
NEDS PLANT ID (STATE/COUNTY/PLANT) .
EPA ID
DUN & BRADSTREET NUMBER
STATE REGISTRATION (ST/ST REG NO.)
STATE: COUNTY: PLANT NAME:
YEAR OF EMISSIONS INVENTORY (OR ANY ALPHA-CHAR(S) FOR CURRENT YEAR)
OR ENTER (ONE) ASBESTOS CONTRACTOR IDENTIFICATION:
CONTRACTOR I.D.(STATE/CONTRACTOR): /
STATE:
CONTRACTOR NAME:
OR ENTER (ONE) LANDFILL IDENTIFICATION:
LANDFILL EPA I.D Updating
STATE: LANDFILL NAME :
August 1995
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-2 IDENTIFICATION SCREEN
To ADD a plant, you must supply a State and County Code, and either a CDS Plant ID, NEDS Plant
ID or both. The state field may be either the FIPS State code or the state postal abbreviation. For
example New York is "36" or "NY".
The acronym CDS is a "left-over" term referring to Compliance Data System; the data system prior
to AFS that stored compliance and enforcement information for the Federal government. If this ID is
provided, the facility may be updated with compliance and enforcement related data. The acronym
NEDS is also a "left-over" term referring to National Emission Data System; the data system prior to
AFS that stored point source emissions information for the Federal government. A NEDS ID
indicates that the facility will contain emissions related data. If both CDS and NEDS IDS are
assigned, the facility can contain both types of data. To assign an AFS Plant ID you must also enter:
the CDS ID if compliance only facility;
the NEDS ID if emissions only facility;
the CDS ID and NEDS ID if associated facility
If you specify a NEDS Plant ID, the year of emissions inventory field must contain a value.
To update an existing emissions inventory, either specify the year of emissions inventory you want to
April 2003
2-2
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
update or enter one or two alphabetic characters and AFS will retrieve the current year. To update
data for a new Year of Emissions Inventory, select the current year of inventory, proceed to the Plant
General emissions data screen, and increment or decrement the Year of Emission Inventory to the
desired year.
If the facility already exists in AFS, you may identify it by one (and only one) of the following
identification numbers: AFS Plant ID, CDS Plant ID, NEDS Plant ID, EPA ID, Dunn & Bradstreet
Number or State Registration Number. Keep in mind that fields other than CDS and NEDS Plant IDs
are optional fields and may not necessarily be filled in for the plant.
Once an identification field is provided, press . At this point, AFS attempts to locate the
facility on the database. If the requested plant can not be found on the database, a message is
displayed and the user is asked to confirm the add of the new plant. Refer to Figure 2-3. If AFS
locates the requested facility on the database, the AFS Update Menu is displayed next. Details on
the AFS Update menu can be found in Section 2.3 of this manual.
PLEASE ENTER (ONE) PLANT IDENTIFICATION:
AFS PLANT ID (STATE/COUNTY/PLANT) : /
CDS PLANT ID (STATE/COUNTY/PLANT) : 22 / 127
NEDS PLANT ID (STATE/COUNTY/PLANT) .... : /
EPA + +
DUN * *
STA * PLANT DOES NOT EXIST. *
STA * CONFIRM AN ADD? (Y/N): *
YEA + + FOR CURRENT YEAR)
OR ENTER (ONE) ASBESTOS CONTRACTOR IDENTIFICATION:
CONTRACTOR I.D.(STATE/CONTRACTOR): /
STATE: CONTRACTOR NAME:
OR ENTER (ONE) LANDFILL IDENTIFICATION:
LANDFILL EPA I.D
STATE: LANDFILL NAME :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-3 CONFIRMATION TO ADD A NEW FACILITY
If you choose to cancel the request, answer "N" and and you will be returned to the
Identification screen where you can re-specify your request. REFER TO FIGURE 2-4 and FIGURE
2-5)
April 2003
2-3
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
AIRS FACILITY SUBSYSTEM
IDENTIFICATION
PLEASE ENTER (ONE) PLANT IDENTIFICATION:
AFS PLANT ID (STATE/COUNTY/PLANT) : / /
CDS PLANT ID (STATE/COUNTY/PLANT) : 22 / 127 / 12345
NEDS PLANT ID (STATE/COUNTY/PLANT) .... : / /
EPA + +
DUN * *
STA * PLANT DOES NOT EXIST. *
STA * CONFIRM AN ADD? (Y/N): N *
YEA + + FOR CURRENT YEAR)
OR ENTER (ONE) ASBESTOS CONTRACTOR IDENTIFICATION:
CONTRACTOR I.D.(STATE/CONTRACTOR): /
STATE: CONTRACTOR NAME:
OR ENTER (ONE) LANDFILL IDENTIFICATION:
LANDFILL EPA I.D
STATE: LANDFILL NAME :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-4 NEGATIVE ANSWER TO CONFIRMATION SCREEN
SELECT ANOTHER IDENTIFIER.
DATE : 0:
SCREEN: 000
AIRS FACILITY SUBSYSTEM
IDENTIFICATION
PLEASE ENTER (ONE) PLANT IDENTIFICATION:
AFS PLANT ID (STATE/COUNTY/PLANT) : / /
CDS PLANT ID (STATE/COUNTY/PLANT) : 22 / 127 / 12345
NEDS PLANT ID (STATE/COUNTY/PLANT) .... : / /
EPA ID :
DUN & BRADSTREET NUMBER :
STATE REGISTRATION (ST/ST REG NO.) .. : /
STATE: COUNTY: PLANT NAME:
YEAR OF EMISSIONS INVENTORY (OR ANY ALPHA-CHAR(S) FOR CURRENT YEAR)
OR ENTER (ONE) ASBESTOS CONTRACTOR IDENTIFICATION:
CONTRACTOR I.D.(STATE/CONTRACTOR): /
STATE: CONTRACTOR NAME:
OR ENTER (ONE) LANDFILL IDENTIFICATION:
LANDFILL EPA I.D
STATE: LANDFILL NAME :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
April 2003
2-4
On-Line Updating
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 2-5 AFS RESPONSE TO NEGATIVE ANSWER ON CONFIRMATION SCREEN
April 2003 2-5 On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
If the intention is to add a new plant, answer "Y" to the confirmation screen and . A series
of screens will be presented depending on the type of Plant Identification number that was entered
on the Identification screen. The Plant General screen will always be displayed next. Refer to
Section 2.4 for Plant General information.
The IDENTIFICATION screen also supports the use of a State Code and partial plant, contractor or
landfill name to prompt AFS to perform a substring search. A substring search looks for the
characters you specified in any part of the name on the database. If no match is found between the
substring parameters and AFS, an on-screen window informs you that no records were found and
offers the opportunity to modify substring search input values. For each plant retrieved during a
substring search, a window displays the SCSC, Name, Address, and City (see Figure 2-6). If you
select a facility to update from the list you will be taken to the Update Menu (screen 002 - Figure 2-
7). To return to the list of selected plants (Plant Name Search), enter "000" in the "screen: "
option at the bottom right hand corner of any update screen.
DflTE : 08/30/05
FIIRS FACILITY SUBSYSTEM
PLflNT NflME SEflRCH
PGM: flFNOOOOl
MflP: flFMOOOlO
SCSC
TftB TO SELECTION flND PRESS
NflME flDDRESS
CITY
0901300813 flMERICflN SLEEVE BEfiRING
0901300838 flMERICflN SLEEVE BEflRING
1 SPRING ST
1 SPRING ST
STAFFORD
STAFFORD
PF3=END PF5=TERM PF7=PREV PF8=NEXT
FIGURE 2-6 PLANT NAME SEARCH SCREEN
September 2005
On-Line Updating
2-6
-------
AFS User's Guide
AF3
AFS Data Storage
2.3 AFS Update Menu
This menu shows up after an existing facility has been identified on the AFS Identification screen
(Figure 2-2). The UPDATE MENU allows you to select one of four AFS data levels for adding or
changing data.
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-7 AFS UPDATE MENU
PLANT INFORMATION The facility for which regulatory compliance and/or emissions data are
recorded
STACK INFORMATION
POINT INFORMATION
SEGMENT INFORMATION
The place within a facility where emissions enter the atmosphere,
typically a stack, vent or location of fugitive emissions
A process location or tank within the facility at which pollutants are
produced
The components of a process, including physical and operating
parameters, that produces emissions
Plant level data is entered first when adding a new plant to AFS and the appropriate screens are
automatically presented to the user. Stack and segment levels are only available to facilities that
have a NEDS Plant ID. AFS requires that at least one Segment General record be created for each
emissions Point General record. This combination identifies at least one process or process
component (segment) for a process location (emissions point). Stack General records describe the
physical properties of the stack, vent or location of fugitive emissions. Once a stack has been
established in AFS, stacks may be linked to segments to identify the pathway from where pollutant
emissions are produced to where the emissions enter the atmosphere. Using this stack linking
mechanism, AFS supports not only the one to one relationship where there exists one point, one
segment and one stack but also the scenarios where emissions are produced at the same emissions
April 2003
2-7
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
point and the resultant pollutant emissions are vented through more than one stack or two processes
are performed at different emissions points and are vented through the same stack.
To select a particular level to update, type in the desired option number and press . The
next menu presented depends on the option selected.
Each of the four AFS levels has an update menu of its own and are described individually in the
following sections.
2.3.1 AFS Plant Update Menu
The Plant level Update menu provides access to the following plant level data update screens.
DATE : 12/08/94
SCREEN: 040
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT INFORMATION
PGM: AFP040
MAP: AFM0401
1 GENERAL INFORMATION (300)
2 POLLUTANT INFORMATION (301)
3 AIR PROGRAMS (302)
4 POLLUTANT AIR PROGRAMS (303)
5 PERMIT ADMINISTRATION (060)
6 MAILING LABEL INFORMATION (305)
7 ACTIONS (306)
8 COMMENTS (307)
9 ASBESTOS INFORMATION (042)
10 HIGH PRIORITY VIOLATOR UPDATE UTILITY (314)
11 COMPLIANCE MONITORING STRATEGY (315)
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
FIGURE 2-8 AFS PLANT LEVEL UPDATE MENU
GENERAL INFORMATION Name, address, SIC, NAICS, general compliance and emissions
inventory data for the plant as a whole
POLLUTANT INFORMATION Plant pollutant emissions by emission type
AIR PROGRAMS
Plant compliance profile by regulatory program type, such as SIP,
NESHAP, PSD, Non-Federal, etc.
POLLUTANT AIR PROGRAMS Plant compliance profile by regulated pollutant
PERMIT ADMINISTRATION Tracking module for data relating to permit applications, permits and
events related to the life cycle of an application, draft and issued
permit data
April 2003
2-8
On-Line Updating
-------
AFS User's Guide
AF3 AFS Data Storage
MAILING LABEL Plant mailing address data. This address may differ from the
INFORMATION actual location of the facility
ACTIONS Regulatory actions applied to the plant as a whole
COMMENTS Comment text applicable to the plant or actions
ASBESTOS INFORMATION Data pertaining to asbestos renovation/demolition, contractor
performance at the plant, or asbestos disposal and landfills
HIGH PRIORITY VIOLATOR Data pertaining to the plant's high priority violation status
COMPLIANCE MONITORING STRATEGY Data pertaining to the plant's compliance
monitoring strategy
To select a particular record to update, type in the desired option number and press . The
next screen presented will be the key data screen for the option selected.
Each of the nine Plant level update screens are described individually in the following sections.
2.3.1.1 Plant General
The Plant General update screen supports the updating of plant name, address, industry type and
other general regulatory compliance and emissions inventory data.
To add a plant to AFS, you must supply information for those mandatory data elements identified by
an asterisk displayed next to the input field: Plant Name, Street Address, Primary Standard
Industrial Classification (SIC) or North American Industry Class System (NAICS). A city code or city
name is also required. The city name will be generated when a city code is entered. The generated
city name will be displayed in update, browse and is retrievable using Ad hoc.
The plant's EPA Id is available for update to the Regional Data Stewards; users who have a special
access code of 'R'.
April 2003 2-9 On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DflTE ;
SCREEN:
08/18/08
300
flIRS FACILITY SUBSYSTEM - UPDflTE
GENERflL PLflNT INFORMflTION
PGM: ftFPSOO
MflP: ftFM3001
CDS...: 00000
EPfl ID:
NEDS :
DUN & BRflDSTREET:
flFS:
DflTE PLflNT INFORMflTION LflST UPDflTED (YYMMDD) :
YEflR OF EMISSIONS INVENTORY: EPfl ID:
*PLflNT NflME ... :
*STREET flDDRESS :
CITY CODE : CITY NOME . :
ZIP CODE : -
NORTH flMERICflN INDUSTRY CLflSSIFICflTION SYSTEM [NfllCS]
STflNDflRD INDUSTRIflL CLflSSIFICftTION *PRIMflRY INDUSTRIE CODE . .
SECONDARY INDUSTRIflL CODE
TERTIflRY INDUSTRIflL CODE .
LOCflL CONTROL REGION
INSPECTOR
REGIONflL PLflNNING flGENCY
RIR TOXIC INITIflTIVE
SOURCE MONITORING INFORMflTION
MORE
FIGURE 2-9
GENERAL INFORMATION FOR PLANT GENERAL SCREEN
The label "More" in the lower right corner of the screen indicates there are additional 'pages' to the
update screen. When adding a compliance or emissions-only facility, a second compliance or emissions
specific 'page' will be displayed following the completion of the general information page.
STATE COMPLIANCE STATUS .... :
STATE CLASSIFICATION CODE .. :
OPERATING STATUS :
PRIORITY CODE :
STATE REGISTRATION NUMBER .. :
*GOVERNMENTAL FACILITY CODE
CONTACT PERSON - COMPLIANCE
TELEPHONE NUMBER
PLANT DESCRIPTION
EPA COMPLIANCE STATUS .. :
EPA CLASSIFICATION CODE :
aiaNIPICANT VIOLATOR PLAO.
FACILITY CAPACITY .... : 0000000
FACILITY CAPACITY UNITS:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
PRIVATE(Y/N): N
SCREEN: 040
FIGURE 2-10 COMPLIANCE 'PAGE1 OF PLANT GENERAL SCREEN
November 2008
On-Line Updating
2-10
-------
AFS User's Guide
AF3 AFS Data Storage
Plant General data elements specific to the compliance community are contained on this screen. A
Government Facility Code must be supplied.
Compliance Status, Classification Code and Operating Status are system generated from Plant Air
Program record data, and appear on this screen as display elements only. The worst case State and
EPA Pollutant Compliance Status values entered for Plant Pollutant Air Program records become the
Compliance Status values for the air program. The worst case State and EPA Pollutant Compliance
Status values generated for Plant Air Program records in turn become the Compliance Status values
for the plant as a whole. The hierarchy of the Pollutant Compliance Status codes from worst (out of
compliance for regulatory or procedural requirements) to best (in compliance for regulatory or procedural
requirements) is: B, 1, 6, W, Y, 0, A, 7, 5, C, 4, 3, M, 2, 8, 9, P.
The most significant State and EPA Pollutant Classification values entered for Plant Pollutant Air
Program records become the Classification values for the air program. The most significant State and
EPA Pollutant Classification values generated for Plant Air Program records in turn become the
Classification values forthe plant as a whole. The hierarchy of the Pollutant Classification codes from
most significant to minor source classification is: A, A1, E1, SM, A2, E2, B, ND, C, UK and blank.
Pollutant Classification values A1, E1, A2, E2, ND and UK are obsolete values; all fields on existing
records can be updated, but new records cannot be created with these code values.
If the air program operating status is shut down, (1.) forthe classification bubble up, that air program
will not be included in the classification bubble-up, except if a plant only has shut down air programs,
then classification would be generated from those air programs even though they are all shut down (2.)
for the compliance bubble up for a non-CMS plant, that air program will not be included in the
compliance bubble up, except if a plant only has shut down air programs, the compliance would be
generated from those air programs even though they are all shut down, and (3.) for compliance bubble
up of a CMS plant, all air programs are included in the bubble up, regardless of the air program status.
The 'most operational' Air Program Status value found among the plant air program records is then
applied as the Operating Status for the plant as a whole as found on the Plant General record. The
hierarchy of valid Operating Status codes from most to least operational is: O, L, R, D, S, I, T, C, P and
X.
National EPA users have update access to the Priority Code data element. Existing values for the
Priority Code data element will be displayed to all user classifications.
Users with sensitive update access will be allowed to enter values for Facility Capacity and Units. Users
with sensitive read-only access will be able to see values for these fields but will not be allowed to
modify them. State or county agency update users may designate non-federally reportable facilities as
'State-Private' by entering 'Y' in that field.
When adding a new compliance facility, once you've entered general plant data, AFS will automatically
bring you to the Plant Air Programs and Plant Pollutant Air Programs update screens. EPA mandates
that all compliance facilities maintained in AFS maintain at least one plant air program and associated
pollutant air program record. These mandated records must be added at the same time to establish the
facility in AFS.
January 2007 On-Line Updating
2-11
-------
AFS User's Guide
AF3
AFS Data Storage
*YEAR OF EMISSIONS INVENTORY(YY)
SIP PROGRAM STATUS AREA
UTM ZONE
UTM HORIZONTAL COOR (KM)
UTM VERTICAL COORD (KM)
LATITUDE (DDMMSS) .
LONGITUDE (DDDMMSS)
00
000 . 0
0000 . 0
00 :
000
00 : 00
: 00 : 00
CONTACT PERSON - EMISSIONS
TELEPHONE NUMBER
NUMBER OF EMPLOYEES
PROPERTY AREA (ACRES)
PRINCIPAL PRODUCT
SDE 1
00000
00000
USER PLANT ID
0 EMERGENCY CONTROL PLAN
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 302
FIGURE 2-11 EMISSIONS 'PAGE1 OF PLANT GENERAL SCREEN
Plant General data elements specific to the emissions community are contained on this screen. A Year
of Emissions Inventory must be supplied.
Multiple years of emissions inventories are resident and updatable in AFS. The year of emissions
inventory displayed on this screen indicates the year for which the emissions inventory is being or has
been developed for the facility selected. Updating this field to change the year triggers the following
special processing. If you increment the Year of Emissions Inventory field, AFS copies current values
of emissions-related information forthe plant and stores them on archive files. SIP data will be included
in the new year of data unless you indicate otherwise in the window supplied at the time the year of
inventory is incremented. Only Plant General and Plant Mail information will be copied to the new year
if the "no emissions data" option was selected in the window. All subsequent changes to emissions
values are for the new year indicated until a different year and/or plant is selected on the Plant
Identification screen. If you decrement the Year of Emissions Inventory field, AFS copies current values
of emissions-related information for the plant and stores them on archive files. You must indicate
whether all emissions data, exclude SIP data, or no emissions data is to be copied in the window
supplied at the time the year of inventory is decremented. All subsequent changes to emissions values
are still forthe most current year, not the decremented year, until a different year and/or plant is selected
on the Plant Identification screen.
You can supply either UTM coordinates or Latitude-Longitude coordinates. Latitude and Longitude
coordinates are generated if UTM coordinates are supplied and vice versa.
State agency update users may designate non-Federally reportable facilities as 'State-Private' by
entering 'Y' in that field.
The SIP Program and Status Area data elements may be entered to indicate the facility resides in a
certain attainment, non-attainment or modeling area. Facilities are subject to SIP processing when a
April 2003
2-12
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
program/non-attainment status area has been entered for a year of emissions inventory in which a SIP
Inventory is required. For a frozen inventory (an inventory which is available for review or has been
approved by headquarters) the following fields will be display only:
UTM Zone
UTM Horizontal Coordinate
UTM Vertical Coordinate
Latitude Coordinate
Longitude Coordinate
SIP Program/Status Area
State Data Element 9
PLEASE ENTER THE CASE-BY-CASE MACT DETERMINATIONS THE FACILITY HAS COMPLETED:
MACT
CATEGORY
SUB
CATEGORY
DATE
SECTION DETERMINATION
112 COMPLETED
INDICATOR (YYYYMMDD)
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 040
FIGURE 2-11.1 MACT DETERMINATION 'PAGE1 OF PLANT GENERAL SCREEN
The MACT Determination screen is displayed for only emissions and associated facilities, the data on
this screen is used to track MACT determinations that have been performed for the facility.
When updating an existing Plant General record, only those screens applicable to the plant type will be
displayed:
Compliance plants- the general information and compliance 'page'
Emissions plants- the general information, emissions 'page', and MACT Determination 'page'
Associated (compliance and emissions) plants- the general information, compliance and emissions
'pages', and MACT Determination 'page'
When values concerning plant name and address information are updated, a window is displayed,
asking if the information should be automatically reflected in the mailing label record forthe plant. A 'Yes'
answer causes the address data to be copied to a mailing label record for the plant.
April 2003
2-13
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
*YEAR OF EMISSIONS INVENTORY(YY):
SIP PROGRAM
CO
OZONE
STATUS AREA
N5601
UTM ZONE
UTM HORIZONTAL COOR (KM)
UTM VERTICAL COORD (KM)
LATITUDE (DDMMSS) .
LONGITUDE (DDDMMSS)
SHOULD THE MAILING LABEL INFORMATION FOR
THIS PLANT BE UPDATED? (Y/N):
CONTACT
TELEPHON +
NUMBER OF EMPLOYEES .
PROPERTY AREA (ACRES)
PRINCIPAL PRODUCT ...
SDE 1
00000
00000
USER PLANT ID
0 EMERGENCY CONTROL PLAN
067-0008_
2
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF10=SCRN
FIGURE 2-12 CONFIRMATION TO CHANGE MAILING LABEL INFORMATION
2.3.1.2 Plant Pollutant
The Plant Pollutant update screen allows users with compliance update access to update pollutant data
for specific plant pollutant emissions types. You must enter either a Pollutant Code or a Chemical
Abstract Service Number to identify the record in AFS.
The PLANT POLLUTANT key data screen will be displayed in response to selecting option 2 on the
Plant Update menu.
April 2003
2-14
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/05/94 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP301
SCREEN: 301 PLANT POLLUTANT INFORMATION MAP: AFM3011
FARMER BROTHERS REFINERY INV YEAR:
POLLUTANT CODE: CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN SCREEN:
FIGURE 2-13 PLANT POLLUTANT KEY DATA SCREEN
If the Pollutant Code (or CAS #) corresponds to an existing record in the database, the current values
for the record will be displayed on the update screen. For new records, entering this key datum will
result in the display of a blank data update screen.
DATE : 11/23/94
SCREEN: 301
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP301
PLANT POLLUTANT INFORMATION MAP: AFM3012
INV YEAR:
POLLUTANT CODE:
EMISSIONS
TYPE VALUE
CHEMICAL ABSTRACT #:
EMISSIONS
UNIT METHOD TYPE VALUE UNIT METHOD
PRIVATE (Y/N) : N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN : 040
FIGURE 2-14 PLANT POLLUTANT UPDATE SCREEN
April 2003
2-15
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
You may update data for one or more plant pollutant emissions types:
Allowable, Potential Controlled, Potential Uncontrolled or Actual Uncontrolled.
You must supply an Emissions Value, Unit Code, and Method Code (where applicable) for each
Emissions Type entered. The emissions value supports the entry of a floating decimal point. The use
of a Method Code of'1'for Actual Uncontrolled emissions prompts the system to bubble up all segment
level Actual Uncontrolled emission values (See Section 1.17).
If the pollutant specified is not a federally regulated pollutant, State or County personnel may specify this
record to be State-Private.
2.3.1.3 Plant Air Programs
The AFS Plant Air Programs update screen supports the updating of data about the regulatory programs
to which the facility is subject. Compliance users adding a plant must add a minimum of one plant air
program record; on-line help will only display air programs which are not permanently shut down
(operating status = X). You must enter an air program code to identify the record in the database.
DATE : 04/01/94
SCREEN: 302
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT AIR PROGRAMS
PGM: AFP302
MAP: AFM3021
*AIR PROGRAM CODE:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-15 AFS PLANT AIR PROGRAMS KEY DATA SCREEN
To update an existing Air Program record, enter the air program code. The data associated with the
record will then be displayed on the following input screen. For new records, entering this key datum
will result in the display of a blank data update screen.
January 2007
On-Line Updating
2-16
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 302
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT AIR PROGRAMS
PGM: AFP302
MAP: AFM3022
*AIR PROGRAM CODE:
STATE COMPLIANCE STATUS ..
STATE CLASSIFICATION CODE
*AIR PROGRAM STATUS
EVEN YEAR OF INSPECTION ..
ODD YEAR OF INSPECTION ..
RDE 1 .
RDE 4 .
RDE 7 .
RDE 11
RDE 2
RDE 5
RDE 9
RDE 12
EPA COMPLIANCE STATUS ....
EPA CLASSIFICATION CODE ..
STATE IMPLEMENTATION PLAN
EVEN STRATEGY: _ FREQUENCY
ODD STRATEGY: _ FREQUENCY
RDE 3 .
RDE 6 .
RDE 10
RDE 15
STAFF CODE
REPORTING REQUIREMENTS TO REGION
SCREEN: 303
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-16 AFS PLANT AIR PROGRAMS UPDATE
The Plant Air Program update screen requires you to supply Air Program Status. The 'most operational'
Air Program Status value found among the plant air program records is then applied as the Operating
Status for the plant as a whole as found on the Plant General record. The hierarchy for the operating
status field from most operational to permanently closed is: O, L, D, R, S, I, T, C, P and X.
State and EPA Compliance Status and Classification Codes are system generated from Plant Pollutant
Air Program record data, and appear on this screen as display elements only.
The worst case State and EPA Pollutant Compliance Status values entered for Plant Pollutant Air
Program records become the Compliance Status values for the air program. The worst case State and
EPA Pollutant Compliance Status values generated for Plant Air Program records in turn become the
Compliance Status values for the plant as a whole. The hierarchy of the Pollutant Compliance Status
codes from worst (out of compliance for regulatory or procedural requirements) to best (in compliance
for regulatory or procedural requirements) is: B, 1, 6, W, Y, 0, A, 7, U, 5, C, 4, 3, M, 2, 8, 9, P.
The most significant State and EPA Pollutant Classification values entered for Plant Pollutant Air
Program records become the Classification values for the air program. The most significant State and
EPA Pollutant Classification values generated for Plant Air Program records in turn become the
Classification values forthe plant as a whole. The hierarchy of the Pollutant Classification codes from
most significant to minor source classification is: A, A1, E1, SM, A2, E2, B, ND, C, UK and blank.
Pollutant Classification values A1, E1, A2, E2, ND and UK are obsolete values; all fields on existing
records can be updated, but new records cannot be created with these code values.
Plant inspection programs may be identified on this screen through the use of the Inspection Tracking
data fields (year of inspection frequency, strategy and inspection frequency). Depending on the current
year value, the current year of inspection program is contained in either the 'Even' or 'Odd' Year of
Inspection field, with the associated inspection program and scheduled inspections contained in the
associated Even or Odd Strategy and Frequency fields. Upcoming year data are contained in whichever
of the even or odd
January 2007
fields do not contain current year data.
On-Line Updating
2-17
-------
AFS User's Guide
AF3
AFS Data Storage
The sensitive Inspection tracking fields are available for update during the following schedule:
Even inspection tracking fields:
If the current calendar year is even -> update during March and September
If the current calendar year is odd -> update during March through November
Odd inspection tracking fields:
If the current calendar year is odd -> update during March and September
If the current calendar year is even -> update during March through November
At other times of the year, these values appear as display elements only.
The label "More" in the lower right hand corner of the Plant Air Programs Update screen indicates there
is an additional "page" of information forthe screen. The additional page of information (Figure 2-16.1)
will be displayed to allow the entry of up to twelve subpart values when updating Air Programs: "9" -
NSPS; "8" - NESHAP; "M" - MACT NESHAP; "0" - SIP SOURCE; and "1" - "SIP SOURCE UNDER
FEDERAL JURISDICTION. The subpart information pertains to sections 60, 61 and 63 of the Code of
Federal Regulations respectively. The Air Program being updated is presented in the Subparts label
on the screen. The corresponding Subpart descriptions will be displayed with the codes once they have
been added to AFS.
40 CFR PfiRT 63 (MflCT NESHflP) SUBPflRTS:
SCREEN: @40
PF1=HELP PF3=END PF4=MflIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRUIS
FIGURE 2-16.1 SUBPARTS 'PAGE1 OF PLANT AIR PROGRAMS
EPA mandates that all air program records must also have at least one associated pollutant air program
record. After adding a new air program record, you will automatically be taken to a Plant Pollutant Air
Program update screen for completion. The air program record will not be added to AFS without the
successful addition of the Plant Pollutant Air Program record.
January 2006
On-Line Updating
2.3.1.4 Plant Pollutant Air Program
The AFS Plant Pollutant Air Programs update screen supports the definition of the regulatory status of
pollutants emitted at a facility and subject to designated air programs. You must add an existing air
2-18
-------
AFS User's Guide
AF3
AFS Data Storage
program code and pollutant code (or CAS #) to identify a record.
DATE : 04/01/94
SCREEN: 303
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT POLLUTANT AIR PROGRAMS
PGM: AFP303
MAP: AFM3031
*AIR PROGRAM CODE:
POLLUTANT:
CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-17 PLANT POLLUTANT AIR PROGRAMS KEY DATA SCREEN
You may enter information specific to any given pollutant in association with a regulatory air program.
Air programs must already be defined for the plant before pollutant air program information can be
added. If the Air Program Code and Pollutant (or CAS #) combination corresponds to an existing record,
the values for the data elements are displayed for you to update. For new records, entering these key
data will result in the display of a blank data update screen.
DATE : 06/28/94
SCREEN: 303
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT POLLUTANT AIR PROGRAMS
PGM: AFP303
MAP: AFM3032
*AIR PROGRAM CODE:
POLLUTANT:
CHEMICAL ABSTRACT #:
*STATE POLLUTANT COMPLIANCE STATUS:
STATE POLLUTANT CLASSIFICATION :
STATE ATTAINMENT/NON-ATTAINMENT :
LOADING DERIVATION CODE :
TOXICITY LEVEL :
STATE REGULATION NUMBER :
EPA POLLUTANT COMPLIANCE STATUS
EPA POLLUTANT CLASSIFICATION ..
EPA ATTAINMENT/NON-ATTAINMENT
RDE 14
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 040
April 2003
2-19
On-Line Updating
-------
AFS User's Guide
AF3 AFS Data Storage
FIGURE 2-18 PLANT POLLUTANT AIR PROGRAM UPDATE SCREEN
The Plant Pollutant Air Programs update screen requires you to supply Pollutant Compliance Status. Users with
compliance update access may enter data in the State Pollutant Classification and State
Attainment/Nonattainment fields. Should EPA differ in their assessment of these values, they may enter different
values in the EPA Compliance Status, Pollutant Classification and Attainment/Nonattainment fields.
The worst case State and EPA Pollutant Compliance Status values entered for Plant Pollutant Air Program
records become the Compliance Status values for the air program. The worst case State and EPA Pollutant
Compliance Status values generated for Plant Air Program records in turn become the Compliance Status values
forthe plant as a whole. The hierarchy of the Pollutant Compliance Status codes from worst (out of compliance
for regulatory or procedural requirements) to best (in compliance for regulatory or procedural requirements) is:
B, 1, 6, W, Y, 0, A, 7, U, 5, C, 4, 3, M, 2, 8, 9, P.
The most significant State and EPA Pollutant Classification values entered for Plant Pollutant Air Program
records become the Classification values for the air program. The most significant State and EPA Pollutant
Classification values generated for Plant Air Program records in turn become the Classification values forthe
plant as a whole. The hierarchy of the Pollutant Classification codes from most significant to minor source
classification is: A, A1, E1 ,SM, A2, E2, B, ND, C, UK and blank. Pollutant Classification values A1, E1, A2, E2,
ND and UK are obsolete values; all fields on existing records can be updated, but new records cannot be created
with these code values.
State Compliance Status is always required. However, classification and attainment status are only required
if the air program code is anything except 8 (NESHAP) and the pollutant is PT, VOC, SO2, PM10 or PM2.5.
If the air program operating status is shut down, (1.) for the classification bubble up, that air program will not be
included in the classification bubble-up, except if a plant only has shut down air programs, then classification
would be generated from those air programs even though they are all shut down (2.) forthe compliance bubble
up for a non-CMS plant, that air program will not be included in the compliance bubble up, except if a plant only
has shut down air programs, the compliance would be generated from those air programs even though they are
all shutdown and (3.) for compliance bubble up of a CMS plant, all air programs are included in the bubble up,
regardless of the air program status.
May 2008 On-line Updating
2.3.1.5 Permit Administration
PERMIT ADMINISTRATION is a tracking module for data relating to permit applications, permits and
events related to the life cycle of an application, draft and issued permit data.
Enhanced AFS screen designs for ease of data entry allows the key and data portions of each permit
record to be presented on one screen instead of two. Also, selection of plants can be done on each
permit screen using the AFS Plant Id.
Another AFS enhancement made to the permit module concerns the ADD and CHANGE logic. If the
user enters both the key and data portions of a record and hits enter, ADD is assumed. If the record
does exist, it is displayed on the screen with an error message overwriting the data the user entered.
If the user enters just the key portion of a record and hits enter, change is assumed. If the record exists,
it is displayed. If not, an error message is displayed.
Permits is fully integrated with the rest of AFS Update. Users can traverse to other parts of AFS by
using the Next Screen function or PF keys. The last plant selected in permits is the one brought into
the other parts of AFS.
The minimum requirements necessary in order to utilize this module are the following:
* PLANT MUST HAVE AN AFS PLANT ID
2-20
-------
AFS User's Guide
AF3 AFS Data Storage
In order to enter plant specific permit data, the
plant must have a user-defined AFS Plant ID. The
existing Emissions or Compliance ID for a facility
may be entered as the AFS Plant ID.
* USER MUST HAVE EITHER COMPLIANCE OR EMISSIONS UPDATE ACCESS
The facility may have only a Compliance ID or an Emissions ID with an AFS Plant ID;
update access to either is required to update Permit Administration data.
* PERMIT AUTHORITY MUST BE DEFINED IN AFS
Title V requirement only
Identifies the Permit Authority for a given
geographic area or single permit.
Users need compliance or emissions update access
for the geographic area of Permit Authority.
If the criteria previously listed can be met, the user may select option 5 on the PLANT UPDATE MENU
(Figure 2-8). The following screen is displayed in response to that option being selected.
April 2003 2-21 On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 060
AIRS FACILITY SUBSYSTEM - UPDATE
PERMIT ADMINISTRATION MENU
PGM: AFP060
MAP: AFM0601
1 APPLICATIONS (350)
2 GENERAL INFORMATION - DRAFT PERMIT (351)
3 CONDITIONS - DRAFT PERMIT (352)
4 ASSOCIATIONS - DRAFT PERMIT (061)
5 EVENT TRACKING ACTIONS (353)
6 AFFECTED AGENCIES - DRAFT PERMIT (354)
7 ADMINISTRATIVE CHANGE TO ISSUED PERMIT (062
8 PERMIT COMPLIANCE (063)
9 PERMIT TARGETING (355)
10 PERMIT CONTACTS (356)
11 FEES (304)
12 DOCUMENT CATALOGUE (358)
ENTER MENU SELECTION:
* - DENOTES THIS OPTION IS CURRENTLY NOT AVAILABLE
PF3=END PF4=MAIN MENU PF5=TERMINATE PF10=NEXT NEXT SCREEN:
FIGURE 2-19 PERMIT ADMINISTRATION UPDATE MENU
At present, the options currently available for use are:
APPLICATIONS
GENERAL INFORMATION - DRAFT PERMIT
ASSOCIATIONS - DRAFT PERMITS
EVENT TRACKING ACTIONS
FEES
April 2003
2-22
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
PERMIT APPLICATIONS
By selecting option 1 on the Permit Administration Menu, the following screen will be displayed.
DATE : 04/01/94
SCREEN: 350
AIRS FACILITY SUBSYSTEM - UPDATE
APPLICATIONS
PGM: AFP350
MAP: AFM3501
*AFS PLANT ID (ST/CNTY/PLANT): /
*APPLICATION:
*APPLICATION CATEGORY :
PARTIAL APPLICATION INDICATOR :
REPORTED COMPLIANCE STATUS... :
PERMIT AUTHORITY STAFF :
APPLICATION TYPE
REPORTED COMPLIANCE REASON
PERMIT AUTHORITY DATA ELEMENTS:
1)
2)
3)
1)
2)
3)
PF3=END PF4=MAIN MENU PF5=TERMINATE PF9=REPEAT PF10=NEXT NEXT SCREEN: 060
FIGURE 2-20 PERMIT APPLICATIONS UPDATE SCREEN
The APPLICATIONS screen supports the updating of a permit application. Application records are
optional. Users will be required to supply an application category. The application category element
identifies whether a new application, an application renewal or an application for a permit modification
is being processed. A value for this field is mandatory because it will be used in the calculation of the
milestone due date for issuing a Title V permit. Milestone due dates are calculated in response to a
primary and/or secondary event. Other fields on the screen are optional.
To add an application, users must enter an AFS Plant ID, Application and Application Category.
April 2003
2-23
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
GENERAL INFORMATION - DRAFT PERMIT
By selecting option 2 on the Permit Administration Menu, the following screen will be displayed.
DATE : 04/01/94
SCREEN: 351
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL INFORMATION - DRAFT PERMIT
PGM: AFP351
MAP: AFM3511
*PERMIT CATEGORY
PERMIT WORK FILE
EFFECTIVE DATE (YYYYMMDD)
MODIFICATION/RENEWAL EFFECTIVE DATE (YYYYMMDD)
EXPIRATION DATE (YYYYMMDD)
PERMIT AUTHORITY DATA ELEMENTS: 1)
2)
3)
PRIVATE (Y/N): N
PF3=END PF4=MAIN MENU PF5=TERMINATE PF9=REPEAT PF10=NEXT NEXT SCREEN: 060
FIGURE 2-21 GENERAL INFORMATION - DRAFT PERMIT UPDATE SCREEN
This screen supports the updating of general information regarding a draft permit. Draft permit
information is optional. Information includes critical data about the kind of permit being processed and
key dates that identify when a permit becomes effective, when it expires, and when renewal or
modification dates are effective (if they apply).
To add a draft permit to the database, users will be required to supply a state, permit and a permit
category. The permit identifier must be unique to the state where the facility resides and the permit
category is mandatory because the value indicates the kind of permit being processed.
The user has the option to make all data for a permit private if it is a non-Title V permit.
April 2003
2-24
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
APPLICATION ASSOCIATIONS - DRAFT PERMIT
By selecting option 4 on the Permit Administration Menu, the following menu screen will be displayed.
DATE : 04/01/94
SCREEN: 061
AIRS FACILITY SUBSYSTEM - UPDATE
ASSOCIATIONS MENU - DRAFT PERMIT
PGM: AFP061
MAP: AFM0611
1 APPLICATIONS (360)
* 2 STACKS (361)
* 3 POINTS (362)
* 4 SEGMENTS (363)
5 COMMENTS (364)
ENTER MENU SELECTION: _
DENOTES THIS OPTION IS CURRENTLY NOT AVAILABLE
PF3=END PF4=MAIN MENU PF5=TERMINATE PF10=NEXT
NEXT SCREEN:
FIGURE 2-22 APPLICATION ASSOCIATIONS - DRAFT PERMIT MENU SCREEN
From this screen, users may elect to associate either an application and draft permit to a plant or add
a comment to a draft permit. Other options on this menu are currently unavailable.
April 2003
2-25
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
APPLICATION ASSOCIATIONS - DRAFT PERMIT
By selecting option 1 on the APPLICATION ASSOCIATION Menu, the choice made was to associate
an application and draft permit. The following ASSOCIATION screen will be displayed.
DATE : 06/14/94
SCREEN: 360
AIRS FACILITY SUBSYSTEM - UPDATE
APPLICATION ASSOCIATIONS - DRAFT PERMIT
PGM: AFP360
MAP: AFM3601
*AFS PLANT ID (ST/CNTY/PLANT): CT / 001 /
*PERMIT:
EPA ID:
COMMENT:
APPLICATIONS:
PF10=NEXT
NEXT SCREEN: 061
FIGURE 2-23 APPLICATION ASSOCIATIONS - DRAFT PERMIT UPDATE SCREEN
The associations screen allows the user to update the list of applications submitted for a permit or link
a permit to a facility. The permit number and applications must be previously established in the
database.
When a permit is issued, the application associated with the draft permit will be stored on the
associations record for the issued permit. When an event associated with approving draft permits or
monitoring issued permits is entered into the system, an associations record is automatically created
if it does not already exist.
Comments may be provided for this association by typing any alphanumeric character in the comment
field. A comment screen will be displayed at the conclusion of this association screen.
April 2003
2-26
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
PLANT PERMIT COMMENTS
Selecting option 5 on the APPLICATION ASSOCIATION Menu provides the user with the ability to add
textual comments applicable to an associated draft permit and application. This screen is also displayed
if the user typed any alphanumeric character in the comments field on the ASSOCIATION
APPLICATION Update screen (Figure 2-23). The following PLANT PERMIT COMMENTS screen will
be displayed.
DATE : 06/14/94 AIRS
SCREEN: 364
FACILITY SUBSYSTEM - UPDATE PGM: AFP364
PLANT PERMIT COMMENTS MAP: AFM3641
*AFS PLANT ID (ST/CNTY/PLANT)
* PERMIT:
CT / 001 / EPA ID:
* COMMENT #:
EPA:
STATE/LOCAL CONTROL REGION: /
OWNER PRIVATE (Y/N) : N
PF3=END PF4=MAIN MENU PF5=TERMINATE PF9=REPEAT PF10=NEXT NEXT SCREEN: 061
FIGURE 2-24 PLANT PERMIT COMMENTS UPDATE SCREEN
The Plant Permit Comments screen allows the addition or update of comments which relate to a permit,
which may or may not be associated with a facility. The permit must be previously established in the
database. This capability extends to users who represent the Permitting Authority, the EPA, and
Affected Agencies. Users may only update comments owned by their agencies.
Comments can be added using comment number 001 - 998 or generated using 999.
April 2003
2-27
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
EVENT TRACKING ACTIONS
By selecting option 5 on the Permit Administration Menu, the following menu screen will be displayed.
DATE : 04/01/94 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP353
SCREEN: 353 EVENT TRACKING ACTIONS MAP: AFM3531
*AFS PLANT ID (ST/CNTY/PLANT) : /
APPLICATION:
/ EPA ID:
PERMIT:
*ACTION TYPE:
EPA: STATE/LOCAL CONTROL
DATE ACHIEVED (YYYYMMDD) :
RESULTS CODE :
COMPLAINT ID :
ACTION DESCRIPTION .... :
*ACTION :
REGION : / COMMENT :
DATE SCHEDULED (YYYYMMDD) :
STAFF NAME :
ACTION DATA ELEMENTS . . : 1)
2)
3)
PF3=END PF4=MAIN MENU PF5=TERMINATE
PF9=REPEAT PF10=NEXT NEXT SCREEN: 060
FIGURE 2-25 EVENT TRACKING ACTIONS UPDATE SCREEN
Once an Application and/or Permit have been established in the database, events connected to the
Application or Permit can be tracked by using this screen. Valid action types are maintained on the AFS
EPA Action Table. You may input an action type '00' when the permit is a non-Title V private permit.
An additional screen may be displayed foragency notification information, depending on the action type
specified (See Figure 2-26). These action types indicate that agency notification is required.
To add an action, users must enter an AFS Plant ID, Application and/or permit, action type, action
number, ownership, and date scheduled or date achieved. All of the actions entered during the
application completeness determination must contain an application. All of the actions entered using
the review and approval of the draft permit must contain a permit and may contain an application. All
of the actions related to an issued permit must contain a permit.
Actions can be added using action number 001-998 or generated using 999.
Ownership is generated for certain action types after processing the EVENT TRACK ACTION screen(s)
if the user is authorized to update data for the designated permit authority.
Comments may be provided forthis action by typing any alphanumeric character in the comment field.
A comment screen will be displayed at the conclusion of processing the EVENT TRACK ACTION
scree n(s).
EVENT TRACKING ACTION COMMENTS
This screen will be displayed as a result of the users providing any alphanumeric character in the
comment field of the EVENT TRACKING ACTION Update screen (Figure 2-25).
April 2003
2-28
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/05/94 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP365
SCREEN: 365 EVENT TRACKING ACTION COMMENTS MAP: AFM3651
*AFS PLANT ID (ST/CNTY/PLANT) : / / EPA ID:
*APPLICATION: PERMIT:
*ACTION TYPE: - *ACTION:
EPA: STATE/LOCAL CONTROL REGION: / *COMMENT:
OWNER PRIVATE (Y/N) : N
PF3=END PF4=MAIN MENU PF5=TERMINATE PF9=REPEAT PF10=NEXT NEXT SCREEN: 060
FIGURE 2-26 EVENT TRACKING ACTION COMMENTS UPDATE SCREEN
EVENT TRACKING ACTION COMMENTS are optional.
The Event Tracking Action Comments screen allows the addition or update of comments which relate
to a particular event which may or may not be associated with a facility. This capability extends to users
who represent the Permitting Authority, the EPA, and Affected Agencies. Users may only update
comments owned by their agency.
The action must be previously established in the database.
Comments can be added using comment number 001 - 998 or generated using 999.
Ownership is generated for certain action types after processing the EVENT TRACK ACTION screen(s)
if the user is authorized to update data for the designated permit authority.
April 2003
2-29
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
FEES
By selecting option 11 on the Permit Administration Menu, the following menu screen FEES UPDATE
SCREEN will be displayed.
DATE : 04/01/94
SCREEN: 304
AIRS FACILITY SUBSYSTEM - UPDATE
FEE CERTIFICATION
PGM: AFP304
MAP: AFM3041
FEE STATUS
FEE CLASSIFICATION
CLASSIFICATION REASON - 1
FEE BILLING AMOUNT
FEE PENALTY AMOUNT
FEE STATUS CHANGE DATE(YYMMDD):
CLASSIFICATION REASON - 2 ... :
0000
0000
00
00
FEE BILLING DATE (YYMMDD)
FEE PENALTY DATE (YYMMDD)
FEE RECEIVED DATE (YYMMDD) :
FEE PAYMENT CHECK NUMBER :
FEE VOUCHER NUMBER :
FEE CERTIFICATION (INSPECTION) DATE (YYMMDD):
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
PRIVATE(Y/N): N
SCREEN: 060
FIGURE 2-27 FEE UPDATE SCREEN
The FEE CERTIFICATION update screen supports the updating of fee information to record monetary
information relating to plant permitting and compliance processes.
Values pertaining to Status and Classification are user-defined and State or County personnel may
specify this record to be private.
April 2003
2-30
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.1.6 Plant Mailing Label
The AFS Plant Mailing Label update screen supports the entry of plant mailing address data.
DATE : 04/01/94
SCREEN: 305
AIRS FACILITY SUBSYSTEM - UPDATE
MAILING LABEL INFORMATION
PGM: AFP305
MAP: AFM3051
YEAR OF EMISSIONS INVENTORY (YY):
*MAILING PLANT NAME :
*MAILING STREET ADDRESS .... :
*MAILING CITY NAME :
*MAILING STATE :
*MAILING ZIP CODE :
MAILING LABEL CODE :
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
SCREEN: 040
FIGURE 2-28 PLANT MAILING LABEL UPDATE SCREEN
To establish an optional Mailing Label Record, you must supply values for:
Mailing Plant Name
Mailing Street Address
Mailing City Name
Mailing State Abbreviation/Code
Mailing Zip Code
Mailing label data will be automatically provided if you answer affirmatively to the "Add Mailing Label"
prompt that appears when updating a Plant General record. When Plant General name and address
information is modified, you will be asked if you want the Mailing Label information updated to reflect the
Plant General modification. For a mailing address which differs from the actual location of the plant, you
should update the mailing label record accordingly.
April 2003
2-31
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.1.7 Plant Actions
The AFS Plant Actions update screen allows you to update scheduled and completed compliance
activities for at the plant. You must enter an action number with a value 1- 998 to identify the record in
the database. If the action number exists, the values forthe action record data elements are displayed
for you to update. For new records, entering this key datum will result in the display of a blank data
update screen.
DATE : 04/01/94
SCREEN: 306
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT ACTIONS
PGM: AFP306
MAP: AFM3061
KEY ACTION (Y/N):
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-29 PLANT ACTION KEY DATA SCREEN
Entering '999' in the Action Number field will prompt AFS to generate the next available sequential action
number for the plant.
Certain compliance actions (administrative penalty, consent decree, administrative order, violation, full
compliance evaluation) result in follow-up activities. AFS allows you to link these activities together. The
initiating action is called a 'Key' action. To designate an Action as a key action for action linking, specify
'Y' in the Key Action field. For more information on the usage of'Action Linking', see the Action Linking
User's Guide. A key action will be automatically generated when an action has an action type which
corresponds to one of these 9 National action types:
NH - Non-HPV Day Zero
2B - Shared Day Zero
2E - State Day Zero
2U - Unassigned Day Zero
2Z - Federal Day Zero
5E - EPA On-site FCE Pathway
5F - EPA Off-site FCE Pathway
5G - State/Local On-site FCE Pathway
5H - State/Local Off-site FCE Pathway
June 2006
On-Line Updating
2-32
-------
AFS User's Guide
AF3
AFS Data Storage
DATE ,:
•.
01.'23/0 ?
306
AISS FACILITY SUBSYSTEM
PLANT ACTIONS
TEST2 TIST PLANT
••ACTION: 003
UPDATE
MAPLE STClECT
KEY ACTION (Y/N):
PGM: AFP306
HAP; AFM3062
*AIR PROGRAM CODE IS) . . :
* ACT I OH TYPE :
ACTION DESCRIPTION ,,. :
OATE SCHEDULED (YYMMDO) •.
RESULTS . .
STAFF CODE
POLLUTANT CODE
CONTRACTOR 10 .
ROE 16
KEY ACT I ON (S):
ACTION TYPE CATEGORY
DATE ACHIEVED (YYMMOD)
PENALTY AMOUNT
SM 8
CHEMICAL ABSTRACT B ..
PRIVATE(Y/N): N
FIGURE 2-30 PLANT ACTION UPDATE SCREEN
The Plant Action update screen requires you to supply values for Air Program Code (minimum of 1,
maximum of 6), Action Type, and Date Scheduled or Date Achieved. Air programs must be defined at
the plant level prior to referencing them on actions.
If the Action Type does not correspond to a valid regional action type, State or County personnel must
specify this record to be private. If the record is not declared State-Private, invalid regional action types
will not be accepted. Key action types must be used when defining Key Actions, and will result in the
display of key action-specific update screens.
The most recent EPA and State Inspection Action Type and Date Achieved, based on Plant Actions,
are recorded and can be browsed on Plant General.
Some action types are obsolete, as flagged on the Action Table. New actions cannot be added with
obsolete action types. All fields on existing records with obsolete action types can be changed,
including changing an obsolete action type to a non-obsolete action type. An existing action type cannot
be changed to an obsolete action type.
For penalty amounts greaterthan 9,999,999, a"K", in the last position of this field may be entered. The
"K" used in this manner represents "thousands".
The pollutant code on a key action for a violation will automatically update the associated violating
pollutant codes.
January 2007
On-line Updating
2-33
-------
AFS User's Guide
AF3
AFS Data Storage
Use of the Action Description field is restricted to actions with an Action Type of "00" or those actions
designated as State-Private. The Action Description is otherwise generated from the Action Table.
Users without update sensitive data access will not be allowed to enter enforcement sensitive Action
Types or access enforcement sensitive action records.
DATE : 04/01/94 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP30603
SCREEN: 306 PLANT ACTIONS - CONSENT DECREE/ADMINISTRATIVE ORDER MAP: AFM3064
AIR PROGRAM CODE(S) : 0 STATE REGISTRATION NUMBER:
COMP STAT (EPA/ST) : / 3 CLASS: El STAFF: GOVT FACIL: 0 HPV:
LEAD AGENCY: VIOLATION IDENTIFIER: DOCUMENT NUMBER:
NEW ACTION
ACTION? NUMBER/TYPE
ACTION
DESCRIPTION
DATE
SCHED
DATE
ACHVD
PENALTY RESULTS
ST
PRIV
FED CON DCR ISS 940401 940401
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-31 PLANT ACTION - CONSENT DECREE/ADMINISTRATIVE ORDER
PATHWAY UPDATE SCREEN
The Plant Actions-Consent Decree/Administrative Order update screen is specific to the updating of
actions resulting from the issuance of a consent decree or administrative order against the facility. The
upper part of the screen displays air program and plant-level compliance information. The lower part
of the screen allows you to add or change actions linked to the original Key Action consent decree or
administrative order. For more information on 'Action Linking' functionality, refer the Action Linking
User's Guide.
The first action listed will be the key action itself.
April 2003
2-34
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 11/06/08
SCREEN: 306
TEST1 TEST HPV PLANT
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT ACTIONS - VIOLATIONS
TEST
AIR PROGRAM CODE(S) : V STATE REGISTRATION NUMBER:
COMP STAT (EPA/ST) : / B CLASS: A STAFF: GOVT FflCIL
LEAD AGENCY: F VIOLATION IDENTIFIER: F VIOLATING PLLTS: THfiP AB
VIOLATION TYPE CODE:
DAY 60: 021130 DAY 150
DAYS USED TO ADDRESS:
NEW ACTION
ACTION? NUMBER/TYPE
N 001 Jl
N 002 FE
N 003 TE
N 004 L5
N 019 AB
N 200 FF
DIS M2C
: 030301 DAY 270: 030629 DAY 300: 030729
0 UNADDRESSED DAYS: 999
ACTION DATE DATE PENALTY
DESCRIPTION SCHED ACHVD
FEDERAL DAY ZER 021001
EPA/ONSITE-EPA 020820
EPA RO STKT REV 020930
EPA NOV 021225
STTE NOV 070210
FCE/OFFSITE-ST 070101
PGM: AFP30604
MAP: AFM3065
: 0 HPV: E
RESULTS ST
PRIV
N
MV N
MV N
N
N
N
MORE
FIGURE 2-32 PLANT ACTION - VIOLATIONS
PATHWAY UPDATE SCREEN
The Plant Actions-Violations update screen is specific to the updating of actions resulting from the
designation of a plant as in violation.
The upper part of the screen displays air program, plant-level compliance and Day 60, 150, 270, and
300 and Days Used to Address information. The Days Used to Address and Unaddressed Days
calculations include actions that are resolved . This is because a pathway may not include an
addressed action; the pathway could go directly to being resolved from a Day Zero action. An
addressing action must be entered before a resolution action, except if the resolving action is National
Action Type '2K', 7G', 'C71 or "WD".
The lower part of the screen allows you to add or change actions linked to the original Key violation
Action. For more information on 'Action Linking' functionality, refer the Action Linking User's Guide.
The first action listed will be the key action itself.
When the user presses the ENTER key to save the data, system logic is performed to determine if a
Plant HPV record must be generated. A new Plant HPV record is generated if the calculation
determines that a violation exists that is worst than the current violation recorded on the Plant HPV
record.
The violating pollutants will be automatically updated as follows:
1.) If a new key action is added with a pollutant, the pollutant will be put in the Imposition of the violating
pollutant codes.
2.) If an existing pollutant on a key action is changed, the matching violating pollutant code will be
overlaid with the changed pollutant.
3.) If the existing pollutant on a key action is blanked out and subsequently replaced with a different
pollutant code, the pollutant code is inserted into an empty violating pollutant position or if all 3 positions
are filled, the pollutant overlays the existing violating pollutant in the 2nd position.
November 2008 On-Line Updating
2-35
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/06/94
SCREEN: 306
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT ACTIONS - ADMINISTRATIVE PENALTY
PGM: AFP30602
MAP: AFM3063
AIR PROGRAM CODE(S) : 0 STATE REGISTRATION NUMBER: AA0016C
COMP STAT (EPA/ST) : / 3 CLASS: B STAFF: GOVT FACIL: 0 HPV:
LEAD AGENCY: _ VIOLATION IDENTIFIER: _
VIOLATION TYPE CODE:
NEW ACTION
ACTION? NUMBER/TYPE
ACTION
DESCRIPTION
DATE
SCHED
DATE
ACHVD
PENALTY RESULTS
ST
PRIV
113D APO COMPL
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-33 PLANT ACTION -ADMINISTRATIVE PENALTY PATHWAY
UPDATE SCREEN
The Plant Actions-Administrative Penalty update screen is specific to the updating of actions resulting
from the issuance of an administrative penalty against the facility. The upper part of the screen displays
air program and plant-level compliance information. The lower part of the allows you to add or change
actions linked to the original Key Action administrative penalty.
The first action listed will be the key action itself. For more information on 'Action Linking' functionality,
refer the Action Linking User's Guide.
April 2003
2-36
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DflTE : 08/26/05
SCREEN: 306
flIRS FflCILITY SUBSYSTEM - UPDflTE
PLflNT flCTIONS - FCE PflTHUflY
PGM: flFP30605
MflP: flFM3066
TEST1 TEST 1 PLflNT
TEST 1 STREET
flIR PROGRflM CODECS) : Q STfiTE REGISTRRTION NUMBER:
COMP STflT (EPR/ST) : / 1 CLRSS: HI STRFF: GOVT FRCIL: 1 HPV: E
CMS SOURCE CATEGORY :
CMS MINIMUM FREQUENCY INDICRTOR :
NEy flCTION
flCTION? NUMBER/TYPE
flCTION
DESCRIPTION
DflTE DflTE RESULTS ST
SCHEDULED flCHIEVED PRIV
033 5E EPfl ONSITE PflTH 050826
MORE
FIGURE 2-33A PLANT ACTION - FCE PATHWAY UPDATE SCREEN
The Plant Actions - FCE Pathway update screen is specific to the updating of actions that lead to a full
compliance evaluation of a facility. The upper part of the screen displays air program, plant-level compliance,
CMS Source Category and the CMS Minimum Frequency Indicator information. The lower part of the screen
allows you to add or change actions linked to the original Key Action for the FCE pathway.
The first action listed will be the key action itself. For more information on 'Action Linking' functionality, referthe
Action Linking User's Guide.
2-36.1
April 2003
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.1.8 Plant Comments
The Plant Comments update screen supports the online addition of textual comments about the plant
or a plant action. For comments associated with the plant as a whole, you must supply a Comment
Number 1-998; for Plant Action Comments you must also enter an existing Action Number in the key
field. Plant Action Comments may only be added for existing Plant Actions. The entry of '999' in the
Comment Number field will result in the system automatically generating the next available sequential
plant comment number for the comment or plant action comment.
DATE : 04/01/94
SCREEN: 307
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT LEVEL COMMENTS
PGM: AFP307
MAP: AFM3071
*COMMENT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-34 PLANT COMMENTS KEY DATA SCREEN
Comment Numbers have an associated one position field identifying the comment as related to
compliance information, "C", or emissions information, "E". AFS automatically fills this field when adding
comments for compliance or emissions-only plants, or for users with update access to only compliance
or emissions information. Users with update access to both compliance and emissions information must
identify the comment as being either emissions or compliance related when updating associated/merged
plants.
April 2003
2-38
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 05/31/95 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP307
SCREEN: 307 PLANT LEVEL COMMENTS MAP: AFM3072
ACTION :
YEAR OF EMISSIONS INVENTORY (YY) :
COMMENT # 001 C :
ENFORCEMENT SENSITIVE (Y/N) :
PRIVATE (Y/N) :
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN:
N
N
040
FIGURE 2-35 PLANT COMMENTS UPDATE SCREEN
Comments consist of 240 characters arranged over four, sixty-character lines. Plant level comments
may be declared State-Private, but only compliance comments may be designated as enforcement
sensitive.
You may provide as many as 998 comments for a plant and 998 comments for a plant action but
remember, as with all other written communication, "Brevity is the soul of wit".
April 2003
2-39
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.1.9 Plant Asbestos Information
The Asbestos Information Menu provides asbestos topics to support the entry of data pertaining to
asbestos renovation/demolition, contractors performance at the facility and asbestos disposal and
landfills. Compliance update access is required to address asbestos information.
When selecting to update Asbestos Information, you will be presented with a menu screen and may
choose to update the following data:
DATE : 04/01/94
SCREEN: 042
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS INFORMATION
PGM: AFP042
MAP: AFM0421
1 CONTRACTOR INFORMATION (308)
2 LANDFILL INFORMATION (309)
3 PERFORMANCE INFORMATION (310)
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
FIGURE 2-36 PLANT ASBESTOS UPDATE MENU
CONTRACTOR INFORMATION
Data pertaining to asbestos
Renovation/Demolition contractors
LANDFILL INFORMATION Data pertaining to EPA certified asbestos landfills
PERFORMANCE INFORMATION Data pertaining to Renovation/Demolition activities at a facility
When a Contractor ID, Contractor or Landfill name search are selected in the Identification screen
(Figure 2-2) you are presented with the Asbestos Information Menu. When a Landfill ID is entered on
the Identification screen, the Plant Asbestos Update Menu is bypassed and you are taken directly to the
Asbestos Landfill Information screen (Figure 2-39).
April 2003
2-40
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 308
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS CONTRACTOR INFORMATION
PGM: AFP308
MAP: AFM3081
CONTRACTOR ID: LA -
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-37 ASBESTOS CONTRACTOR KEY DATA SCREEN
The Asbestos Contractor Information update screen supports the tracking of asbestos
renovation/demolition contractors and their certification status within their states of operation. You must
enter a unique contractor State Identification Number, prefixed by a State Code, to identify the record
in the database. The state code is prefilled with the state code selection on the Identification screen
(Figure 2-2). The state code value may be changed on the key data screen to target different contractor
information.
April 2003
2-41
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 308
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS CONTRACTOR INFORMATION
PGM: AFP308
MAP: AFM3082
CONTRACTOR ID:
*CONTRACTOR NAME ...
*STREET ADDRESS ....
*CITY
COUNTY CODE
*STATE ABBREVIATION
CONTRACTOR COMPLIANCE STATUS:
NATIONAL CONTRACTOR ID .
DUN & BRADSTREET NUMBER
LISTING (YYMMDD)
CERTIFICATION (YYMMDD).
METHOD CODE
EPA REGION .
DELISTING (YYMMDD) .... :
DECERTIFICATION (YYMMDD):
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 042
FIGURE 2-38 ASBESTOS CONTRACTOR UPDATE SCREEN
When an existing key data combination is input, the values for the remaining data elements are
displayed for you to update. For new records, entering these key data will result in the display of a blank
data update screen.
April 2003
2-42
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 309
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS LANDFILL INFORMATION
PGM: AFP309
MAP: AFM3091
*LANDFILL EPA ID:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-39 ASBESTOS LANDFILL KEY DATA SCREEN
The AFS Asbestos Landfill update screen allows you to add landfills where asbestos has been
deposited. You mustentera landfill identification numberto identify the record in the database. Landfill
ID's are unique nationwide.
For existing records, the entry of the Landfill ID will result in the display of the existing landfill record
data. When entering a new Landfill ID, a blank data update screen will be displayed.
All landfills referenced in contractor performance records must be previously defined in the database
or they can not be accepted in the performance record.
April 2003
2-43
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/01/94
SCREEN: 309
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS LANDFILL INFORMATION
PGM: AFP309
MAP: AFM3092
*LANDFILL EPA ID:
*LANDFILL NAME :
*STREET ADDRESS:
*CITY :
*STATE :
*ZIP CODE .... :
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 042
FIGURE 2-40 ASBESTOS LANDFILL UPDATE SCREEN
The Asbestos Landfill update screen requires you to supply:
Landfill Name
Landfill Street Address
City Name
State Abbreviation or State Code
Zip Code
April 2003
2-44
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The AFS asbestos performance update screen allows you to identify an AFS facility, an asbestos
renovation/demolition contractor, and the performance of reno/demo work at the plant.
DATE : 04/01/94
SCREEN: 310
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS PERFORMANCE
PGM: AFP310
MAP: AFM3101
CONTRACTOR ID: LA -
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-41 ASBESTOS PERFORMANCE KEY DATA SCREEN
Each Asbestos Performance screen requires you to enter an existing AFS plant ID and an existing
contractor ID. To isolate a specific location within a plant where reno/demo work was performed, you
may also specify an existing AFS compliance point ID. For existing records, the entry of the key data
will result in the display of the existing asbestos performance record data. When entering new key data,
a blank data update screen will be displayed.
April 2003
2-45
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
This screen supports the updating of data pertaining to a contractor's asbestos reno/demo removal and
disposal activities at a facility.
DATE : 04/01/94
SCREEN: 310
AIRS FACILITY SUBSYSTEM - UPDATE
ASBESTOS PERFORMANCE
PGM: AFP310
MAP: AFM3102
CONTRACTOR ID:
BUILDING OWNER/OPER.:
STREET ADDRESS:
CITY :
CONTRACTOR OWNER/OPER
ASBESTOS 0000000 LIN
REMOVED
FT.(PIPING) METHOD CODE(S)
0000000 SQ. FT.(SURFACE) METHOD(Z) DESC
0000000 CUB. FT.(VOLUME)
DISPOSAL SITE UNKNOWN (Y/N):
LANDFILL EPA IDS
UNAUTHORIZED
LANDFILL :
STREET .. : _
CITY .... : _
STATE ... :
ZIP CODE:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 042
FIGURE 2-42 ASBESTOS PERFORMANCE UPDATE SCREEN
The plant, contractor, and landfill EPA IDs must be already be established in AFS before they can be
referenced in this screen.
The building owner address represents the address of the owner or operator of the facility where asbestos
Demolition/Renovation activities are being performed.
AFS also automatically creates asbestos contractor performance records whenever an asbestos contractor
Identification Number is included in the action data. These system created records are generated to
support faster Ad Hoc reporting retrievals of asbestos contractor performance at a given facility.
April 2003
2-46
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.1.10 Plant High Priority Violator Utility
The Plant High Priority Violator Utility supports the entry of plant high priority violator information. The
12 HPV Flags are displayed in order from group 1 through group 12 as they are stored on the AFSS-
PLANT-HPV table record. The flags are stored on the record by order of addition to the record, with the
most recent entry first.
DATE : 09/09/99
SCREEN: 314
AIRS FACILITY SUBSYSTEM - UPDATE
PLANT HIGH PRIORITY VIOLATOR UPDATE UTILITY
PGM: AFP314
MAP: AFM3141
AIR PROGRAM CODES:
STATE COMPL STAT:
EPA COMPL STAT:
FLAG ENTER HIGH PRIORITY VIOLATOR FLAG AND EFFECTIVE DATE OF ACTIVITY:
POS HPV DESCRIPTION EFFECT DATE ACTION DATE MOD USER SOURCE
1
2
3
4
5
6
7
8
9
10
11
12
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=NEW PF10=SCRN PF11=RECALC SCREEN:
FIGURE 2-42.1 PLANT HIGH PRIORITY VIOLATOR UPDATE UTILITY SCREEN
The HPV Flag, HPV Effective Date and HPV Action Numberfields may be modified on any flag line item
displayed. When the record is updated to the database, the flag line item is updated on the record with
the User ID of the person making the update, the current system date and "U" for HPV-FLAG-SOURCE
(indicating that the user updated the flag manually).
The PF9 key is available for adding a new flag. When PF9 is pressed, a pop-up window is displayed
with the HPV Flag, HPV Effective Date, and HPV Action Number fields available for entry. When
ENTER is pressed in the pop-up window, the HPV Update Utility screen is redisplayed. The newly
entered flag is placed on the first line of the screen and all previous flag line items are shifted down a
position. For example: previous position 1 becomes position 2, previous position 2 becomes position
3, etc., and previous position 12 values are deleted. When the record is updated to the database, the
flag line item is updated on the record with the User ID of the person making the update, the current
system date and "U" for HPV-FLAG-SOURCE indicating that the user updated the flag manually.
Blanking out the HPV Flag field and the HPV Effective Date fields results in the deletion of the entire line
of data. Both fields must be blanktotriggerthe deletion of the remaining data on the line. The gap that
the deleted flag leaves on the record is corrected by repositioning the HPV Flags from the subsequent
lines. The user can cancel the deletion of a flag by pressing the PF3 function key.
Users may modify data on a line(s), delete data on a line(s), and then add a line of data in one session
of the screen.
A user can invoke the recalculation of the current HPV Flag for a plant by pressing the PF11 function
April 2003 2-44.1 On-Line Updating
-------
AFS User's Guide
AF3 AFS Data Storage
key. This is used primarily to "turn on" flag generation for a plant for which the automatic generation logic
is not being invoked because the Flag Source value of the current HPVflag is "U" (user generated). It
can also be used at any time to recalculate the HPVFlag if there is a need or if one wishes to verify the
current calculations provided by the system. The result of the recalculation is to generate the most
current HPVFlag value with a Flag Source of "S" (system generated). If there are no Day Zero action
linked data for the plant resulting in no HPV Flag being generation, a message window is displayed
indicating" A RECALCULATION CANNOT BE PERFORMED BECAUSE NO VIOLATION PATHWAYS
COULD BE FOUND."
When the value of the current HPV Flag is changed, this activity will be recorded to the CDE file.
April 2003 2-45 On-Line Updating
-------
AFS User's Guide
AF3 AFS Data Storage
2.3.1.11 Compliance Monitoring Strategy (CMS)
The Compliance Monitoring Strategy update screen allows you to update CMS related fields. CMS data
forms the basis for planning, implementing and evaluating stationary source air compliance monitoring
programs. AFS supports the data collection activities associated with identifying facilities and
conducting full compliance evaluations.
DATE : 09/20/01 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP315
SCREEN: 315 COMPLIANCE MONITORING STRATEGY MAP: AFM3151
10000 TEST PLANT 123 TEST DRIVE
(2001/09/17-JH1 )
CMS SOURCE CATEGORY: A
CMS MINIMUM FREQUENCY INDICATOR: 6
PLANNED YEAR(S) OF FULL COMPLIANCE EVALUATION (FCE):
FISCAL YEAR A: ON-SITE VISIT PLANNED (Y/N): _
FISCAL YEAR B: 2011 ON-SITE VISIT PLANNED (Y/N): Y
FISCAL YEAR C: 2012 ON-SITE VISIT PLANNED (Y/N): N
FISCAL YEAR D: 2015 ON-SITE VISIT PLANNED (Y/N): Y
FISCAL YEAR E: 2020 ON-SITE VISIT PLANNED (Y/N): N
COMMENT: ROBS TEST COMMENT
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN SCREEN:
FIGURE 2-42.2 PLANT COMPLIANCE MONITORING STRATEGY UPDATE SCREEN
When a CMS source category code is entered, the associated minimum frequency indicator must be
entered. The source category identifies the CMS facility and the minimum frequency indicator indicates
the number of years allowed between full compliance evaluations.
Update access to the CMS screen is restricted to those users with compliance access to the geographic
area where the facilitity is located and have a special access code of'S' in their security profile.
April 2003 2-46 On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.2 AFS Stack Update Menu
Stack level data is optional information. However, AFS supports the on-line updating of three stack level
record types if desired.
DATE : 03/31/94
SCREEN: 044
AIRS FACILITY SUBSYSTEM - UPDATE
STACK INFORMATION
1 GENERAL INFORMATION (320)
2 POLLUTANT INFORMATION (321)
3 COMMENTS (322)
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
PGM: AFP044
MAP: AFM0441
FIGURE 2-43 AFS STACK LEVEL UPDATE MENU
GENERAL INFORMATION Stack descriptive data
POLLUTANT INFORMATION Stack pollutant emissions data
COMMENTS Text comments pertaining to stacks or stack activities
Only users with update access for emissions data may update Stack General data. Compliance users
may update Stack Pollutant with compliance emission types for existing stacks on associated facilities.
To select a particular record to update, type in the desired option number and press . The
next screen presented will be the key information screen for the option selected.
Each of the three Stack level update records are described individually in the following sections.
April 2003
2-47
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.2.1 Stack General
The Update General Stack Information screen supports the updating of general stack descriptive data.
You must identify a stack by entering a unique Stack Number, 1-998. The entry of'999' in the Stack
Number field will result in the system automatically generating the next available sequential stack
number.
DATE : 04/01/94
SCREEN: 320
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL STACK INFORMATION
PGM: AFP320
MAP: AFM3201
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-44 AFS STACK KEY DATA SCREEN
April 2003
2-48
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
For existing records, the entry of the key data will result in the display of all associated record data.
When entering new key data, a blank data update screen will be displayed.
DATE : 04/01/94
SCREEN: 320
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL STACK INFORMATION
PGM: AFP320
MAP: AFM3202
*STACK:
YEAR OF EMISSIONS INVENTORY (YY):
STACK HEIGHT (FT) :
EXIT GAS TEMPERATURE (F) : 0000
EXIT GAS VELOCITY (FT/SEC) : 000 .
PLUME HEIGHT (FT) :
STACK TYPE CODE : _
STACK DESCRIPTION :
STACK DIAMETER (FT)
GAS FLOW RATE (ACFM) ...
EMISSION RECORDER
STACK LINING
ROUGH TERRAIN INDICATOR
UTM HORIZ COORD (KM)
LATITUDE (DDMMSS) ..
000
00 :
. 00
00 :
UTM VERT COORD (KM)
00 LONGITUDE (DDDMMSS)
0000
000 :
. 00
00 :
G.E.P. STACK HEIGHT (FT) :
G.E.P. BUILDING LENGTH (FT):
0000
0000
G.E.P. BUILDING HEIGHT (FT) : 0000
G.E.P. BUILDING WIDTH (FT) : 0000
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 044
FIGURE 2-45 AFS STACK GENERAL UPDATE SCREEN
The Stack General update screen requires you to enter Stack Height and Stack Diameter and/or Plume
Height.
You may use either UTM coordinates or Latitude-Longitude coordinates to identify a stack location.
Latitude and Longitude coordinates are generated if UTM coordinates are supplied, and vice-versa. A
UTM Zone will be generated from stack UTM coordinates and stored at the plant level if one does not
already exist.
If the stack is already included in a frozen AFS SIP Inventory and has stack pollutant records for SIP
inventory pollutants, data in the following fields will be display only:
Stack Height
Plume Height
Latitude Coordinate
UTM Horizontal Coordinate
Stack Exit Gas Temperature
Stack Exit Gas Velocity
Stack Diameter
Longitude Coordinate
UTM Vertical Coordinate
Stack Gas Flow Rate
2.3.2.2 Stack Pollutant
April 2003
2-49
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Stack Pollutant update screen allows you to update pollutant data for stack pollutant emissions
types. You must enter a stack number and either a Pollutant Code or a Chemical Abstract Service
Number to identify the record in AFS.
DATE : 04/01/94
SCREEN: 321
AIRS FACILITY SUBSYSTEM - UPDATE
STACK POLLUTANT INFORMATION
PGM: AFP321
MAP: AFM3211
INV YEAR:
POLLUTANT CODE:
CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-46 AFS STACK POLLUTANT KEY DATA SCREEN
For existing records, the entry of the key data will result in the display of all current record data. When
entering new key data, a blank data update screen will be displayed.
April 2003
2-50
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 11/23/94
SCREEN: 321
AIRS FACILITY SUBSYSTEM - UPDATE
STACK POLLUTANT INFORMATION
PGM: AFP321
MAP: AFM3212
POLLUTANT CODE:
INV YEAR:
CHEMICAL ABSTRACT #:
EMISSIONS
TYPE VALUE
UNIT METHOD
EMISSIONS
TYPE VALUE
UNIT METHOD
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 044
FIGURE 2-47 AFS STACK POLLUTANT DATA UPDATE SCREEN
Depending upon your update access profile and the merge status of the facility, your update screen will
allow update access to either compliance only, emissions only or merged stack emissions types.
For associated plants, users authorized to address both emissions and compliance information may
enter data for one or more of the following pollutant emission types: Measured, Allowable, Potential
Controlled, Potential Uncontrolled, Actual Uncontrolled.
For associated plants, users authorized to address only compliance information may update data for
one or more of the following pollutant emission types: Allowable, Potential Controlled, Potential
Uncontrolled, Actual Uncontrolled.
Users authorized to address only emissions information may enter data for the Measured emissions
type.
You must supply an Emissions Value, Unit Code, and a Method Code (for measured or actual
uncontrolled emissions) for each Emissions Type entered. The emissions value supports the entry of
a floating decimal point. The use of a Method Code of'1' for Actual Uncontrolled emissions will result
in the system bubbling up segment level emissions values for this emissions type.
The Year of Inventory entered when you first identified the plant for updating is applied to all emissions
community emissions types updated on the stack pollutant screen. The present year is applied to
compliance emissions types.
If the pollutant specified is not a federally regulated pollutant, State personnel may specify this record
to be State-Private.
April 2003
2-51
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.2.3 Stack Comment
The Stack Comments update screen supports the online addition of textual comments about the stack.
You must enter an existing stack number and a comment number 1 -998 to update a record. The entry
of'999' in the Comment Numberfield will result in the system automatically generating the next available
sequential stack comment number for the stack comment.
DATE : 04/01/94
SCREEN: 322
AIRS FACILITY SUBSYSTEM - UPDATE
STACK LEVEL COMMENTS
PGM: AFP322
MAP: AFM3221
*COMMENT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-48 AFS STACK COMMENT KEY DATA SCREEN
Comment Numbers have an associated one position field identifying the comment as related to
compliance information, "C",oremissions information, "E". AFS automatically fills this field when adding
comments for compliance or emissions-only plants, or for users with update access to only compliance
or emissions information. Users with update access to both compliance and emissions information
must identify the comment as being either emissions or compliance related when updating associated
plants.
April 2003
2-52
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
Comments consist of 240 characters arranged over four, sixty-character lines. Stack level comments
may be declared State-Private, but only compliance comments may be designated as enforcement
sensitive.
You may provide as many as 998 comments for a stack.
DATE : 05/31/95
SCREEN: 322
*STACK:
YEAR OF EMISSIONS
COMMENT # 001 C :
PF1=HELP PF3=END
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP322
STACK LEVEL COMMENTS MAP: AFM3222
INVENTORY (YY) :
ENFORCEMENT SENSITIVE (Y/N) : N
PRIVATE (Y/N) : N
PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 044
FIGURE 2-49 AFS STACK COMMENT UPDATE SCREEN
April 2003
2-53
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3 AFS Point Level Update Menu
The Update Point Information menu provides access to the point level data update screens. AFS
supports Point level compliance and emissions information for both compliance related points and
emission related points. Selecting option 3 on the AFS Update Menu (FIGURE 2-8) will cause the
following menu to be displayed.
DATE : 12/15/97
SCREEN: 046
AIRS FACILITY SUBSYSTEM - UPDATE
POINT INFORMATION
1 GENERAL INFORMATION (330)
2 POLLUTANT INFORMATION (331)
3 AIR PROGRAMS (332)
4 MONITOR INFORMATION (333)
5 CONTINUOUS EMISSIONS (334)
6 TANK INFORMATION (335)
7 ACTIONS (336)
8 COMMENTS (337)
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
PGM: AFP046
MAP: AFM0461
FIGURE 2-50 AFS POINT LEVEL UPDATE MENU
GENERAL INFORMATION
POLLUTANT INFORMATION
AIR PROGRAMS
MONITOR INFORMATION
CONTINUOUS EMISSIONS
TANK INFORMATION
ACTIONS
COMMENTS
General descriptive information about the point
Point pollutant emissions by emission type
Point compliance profile by regulatory program type
Data on continuous emission monitors at the point
Quarterly point continuous emissions monitoring exceedance data
Descriptive data for points that are tanks
Regulatory actions applied to the point
Comment text applicable to the point, point monitors, point excess
emissions reports or point actions
Only users with update access for compliance data may update air programs, monitor, continuous
emissions and action point data.
To select a particular record to update, type in the desired option number and . The next
screen presented will be the key information screen for the option selected.
April 2003
2-54
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
Each of the eight Point level update records are described individually in the following sections.
2.3.3.1 Point General
The AFS General Point Information update screen supports the updating of general description and
operating data about compliance and emissions points within a facility.
DATE : 04/01/94
SCREEN: 330
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL POINT INFORMATION
PGM: AFP330
MAP: AFM3301
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-51 AFS POINT GENERAL KEY DATA SCREEN
You must enter a point number to update a General Point Information record. Point numbers may be
alphanumeric. For existing records, the entry of this key datum will result in the display of all associated
record data. When entering a new point number, a blank data update screen will be displayed. The data
screen will differ depending on your update access status or the emissions-only, compliance-only or
merged configuration of your plant or point.
Point numbers have an associated one position field identifying the points as related to compliance
information, "C", emissions information, "E" or both compliance and emissions information, "M"
(merged). AFS automatically fills this field when adding points for compliance or emissions-only plants,
or for users with update access to only compliance or emissions information. Users with update access
to both compliance and emissions information must identify the point as being either emissions,
compliance or merged related when updating merged or associated plants.
An identifier of "M" may only be specified to update compliance and emissions information on merged
facilities.
April 2003
2-55
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 06/15/95
SCREEN: 330
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL POINT INFORMATION - COMPLIANCE
PGM: AFP330
MAP: AFM3302
*POINT DESCRIPTION
STATE SENSITIVE INDICATOR
DESIGN CAPACITY
OPERATING RESTRICTION
DESIGN CAPACITY UNITS:
REGULATED SOURCE CLASSIFICATION CODE:
SOOT BLOWING INDICATOR (Y/N) :
TIMES PER DAY
TIMES PER WEEK
AM OR PM
00
00
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 046
FIGURE 2-52 AFS POINT GENERAL UPDATE SCREEN
COMPLIANCE POINT
This screen is displayed for users updating an unmerged compliance point. Users adding a point are
required to supply a point description.
Compliance points which remain unmerged possess fields for Design Capacity and Design Capacity
Units. Compliance users with update sensitive access can assign State sensitive status to Design
Capacity and Design Capacity Units by entering 'Y' in the State Sensitive Indicator. Refer to section
1.8.4 Sensitive Data for additional information.
This next screen supports emissions update users in the update of emissions data on emissions-only
points. All data fields on this screen are optional. Emissions users can assign State sensitive status
to Design Capacity, Design Capacity Units, and Space Heat by entering 'Y' in the State Sensitive
Indicator.
April 2003
2-56
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 06/15/95
SCREEN: 330
AIRS FACILITY SUBSYSTEM -
GENERAL POINT INFORMATION -
UPDATE
EMISSIONS
PGM: AFP330
MAP: AFM3304
*POINT: 001
YEAR OF EMISSIONS INVENTORY (YY):
STATE SENSITIVE INDICATOR : _
DESIGN CAPACITY : 00000
PERCENTAGE ANNUAL THRUPUT :
NORMAL OPERATING SCHEDULE :
CONTROL REGULATION :
BURNER TYPE - MAKE :
INSTALLATION DATE (YYMMDD):
DRAFT TYPE :
DRAFT CONTROL LOCATION .. :
SPACE-HEAT(PERCENT) :
DESIGN CAPACITY UNITS:
DEC - FEE ... : 00
JUN - AUG ... : 00
HOURS PER DAY : 00
HOURS PER YEAR: 0000
/ USER POINT ID
BURNER TYPE -
00 . 0
MAR - MAY ..
SEP - NOV ..
DAYS PER WEEK
00
00
0
DRAFT CONTROL TYPE
SDE 2 : SDE
SDE 4
SDE 5
POINT DESCRIPTION
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-53 AFS POINT GENERAL UPDATE SCREEN
EMISSIONS POINT
If the display of 'More' is in the lower right corner, this indicates that an additional data 'page' will be
displayed upon completion of data updating on this screen.
If the point is included in a 'frozen' SIP Inventory and the point has point pollutant records for the SIP
Inventory pollutants, the following fields will be display-only:
Percent Annual Thruput:
Dec-Feb
Mar-May
Jun-Aug
Sep-Nov
Normal Operating Hours Per Day
Normal Operating Days Per Week
Normal Operating Hours Per Year
For 'unfrozen' SIP inventory facilities, modifications to the seasonal throughput (Dec-Feb for CO and
Jun-Aug for Ozone) or the operating parameter fields will initiate a recalculation of the Peak CO and/or
Ozone Season Daily Process Rate, if the process rate was system-calculated and not user input.
April 2003
2-57
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The next screen (figure 2-54) is the first of two screens displayed for users updating a merged point.
The first screen is the same as the compliance screen (figure 2-52) except that the design capacity and
design capacity units fields have been removed because they may be updated on the emissions screen
(Figure 2-53,) displayed second.
DATE : 07/01/94
SCREEN: 330
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL POINT INFORMATION - COMPLIANCE
PGM: AFP330
MAP: AFM3303
*POINT: _
YEAR OF EMISSIONS INVENTORY (YY):
*POINT DESCRIPTION :
OPERATING RESTRICTION :
REGULATED SOURCE CLASSIFICATION CODE:
SOOT BLOWING INDICATOR (Y/N) :
TIMES PER DAY
TIMES PER WEEK
AM OR PM
00
00
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-54 AFS POINT GENERAL UPDATE SCREEN
MERGED POINT
To establish a merged point, the facility must be associated and the State must have undergone "Direct Data
Merging." This screen will not be presented if you do not have access to merged data.
The Point Description is mandatory. After completing the emissions Point General Screen (figure 2-53,) AFS
will take you to the Segment General Screen to enter the mandatory requirements.
April 2003
2-58
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 04/07/94
SCREEN: 330
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP330
GENERAL POINT INFORMATION - EMISSIONS MAP: AFM3305
OPERATION START TIME (HHMM)
OPERATION END TIME (HHMM)
SCREEN: 340
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-55 AFS POINT GENERAL UPDATE SCREEN
'EMISSIONS PAGE 2'
It is mandatory that at least one Segment general record be attached to each Emissions Point. Upon
the successful completion of a new POINT GENERAL EMISSION POINT, AFS will automatically take
the user to a Segment General update screen (FIGURE 2-75). This is required without regard to the
SIP Inventory status.
SIP update access is required to address these fields on facilities included in a SIP inventory.
If the facility is included in a frozen SIP Inventory and the point has point pollutant records forthe frozen
SIP Inventory pollutants, the fields on this screen will be display-only. SIP inventory data are frozen,
not updatable, when the SIP inventory has been submitted for review and remains frozen once the
inventory has been approved by EPA headquarters. To modify frozen SIP inventory data, the inventory
must be disapproved by EPA. The status of SIP inventories is maintained using the SIP Inventory
Utility.
April 2003
2-59
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.2 Point Pollutant
The Point Pollutant update screen supports the updating of pollutant data for point emissions types.
You must enter an existing point number and either a Pollutant Code or a Chemical Abstract Service
Number to identify the record in AFS.
DATE : 04/01/94
SCREEN: 331
* POINT:
POLLUTANT CODE:
PF1=HELP PF3=END
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP331
POINT POLLUTANT INFORMATION MAP: AFM3311
INV YEAR:
CHEMICAL ABSTRACT #:
PF4=MAIN PF5=TERM PF10=SCRN SCREEN:
FIGURE 2-56 POINT POLLUTANT KEY DATA SCREEN
For existing records, the entry of the key data will result in the display of all associated record data.
When entering new key data, a blank data update screen will be displayed.
Depending upon your update access profile and the merge status of the facility, your update screen will
allow update access to either compliance only, emissions only or merged point emissions types.
April 2003
2-60
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 03/08/95
SCREEN: 331
AIRS FACILITY SUBSYSTEM - UPDATE
POINT POLLUTANT INFORMATION
PGM: AFP331
MAP: AFM3312
INV YEAR:
*POINT: _
POLLUTANT CODE:
CHEMICAL ABSTRACT #:
EMISSIONS
TYPE VALUE
UNIT METHOD
EMISSIONS
TYPE VALUE
UNIT METHOD
STATE REGULATION
PRIVATE(Y/N): N
SCREEN: 046
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-57 POINT POLLUTANT UPDATE SCREEN
For associated/merged points, users authorized to address both emissions and compliance information
may update one or more types of pollutant emissions: Measured, State Defined, Emission Limitation,
Allowable, Potential Controlled, Potential Uncontrolled, Actual Uncontrolled.
For compliance points or merged points, users authorized to address only compliance information may
enter data for one or more of the following emissions types: Allowable, Potential Controlled, Potential
Uncontrolled, Actual Uncontrolled.
Users authorized to address only emissions information may enterdata forthe Measured, State Defined
and/or Emission Limitation emissions types. If the pollutant is included in a SIP inventory, SIP access
is required to enterdata forthe Emission Limitation emission type.
The State Regulation field will only be displayed on the screen to users with Compliance Update access
on Compliance only or associated facilities.
You must supply an Emissions Value, Unit Code, and Method Code for each Emissions Type entered.
Method Code only applies to Measured and Actual Uncontrolled Emissions. The emissions value
supports the entry of a floating decimal point. The use of a Method Code of '1' for Actual Uncontrolled
emissions will result in the bubbling up segment level Actual Uncontrolled emissions.
April 2003
2-61
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.3 Point Air Programs
The AFS Point Air Programs update screen is used to identify the regulatory programs to which the point
is subject. You must enter an existing point ID and valid air program to update a Point Air Programs
record. The air program provided for the point must exist at the plant level. Point Air Program records
must exist if users plan on adding , Excess Emission Reports or Actions to the point.
DATE : 04/01/94
SCREEN: 332
AIRS FACILITY SUBSYSTEM - UPDATE
POINT AIR PROGRAMS
PGM: AFP332
MAP: AFM3321
*AIR PROGRAM CODE:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-58 POINT AIR PROGRAMS KEY DATA SCREEN
For existing records, the entry of the key data will result in the display of all associated record data.
When entering new key data, a blank data update screen will be displayed.
April 2003
2-62
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Air Programs update screen requires you to supply a State Compliance and Air Program
Status.
DATE : 04/01/94
SCREEN: 332
AIRS FACILITY SUBSYSTEM - UPDATE
POINT AIR PROGRAMS
PGM: AFP332
MAP: AFM3322
*AIR PROGRAM CODE:
*STATE COMPLIANCE STATUS
*AIR PROGRAM STATUS
RDE 7
POLLUTANT CODE
EPA COMPLIANCE STATUS .. :
STATE IMPLEMENTATION PLAN:
RDE 15 :
CHEMICAL ABSTRACT # .... :
SCREEN: 046
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-59 POINT AIR PROGRAMS UPDATE SCREEN
Users with compliance update access may enterdata in the State Compliance and Air Program Status
fields. Should EPA differ in their assessment of the State Compliance Status, they should enter their
status determination in the EPA Compliance Status.
Unlike Plant Air Program Compliance Status data, point level data are not assessed for a worst case
scenario, nor is a worst case compliance status value applied to the point as a whole.
April 2003
2-63
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The label "More" in the lower right hand corner of the Plant Air Programs Update screen indicates there
is an additional "page" of information (Figure 2-59.1) forthe screen. The additional page of information
will be displayed to allow the entry of up to nine subpart values when updating Air Programs: "9" -
NSPS; "8" - NESHAP ; "M" - MACT NESHAP; "0" - SIP SOURCE; and "1" - SIP SOURCE UNDER
FEDERAL JURISDICTION. The subpart information pertains to sections 60, 61 and 63 of the Code of
Federal Regulations respectively.
40 CFR PART 60 (NSPS) SUBPARTS
SCREEN: 046
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-59.1 SUBPARTS 'PAGE1 OF POINT AIR PROGRAMS
Additionally, point data are not considered when determining plant values.
April 2003
2-64
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.4 Point Monitor
The AFS Point Monitor update screen supports users in the tracking of manufacturer, installation and
performance data associated with continuous emission monitoring devices.
Point Monitor records require that you enter a Point ID, and a Channel Number. For existing records,
the entry of the key data will result in the display of all associated record data. When entering new key
data, a blank data update screen will be displayed.
The first position of a Channel Number must correspond to a valid parameter code, which represents
the pollutant type being monitored. The second position for a Point Monitor channel number must be
a "I', which indicates the channel number pertains to a Point Monitor record (as opposed to continuous
emissions record ). The third character is used to indicate whether the monitor is a single monitor for
an emissions point (as indicated by a '1'), or one of a clustered group of monitors (as indicated by '2'
through '9').
DATE : 04/01/94
SCREEN: 333
AIRS FACILITY SUBSYSTEM - UPDATE
POINT MONITOR INFORMATION
PGM: AFP333
MAP: AFM3331
*CHANNEL #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-60 POINT MONITOR KEY DATA SCREEN
April 2003
2-65
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Monitors update screen requires you to provide a Monitor Requirement Code.
AFS keeps track of the Performance Specification Test values you enter for a Point Monitor record as
you update the record with the most current test status. The system will increment the number of Tests
and the number of Passes or Failures whenever the date and result of a Specification Test is modified.
The total number of tests, number of passes, and number of failures is displayed in the Point Monitor
Browse screen for the specific monitor record.
If you supply a date for a Specification Test, you will be required to enter a valid test status.
DATE : 04/01/94
SCREEN: 333
AIRS FACILITY SUBSYSTEM -
POINT MONITOR INFORMATION
PGM: AFP333
MAP: AFM3332
*CHANNEL #:
MONITOR MANUFACTURER .
MONITOR MODEL NUMBER .
MONITOR SERIAL NUMBER
*MONITOR REQUIREMENT CODE : _
PERMISSIBLE EMISSION LIMIT :
INSTALLATION DATE (YYMM) :
PERFORMANCE SPECIFICATION TEST DATE (YYMM):
PERFORMANCE SPECIFICATION TEST STATUS ... :
CERTIFICATION DATE (YYMMDD) :
CEM ENFORCEMENT AGENCY
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 046
FIGURE 2-61 POINT MONITOR UPDATE SCREEN
April 2003
2-66
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.5 Point Continuous Emissions
The AFS Continuous Emissions Update screen supports users in the tracking of quarterly excess
emissions reports submitted by the facility.
Continuous Emissions records, also referred to as Excess Emissions Report (EER) records, require you
to enter a Point ID, Channel Number, and a Reporting Quarter. For existing records, the entry of the
key data will result in the display of all associated record data. When entering new key data, a blank
data update screen will be displayed.
The first position of a Channel Number must correspond to a valid parameter code, which represents
the pollutant type being monitored. The second position for a EER channel number must be a'9', which
indicates the channel number pertains to an EER record (as opposed to an Point Monitor record). The
third character must have either a '5' (indicating "percentage reduction for SO2 and Nox") or '9'
(indicating the EER applies for all pollutants).
DATE :
SCREEN:
* POINT:
* CHANNEL
PF3=END
10/16/92 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP334
334 CONTINUOUS EMISSIONS MAP: AFM3341
_
#: CHEMICAL ABSTRACT #: *REPORT QUARTER (YYQQ) :
PF4=MAIN MENU PF5=TERM PF10=NEXT NEXT SCREEN:
FIGURE 2-62 CONTINUOUS EMISSIONS KEY DATA SCREEN
April 2003
2-67
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Continuous Emissions update screen requires you to supply an Air Program Code (minimum
1, maximum 6), and a Time Period Code.
Air Programs must be defined at the point air program level prior to referencing them for a continuous
emissions record.
The 'exceedance reason' fields contained on this screen are aggregated into logical groups on the
associated Continuous Emissions Browse screen, and a percentage that each 'reason' was responsible
for the total exceedance reported in the EER is displayed.
Once you data on this screen, you will be brought to the second 'page' for updating continuous
emissions data.
DATE : 10/16/92
SCREEN: 334
AIRS FACILITY SUBSYSTEM - UPDATE
CONTINUOUS EMISSIONS
PGM: AFP334
MAP: AFM3342
*POINT:
*CHANNEL #:
CHEMICAL ABSTRACT #:
*REPORT QUARTER:
*AIR PROGRAM CODE(S) :
TOTAL SOURCE OPERATING TIME:
*TIME PERIOD CODE:
STARTUP/SHUTDOWN :
CLEANING/SOOT BLOWING :
UNKNOWN EXCESS EMISSIONS :
CONTROL EQUIPMENT FAILURE :
CONTROL EQUIPMENT MALFUNCTION UNACCEPTABLE :
PROCESS PROBLEMS :
PROCESS PROBLEMS UNACCEPTABLE :
NUMBER OF INCIDENTS OF EXCESS EMISSIONS :
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 2-63 CONTINUOUS EMISSIONS UPDATE SCREEN - 1ST PAGE
This is the second page of the Continuous Emissions screen.
April 2003
2-68
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
FUEL PROBLEMS
OTHER KNOWN EXCESS EMISSIONS
MONITOR EQUIPMENT MALFUNCTIONS
NON-MONITOR EQUIPMENT MALFUNCTIONS
CALIBRATION (QA)
UNKNOWN MONITOR DOWNTIME
OTHER KNOWN MONITOR DOWNTIME
NUMBER OF INCIDENTS OF MONITOR DOWNTIME
SCREEN: 046
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-64 CONTINUOUS EMISSIONS UPDATE SCREEN - 2ND PAGE
Data entered into the ' downtime reason' fields contained on this screen will be aggregated into logical
groups on the associated Continuous Emissions Browse screen, with percentages assigned to each
'reason's' contribution to the total monitor downtime reported in the EER.
April 2003
2-69
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.6 Point Tank
The AFS Point Tank Update screen supports the identification of a point as a storage tank, and the
maintenance of tank descriptive data used in calculating tank emissions.
Tank records are identified by a Point ID. Point Tank records may only be added to existing emissions
points and only one tank record may be added per point. For existing point tank records, the entry of
the key data will result in the display of all associated record data. When entering new key data, a blank
data update screen will be displayed.
DATE : 04/01/94
SCREEN: 335
AIRS FACILITY SUBSYSTEM - UPDATE
POINT TANK INFORMATION
PGM: AFP335
MAP: AFM3351
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-65 POINT TANK KEY DATA SCREEN
April 2003
2-70
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
This screen supports the updating of tank descriptive data typically used in the performance of tank
emissions calculations. AFS does not perform these calculations.
DATE : 04/01/94
SCREEN: 335
AIRS FACILITY SUBSYSTEM - UPDATE
POINT TANK INFORMATION
PGM: AFP335
MAP: AFM3352
*POINT:
YEAR OF EMISSIONS INVENTORY (YY):
DIAMETER (FT): 000 HEIGHT (FT)
LOADING TYPE :
DATA FOR FIXED ROOF TANKS ONLY -
ROOF PAINT COLOR
AVERAGE VAPOR SPACE HEIGHT(FT) ..
DIURNAL TEMPERATURE CHANGE (F)
DATA FOR FLOATING ROOF TANKS ONLY -
CONSTRUCTION TYPE
DECK CONSTRUCTION TYPE
AVERAGE WIND SPEED (MPH)
AGE . .
COLOR
00
00
SHELL PAINT COLOR :
PAINT CONDITION ... :
i Updating
TANK SHELL CONDITION:
SEAL TYPE :
00 SUPPORT TYPE :
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 046
FIGURE 2-66 POINT TANK UPDATE SCREEN
Point Tank Information is optional and should only be addressed if the physical emission point is a
storage tank.
April 2003
2-71
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.7 Point Action
The AFS Point Actions update screen allows you to track compliance activities performed at the point.
Actions for a point are identified by an existing point ID and a unique numeric Action Number with a
value 1-998. For existing point action records, the entry of the key data will result in the display of all
associated record data. When entering new key data, a blank data update screen will be displayed.
DATE : 04/01/94
SCREEN: 336
AIRS FACILITY SUBSYSTEM - UPDATE
POINT ACTIONS
PGM: AFP336
MAP: AFM3361
KEY ACTION (Y/N)
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-67 POINT ACTION KEY DATA SCREEN
The entry of '999' in the Action Number field will result in the system automatically generating the next
available sequential point action number for the point action.
Certain compliance actions (administrative penalty, consent decree, administrative order, violation)
result in follow-up activities. AFS allows you to link these activities together. The initiating action is
called a 'Key' action. To designate an Action as a key action for action linking, specify 'Y' in the Key
Action field. Refer to the Action Linking User's Guide for additional information on the functionality of
Action Linking.
Point actions cannot be linked to an FCE pathway.
April 2003
2-72
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Action update screen requires you to supply values for Air Program Code (minimum of 1,
maximum of 6), Action Type, and Date Scheduled or Date Achieved. Air programs must be defined on
point air program record(s) prior to referencing them on point actions.
DATE : 10/16/92
SCREEN: 336
AIRS FACILITY SUBSYSTEM - UPDATE
POINT ACTIONS
PGM: AFP336
MAP: AFM3362
KEY ACTION (Y/N)
*AIR PROGRAM CODE(S) .. :
*ACTION TYPE :
ACTION DESCRIPTION ... :
DATE SCHEDULED (YYMMDD):
RESULTS CODE ..
STAFF CODE
POLLUTANT CODE
CONTRACTOR ID .
KEY ACTION(S):
ACTION TYPE CATEGORY :
"DATE ACHIEVED (YYMMDD) :
PENALTY AMOUNT : $
RDE 8 :
CHEMICAL ABSTRACT # .. :
PRIVATE(Y/N):
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF12=BRWS
FIGURE 2-68 POINT ACTION UPDATE SCREEN
If the Action Type does not correspond to a valid regional action type, State or County personnel may
specify the record to be private. If the record is not declared State-Private, invalid regional action types
will not be accepted.
Key action types must be used when defining Key Actions, and will trigger the display of key
action-specific update screens.
Use of the Action Description field is restricted to actions with an Action Type of "00" or those actions
designated as State-Private.
Users without update sensitive data access will not be allowed to enter enforcement sensitive Action
Types or access enforcement sensitive action records.
The most recent EPA and State Inspection Action Type and Date Achieved, based on Point Actions,
are recorded and can be browsed on Point General.
Some action types are obsolete, as flagged on the Action Table. New actions cannot be added with
obsolete action types. All fields on existing records with obsolete action types can be changed,
including changing an obsolete action type to a non-obsolete action type. An existing action type cannot
be changed to an obsolete action type.
For penalty amounts greater than 9,999,999, a"K", in the last position of this field may be entered. The
"K" used in this manner represents "thousands".
November 2003
On-Line Updating
2-73
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Actions-Consent Decree/Administrative Order update screen is specific to the updating of
actions resulting from the issuance of a consent decree or administrative order against the point. The
upper part of the screen displays air program and point-level compliance information. The lower part
of the screen allows you to add or change actions linked to the original Key Action consent decree or
administrative order.
DATE : 04/01/94 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP33603
SCREEN: 336 POINT ACTIONS - CONSENT DECREE/ADMINISTRATIVE ORDER MAP: AFM3364
*POINT: _
AIR PROGRAM CODE(S) : 8 STATE REGISTRATION NUMBER:
COMP STAT (EPA/ST) : / 3 CLASS: El STAFF: GOVT FACIL: 0 HPV:
LEAD AGENCY: VIOLATION IDENTIFIER: DOCUMENT NUMBER:
NEW
ACTION?
ACTION
NUMBER/TYPE
ACTION
DESCRIPTION
DATE
SCHED
DATE
ACHVD
PENALTY RESULTS
ST
PRIV
EPA 113A SIP OI
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-69 POINT ACTION UPDATE SCREEN FOR
CONSENT DECREE/ADMINISTRATIVE ORDER PATHWAY
The first action listed will be the key action itself.
April 2003
2-74
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Actions-Administrative Penalty update screen is specific to the updating of actions resulting
from the levy of an administrative penalty against the point. The upper part of the screen displays air
program and point-level compliance information. The lower part of the screen allows you to add or
change actions linked to the original Key Action administrative penalty.
DATE : 04/01/94
SCREEN: 336
AIRS FACILITY SUBSYSTEM - UPDATE
POINT ACTIONS - ADMINISTRATIVE PENALTY
PGM: AFP33602
MAP: AFM3363
*POINT:
AIR PROGRAM CODE(S) : STATE REGISTRATION NUMBER:
COMP STAT (EPA/ST) : / CLASS: STAFF: GOVT FACIL:
LEAD AGENCY: _ VIOLATION IDENTIFIER: _
VIOLATION TYPE CODE:
NEW ACTION
ACTION? NUMBER/TYPE
ACTION
DESCRIPTION
DATE
SCHED
DATE
ACHVD
PENALTY RESULTS
ST
PRIV
113D APO COMPL
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-70 POINT ACTION UPDATE SCREEN FOR
ADMINISTRATIVE PENALTY PATHWAY
The first action listed will be the key action itself.
April 2003
2-75
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Point Actions-Violations update screen is specific to the updating of actions resulting from the
designation of a point as in violation. The upper part of the screen displays air program, plant-level
compliance and Day 60, 150, 270, and 300 and Days Used to Address information. The Days Used
to Address and Unaddressed Days calculations include actions that are resolved. This is because a
pathway may not include an addressed action; the pathway could go directly to being resolved from a
Day Zero action. The lower part of the screen allows you to add or change actions linked to the original
Key violation Action.
DATE : 04/13/94
SCREEN: 336
AIRS FACILITY SUBSYSTEM - UPDATE
POINT ACTIONS - VIOLATIONS
PGM: AFP33604
MAP: AFM3365
* POINT:
AIR PROGRAM CODE(S) : STATE REGISTRATION NUMBER:
COMP STAT (EPA/ST) : / CLASS: STAFF: GOVT FACIL: HPV:
LEAD AGENCY: VIOLATION IDENTIFIER: VIOLATING PLLTS :
VIOLATION TYPE CODE:
DAY 60: DAY 150
DAYS USED TO ADDRESS :
NEW ACTION
ACTION? NUMBER/TYPE
N 001 Jl
: DAY 270: DAY 300:
0 UNADDRESSED DAYS: 0
ACTION DATE DATE PENALTY
DESCRIPTION SCHED ACHVD
FEDERL DAY ZERO 950101 0000000
RESULTS ST
PRIV
N
PF1=HELP PF3=END PF4=MAIN PF5=TERM
MORE
FIGURE 2-71 POINT ACTION UPDATE SCREEN FOR VIOLATION PATHWAY
The first action listed will be the key action itself.
April 2003
2-76
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.3.8 Point Comments
The Point Comments update screen supports the online addition of textual comments about a point,
point action monitor and/or Continuous Emissions excess emissions report. The keys specified
determine which of the aforementioned point information records the comment is referencing. The Point
Id and comment number are always required. Specification number to update a comment pertaining
to a particular action. Specify a channel numberto update a comment pertaining to a particular monitor.
Specify a channel number and a Report Quarter to update a comment for a particular Continuous
Emissions (EER) record, supply a Comment Number 1-998; . Point Action Comments can only be
added for existing Point Actions. 998 comments may be update for each combination of keys entered.
DATE : 04/14/94
SCREEN: 337
* POINT:
* COMMENT #:
PF1=HELP PF3=END
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP337
POINT LEVEL COMMENTS MAP: AFM3371
ACTION: CHANNEL #: REPORT QUARTER:
PF4=MAIN PF5=TERM PF10=SCRN SCREEN:
FIGURE 2-72 POINT COMMENT KEY DATA SCREEN
The entry of'999' in the Comment Numberfield will trigger AFS to generate the next available sequential
point comment number for the point key specific comment.
April 2003
2-77
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
Comments consist of 240 characters arranged over four, sixty-character lines. Point level comments
may generally be declared State-Private, but point comments linked to actions associated with valid
regional Action Types may not. Only compliance comments may be designated as enforcement
sensitive.
DATE : 05/31/95 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP337
SCREEN: 337 POINT LEVEL COMMENTS MAP: AFM3372
*POINT: _ ACTION: CHANNEL #: REPORT QUARTER:
YEAR OF EMISSIONS INVENTORY (YY) :
COMMENT # 001 C :
ENFORCEMENT SENSITIVE (Y/N)
PRIVATE (Y/N)
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN:
N
N
046
FIGURE 2-73 POINT COMMENT UPDATE SCREEN
You may provide as many as 998 comments for a point.
April 2003
2-78
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.4 AFS Segment Level Update Menu
Segments are components of processes, as defined by an eight-character source classification code,
that generate pollutants.
The Update Segment Information menu allows you to access update screens forthe following Segment
record types.
DATE : 12/15/97
SCREEN: 048
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT INFORMATION
1 GENERAL INFORMATION (340)
2 POLLUTANT INFORMATION (341)
3 CHEMICAL INFORMATION (342)
4 PROJECTED POLLUTANT (344)
5 COMMENTS (343)
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN PF12=BRWS
PGM: AFP048
MAP: AFM0481
FIGURE 2-76 AFS SEGMENT LEVEL UPDATE MENU
GENERAL INFORMATION General descriptive and operating data about a process
POLLUTANT INFORMATION Process-based pollutant emissions data
CHEMICAL INFORMATION Density and weight data for chemicals utilized by the process
PROJECTED POLLUTANT Projected process-based emissions, based on the SIP emissions
inventory forthe process
COMMENTS
Comments pertaining to the process segment
Only users with update access for emissions data may update segment data.
To select a particular record to update, type in the desired option number and . The next
screen presented will be the key information screen forthe option selected.
Each of the five Segment level update records are described individually in the following sections.
2.3.4.1 Segment General
The AFS General Segment Update screen allows you to update general descriptive data about a
April 2003 2-79 On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
process within a facility. These descriptive data may be used in conjunction with Segment Pollutant
data to support AFS-generated estimated emissions for the segment.
Segment records require a Point ID and Segment Number. Segment Numbers are unique within a
point. You can supply a value between '1' and '98' for a Segment Number. The entry of '99' in the
Segment Number field will trigger AFS to generate the next available sequential segment number for
that segment.
DATE : 04/08/94
SCREEN: 340
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL SEGMENT INFORMATION
PGM: AFP340
MAP: AFM3401
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-77 SEGMENT GENERAL KEY DATA SCREEN
For existing records, the entry of the key data will result in the display of all associated record data.
When entering new key data, a blank data update screen will be displayed.
Stack Numbers are not required to establish a segment in AFS, but provide you with a method of
indicating the stack through which a segment's emissions enter the atmosphere. Only numbers for
existing stacks may be associated to a segment.
It is not necessary to specify the stack number once a stack has been linked (associated) to a segment.
To unlink (unassociate) a stack from a segment, utilize the Segment Level Unlink Stack option of the
Delete Utility. This will only unlink the stack. It will not delete any portion of the stack or segment data.
April 2003
2-80
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
The Segment General update screen requires you to provide a Source Classification Code. Source
classification code is an eight-character number that defines a process and its valid pollutant types,
emission factors and emissions units.
DATE : 05/31/95
SCREEN: 340
AIRS FACILITY SUBSYSTEM - UPDATE
GENERAL SEGMENT INFORMATION
PGM: AFP340
MAP: AFM3402
STACK:
*SEGMENT:
YEAR OF EMISSIONS INVENTORY (YY):
*SOURCE CLASSIFICATION CODE ..
SEGMENT DESCRIPTION
ANNUAL FUEL PROCESS RATE ....
STD. FUEL PROCESS RATE UNITS
OPT. FUEL PROCESS RATE UNITS
FUEL DATA: SULFUR (%)
ASH/SULFUR SOURCE
HEAT CONTENT(MMBTU)
FUEL/MATERIAL SUPPLIER
TANK DATA: VAPOR PRESS (PSIA)
CONTROL EQUIPMENT COST
SOLVENT PURCHASED (GAL)
MATERIAL SAFETY DATA SHEET(YY)
POLLUTION PREVENTION IND
STATE SENSITIVE IND
MAX OPER RATE-PER HR
ASH (%)
ASH/SULFUR ORIGIN
00000
00
00 . 0000VAPOR MOLE.WT.(LB/LB MOLE): 000
00000 . 00 INSTALLATION DATE (YYMMDD):
000000 SOLVENT REPROCESSED (GAL) : 000000
SDE 6 : SDE 7 :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-78 SEGMENT
GENERAL UPDATE SCREEN
Emissions users may utilize the State Sensitive Indicatorto make the following fields State sensitive for
the segment: Annual Fuel Process Rate, Maximum Operation Rate Per Hour, Peak Ozone Season
Daily Process Rate, Peak CO Season Daily Process Rate, and Annual Estimation Methods. SIP update
sensitive access is required to update State sensitive daily process rates on SIP facilities.
For existing segments, where segment level estimated emissions are AFS calculated (as identified by
an annual or daily estimated emissions Method Code = 8 or 9 or Actual Uncontrolled method code =
1), modifications to the following fields will initiate re-calculations for these Emissions. Summary
explanations of emissions aggregations and calculations are in sections 1.17 and 1.18.
Source Classification Code
Annual Fuel Process Rate
Fuel Data: Ash or Sulfur Content Percent
If the facility is included in a frozen ozone or CO SIP inventory and the segment has segment pollutant
record(s) for the SIP inventory pollutant(s), the following fields will be display only:
Stack Number
Annual Fuel Process Rate
Ash and Sulfur Content
Source Classification Code
Maximum Operation Rate Per Hour
Optional Fuel Process Rate Units
A Pollution Prevention Indicator of'Y' indicates that a segment comment exists detailing the pollution
prevention measures that are in place.
April 2003
2-81
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
PEAK OZONE SEASON DAILY PROCESS RATE
PEAK OZONE SEASON VAPOR PRESSURE
PEAK CO SEASON DAILY PROCESS RATE
00000 . 000
00 . 0000
00000 . 000
SCREEN: 048
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-79 PAGE - SEGMENT GENERAL UPDATE SCREEN
This is a continuation 'page' of the Segment General screen.
For existing segments, where segment level estimated emissions are AFS calculated (as identified by
a daily estimated emissions Method Code = 8 or 9), modifications to the following fields will initiate
re-calculations and bubble-up of segment pollutant CO Season Daily and/or Ozone Season Daily
Emissions. Summary explanations of emissions aggregations and calculations are in sections 1.17 and
1.18.
Peak CO Season Daily Process Rate
Peak Ozone Season Daily Process Rate
If the facility is included in a frozen ozone SIP inventory and the segment has segment pollutant
record(s) for the SIP inventory pollutants (CO,NO2,VOC), the following fields will be displayed and not
allowed to be updated:
Peak Ozone Season Daily Process Rate
Peak Ozone Season Vapor Pressure
If the facility is included in a frozen CO SIP inventory and the segment has segment pollutant record(s)
forthe SIP inventory pollutant (CO), the following fields will be displayed and not allowed to be updated:
Peak CO Season Daily Process Rate
April 2003
2-82
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.4.2 Segment Pollutant
The AFS Segment Pollutant update screen supports the identification of emission types and pollutant
amounts emitted as a result of segment process operations.
Segment pollutant records require a Point ID, Segment Number, and either a Pollutant Code or
Chemical Abstract Service Number. For existing records, the entry of the key data will result in the
display of all associated record data. When entering new key data, a blank data update screen will be
displayed.
DATE : 04/08/94
SCREEN: 341
STACK:
POLLUTANT CODE:
PF1=HELP PF3=END
AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP341
SEGMENT POLLUTANT INFORMATION MAP: AFM3411
INV YEAR:
* POINT: *SEGMENT:
CHEMICAL ABSTRACT #:
PF4=MAIN PF5=TERM PF10=SCRN SCREEN:
FIGURE 2-80 SEGMENT POLLUTANT KEY DATA SCREEN
Users authorized to address compliance information may enter data for one or more of the following
emissions types on a merged point (Compliance Emissions Identifier = "M"): Allowable, Potential
Controlled, Potential Uncontrolled, Actual Uncontrolled.
Users authorized to address emissions information may enter Estimated (with or without Rule
Effectiveness) and/or Measured Emissions types. Minimum requirements are: An annual estimated
emissions value (ESTI or ESTW) must be entered. Which type is required is dependent on which
emission types exist at the plant level. If neither or both ESTI or ESTW exist at the plant level, either
or both ESTI or ESTW may be entered. If only ESTI exists at the plant level then ESTI is required. If
only ESTW exists at the plant level then ESTW is required. In addition, the following emissions types
may be entered for pollutants not being recorded as part of a SIP inventory: Peak CO Season Daily
(with or without Rule Effectiveness), Peak Ozone Season Daily (with or without Rule Effectiveness),
Annual Banked, Emission Limitation. For merged points, users authorized to address emissions and
compliance information may enter data for one or more of the above mentioned emission types.
April 2003
2-83
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 08/31/95 AIRS FACILITY SUBSYSTEM - UPDATE
SCREEN: 341 SEGMENT POLLUTANT INFORMATION
PGM: AFP341
MAP: AFM3412
INV YEAR:
STACK: *POINT:
POLLUTANT CODE:
*SEGMENT:
CHEMICAL ABSTRACT #:
POLLUTANT FORM:
EMISSIONS
TYPE VALUE UNIT METHOD
EMISSIONS
TYPE VALUE
UNIT METHOD
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-81 SEGMENT POLLUTANT UPDATE SCREEN
For emissions and merged points, users authorized to address SIP information for a segment pollutant
record in a SIP Inventory may enter data on one or more of the following emissions types in addition to
those listed for emissions access: Estimated (with Rule Effectiveness, Peak CO Season Daily (with or
without Rule Effectiveness), Peak Ozone Season Daily (with or without Rule Effectiveness), Annual
Banked, Emission Limitation. When authorized users enter Estimated emissions without Rule
Effectiveness for a merged point, the system will automatically compute Actual Uncontrolled emissions
where no user-supplied value exists.
You must supply Emissions Type, Emissions Value, Unit Code, and Method Code (where applicable)
for each emission type entered. The emissions value supports the entry of a floating decimal point.
When using a Method Code to have AFS calculate emissions, enter only the Emissions Type and the
Method Code.
If the segment is included in a frozen SIP Inventory and the segment has segment pollutant records for
the SIP inventory pollutants, the following fields will be displayed and not allowed to be updated:
Estimated Emissions Value, Estimated Emissions Units, Estimated Emissions Method.
If the pollutant specified is not a federally regulated pollutant, State personnel may specify this record
to be State-Private.
The Pollutant Form is required for a hazardous air pollutant (HAP).
April 2003
2-84
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
This is the second 'page' of the Segment Pollutant update screen for segments associated with
emissions-only points.
DATE : 08/31/95
SCREEN: 341
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT POLLUTANT INFORMATION
PGM: AFP341
MAP: AFM3413
INV YEAR:
PRIMARY/SECONDARY CONTROL
EQUIPMENT : /
MANUFACTURER : /
EMISSION FACTOR :
EMISSION FACTOR ORIGIN:
STD EMISSION FACTOR UNITS:
ASH/SULFUR/TRACE CODE : _
TRACE ELEMENT PERCENT : 00
SIP RULE IN PLACE
SEASONAL ADJUSTMENT FACTOR
RULE EFFECTIVENESS PERCENT
EMISSION LIMIT DESCRIPTION
CONTROL EQUIPMENT
EFFICIENCY (%): 00 . 000 METHOD:
EMISSION FACTOR SOURCE
SDE 8
TRACE ELEMENT METHOD CODE ....
YEAR REGULATED (YY)
YEAR LAST MODIFIED (YY)
RULE EFFECTIVENESS METHOD CODE
PRIVATE(Y/N) : N
SCREEN : 048
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-82 2ND PAGE - SEGMENT POLLUTANT UPDATE SCREEN
For existing segment pollutant records that utilize a Method Code = 8 or 9 to trigger AFS to calculate
emissions values, modifications to the following fields will initiate re-calculations for Estimated emissions
and Peak CO and Ozone Season Daily (with and without Rule Effectiveness) emissions. Summary
explanations of emissions aggregations and calculations are in sections 1.17 and 1.18.
Ash/Sulfur/Trace Code
Trace Element Percent
Control Equipment Efficiency
Emission Factor (Method Code = 9)
Rule Effectiveness Percent (with Rule Effectiveness emissions)
Emissions Method Code to 8 or 9
Modifications to Estimated Emissions values will initiate recalculations for Actual Uncontrolled Emissions
when using a Method code for computer-calculated values (1).
The emission factor supports the entry of a floating decimal point.
April 2003
2-85
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
If the segment is included in a frozen SIP Inventory, the following fields will be display only on SIP
inventory segment pollutant records:
Estimated Emissions
with and without Rule Effectiveness
Peak CO and Ozone Season Daily Emissions
with and without Rule Effectiveness
Annual Banked Emissions
Emission Limitation data
SIP Rule data
Seasonal Adjustment Factor,
Primary/Secondary Control
Equipment
Control Equipment
Efficiency
Emission Factor
If the pollutant specified is not a federally regulated pollutant, State personnel may specify this record
to be State-Private.
2.3.4.3 Segment Chemical
The AFS Segment Chemical update screen supports updating of chemical records as identified by Point
ID, Segment Number and a Chemical Abstract Service Number.
DATE : 04/08/94 AIRS FACILITY SUBSYSTEM - UPDATE
SCREEN: 342 SEGMENT CHEMICAL
PGM: AFP342
MAP: AFM3421
INV YEAR:
*CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-83 SEGMENT CHEMICAL KEY DATA SCREEN
For existing records, the entry of the key data will result in the display of all associated record data.
When entering new key data, a blank data update screen will be displayed.
April 2003
2-86
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
All segment chemical records require you to supply:
Chemical Density and its Decimal Position, or
Chemical Weight Percent
State personnel may specify this record to be State-Private.
DATE : 04/08/94 AIRS FACILITY SUBSYSTEM - UPDATE
SCREEN: 342 SEGMENT CHEMICAL
PGM: AFP342
MAP: AFM3422
INV YEAR:
*CHEMICAL ABSTRACT #:
CHEMICAL DENSITY : 00000
CHEMICAL WEIGHT PERCENT: 00 . 00
DECIMAL POSITION:
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 048
FIGURE 2-84 SEGMENT CHEMICAL UPDATE SCREEN
April 2003
2-87
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.4.4 Segment Projected Pollutant
The AFS Segment Projected Pollutant update screen supports the input of projected emissions values
subject to State Implementation Plan (SIP) 1990 baseline and follow-up inventory reporting
requirements.
Projected pollutant records require a Projection Year, Point ID, a Segment Number, an Emission Type
Indicator, an Inventory Type and either a SIP Program Pollutant Code or Chemical Abstract Service
Number for SIP facilities. Projected information may be supplied for any existing segment pollutant on
non-SIP Inventory reportable facilities. For existing records, the entry of the key data will result in the
display of all associated record data. When entering new key data, a blank data update screen will be
displayed.
DATE : 04/08/94
SCREEN: 344
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT PROJECTED POLLUTANT INFORMATION
PGM: AFP344
MAP: AFM3441
STACK: *PROJECTION YEAR:
*SEGMENT: 01 *EMISSION TYPE INDICATOR:
POLLUTANT CODE: VOC
INV YEAR:
*POINT:
* INVENTORY TYPE:
CHEMICAL ABSTRACT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-85 SEGMENT PROJECTED POLLUTANT KEY DATA SCREEN
Users authorized to address emissions information who are updating a facility under a SIP inventory
may select this screen to enter data. If the pollutant selected is a pollutant included in a SIP inventory
for the facility, SIP update authority is needed. Projected Pollutant information may be entered for all
other pollutants on SIP plants and/or all pollutants on non-SIP plants.
April 2003
2-88
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
Projected (estimated emissions for a SIP projection year) and/or Projected Emission Limitation may be
entered on the data screen.
DATE : 11/23/94
SCREEN: 344
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT PROJECTED POLLUTANT INFORMATION
PGM: AFP344
MAP: AFM3442
STACK:
*PROJECTION YEAR:
INV YEAR:
*POINT:
*SEGMENT:
POLLUTANT CODE:
*EMISSION TYPE INDICATOR:
SCC:
* INVENTORY TYPE:
CHEMICAL ABSTRACT #:
EMISSIONS
TYPE VALUE
UNIT METHOD
EMISSIONS
TYPE VALUE
UNIT METHOD
EMISSION LIMITATION DESCRIPTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 2-86 SEGMENT PROJECTED POLLUTANT UPDATE SCREEN
You must supply an emission Type, Unit Code, and Method Code (where applicable) if an Emissions
value is entered. The emissions value supports the entry of a floating decimal point.
If the segment is subject to a frozen SIP Inventory and the segment has segment projected pollutant
records for the SIP Inventory pollutants, the entire screen will be displayed and not allowed to be
updated.
April 2003
2-89
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
This is the second 'page' of the Projected Pollutant update screen.
This screen supports the update of growth factor, control efficiency and SIP rule variable data.
SIP RULE IN PLACE
YEAR REGULATED
PRIMARY/SECONDARY
CONTROL EQUIPMENT.... :
GROWTH FACTOR
RULE EFFECTIVENESS PERCENT
CONTROL EQUIP
EFFICIENCY (%): 00 . 000 METHOD:
RULE EFFECT. PERCENT METHOD ..
SCREEN: 048
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP PF9=DUPL PF10=SCRN PF12=BRWS
FIGURE 2-87 2ND PAGE - SEGMENT PROJECTED POLLUTANT UPDATE SCREEN
If the segment is subject to a frozen SIP Inventory and the segment has segment projected pollutant
records for the SIP Inventory pollutants, the entire screen will be displayed and may not be updated.
April 2003
2-90
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
2.3.4.5 Segment Comments
The Segment Comments update screen supports the online addition of textual comments about the
segment. Segment Comments can only be added for existing segments. You must supply the point
ID and segment number the comment references. You must supply a Comment Number 0-998 and a
Comment Identifier of M (merged), 'E'(emissions), or'P' (pollution prevention remark).
DATE : 04/08/94
SCREEN: 343
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT LEVEL COMMENTS
PGM: AFP343
MAP: AFM3431
*COMMENT #:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF10=SCRN
FIGURE 2-88 SEGMENT COMMENTS KEY DATA SCREEN
The entry of '999' in the Comment Number field will result in the system automatically generating the
next available sequential segment comment number.
April 2003
2-91
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
Comments consist of 240 characters arranged over four, sixty-character lines. Segment and
segment-stack comments may be declared State-Private. Users with compliance update sensitive
access may declare comments enforcement sensitive.
DATE : 05/31/95
SCREEN: 343
AIRS FACILITY SUBSYSTEM - UPDATE
SEGMENT LEVEL COMMENTS
PGM: AFP343
MAP: AFM3432
STACK: *POINT:
YEAR OF EMISSIONS INVENTORY (YY):
COMMENT # 001 C :
*SEGMENT:
ENFORCEMENT SENSITIVE(Y/N): N
PRIVATE(Y/N): N
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN: 048
FIGURE 2-89 SEGMENT COMMENT UPDATE SCREEN FOR 'E1 AND 'C1 COMMENTS
April 2003
2-92
On-Line Updating
-------
AFS User's Guide
AF3
AFS Data Storage
DATE : 08/31/95 AIRS FACILITY SUBSYSTEM - UPDATE PGM: AFP
SCREEN: 343 SEGMENT LEVEL COMMENTS MAP: AFM
STACK: * POINT: *SEGMENT:
YEAR OF EMISSIONS INVENTORY (YY) :
POLLUTION PREVENTION REMARKS
COMMENT # 001 P :
ENFORCEMENT SENSITIVE (Y/N) :
PRIVATE (Y/N) :
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF9=DUPL PF10=SCRN PF12=BRWS SCREEN:
343
3432
N
N
048
FIGURE 2-89.1 SEGMENT COMMENT UPDATE SCREEN FOR 'P1 COMMENTS
You may provide as many as 998 comments for a segment.
April 2003
2-93
On-Line Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.0 Batch Updating
3.1 Introduction
In addition to the On-Line processing described in Section 2 of this manual, AFS allows users to
add, change, or delete data in a batch mode. Batch users supply datasets in a supported batch
transaction format, and submit the transaction file for processing.
The Batch Update function includes two separate, related processes: the Compare Process and the
Edit/Update Process. Section 3.2 of this manual describes the input transactions used by both
processes. Section 3.3 describes the Compare Process, and Section 3.4 describes the Edit/Update
Process.
The AF1 - Data Dictionary and AF2 - Data Coding Manual also provide valuable information on each
data element in AFS and the requirements for supplying these data to AFS utilizing the Batch
Update process. Agencies submitting data in Batch may also refer to Section 2 - On-Line Updating
for a visual aid. The majority of the data processing rules and validations apply to both Online and
Batch data submittals.
3.2 Update Transactions
3.2.1 Transaction Formats
Transactions contain the information to be added, changed or deleted in AFS. The format of the
transaction is predefined for AFS to interpret. Transactions may be created in any computing
environment. These typically include computer generated from a local or state system, TSO/ISPF
and PC editors. However created, they must be in a transaction format acceptable to AFS, and
reside on the NCC-IBM prior to executing a batch submittal using the Batch Edit/Update Process.
Files transferred to the NCC IBM are automatically assigned a first qualifier consisting of your User
ID and Account Code.
You can perform a batch update of AFS by submitting datasets containing transactions in one of the
following formats:
• AFS (AIR Facility Subsystem) Transaction Format, 80-character records
• AFX Transaction Format
The AFX Transaction Format is an expanded format, 120 characters rather than 80, designed to use
the 15-character AFS plant ID and a number of other new or enhanced data fields.
This Section 3.2 describes the AFS and AFX Transaction Formats.
Section 3.4 describes the Edit/Update Process in detail. Edit validates the user's transaction dataset
and produces reports that detail the errors. Data that pass Edit can be written to a file of accepted
transactions, and data that fail can be written to a file of rejected transactions.
Update works very much like Edit, except that valid data elements are applied to the database.
Invalid data are written to a file of rejected transactions for subsequent correction and re-
April 2003 3-1 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
processing.
3.2.2 General Format of AFS and AFX Batch Transactions
AFS and AFX Batch transactions are designed in accordance with the AFS On-Line system. A
transaction set (transaction type and sequences) has been developed for each AFS record type and
each set follows the data flow pattern of the On-Line Update screens where possible. Due to the
transaction length constraints some flexibility of field placement was used so contiguous fields
found on an on-line update screen are not always contiguous on the comparable batch update
transaction format.
Separate batch transaction sequences have been developed for the AFS users who access
Compliance only or Emissions only data. These transaction sequences were created in order to
avoid the confusion that may exist if either a Compliance only or Emissions only user is confronted
with a set of transactions containing data fields irrelevant for their specific use.
AFS and AFX Batch transactions consist of fixed-format records. Each record contains:
• Transaction Type
• Sequence Number
• Key Fields
• Data Elements
• Update Code
Transaction type is the 2-position code that identifies a specific transaction. Each of the
transaction types corresponds to the AFS on-line update screen(s). Batch transactions are identified
by a 2-position transaction type code, that distinguishes the AFS record type, and a 1-digit sequence
number that determines the data sequence within the record. In most cases, the first character of
the transaction number identifies the transaction level (i.e., plant, point, etc) and the second
character determines the transaction type within the level (i.e., pollutant, air program, action, etc.).
The hierarchy of AFS batch transactions is shown in Figure 3-1.
Sequence number is the number associated with the transaction type to provide a means of
sequencing transaction sets that require more than one record to contain all of the data elements of
the corresponding AFS on-line update screen.
Key fields are the required fields for each transaction type that uniquely identify the record to be
affected by the transaction being processed. These key fields correspond to the required key fields
on the related AFS on-line update screen. All positions of key fields must be entered, including any
leading zeros.
The Federal Information Processing Standard (FIPS) State and County codes and the plant identifier
are key fields on the majority of transactions. The plant identifiers supported in AFS batch
transactions are the 5-position compliance (CDS) plant ID, the 4-position emissions (NEDS) plant ID
and the 15-position AFS plant ID. The AFS plant ID is supported on both AFS and AFX permit data
transaction formats, as well as on all other AFX transactions that use plant ID. Users entering
emissions plant ID's must enter the ID beginning in the first column (6) and leave the last column
(10) blank.
The Year of Record is a key field that indicates which year of emissions data is to be updated. The
Year of Record must be supplied on all emissions-only transactions and for all emissions-only
plants, regardless of the type of plant ID used (NEDS, CDS, or AFS plant ID). Year of Record is
April 2003 3-2 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
required whenever updating emissions information, including emission data types for a merged
plant. The owner, or "data type" of each field can be found in the data dictionary.
Compliance data are cumulative. All the data for a facility throughout the years of operation are
kept together. Year of Record should not be addressed for compliance-only transactions or plants.
Data elements are the individual data fields in the transaction that correspond to the individual
data fields on the related AFS on-line update screen.
Update code is the action code to be performed for a record as a whole that corresponds to the
related AFS on-line update screen(s). Valid update codes are A (add), C (change) or D (delete).
AFS Batch Transaction Format Graphic representations are available. The text representation is in
Appendix A of this manual. New versions are reissued as part of any enhancement developed
which results in a change in the formats. You may contact the AFS Helpline to request the latest
version.
April 2003 3-3 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
Level
A
B
C
Level
Type
Permit
Plant
Transaction
Type
1
2
7
0
1
2
3
4
5
Transaction Sequence
Name Numbers
Application 1-5
Draft Permit 1-5
Application Association 1
Event Tracking Action 1-8
Plant Permit Comment 1-4
Event Tracking Action 1-9
Comment
General Plant Information 1-9
Plant Pollutant Information 1
Plant Air Program 1
Plant Pollutant Air Program 1
Fee Certification 1
Mailing Label Information 1-3
Plant Action 1-4
Plant Level Comment 1-4
Compliance Monitoring Strategy 1
Stack
Point
Segment
Contractor
Landfill
Performance
Utility
0
1
7
0
1
2
3
4
5
0
1
2
3
7
0
1
2
0
1
4
5
General Stack Information 1-2
Stack Pollutant Information 1
Stack Level Comment 1-4
General Point Information 1-4
Point Pollutant Information 1-3
Point Air Program 1
Point Monitor Information 1-2
Continuous Emission 1-3
Point Tank Information 1
Point Action 1-4
Point Level Comment 1-4
General Segment Information 1-5
Segment Pollutant Information 1-3
Segment Chemical 1
Segment Projected Pollutant 1-3
Segment Level Comment 1-4
Asbestos Contractor Information 1-4
Asbestos Landfill Information 1-3
Asbestos Performance Information 1-9
Merge Plant 1
Archive Plant 1
Source/Point Swap 1
Merge Point 1
Figure 3-1 AFS BATCH TRANSACTION HIERARCHY
3.2.3 General Coding Instructions
Four general types of values are used to code AFS Batch Transactions:
• CODES
April 2003
3-4
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
• DATES
• NUMERIC DATA
• ALPHANUMERIC DATA
• SPECIAL CHARACTERS
Codes must be entered exactly as they are listed in the AFS and Geographic/Common Table files.
For example, a county code is three digits, and all three digits of the code are required (including
any leading zeros). Code values are listed in AF1 - Data Dictionary if the list is short. Batch listings
of code values may be produced from the AFS Table Lookup option. Refer to the Table Lookup
option in the Utilities Section 4 for operational instructions. Batch listings may also be obtained
from the Batch Retrievals option in Geographic/Common.
Dates are entered in CCYYMMDD or YYMMDD format. CC is the century portion of the year, YY is
the decade portion of the year, MM is the month number and DD is the day number. No blanks are
allowed.
To address the Y2K date problem, the AFS system applies the "50" rule when evaluating 2-digit
years. The "50" rule states that if the 2-digit year is greater than 50, the century is processed as 19,
otherwise, the century is processed as 20. The '50' rule is applied to all 2 digit year dates discussed
in this manual.
Numeric values can be entered left-justified or entered with leading zeros in the fields of batch
transactions. When entering a value beginning in the first position of the field (left-justified) it is
unnecessary to fill the field with leading zeros. Numeric fields may never contain leading blanks.
For example, to express an emissions value of 150 tons/year, you could enter:
0000150 (leading zeros and right-justified) or
150 (left-justified and trailing blanks) or
0150 (left-justified and trailing blanks).
For batch transactions, Decimal Points (.) may not be entered within a numeric field. When a
numeric field may have differing numbers of decimal places a separate companion field exists for
the Decimal Position. When a numeric field has a fixed decimal position, the field itself is an
Implied Decimal field.
Numeric fields and companion Decimal Position values are used in batch transactions to identify
the number of positions that the numeric value contains that should be right of the decimal. For
example, the Emissions Decimal is a companion field to the Emissions field, the value for an
estimated emission of 123.45 could be entered in any of the following ways:
April 2003 3-5 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
EMISSION
EMISSION DECIMAL
0012345 2 (leading zeros, right-justified)
12345 2 (left-justified, trailing blanks)
Numeric fields that have an Implied Decimal place must be entered in relation to the decimal
position. For example, Control Equipment Efficiency % is defined as a 5 position field (99-999) with
an implied decimal between positions 2 and 3. Typical values would be entered as follows:
VALUE ENTERED FIELD
85% 85000
62.55% 62550
Alphanumeric values should be entered left-justified in the field. Any letter or number may be
used. Input data fields entered in lower-case alpha characters are converted to upper-case
characters.
Special Characters: Three special characters are reserved and may not be entered on transaction
formats. These are: semicolon (;); carrot (~); and the broken bar (|).
3.2.4 Year of Emission Inventory Processing
AFS supports the entry and maintenance of multiple years of emission inventory data. To access
emission inventory data, you must indicate which year of inventory data to update. This is
accomplished by entering the last two digits of the year in the Emissions Inventory Year of Record.
Alternatively, if you are submitting transactions for a single year of emissions inventory, you may
leave the Emissions Inventory Year of Record field blank and supply the Emissions Inventory Year of
Record on the Batch Submittal Year of Record screen (see Figure 4-30) when you submit your
transactions. Every transaction in your submittal is assigned the Emissions Inventory Year of
Record specified (except blank) on the Batch Submittal Year of Record screen, regardless of any
years supplied on your transactions.
AFS uses the Emissions Year of Increment field on the Plant General transaction type 10,
sequence 6 to enable users to retain a copy of the current year of inventory to use as the base
inventory for the new year. This newly created emissions year may be greater than or less than the
current year. The new year's inventory may be updated with any appropriate changes (adds,
changes and/or deletes). This process is accomplished by submitting a Plant General transaction
type 10, sequence 6 with a change update code with the Emissions Year of Increment value other
than the most recent value on AFS. This results in special processing being performed. Changing
(incrementing or decrementing) the value of this data element indicates that a new year of
emissions inventory data is to be created for the plant. AFS copies all current values of
emissions-related information for the plant to the new year. SIP data will be included in the new
year of data unless you indicate "Annual Only" on the Batch Submittal Copy Options screen (Figure
4-30) when the transaction file is submitted. All other emissions data submitted will be applied to
the year of record indicated (either in the Year of Record field or on the Batch Submittal Utility
screen).
April 2003 3-6 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.2.5 General Edits
Required fields: Each AFS Batch Transaction must contain the following required fields:
• TRANSACTION TYPE
• SEQUENCE CODE
• KEY FIELDS
• UPDATE CODE
Key and Data Field Edit checks: The data value, range, relational and format checks that are in
place for On-Line processing are also enforced for Batch processing. An example of a relational edit
is: Control Equipment must be valued in order to add Control Equipment Efficiency Percent.
Security Edits: The security edit checks the user's security profile to verify update access to the
plant (state/county).
3.2.6 Add Transactions
The Update code for Adding a transaction to the AFS database is A.
To Add a record, a record with the same key fields must not exist on AFS. If you attempt to add a
record that already exists, the transaction will be rejected and reported on the Edit/Update Error
Report with the message:
RECORD TO BE ADDED WAS FOUND ON FILE
Transaction Types (records) are generally comprised of multiple sequences in order to
accommodate all of the data on the record. The simplest way to determine which update code to
use to add a record is to specify an "A" (Add) update code on all unique sequence numbers for a
given transaction. At a minimum all sequences that contain mandatory data elements must have an
update code of "A" to add a record. When submitting multiple same sequences, for example two
sequence 1 transactions, for a single transaction type, one must be an add and the others must be
changes. When adding a new pollutant record with multiple emission types, for example, one of
the transaction type sequence 1 transactions must have an update code of "A" (Add) and all other
transaction type sequence 1's for additional emissions types must have an update code of "C".
When adding a new segment pollutant record, one emission type is required (refer to Adding a
Segment Pollutant later in this section). The transaction type 41/sequence 1 which has the required
emissions type must have the update code of "A" and the other transaction type 41/sequence 1's
must have an update code of "C" (Change). Please refer to the following examples.
April 2003 3-7 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Example 1: Transaction Type 41 - Segment Pollutant
All three sequence transactions (sequence 1,2 and 3) are
assigned an update code of "A" to add data for the VOC segment
pollutant record.
1234567
010010001 41190001E01VOC ESTI00345006TY3
A
010010001 41290001E01VOC 001002989892 0034265STATE 098E
NA
010010001 41390001E01VOC NO EMISSION LIMIT
Y8989 A
Example 2: Transaction Type 41 - Segment Pollutant
There are three sequence 1 transactions to add data for the VOC
segment pollutant record.
010010001 41190001E01VOC ESTI00345004TY3
A
010010001 41190001E01VOC ESTW00365004TY3
C
010010001 41190001E01VOC ACTU00370004TY3
C
There are minimum data requirements that require the submittal of more than one transaction
type/sequence set to successfully add records in AFS. These requirements apply to adding a
compliance facility, an air program, an emissions facility, an emissions point, an associated facility
and segment pollutant emissions. The transactions required for each are identified below. Refer to
Section 1.12 - Mandatory Data for additional information.
Adding a Compliance Facility
The mandatory transaction type/sequences for adding a compliance facility are Plant General
(transaction type 10, sequence 1, 2, 3, and 4), an Air Program (transaction type 12, sequence 1) and
an Air Program Pollutant (transaction type 13, sequence 1). This combination identifies at least one
pollutant being tracked for a regulatory air program at the facility.
Adding an Air Program
The mandatory transaction type for adding an air program (transaction type 12) is an air program
pollutant (transaction type 13, sequence 1). This combination identifies at least one pollutant being
tracked for each regulatory air program at the facility.
Adding an Emissions Facility
The mandatory transaction type/sequences for adding an emissions facility are Plant General
(transaction type 10, sequence 1, 2, 3, and 6).
Adding an Emissions Point
The mandatory transaction type/sequence for adding an emissions point (transaction type 30) is a
April 2003 3-8 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
segment general (transaction type 40, sequence 1). At least one Segment General record must be
added for each emissions Point General record. This combination identifies at least one process or
process component (segment) for a process location (emissions point).
Adding an Associated Facility
You must supply both the compliance and emissions facility transactions when adding an
associated facility. To add an associated facility you must supply the compliance plant ID as the
base ID (columns 6-10 on all transaction types submitted) and the emissions plant ID in the
associated plant ID (transaction type 10, sequence 1, columns 56-60). Do not enter an emissions
year of record on the transaction or the Batch Submittal Copy Options screen. The Year of
Emissions Increment field on the transaction type 10, sequence 6 will be used to establish the
Emissions Inventory Year of Record.
Adding a Segment Pollutant
To ensure that an annual plant pollutant estimated emissions total can be determined based on
complete segment pollutant emissions information the following requirements are enforced for
adding segment pollutant information:
Either Estimated Emissions Without Rule Effectiveness (emission type ESTI) or Estimated Emissions
With Rule Effectiveness (emission type ESTW) is required. Which emission type is required is
dependent on which emission type(s) exist at the plant level. If neither or both ESTI or ESTW exist
at the plant level, either or both ESTI or ESTW may be entered.
If only ESTI exists at the plant level then ESTI is required.
If only ESTW exists at the plant level then ESTW is required.
The required emission type on segment pollutant transaction type/sequence 41/1 is submitted with
an Update code of A (Add), a update code of C (change) must be used for all other emission types
for the same segment pollutant.
For example: To add a segment pollutant record for VOC with estimated emissions without rule
effectiveness supply transaction type/sequence 41/1 with ESTI emission type and
an update code of A.
To add additional emission types such as ESTW (estimated emissions with rule
effectiveness), 03DA (peak Ozone season daily emissions without rule
effectiveness) and CODA (peak Ozone season daily emissions without rule
effectiveness) to the same segment for VOC (all segment pollutant keys must be
identical), supply three transaction type/sequence 41/1's one each for ESTW, 03DA
and CODA emission type with an update code of C. The emission type, value, units
code and method code must be supplied unless using method code 8 or 9. Supply
only the emission type with method code 8 or 9.
The previous example assumes either this is the first VOC pollutant record for the
facility or that all previously entered VOC emissions were entered with a minimum
of estimated emissions without rule effectiveness (ESTI). Otherwise all of the 41/1
transactions would have failed because estimated emissions with rule effectiveness
(ESTW) would be required.
Once a transaction type (record) has been successfully added to AFS for a given key, an update
April 2003 3-9 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
code of A (ADD) should not be used to access that record in later submittals.
3.2.7 Change Transactions
The Update code for Changing a transaction on the AFS database is C.
To change a record, a record with the same key fields must exist on AFS. If you attempt to change
a record that does not exist, the transaction will be rejected and reported on the Edit/ Update Error
Report with the message:
RECORD TO BE CHANGED DOES NOT EXIST
Any valid Transaction Type and Sequence can be used with a Change Update Code. The
exception is that an update code of "C" may not be used on an Association Application transaction
type A7. Application is the only modifiable field on this record. The following information on
blanking out existing data values provides additional information.
A BLANK data field in an AFS Batch Transaction with a Change Update code is treated by AFS as a
data field being skipped and not changed. The value existing on AFS will be unaffected.
Blanking Out Existing Data Values
If you wish to blank out data values already stored in AFS without deleting the record, use a Change
Update Code and place an asterisk (*) in the first position of the data field in the AFS Batch
Transaction. For example, to delete (blank out) the Compliance Contact Person data element,
submit a Plant General transaction type 10 sequence 5 with the state, county and plant ID keys, an
"*" in column 14 of AFS transactions (the first column of the Compliance Contact Person data
element) with an Update Code of "C" (change). Do not use an update code of "D" - Delete to blank
out data elements. The exception to this rule is the Application Association record, transaction type
A7. To blank out an application submit the A7 transaction with the application to be deleted and an
update code of "D". Refer to Section 3.2.8 - Delete Transactions for information on how to delete
entire records.
Note that for the Plant General record, the MACT Determination fields may not be deleted
individually. You may only delete the logical grouping of fields which includes MACT Category, Sub
Category, Section 112 Indicator, and Date Determination Completed. To do this, submit a Plant
General transaction type 10 sequence 8 with the State, County, Plant ID, MACT Category, Sub
Category, and Section 112 keys, an "*" in column 55 (the first column of the Date Determination
Completed data element) with an Update Code of "C" (change). Do not use an update code of "D" -
Delete.
April 2003 3-10 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.2.8 Delete Transactions
The Update code for Deleting a record on the AFS database is D.
To delete a record, a record with the same key fields must exist on AFS. If you attempt to delete a
record that does not exist, the transaction will be rejected and reported on the Edit/Update Error
Report with a message stating that the specific record selected for deletion does not exist.
To delete an AFS record, you need only supply the key fields and an update code of D on the
transaction. Data fields are ignored if populated, except for transaction type A7 as explained in
Section 3.2.7. Deletes may be requested by submitting any transaction type sequence that
identifies the record. For example, to delete an entire facility submit a transaction type 10, any
single sequence with the keys, state, county, plant ID and a D in the update code.
Deletions will be made in accordance to the system hierarchy (see Section 1.10.1, Figure 1-14 - AFS
Update Road Map). Consequently, records subordinate to a deleted record will also be deleted.
This cascade effect is reflected in the following example: By specifying the deletion of an emissions
point, all existing point level records tied to that point will be deleted as part of the point delete.
These records include: comment, point pollutant, segment, segment pollutant, segment comment,
chemical and projected pollutant. Security is checked only on the parent record, not on subordinate
records.
There is no recovery for information deleted by an Update job. It is recommended that you contact
your Regional Coordinator if you have questions about the implications of a delete request. A
backup of facility data transactions may be obtained by running the fixed format report AFS
transaction generator workfile (654). This backup transaction file will enable you to resubmit
transactions that may be deleted inadvertently.
3.2.9 Error Reporting
The Batch Edit/Update Process allows as much data as possible is validated and updated to the
database. Those fields in error are highlighted on the Edit/Update Error Report, but if the mandatory
data elements are valid, the record is added or changed (depending on the Update Code). An error
message will be reported for every error encountered in the submittal. Refer to Sections 3.4 and 3.5
for examples of the Edit/Update Edit and Summary Reports.
April 2003 3-11 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.2.10 Accept and Reject Files
The Batch Edit/Update Process creates the Accept, Reject, and Sorted transaction files. In an Edit
job, the creation of Accept, Reject, or Sorted output transaction files is optional. In an Update job,
the Reject file is mandatory and the Accept file is optional. The Sorted transaction file is for Edit
jobs only and is not available in an Update job.
An Accept file is a sequential transaction file, of valid transactions suitable for re-submittal to Edit or
Update. These transactions include all the valid data fields from the transactions submitted by the
user. The invalid, non-mandatory data fields are "blanked out" on the corresponding Accept file
transactions. An Accept file transaction is created for each user-submitted transaction having valid
key field information and at least one updatable data element.
A Reject file is similar to the Accept file, except that it contains copies of the user-submitted
transactions that had errors. Valid non-key data fields are not written to the Reject file transactions;
these go to the Accept file in an Edit job, and to the Accept file and to the database in an Update
job. The erroneous data fields are written, unmodified, to the Reject file transactions. The user can
then use ISPF Edit to correct the transactions and resubmit them to the Edit Process.
The Sorted output file can be selected in an Edit job as an alternative to the Accept and Reject files.
More detailed information regarding the Accept, Reject, and Sorted transaction files is contained in
Section 3.4.3.
April 2003 3-12 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
3.3 AFS Compare Submittal
The purpose of the AFS Compare Submittal is to allow users to create AFS emissions, compliance
and permit transactions on their state system, submit the transactions to AFS and have AFS
determine if the transactions are adds or changes. Delete transactions are not created. The output
file produced from the Compare Submittal may be submitted to the batch Edit or Update to validate
and apply the data to AFS. The Compare Submittal does not perform any updates to AFS.
The Compare Submittal screen is accessed by selecting Option 1, UPDATE THE DATABASE, from
the AFS Main Menu (Figure 3-13), selecting Option 2, BATCH, from the Update Menu (Figure 3-14)
and selecting Option 1, COMPARE from the Batch Update Menu (Figure 3-15).
Compare Selection Criteria
AIRS FACILITY SUBSYSTEM
COMPARE SUBMITTAL
PGM: AFP480
MAP: AFM4801
INPUT FILE NAME:
TRANSACTION FORMAT: 1 (1 = AFS, 2 = AFX)
OUTPUT FILE NAME: EIKASWD .
REPORT OPTION(S):
X GENERATE BEFORE-AFTER COMPARISON REPORT
*IF YOU HAVE CHANGED THE YEAR OF EMISSION INVENTORY, PLEASE INDICATE
DATA TO BE COPIED OVER TO THIS NEW YEAR FROM THE PREVIOUS YEAR:
ALL EMISSIONS DATA, INCLUDING SIP DATA
ONLY ANNUAL EMISSIONS DATA (OMIT SIP DATA)
NO EMISSIONS DATA
PF1=HELP PF3=END PF4=MAIN PF5=TERM
Figure 3-2 COMPARE SUBMITTAL SCREEN
The Compare Submittal screens allows users to select options and submit a batch job. Selections
that may be made are:
input file name
transaction format
output file name
produce a Before-After Comparison report
year of record to be placed on each emissions transaction
type of emissions data to be copied to the new year when
incrementing/decrementing the Year of Emissions Inventory
April 2003
3-13
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
The selection information is validated. Online validation is performed to ensure both file names
have been supplied and that the file names are in valid NCC format. The Input File Name may be a
sequential dataset or a partitioned dataset with a member name specified in parentheses. The first
qualifier of the Output File Name is prefilled with your User ID and Account Code. This qualifier may
not be changed.
A transaction format must be selected. The default selection is AFS Format (1). Two formats for
input transactions are supported; an 80 character AFS transaction and an 120 character AFX
transaction.
AFS Compare Transaction Format (AFS Transaction Format with update codes
blank)
AFX Compare Transaction Format (AFX Transaction Format with update codes
blank)
A Before-After Comparison Report will be created if the user selected to have one printed. The
default is to produce the report. This report will display a snapshot, in the transaction format
submitted, of the database before any changes are applied as well as the changes which have been
requested.
The selections that pertain to emissions transaction types are identifying a Year of Record and the
amount of emissions data to be copied to a new year when the Emissions Inventory Increment field
is supplied on a transaction type 10 sequence 6.
Emissions transaction types must either have a Year of Record specified on each transaction in
columns 14-15 or you must specify a Year of Record on the Compare Submittal screen to be
applied to all of the emissions transactions in the input file. If you specify a Year of Record on the
selection screen, the Compare Submittal will replace all emission inventory year of record (columns
14-15 AFS format, columns 25-26 AFX format) values with the screen selection value. Input files
that do not contain emissions transaction types should leave this selection blank. The selection will
be ignored for non-emissions transaction types.
When an Emissions Inventory Increment value is supplied on a transaction type 10 sequence 6 (AFS
format columns 16-17 or AFX format columns 27-28) and it is different than the Year of Emissions
Inventory on Plant General, special emissions inventory copy processing is invoked during an
update. The Compare Submittal simulates the Update processing to compare your data
appropriately. Emission Inventory data will be compared assuming what AFS will look like if the
copy option was performed. You must select one of the three copy options presented on the
Compare Submittal if your input file contains transaction type 10 sequence 6 transactions that meet
the stated criteria. If you do not select a copy option and the Compare Submittal encounters this
situation all of the emissions transactions for the facility will not be compared and will be appended
to your output file for correction. The copy option: "No Emissions Data" assumes that you are
replacing all stack, point and segment inventory data with new data for the new year specified in the
Emissions Year of Increment columns thus making all these transaction types adds. Whichever
copy option you specify on the Compare Submittal screen should also be selected on the Edit and
Update submittal screens to produce the correct results.
An audit page is produced for each Compare Submittal stating the selection criteria used for the
submittal.
After specifying the criteria and pressing you will be presented with the second screen to
April 2003 3-14 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
specify the Job Control Language (JCL) parameters to execute your Compare Submittal. The JCL
parameters are validated and the JCL is generated to execute the Compare Submittal in batch (refer
to Figure 3-3).
DATE : 06/15/95
SCREEN: U4802
AIRS FACILITY SUBSYSTEM
COMPARE SUBMITTAL
PGM: AFP480
MAP: AFM4802
PLEASE MAKE ANY NECESSARY JCL MODIFICATION
ACCOUNT CODE : ASWD
FIMAS ID : AFSED
TIME ( MMMM SS ) : 1
PRIORITY CODE : 2
MSGCLASS : P
NUMBER OF COPIES : 1
FORM NUMBER :
ROOM/BIN NUMBER : MEIK
HOLD OUTPUT? (Y/N): Y
PRINTER SITE ID : R255
ASWD
AFSED
5 0
2
A
1
MEIK
Y
R255
PRESS ENTER TO SUBMIT JOB
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PGUP
Figure 3-3 COMPARE SUBMITTAL JCL PARAMETERS SCREEN
Compare Functionality
The Compare Submittal compares the user supplied input workfile of AFS or AFX format
transactions to the AFS database and assigns an update code of "A" (add) or "C" (change) to each
transaction. The output file will contain the transactions in the selected format with update codes
applied. Transactions that would not alter the database are not written to the output file. The
comparison is performed field by field to enable individual fields to be removed from the output file
(blanked out) if they match the field value which is already contained on the data base. This
improves the batch update efficiency. The output file created by the comparison may subsequently
be submitted to the AFS batch edit/ update process.
The Compare Submittal performs a comparison of the data submitted and the data in AFS,
it does not update AFS. The adds and changes produced in the Compare have not been
validated except for the conditions stated below. The independent Batch Edit and Update
perform the validations to determine whether to apply the data to AFS.
Transactions containing Number Generation requests are accepted in the Compare Submittal.
Stack, Segment, Action and Comment Numbers may be generated using 9's as their field value.
These transactions will have an 'A' update code applied and are appended to the end of the output
file preceding any transactions found to be in error. The Number Generation transactions are
written to the file in the order in which they were submitted. Note that there are limits to the
number of number generation requests that may be submitted at one time in the Edit and Update
Submittals. Refer to Section 3.4 for specifics.
Validations
April 2003
3-15
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
The Compare Submittal performs very few data validations. The majority of data validation is
performed by the Batch Edit and Update software. Transactions found to be in error during
Compare Submittal processing are written to the end of the output file for correction. The errors
that will be reported are:
Transactions that are submitted with a value in the update code field (AFS format -
column 80; AFX format - column 1). Update codes must be blank. The original
transactions are written to the output file for correction.
Transactions that are submitted with invalid transaction types (AFS format - column
11-12; AFX format column 22-23). Transaction types must not only be a valid type
but be submitted with a valid sequence number for the transaction type. The
original transactions are written to the output file for correction.
If no copy option was selected and an emissions transaction type 10 sequence 6
had a value in the Year of Increment field different from the value in the Year of
Emissions Inventory on Plant General, the 10-6 transaction is reported as an error
and all other emissions transactions for that facility are not compared or reported
but are written to the end of the output workfile. Compliance and Permit
transactions submitted for the same facility will be compared.
Emissions transactions that do not have a valid Year of Record entered in columns
14-15 and the user did not specify a Year of Record on the Compare Submittal
screen.
Transactions submitted in AFX format that are not for update to a Direct Data
Merged state.
Compare Submittals produce a Before - After Comparison Report, upon request, for user review. If
the transaction is an add, the input transaction is displayed in the transaction format submitted
(AFS or AFX). If the transaction is a change two lines are printed. The first transaction listed
displays a before picture of the existing database values. The second transaction displays the
proposed changes to the database as a result of the comparison between the transaction submitted
and the existing database values.
Refer to the following figures for examples of AFS and AFX Before - After Comparison Reports and
Compare Transaction Status Reports.
April 2003 3-16 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Report Formats
The following figures show the report outputs produced from the Compare Submittal:
Figure 3-4 AFS Before-After Comparison Report - Audit Report
Figure 3-5 AFS Before-After Comparison Report - Non-Permit Transactions
Figure 3-6 AFS Before-After Comparison Report - Permit Transactions
Figure 3-7 AFS Compare Transaction Status Report - Non-Permit Transactions
Figure 3-8 AFS Compare Transaction Status Report - Permit Transactions
Figure 3-9 AFX Before-After Comparison Report - Audit Report
Figure 3-10 AFX Before-After Comparison Report
Figure 3-11 AFX Compare Transaction Status Report
April 2003 3-17 Batch Updating
-------
ro
o
o
CO
DATE : 04December 1995
TIME : 11:06:09.8
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
FACILITY SUBSYSTEM
INPUT FILE NAME:
TRANSACTION FORMAT: 1
OUTPUT FILE NAME:
EIKA026.SRF739.INP521C.AFS
(1 = AFS, 2 = AFX)
EIKA026.SRF739.OUT521D.AFS
O
c
CL
(D
C
u
TJ
m
TJ
O
REPORT
BEFORE AFTER COMPARISON REPORT
CO
00
en
c
3
CO
i
C/)
O
O
TJ
C/)
O
x
OPTIONS APPLICABLE TO EM^gJOJf 5gA|SASTJ8NgFS _ 25/26_AFX ARE BLANK ON EMIS
YEAR OF RECORD: 91
*IF YOU HA-VE effiNGieNTHiA5EARI6i;LIfiIIglgiPINlAl'NTORY, PLEASE INDICATE
DATA TO BE COPIED OVER TO THIS NEW YEAR FROM THE PREVIOUS YEAR.
X
TRANSACTION ENTERED ON 12/04/95 AT 11:05:33.9
ONLY ANNUAL EMISSIONS DATA (OMIT SIP DATA)
NO EMISSIONS DATA
AFS COMPARISON AUDIT REPORT
TRANS. IF VALUED, OVERRIDES COLS 14/15-AFS, 25/26-AFX)
DO
a>
r-t-
O
3"
Q.
o>
CQ
00
D
a>
r-t-
a>
00
r-h
o
05
CQ
(D
-------
ro
o
o
CO
CO
CD
DO
o>
r-t-
o
3-
Q.
o>
CO
(Q
C
3
CO
Ul
C/)
00
m
-n
O
33
m
m
•33
O
O
1
5
V)
o
33
m
TJ
O
TJ
m
3
o
V)
DATE : 04December 1995
TIME : 11:06:09.9
* NOTE * UPDATE EDITS
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
FACILITY SUBSYSTEM
HAVE NOT
PAGE : 2
YET BEEN APPLIED. THE FORMAT FOR REPORT SEQUENCE WILL BE AS FOLLOWS :
THE FIRST CARD LISTED WILL DISPLAY A BEFORE
THE SECOND CARD LISTED
WILL DISPLAY A VIEW
CNTY PLNT TRANS -TYPE
ST 1
0 345 67890
9§g
99
99
999 XXXXX
99 999 XXXXX
99
999 XXXXX
99 999 XXXXX
99
999 XXXXX
TRANSACTION ENTERED ON
12
50
50
51
51
15
15
15
15
17
12/04/95
SEQU-NO
3
2
2
1
1
1
1
3
3
1
AT 11:05:33
APS BEFOREg- AB5HS8XCOMPARISON REPORT 2
99
999 XXXXX
99 999 XXXXX
99
999 XXXXX
99 999 XXXXX
99
999 XXXXX
99 999 XXXXX
99
17
17
17
17
20
20
1
1
2
2
1
1
PICTURE OF THE DATABASE VALUES .
OF THE PROPOSED CHANGES TO THE DATABASE VALUES.
CARD COLUMNS :
234567
456789012345678901234567890123456789012345678901234567890123456789
ABC MAIN STREET 001
ABC 809 LINCOLN AVE
ABC LANDFILL ABC
ABC ABC LANDFILL
ETTIENE PAINT SUPPLY FABRICATION INC.
ACME PAINT INCORPORATED
098090684AA
876866876AS
001CCOMMENT 001 C NN
001CCOMMENT 001 C ALL THE WAY TO THE END OF THE AVAILABLE XY
. 9
001EERED. ALL FOUR LINES WILL BE FULL FOR ALL SIXTY CHARACTE
001EEMISSIONS
002CCOMMENT 002 C NN
002CCOMMENT 002 C TOTALLY FULL LINE, NO EXTRA SPACE ON THEXY
002CCOMPLIANCE
002CCOMPLIANCE FA, LALA, LALA, LALA, LALA END OF THE LINE WOW
00109878770034000002450133N02341D STACK 001
001 Y
UPDATE- CODE
8
0
C
C
C
C
C
C
C
C
C
UPDATE
NOTE
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
C
(/)
(D
—i
(f>
O
c
CL
(D
CO
D
o>
CO
r-h
o
—i
o>
CQ
(D
-------
ro
o
o
CO
C
(/)
(D
—
CL
(D
CO
ro
o
DO
o>
r-t-
O
3-
Q.
o>
CO
C/) -n
>(5'
31
O co
C/)
00
m
-n
O
33
m
m
•33
O
O
33
V)
O
•2.
•33
m
TJ
O
TJ
m
•33
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
DATE : 04December 1995 FACILITY SUBSYSTEM
TIME : 11:06:09.9
* NOTE * UPDATE EDITS HAVE NOT YET BEEN APPLIED. THE FORMAT FOR REPORT SEQUENCE WILL BE AS FOLLOWS :
THE FIRST CARD LISTED WILL DISPLAY A BEFORE PICTURE OF THE DATABASE VALUES.
THE SECOND CARD LISTED WILL DISPLAY A VIEW OF THE PROPOSED CHANGES TO THE DATABASE VALUES.
ST,
12
9§9
99
99
99
99
99
CNTY
345
999
999
BEFORE9-
999
99 999
TRANSACTION
99
99
99
99
99
99
99
99
99
99
99
99
999
999
999
999
999
999
999
999
999
999
999
999
AFS PLANT ID
1 2
678901234567890
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
AKSKKXK8MEXKXX8H
XXXXXXXXXXXXXXX
PAGE
2
TRANS-TYPE SEQU-NO CARD COLUMNS : UPDATE-CODE UPDATE
34567 8 NOTE
12 3 45678901234567890123456789012345678901234567890123456789 0
A2
A2
A2
A2
Al
Al
REPORffil- PERMIT
Al
XXXXXXXXXXXXXXX A8
XXXXXXXXXXXXXXX A8
ENTERED ON 12/04/95 AT 11:05:33.9
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
XXXXXXXXXXXXXXX
A8
A8
A8
A8
A8
A8
A8
A8
A8
A8
A8
A8
3
3
4
4
1
1
2
2
2
2
2
2
TRANSACTIONS
5 2
1
1
2
2
3
3
8
8
1
2
3
5
6
7
THIS IS THE
ONE
THE SECOND
TWO
FIRST PERMIT AUTH DATA ELEM.
PERMIT AUTHORITY DATA ELEMENT
RNI PS 03 ALEXANDER ROBERT CHAPMAN
NNBEC01DAVE
IT WAS A COLD AND STORMY DAY THAT DAY . . .
THREE
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
FULLAPPLICATION2
2
2
2
2
2
2
2
2
2
2
2
2
XX00104 VALERIE EUGENIY
XX001 DAVE
XXOO 10 11 99 00 10 11 99 01 010
XX001 19901010
XX001ABC-XYZ-12
XX001ABC
XX001
XX001ONE
XX001 DAVE
XXOO 10 11 99 01 01 01 99 01 010
XX001ABC
XX001ONE
XX001TWO
XX001THREE
C
C
C
C
C
C
C
C
A
A
A
A
A
A
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
BEFORE
AFTER
ADD
ADD
ADD
ADD
ADD
ADD
CO
D
o>
CO
r-h
o
—i
o>
CQ
(D
-------
^>
^3
ro
o
CO
CO
ro
— *
DO
o>
r-t-
O
3-
C
Q.
o>
r-t-
^
CO
H
2
C/)
0 3!
Hen
O =
2
C/) w
>j
w
-n
C/)
0
O
TJ
31
m
H
3]
2
C/)
*-»
__|
O
C/)
H
^
C
C/)
3]
m
TJ
O
3D
H
2
o
TJ
m
i
H
DATE : 04December 1995
TIME : 11:06:01.7
ALL TRANSACTIONS IN
NOTE :
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS) PAGE : 1
FACILITY SUBSYSTEM
THIS REPORT HAVE BEEN APPENDED TO THE END OF THE COMPARED OUTPUT FILE. THESE TRANSACTIONS
CNTY PLNT TRANS-TYPE SEQU-NO CARD COLUMNS: UPDATE-CODE
ST 1
0 345 67890
WE^E-UNABL-E-Te-BE-GeMPAREB-ANB
50
99
* TRANSACTION ERROR MESSAGE
51
99
* TRANSACTION ERROR MESSAGE
999 XXXXX AB
99
* TRANSACTION ERROR MESSAGE
TRANSACTION ENTERED ON 12/04/9
AFS COMPARE TRANSACTION STATUS
999 XXXXX 10
99
* TRANSACTION ERROR MESSAGE
999 XXXXX 11
99
* TRANSACTION ERROR MESSAGE
999 XXXXX 14
99
* TRANSACTION ERROR MESSAGE
999 XXXXX 15
99
* TRANSACTION ERROR MESSAGE
999 XXXXX 16
99
* TRANSACTION ERROR MESSAGE
234567 8
12 456789012345678901234567890123456789012345678901234567890123456789 0
MUST BE GQRREGTEB 6R THEY WILL REiJEGT IN THE EBIT/UPBATE .
5 ABC 1ABCDEFGH900909900808900707900606
3
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
4 ABC TUCSON 04989879877
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
1 001MCO ACTU 1
: INVALID TRANSACTION TYPE.
5 AT 11:05:33.9
REPORT
A MAIN STREET 07940
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
3 PT ACTU 1 N
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
4 A900909BCD987090900808689700900909901111987 654 901212 N
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
5 MAIN STREET BUCKEYE 04
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
6 001001FS VOC
: INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
C
(D
—i_
O
E
CD
J,
^-l
GO
D
o>
r-h
o>
CO
r-h
o
05
CQ
CD
-------
ro
o
o
CO
CO
ro
ro
DO
o>
I— h
O
^~
c
Q.
Q)
CQ
IT,
2
c/)(5'
J> C
o 3
z! w
0<3o
2 ^
C/) >
Tl
C/)
0
o
TJ
^^
TJ
m
H
|
f/)
^
g
o
£
H
C
C/)
TJ
m
TJ
O
H
1
TJ
m
TJ
^
H
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
DATE : 04December 1995 FACILITY SUBSYSTEM
TIME : 11:06:01.6
ALL TRANSACTIONS IN THIS REPORT HAVE BEEN APPENDED TO THE END OF THE COMPARED OUTPUT
NOTE :
CNTY AFS PLANT ID TRANS -TYPE SEQU-NO CARD COLUMNS :
ST 12 3456
0 345 678901234567890 12 3 4567890123456789012345678901234567890123
WERE UNABLE TO BE COMPARED AND MUSTABE CORRECTED OR THEY WILL REJECT TNREHE EDIT/UPDATE.
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX Al A 2 BOB
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX Al B 2 ONE
99
AFS TBHBSRETTeMNERE^EOMESSAfflBS:REBS!Rl!ID SEeMEraCERHNBREBIEQB SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX Al 92 TWO
TMAN§ACJ38gTEggEggg0gNMJ2^£4,E95 $HVftii65SEQ'UENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX A7 A 2 2
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX A8 A FULLAPPLICATION2 XX001TWO
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
999 XXXXXXXXXXXXXXX A8 B FULLAPPLICATION2 XX001THREE
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
PAGE : 1
FILE. THESE TRANSACTIONS
UPDATE -CODE
7 8
4567890123456789 0
SHARON
999 XXXXXXXXXXXXXXX B9 62 001THE FIRST COMMENT. THE SECOND LINE, -
99
* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
C
(D
—i_
O
c
CL
(D
>
~n
00
D
Q)
r-t-
O>
00
r-h
o
05
CQ
(D
-------
ro
o
o
CO
DATE : 04December 1995
TIME : 11:21:23.3
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
FACILITY SUBSYSTEM
INPUT FILE NAME:
TRANSACTION FORMAT:
OUTPUT FILE NAME:
EIKA026.SRF739.INP521C.AFX
(1 = AFS, 2 = AFX)
EIKA026.SRF739.OUT521D.AFX
O
c
CL
(D
u
m
TJ
O
REPORT
BEFORE AFTER COMPARISON REPORT
CO
So
CO
CQ
C
3
CO
tfl
X
O
O
TJ
5
o
X
OPTIONS APPLICABLE TO EM^gJOJf 5gA|SASTJ8NgFS _ 25/26_AFX ARE BLANK ON EMIS
YEAR OF RECORD: 91
*IF YOU HA-VE effiNGieNTHiA5EARI6i;LIfiIIglgiPINlAl'NTORY, PLEASE INDICATE
DATA TO BE COPIED OVER TO THIS NEW YEAR FROM THE PREVIOUS YEAR.
X
TRANSACTION ENTERED ON 12/04/95 AT 11:20:50.3
ONLY ANNUAL EMISSIONS DATA (OMIT SIP DATA)
NO EMISSIONS DATA
AFX COMPARISON AUDIT REPORT
TRANS. IF VALUED, OVERRIDES COLS 14/15-AFS, 25/26-AFX)
DO
a>
r-t-
O
3-
C
•D
a.
a>
ca
00
D
a>
r-t-
a>
00
O
05
CQ
(D
-------
^>
~Q
—1
ro
o
o
CO
CO
ro
^^
DO
o>
r-t-
O
3-
c
Q.
o>
r-t-
^
CD
Tl
(5'
c
^
CO
0
^
-n
x
00
m
-n
O
•33
m
^
Z]
^
m
"
O
O
g
TJ
^
30
pT
o
3]
m
^0
o
3J
EPA AEROMETRIC
DATE : 04December 1995
TIME : 11:21:23.6
INFORMATION RETRIEVAL SYSTEM (AIRS)
FACILITY SUBSYSTEM
PAGE : 2
* NOTE * UPDATE EDITS HAVE NOT YET BEEN APPLIED. THE FORMAT FOR REPORT SEQUENCE WILL BE AS FOLLOWS :
THE FIRST CARD LISTED WILL DISPLAY A BEFORE PICTURE OF THE DATABASE VALUES.
THE SECOND CARD LISTED WILL DISPLAY A VIEW OF THE PROPOSED CHANGES TO THE DATABASE VALUES.
TT S
U?O RY E
DD AP Q
TE ST CNTY AFS PLANT ID NE # CARD COLUMNS :
0 12 34
1 23 456 789012345678901 23 4 567890123456789012345678
1
567890
90123456789012345678901234567890123456789012345678901234
UN
PO
1 feT^E
1 2
5678901234567890
A2 3 2 THIS IS THE FIRST PERMIT AUTH DATA ELEM.
C 99 A2 3 2 ONE
99
BEF
AFT
A2 4 2 THE SECOND PERMIT AUTHORITY DATA ELEMENT
C 99 A2 4 2 TWO
99
50 2 ABC MAIN STREET
C 99 50 2 ABC 809 LINCOLN
99
51 1 ABC LANDFILL ABC
C 99 51 1 ABC ABC LANDFILL
TRANSACTION ENTERED ON 12/04/95 AT 11:20:50.3
AgX BJFQ.RE xXaX1X1Sxx'$Sffia8x-S85! 5EgORT NNBECOIDA
99 999 XXXXXXXXXXXXXXX Al 1 2
IT WAS A
C 99 999 XXXXXXXXXXXXXXX Al 5 2 THREE
99 999 XXXXXXXXXXXXXXX Al 5 2
C 99 999 XXXXXXXXXXXXXXX A8 1 FULLAPPLICATION2
99 999 XXXXXXXXXXXXXXX A8 1 FULLAPPLICATION2
C 99 999 XXXXXXXXXXXXXXX A8 2 FULLAPPLICATION2
99 999 XXXXXXXXXXXXXXX A8 2 FULLAPPLICATION2
C 99 999 XXXXXXXXXXXXXXX A8 3 FULLAPPLICATION2
99 999 XXXXXXXXXXXXXXX A8 3 FULLAPPLICATION2
C 99 999 XXXXXXXXXXXXXXX A8 8 FULLAPPLICATION2
99 999 XXXXXXXXXXXXXXX A8 8 FULLAPPLICATION2
A 99 999 XXXXXXXXXXXXXXX A8 1 2 2
A 99 999 XXXXXXXXXXXXXXX A8 2 2 2
001
AVE
VE
COLD AND STORMY DAY THAT DAY . . .
XX00104 VALERIE EUGENIY
XX001 DAVE
XXOO 10 11 99 00 10 11 99 01 010
XX001 19901010
XX001ABC-XYZ-12
XX001ABC
XX001
XX001ONE
XX001 DAVE
XXOO 10 11 99 01 01 01 99 01 010
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
BEF
AFT
ADD
ADD
§§
C
CD
—i_
C
CL
CD
CO
D
o>
r-h
o>
CO
r-h
o
05
CD
CD
-------
ro
o
o
CO
en
c
3
CO
DATE : 04December 1995
TIME : 11:21:12.3
EPA AEROMETRIC INFORMATION RETRIEVAL SYSTEM (AIRS)
FACILITY SUBSYSTEM
ALL TRANSACTIONS IN THIS REPORT HAVE BEEN APPENDED TO THE END OF THE COMPARED OUTPUT FILE. THESE TRANSACTIONS
NOTE :
TT S
UPO RY E
DD AP Q
TE ST CNTY AFS PLANT ID NE # CARD COLUMNS :
WBRE UNABLE TO1BE COMPARED AND MUST BE CORRECTED OR THEY BILL REJECS1 IN THE EDIT/UPDATES
1 23 456 789012345678901 23 4
A2 9 2 THREE
99* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
C
CD
C
CL
CD
CO
ro
01
X
O
o
•33
m
33
V)
O
V)
c
V)
33
m
TJ
O
50 5 ABC 1ABCDEFGH900909900808900707900606
99* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
51 4 ABC
TUCSON
04989879877
99* TRANSACTION ERROR MESSAGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
TRANSACTION ENTERED ON 12/04/95 AT 11:20:50.3
AFX COMPARE TRANSACTION STATUS REPOETMCO ACTU 1
99*9W^xx-xIxx%Sx-x'x-xMft:is$aE : INVALID TRANSACTION TYPE.
021E01021P THIS IS A BAD TRANSACTION AND SEQUENCE NUMBER
99*9W^XX-SxX%Sx-x'x-XMft:iSDaE : INVALID TRANSACTION TYPE.
BOB SHARON
99*95§ASxftSS2Hx5SS2SxMfiSsSa5 : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
ONE
99*9?§AHxASx2HxSSS2SxMfifSSGE : INVALID SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE.
DO
a>
r-t-
O
3"
Q.
o>
CQ
CO
D
a>
r-t-
a>
CO
r-h
o
05
CQ
(D
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4 Batch Edit/Update Process
3.4.1 Introduction
The AFS Batch Edit/Update Process has been completely re-designed. This section describes this
new process in detail.
3.4.1.1 What Has Changed
• New Menus / Screens for batch job submission.
• Supported Transactions - CDS and NEDS format transactions are no longer supported.
AFS transactions and the new AFX (an extended AFS format) transactions are used in the
new system.
• Separate Processes - For Edit, Update, and Compare, each invocation of the process
generates a single batch job. The 'dummy update' has been replaced by a new Edit process
designed solely for the batch editing task.
• Compare Process - The Compare Process processes all AFS or AFX Compliance,
Emissions, and Permits transactions - not just Emissions transaction types. It also supports
the option of retaining no emissions data in the new current year when incrementing the
Emissions Inventory Year of Record.
• Field Level Updating - Some transactions will no longer be subject to "all or nothing" editing.
Where it is practical to do so, correct data from a transaction that also contains errors will
be allowed to update the AFS Database.
• Edit and Update Reports - Edit and Update perform the same validations (depending on edit
level chosen), and produce the same Edit report. No Regional or National reports are
produced. Rather, the new Notification process may be used to send report copies to other
users.
• Critical Data Element (CPE) Reports - The CDE processing produces the same CDE report.
However, the report is no longer produced automatically as part of the Batch Update. It is
now solely a Fixed Format report.
• New Processing Options For Update
Job Submission by Users: You can submit a batch Update (as well as a batch Edit) job any
time that the system is available. This choice is now also available for the updating of utility
transactions that are created "online."
Central Support Submission: As an alternative to submitting your own jobs, you can
request that your transactions be run as part of the nightly (Monday - Friday) Central
Update. An individual job will be created for each person's file of transactions. Your job
will be monitored by one of the AFS Production Control Staff.
User-Controlled, or Automatic Submission for Online Utilities: You can be an "Automatic
User," which is the default arrangement.. The Online Utilities that you run generate
transactions that are automatically included in the Central Update. Or, if you wish, you can
be defined as a "Manual User," in which case transactions generated by the Online Utilities
April 2003 3-26 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
will be written to a file you name, and processed by an Update job that you submit. Users
are defined as "Manual Users" via a Special Access Code of "P" entered on their User Profile
record.
• Increased Reliability - As stated above, a separate job is created for each person's file of
transactions, regardless of whether the job is submitted immediately by the user, or later as
part of the Central Support Submission. The "lone, large, long" nightly job has been
eliminated. If one agency's transactions encounter problems, the processing of other
transactions is not affected.
• Flexibility for the Future - A new transaction format has been added to AFS. The new "AFX"
format supports an expanded 120-character record. It uses a 15-character AFS Plant-ID. It
will also accommodate a future modification to AFS that will expand the size of the Stack,
Point, and Segment number fields.
• Alternate User Notification - This is actually two new capabilities. You can specify that a
copy of the Edit or Update reports be printed for another user by specifying an Alternate
User ID. You also can indicate, through the new Notification component of the State-Code
table, that you want to receive a "message" when another user submits data with your state
code.
• Batch Update to Assign AFS Plant ID - The AFS plant ID has been added to transaction 10,
sequence 1, and provides a mechanism for any user with update access to assign this ID.
Previously, it could only be assigned interactively or with a special utility executed by TRC.
3.4.1.2 Edit Work Group Recommendations Added
Edit changes recommended by the Edit Work Group have been incorporated into the New AFS
Batch Edit processing. These include the following:
• City Code or City Name - Either code or name must be supplied to add a plant. If the city
code is entered, it is validated as an existing city code for the state-county combination. If
the city code is valid for the county, then the corresponding city name is retrieved from
AIRS GEO-COMMON, and is saved on the PLANT-GENERAL record. If both code and name
are supplied, the user-entered city name is flagged with an error, and is ignored.
• ZIP Code - ZIP Code is not required to add a plant.
• Geographic Coordinates - At both plant and stack level, if the latitude or longitude is
outside the range for the county, as defined in AIRS GEO-COMMON, the values may be
updated to the database, but a warning message is given. If the values are outside the
range for the state as well, an error message is given, and the values are invalidated.
• Plume Height - Stack height, stack diameter, and plume height may all be stored whenever
they are reported.
• Skipped Year of Emissions - The system has been modified to allow the "in-filling" of a
missing emissions year when there are both earlier and later emissions years already
entered. For example, emissions data for 1991, 1992, or both, may be created when only
1990 and 1993 currently exist for a plant.
April 2003 3-27 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4.1.3 Overview
The basics of entering data into AFS via batch updates are similar to what they were previously:
Enter your AFS or AFX format transactions into a file on the NCC mainframe. This file can
be either a sequential data set or a member in a partitioned data set (fixed length, blocked
format, record length = 80 for AFS, 120 for AFX).
You can run Edit, followed by a separate Update (see Charts 1 and 2). Make corrections to
your transactions until one or more passes edit level 3. The Edit reports will flag all of your
errors. Utility-generated transactions do not require a separate Edit job - they are generated
error-free by the online processes.
Alternatively, you can run Update without having run the separate Edit job. Update
automatically performs all the same validations that Edit does, and then updates the valid
transactions to the database.
If you wish to run the Compare Process against your AFS or AFX transaction data set,
invoke that process first. Then submit the Compare output data set to the Edit and Update
processes.
Submit your transactions for update. You can submit and monitor the Update job yourself
or request that your data be included as part of a nightly Update job.
Track the status of your Edit and Update jobs by using the Notification screens.
The following pages show you how to submit AFS or AFX transactions for the Compare Process,
Batch Edit, and Batch Update processing, and how to use the Notification screens. The procedures
for creating a data set profile under Resource Access Control Facility (RACF) are also included. If
you have any questions, please call the AFS Help Line at: 1-800 367-1044.
April 2003 3-28 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
Chart 3-1 Batch Edit/Update Screen Flow
Actions Available
Restart A Job
Cancel A Job
Reprint Reports
Delete Messages
Submit A Utility File
View Error Summary
View Trans. Summary
April 2003
3-29
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
Chart 3-2 Utility Transaction Screen Flow
"Automatic" User
Do Nothing! Your transactions
will be submitted overnight.
AFS
MAIN MENU
UTILITY SELECTION
MENU
UTILITY
FILE NAME
PERFORM
ONLINE UTILITY
"Manual" User
i
UPDATE SUBMITTAL
EMISSIONS OPTIONS
BATCH
SUBMITTAL JCL
BATCH
SUBMIT CONFIRM
April 2003
3-30
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
3.4.2 Invoking the New AFS Batch Update Processes
This section describes the steps required to access the new AFS Batch Update processes:
Compare, Edit, Update, and Notification. Figures 3-12 through 3-15 contain the AIRS Main Menu,
the AFS MAIN MENU, the AFS UPDATE MENU, and the AFS BATCH UPDATE MENU, and describe
the steps required to reach the process that you want to use.
STEP 1:
0^/24/96 Aerometrk Information Retrieval 5ystem AAPOOO
lv|ain lv|enu
I. Air duality (A
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
PATC. :
AE.5 FACILITY 6U&5Y6TtM
MAIN MtNU MAP:
PQ4 ffPOOO
I UPPATtTitPATA&A5E.
2. &R.£A\/5L Tit PATA&A5E.
3 5LLLCT A KLPOKl
A 5LLLCT A UTILITY
LNTtG. MtNU ^JULCTlM. l_
NtLP A6616TANCL? CALL Tilt Af5 ilLLPLlNt AT \-SOO-367-\OM
Pri=iltLP
PF5=TtRJv|
Instructions
Enter "1" to select "UPDATE THE DATABASE".
April 2003
3-32
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 3:
PATL 02/24/96 AIR.5 FACILITY 5U&5Y6Ttlv| PC, M: AfPOII
5CR.LLN: 01 AF6 UPPATt MtNU MAP: AfTv|OOII
IMMUNE.
2.&ATOJ
LNTLG. MtNU 5LLLCTI^N: 2
PH=iltLP
Instructions
Enter "2" to select "BATCH".
April 2003
3-33
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 4:
PATL 02/24/96 AIR.5 FACILITY 5U&5Y6Ttlv| PQ4 AfPOI2
: 012 Af5 &ATOJ UPPATE. lv|t^U MAP: AfTv|OOI2
2.LPIT
4.UPPATt
S.N^TflCATI^N
LNTLG. MtNU 5LLLCTI^N: 2
' OP-[\M tiffl AVAIUX&LL
Instructions
To invoke the Compare Process,
enter "1".
To invoke Edit,
enter "2" .
To invoke Update,
enter "4" .
To invoke Notification,
enter "5" .
April 2003
3-34
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
3.4.3 Submitting an Edit Job
The AFS BATCH EDIT screen (Figure 3-16) is invoked by selecting option "2. EDIT" on the AFS
BATCH UPDATE MENU (Figure 3-15). You will use the AFS BATCH EDIT screen to specify input and
output files and other options. Instructions are included for completing this screen, as well as the
EDIT SUBMITTAL (YEAR OF RECORD) screen (Figure 3-17) and the BATCH SUBMITTAL (JCL
Parameters) screen (Figure 3-18). The final screen of this section is the confirmation BATCH
SUBMITTAL screen (Figure 3-19) for your Batch Submittal job.
STEP 1:
PATL 02/24/96
-SCELLNl: ADA
AIR.5 FACILITY 5U&5Y6TLM
Af5 &ATOJ LPIT MAP: AfTv|0404
INPUT FLL NAML A&CA026.texpLant«cs0995_
INPUT FILL TYPL I I = PU&LC 2 = PRJVATL
TE.AN5ACTI^N F^R-MAT: I I = Af5 2 = AfX
LPITLLVLL 3
OUTPUT FILL PELFLELMCL (0PTI0NAL)
5^RTLP FILL NAML A&CA026..
(M.
ACCLPT FILL NAML A&CA026. _
ANP
RLJLCT FILL NAML ABCA026. _
PFi=ilLLP PF3=LNP
PF5=TLG.M
Instructions
Use this screen to specify input and output files and other options. Complete this screen by
entering the name of the file containing your AFS transactions. Change any of the default
values as needed. Use the TAB and BACK TAB keys to move to the fields you wish to
change. Press ENTER when finished.
INPUT FILE NAME: This is the name of the file containing the AFS or AFX transactions
that you want to submit for Editing. This file can be either a sequential data set or a
member in a partitioned data set (fixed or variable length, blocked format). When you have
completed this screen and press ENTER, the system will verify that this file exists.
April 2003
3-35
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
INPUT FILE TYPE: The default setting is "1" (Public), which will allow notified users to print
a copy of the Edit report for this job from the Notification screen. They can also view
Transaction and Error summary screens. Entering 2 will cause your edit and update reports
(which report the data that is input to the job) to be marked as private. Only the job owner
can print the reports, or view the summary screens, for a private job. Other users may by
notified of the job's status, but they may not print or view the results.
NOTE: This field is not a substitute for the NCC's RACF security. If you have strict
security needs, contact your Resource Security Administrator or the AFS
Help Line. The default for this field is: 1, Public.
TRANSACTION FORMAT: The default for this field is: 1,AFS. This is the current format.
The AFX format supports the new, expanded 120-character record format. The AFX format
is designed to support the 15-character AFS Plant-ID as the key Plant-ID on all transaction
types. It will also accommodate a future modification to AFS that will expand the size of the
Stack, Point, and Segment number fields to five characters.
EDIT LEVEL: Editing of transactions can be performed at three levels of complexity.
Transactions accepted at level Swill be accepted by the Update process, provided that
changes to the data in the database have not been made between the time the Edit and
Update batch jobs were run. The default is 3.
Level 1: Validates the values for individual fields.
Level 2: Validates the values for individual fields and relationships between
multiple transactions. Level 2 edits also check for duplicate
transactions.
Level 3: Level 3 editing performs level 1 and 2 edits, plus validation against
the AFS database values at the time that the Edit is run. The level 3
edit capabilities are not as extensive as those of the update and,
therefore, may not always recognize the relationship between a
precedent data item and subsequent data within a transaction file.
Should this occur, disregard the level 3 edit error.
SORTED FILE NAME, ACCEPT FILE NAME, AND REJECT FILE NAME: All of these
files are optional; there are no default values. If a file name is entered, a new file will be
created. You would enter a Sorted File Name to obtain a file of all of your transactions that
were in the input file, sorted in processing sequence. Accept and Reject files may only be
specified for edit level 3. Both the Accept and Reject File Names must be entered for this
option. The Accept file contains the transactions that pass Edit Level 3. The Reject file
contains the transactions that do not pass Edit Level 3. The transactions in the Accept file
can be processed through Update at any time. You can update these Accept file
transactions to the database while errors on the Reject file transactions are being corrected.
Any file names entered will be checked to verify that they do not already exist.
April 2003 3-36 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Validations
BOTH ACCEPT & REJECT FILE NAMES REQUIRED FOR THIS OPTION.
Both files must be specified for this option.
DUPLICATE FILE NAMES ARE NOT ALLOWED.
The same file name cannot be entered more than once on this screen.
ENTER 1 OR 2.
FILE-TYPE must be "1" or "2".
FILE-FORMAT must be "1" or "2".
ENTER 1, 2, OR 3.
EDIT-LEVEL must be "1" or "2" or "3".
FILE EXISTS. CHANGE NAME OR DELETE BEFORE SUBMITTING.
The Batch system creates new output files for each submit, in order to avoid
accidently overwriting existing files.
FILE IS PARTITIONED, A MEMBER NAME IS REQUIRED.
Enter the correct member name.
FILE NAME IS INVALID.
This message is displayed for one or more of the following:
Blank(s) within the file name.
The first character of each qualifier must be A - Z, or "#", "$", or "@".
Position 2 - 8 of each qualifier must be either A - Z, 0 - 9, "#", "$", "@" or
FILE NAMES ARE LIMITED TO 5 QUALIFIERS OR LESS.
More than five qualifiers were specified on the Load file.
INPUT FILE IS REQUIRED.
The Load file name is blank.
MEMBER NAME INVALID. FILE IS NOT A PDS.
Sequential files are not allowed to have member names.
MEMBER NAME MUST BE 8 CHARACTERS OR LESS.
The member name specified has more than eight characters.
MEMBER NOT FOUND. CHECK THE SPELLING
Member names must be entered exactly as they appear on the NCC mainframe.
NO FILE WITH THIS NAME EXISTS. CHECK THE SPELLING.
Confirm the full name of the file on the NCC mainframe that contains your Load
transactions.
April 2003 3-37 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
NOT VALID WHEN SORT FILE OPTION SELECTED.
Accept and Reject output file options cannot be entered if the Sorted output file
option is entered.
ONLY VALID FOR EDIT LEVEL 3.
Accept and Reject output file options can only be specified for Edit Level 3.
April 2003 3-38 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
PATt 02/2/1/96 AIR.5 FACILITY 5U&5Y6Ttlv| PC, M: AFP420
5CR.ttN: 420 tPIT 5U&MITTAL MAP: Af M&420
YtAE.
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 3:
PATL :
5CG.LLN: 430
AIG.5 FACILITY 5U&5Y6TLM
&ATCJJ 5U&MITTAL MAP: AFM0430
PLLA5L MAUL ANY NLCL55AG.Y JCL MODIFICATION
ALTLG.NATL U5LG. IP :
jo& NAML : A&C LPITI
ACCOUNT CODL : A026
F1MA6 IP : Af5CP
TIMt ( MMMM AA ) : 200 00
PGJOGJTYCOPL :2
MAC, CLA55 : A
NUM&LG. OF COPIL5 :|_ _
FOG.M NUM&LG. :
G.OOM/&IN NUM&LG. :&I23
ilOLD OUTPUT? (Y/N> Y
PG.lNTLG.5ITL IP : R255
PG.L66 LNTLG. -[0 5U&MIT JO&
PFI=ULLP
Instructions
The BATCH SUBMITTAL screen (Figure 3-18) is used to specify the Job Control Language
(JCL) information for the batch job. The data from the screen will be used to control your
batch job. The default values (from your User JCL record) can be changed. You can find
more information about the User JCL record in Section 4 of the AFS Data Storage Manual.
Also see Section 4 of the NCC-IBM User's Guide for more information about any of the
BATCH SUBMITTAL screen parameters. When you have finished entering JCL parameters
or making changes to the default parameters, press ENTER. Your batch job will be
immediately submitted to the NCC system.
JOB NAME: The eight-character job name for the batch job to be submitted. The first
three characters are your User-ID and cannot be changed. The default value of the last five
characters is the type of job being submitted, such as "EDIT1" or "UPD1". You may change
the last five characters of job name to any value consisting of letters and numbers.
ACCOUNT CODE: The NCC-IBM account to which the cost of the batch job will be
charged. The initial value shown on the screen is what you specified for account code on
the AFS User Profile screen. You can change the account to a different value, but it must be
a valid code that you are authorized to use.
FIMAS ID: The FIMAS code links the batch run to an application, such as AFS. Enter
"AFSCP" if you are a Compliance user, or "AFSEP" if you are an Emissions user.
TIME (MMMM.SS): The maximum CPU time allowed for your batch job. You may
change the default to another value so long as it is a valid job time. The amount of time
April 2003
3-40
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
specified affects when the job will run; jobs with shorter times generally run sooner than
jobs with longer times. The NCC-IBM User's Guide explains the allowed formats of the job
time parameter and the effect of job time on job scheduling.
PRIORITY CODE: A one-digit code that affects job scheduling and cost. The default value
"2" is normal priority. You may specify a lower priority of "1", which causes a job to be
executed at night and costs less. A priority of "0" is the least expensive and causes the job
to be executed over the following weekend.
MSGCLASS: A one-character code that defines a category (message class) of printed
output. The default value "A" is a general category.
NUMBER OF COPIES: The number of copies of batch job output to be printed. The
default value is 1; permissible values are 1 through 99.
FORM NUMBER: A four-digit code for the type of paper on which your output will be
printed, the number of lines printed per inch, and whether lower-case letters are printed.
The default value is blanks, which results in usage of the standard form (STD). For the local
printers at NCC the standard form is 8381, for upper- and lower-case at eight lines per inch
on 11 x 8.5-inch paper. Other common forms are 6311, for upper- and lower-case at six
lines per inch on 15x11-inch paper. Be aware that remote printers probably cannot handle
anything but the standard form. If you are directing output to a remote printer, select the
standard form by leaving the form number field blank or by entering "STD".
ROOM/BIN NUMBER: A four-character code used by the Computer Center for
distribution of printed output to the appropriate location. The initial value shown on the
screen is what you specified on the AFS User Profile screen. You may change it to another
valid bin number.
HOLD OUTPUT (Y/N): A yes/no field that specifies whether the output of your batch job
is to be held in the output queue of the computer system ("Y") or to be printed ("N"). The
default value is "N" (no).
PRINTER SITE ID: The printer site-ID where the output of your batch job is to be printed.
The initial value shown on the screen is what you specified on the AFS User Profile screen.
You may change it to another valid printer site-ID, such as "LOCAL" or "R321". This field is
not used if you specify "Y" for Hold Output.
ALTERNATE USER ID (optional): Enter the NCC User-ID of the person that you want to
receive a copy of the Edit report produced by this job. The system will fill in the defaults for
this user from the AFS User JCL Record for this User-ID. You may change the defaults for
the alternate user by typing over the contents of these fields. If the alternate user does not
have an AFS User Profile record defined in the system, an error message is produced.
April 2003 3-41 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Validations
JOB NAME MUST BE ALPHANUMERIC.
JOB NAME can be blank or contain one through five letters and numbers, with no
intervening spaces or special characters such as "-".
PLEASE ENTER A VALID MESSAGE CLASS.
The message class must be a letter or a number. Usual values are A and F.
PLEASE ENTER AN ACCOUNT CODE.
The account code cannot be blank. Enter a four-character code.
PLEASE ENTER AN ALPHANUMERIC PRINTER SITE-ID.
The printer site-ID must be alphanumeric. Examples of valid site-IDs are "RMT321"
and "LOCAL".
PLEASE ENTER TIME IN MINUTES, SECONDS.
The minutes and seconds fields both contain zeros or spaces. At least one of these
two fields must contain a valid numeric value greater than zero.
PLEASE ENTER VALID MINUTES.
Minutes must be numeric in the range 0000 through 9999.
PLEASE ENTER VALID SECONDS.
Seconds must be numeric in the range 00 through 59.
PLEASE ENTER "Y" OR "N".
HOLD OUTPUT must be either "Y" to hold output or "N" to print output.
PLEASE USE A VALID PF-KEY.
You used a PF key not defined for this screen.
ROOM/BIN NUMBER MUST BE ALPHANUMERIC.
ROOM/BIN NUMBER must consist of letters and numbers.
THE NUMBER OF COPIES MUST BE IN THE RANGE OF 1 TO 99.
The NUMBER OF COPIES requested is not in the range of 01 through 99.
USER JCL PROFILE NOT ON FILE - CONTACT AFS HELPLINE.
There must be a JCL Profile record on file in order to generate the appropriate
information for the batch Job Card. Contact the AFS Helpline for assistance with
this problem.
April 2003 3-42 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 4:
PATL 02/24/96 AIR.5 FACILITY 6U&5Y6TtM PC.MAFC985PI
55 &ATCJJ 5U&MITTAL MAP AFM0985
Job 5tatus
Job 7299 5U&MITTtP
PH=iltLP
Instructions
The BATCH SUBMITTAL (Confirmation) screen displays the job number that the NCC
system has assigned to your job. You may wish to write this number down before moving
to another screen.
April 2003
3-43
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4.4 Edit/Update Output Reports
Figure 3-20 is a sample of the Error Report produced by the Batch Edit process. The Update Error
Report is identical in format; the word "UPDATE" appears in the title in place of "EDIT". Each field of
the input transaction that contains an error is marked with an "E" (error) or "W" (warning) indication,
with asterisks used to fill out the length of the field in error. For example, an error for a five-position
field would be marked "E****". An error indication results when the Edit/Update program finds
something wrong, for example, data missing from a required field, alphabetic or alphanumeric data
in a numeric field, or incorrect or invalid data.
For each "E" or "W" error indication, there is a corresponding message printed below the transaction.
The messages for the fields in error are listed in an order corresponding to the positions of these
fields on the transaction, reading the transaction from left to right.
Figure 3-21 is a sample of the Summary Report produced by the Batch Edit process. The Update
Summary Report is identical in format; the word "UPDATE" appears in the title in place of "EDIT".
This report provides a tally of all errors noted in this batch and also include counts for all
transactions by sequence. This summary information is also available from the Notification screen
by using the "T" (TRANS SUMMARY) or "E" (ERROR SUMMARY) action codes.
Identifying Your Output
Under normal circumstances, your printed reports will begin with a banner page. The banner page
has in large letters: Job Name, Job Number, and Output Bin Number. For Edit and Update jobs that
you submit yourself and print this will not change. For jobs that you submit with an alternate user
ID (to send a copy of your report to another user) the Job Name that will be printed will appear as
your user Id followed by the alternate user ID followed by "ED" or "UP. Example: your user ID is
AAA and you want to send a copy of your Edit reports to user ID XXX. The banner page job name
will be AAAXXXED for both sets of printed reports. Be sure to tell the intended recipient what to
look for.
For Updates that are Central Submit, the first three characters will be JH1 followed by your user ID.
Be sure that your User JCL Parameter (an option on the Utility Selection Menu) has the correct
printer ID for your printer. If you want the reports to print automatically, set the Hold Output field to
"N". If you want to preview them from TSO/ISPF before printing, set the Hold Output field to "Y".
Then look for your job under prefix "JH1 *".
April 2003 3-44 Batch Updating
-------
ro
o
o
CO
CO
-k
01
DO
o>
r-t-
o
3-
Q.
o>
CO
PATL 04/30/96
t: I3JH2
ALR^MtTRIC INFORMATION RiTR-tVAL 6Y6TtM PAC.LI
AIR6 FACILITY 6U&6Y6TLM PC.M: AftElOR
LPIT tEE^G. G.tP^G.7 T^G- LtVtL 3
5TCNTY
20 00154321
O
c
CL
(D
20001543210395
#1 A
LITUtG. CITY COVL. (M. CRT NAIv|t 16 KL.OUKLD.
PRIMARY INPU5TG.IAL CLA65fCATl^N CODL. 16 R.L
CO
r-h
o
—1
o>
CQ
(D
-------
AIRS User's Guide
AF3 AFS Data Storage
April 2003 3-46 Batch Updating
-------
ro
o
o
CO
"3
c
(D
PATL: 04/30/96
TIML: 13:11:12
ALR£7MLTRIC iNr^RMATI^N RLTRILVAL 6Y6TLM
AIR6 rACILITY 6U&6Y6TLM PC, M: AftRIOPI
LPIT 6UMMARY RLP£7RT R?R- LLVLL 3
: NllJA026.Ar6riLL.TTIOAPPJNPUT.Ar6
PAC,L:I
CL
(D
NUJLPIT3
ACCLPT OUTPUT HLL: NllJA026Ar6nLL.TT10APPL3ACCLPTArX
G.LJLCT OUTPUT HLL: NHJA026Ar6riLL.TTIOAPPL3G.LJLCT.ArX
04/30/96
13:11:03
CO
i.
-vl
TEAN6ACT1^N 6UMMAE.Y
TEAN6 6L(?
LEE^G. 6UMMAE.Y
PL6CRJPTI^N
DO
CO
10
10
10
10
2 I
3 ;
9 i
TOTAL6
3 LITJJLG. CITY C£7PL OR. CITY NAIv|L 16 G.L(?UIG.LP.
PRIMARY INPU6TE.IAL CLA66iriCATI^N C^7PL 16 KL.MKL.D.
I I 6TATU6 AE.LA 16 G.L(?UIG.LP
I CANNOT JJAVL PUPLICATL 6TATU6 AE.LA6.
I CANNOT JJAVL PUPLCATL 6IP PR^C, GAIv|6 r^G- N^N-ATTAlNlv|LNT AG.LA6.
I PLANT NAML 16 R.L
Q.
O)
CQ
00
r-h
o
—i
CO
CQ
(D
-------
AIRS User's Guide
AF3
AFS Data Storage
3.4.5 Submitting an Update Job
This section describes the steps required to submit an AFS Update job. The AFS Batch UPDATE
SUBMITTAL screen (Figure 3-22) is invoked by selecting option "4. UPDATE" from the AFS BATCH
UPDATE MENU (Figure 3-15). The UPDATE SUBMITTAL screen, which is similar to the AFS BATCH
EDIT screen shown in Figure 3-16, is used to specify input and output files and other options.
Figure 3-23 contains the UPDATE SUBMITTAL (YEAR OF RECORD) screen.
STEP 1:
PATL 02/24/95
5CG.LLN: 406
AIG.5FACII_rTY6U&5Y6TLM P
UPPATL 5U&MITTAL MAP AfTv|0406
INPUT FLL NAML A&CA026.tespLant«cs0995_
\VA6 TJJI6 INPUT FILL CG.LATLP TG-^M Tilt ^NLlNt UTILITt5: N
5U&MH INPUT FILL r^G- CLNTGAL UPPATL N
INPUT FILL TYPL I (I = PU&LIC 2 = PGJVATL)
TG.AN5ACTI^N FORMAT I (I = AF6.2 = AFX)
OUTPUT FILL PG.LrtG.LNCL (ACCLPT FILL15 ^PTl^NAL)
ACCLPT FILL NAML A&CA026. . .
ANP
G.LJLCT HLL NAML ABCA026. texpbnt. vocs0995 . rejects..
PH=ilLLP
P|=5=TLG.M
Instructions
INPUT FILE NAME: This is the name of the file containing the AFS or AFX transactions
that you want to submit for Editing. This file can be either a sequential data set or a
member in a partitioned data set (fixed or variable length, blocked format). When you have
completed this screen and press ENTER, the system will verify that this file exists.
INPUT FILE TYPE: The default setting is "1" (Public), which will allow notified users to print
a copy of the Edit report for this job from the Notification screen. They can also view
Transaction and Error summary screens. Entering 2 will cause your edit and update reports
(which report the data that is input to the job) to be marked as private. Only the job owner
can print the reports, or view the summary screens, for a private job. Other users may by
notified of the job's status, but they may not print or view the results.
NOTE: This field is not a substitute for the NCC's RACF security. If you have strict
security needs, contact your Resource Security Administrator or the AFS
Help Line. The default for this field is: 1, Public.
April 2003
3-48
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
TRANSACTION FORMAT: The default for this field is: 1,AFS. This is the current format.
The AFX format supports the new, expanded 120-character record format. The AFX format
is designed to support the 15-character AFS Plant-ID as the key Plant-ID on all transaction
types. It will also accommodate a future modification to AFS that will expand the size of the
Stack, Point, and Segment number fields to five characters.
WAS THIS INPUT FILE CREATED FROM THE ONLINE UTILITIES: If you want to
submit a file of transactions that you created using one or more of the utilities, change the
default "N" to "Y". If you move to this screen from the UTILITY SELECTION MENU (Figure 3-
28), this field will already contain a "Y".
SUBMIT INPUT FILE FOR CENTRAL UPDATE: If you wish your data to be run as a
"centrally monitored" nightly update, change the default "N" to "Y". If you enter "Y" you will
not see the BATCH SUBMITTAL (Job Control Language) screen (Figure 3-18). Following the
UPDATE SUBMITTAL (YEAR OF RECORD) screen (Figure 3-23), you will be returned to the
BATCH UPDATE MENU (Figure 3-15). Your file will be automatically submitted as a Batch
Update during the evening, and your update reports will be available the next morning.
If you wish to submit and monitor the job yourself, leave this value as "N". If you enter "N"
you will next see the BATCH SUBMITTAL (Job Control Language) screen (Figure 3-18).
After you make any needed entries on this screen, and press enter, the job is submitted,
and you are given the job number so that you can monitor its progress.
ACCEPT FILE NAME AND REJECT FILE NAME: The REJECT FILE NAME must be
specified. The ACCEPT FILE NAME is optional. However, writing the accepted transactions
to the Accept file is the only way to record, for later review, which transactions were
actually updated to the database. If you entered "Y" for the "SUBMIT INPUT FILE FOR
CENTRAL UPDATE" option, the second part of both file names must be "AFSFILE",
because of RACF security profile considerations (discussed in section 3.4.10).
Validations
BOTH ACCEPT & REJECT FILE NAMES REQUIRED FOR THIS OPTION.
Both files must be specified for this option.
DUPLICATE FILE NAMES ARE NOT ALLOWED.
The same file name cannot be entered more than once on this screen.
ENTER 1 OR 2.
FILE-TYPE must be "1" or "2".
FILE-FORMAT must be "1" or "2".
FILE EXISTS. CHANGE NAME OR DELETE BEFORE SUBMITTING.
The Batch system creates new output files for each submit, in order to avoid
accidently overwriting existing files.
FILE IS PARTITIONED, A MEMBER NAME IS REQUIRED.
Enter the correct member name.
FILE NAME IS INVALID.
This message is displayed for one or more of the following:
April 2003 3-49 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Blank(s) within the file name.
The first character of each qualifier must be A - Z, or "#", "$", or "@".
Position 2 - 8 of each qualifier must be either A - Z, 0 - 9, "#", "$", "@" or "-".
FILE NAMES ARE LIMITED TO 5 QUALIFIERS OR LESS.
More than five qualifiers were specified on the Load file.
INPUT FILE IS REQUIRED.
The Load file name is blank.
MEMBER NAME INVALID. FILE IS NOT A PDS.
Sequential files are not allowed to have member names.
MEMBER NAME MUST BE 8 CHARACTERS OR LESS.
The member name specified has more than eight characters.
MEMBER NOT FOUND. CHECK THE SPELLING
Member names must be entered exactly as they appear on the NCC mainframe.
NO FILE WITH THIS NAME EXISTS. CHECK THE SPELLING.
Confirm the full name of the file on the NCC mainframe that contains your Load
transactions.
AN OPEN UTILITY FILE DOES NOT EXIST.
You must first run one of the AFS Utilities to create a file of transactions. Return to
the AFS Main Menu (Figure 3-13) and select "SELECT A UTILITY".
FOR CENTRAL UPDATE, SECOND PART OF THE NAME MUST BE "AFSFILE".
The nightly Central Update will need to create Accept and Reject file names on the
NCC system that begin "uuuaaaa.AFSFILE" where: uuu = your User-ID and aaaa =
your account code.
April 2003 3-50 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
DATE: 02/24/96
SCREEN: 420
AIRS FACILITY SUBSYSTEM
UPDATE SUBMITTAL
PGM: AFP420
MAP: AFM0420
YEAR OF RECORD: (REQ IF COLS 14/15-AFS, 25/26-AFX ARE
BLANK ON EMIS TRANS. IF VALUED, OVERRIDES
COLS 14/15-AFS, 25/26-AFX.)
IF YOU HAVE CHANGED THE YEAR OF EMISSION INVENTORY,
PLEASE INDICATE DATA TO BE COPIED OVER TO THIS NEW YEAR
FROM THE PREVIOUS YEAR:
_ ALL EMISSIONS DATA, INCLUDING SIP DATA
_ ONLY ANNUAL EMISSIONS DATA (OMIT SIP DATA)
NO EMISSIONS DATA
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF6=PREV
Jujurvd
Instructions
Enter a Year of Record (required in some cases, as described below). In addition, if the
Year of Emission Inventory is to be incremented or decremented, specify the data that is to
be copied to the new year:
ALL EMISSIONS DATA, INCLUDING SIP DATA
or
ONLY ANNUAL EMISSIONS DATA (OMIT SIP DATA)
or
NO EMISSIONS DATA
If Compare and/or Edit jobs have been submitted for the file being updated, you must select
the same "data to be copied" options for this Update job as were used for those previous
jobs.
YEAR OF RECORD: Providing a Year of Record indicates to which Year of Emission
Inventory the submitted Emissions data will be applied. A value for Emissions Inventory
Year of Record is required on all Emissions transactions (columns 14 and 15 for AFS
format or columns 25 and 26 for AFX format). If Year of Record is not valued on your
transactions, you should enter a year on this screen. A value entered here will override
the value specified in the transaction.
Complete the Update process by following the steps described for Figure 3-18, BATCH
SUBMITTAL (JCL Parameters) Screen, in section 3.4.5, Submitting An Edit Job. The
BATCH SUBMITTAL (Confirmation) screen (Figure 3-19) will appear.
April 2003
3-51
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Validations
ONLY ONE COPY OPTION MAY BE SELECTED.
Three options are available when changing the Year of Emissions Inventory and
copying Emissions data from the "current" year to the new year. Only one of these
may be selected.
April 2003 3-52 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4.6 Notification
The ability to provide information about your Edit and Update jobs to other users is one of the new
features of the AFS Batch Edit/Update process. Other users can, likewise, provide this information
to you. The Notification screen (Figure 3-24) displays information about the status of your Batch Edit
and Update jobs, and the jobs submitted by other users who are "notifying" you. This is an
interactive screen; from it, you may select a number of actions to be executed for each of the jobs
displayed. These action choices are explained below.
Each user decides whether or not the reports produced by the Edit or Update job will be available to
the notified users for viewing or printing. This is done by setting the "INPUT FILE TYPE" option on
the Edit or Update submittal screen to "Public" or "Private".
3.4.6.1 Copying Reports to Another User
Sending a copy of your Edit or Update reports to another user is a separate, but related capability
explained in Section 4, Submitting An Edit Job, under "ALTERNATE USER ID". The reports can be
sent to any valid remote "PRINTER SITE ID". Be sure to tell the intended recipient to look for the
report. The jobs sent to another user via the "ALTERNATE USER ID" capability will not appear as an
entry on the NOTIFICATION screen.
3.4.6.2 Notifying Other Users by State Code
Another new feature - Notification - is the ability to be notified whenever transactions are submitted
for a particular state code. A state user may want to know when another user in the state has
submitted data. A regional user might want to track Edit and/or Update activity for one or more
states within his or her region.
The AFS database administrators, who maintain the AIRS Geo-Common State Table, will set up the
Notification by state code feature. A third screen has been added to the State Table Update process
for this purpose. You may notify other users about Edit jobs, Update jobs, or both.
This section describes how to use the Notification process features. The AFS NOTIFICATION screen
(Figure 3-24) is invoked by selecting option "5. NOTIFICATION" on the AFS BATCH UPDATE MENU
(Figure 3-15). Figure 3-24 contains the NOTIFICATION screen, which displays the status of your
jobs, and those you are being notified for. Figure 3-25 is the TRANSACTION SUMMARY report
screen, and Figure 3-26 is the ERROR SUMMARY screen. These are online edit reports generated
for the Edit and Update jobs that are listed on the NOTIFICATION screen.
April 2003 3-53 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 1:
PATL 02/24/96
: 408
AIR.5 FACILITY 5UB5Y6TEJv| PQ4 ATP408
CATION MAR Af M&408
ACT U5LG. TYPE. NAME. 5TATU5 NUMBER. PATE TIME
ABC E ABCEPITI 6 J£7B2I|62 02/24/96 I&50I
ABCA026.TEXPI_ANT.V^C50995
ABC U ABCUPPTI C J^7Bl6359 02/24/96 E40a
ABCA026.TD
-------
AIRS User's Guide
AF3 AFS Data Storage
Job Status is: Utility, Submitted, Incomplete*, Incomplete, and Complete*, and Completed
jobs.
Messages for your User-ID will be listed as two lines. The first line displays the status
information. The second line displays the name of the transaction file that you specified for
this job. Messages from other users will only display a status line.
This screen has been designed to assist you in managing your jobs and messages. From
this screen you can perform the following job disposition or view functions, by entering the
appropriate one-character code under the "ACT'ion header in the space corresponding to
the job:
D = Delete a message.
NOTE: You should delete messages you do not need. But when you
delete a message it is gone forever. You will not be able to view or print a
report corresponding to the message later. If you do not delete these job
message records, there is an automatic clean-up process executed once a
week that deletes records older than 60 days.
P = Print another copy of the Edit or Update reports.
C = Cancel a job that belongs to you. Must have a Job Status of "S" (Submitted).
R = Restart a job that belongs to you. Must have a Job Status of "I" or "I*"
(Incomplete).
S = Submit a Utility file for Update. Must have a Job Status of "U" (Utility).
The following options, "T" and "E", can be applied only to completed jobs, i.e., job
status = "C" or "C*".
T = View the Transaction Summary (Figure 24) for a given job.
E = View the Error Summary (Figure 25) for a given job.
Validations
ALREADY AT THE BEGINNING OF SELECTED RECORDS.
There are no records before these for your User-ID.
DETAIL RECORD(S) COULD NOT BE FOUND - CONTACT AFS HELPLINE.
END OF SELECTED RECORDS.
These are the last records for your User-ID.
FILE IS SET FOR AUTO SUBMISSION, YOU CANNOT SUBMIT IT MANUALLY.
Your User Profile has been set up so that this job will automatically be included in
the nightly Batch Update job.
April 2003 3-55 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
INVALID ACTION CODE.
Valid codes are "C", "D", "E", "P", "R", "S", or "T".
JOB STATUS MUST BE "C" or "C*".
A job must have a status of "C" or "C*"for this Action.
JOB STATUS MUST BE "I" or "I*".
You can only restart an incomplete job.
JOB STATUS MUST BE "S".
A job must have a status of "S" for this Action.
JOB STATUS MUST BE "U".
You can only SUBMIT Utility file jobs from this screen.
ONLY 1 ACTION CAN BE SPECIFIED AT A TIME.
More than one Action Code cannot be specified on a screen at a time.
ONLY THE FILE OWNER CAN CANCEL THIS JOB.
You cannot cancel this job; only the owner can.
ONLY THE FILE OWNER CAN RESUBMIT THIS JOB.
You cannot restart this job; only the owner can.
RESUBMIT DENIED - SAME JOB CAN BE SUBMITTED A MAX. OF 20 TIMES.
If you have restarted this job 20 times, you should consult with the AFS Helpline.
STATISTICS RECORD COULD NOT BE FOUND - CONTACT AFS HELPLINE.
THE OWNER HAS MARKED THIS FILE AS PRIVATE, REQUEST DENIED.
You cannot reprint the reports for this job; only the owner can.
April 2003 3-56 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
DATE: 02/24/96
SCREEN: 412
USER: XYZ
AIRS FACILITY SUBSYSTEM
TRANSACTION SUMMARY
TYPE : E JOB
TRANSACTION SEQUENCE
11
12
13
14
15
16
17
18
19
20
PF1=HELP
1
1
1
1
1
1
1
1
1
1
TOTALS :
NUMBER: JOB99999 JOB DATE:
COUNT
20
18
16
14
12
10
8
6
4
2
110
PF3=END PF4=MAIN PF5=TERM
ERROR
10
9
8
7
6
5
4
3
2
1
55
PGM: AFP412
MAP: AFM0412
02/23/96 JOB TIME: 17590
PF7=PREV PF8=NEXT PF9=ERROR SUMMARY
Instructions
The TOTALS line appears on the last screen of the TRANSACTION SUMMARY. For multiple
screens, use PF keys 7 and 8 to move back and forward. Use the PF9 key if you wish to
view the online Error Summary. The COUNT column represents the total for this
transaction/sequence for this job. The ERROR column contains the total number of errors
detected for this transaction/sequence.
April 2003
3-57
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 3:
DATE: 02/24/95
SCREEN: 410
AIRS FACILITY SUBSYSTEM
ERROR SUMMARY
PGM: AFP410
MAP: AFM0410
USER: XYZ TYPE: E JOB NUMBER: JOB99999 JOB DATE: 02/23/96 JOB TIME: 17590
COUNT DESCRIPTION
1 CRITERIA POLLUTANT, STATE PRIVATE INDICATOR MUST BE 'N'.
2 EMIS. YEAR OF INCREMENT MUST BE GREATER THAN YEAR OF EMIS. INV.
3 INVALID EMISSIONS TYPE FOR TRANSACTION 11.
4 INVALID EMISSIONS TYPE FOR TRANSACTION 41.
5 COMPLIANCE EMISSION IDENTIFIER MUST BE 'E'.
6 POLLUTANT ABBREV OR CASN IS REQUIRED.
7 INVALID EMIS TYPE FOR OTHER THAN SEGMENT LEVEL UPDATE.
8 EMISSIONS TYPE INVALID FOR POINT.
9 INVALID EMIS TYPE FOR A NON-EMISSION USER.
10 INVALID EMIS TYPE FOR A NON-COMPLIANCE USER.
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF7=PREV PF8=NEXT PF9=TRANS SUMMARY
Instructions
The COUNT column is the total number of this particular error detected during this job. Use
PF keys 7 and 8 to move back and forward if there are multiple screens. Ideally, this will not
be necessary. Use the PF9 key if you wish to view the online Transaction Summary.
April 2003
3-58
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
3.4.7 Submitting Utility Transactions
This section describes the steps required to submit an AFS Utility Transaction. Figures 3-27 and 3-
28 contain the AFS MAIN MENU and the AFS UTILITY SELECTION MENU. Figures 3-29 and 3-30
show you how to either specify a UTILITY FILE NAME or accept the system default name.
STEP 1:
02/24/96
AIRS FACILITY SUBSYSTEM
MAIN MENU
PGM: AFPOOO
MAP: AFM0001
1 UPDATE THE DATABASE
2 BROWSE THE DATABASE
3 SELECT A REPORT
4 SELECT A UTILITY
ENTER MENU SELECTION:
NEED ASSISTANCE? CALL THE AFS HELPLINE AT 1-800-367-1044
PF1=HELP PF3=END PF4=SUBSYSTEM MENU PF5=TERM
Instructions
Enter "4" to select "SELECT A UTILITY".
April 2003
3-59
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
DATE : 02/24/96
SCREEN: 081
AIRS FACILITY SUBSYSTEM
UTILITY SELECTION MENU
PGM: AFP008
MAP: AFM0081
1 MERGE PLANTS (ASSOCIATION)
2 MERGE POINTS
3 UNMERGE PLANTS
4 DELETE INFORMATION
5 UNDELETE INFORMATION
6 COMPLIANCE HISTORY
7 SOURCE/POINT SWAP
8 ARCHIVE
9 DEARCHIVE
10 USER JCL PARAMETERS
11 TABLE FILE LOOKUP
12 SIP INVENTORY
13 UPDATE AFS PLANT ID
14 SUBMIT CURRENT UTILITY FILE
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
Instructions
Enter a number from "1" to "14" to select the appropriate Utility process to be performed.
There are two ways that the transactions that you create from running one or more of the
Utilities can be submitted. The difference depends on whether your User Profile has been
set up as an "automatic" or "manual" user. A Special Access Code of "P" is used to define a
Manual user (the default is Automatic):
Automatic: You do not have to do anything to submit an Update job after running
a Utility and creating transactions. The system will automatically submit the
transactions as part of the next nightly batch update. The system will automatically
assign the files that your job needs:
Your transactions will be put into a file with the name
uuuaaaa.AFSFILE.UTILFILE.DTyymmdd
where: uuu
aaaa
yymmdd
= your User-ID
= your Account Code
= the current date
April 2003
3-60
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Similarly, your Accept(ed) and Reject(ed) transactions will be put into files named:
uuuaaaa.AFSFILE.ACCEPT.UTILFILE.DTyymmdd
and
uuuaaaa.AFSFILE.REJECT.UTILFILE.DTyymmdd
Manual: When you select an option from the UTILITY SELECTION MENU, you will
be prompted to specify a Utility file name if a file is not currently open (see Figure
3-29). All of the transactions from any of the Utilities that you run will be placed in
this file until you submit the Update.
If you are a Manual user, it is your responsibility to submit and monitor your Utility
file Update job. To do this, you may select option 14, SUBMIT CURRENT UTILITY
FILE, from the UTILITY SELECTION MENU (Figure 3-28). Selecting this option will
take you to the UPDATE SUBMITTAL screen (Figure 3-22). Use this screen to
specify input and output files and other options, as described in Section 6,
Submitting an Update Job.
NOTE: For "automatic" users, selection 14, SUBMIT CURRENT UTILITY
FILE, will not be displayed on the UTILITY SELECTION MENU
(Figure 3-28).
April 2003 3-61 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 3:
DATE : 02/24/96
SCREEN: 083
AIRS FACILITY SUBSYSTEM
UTILITY FILE NAME
PGM: AFP008
MAP: AFM0083
NO UTILITY FILE CURRENTLY OPEN, PLEASE SPECIFY A FILE NAME
UTILITY FILE NAME: ABCA026 .
PF1=HELP PF3=END PF4=MAIN PF5=TERM
Instructions
Specify a Utility transaction file name. If you would like the system to create a file name for
you, press ENTER without specifying a file name. When you do so, a pop-up box appears
to confirm that choice.
Validations
FILE NAME IS INVALID.
This message is displayed for one or more of the following:
Blank(s) within the file name.
The first character of each qualifier must be A - Z, or "#", "$", or "(j
Position 2 - 8 of each qualifier must be either A - Z, 0 - 9, "#", "$",
or -
April 2003
3-62
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 4:
DATE : 02/09/96
SCREEN: 083
AIRS FACILITY SUBSYSTEM
UTILITY FILE NAME
PGM: AFP008
MAP: AFM0083
NO UTILITY FILE CURRENTLY OPEN, PLEASE SPECIFY A FILE NAME
MANUAL FILE OPTION
UTILITY FILE NAME: NHJA026.444444444444444444444444444444444444447
5 WOULD YOU LIKE TO SELECT
5 THE DEFAULT FILE SELECTION
5 (Y/N) ?
5
94444444444444444444444444444444444444448
PF1=HELP PF3=END PF4=MAIN PF5=TERM
Instructions
The Manual user may choose the default file name:
uuuaaaa.AFSFILE.UTILFILE.DTyymmdd. Enter "Y" for "yes" or "N" for "no".
Accept and Reject file names will be specified during the actual Update submittal (see
section 3.4.5).
April 2003
3-63
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4.8 Edit/Update Processing Details
Number Generation
The Edit/Update Process performs requested number generations for transactions
which have the number generator functionality (all levels of actions, all levels and
types of comments, segment numbers, and stacks). The number generator
functionality is invoked when a user supplies 9's for the supported keys. These
keys are action numbers, comment numbers, stack numbers, segment numbers
and asbestos plant ID's. AFS attempts to supply the next highest number for the
field requested. If a number cannot be generated because the highest number has
already been used, the transaction is rejected and the error condition reported.
The following are the limits on the amount of number generation requests that may
be submitted in a single update:
Action Numbers: plant (350)
point (350)
permit (250)
Comment Numbers: plant (200)
stack (100)
point (350)
segment (100)
permit comment (200)
permit action comment (150)
Stack Numbers<100)
Segment Numbers: (100)
If these limits are exceeded the edit/update reports will tell you the next transaction
to be processed. You will need to resubmit the remaining transactions in your
input file.
Number generator requests for action comments, stack comments and segment
comments will be rejected in the case where the action number, stack number or
segment number was requested on the comment record but a valid number
generator request was not found in the transactions for the action, stack or
segment record. For example an action comment (transaction type 17, sequence
1) is submitted with action number '999' and comment number '001'. There must
have been an plant action transaction (transaction type 16, sequence 1) with an
action number '999' to be generated, otherwise an error will be reported. If the
plant action number '999' had been submitted with a '999' action number, AFS will
apply the same action number generated to any comments with an action number
'999' that follow the action transaction. Similar processing is invoked for generating
asbestos plant ID's.
April 2003 3-64 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
The Load Program (the first step of any Edit or Update job) identifies errors associated with
generating numbers for stack and segment numbers, all levels of actions and plant, stack
and point levels of comments. Currently, there are three error conditions which will be
seen in this section:
1) If a record already exists on AFS with the highest possible number, a
message stating that AFS was unable to generate the next highest number
: NO MORE NUMBERS TO GENERATE. The highest numbers for two digit
and three digit fields are 98 and 998 respectively. If you receive this error
condition you will need to assign an unused number (if available). Unused
numbers often exists where gaps have been left between numbers or
records have been deleted.
2) Validations are performed to ensure that a previously generated number
exists for a submitted dependent transaction also requesting number
generation. If the parent and dependent record are not submitted together
you will receive an error condition: NO STACK NUMBER or ACTION
NUMBER OF 999 TO LINK TO THIS TRANSACTION. You must submit the
parent transaction, either action number or stack number, with the same
number generator request as the transaction that failed and resubmit the
transaction that failed.
3) There is a limit on the number of transactions requesting number
generation that can be processed in one submittal. If the limit is reached,
all transactions submitted prior to reaching the limit are processed and the
transaction that exceeded the limit is identified. The transaction indicated
is the first transaction that did not get processed and is the resubmittal
position in the user's input file. Refer to Section 3.4.1 for the number of
transactions limit in a given submittal.
Level 1, Level 2, and Level 3 Data Validation
The new Batch Edit Process allows the user to choose the level of complexity and detail for each
Edit job submitted.
Level 1 -- Level 1 edits are mainly field-level edits, verifying that each field value, of itself, is
valid. Many of these edits are AFS table look-ups to check that codes entered on
transactions are valid. Some are checks of Update-Code, Transaction-Type, and Sequence-
Number, as described below.
a. Transactions with update codes valued other than "A" (Add), "C" (Change)
or "D" (Delete) are reported with the message: INVALID UPDATE CODE.
Provide a valid update code and resubmit the transaction. Multiple
applications may be added to or deleted from the Application Association
record, transaction type A7. An update code of "A" is used to add the
record as well as add additional applications. An update code of "D" is
used to delete individual applications.
b. Each record in AFS corresponds to a transaction type for batch processing.
Appendix A contains the AFS batch transaction type formats depicting the
layout of the data contained in each transaction type. The following error
April 2003 3-65 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
message is reported when an unsupportable transaction type is submitted:
INVALID TRANSACTION TYPE. Provide a valid transaction type and
resubmit the transaction.
c. Each transaction type has specific sequence numbers corresponding to the
data addressable for each AFS record. Appendix A contains the AFS batch
transaction type formats which details each sequence for transaction
types. The following error message is reported when the sequence
number is not valid for the transaction type submitted: INVALID
SEQUENCE NUMBER FOR SPECIFIED TRANSACTION TYPE. Provide the
correct sequence number corresponding to the data to be updated and
resubmit the transaction.
Other Level 1 edits are key data validations. Each transaction type has key data
that uniquely identify a record in AFS. These data are required for AFS to perform
update requests. The following is a list of error messages that will be displayed for
each associated transaction type encountered with missing or invalid key data. If
you receive these messages, provide the information requested and resubmit the
transaction(s).
Transaction
Types
All
All
All
10
10
12,13
12,13
20,21,27
16,36
11,13,21,31,41,43
42
Error
Messages
INVALID STATE.
INVALID COUNTY FOR STATE SPECIFIED.
INVALID PLANT ID.
CANNOT ASSOCIATE TWO EMISSION IDS.
CANNOT ASSOCIATE TWO COMPLIANCE IDS.
INVALID AIR PROGRAM CODE.
AIR PROGRAM CODE IS REQUIRED.
STACK NUMBER IS REQUIRED.
ACTION NUMBER IS REQUIRED.
POLLUTANT CODE OR CAS NUMBER IS
REQUIRED.
CHEMICAL ABSTRACT SERVICE NUMBER IS
REQUIRED.
11,13,21,31,41,43 INVALID POLLUTANT.
April 2003
3-66
Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
17,27,37,47 COMMENT NUMBER IS REQUIRED.
17,27,37,47 BOTH COMMENT NUMBER AND IDENTIFIER ARE
REQUIRED.
30,31,32,33,34, POINT IS REQUIRED.
35,36,37,40,41,
42,43,47,64,65
30,31,32,33,34, BOTH POINT NUMBER AND IDENTIFIER ARE
35,36,37,40,41, REQUIRED.
42,43,47,64,65
40,41,42,43,47 SEGMENT NUMBER IS REQUIRED.
50,51,52 STATE AND CONTRACTOR ID ARE BOTH
REQUIRED.
50,52 CONTRACTOR ID IS REQUIRED.
33,34 CHANNEL NUMBER IS REQUIRED.
34 REPORT QUARTER IS REQUIRED.
43 PROJECTION YEAR IS REQUIRED.
43 EMISSIONS TYPE INDICATOR IS REQUIRED.
43 INVALID EMISSION TYPE INDICATOR.
43 PROJECTION YEAR MUST BE NUMERIC.
43 PROJECTED POLLUTANT DOES NOT EXIST.
A2,A7,B9 PERMIT IS REQUIRED
A1 APPLICATION IS REQUIRED
A8,C1 ACTION NUMBER IS REQUIRED
A8,C1 ACTION TYPE IS REQUIRED
A8,C1 EITHER PERMIT OR APPLICATION IS REQUIRED
B9,C1 COMMENT NUMBER IS REQUIRED
April 2003 3-67 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Level 2 -- Level 2 edits are inter-transaction edits, e.g., duplicate record checks.
Additionally, they verify that required transaction relationships are properly coded, as
detailed below.
a. AFS requires a Plant General, an Air Program and an Air Program Pollutant
record be added at the same time to add a compliance facility. These
records correspond to transaction types 10, 12 and 13 respectively. The
error message: CANNOT ADD COMPLIANCE PLANT WITHOUT VALID 12-1
AND 13-1 TRANS is issued if you attempt to add a compliance or
associated facility without valid 12-1 or 13-1 Add transactions. Submit all
three transaction types (10, 12 and 13) together as adds to add a
compliance or associated facility.
b. AFS requires an Air Program and an Air Program Pollutant record be
added at the same time to add a new Air Program. These records
correspond to transaction types 12 and 13 respectively. The error
message: CANNOT ADD AIR PROGRAM WITHOUT VALID 12-1 AND 13-1b
TRANS is issued if you attempt to add an Air Program with both required
transactions. Submit both transactions (12-1 and 13-1) together as adds to
add an air program.
c. AFS requires each emissions point to be associated to at least one
segment. A Point General with a compliance/emissions identifier of 'E' or
M and a Segment General record must be added at the same time to add
a new emissions point. These records correspond to transaction types 30
and 40 respectively. The error message: CANNOT ADD EMISS. POINT
GENERAL WITHOUT 30-3 OR 4, AND 40-1 TRANS is issued if you attempt
to add an emissions ('E') point without these required transactions. Submit
both transactions (30-3 or -4, and 40-1) together as adds to add an
emissions point.
The error message: CANNOT ADD MERGED POINT GENERAL W/0 30-1, 3,
OR 4, AND 40-1 TRANS is issued if you attempt to add a merged ('M') point
without the 30-1 (for the compliance information), 30-3 or 30-4 (for the
emissions information), and 40-1 (for the segment information).
d. The Point General record, transaction type 30, has compliance information
on sequences 1 and 2 and emissions information on sequences 3 and 4.
The compliance/ emissions indicator must be a "C" (compliance) or "M"
(merged) on sequences 1 and 2, and an "E" (emissions) or "M" (merged) on
sequences 3 and 4. If a compliance indicator is submitted with a value of
"C" in either sequence 3 or 4 the following error message is provided:
COMPLIANCE EMISSION IDENTIFIER MUST BE 'E' OR 'M'. If a
compliance/emissions indicator is submitted with a value of "E" in either
sequence 1 or 2 the following error message is provided: COMPLIANCE
EMISSIONS IDENTIFIER MUST BE 'C' OR 'M'.
April 2003 3-68 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
Level 3 -- Level 3 edits relate the transactions to the contents of the AFS database. To Add
an entitity, it must not already exist. To Change or Delete an entity, it must already exist.
April 2003 3-69 Batch Updating
-------
AIRS User's Guide
AF3 AFS Data Storage
3.4.9 Resource Access Control Facility (RACF)
In order to submit an AFS Batch Update job as part of the Central nightly update, you need to
create a Data Set Profile within the Resource Access Control Facility (RACF). The EPA's National
Computer Center uses RACF to control access to all mainframe resources. You may grant and/or
restrict access to your files by using RACF, which is available under TSO/ISPF. Only you or the
regional Resource Security Administrator who controls your account can grant the necessary
access. You can revoke access at any time.
Each region has its own predefined groups of users and RACF procedures. The regional Resource
Security Administrators must have "alter" access to your ID and regional Program users must have
"read" access to your ID. The examples in this section are just that - examples of how one might set
up the RACF access. You should follow your regional procedure for setting up RACF accesses.
You need to create a profile to allow the Central User-ID "JH1" limited access to create the necessary
files under your User-ID/Account. In addition to the Central User-ID, you should add "TSDGRP" to
the profile. "TSDGRP" is the Information Management Group at the Office of Air Quality Planning
and Standards; they will be able to manage any files should your User-ID and/or Account become
inactive.
The Rejected and Accepted (optional) transactions written by the Update process will be written to
these files. The access that you grant will be limited to files that have the format:
uuuaaaa.AFSFILE.name3.name4.name5
Where:
uuuaaaa is your User-ID and Account,
AFSFILE indicates that this is a Batch Update process file, and nameS, name4, and name5
are names that you enter to make each file unique. Names should be indicative of the
contents or purpose of the file.
NOTE: The Data Set Profile is required only for centrally submitted nightly Updates; it is
not required for Edit runs or for Batch Update runs that you submit yourself.
The following pages show the steps necessary to establish the Data Set Profile. Once you have
completed these steps, it will take approximately 30 minutes for the RACF system to update the
access master files.
April 2003 3-70 Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 1:
Environmental Protection Agency
Menu System
Date: 12/15/95
Time: 15:21:05
Terminal:H04222F8
Logmode: M2SDLCQ
Please enter selection or command and then press ENTER.
1. INFORMATION News Alerts and User Memos
2. SYSTEM MENU System Selection Menu
3. MAIL EPA Electronic Mail for 3270
4. APPLICATIONS EPA Applications Menu
5. INTER-AGENCY Inter-Agency Applications Menu
6. PUBLIC Public Access Applications Menu
WARNING:The use of this computer is for official Government business only.
Unauthorized use of this computer is a criminal offense under Title 18
United States Code, Section 641, and may subject violators to a fine of
up to $10,000, or imprisonment of up to 10 years, or both.
Command ===> tso
Optional Quick Logon - USERID ===> abc
PASSWORD ===>
Fl/F13=Help F5/F17=Refresh F12/F24=Cancel
Instructions
Logon to TSO by entering "tso" in the Command line, and then entering your USERID and
PASSWORD at the prompts.
April 2003
3-71
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 2:
ICH70001I
IKJ56455I
95/12/13
95/12/12
95/12/12
95/12/11
95/12/11
95/12/11
95/12/07
95/12/07
95/12/04
95/12/01
READY
ispf
ABC LAST ACCESS AT 11:06:46 ON FRIDAY, DECEMBER 15,
ABC LOGON IN PROGRESS AT 11:48:17 ON DECEMBER 15, 1995
FOCUS 7.0.3 IMPLEMENTATION POSTPONED - SEE NEWS
CHRISTMAS HOLIDAY SHUTDOWN
DB2 VERSION 3R1 DEVELOPMENT IMPLEMENTATION
ISPF 4.2 IMPLEMENTATION
REMOVAL OF SYSD FROM CICS
IBM HLASM V1R2 AVAILABLE FOR TESTING
NATURAL ISPF INSTALLATION IN PCICS
NSC ROUTER MAINTENANCE IN RTP 12/17
SAS AND S2K EXPIRATION WARNINGS
A LIST OF RECENTLY RELEASED EPA MEMOS
Instructions
Logon to ISPF by entering "ispf" at the READY prompt.
April 2003
3-72
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 3:
Menu
Utilities Compilers Options Status
ISPF Primary Option Menu
Help
Option ===> e
0
1
2
3
4
5
6
7
8
9
10
E
G
U
Settings
View
Edit
Utilities
Foreground
Batch
Command
Dialog Test
LM Facility
IBM Products
SCLM
EPA
Group
User
Terminal and user parameters
Display source data or listings
Create or change source data
Perform utility functions
Interactive language processing
Submit job for language processing
Enter TSO or Workstation commands
Perform dialog testing
Library administrator functions
IBM program development products
SW Configuration Library Manager
EPA/NCC Application Option Menu
Group Application Option Menu
User Defined Application Option Menu
< Calendar
November 1995
Su Mo Tu We Th Fr
123
5 6 7 8 9 10
12 13 14 15 16 17
19 20 21 22 23 24
26 27 28 29 30
Time . . . . :10:
>
Sa
4
11
18
25
56
Day of year. : 326
Enter X to Terminate using log/list defaults
Instructions
Enter "e" to display the EPA/NCC Application Option Menu.
April 2003
3-73
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 4:
OPTION
A
ARE
C
D
FA
FL
FO
G
IDEA
INFO
ISMF
J
L
LI
M
PDS
PLS
PP
R
===> r
ASM2
ARBITER
COBAID
DB2 MENU
FILEAID
FLSF
FOCUS
GOPHER
IDEA
INFO
ISMF
JSTS
LIBRARIAN
LIBRARY
UCLA MAIL
PDS/E
PLSORT
PUB/PRT
RACF
EPA/NCC OPTION MENU
More : +
- Disk Storage Management System
- Arbiter ISPF PC Data Access
- VS COBOL II Conversion Aid
- DB2 Product Selection Menu
- Data Management Ut il ity
- Font Library Service Facility
- Invoke Focus
- Internet Gopher client
- Integrated Data for Enforcement Analysis
- IBM Information Management
- IBM ISMF dialog
- Job Status Tracking System
- Perform Librarian Services
- EPA SoftCopy Library
- UCLA Mail BITNET Interface
- PDS/E Utility Program
- Phase Linear Sort Panels Product
- Publishing and Printing
- Resource Access Control Facility
Instructions
Enter "r" to select "RACF - Resource Access Control Facility".
April 2003
3-74
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEPS:
OPTION ===>
PLEASE NOTE :
In the following RACF dialog, not all functions
will work for all users.
Some functions are restricted to systems or
administrative personnel.
Instructions
No input is required for this screen; it displays a message for information only. Press
ENTER.
April 2003
3-75
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 6:
RACF - SERVICES OPTION MENU
OPTION ===> 1
SELECT ONE OF THE FOLLOWING:
1 DATA SET PROFILES
2 GENERAL RESOURCE PROFILES
3 GROUP PROFILES AND USER-TO-GROUP CONNECTIONS
4 USER PROFILES AND YOUR OWN PASSWORD
5 SYSTEM OPTIONS
99 EXIT
Licensed Materials - Property of IBM
5695-039 (C) Copyright IBM Corp. 1983, 1993
All Rights Reserved - U.S. Government Users
Restricted Rights, Use, Duplication or Disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Instructions
Enter "1" to select "DATA SET PROFILES".
April 2003
3-76
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 7:
RACF - DATA SET PROFILE SERVICES
OPTION ===> 1
SELECT ONE OF THE FOLLOWING:
1 ADD Add a profile
2 CHANGE Change a profile
3 DELETE Delete a profile
4 ACCESS Maintain the access lists
5 AUDIT Monitor access attempts (for auditors only)
DISPLAY Display profile contents
SEARCH Search the RACF data base for profiles
Instructions
Enter "1" to select "ADD - Add a profile".
April 2003
3-77
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEPS:
RACF - DATA SET PROFILE SERVICES - ADD
COMMAND ===>
ENTER THE FOLLOWING INFORMATION:
PROFILE NAME
TYPE
VOLUME SERIAL
===> AFSFILE.
===> GENERIC
USE A MODEL
MODEL, TAPE, GENERIC,
or blank
If a discrete profile and the
data set is not cataloged
If you are adding a profile
and specified VOLUME SERIAL
Data set password, if the data
is password protected
Re-enter password to verify
YES or NO
Instructions
Enter "AFSFILE.*" to set up a profile for all files that begin with "uuuaaaa.AFSFILE".
April 2003
3-78
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 9:
RACF - ADD DATA SET PROFILE
COMMAND ===5
PROFILE: AFSFILE.*
ENTER OR CHANGE THE FOLLOWING INFORMATION:
OWNER == = > ABC
LEVEL ===> 0
FAILED ACCESSES ===> FAIL
UACC ===> NONE
AUDIT SUCCESSES
AUDIT FAILURES
INDICATOR
NOTIFY
ERASE ON DELETE
TO ADD OPTIONAL INFORMATION, ENTER YES
===> NOAUDIT
===> READ
Userid or group name
0-99
FAIL or WARN
NONE, READ, UPDATE,
CONTROL, ALTER or EXECUTE
READ, UPDATE, CONTROL,
ALTER, or NOAUDIT
READ, UPDATE, CONTROL,
ALTER, or NOAUDIT
SET, NOSET, or ONLY
Userid
YES or blank
===> yes
Instructions
Enter "yes" to add optional information.
April 2003
3-79
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 10:
RACF - ADD DATA SET PROFILE
COMMAND ===>
PROFILE: AFSFILE.*
TO ADD THE FOLLOWING INFORMATION, ENTER YES:
OTHER VOLUMES
SECURITY LEVEL or CATEGORIES
SECURITY LABEL
INSTALLATION DATA
DFP-RELATED PARAMETERS
ACCESS LIST
TAPE-RELATED PARAMETERS
===> NO
===> NO
===> NO
===> NO
===> NO
===> yes
===> NO
Instructions
Enter "yes" to perform ACCESS LIST maintenance.
April 2003
3-80
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 11:
RACF - MAINTAIN DATA SET ACCESS LIST
OPTION ===> 1
PROFILE: AFSFILE.*
SELECT ONE OF THE FOLLOWING:
1 ADD Add users or groups.
Copy the access list from an existing profile.
2 REMOVE Remove specific users and groups from the access list.
3 RESET Remove all users and groups from the access list.
Instructions
Enter "1" to ADD users or groups to an existing access list.
April 2003
3-81
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 12:
RACF - MAINTAIN DATA SET ACCESS LIST - ADD
COMMAND ===>
PROFILE: AFSFILE.*
ENTER YES FOR EITHER OR BOTH OF THE FOLLOWING:
COPY ===> NO YES to copy the access list from another
profile.
SPECIFY ===> yes YES to specify the users and groups to be
added to the access list.
Instructions
Enter "yes" to SPECIFY the users and groups to be added to the access list.
April 2003
3-82
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 13:
RACF - MAINTAIN DATA SET ACCESS LIST - ADD
COMMAND ===>
PROFILE: AFSFILE.*
Enter the access authority to be granted:
AUTHORITY
===> alter NONE, READ, UPDATE,
CONTROL, ALTER or EXECUTE
Enter the users or groups for which entries are to be added:
===> jhl ===> tsdgrp ===>
To add these entries to the conditional access list,
enter YES ===>
Instructions
Enter "alter" in the AUTHORITY command line, and "jh1" and "tsdgrp" in the "users or
groups" area of the screen. Press ENTER when finished.
April 2003
3-83
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
STEP 14:
RACF - DATA SET PROFILE SERVICES
PROFILE ADDED
OPTION ===>
SELECT ONE OF THE FOLLOWING:
ADD Add a profile
CHANGE Change a profile
DELETE Delete a profile
ACCESS Maintain access list
AUDIT Monitor access attempts (Auditors only)
DISPLAY Display profile contents
SEARCH Search the RACF data base for profiles
Instructions
This screen confirms that the profile has been added (see top right corner of screen). Press
PF4 to return to the ISPF Primary Option Menu.
April 2003
3-84
Batch Updating
-------
AIRS User's Guide
AF3
AFS Data Storage
4.0
AFS Utilities
AFS utilities provide you with the ability to accomplish complex data management functions
through the use of simple user input utility screens.
In the following sections, Utilities will be described in detail. Each description will include sample
figures of the Utility screens.
4.1 Accessing Utilities
During the logon procedure outlined in Section 1.5, you logged onto AFS (Figure 1-7) and received
the AIRS Facility System Main Menu (Figure 1-8). Performing AFS utilities is accessed through this
menu by selecting option 4, entitled 'SELECT A UTILITY' and pressing as shown in Figure
4-1.
03/30/94
AIRS FACILITY SUBSYSTEM
MAIN MENU
PGM: AFPOOO
MAP: AFM0001
1 UPDATE THE DATABASE
2 BROWSE THE DATABASE
3 SELECT A REPORT
4 SELECT A UTILITY
ENTER MENU SELECTION:
NEED ASSISTANCE? CALL THE AFS HELPLINE AT 1-800-367-1044
PF1=HELP PF3=END PF4=SUBSYSTEM MENU PF5=TERM
FIGURE 4-1 AFS MAIN MENU SCREEN
April 2003
4-1
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
Utilities (Figure 4-2) offer the following functions:
PATE. : 05/05/94
AE.5 FACILITY 6U&5Y6TLM
UTILITY 5LLE.CTON MEJ^U
PCM AfPOOS
lv|AP: ATM0082
3 UNMLR.C.L PLANT6
4 PLLCTL INFORMATION
5 UNPELC.TE. INFORMATION
6 COMPLIANCLUI5TOR.Y
7 50UR.CC/POlNT 5\VAP
8 AROJlVt.
9 PCAROJlVt.
10 U5C.RJCLPARAMC.TER5
II TA&LC. FILL LOOklUP
12 5IP INVENTORY
13 UPPATLAF6 PLANT IP
\A 5U&MH~ CURRENT UTILITY FLE.
ENTER MENU SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-2 AFS UTILITY MENU SCREEN
To access a particular Utility, type the desired option number and press the key. The
next screen presented will be the Utility screen for the selected Utility option.
Because of the need to maintain on-line responsiveness, most utilities are processed in a batch
mode.
All utilities are invoked on-line through the use of the specific utility screen. However, the five
utilities that are processed on-line are: Option 5 - Undelete Information; Option 10 - User JCL
Parameters; Option 11 - Table File Lookup; Option 12 - SIP Inventory; and Option 13 - Update AFS
Plant Id. These Utilities are performed similar to online update. If the request is error free it is
performed when the key is pressed.
The utility request has passed the online edits if no error messages are returned to the screen.
When you press the key, processing is returned to the Utility Selection Menu. A batch
transaction has been generated for the AFS batch update for each utility not processed online.
The results of any AFS Utility that is processed in batch will be reported in the successful or failed
Utility Transaction section of the AFS batch processing report.
Error messages associated with each utility are explained at the end of each utility section.
The Merge Plants (association), Merge Points and Source/Point Swap Utilities may also be
performed by creating and submitting AFS batch transactions. The transaction types for these
April 2003
4-2
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
utilities are 60, 65 and 64 respectively. The layout of these batch transaction formats are included in
Appendix A. The Delete Utility is also supported using the update AFS batch transactions.
April 2003 4-3 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.2 Utility - Merge Plants (Association)
The Merge Plants (Association) utility allows you to take separate compliance and emissions facility
records for the same plant and combine them so that an 'associated' profile is created, replacing the
previous compliance-only and emission-only profiles. Associating of plants provides you with the
ability to update and retrieve both compliance and emissions data by specifying any of the IDs
applicable to the plant (CDS, NEDS, EPA, Dun & Bradstreet, etc.).
Each AFS plant meets one of three profiles:
COMPLIANCE AFS data pertains only to the plant's regulatory compliance
EMISSIONS AFS data pertains only to the plant's annual and/or SIP emission
inventories
ASSOCIATED AFS data pertains to a combination of the plant's regulatory compliance
and emission inventory.
To access the MERGE PLANTS (Association) Utility, select option 1 on the UTILITY MENU (Figure 4-
2) and press the key. The MERGE PLANTS (Association) Utility screen is shown in Figure
4-3.
05/01/94
AIRS FACILITY SUBSYSTEM
MERGE PLANTS (ASSOCIATION)
PGM: AFP022
MAP: AFM0221
PLEASE ENTER PLANT IDENTIFICATION:
CDS PLANT I.D. (STATE/COUNTY/PLANT)
PLEASE ENTER IDENTIFICATION OF PLANT TO BE MERGED:
NEDS OR CDS PLANT I.D. (STATE/COUNTY/PLANT)..
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-3 UTILITY MERGE PLANTS SCREEN
April 2003
4-4
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Two types of plant associations may be performed through this utility: compliance-to-compliance
and compliance-to-emissions. In both types of associations, the data elements on the primary
compliance facility common to both compliance and emissions facilities, such as name and address,
are retained for the associated plant general record. Those of the secondary plant are discarded.
To perform a compliance-to-compliance merge, fill in the state, county, and plant I.D. for the first
compliance plant on the first line. On the second line provide the state, county and plant I.D. of the
compliance plant you want merged into the first one. To perform a compliance-to-emissions
merge, fill in the state, county, and plant I.D. for the compliance plant on the first line and on the
second line provide the state, county and plant I.D. of the emission plant.
The results of the MERGE PLANT Utility will be reported in the successful or failed Utility
Transaction section of the AFS batch processing report.
All facility merge (association) information is retained for 3 months. Elements from the plant-
general records of emissions plants which have been associated to compliance plants are retained
to allow "dis-association" (unmerge) processing which can restore the original emissions plant
general information if associations occur in error. "Disassociation" (unmerge) processing performed
after the 3 month time frame will retain the compliance plant general information for both the
compliance and emissions facilities. See Section 4.4 for instructions on Unmerging.
Another way of performing this same type of Utility operation, is to create an AFS batch transaction.
The user would create a transaction type 60 providing the same fields as the on-line screens.
Additional fields necessary for batch are the transaction type, sequence number and update code.
This batch transaction would then be processed by utilizing the Update process (refer to Section
3.4.5).
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages. Clarification of the unfamiliar error conditions
specific to the Merge Plants (Association) Utility are described below.
Error Message: MERGED PLANTS CANNOT HA VE DUPLICA TE AIR PROGRAMS.
Explanation: The two compliance facilities requested to be merged (associated) have the same
air program code. One of the duplicate Air Programs must be deleted prior to
resubmitting the Merge Plant request. If the facilities do not have duplicate air
programs the message refers to the compliance history for the facility. Contact
the AFS Help Line to delete duplicate history records.
Error Message: CDS PLANTS MUST BE INDIRECT SOURCES.
Explanation: Two compliance facilities are entered that are located in a direct state rather than
in an indirect state. Direct states do not have indirect source id's and therefore
have no need to be merged (associated).
Error Message: THE FIRST CDS PLANT ENTERED MUST HAVE AN A CTION PRIOR TO
MERGING.
Error Message: THE SECOND CDS PLANT ENTERED MUST HA VE AN A CTION PRIOR TO
MERGING.
Explanation: One or both of the compliance facilities entered does not have a plant or point
action on either the first or second facility indicated. The action will distinguish
which Indirect State Source Id is associated to which Air Program Code. A plant
April 2003 4-5 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
or point action must exist on both plants before resubmitting the Merge Plant
request.
Error Message: (In Online mode a Window is displayed; in Batch a multiple line message is
displayed)
THESE FA CILITIES HA VE DIFFERENT AFS PLANT IDS,
AND CANNOT BE ASSOCIATED.
ONE (OR BOTH) OF THE AFS PLANT IDS MUST BE DELETED
BEFORE THESE IDS CAN BEASSOCIA TED.
USE THE UPDATE AFS PLANT ID UTILITY ON THE
UTILITY MENU TO DELETE THE AFS PLANT ID(S).
PLEASE PRESS ENTER TO CONTINUE.
The facilities entered have different AFS Plant IDs. Only one AFS Plant ID may be
assigned to a facility. This error condition requires the user to review the data
and determine which AFS Plant ID is the one to be perpetuated and remove the
other AFS Plant ID.
Explanation:
Error Message:
Explanation:
SIP LOCKED FACILITIES CANNOT BE MERGED.
Two compliance facilities are entered and the first facility is associated with an
emissions facility which is part of a frozen SIP inventory (an inventory that has not
been approved by headquarters). The emissions facility must be disapproved by
headquarters before it can be merged.
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated.
The following error messages will be received when the user does not have access for the request
submitted.
Error Message:
Explanation:
Error Message:
Explanation:
Error Message:
Explanation:
ACCESS TO FIRST CDS PLANT DENIED.
The user does not have compliance update access for the first CDS Plant
specified.
A CCESS TO STA TE PRIM A TE PLANT DENIED - FIRST CDS PLANT.
The first facility entered is State Private and the requestor does not have State
Private access.
CANNOT MERGE A PUBLIC AN DA STATE PRIVATE PLANT.
The first facility entered is State Private and the second facility entered is not
State Private, or the first facility entered is not State Private and the second facility
entered is State Private. Both facilities must be either public or state private to
perform the Merge Plants (Association) Utility.
April 2003
4-6
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Error Message: COM PL B EM IS UPDA TE A CCESS REQ WHEN A SSOC PLNTS W/AN AFS
PLNTID.
Explanation: Two compliance facilities are entered and one of the compliance facilities has an
AFS Plant ID and the user does not have compliance and emissions update
access. Both compliance and emissions update access is required to perform the
Merge Plants (Association) Utility on facilities with an assigned AFS Plant ID.
April 2003 4-7 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.3 Utility - Merge Points
The Merge Points utility allows you to take separate compliance and emissions point records for the
same plant and combine them so that a 'merged' point is created, replacing the previous
compliance-only and emission-only point. Merging of points provides you with the ability to update
and retrieve both compliance and emissions data by specifying the point number and a point
indicator of "M". This Utility may also be used to create a Merged point from an emission-only point
with no compliance counterpart.
Each AFS point record includes a field called Compliance/Emissions Indicator. These indicators are:
C - The point contains only compliance related data elements
E - The Point contains only emissions related data elements
M - The point contains both compliance and emissions data elements.
To access the MERGE POINTS Utility, select option 2 on the UTILITY MENU (Figure 4-1) and press
the key. The MERGE POINTS Utility screen is shown in Figure 4-4.
05/01/94
AIRS FACILITY SUBSYSTEM
MERGE POINTS
PGM: AFP025
MAP: AFM0251
PLEASE ENTER PLANT AND POINT IDENTIFICATION OF POINTS TO BE MERGED:
NEDS OR CDS PLANT I.D. (STATE/COUNTY/PLANT)..: / /
POINT...:
POINT...:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-4 UTILITY MERGE POINTS SCREEN
April 2003
4-8
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
The plant that you specify with the CDS Plant ID or NEDS Plant ID must be an associated plant and
must have been processed through the Direct Data Merge. When specifying 2 point numbers, one
must be a 'C' (Compliance) Point and the other must be an 'E' (Emissions) point. The point resulting
from the merge will be an M (Merged) point and will be valued with the Point Number that was
specified first. All point comments will be retained and will be renumbered. You may also convert
an 'E' point to an 'M' point using this utility by specifying the 'E' point as the first point and leave the
second point entry blank. A point description of "CREATED FROM MERGE" will be supplied.'
The results of the MERGE POINTS Utility will be reported in the successful or failed Utility
Transaction section of the AFS batch processing report.
Another way of performing this same type of Utility operation, is to create an AFS batch transaction.
The user would create a transaction type 65 providing the same fields as the on-line screens.
Additional fields necessary for batch are the transaction type, sequence number and update code.
This batch transaction would then be processed by utilizing the Update process (refer to Section
3.4.5).
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages. Clarification of the unfamiliar error conditions
specific to the Merge Points Utility are described below.
Error Message: MERGED POINTS CANNOT BE ADDED TO INDIRECT SOURCES.
Explanation: The facility State is an indirect state and merged points can only be added to a
direct state. Direct states are created using the Direct Data Merge.
Error Message:
Explanation:
Error Message:
Explanation:
Error Message:
Explanation:
Error Message:
Explanation:
COMPLIANCE EMISSION IDENTIFIERS MUST BE DIFFERENT.
The specified compliance emission identifiers are the same. You must enter
either a compliance point (compliance emissions identifier = 'C') and an emission
point (compliance emissions identifier = 'E') or an emission point (compliance
emissions identifier = 'E') with the second point identifier blank.
PLANT MUST BE MERGED.
The facility is not an associated facility. The facility must be merged (associated)
before adding a merged point. Merged points may not be added to compliance
only or emissions only facilities.
YOU CANNOT CONVERT A "C" TO AN "M" POINT.
Both the second point and compliance emission identifier are blank and first
compliance emission identifier is equal to 'C. Compliance points do not have the
same mandatory requirements as an emissions point (i.e. segment general).
BA SE POINT HA S ALREADY BEEN USED.
This message will be displayed when one of the following two situations
described is encountered. The first compliance emission identifier = 'C' and there
is a point with a compliance emission identifier of 'E' that already exists and the
first point is not equal to the specified second point, or the first compliance
emission identifier = 'E' and there is a point with a compliance emission identifier
of 'C that already exists and the first point is not equal to the specified second
point. A different base point must be used because a facility cannot have both an
'M' point and a 'C or 'E' point with the same point number.
April 2003
4-9
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated.
The following error messages will be received when the user does not have access for the request
submitted.
Error Message: COM P. B EM IS. UPDA TE A CCESS IS REQUIRED TO ADD A MERGED POINT.
Explanation: The user does not have both compliance and emissions update access. Since
the merged point may have both compliance and emissions data either as a
result of the merge or in the future, access to both compliance and emission are
required.
Error Message: A CCESS TO STA TE PRIM A TE INFORM A TION DENIED.
Explanation: The user does not have State Private access to the specified State Private facility.
April 2003 4-10 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.4 Utility - Unmerge Plants
The Unmerge utility disassociates compliance and emission information for plants merged in error.
The UNMERGE utility results in the re-creation of the original CDS and NEDS plant and point
information when the utility is invoked within 90 days of the association (Utility Merge) of a
compliance and emissions facility. (After 90 days, both Plant General records will contain the
merged version.) All record types associated with the original NEDS and CDS Plant Ids are
separated and restored to AFS under the separate plant IDs. Similarly, all point data are separated
and restored under the original plant and point IDs: all "E" points will be moved to the NEDS plant
ID and all "C" points will be moved to the CDS plant ID. The values for data elements with shared
ownership, which in the merged entities represented the original compliance value, will be restored
to the original compliance and emissions values.
Updates made to the merged facility are retained upon unmerging. However, if the plant general
and/or plant mail records were updated, these updates will be reflected in the unmerged
compliance facility. The emissions facility would reflect the values at the time of the merge, if
unmerged within the 90 day time frame.
LIMITATIONS:
1) The Unmerge Utility may not be performed for facilities that have Merged ("M")
points.
2) There is no automated utility to perform an unmerge between compliance plants.
To access the UNMERGE PLANT Utility, select option 3 on the UTILITY MENU (Figure 4-2) and press
the key. The UNMERGE PLANT Utility screen is shown in Figure 4-5.
05/01/94
AIRS FACILITY SUBSYSTEM
UNMERGE PLANTS/POINTS
PGM: AFP024
MAP: AFM0241
PLEASE ENTER PLANT IDENTIFICATION:
CDS PLANT I.D. (STATE/COUNTY/PLANT) : /
PLEASE ENTER IDENTIFICATION OF PLANT TO BE UNMERGED:
NEDS PLANT I.D. (STATE/COUNTY/PLANT) : /
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-5 UTILITY UNMERGE PLANT SCREEN
April 2003
4-11
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
To Unmerge a compliance and emissions plant, provide the compliance plant I.D. on the first line
and the emissions plant I.D on the second line. When you press the key, processing is
returned to the Utility Selection Menu. Even though a batch transaction has been generated for the
batch AFS update, no message indicating this will be displayed.
The results of the UNMERGE PLANTS Utility will be reported in the successful or failed Utility
Transaction section of the AFS batch processing report.
Following the unmerge the CDS and NEDS plants will be separate, and will not be linked in any way
in AFS.
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages. Clarification of the unfamiliar error conditions
specific to the Unmerge Plants Utility are described below.
Error Message:
Explanation:
Error Message:
Explanation:
FIRST PLANT ENTERED MUST BE A CDS PLANT.
An emissions facility is entered as the first facility.
MUST ENTER PLANT ID'S FROM THE SAME MERGED PLANT.
The compliance facility entered is not associated with the emissions facility
entered.
Error Message: MUST UNMERGE POINTS BEFORE UNMERGE OF PLANTS.
Explanation: The compliance facility entered has an 'M' (merged) point already. In order to
unmerge a facility that has an 'M' point, the user has to delete the 'M' point and re-
add the 'C' and 'E' points before unmerging the plant.
Error Message: SIP LOCKED FACILITIES CANNOT BE UNMERGED.
Explanation: The emissions facility is in a frozen SIP Inventory (an inventory that has not been
approved by headquarters). The emission facility must be disapproved by
headquarters before it can be unmerged.
Error Message: Online Window Selection; In Batch the AFS Plant ID will be assigned to the
unmerged Compliance facility.
THE SELECTED FACILITY CONTAINS AN AFS PLANT ID.
PLEASE SPECIFY WITH ANY ALPHA CHARACTER,
WHICH UNMERGED FACILITY WILL RECEIVE
THE AFS PLANT ID AND ANY ASSOCIATED PERMIT DATA.
FACILITY!:
FACILITY 2:
STI CNTYIPLNT1 : X
ST/ CNTY/ PLNT2 :
Explanation:
PLEASE PRESS ENTER TO CONTINUE
The facility to be unmerged has an AFS PLANT ID. The window prompts for a
response as to which facility, the compliance or the emissions, is to receive the
AFS Plant ID and associated Permit data when they are unmerged. No choice is
provided in batch mode. The compliance facility will always receive the AFS
April 2003
4-12
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Plant ID and associated Permit data when they are unmerged.
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated.
The following error messages will be received when the user does not have access for the request
submitted.
Error Message: UPDA TE A CCESS TO CDS PLANT DENIED.
Explanation: The user does not have compliance update access
Error Message: UPDA TE A CCESS TO NEDS PLANT DENIED.
Explanation: The user does not have emissions update access
Error Message: A CCESS TO STA TE PRIM A TE PLANT DENIED - FIRST CDS PLANT.
Explanation: The first facility entered is State Private and the user does not have State Private
access.
Error Message: A CCESS TO STA TE PRIM A TE NEDS PLANT DENIED.
Explanation: This occurs when the two facilities selected are not associated to each other. The
second facility entered is State Private and the user does not have State Private
access.
April 2003 4-13 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5 Utility - Delete
This Utility will DELETE all indicated records in their entirety from the database. Extreme caution
should be taken when using this Utility feature since NO back-ups are made of these records. This
DELETE Utility should only be used to remove erroneous records.
To access the DELETE Utility, select option 4 on the UTILITY MENU (Figure 4-2) and press the
key. A DELETE menu (Figure 4-6) defines the categories of AFS data that may be deleted
from AFS using the delete utility. These data include plant, stack, point, segment level data, as well
as record types associated with inventories, asbestos renovation/demolition contractors and
asbestos disposal landfills. Permit Administration records may also be deleted using this utility.
DATE : 05/01/94
SCREEN: 026
AIRS FACILITY SUBSYSTEM
DELETE INFORMATION
PGM: AFP026
MAP: AFM0261
1 PLANT
2 STACK
3 POINT
4 SEGMENT
5 INVENTORY
6 CONTRACTOR
7 LANDFILL
8 PERMIT ADMINISTRATION
ENTER LEVEL OF INFORMATION TO BE DELETED:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-6 UTILITY DELETE MENU SCREEN
Deletions will be made in accordance to the system hierarchy (see AFS Roadmap). Consequently,
records subordinate to a deleted record will also be deleted. For example, by specifying the deletion
of an emissions point, all existing point level records tied to that point will be deleted as part of the
point delete. These records include: comment, point pollutant, segment, segment pollutant,
segment comment, chemical and projected pollutant. Security is checked only on the parent
record, not on subordinate records.
Plant, Stack, Point and Segment Level Information screens require that you specify a Year of Record
when requesting to delete emissions information. The delete utility will only process the request for
the year of emissions inventory data specified. Any non-permanently archived year of emissions
inventory data is accessible. Entire plant delete restrictions are discussed in the plant- level delete
section.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the update, a utility report will be generated, identifying which records were deleted
and which delete requests resulted in errors.
Any delete transactions may be canceled prior to the AFS batch update by selecting Option 5,
April 2003
4-14
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Undelete Information, from the AFS Utility Menu Screen (Figure 4-2) and subsequently Option 1
from the Undelete Information. Refer to Section 4.6 for further information.
To access the desired DELETE screen, determine the AFS level where your request will be made.
Select the option and press the key. You will then be shown the applicable delete
screen.
The alternative to using the online Delete Utility is to create AFS Batch Transactions. To delete an
AFS record in batch, you need only supply the key fields, transaction type, sequence and an update
code of D on the transaction. All of the key fields one would have used with the on-line screen
would be the keys supplied on the batch transaction. Any valid sequence for the transaction type
corresponding to the record to be deleted can be supplied. For example, to delete an entire facility
submit a transaction type 10, with any one of the valid sequences with the keys, state, county, plant
ID and a "D" in the update code. Data fields are ignored if populated, except for transaction type A7
as explained in Section 3.2.7. Refer to Section 3.2.8 for more information on batch Delete
transactions and Section 4.12 for details on submitting batch transactions.
April 2003 4-15 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.1 Plant Level Delete
Plant Level Delete is used to delete entire facilities, Plant Pollutant records, Fee Certification records,
Mailing Label records, Air Programs records, Air Program Pollutant records, Action records,
Asbestos Performance records, Comments or to unlink Actions from pathways at Plant level.
To access PLANT LEVEL DELETE, select option 1 on the DELETE UTILITY MENU (Figure 4-6) and
press the key. PLANT LEVEL DELETE screen is shown in Figure 4-7.
DATE : 05/01/94
SCREEN: 108
AIRS FACILITY SUBSYSTEM
DELETE PLANT LEVEL INFORMATION
PGM: AFP108
MAP: AFM1081
PLEASE ENTER PLANT IDENTIFICATION
CDS PLANT I.D.
NEDS PLANT I.D.
(STATE/COUNTY/PLANT)
(STATE/COUNTY/PLANT)
PLEASE ENTER PLANT LEVEL KEY VALUES:
(FEE CERTIFICATION)
(MAILING LABEL)
(AIR PROGRAM)
(POLLUTANT AIR PROGRAM)
(POLLUTANT)
(ASBESTOS PERFORMANCE)
(ACTION)
(COMMENT)
(UNLINK ACTION)
(Y/N) :
(Y/N) :
AIR PROGRAM CODE:
AIR PROGRAM CODE:
STATE CODE .... :
ACTION :
ACTION :
KEY ACTION :
POLLUTANT/CAS #:
POLLUTANT/CAS #:
CONTRACTOR ID :
COMMENT # .... :
ACTION :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
(C/E)
FIGURE 4-7 PLANT LEVEL DELETE SCREEN
To delete plant level data, you must supply either a CDS Plant ID or NEDS Plant ID along with a year
of record, if applicable.
April 2003
4-16
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
If only a Plant ID is provided, confirmation to delete the entire plant will be requested (see Figure 4-8 '
DATE : 05/01/94
SCREEN: 108
AIRS FACILITY SUBSYSTEM
DELETE PLANT LEVEL INFORMATION
PGM: AFP108
MAP: AFM1081
PLEASE ENTER PLANT IDENTIFICATION :
CDS PLANT I.D. (STATE/COUNTY/PLANT) : /
NEDS PLANT I.D. (STATE/COUNTY/PLANT) : /
PLEASE ENTER PLANT LEVEL KEY VALUES:
(FEE CERTIFICATION) (Y/N) : _
(MAILING LABEL) (Y/N) : _
(AIR PR +
(POLLUT
ENTIRE PLANT IS TO BE DELETED.
(POLLUT
(ASBEST
(ACTION
(COMMEN
(UNLINK
IS THIS OK? (Y/N)
C/E)
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-8 DELETE ENTIRE PLANT CONFIRMATION SCREEN
Upon receiving confirmation, the appropriate AFS batch transaction will be generated to delete the data
indicated.
The DELETE transaction will be processed during the AFS batch update. Following the successful
completion
of the batch update, a utility report will be generated. The successful and failed utility transactions
identify the
plant record. Subordinate data deleted as a result of the hierarchy are not reported. Refer to the
introduction of
this section (4.5) for a example of the hierarchical delete.
When identifying a plant for deletion, if the facility is associated, both compliance and emissions
components
will be deleted regardless of the Plant ID entered.
To specify a particular plant level record to be deleted, such as Plant Air Program, you must identify
both the
plant and the key values required to identify each record.
to
To delete an air program, the user must have a special access code of "T". Prior to accepting a request
delete an air program code, this warning message will appear:
ALL ACTIONS ASSOCIATED WITH JUST THIS AIR PROGRAM WILL BE DELETED
USERS WHO RESPOND Y WILL HAVE THEIR AIR PROGRAM DELETE TRANSACTION
PROCESSED
USERS WHO RESPOND N WILL BE BROUGHT BACK TO THE ONLINE DELETE PLANT SCREEN
DO YOU WANT TO CONTINUE? (Y/N) _
Only users who possess a security profile permitting update access to compliance data will be allowed
-------
AIRS User's Guide
AF3 AFS Data Storage
to delete compliance plants and associated data from AFS. Only users who possess a security profile
permitting update
access to emissions data will be allowed to delete emissions plants and associated data from AFS. An
associated plant can only be deleted by users with update access to both compliance and emissions
data.
March 2006 4-17
Utilities
April 2003 4-18 Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Edits exist which may prevent the deletion of a plant, such as the presence of compliance history
records or the presence of actions which are less than three years old. The history records reflect the
facility's monthly and quarterly compliance status for the last two years, and the latest actions reflect
the most recent activity at the facility. Since this information indicates current activity and/or historical
information at the facility, it is recommended that the plant be considered for archiving instead of
deletion. Entire plants that are no longer operational should be archived (Option 8 on the Utility Menu)
rather than deleted to maintain the historical perspective of the facility. These edits are invoked when
an entire facility is requested to be deleted. Individual records within the facility are not affected by
these edits and may be deleted.
Additional edits include those encountered when an attempt has been made to delete current facilities
which have earlier years of inventory or ones that have been permanently archived. Permanently
archived facilities or current facilities which possess earlier years can only be deleted by the ADBA or
by a user with Administrative Delete capability setup in their user profile.
Administrative Delete capability is provided to users who have been designated to have delete
authority. The Regional Coordinators can request authority for themselves and/or other users. A
special function code is provided in the individual's profile indicating Administrative Delete capability.
The enhanced profile allows for the deletion of plants with historical compliance status records, actions
less than three years old or permanently archived plants. Facilities with earlier years of inventory may
be deleted after the prior years of data have been deleted. The earlier years may be deleted in any
order, but the current year of the data must always be deleted last.
The Unlink Action function is used to disassociate actions previously linked using Action Linking or
remove the key action designation from an action. Entering only the key action will remove the key
action designation and unlink all actions associated with that key action. Specifying a key action with a
specific linked action will sever the link between the action and the key action specified. No record
deletion is performed using this function.
Refer to the introduction of this section (4.5) and Section 3.2.8 - Delete Batch Transactions for
information on performing deletes in batch mode.
April 2003 4-19 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.2 Stack Level Delete
Stack Level Delete is used to delete entire Stack records, Stack pollutant records or Stack comment
records.
To access STACK LEVEL DELETE, select option 2 on the DELETE UTILITY MENU (Figure 4-6) and press
the key. The STACK LEVEL DELETE screen is shown in Figure 4-9.
DATE : 05/01/94
SCREEN: 110
AIRS FACILITY SUBSYSTEM
DELETE STACK LEVEL INFORMATION
PGM: AFP110
MAP: AFM1101
PLEASE ENTER PLANT IDENTIFICATION :
CDS PLANT I.D. (STATE/COUNTY/PLANT)
NEDS PLANT I.D. (STATE/COUNTY/PLANT)
PLEASE ENTER STACK LEVEL KEY VALUES:
(STACK)
(POLLUTANT)
(COMMENT)
STACK
STACK
STACK
POLLUTANT/CAS #
COMMENT #
(C/E)
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-9 STACK LEVEL DELETE SCREEN
To delete stack level data, you must supply either a CDS Plant ID or NEDS Plant ID and a Year of
Record.
You can specify subordinate stack level records to be deleted by supplying the key values required to
identify the record, such as a Stack Number-Pollutant Code combination. If only a Stack Number is
supplied, the stack and all records related to the stack will be deleted.
If only a CDS or NEDS Plant ID and a Stack Number are provided, confirmation to delete the entire
stack will be requested.
The DELETE transaction will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
Only users who possess a security profile which permits update access to emissions data will
be allowed to delete stack general records in AFS. Update access to compliance and/or
emissions data is necessary to delete stack pollutant information. If there are bubbled-up
emissions on the record, all other data besides the bubbled-up emissions data will be
April 2003
4-20
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
removed. The compliance emissions identifier on the stack comments indicates which update
access is required.
Refer to the introduction of this section (4.5) and to Section 3.2.8 - Delete Batch Transactions for
information on performing deletes in batch mode.
April 2003 4-21 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.3 Point Level Delete
Point Level Delete is used to delete entire Point records, Point Pollutant records, Point Tank records,
Point Air Program records, Point Monitor records, Point CEM Records, Point Action records, Point
Comment records, Point Asbestos Performance records, or to Unlink actions at Point level.
To access POINT LEVEL DELETE, select option 3 on the DELETE UTILITY MENU (Figure 4-6) and press
the key. The POINT LEVEL DELETE screen is shown in Figure 4-10.
DATE : 05/01/94 AIRS FACILITY SUBSYSTEM PGM: AFP112
SCREEN: 112 DELETE POINT LEVEL INFORMATION MAP: AFM1121
PLEASE ENTER PLANT IDENTIFICATION :
CDS PLANT I.D. (STATE/COUNTY/PLANT) : / /
NEDS PLANT I.D. (STATE/COUNTY/PLANT) : / / YEAR:
PLEASE ENTER POINT LEVEL KEY
(POINT) POINT
(TANK) POINT
(AIR PROGRAM) POINT
(POLLUTANT) POINT
(MONITOR) POINT
(CONT. EMISSIONS) POINT
(ASBESTOS PERF.) POINT
(ACTION) POINT
(COMMENT) POINT
ACTION
(UNLINK ACTIONS) POINT
PF1=HELP PF3=END PF4=MAIN
VALUES :
_ _ (C/E/M)
~~ ~ (C/E/M) AIR PROGRAM . . :
(C/E/M) POLLUTANT/CAS #:
(C/E/M) CHANNEL # .... :
(C/E/M) CHANNEL # .... : RQTR:
(C/E/M) ST / CONTRACTOR:
(C/E/M) ACTION :
(C/E/M) COMMENT # .... : (C/E)
CHANNEL # .... : RQTR:
(C/E/M) KEY ACTION . . . . : ACTION:
PF5=TERM
FIGURE 4-10 POINT LEVEL DELETE SCREEN
To delete point level data, you must supply either a CDS Plant ID or NEDS Plant ID, Year of Record (for
emissions or merged point data), and a Point Number.
You can specify subordinate point level records to be deleted by supplying the key values required to
identify the record, such as Point ID-Action Number combination. If only a CDS or NEDS Plant ID and a
Point Number are provided, confirmation to delete the entire point will be requested. The results of
this request will delete the point and all records related to the point.
The Compliance Emissions Identifier indicates the type of data contained on the point. Users who
possess a security profile which permits update access to compliance data may delete compliance
points (Compliance Emissions Identifier = C). Users who possess a security profile which permits
update access to emissions data may delete emissions points (Compliance Emissions Identifier = E). A
merged point can only be deleted by a user with update access to both compliance and emissions
data.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
Refer to the introduction of this section (4.5) and to Section 3.2.8 - Delete Batch Transactions for
information on performing deletes in batch mode.
April 2003
4-22
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
April 2003 4-23 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.4 Segment Level Delete
Segment Level Delete is used to delete entire Segments, Segment Pollutant records, Segment
Chemical records, Projected Segment Pollutant records, Segment Comment Records, and to Unlink a
Stack from a Segment.
To access SEGMENT LEVEL DELETE, select option 4 on the DELETE UTILITY MENU(Figure 4-6) and
press the key. The SEGMENT LEVEL DELETE screen is shown in Figure 4-11.
DATE : 05/01/94
SCREEN: 114
AIRS FACILITY SUBSYSTEM
DELETE SEGMENT LEVEL INFORMATION
PGM: AFP114
MAP: AFM1141
PLEASE ENTER PLANT IDENTIFICATION :
CDS PLANT I.D. (STATE/COUNTY/PLANT)
NEDS PLANT I.D. (STATE/COUNTY/PLANT)
PLEASE ENTER SEGMENT LEVEL KEY
* POINT : _
(SEGMENT) SEGMENT .... : _
(POLLUTANT) SEGMENT .... : _
(CHEMICAL) SEGMENT .... : _
(PROJECTED) SEGMENT .... :
(COMMENT) SEGMENT
(STACK LINK) SEGMENT
VALUES:
(E/M)
POLLUTANT/CHEMICAL ABSTRACT #:
CHEMICAL ABSTRACT # :
POLLUTANT/CHEMICAL ABSTRACT #:
PROJECTION YEAR :
EMISSION TYPE INDICATOR .... :
INVENTORY TYPE :
COMMENT # :
STACK :
(C/E)
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-11 SEGMENT LEVEL DELETE SCREEN
To delete segment level data, you must supply either a CDS Plant ID or NEDS Plant ID, Year of Record,
a Point Number, and a Segment Number.
You can specify subordinate segment level records to be deleted by supplying the key values required
to identify the record, such as a Segment Number-Pollutant Code combination. If only a Point and
Segment Number are supplied, the segment and all records related to the segment will be deleted. A
confirmation to delete the entire segment will be requested.
The DELETE transaction will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying the parent records
deleted.
If the segment being deleted is the only segment attached to the point, the request will be denied.
Minimum data requirements of AFS specify that each emission point have at least one segment
attached to it.
Only users who possess a security profile that permits update access to emissions data will be allowed
to delete segment records in AFS.
Stacks can be unlinked from segment(s) through the delete utility. If just a Stack Number is supplied,
all segments linked to the stack will have the Stack Number removed from their records. This
April 2003
4-24
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
operation does not delete the stack itself.
Refer to the introduction of this section (4.5) and to Section 3.2.8 - Delete Batch Transactions for
information on performing deletes in batch mode.
4.5.5 Inventory Delete
Inventory Delete is used to delete entire Inventory records or Inventory Comment records.
To access INVENTORY DELETE, select option 5 on the DELETE UTILITY MENU (Figure 4-6) and press
the key. The SIP INVENTORY DELETE screen is shown in Figure 4-12.
DATE : 05/01/94
SCREEN: 115
AIRS FACILITY SUBSYSTEM
DELETE SIP UTILITY INFORMATION
PGM: AFP115
MAP: AFM1151
PLEASE ENTER INVENTORY IDENTIFICATION:
BASE YEAR
SIP PROGRAM
INVENTORY TYPE ....
STATE CODE
COMMENT LEVEL INFORMATION:
COMMENT LEVEL
COMMENT NUMBER....
PF1=HELP PF3=END PF4=MAIN PF5=TERM
PROJECTED YEAR
STATUS AREA
RADIUS COUNTY/PLANT
FIGURE 4-12 SIP INVENTORY DELETE SCREEN
To delete SIP Inventory tracking data, you must supply the Base Year, SIP Program, Status Area,
Inventory Type, and State Code. You can specify subordinate SIP Inventory Comment Level records to
be deleted by adding the key values to the mandatory SIP data delete fields. If only a Base Year, SIP
Program, Status Area, Inventory Type and State Code are supplied, the SIP Inventory record will be
deleted. Deleting this record does not delete any SIP Inventory facility data submitted online
or in batch.
Only users who possess a security profile which permits update access to SIP data will be allowed to
delete SIP Inventory records in AFS.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying the record deleted.
Another method of deleting Inventory level records is to create an AFS batch transaction. The user
would create a transaction type 00 (Inventory SIP) or 07 (Inventory Comment) and supply any valid
sequence number. All of the key fields one would have used with the on-line screen would also need
to be provided on the batch transaction. Additional fields necessary for batch are the transaction type,
April 2003
4-25
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
sequence number and update code. This batch transaction would then be processed by utilizing the
Update process (refer to Section 3.4.5).
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages.
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated. The
following error messages will be received when the user does not have access for the request
submitted.
Error Message: UPDA TE A CCESS DENIED TO SIP IN FOR MA TION.
Explanation: The user does not have SIP Update access.
April 2003 4-26 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.6 Contractor Delete
Contractor Delete is used to remove Asbestos Contractors from the list of available Contractors.
To access CONTRACTOR DELETE, select option 6 on the DELETE UTILITY MENU (Figure 4-6) and press
the key. The CONTRACTOR DELETE screen is shown in Figure 4-13.
DATE : 05/01/94
SCREEN: 116
AIRS FACILITY SUBSYSTEM
DELETE CONTRACTOR INFORMATION
PGM: AFP116
MAP: AFM1161
PLEASE ENTER CONTRACTOR STATE:
CONTRACTOR ID:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-13 ASBESTOS CONTRACTOR DELETE SCREEN
To delete a Contractor ID, you must supply the Contractor State and Contractor ID. All records related
to the Contractor ID will be removed from the database.
Only users who possess a security profile which permits update access to compliance data will be
allowed to delete contractor records in AFS.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying the parent records
deleted.
Asbestos Contractors may also be deleted by creating an AFS batch transaction. The user would create
a transaction type 50 and supply any valid sequence number. All of the key fields one would have
used with the on-line screen would also need to be provided on the batch transaction. Additional fields
necessary for batch are the transaction type, sequence number and update code (D). This batch
transaction would then be processed by utilizing the Update process (refer to Section 3.4.5).
April 2003
4-27
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.7 Landfill Delete
Landfill Delete is used to delete Asbestos Landfills from the AFS Database list.
To access LANDFILL DELETE, select option 7 on the DELETE UTILITY MENU (Figure 4-6) and press the
key. The LANDFILL DELETE screen is shown in Figure 4-14.
DATE : 05/01/94
SCREEN: 118
AIRS FACILITY SUBSYSTEM
DELETE LANDFILL INFORMATION
PGM: AFP118
MAP: AFM1181
PLEASE ENTER LANDFILL EPA ID:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-14 ASBESTOS LANDFILL DELETE SCREEN
To delete a Landfill EPA ID, you must supply the ID of the Landfill to be deleted. All records related to
the Landfill EPA ID will be removed from the database.
Only users who possess a security profile which permits update access to compliance data will be
allowed to delete landfill records in AFS.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying the landfill record deleted.
Landfills may also be deleted by creating an AFS batch transaction. The user would create a transaction
type 51 and supply any valid sequence number. All of the key fields one would have used with the on-
line screen would also need to be provided on the batch transaction. Additional fields necessary for
batch are the transaction type, sequence number and update code (D). This batch transaction would
then be processed by utilizing the Update process (refer to Section 3.4.5).
April 2003
4-28
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.5.8 Permit Administration Delete
Permit Administration Delete is used to delete records associated with Title V Permit Administration
Tracking.
To delete information pertaining to PERMIT ADMINISTRATION, select option 8 on the DELETE UTILITY
MENU (Figure 4-6) and press the key. The PERMIT ADMINISTRATION DELETE MENU
screen is shown in Figure 4-15.
DATE : 05/01/94
SCREEN: 026
AIRS FACILITY SUBSYSTEM
DELETE PERMIT ADMINISTRATION
1 APPLICATION GENERAL
2 ASSOCIATIONS
3 PERMIT GENERAL
ENTER LEVEL OF INFORMATION TO BE DELETED:
PGM: AFP026
MAP: AFM0262
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-15 PERMIT ADMINISTRATION DELETE MENU
To access the desired PERMIT ADMINISTRATION DELETE screen, determine the level where your
request will be made. Select the option and press the key. The applicable delete screen will
be presented.
Delete capabilities for Permits are dependent on a combination of compliance or emissions access
authority, the Permit data type to be deleted, ownership/origin of the data and authority as stored on
the AFS Permitting Authority Table.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
April 2003
4-29
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
APPLICATION GENERAL
The delete screen for Application Information is used to delete Permit Applications, Permit Application
Actions (Cycle I Actions), and any Cycle I comments.
To access APPLICATION LEVEL DELETE, select option 1 on the PERMIT ADMINISTRATION MENU
(Figure 4-15). The DELETE APPLICATION INFORMATION screen is shown in Figure 4-16.
DATE : 07/18/94
SCREEN: 124
AIRS FACILITY SUBSYSTEM
DELETE APPLICATION INFORMATION
PGM: AFP124
MAP: AFM1241
PLEASE ENTER PLANT IDENTIFICATION :
AFS PLANT ID (STATE/COUNTY/PLANT) :
PLEASE ENTER APPLICATION KEY VALUES:
(APPLICATION) APPLICATION:
(ACTION)
APPLICATION:
PERMIT:
ACTION TYPE:
ACTION NUMBER:
(ACTION CMNT) APPLICATION:
PERMIT:
ACTION TYPE:
ACTION NUMBER:
COMMENT NUMBER:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-16 APPLICATION DELETE SCREEN
To delete Permit Application records, you must supply an AFS Plant ID and an Application Number.
You can specify subordinate Application records to be deleted by supplying the key values required to
identify the record, such as Application Number, Action Type, Action Number or comment number. If
only the AFS ID and Application number are provided, a confirmation message will ask for verification
to delete the entire Application. At least one Application number is required. If Application Number
was entered on Cycle II actions and comments, these also get deleted when an Application is deleted.
Permit Administration contains a generated field called Permit Status. Certain Event Tracking activity
will generate this flag. If this flag indicates that a Permit has been Issued or is Pending the delete
request will be denied.
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
Permit Administration records may also be deleted by creating AFS batch transactions. The user would
create transaction types A1, A8 or C1. All of the key fields one would have used with the on-line screen
April 2003
4-30
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
would also need to be provided on the batch transaction. Additional fields necessary for batch are the
transaction type, sequence number and update code (D). This batch transaction would then be
processed by utilizing the Update process (refer to Section 3.4.5).
ASSOCIATION DELETE
The DELETE ASSOCIATION function is used to delete Association records, remove Applications from
the Association record, delete Cycle II Actions, and Cycle II Action comments or delete Permit
Comments associated with a Permit.
To access DELETE ASSOCIATION, select option 2 on the PERMIT ADMINISTRATION MENU (Figure 4-
15). The DELETE ASSOCIATION screen is shown in Figure 4-17.
DATE : 07/18/94
SCREEN: 126
AIRS FACILITY SUBSYSTEM
DELETE ASSOCIATION INFORMATION
PGM: AFP126
MAP: AFM1261
PLEASE ENTER PLANT IDENTIFICATION :
AFS PLANT ID (STATE/COUNTY/PLANT)
PLEASE ENTER ASSOCIATION KEY VALUES:
(ASSOCIATION) PERMIT:
(REMOVE APPLICATION ONLY) PERMIT:
(ACTION) PERMIT:
APPLICATION:
APPLICATION:
ACTION TYPE:
(ACTION CMNT) PERMIT:
ACTION TYPE:
(PLANT PERMIT CMNT) PERMIT:
ACTION NUMBER:
APPLICATION:
ACTION NUMBER: COMMENT NUMBER:
COMMENT NUMBER:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-17 ASSOCIATION DELETE SCREEN
To delete an Association record, you must supply an AFS Plant ID.
You can specify Association records to be deleted by supplying the key values required to identify the
record, such as Permit number, Application Number, Action Type, Action Number or comment
number. At least one Association level must be filled in.
Permit Administration contains a generated field called Permit Status. Certain Event Tracking activity
will generate this flag. If this flag indicates that a Permit has been Issued or is Pending the Association
record can not be deleted.
If only the PERMIT number is provided, a confirmation to delete the entire Association record will be
April 2003
4-31
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
requested.
Permit Association records may also be deleted by creating AFS batch transactions. The user would
create transaction types A2, A8, C1 or B9. All of the key fields one would have used with the on-line
screen would also need to be provided on the batch transaction. Additional fields necessary for batch
are the transaction type, sequence number and update code (D). This batch transaction would then be
processed by utilizing the Batch Submittal Utility. (Refer to Section 4.15 for Batch Submittal details.)
The DELETE transaction will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
PERMIT DELETE
The DELETE PERMIT function is used to delete Permit records, remove Cycle II Actions, Cycle II Action
Comments, Cycle III Actions, Cycle III Action Comments and Plant Permit comments.
To access DELETE PERMIT, select option 3 on the PERMIT ADMINISTRATION MENU (Figure 4-15). The
DELETE PERMIT screen is shown in Figure 4-18.
DATE : 07/18/94
SCREEN: 128
AIRS FACILITY SUBSYSTEM
DELETE PERMIT INFORMATION
PGM: AFP128
MAP: AFM1281
PLEASE ENTER STATE IDENTIFICATION: STATE:
PLEASE ENTER PERMIT KEY VALUES:
(PERMIT) PERMIT:
(ACTION) PERMIT: ACTION TYPE:
ACTION TYPE:
(ACTION CMNT) PERMIT:
COMMENT NUMBER:
(PERMIT CMNT) PERMIT:
ACTION NUMBER:
ACTION NUMBER:
COMMENT NUMBER:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-18 DELETE PERMIT SCREEN
April 2003
4-32
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
To delete a PERMIT record, you must supply a State Code or State Abbreviation, and a Permit Number.
You can specify subordinate PERMIT records to be deleted by supplying the key values required to
identify the record, such as Permit number, Action Type, Action Number or Comment Number. At least
one PERMIT level must be filled in.
Permit Administration contains a generated field called Permit Status. Certain Event Tracking activity
will generate this flag. If this flag indicates that a Permit has been Issued or is Pending the Action,
Action comment or Permit comment may not be deleted.
If only the PERMIT number is provided, a confirmation to delete the entire PERMIT will be requested.
Permit records may also be deleted by creating AFS batch transactions. The user would create
transaction types A2, A8, C1 or B9. All of the key fields one would have used with the on-line screen
would also need to be provided on the batch transaction. Additional fields necessary for batch are the
transaction type, sequence number and update code (D). This batch transaction would then be
processed by utilizing the Update process (refer to Section 3.4.5).
The DELETE request will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
deleted.
April 2003 4-33 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.6 Utility - Undelete
The UNDELETE Utility is used to remove delete requests from the AFS batch transaction file BEFORE
they have been processed by the AFS batch update. A typical use for UNDELETE is when an online
DELETE request has been issued in error.
To access the UNDELETE Utility, select option 5 on the UTILITY MENU (Figure 4-6) and press the
key. The UNDELETE Menu screen is shown in Figure 4-19.
DATE : 05/01/94
SCREEN: 028
AIRS FACILITY SUBSYSTEM
UNDELETE INFORMATION
PGM: AFP028
MAP: AFM0281
1 CANCEL FOR UNPROCESSED DELETION
2 UNDELETE FOR PROCESSED DELETION (RESTORE DATABASE)
ENTER SELECTION:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-19 UNDELETE MENU SCREEN
The UNDELETE INFORMATION utility menu displays two options.
Option 1, "Cancel for Unprocessed Deletion" allows you to cancel a delete transaction that has not yet
been processed. This applies when the AFS batch update has not processed the DELETE request and
you may remove the request from the transaction file. You can only undelete transactions that you
submitted.
Option 2 is not available at this time.
April 2003
4-34
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
Selecting Option 1 will bring you to the following screen:
DATE : 05/01/94
SCREEN: 028
AIRS FACILITY SUBSYSTEM
UNDELETE INFORMATION
PLEASE ENTER PLANT IDENTIFICATION :
CDS PLANT I.D. (STATE/COUNTY/PLANT) :
NEDS PLANT I.D. (STATE/COUNTY/PLANT) :
SIP INVENTORY I.D. (STATE) :
PGM: AFP028
MAP: AFM0282
NOTE: (1) ENTER ONLY STATE, OR STATE AND COUNTY, TO
DISPLAY MORE THAN ONE PLANT.
(2) IF ENTRY IS MADE ON CDS PLANT LINE ONLY CDS
OR MERGED PLANTS WILL BE LISTED. IF ENTRY IS
MADE ON NEDS LINE ONLY NEDS OR MERGED PLANTS
WILL BE LISTED.
(3) IF ENTRY IS MADE ON SIP LINE, ONLY INVENTORY AND
INVENTORY COMMENTS WILL BE LISTED.
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-20 CANCEL UNPROCESSED DELETES SCREEN
This UNDELETE INFORMATION utility screen allows you to specify the delete transactions that you
wish to cancel. The resulting screen will be a list of the deletes that meet your criteria request. (Refer to
Figure 4-21.)
To display delete transactions for more than one plant, specify a State or State and County.
If a NEDS Plant ID is entered, only NEDS plant and merged plant deletion requests will be displayed.
If a CDS Plant ID is entered, only CDS plant and merged plant deletion requests will be displayed.
All individual delete requests for a plant or geography specified will be displayed.
If an entry is made for SIP Inventory ID, only SIP Inventory and SIP Inventory Comment deletion
requests will be displayed.
April 2003
4-35
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
DATE : 09/21/94
SCREEN: 028
AIRS FACILITY SUBSYSTEM
CANCEL DELETION INFORMATION
PGM: AFP120
MAP: AFM1201
PLANT ID
1 22-001-00217
DELETION REQUEST
ENTIRE POINT 001 C DELETE INDIRECT = 00217
******* END OF DATA ********
USER
KGJ
ENTER SELECTION TO CANCEL:
PF1=HELP PF3=END PF4=MAIN PF5=TERM PF7=PREV PF8=NEXT
FIGURE 4-21 CANCEL DELETION INFORMATION SCREEN
The data displayed on the screen will reflect all unprocessed delete requests that match your search
criteria. You may cancel as many requests as needed. The request is canceled upon pressing the
key.
April 2003
4-36
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.7 Compliance History
The COMPLIANCE HISTORY utility supports the taking of monthly or quarterly 'snapshots' of various
plant compliance parameters tracked by EPA headquarters.
This utility may only be invoked by AFS administrative personnel. Authorization is controlled by the
security profile special functions.
To access the COMPLIANCE HISTORY Utility, select option 6 on the UTILITY MENU (Figure 4-6) and
press the key. The COMPLIANCE HISTORY screen is shown in Figure 4-22.
DATE : 05/05/94 AIRS FACILITY SUBSYSTEM
COMPLIANCE HISTORY UTILITY
PGM: AFP030
MAP: AFM0301
GENERATE MONTHLY COMPLIANCE HISTORY (Y/N)
GENERATE QUARTERLY COMPLIANCE HISTORY (Y/N)
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-22 COMPLIANCE HISTORY SCREEN
For monthly historical updates, the current compliance status value for each air program associated
with every compliance facility will be replicated and stored as the most recent entry to the monthly
historical record. Each record maintains the last thirty-six compliance statuses, along with the month
and year associated with each status.
For quarterly historical updates, the current compliance status value for each air program associated
with every compliance facility will be replicated and stored as the most recent entry to the quarterly
historical record. In addition, the current compliance status for each air program maintained at every
point associated with a compliance facility will be replicated and stored.
Each quarterly historical record maintains the last twelve quarterly compliance statuses, along with the
quarter and year associated with each status. Compliance status cycles for repeat violators are also
evaluated during the historical utility processing. The number of times a plant goes from
out-of-compliance, in-compliance, and back to out-of-compliance is recorded and stored in repeating
violator fields for each relevant air program.
January 2007
Utilities
4-37
-------
AIRS User's Guide
AF3 AFS Data Storage
The COMPLIANCE HISTORY request will be processed during the AFS batch update.
April 2003 4-38 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.8 Source/Point Swap
The Source Swap function allows you to replace either a CDS or NEDS Plant ID with another unique
Plant ID, swap a plant to another county, or swap both county and Plant ID at the same time. The Point
Swap function allows you to replace a Point ID with another unique Point ID.
AFS does not permit CDS or NEDS Plant IDs to be reused and will prohibit users from supplying IDs that
are associated with existing or archived plants.
To access the SOURCE/POINT SWAP Utility, select option 7 on the UTILITY MENU (Figure 4-6) and press
the key. The SOURCE/POINT SWAP screen is shown in Figure 4-23.
DATE : 05/05/94
SCREEN: 132
AIRS FACILITY SUBSYSTEM
SOURCE / POINT SWAP
PGM: AFP132
MAP: AFM1321
PLEASE ENTER CURRENT PLANT IDENTIFICATION:
CDS PLANT I.D. (STATE/COUNTY/PLANT) : / /
NEDS PLANT I.D. (STATE/COUNTY/PLANT): / /
PLEASE ENTER NEW PLANT IDENTIFICATION:
CDS PLANT I.D. (STATE/COUNTY/PLANT) : / /
NEDS PLANT I.D. (STATE/COUNTY/PLANT): / /
PLEASE ENTER CURRENT POINT IDENTIFICATION:
(STATE/COUNTY/PLANT/POINT/CEID): / /
PLEASE ENTER NEW POINT IDENTIFICATION:
(POINT/CEID) : / _
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-23 SOURCE/POINT SWAP SCREEN
To perform a source swap, supply an existing CDS or NEDS Plant ID in addition to a new and unique
CDS or NEDS Plant ID, respectively. All information currently associated with the plant, as well as other
identifiers (e.g. Dun & Bradstreet) will be cross-referenced to the new Plant ID. The source swap
function is performed in batch.
The state code or state abbreviation must be the same in both the current and new fields.
In order to swap a facility to a new county, provide the current state code or abbreviation, the current
county code and the current CDS or NEDS Plant ID in the section marked "ENTER CURRENT PLANT
IDENTIFICATION". Then enter the new identification fields in the section marked "ENTER NEW PLANT
IDENTIFICATION'. Use the same state code or abbreviation as the current plant ID and provide a NEW
county code. If the CDS or NEDS Plant ID does not exist in the NEW county, you may use the current
CDS or NEDS ID's in the NEW plant fields. However, if these Plant ID's DO exist in the NEW county, you
MUST supply a NEW CDS or NEDS ID.
April 2003
4-39
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
Only users with update access to compliance, emissions or associated plant data may perform source
swaps, and may only modify those plant ID types for which they have update access.
To perform a point swap, bypass the top portion of the screen. Supply an existing CDS or NEDS Plant
ID, Point ID and point compliance/emissions identifier in addition to a new and unique Point ID and point
compliance/emissions identifier, respectively. The point compliance/emissions identifiers must be the
same.
All information currently associated with the plant, as well as other identifiers (e.g. Dun & Bradstreet) will
be cross-referenced to the new Plant ID.
Source/Point Swap may also be performed by creating AFS batch transactions. The user would create
transaction type 64 and supply all the key fields one would have used with the on-line screen.
Additional fields necessary for batch are the transaction type, sequence number and update code (C).
This batch transaction would then be processed by utilizing the Update process (refer to Section 3.4.5)
Whether initiated through the online Utility or by batch submittal, the SWAP request is validated and will
be processed during the AFS batch update. Following the successful completion of the batch update, a
utility report will be generated, identifying the success or failure of the swap.
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages. Clarification of the unfamiliar error conditions specific to
the Source/Point Swap Utility are described below.
Error Message:
Explanation:
Error Message:
Explanation:
CANNOT CHANGE A CDS PLANT TO A NEDS PLANT.
The current CDS Plant ID and the new NEDS Plant ID are both entered. A CDS Plant
ID can only be swapped to another CDS Plant ID.
CANNOT CHANGE A NEDS PLANT TO A CDS PLANT.
The current NEDS Plant ID and the new CDS Plant ID are both entered. A NEDS Plant
ID can only be swapped to another NEDS Plant ID.
Error Message: THE CURRENT PLANTS AFS PLANT ID ALREADY EXISTS IN NEW COUNTY.
Explanation: The AFS Plant ID associated to the current CDS or NEDS Plant Identifier already exists
in the new county. A plant is not allowed to be swapped to a new county if the AFS
Plant ID associated with the plant being swapped already exists in that new county.
Error Message: IDS A SSOCIA TED WITH PLANT BEING S WAPPED ALREADY EXIST IN NEW
CNTY.
Explanation: The CDS Plant Identifier(s) or the NEDS Plant Identifier associated to the current CDS
Plant Identifier already exists in the new county or the CDS Plant Identifier(s)
associated to the current NEDS Plant Identifier already exists in the new county. A
plant is not allowed to be swapped to a new county if the IDs associated with the
plant being swapped already exist in that new county.
Error Message: THE CURRENT PLANTS PROGRAM/STA TUS AREA IS INVALID FOR NEW
COUNTY.
Explanation: The current associated or NEDS Plant Program/Status area is not in a valid
Program/Status Area for the new county.
April 2003
4-40
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
Error Message:
Explanation:
THE PLANTS CITY CODE IS INVALID FOR NEW PLANTS PGM/STATUS AREA.
The city code on current associated CDS Plant or the current NEDS Plant city code is
not a valid city code in the new plant's Program/Status Area. The current NEDS
facility has a Program/Status area identified on its plant general record. The county
the plant is to be swapped to is not in the same Program/Status area. The current
Program/Status area must be changed or blanked out prior to requesting the swap.
Error Message: COMPLIANCE EMISSIONS IDENTIFIERS MUST BE THE SAME FOR POINT
SWAP.
Explanation: The current and new compliance emissions identifiers are not the same. Only the
point number can be swapped not the type of point.
Error Message: BA SE POINT HA S ALREADY BEEN USED.
Explanation: The base point that has been specified to be swapped already exists.
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated. The
following error messages will be received when the user does not have access for the request
submitted.
Error Message: COMPLIANCE UPDA TE A CCESS TO CURRENT GEOGRAPHIC AREA DENIED.
Explanation: The user does not have Compliance Update Access to the current CDS Plant's
geography.
Error Message: EMISSIONS UPDA TE A CCESS TO CURRENT GEOGRAPHIC AREA DENIED.
Explanation: The user does not have Emissions Update Access to the current NEDS plant's
geography.
Error Message: COMPLIANCE UPDA TE A CCESS TO NEW GEOGRAPHIC AREA DENIED.
Explanation: A county user does not have Compliance Update Access for the new CDS Plant
county specified.
Error Message: EMISSIONS UPDA TE A CCESS TO NEW GEOGRAPHIC AREA DENIED.
Explanation: A county user does not have Emissions Update Access for the new NEDS Plant
county specified.
Error Message: STA TE PRIM A TE A CCESS TO CURRENT PLANT DEN/ED.
Explanation: The user does not have State Private Access for either the current CDS Plant or the
current NEDS Plant.
Error Message: STA TE PRIM A TE A CCESS TO NEW COUNTY DEN/ED.
Explanation: The user does not have State Private Access for either the new CDS Plant or the new
NEDS Plant.
April 2003
4-41
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.9 Archive
The ARCHIVE function allows you to remove data from AFS production files and place them on AFS
archive files. The data becomes "permanently archived" which means that the facility is not expected to
undergo further updating. This Utility CAN NOT be used prior to the entry of a new annual emissions
inventory. This feature enables you to eliminate obsolete information from your data files, thereby
increasing overall system processing and storage efficiency while allowing you to retain data for
historical or analytical purposes.
To access the ARCHIVE Utility, select option 8 on the UTILITY MENU (Figure 4-6) and press the
key. The ARCHIVE screen is shown in Figure 4-24.
05/05/94
AIRS FACILITY SUBSYSTEM
ARCHIVE
PGM: AFP032
MAP: AFM0321
PLEASE ENTER IDENTIFICATION OF PLANT TO BE ARCHIVED:
CDS OR NEDS PLANT I.D. (STATE/COUNTY/PLANT)..:
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-24 ARCHIVE SCREEN
To perform an ARCHIVE, supply an existing CDS or NEDS Plant ID. All information currently associated
with the plant will be archived.
The ARCHIVE request is validated and will be processed during the AFS batch update. Following the
successful completion of the batch update, a utility report will be generated, identifying the success or
failure of the archive.
Should you want to restore the plant to the AFS production files at a future date, you can do this using
the Dearchive Utility described in Section 4.10.
April 2003
4-42
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
Error Conditions:
Basic error conditions such as "invalid state" or "plant does not exist" are validated for all utilities and
reported with self explanatory error messages. Clarification of the unfamiliar error conditions specific to
the Archive Utility are described below.
Error Message: A PLANT WITH A CTIONS LESS THAN 3 YEARS OLD CANNOT BE ARCHIVED.
Explanation: The compliance or associated facility has actions that are less than three years old
(based on date achieved). AFS does not allow facility's to be archived with recent
activity.
Security Error Messages:
Each utility validates the update access authority of the requestor with the data to be manipulated. The
following error messages will be received when the user does not have access for the request
submitted.
Error Message: UPDA TE A CCESS TO CDS PLANT DEN/ED.
Explanation: The facility is compliance-only and the user does not have compliance update access
for the facility.
Error Message: UPDA TE A CCESS TO NEDS PLANT DEN/ED.
Explanation: The facility is emissions-only and the user does not have emissions update access for
the facility.
Error Message: A CCESS TO STA TE PRIM A TE INFORM A T/ON DEN/ED.
Explanation: The user does not have State Private access to the specified State Private facility.
Error Message: UPDA TE A CCESS TO MERGED PLANT DEN/ED.
Explanation: The facility is associated/merged and the user does not have compliance and
emissions update access for the facility. A user must have both compliance and
emissions update access to archive a merged plant.
Error Message: UPDA TE A CCESS DEN/ED TO S/P INFORM A T/ON.
Explanation: The facility is a SIP-designated facility. The user is not ADBA and does not have
update access to SIP information for the facility.
April 2003 4-43 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.10 Dearchive
The Dearchive function provides you with the opportunity to reactivate permanently archived facilities.
However, states that have gone through the Direct Data Merge cannot dearchive associated or
compliance only facilities if they were archived prior to the Direct Data Merge. Once a plant has been
dearchived successfully, all system functions (update, browse, reporting and utilities) are allowed.
To access the DEARCHIVE Utility, select option 9 on the UTILITY MENU (Figure 4-6) and press the
key. The DEARCHIVE screen is shown in Figure 4-25.
05/05/94
AIRS FACILITY SUBSYSTEM
DEARCHIVE
PGM: AFP035
MAP: AFM0351
PLEASE ENTER IDENTIFICATION OF PLANT TO BE DEARCHIVED:
STATE / COUNTY / PLANT ID TYPE / PLANT IDENTIFIER
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-25 DEARCHIVE SCREEN
Specify the facility to be dearchived by entering the FIPS State code or postal abbreviation, FIPS county
code, plant ID type and plant identifier.
Upon successful completion of the DEARCHIVE request, an AFS batch transaction will be generated.
The DEARCHIVE transaction will be processed during the AFS batch update. Following the successful
completion of the batch update, a utility report will be generated, identifying which records were
dearchived.
April 2003
4-44
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.11 User JCL Parameters
The definition of JCL is simply Job Control Language; The descriptive and control statements used to
direct the operating system of the IBM computer in the processing of a batch job.
Job Control Language is required in AFS anytime a batch job is submitted by the user. This could be an
Ad-hoc report, a Fixed Format report, or perhaps requesting a hard copy of an AFS table using Table
File Look-up.
The User JCL Parameters Utility function allows you to provide default JCL parameters for your User ID.
Once you have established default JCL parameters, JCL parameters will always be provided for you
when requesting a batch job, thereby eliminating the need to fill them in each time. If any JCL
parameter needs to be changed for a particular batch job, the user only changes those parameters.
(Note: The JCL change is performed while submitting the particular operation; Users do not have to
return to this Utility to make temporary changes to JCL).
To access the USER JCL PARAMETERS UTILITY, select option 10 on the UTILITY MENU (Figure 4-6) and
press the key. The USER JCL PARAMETERS screen is shown in Figure 4-26.
05/05/94
AIRS FACILITY SUBSYSTEM
USER JCL PARAMETERS
PGM: AFP136
MAP: AFM1361
JOB NAME
ACCOUNT CODE
FIMAS ID
TIME (MMMM)
TIME (SS)
PRIORITY CODE
MSGCLASS
NUMBER OF COPIES
FORM NUMBER
ROOM/BIN NUMBER
HOLD OUTPUT? (Y/N)
PRINTER SITE ID
2
A
1
MKGJ
Y
R255
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-26 USER JCL PARAMETERS SCREEN
These individual parameters are utilized to process batch jobs through the NCC-IBM system. Parameter
data are entered in the following fields:
JOB NAME The name you apply to a particular batch processing job - not required.
ACCOUNT CODE The NCC account code that your User ID is connected to.
FIMAS ID An NCC Utilization Identifier used to identify a specific system or activity and to
April 2003
4-45
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
associate computer usage statistics with that activity. Compliance users
should use a FIMAS ID = AFSCP, while emissions users should enter AFSEP.
TIME (MM MM) The maximum amount of minutes you authorize the job to run, ranging from 0
- 1450. By NCC standards, jobs given 5 minutes or more will automatically be
held for processing during the upcoming night; jobs with fewer minutes will be
processed, when possible, during the day which they are submitted.
TIME(SS) The maximum amount of seconds you authorize the job to run, ranging from 1
-59.
PRIORITY CODEPriority you assign to the processing of your job. A code = 1 results in processing that
night while a code = 2 results in same day processing, at increased cost. The priority
code does not override the NCC time standards. A code = 0 results in processing
during the following weekend.
MESSAGE CLASS An optional parameter used to designate printer type; 'A' = remote site or
non-laser NCC printer, 'F'= NCC laser printer. If left blank, the default value=A.
A message class of 'Z' will cause the JCL stream to be held, while allowing the
report to print.
NUMBER OF COPIES An optional parameter indicating the number of copies of a report to be
printed. If left blank, the default value = 1.
FORM NUMBER An optional parameter which indicates the type of form desired for printed
output. Blanks default to the standard form on the printer where output has
been directed.
ROOM/BIN NUMBER The location in a printer room to which printed output should be left for the
user, i.e. cubbyhole.
HOLD OUTPUT Approval to print job or hold for online review.
PRINTER SITE ID The ID of the remote job printer site.
Use the TAB key to maneuver around the USER JCL PARAMETER screen. When your satisfied with the
parameters, press . Processing will return to the UTILITY MENU.
These parameters may be modified by the user at any time.
April 2003 4-46 Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
4.12 Table File Lookup Utility
The TABLE FILE LOOKUP option provides access to tables used within AFS for cross reference and
validation checking.
Through this utility, you may view table values on-line or may also send a copy of a table to a printer
location.
To access the TABLE FILE LOOKUP UTILITY option, select option 11 on the UTILITY MENU (Figure 4-5)
and press the key. The TABLE FILE LOOKUP MENU is shown in Figure 4-27.
05/05/94
AIRS FACILITY SUBSYSTEM
TABLE FILE MAINTENANCE MENU
PGM: AFP150
MAP: AFM1501
1 ACTIONS
2 DESCRIPTIONS
3 EMISSION FACTORS
4 EMISSION TYPES
5 LATITUDE/LONGITUDE
6 PERMITS
7 PLANT IDENTIFICATION
8 POLLUTANT
9 REPORT TABLES
10 RESULTS
11 SAROAD/FIPS COUNTY/CITY XREF
12 SOURCE CLASSIFICATION CODE TABLES (SCC)
13 STAFF
14 STANDARD INDUSTRIAL CLASS TABLES (SIC)
15 USER JCL
16 USER PROFILE
17 UTM
ENTER MENU SELECTION:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-27 TABLE FILE LOOKUP MENU
To select a particular table, type in the option number and press . Each TABLE option will
offer the choice of BROWSE or LIST. The Browse option will list each entry in the selected table
separately. The List option will offer a choice of listing the selected table to the screen or a hard copy
listing directed to a printer. The List option will list a screen 'page' at a time.
An example of how this function works is shown in the following text and figures (Figure 4-28 through
Figure 4-32) using option 1 - ACTIONS.
April 2003
4-47
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
05/05/94
AIRS FACILITY SUBSYSTEM
TABLE FILE MAINTENANCE MENU
PGM: AFP150
MAP: AFM1502
SELECTED FILE:
KEY SELECTED FILE BY:
1 REGIONAL ACTION TYPE
2 NATIONAL ACTION TYPE
ENTER MENU SELECTION:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-28 Page 1 - ACTION OPTION of TABLE FILE LOOKUP
On this screen, you identify the type of ACTION table: Regional Action types, or National Action Types.
Figure 4-28 shows us that Regional Action Types were selected. Press after typing in the
selection.
April 2003
4-48
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
05/05/94
AIRS FACILITY SUBSYSTEM
TABLE FILE MAINTENANCE FUNCTION
PGM: AFP152
MAP: AFM1521
SELECTED FILE: ACTIONS BY REGIONAL ACTION TYPE
1 BROWSE
2 LIST
ENTER MENU SELECTION: 1
PF3=END PF4=MAIN PF5=TERM
FIGURE 4-29 Page 2 - ACTION OPTION of TABLE FILE LOOKUP
TABLE FILE LOOKUP offers choices for Browse and List.
The Browse option will display each entry in the selected table item by item.
The List option will display all values on a continuous list offering a choice of On-line display of
selections, or a hard copy listing directed to a printer.
In Figure 4-29, the Browse option is selected.
April 2003
4-49
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
05/05/94
AIRS FACILITY SUBSYSTEM
ACTION TABLE - BROWSE
PGM: AFP159
MAP: AFM1591
REGION CODE: 06
REGIONAL ACTION TYPE:
PF3=END PF4=MAIN PF5=TERM
FIGURE 4-30 Page 3 - ACTION OPTION of TABLE FILE LOOKUP
The more criteria you provide for your requested table, the more specific entries you will receive. For
example, providing a Region code will produce an Action table for that Region. In addition, providing an
Action Type will produce an Action table beginning with that Action Type. In Figure 4-30, EPA Region
06 was provided. The resulting table will be limited to only Region 06 Action types. Leaving a selection
screen blank results in displaying all data available on the table requested.
April 2003
4-50
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
81/23/87
SIRS FACILITY SUBSYSTEM
ftCTION TflBLE - BROWSE
P6H:
MflP:
flFN15982
flF«1592
REGION CODE:
BEG I OWL fiCTION TYPE:
08
fifi
( 9)1/04/14 - CBC )
DESCRIPTION:
LONG DESCRIPTION:
NfiTIONfiL:
fiCTION TYPE:
LONG DESCRIPTION:
113D fiPO
113|D) flPO COHPLRINT
7F
1130 HPO CQHPLflINT FILED
flCTION FLflG:
KEY fiCTION FLflG: A
BECOMHENDED fiCTION FLfiG: V
RESOLUTION flCTION FLfiG: X
FEOERflL PRIVflTE FLflG:
OBSOLETE flCTION TYPE FLflG:
DISABLE DflTE SCHEDULED SECURITY:
PF5=TERH PF7=PRE¥ PF8=MEXT _
FIGURE 4-31 BROWSING ACTION TABLE
Pressing the key will display the next value on the table. If the end of the table has been
reached, control will be returned to the Browse/List screen.
From either the Browse option or the List option, pressing the key will display on-line screen help
with a listing of definitions of all the flags on the action table.
If LIST had been selected in Figure 4-29, On-line display selected on the subsequent screen and, and the
same selection as seen in Figure 4-30 the results would look different. Multiple records that meet the
selection are displayed on the screen (see Figure 4-32). Pressing enter will display an additional
screen(s) until the request is fulfilled or a function (PF) key is pressed. In this action example, the
national action types indicated by an action type - N, are displayed beneath the regional action types,
where applicable.
Notice that the first entry on this screen can be seen as using Browse ( refer to Figure 4-31).
January 2007
Utilities
4-51
-------
AIRS User's Guide
AF3
AFS Data Storage
•DATE: 01/23/0?
ACTION TYPi
RiG
06
06
06
06
06
06
06
06
06
06
RiG/NAT
AA-R
7F-I)
AE-R
AP-R
AS-R
A3-R
A4-R
AS-R
A7-R
A8-R
A9-P,
PFl»HiiP
OESCRIPTION
1130 APO COMPL
ALT ENF LITTER
ARCHIVE PROCESS
ASSOC/WIRCi
VC DETECT
VC S/ ANNUAL RPT
NESNAPS RiQ INS
NESNAPS REF LEG
NESNAPS HOC LEG
NESNAPS VIO LTR
PF4«MA
ACTION TABLE LISTING PGM; AFN1S9
BY REGIONAL ACTION TYPE FLAGS 0
0 A K F AP
LONG OESCRIPTION i C i AW/ i Tl
NATIONAL OESCfilPTION S T RECMC Y RiS 0 Ei
113(0) APO COMPLAINT FliEO V A K
iWO APO COMPLAINT FILEO
STATE ALTERNATIVE
ENFORCEMENT LITTER
ARCHIVING PROCESS PERFORMED
ASSOCIATION/MERGE UTILITY
PERFORMED
VC DETECTION SyeMITTAL
VC ANNUAL
NESNAPS REQUEST FOR
INSPECTION 6Y SlA
NiSHAPS REFERRAL TO LEGAL
NESHAPS UOC TO
LEGAL
NESHAPS VIOLATION LITTER V
IN MiNy PFS»TIWINATE
FIGURE 4-32 LISTING ACTION TABLE
January 2007
Utilities
4-52
-------
AIRS User's Guide
AF3
AFS Data Storage
4.13 SIP Inventory Utility
To create, change or browse a SIP Inventory record, select option 12 on the Utility Menu. The SIP
Inventory Utility is the mechanism used to track the review status of base year and projected SIP
Inventories.
To access the SIP INVENTORY UTILITY INFORMATION UTILITY option, select option 12 on the UTILITY
MENU (Figure 4-6) and press the key. The SIP INVENTORY INFORMATION OPTION MENU is
shown in Figure 4-33.
DATE : 05/05/94
SCREEN: 034
AIRS FACILITY SUBSYSTEM - UTILITY
SIP INVENTORY INFORMATION
PGM: AFP034
MAP: AFM0341
1. UPDATE
2. BROWSE
ENTER MENU OPTION :
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-33 SIP INVENTORY SELECTION MENU
Browse lets you LOOK at existing records. Update lets you LOOK and TOUCH (that is add and change)
records.
When you select either the Update or Browse function you receive the screen shown in Figure 4-34.
April 2003
4-53
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
DATE : 05/05/94
SCREEN: 034
AIRS FACILITY SUBSYSTEM - UTILITY
SIP INVENTORY INFORMATION
PGM: AFP034
MAP: AFM0342
*BASE YEAR (YY)
*SIP PROGRAM
PROJECTED YEAR (YY)
*INVENTORY TYPE
* INVENTORY STATUS AREA
COUNTY
*STATE
PLANT
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-34 SIP INVENTORY KEY DATA SCREEN
To update, you must enter all of the key data associated with either a base SIP Inventory or projected
SIP Inventory. The key data for a Base year SIP Inventory are: a unique Base Year, SIP Program,
Inventory Type, Inventory Status Area and a State. Once you enter these key data, you will be taken to
the SIP Inventory Information Update screen.
To browse, you can enter either all of the key data for a specific inventory or enter only the State Code.
Entering only the State Code will display all existing SIP Inventory records for the state. Once you enter
these key data, you will be taken to the SIP Inventory Information Screen.
To associate a plant with a SIP inventory which is within a 25 mile radius of the SIP non-attainment area,
enter a FIPS county code and NEDS Plant ID in addition to the key data referenced above. Enter the
same keys to browse.
The key data for a projected SIP inventory are the Base Inventory keys and the Projected Year.
April 2003
4-54
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
DATE : 10/16/92
SCREEN: 134
AIRS FACILITY SUBSYSTEM - UTILITY
SIP INVENTORY INFORMATION UPDATE
PGM: AFP134
MAP: AFM1341
*BASE YEAR (YY)
*SIP PROGRAM
PROJECTED YEAR (YY)
*INVENTORY TYPE
* INVENTORY STATUS AREA
COUNTY
*STATE
PLANT
INVENTORY STATUS - AVAILABLE FOR REVIEW
REGIONAL REVIEW
HEADQUARTERS REVIEW .
COMMENT NUMBER/LEVEL:
PF3=END PF4=MAIN MENU PF5=TERMINATE
FIGURE 4-35 SIP INVENTORY DATA SCREEN
SIP Inventory data are considered "Draft", not public, until EPA Headquarters approves the inventory by
setting the Headquarter Review flag to 'Y' (approved). SIP Inventory data are defined by the keys on this
screen. After the SIP Inventory data have been added to AFS and are available for EPA review, the
Available for Review flag is set to 'Y' (yes).
SIP State or Regional Users with SIP state access adding or updating an inventory may supply a value
for the Inventory Status - Available for Review. If Available for Review, Regional Review or
Headquarters Review is set to 'Y', the SIP Inventory data defined by the geography and inventory
parameters in the SIP Inventory Information record are frozen. Frozen SIP Inventory data may not be
modified. If any of the parties rejects the Inventory, they set the review flag to 'N' (not approved), at
which time the SIP Inventory data become accessible for update (unfrozen). The review process begins
again.
Users who wish to attach a comment to their Inventory record need to provide a comment number and
a level. SIP Inventory comments are identified by the Base Year, SIP program, Inventory type, Inventory
Status Area and State. You may supply a comment value of 001 - 998. If you want AFS to generate the
next available comment number for an Inventory, the field should be filled with '999'.
Comment Numbers have an associated one position field, labelled Level, which identifies the comment
as being related to a State user'S', a Regional user 'R' or a National user 'N'.
If no existing record is found for the key specified, you will be asked to confirm an add.
Comments consist of 4 lines, each sixty characters long.
4.14 Update AFS Plant ID
April 2003
4-55
Utilities
-------
AIRS User's Guide
AF3
AFS Data Storage
The UPDATE AFS PLANT ID UTILITY allows you to change or delete an AFS Plant ID. Changing or
deleting an AFS ID is necessary to correct one that was incorrectly assigned to a plant using the ID
Selection program (Screen 000). Deleting an AFS Plant ID does not effect any other information
associated with the plant. A delete can not be performed if permit applications or operating permits
exist for the plant since this information is referenced using the AFS Plant ID.
To access the UPDATE AFS PLANT ID Utility, select option 13 on the UTILITY MENU (Figure 4-6) and
press the key. The UPDATE AFS PLANT ID screen is shown in Figure 4-36.
DATE : 05/11/94
SCREEN: 137
AIRS FACILITY SUBSYSTEM
UPDATE AFS PLANT ID
PGM: AFP137
MAP: AFM1371
PLEASE ENTER ONE CURRENT PLANT IDENTIFIER:
AFS PLANT ID (STATE/COUNTY/PLANT): /
CDS PLANT ID (STATE/COUNTY/PLANT): /
NEDS PLANT ID (STATE/COUNTY/PLANT): /
PLEASE ENTER NEW AFS PLANT IDENTIFICATION:
AFS PLANT ID (STATE/COUNTY/PLANT): /
TO DELETE AN AFS PLANT ID, LEAVE THE NEW AFS PLANT ID BLANK AND PRESS ENTER.
PF1=HELP PF3=END PF4=MAIN PF5=TERM
FIGURE 4-36 UPDATE AFS PLANT ID SCREEN
The plant to be updated must be identified by supplying either the current AFS, CDS, or NEDS Plant
Identifier. Only one current plant identifier may be supplied. The new AFS Plant ID may be specified
along with the current plant ID when performing a change. Otherwise, the screen is redisplayed with all
current plant IDs displayed when the key is pressed. Specify a new AFS Plant ID to perform
a change or leave it blank to delete the AFS Plant ID associated with the plant. For a change, the new
AFS Plant ID must be unique to the county.
Only users with update access to compliance and emissions plant data may perform this utility.
April 2003
4-56
Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
4.15 Submit Current Utility File
The SUBMIT CURRENT UTILITY FILE allows you to submit AFS Utility transactions to batch. If you are an
"automatic" user, you will not see this option (14) on the Utility Selection Menu (Figure 4-6) as your
utility batch transactions are automatically submitted to batch. If you are a "manual" user you will be
required to use this utility to submit utility batch transactions that you have requested.
For more information on this utility option, refer to section 3.4.7.
April 2003 4-57 Utilities
-------
AIRS User's Guide
AF3 AFS Data Storage
APPENDIX A
AFS BATCH TRANSACTION FORMATS
April 2003 Appendix A
-------
Rev. 02/02
AFS BATCH TRANSACTION FORMATS
AFS Batch transactions are designed in accordance with the AFS On-line
System specifications. A transaction set has been developed for each AFS record
type and each set follows the data flow pattern of the on-line update screens
where possible. Due to the record length constraints some flexibility of field
placement was used. Batch transactions are identified by a 2-digit transaction
number, that distinguishes the AFS record type, and a 1-digit sequence number
that determines the data sequence within the record. The first digit of the
transaction number identifies the transaction level (i.e., plant, point, etc.)
and the second digit determines the transaction type within the level (i.e.,
pollutant, air program, action, etc.) . The hierarchy of the AFS batch
transactions is shown below:
Level Transaction
Level Type Type
A Permit 1
2
7
8
B 9
C 1
Transaction Sequence
Name Numbers
Application
Draft Permit
Application Association
Event Tracking Action
Plant Permit Comment
Event Tracking Action
1
1
1
1
1
-5
-5
1
-8
-4
-9
Plant
Stack
0
1
2
3
4
5
6
7
Comment
General Plant Information 1-9
Plant Pollutant Information 1
Plant Air Program 1-2
Plant Pollutant Air Program 1
Fee Certification 1
Mailing Label Information 1-3
Plant Action 1-4
Plant Level Comment 1-4
Plant CMS 1
General Stack Information 1-2
Stack Pollutant Information 1
Stack Level Comment 1-4
-------
Rev. 02/02
Level Transaction
Level Type Type
3 Point 0
1
2
3
4
5
6
7
4 Segment 0
1
2
3
7
5 Contractor 0
Landfill 1
Performance 2
6 Utility 0
1
4
5
Transaction Sequence
Name Numbers
General Point Information
Point Pollutant Information
Point Air Program
Point Monitor Information
Continuous Emission
Point Tank Information
Point Action
Point Level Comment
General Segment Information
Segment Pollutant
Information
Segment Chemical
Segment Projected Pollutant
Segment Level Comment
Asbestos Contractor
Information
Asbestos Landfill
Information
Asbestos Performance
Information
Merge Plant
Archive Plant
Source/Point Swap
Merge Point
1
1
1
1
1
1
1
1
1
1
1
1
1
-4
-3
1
-2
-3
1
-4
-4
-5
-3
1
-3
-4
-4
-3
-9
1
1
1
1
Separate batch transaction formats have been developed for AFS users who
access Compliance only or Emissions only data. These formats were created in
order to avoid the confusion that may exist if either a Compliance only or
Emissions only user is confronted with a set of transactions containing data
fields irrelevant for their specific use. Emissions and Compliance plant ID'S
are entered in the same field on the batch formats. Users entering emissions
plant ID'S should enter the ID beginning in the first column (6) and leave the
last column (10) blank.
-------
Rev. 11/08
AFS GENERAL PLANT INFORMATION
TRANSACTION TYPE 10
Columns Field
1
2
3
4
5
6
7
8
9
10
5
6
7
8
9
5
6
7
8
9
9a
9b
9c
10
11
12
13
14
15
16
5
6
7
8
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Plant Name
Associated Plant Id
AFS Plant ID
Update Code
Sequence Number
Emissions Inventory
Year of Record
Plant Street Address
City Code
Update Code
Sequence Number
Emissions Inventory
Year of Record
Plant City Name
Plant Zip Code
Standard Industrial
Classification
Primary Industrial Code
Secondary Industrial Code
Tertiary Industrial Code
Local Control Region
Regional Planning Agency
Inspector
Air Toxics Initiative
Source Monitoring Info.
State Private Indicator
Update Code
Sequence Number
Governmental Facility Code
Priority Code
State Registration Number
From
1
3
6
11
13
14
16
56
61
80
13
14
16
46
80
13
14
16
46
55
59
63
67
69
71
74
75
79
80
13
14
15
16
Thru Length
2
5
10
12
13
15
55
60
75
80
13
15
45
50
80
13
15
45
54
58
62
66
68
70
73
74
75
79
80
13
14
15
30
2
3
5
2
1
2
40
5
15
1
1
2
30
5
1
1
2
30
9
4
4
4
2
2
3
1
1
1
1
1
1
1
15
Remarks
Key
Key
Key
Key, Always 10
Key, Always 1
Key for Emissions
Key, Always A, C, or D
Key, Always 2
Key for Emissions
Key, Always A, C, or D
Key, Always 3
Key for Emissions
Key, Always A, C, or D
Key, Always 4
-------
Rev. 12/02
AFS GENERAL PLANT INFORMATION
TRANSACTION TYPE 10
(Continued)
Columns Field
Name of Field From
9
10
11
12
5
6
7
8
9
5
6
7
8
9
10
11
12
13
14
16
Facility Capacity
Facility Capacity Units
NAICS (North American
Industry Classification
System) Code
Update Code
Sequence Number
Contact Person-Compliance
Telephone Number
Plant Description
Update Code
Sequence Number
Emissions Inventory
Year of Record
Emissions Year of Increment
UTM Zone
UTM Horizontal Coord (km)
UTM Vertical Coord (km)
Latitude (DDMMSS)
Longitude (DDDMMSS)
Contact Person-Emissions
Telephone Number
Update Code
35
42
57
80
13
14
34
44
80
13
14
16
18
20
24
29
35
42
62
80
Thru Length Remarks
41
56
62
80
13
33
43
68
80
13
15
17
19
23
28
34
41
61
71
80
7
15
6
1 Key, Always A, C, or D
1 Key, Always 5
20
10
25
1 Key, Always A, C, or D
1 Key, Always 6
2 Key
2
2
4 1 Decimal Position
Assumed
5 1 Decimal Position
Assumed
6
7
20
10
1 Key, Always A, C, or D
-------
Rev. 7/97
AFS GENERAL PLANT INFORMATION
TRANSACTION TYPE 10
(Continued)
Columns Field
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
12
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Number of Employees
User Plant ID
Property Area (Acres)
Emergency Control Plan
Principal Product
SDE 1
Update Code
Sequence Number
Emissions Inventory
Year of Record
SDE 9
MACT Category
Sub Category
Section 112 Indicator
Date Determination
Completed
Update Code
From
13
14
16
21
33
39
40
65
80
13
14
16
46
50
54
55
80
Thru Length Remarks
13
15
20
32
38
39
64
67
80
13
15
45
49
53
54
62
80
1 Key, Always 7
2 Key
5
12
6 1 Decimal Position
Assumed
1
25
3
1 Key, Always A, C, or D
1 Key, Always 8
2 Key
30
4
4
1
8
1 Key, Always A, C, or D
Sequence Number
Emissions Inventory
Year of Record
SIP Program
Status Area
SIP Program
Status Area
SIP Program
Status Area
SIP Program
Status Area
SIP Program
Status Area
Update Code
13 13
14
16
21
26
31
36
41
46
51
56
61
80
15
20
25
30
35
40
45
50
55
60
65
80
Key, Always
Key
Key, Always A, C or D
-------
Rev. 7/97
AFS PLANT POLLUTANT INFORMATION
TRANSACTION TYPE 11
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Pollutant Code/Chemical
Abstract Number
Emissions Type Indicator
Emissions Value
Decimal Position
Units Code
Method Code
State Private Indicator
Update Code
From
1
3
6
11
13
14
23
27
34
35
37
79
80
Thru
2
5
10
12
13
22
26
33
34
36
37
79
80
Field
Length
2
3
5
2
1
9
4
7
1
2
1
1
1
Remarks
Key
Key
Key
Key, Always 11
Key, Always 1
Key
Key*
Key, Always A, C, or D
*Emissions Type Indicators:
ALLW - Allowable
POTC - Potential Controlled
POTU - Potential Uncontrolled
ACTU - Actual Uncontrolled
-------
AFS PLANT AIR PROGRAM
TRANSACTION TYPE 12
Rev. 7/97
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Air Program Code
Air Program Status
State Implementation Plan
RDE 1
RDE 2
RDE 3
RDE 4
RDE 5
RDE 6
RDE 7
RDE 9
RDE 10
RDE 11
RDE 12
RDE 15
Staff Code
Reporting Requirements
to Region
Odd Year of Inspection
Frequency
Odd Inspection Strategy
Odd Inspection Frequency
Even Year of Inspection
Frequency
Even Inspection Strategy
Even Inspection Frequency
Update Code
From
1
3
6
11
13
14
15
16
20
21
22
23
28
33
43
44
51
53
55
56
57
60
61
63
64
66
68
69
80
Thru Length Remarks
2
5
10
12
13
14
15
16
20
21
22
27
32
42
43
50
52
54
55
56
59
60
62
63
65
67
68
70
80
2 Key
3 Key
5 Key
2 Key, Always 12
1 Key, Always 1
1 Key
1
1
1
1
1
5
5
10
1
7
2
2
1
1
3
1
2
1
2
2
1
2
1 Key, Always A, C, or D
-------
AFS PLANT AIR PROGRAM
TRANSACTION TYPE 12
Rev. 02/2006
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Air Program Code
Subparts update indicator
Subparts 1
Subparts 2
Subparts 3
Subparts 4
Subparts 5
Subparts 6
Subparts 7
Subparts 8
Subparts 9
Subparts 10
Subparts 11
Subparts 12
Update Code
From
1
3
6
11
13
14
15
16
21
26
31
36
41
46
51
56
61
66
71
80
Thru
2
5
10
12
13
14
15
20
25
30
35
40
45
50
55
60
65
70
75
80
Field
Length
2
3
5
2
1
1
1
5
5
5
5
5
5
5
5
5
5
5
5
1
Remarks
Key
Key
Key
Key, Always 12
Key, Always 2
Key
Key, Always A, C, or D
-------
Rev. 7/97
AFS PLANT POLLUTANT AIR PROGRAM
TRANSACTION TYPE 13
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Air Program Code
Pollutant Code/Chemical
Abstract Number
State Pollutant
Compliance Status
State Pollutant
Classification
State Attainment/
Non- Attainment
EPA Pollutant
Compliance Status
EPA Pollutant
Classification
EPA Attainment/
Non -Attainment
Loading Derivation Code
RDE 14
Toxicity Level
State Regulation Number
Update Code
From
1
3
6
11
13
14
15
24
25
27
28
29
31
32
33
34
35
80
Thru Length
2
5
10
12
13
14
23
24
26
27
28
30
31
32
33
34
49
80
2
3
5
2
1
1
9
1
2
1
1
2
1
1
1
1
15
1
Remarks
Key
Key
Key
Key, Always 13
Key, Always 1
Key
Key
Key, Always A, C, or D
-------
Rev. 7/97
AFS FEE CERTIFICATION
TRANSACTION TYPE 14
Columns
1
2
3
4
5
6
7
8
8a
8b
9
10
11
12
13
14
15
16
17
18
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Fee Status
Fee Status Change Date
Fee Classification
Classification Reason-1
Classification Reason-2
Fee Billing Amount
Fee Billing Date
Fee Penalty Amount
Fee Penalty Date
Fee Received Date
Fee Payment Check Number
Fee Voucher Number
Fee Certification
(Inspection) Date
State Private Indicator
Update Code
From
1
3
6
11
13
14
15
21
22
23
24
30
36
42
48
54
63
68
79
80
Thru
2
5
10
12
13
14
20
21
22
23
29
35
41
47
53
62
67
73
79
80
Field
Length
2
3
5
2
1
1
6
1
1
1
6
6
6
6
6
9
5
6
1
1
Remarks
Key
Key
Key
Key, Always 14
Key, Always 1
2 Decimal Positions
Assumed
2 Decimal Positions
Assumed
Key, Always A, C, or D
10
-------
Rev. 7/97
AFS MAILING LABEL INFORMATION
TRANSACTION TYPE 15
Name of Field
1 State Code
2 County Code
3 Plant ID
4 Transaction Type
5 Sequence Number
6 Emissions Inventory
Year of Record
7 Mailing Plant Name
8 Update Code
Columns Field
From Thru Length Remarks
122 Key
353 Key
6 10 5 Key
11 12 2 Key, Always 15
13 13 1 Key, Always 1
14 15 2 Key for Emissions
16 55 40
80 80 1 Key, Always A, C, or D
9
10
Sequence Number 13
Emissions Inventory
Year of Record 14
Mailing Street Address 16
Mailing City Name 46
Mailing State Abbreviation 76
Update Code 80
13 1 Key, Always 2
15 2 Key for Emissions
45 30
75 30
77 2
80 1 Key, Always A, C, or D
5 Sequence Number
6 Emissions Inventory
Year of Record
7 Mailing Zip Code
8 Mailing Label Code
9 Update Code
13
14
16
25
80
13
15
24
26
80
1 Key, Always 3
2 Key for Emissions
9
2
1 Key, Always A, C, or D
11
-------
Rev. 7/97
AFS PLANT ACTION
TRANSACTION TYPE 16
Columns Field
1
2
3
4
5
6
7
7a
7b
7c
7d
7e
7f
8
9
10
11
12
13
14
15
16
17
18
19
5
6
7
8
9
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Action Number
Air Program Codes
1
2
3
4
5
6
Action Type
Action Type Category
Action Description
Date Scheduled
Date Achieved
Results Code
Penalty Amount
Staff Code
RDE 8
Pollutant Code/Chemical
Abstract Number
State Private Indicator
Update Code
Sequence Number
Action Number
Contractor State
Contractor ID
Update Code
From
1
3
6
11
13
14
17
18
19
20
21
22
23
25
26
41
47
53
55
62
65
67
79
80
13
14
17
19
80
Thru Length
2
5
10
12
13
16
17
18
19
20
21
22
24
25
40
46
52
54
61
64
66
75
79
80
13
16
18
30
80
2
3
5
2
1
3
1
1
1
1
1
1
2
1
15
6
6
2
7
3
2
9
1
1
1
3
2
12
1
Remarks
Key
Key
Key
Key, Always 16
Key, Always 1
Key
Key, Always A, C, or D
Key, Always 2
Key
Key, Always A, C, or D
12
-------
Rev. 2/01
AFS PLANT ACTION
TRANSACTION TYPE 16
(Continued)
Columns
5
6
7
8
9
10
11
12
5
6
7
8
8a
8b
8c
8d
8e
8f
8g
9
Name of Field
Sequence Number
Action Number
Key Action Number
Lead Agency
Violation Identifier
Document Number
Violating Pollutants
Update Code
Sequence Number
Action Number
RDE 16
Violation Type Codes
1
2
3
4
5
6
7
Update Code
From
13
14
17
20
21
29
43
80
13
14
17
42
45
48
51
54
57
60
80
Thru
13
16
19
20
21
42
57
80
13
16
41
44
47
50
53
56
59
62
80
Field
Length
1
3
3
1
1
14
15
1
1
3
25
3
3
3
3
3
3
3
1
Remarks
Key, Always 3
Key
Key
Key, Always A, C, or D
Key, Always 4
Key
Key, Always A, C, or D
13
-------
Rev. 7/97
AFS PLANT LEVEL COMMENT
TRANSACTION TYPE 17
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
5
6
7
8
9
10
11
5
6
7
8
9
10
11
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Action Number
Comment Number
Comment Identifier
Comment
Enfrcmnt Sensitive Indie.
State Private Indicator
Update Code
Sequence Number
Emissions Inventory
Year of Record
Action Number
Comment Number
Comment Identifier
Comment
Update Code
Sequence Number
Emissions Inventory
Year of Record
Action Number
Comment Number
Comment Identifier
Comment
Update Code
Sequence Number
Emissions Inventory
Year of Record
Action Number
Comment Number
Comment Identifier
Comment
Update Code
From
1
3
6
11
13
14
16
19
22
23
78
79
80
13
14
16
19
22
23
80
13
14
16
19
22
23
80
13
14
16
19
22
23
80
Thru Length
2
5
10
12
13
15
18
21
22
77
78
79
80
13
15
18
21
22
79
80
13
15
18
21
22
79
80
13
15
18
21
22
79
80
2
3
5
2
1
2
3
3
1
55
1
1
1
1
2
3
3
1
57
1
1
2
3
3
1
57
1
1
2
3
3
1
57
1
Remarks
Key
Key
Key
Key,
Key,
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key
Key,
Key,
Always
Always
17
1
for Emissions
Always
Always
Always
C or E
A, C, or
2
D
for Emissions
Always
Always
Always
C or E
A, C, or
3
D
for Emissions
Always
Always
Always
C or E
A, C, or
4
D
for Emissions
Always
Always
C or E
A, C, or
D
14
-------
Rev. 11/01
AFS PLANT COMPLIANCE MONITORING STRATEGY (CMS)
TRANSACTION TYPE 18
Name of Field
1 State Code
2 County Code
3 Plant ID
4 Transaction Type
5 Sequence Number
6 Source Category
7 Min Frequency Indicator
8 Fiscal Year of FCE - Yr A
9 On Site Visit Ind -
10 Fiscal Year of FCE
11 On Site Visit Ind -
12 Fiscal Year of FCE
13 On Site Visit Ind -
14 Fiscal Year of FCE
15 On Site Visit Ind -
16 Fiscal Year of FCE - Yr
17 On Site Visit Ind -
18 Comment
19 Update Code
Columns
From Thru
Field
Length Remarks
1
3
6
11
13
14
ator 15
- Yr A 16
A 20
- Yr B 21
B 25
- Yr C 26
C 30
- Yr D 31
D 35
- Yr E 36
E 40
41
80
2
5
10
12
13
14
15
19
20
24
25
29
30
34
35
39
40
79
80
2
3
5
2
1
1
1
4
1
4
1
4
1
4
1
4
1
39
1
Key
Key
Key
Key, Always 18
Key, Always 1
Key, Always A or C
15
-------
Rev. 7/97
AFS GENERAL STACK INFORMATION
TRANSACTION TYPE 20
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Stack Height (ft)
Stack Diameter (ft)
Exit Gas Temperature (• F)
Gas Flow Rate (ACFM)
Exit Gas Velocity (ft/sec)
Emission Recorder
Plume Height (ft)
Stack Lining
Stack Type Code
Rough Terrain Indicator
Stack Description
Update Code
From
1
3
6
11
13
14
16
19
23
27
31
38
42
43
47
48
49
50
80
Thru
2
5
10
12
13
15
18
22
26
30
37
41
42
46
47
48
49
74
80
Field
Length
2
3
5
2
1
2
3
4
4
4
7
4
1
4
1
1
1
25
1
Remarks
Key
Key
Key
Key, Always 20
Key, Always 1
Key
Key
2 Decimal Positions
Assumed
1 Decimal Position
Assumed
Key, Always A, C, or D
10
11
12
13
14
15
16
Sequence Number 13 13
Emissions Inventory
Year of Record 14 15
Stack Number 16 18
UTM Horizontal Coord (km) 19 23
UTM Vertical Coord (km) 24 29
Latitude (DDMMSS) 30 35
Longitude (DDDMMSS) 36 42
G.E.P. Stack Height (ft) 43 46
G.E.P. Building Height (ft)47 50
G.E.P. Building Length (ft)51 54
Building Width (ft) 55 58
80
1 Key, Always 2
G.E.P.
Update Code
80
Key
Key
2 Decimal Positions
Assumed
2 Decimal Positions
Assumed
Key, Always A, C, or D
16
-------
Rev. 7/97
AFS STACK POLLUTANT INFORMATION
TRANSACTION TYPE 21
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Pollutant Code/Chemical
Abstract Number
Emissions Type Indicator
Emissions Value
Decimal Position
Units Code
Method Code
State Private Indicator
Update Code
From
1
3
6
11
13
14
16
19
28
32
39
40
42
79
80
Thru
2
5
10
12
13
15
18
27
31
38
39
41
42
79
80
Field
Length
2
3
5
2
1
2
3
9
4
7
1
2
1
1
1
Remarks
Key
Key
Key
Key, Always 21
Key, Always 1
Key for Emissions
Key
Key
Key*
Key, Always A, C, or D
*Emissions Type Indicators:
MEAS - Measured
ALLW - Allowable
POTC - Potential Controlled
POTU - Potential Uncontrolled
ACTU - Actual Uncontrolled
17
-------
Rev. 7/97
AFS STACK LEVEL COMMENT
TRANSACTION TYPE 27
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
5
6
7
8
9
10
11
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Comment Number
Comment Identifier
Comment
Enfrcmnt Sensitive Indie.
State Private Indicator
Update Code
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Comment Number
Comment Identifier
Comment
Update Code
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Comment Number
Comment Identifier
Comment
Update Code
From
1
3
6
11
13
14
16
19
22
23
78
79
80
13
14
16
19
22
23
80
13
14
16
19
22
23
80
Thru Length
2
5
10
12
13
15
18
21
22
77
78
79
80
13
15
18
21
22
79
80
13
15
18
21
22
79
80
2
3
5
2
1
2
3
3
1
55
1
1
1
1
2
3
3
1
57
1
1
2
3
3
1
57
1
Remarks
Key
Key
Key
Key,
Key,
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key
Key,
Key,
Always
Always
27
1
for Emissions
Always
Always
Always
C or E
A, C, or D
2
for Emissions
Always
Always
Always
C or E
A, C, or D
3
for Emissions
Always
Always
C or E
A, C, or D
18
-------
Rev. 7/97
AFS STACK LEVEL COMMENT
TRANSACTION TYPE 27
(Continued)
7
8
9
10
11
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Stack Number
Comment Number
Comment Identifier
Comment
Update Code
Columns
From Thru
13
14
16
19
22
23
80
13
15
18
21
22
79
80
Field
Length Remarks
1 Key, Always 4
2
3
3
1
57
1
Key for Emissions
Key
Key
Key, Always C or E
Key, Always A, C, or D
19
-------
Rev. 7/97
AFS GENERAL POINT INFORMATION
TRANSACTION TYPE 30
Columns
1
2
3
4
5
6
7
8
9
10
11
5
6
7
8
8a
8b
8c
9
10
11
12
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point ID
Compliance /Emissions
Indicator
Point Description
Operating Restriction
Regulated Source
Classification Code
Update Code
Sequence Number
Point ID
C/E Indicator
Soot Blowing Indicator
Times Per Day
Times Per Week
AM or PM
Design Capacity
Design Capacity Units
State Sensitive Indicator
Update Code
From
1
3
6
11
13
14
17
18
43
68
80
13
14
17
18
19
21
23
24
29
30
80
Thru
2
5
10
12
13
16
17
42
67
75
80
13
16
17
18
20
22
23
28
29
30
80
Field
Length
2
3
5
2
1
3
1
25
25
8
1
1
3
1
1
2
2
1
5
1
1
1
Remarks
Key
Key
Key
Key, Always 30
Key, Always 1
Key
Key, Always C or M
Key, Always A, C, or D
Key, Always 2
Key
Key, Always C or M
Applies only if C/E
Indicator = C
Applies only if C/E
Indicator = C
Key, Always A, C, or D
20
-------
Rev. 7/97
AFS GENERAL POINT INFORMATION -
TRANSACTION TYPE 30
(Continued)
EMISSIONS
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
13a
13b
13c
13d
14
14a
14b
14c
15
16
17
18
19
20
21
22
23
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
State Sensitive Indicator
Space-Heat (Percent)
Design Capacity
Design Capacity Units
Percentage Annual Thruput
December - February
March - May
June - August
September - November
Normal Operating Schedule
Hours Per Day
Days Per Week
Hours Per Year
Control Regulation
User Point ID
Burner Type - Make
Burner Type - Model
Installation Date
Draft Type
Draft Control Type
Draft Control Location
Update Code
From
1
3
6
11
13
14
16
19
20
21
24
29
30
32
34
36
38
40
41
45
57
60
70
71
77
78
79
80
Thru Length
2
5
10
12
13
15
18
19
20
23
28
29
31
33
35
37
39
40
44
56
59
69
70
76
77
78
79
80
2
3
5
2
1
2
3
1
1
3
5
1
2
2
2
2
2
1
4
12
3
10
1
6
1
1
1
1
Remarks
Key
Key
Key
Key, Always 30
Key, Always 3
Key
Key
Key, Always E or M
1 Decimal Position
Assumed
Key, Always A, C, or D
21
-------
Rev. 7/97
AFS GENERAL POINT INFORMATION -
TRANSACTION TYPE 30
(Continued)
EMISSIONS
Name of Field
5 Sequence Number
6 Emissions Inventory
Year of Record
7 Point ID
8 Compliance/Emissions
Indicator
9 SDE 2
10 SDE 3
11 SDE 4
12 SDE 5
13 Point Description
14 Operation Start Time
15 Operation End Time
16 Update Code
Columns
From Thru
13
14
16
19
20
21
23
27
33
58
62
80
13
15
18
19
20
22
26
32
57
61
65
80
Field
Length Remarks
1 Key, Always 4
2
3
1
1
2
4
6
25
4
4
1
Key
Key
Key, Always E or M
Key, Always A, C or D
22
-------
Rev. 7/97
AFS POINT POLLUTANT INFORMATION
TRANSACTION TYPE 31
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
5
6
7
8
9
10
11
12
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Pollutant Code/Chemical
Abstract Number
Emissions Type Indicator
Emissions Value
Decimal Position
Units Code
Method Code
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Pollutant Code/Chemical
Abstract Number
State Regulation Number
State Private Indicator
Update Code
From
1
3
6
11
13
14
16
19
20
29
33
40
41
43
80
13
14
16
19
20
29
44
80
Thru
2
5
10
12
13
15
18
19
28
32
39
40
42
43
80
13
15
18
19
28
43
44
80
Field
Length
2
3
5
2
1
2
3
1
9
4
7
1
2
1
1
1
2
3
1
9
15
1
1
Remarks
Key
Key
Key
Key,
Key,
Key
Key
Key,
Key
Key*
Key,
Key,
Key
Key
Key,
Key
Key,
Always 31
Always 1
for Emissions
Always C, E,
Always A, C,
Always 2
for Emissions
Always C, E,
Always A, C,
or M
or D
or M
or D
23
-------
Rev. 7/97
AFS GENERAL POINT INFORMATION -
TRANSACTION TYPE 31
(Continued)
EMISSIONS
Name of Field
Columns
From Thru
Field
Length Remarks
5
6
7
8
9
10
11
12
13
14
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Pollutant Code/Chemical
Abstract Number
Emissions Limitation
Description
SIP Rule in Place
Year Regulated
Year Last Modified
Update Code
13
14
16
19
20
29
59
60
62
80
13
15
18
19
28
58
59
61
63
80
1
2
3
1
9
30
1
2
2
1
Key,
Key
Key
Key,
Key
Key,
Always 3
for Emissions
Always C, E,
Always A, C,
or M
or D
*Emission Type Indicators:
MEAS - Measured
SDEF - State Defined
POTC - Potential Controlled
POTU - Potential Uncontrolled
ACTU - Actual Uncontrolled
ALLW - Allowable
LIME - Emission Limitation
24
-------
Rev. 7/97
AFS POINT AIR PROGRAM
TRANSACTION TYPE 32
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point ID
Compliance /Emissions
Indicator
Air Program Code
State Compliance Status
EPA Compliance Status
Air Program Status
State Implementation
Plan
RDE 7
RDE 15
Pollutant Code/Chemical
Abstract Number
Subparts Update Indicator
Subparts 1
Subparts 2
Subparts 3
Subparts 4
Subparts 5
Subparts 6
Subparts 7
Subparts 8
Subparts 9
Update Code
From
1
3
6
11
13
14
17
18
19
20
21
22
23
24
25
34
35
40
45
50
55
60
65
70
75
80
Thru Length
2
5
10
12
13
16
17
18
19
20
21
22
23
24
33
34
39
44
49
54
59
64
69
74
79
80
2
3
5
2
1
3
1
1
1
1
1
1
1
1
9
1
5
5
5
5
5
5
5
5
5
1
Remarks
Key
Key
Key
Key, Always 32
Key, Always 1
Key
Key, Always C or M
Key
Key, Always A, C, or D
25
-------
Rev. 7/97
AFS POINT MONITOR INFORMATION
TRANSACTION TYPE 33
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
5
6
7
8
9
10
11
12
13
14
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point ID
Compliance /Emissions
Indicator
Channel Number
Monitor Manufacturer
Monitor Model Number
Monitor Serial Number
Monitor Requirement Code
CEM Enforcement Agency
Update Code
Sequence Number
Point ID
Compliance /Emission
Indicator
Channel Number
Permissible Emission Limit
Monitor Installation Date
Performance Specification
Test Date
Performance Specification
Test Status
Monitor Certification
Date
Update Code
From
1
3
6
11
13
14
17
18
21
41
56
71
72
80
13
14
17
18
21
41
45
49
53
80
Thru Length
2
5
10
12
13
16
17
20
40
55
70
71
72
80
13
16
17
20
40
44
48
52
58
80
2
3
5
2
1
3
1
3
20
15
15
1
1
1
1
3
1
3
20
4
4
4
6
1
Remarks
Key
Key
Key
Key, Always 33
Key, Always 1
Key
Key, Always C or M
Key
Key, Always A, C, or D
Key, Always 2
Key
Key, Always C or M
Key
Key, Always A, C, or D
26
-------
Rev. 7/97
AFS CONTINUOUS EMISSION
TRANSACTION TYPE 34
Columns
1
2
3
4
5
6
7
8
9
10
11
lla
lib
lie
lid
lie
llf
12
13
14
15
16
17
18
19
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point ID
Compliance /Emissions
Indicator
Channel Number
Report Quarter
Chemical Abstract Number
Air Program Codes
1
2
3
4
5
6
Total Source Operating
Time
Time Period Code
Star tup/ Shut down
Cleaning/Soot Blowing
Unknown Excess Emissions
Control Equipment Failure
Control Equipment
Malfunction Unacceptable
Update Code
From
1
3
6
11
13
14
17
18
21
25
34
35
36
37
38
39
40
46
47
53
59
65
71
80
Thru
2
5
10
12
13
16
17
20
24
33
34
35
36
37
38
39
45
46
52
58
64
70
76
80
Field
Length
2
3
5
2
1
3
1
3
4
9
1
1
1
1
1
1
6
1
6
6
6
6
6
1
Remarks
Key
Key
Key
Key, Always 34
Key, Always 1
Key
Key, Always C or M
Key
Key
Key, Always A, C, or D
27
-------
Rev. 7/97
AFS CONTINUOUS EMISSION
TRANSACTION TYPE 34
(Continued)
Columns Field
5
6
7
8
9
10
11
12
13
14
15
16
17
18
5
6
7
8
9
10
11
12
13
Name of Field
Sequence Number
Point ID
Compliance /Emissions
Indicator
Channel Number
Report Quarter
Process Problems
Process Problems
Unacceptable
Number of Incidents
Of Excess Emissions
Fuel Problems
Other Known Excess
Emissions
Monitor Equipment
Malfunctions
Non-Monitor Equipment
Malfunctions
Calibration (QA)
Update Code
Sequence Number
Point ID
Compliance /Emissions
Indicator
Channel Number
Report Quarter
Unknown Monitor Downtime
Other Known Monitor
Downtime
Number of Incidents
of Monitor Downtime
Update Code
From
13
14
17
18
21
25
31
37
40
46
52
58
64
80
13
14
17
18
21
25
31
37
80
Thru Length
13
16
17
20
24
30
36
39
45
51
57
63
69
80
13
16
17
20
24
30
36
39
80
1
3
1
3
4
6
6
3
6
6
6
6
6
1
1
3
1
3
4
6
6
3
1
Remarks
Key, Always 2
Key
Key, Always C or M
Key
Key, Always A, C, or D
Key, Always 3
Key
Key, Always C or M
Key
Key
Key, Always A, C, or D
28
-------
Rev. 7/97
AFS POINT TANK INFORMATION
TRANSACTION TYPE 35
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
14a
14b
14c
14d
14e
15
15a
15b
15c
15d
15e
15f
16
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Diameter (ft)
Height (ft)
Age
Loading Type
Color
Fixed Roof Tanks
Roof Paint Color
Shell Paint Color
Average Vapor Space
Height (ft)
Paint Condition
Diurnal Temperature
Change (• F)
Floating Roof Tanks
Construction Type
Tank Shell Condition
Deck Construction Type
Seal Type
Average Wind Speed (mph)
Support Type
Update Code
From
1
3
6
11
13
14
16
19
20
23
26
28
43
44
45
46
48
49
51
52
53
54
55
59
80
Thru Length Remarks
2
5
10
12
13
15
18
19
22
25
27
42
43
44
45
47
48
50
51
52
53
54
58
59
80
2 Key
3 Key
5 Key
2 Key, Always 35
1 Key, Always 1
2 Key
3 Key
1 Key, Always E or M
3
3
2
15
1
1
1
2
1
2
1
1
1
1
4 2 Decimal Positions
Assumed
1
1 Key, Always A, C, or D
29
-------
Rev. 7/97
AFS POINT ACTION
TRANSACTION TYPE 36
Columns Field
1
2
3
4
5
6
7
8
9
9a
9b
9c
9d
9e
9f
10
11
12
13
14
15
16
17
18
19
20
5
6
7
8
9
10
11
12
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point ID
Compliance /Emissions
Indicator
Action Number
Air Program Codes
1
2
3
4
5
6
Action Type
Action Type Category
Action Description
Date Scheduled
Date Achieved
Results Code
Penalty Amount
Staff Code
Pollutant Code/Chemical
Abstract Number
State Private Indicator
Update Code
Sequence Number
Point ID
Compliance /Emissions
Indicator
Action Number
RDE 8
Contractor State
Contractor ID
Update Code
From
1
3
6
11
13
14
17
18
21
22
23
24
25
26
27
29
30
45
51
57
59
66
69
79
80
13
14
17
18
21
23
25
80
Thru Length
2
5
10
12
13
16
17
20
21
22
23
24
25
26
28
29
44
50
56
58
65
68
77
79
80
13
16
17
20
22
24
36
80
2
3
5
2
1
3
1
3
1
1
1
1
1
1
2
1
15
6
6
2
7
3
9
1
1
1
3
1
3
2
2
12
1
Remarks
Key
Key
Key
Key, Always 36
Key, Always 1
Key
Key, Always C or M
Key
Key, Always A, C, or D
Key, Always 2
Key
Key, Always C or M
Key
Key, Always A, C, or D
30
-------
Rev. 2/01
AFS POINT ACTION
TRANSACTION TYPE 36
(Continued)
Columns
5
6
7
8
9
10
11
12
13
14
5
6
7
8
9
10
lOa
lOb
lOc
lOd
lOe
lOf
lOg
11
Name of Field
Sequence Number
Point Number
Compliance /Emissions
Indicator
Action Number
Key Action Number
Lead Agency
Violation Identifier
Document Number
Violating Pollutants
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Action Number
RDE 16
Violation Type Codes
1
2
3
4
5
6
7
Update Code
From
13
14
17
18
21
24
25
33
47
80
13
14
17
18
21
46
49
52
55
58
61
64
80
Thru
13
16
17
20
23
24
25
46
61
80
13
16
17
20
45
48
51
54
57
60
63
66
80
Field
Length
1
3
1
3
3
1
1
14
15
1
1
3
1
3
25
3
3
3
3
3
3
3
1
Remarks
Key, Always 3
Key
Key, Always C or M
Key
Key
Key, Always A, C, or D
Key, Always 4
Key
Key, Always C or M
Key
Key, Always A, C, or D
31
-------
Rev. 7/97
AFS POINT LEVEL COMMENT
TRANSACTION TYPE 37
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
5
6
7
8
9
10
11
12
13
14
15
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Action Number
Channel Number
Report Quarter
Comment Number
Comment Identifier
Comment
Enfrcmnt Sensitive Indie.
State Private Indicator
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Action Number
Channel Number
Report Quarter
Comment Number
Comment Identifier
Comment
Update Code
From
1
3
6
11
13
14
16
19
20
23
26
30
33
34
78
79
80
13
14
16
19
20
23
26
30
33
34
80
Thru Length
2
5
10
12
13
15
18
19
22
25
29
32
33
77
78
79
80
13
15
18
19
22
25
29
32
33
79
80
2
3
5
2
1
2
3
1
3
3
4
3
1
44
1
1
1
1
2
3
1
3
3
4
3
1
46
1
Remarks
Key
Key
Key
Key,
Key,
Key
Key
Key,
Key
Key
Key
Key
Key,
Key,
Key,
Key
Key
Key,
Key
Key
Key
Key
Key,
Key,
Always 37
Always 1
for Emissions
Always C, E, or
Always C or E
Always A, C, or
Always 2
for Emissions
Always C, E, or
Always C or E
Always A, C, or
M
D
M
D
32
-------
AFS POINT LEVEL COMMENT
TRANSACTION TYPE 37
(Continued)
Rev. 7/97
9
10
11
12
13
14
15
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance/Emissions
Indicator
Action Number
Channel Number
Report Quarter
Comment Number
Comment Identifier
Comment
Update Code
Columns
From Thru
13
14
16
19
20
23
26
30
33
34
80
13
15
18
19
22
25
29
32
33
79
80
Field
Length
2
3
1
3
3
4
3
1
46
1
Remarks
Key, Always 3
Key for Emissions
Key
Key, Always C, E, or M
Key
Key
Key
Key
Key, Always C or E
Key, Always A, C, or D
5 Sequence Number
6 Emissions Inventory
Year of Record
7 Point ID
8 Compliance/Emissions
Indicator
9 Action Number
10 Channel Number
11 Report Quarter
12 Comment Number
13 Comment Identifier
14 Comment
15 Update Code
13
13
14
16
19
20
23
26
30
33
34
80
15
18
19
22
25
29
32
33
79
80
2
3
1
3
3
4
3
1
46
1
1 Key, Always 4
Key for Emissions
Key
Key, Always C, E, or M
Key
Key
Key
Key
Key, Always C or E
Key, Always A, C, or D
33
-------
Rev. 7/97
AFS GENERAL SEGMENT INFORMATION
TRANSACTION TYPE 40
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment ID
Stack ID
Source Classification Code
State Sensitive Indicator
Segment Description
Annual Fuel Process Rate
Maximum Operation Rate
- Per Hour
Pollution Prevention
Indicator
Update Code
From
1
3
6
11
13
14
16
19
20
22
25
33
34
59
66
73
80
Thru
2
5
10
12
13
15
18
19
21
24
32
33
58
65
72
73
80
Field
Length
2
3
5
2
1
2
3
1
2
3
8
1
25
7
7
1
1
Remarks
Key
Key
Key
Key, Always 40
Key, Always 1
Key
Key
Key, Always E or M
Key
3 Decimal Positions
Assumed
Key, Always A, C, or D
9
10
lOa
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance/Emissions
Indicator
Segment ID
Fuel Data
Sulfur Content (%)
13
13
1 Key, Always 2
lOb Ash Content (%)
lOc Ash/Sulfur Source
lOd Ash/Sulfur Origin
lOe Heat Content (MMBTU)
11 Update Code
14
16
19
20
22
27
31
32
39
15
18
19
21
26
30
31
38
45
Key
Key
1 Key, Always E or M
2 Key
3 Decimal Positions
Assumed
2 Decimal Positions
Assumed
80
80
5
4
1
7
7 2 Decimal Positions
Assumed
1 Key, Always A, C, or D
34
-------
Rev. 7/97
AFS GENERAL SEGMENT INFORMATION
TRANSACTION TYPE 40
(Continued)
9
10
11
lla
lib
12
13
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance/Emissions
Indicator
Segment ID
Fuel/Material Supplier
Tank Data
Vapor Pressure (PSIA)
Columns
From Thru
13
14
16
19
20
22
62
Vapor Mole. Wt.(lb/lb mole) 68
Peak Ozone Season Vapor 71
Pressure
Update Code 80
13
15
18
19
21
61
67
70
76
80
Field
Length Remarks
1 Key, Always 3
40
6
3
6
Key
Key
1 Key, Always E or M
2 Key
4 Decimal Positions
Assumed
4 Decimal Positions
Assumed
1 Key, Always A, C, or D
5 Sequence Number 13 13
6 Emissions Inventory
Year of Record 14 15
7 Point ID 16 18
8 Compliance/Emissions
Indicator 19 19
9 Segment ID 20 21
10 Control Equipment Cost 22 28
11 Installation Date 29 34
12 Solvent Quantity Purchased 35 40
(gallon)
13 Solvent Quantity 41 46
Reprocessed (gallon)
14 Material Safety Data
Sheet 47 48
15 SDE 6 49 49
16 SDE 7 50 54
17 Peak Ozone Season Daily 55 62
Process Rate
18 Peak CO Season Daily 63 70
Process Rate
19 Update Code 80 80
1 Key, Always 4
Key
Key
1 Key, Always E or M
2 Key
7 2 Decimal Positions
Assumed
6
6
3 Decimal Positions
Assumed
8 3 Decimal Positions
Assumed
1 Key, Always A, C, or D
35
-------
Rev. 7/97
AFS GENERAL SEGMENT INFORMATION
TRANSACTION TYPE 40
(Continued)
9
10
11
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance/Emissions
Indicator
Segment ID
Optional Fuel Units
Update Code
Columns
From Thru
13
14
16
19
20
22
80
13
15
18
19
21
61
80
Field
Length Remarks
1 Key, Always 5
2
3
1
2
40
1
Key
Key
Key, Always E or M
Key
Key, Always A, C, or D
36
-------
Rev. 7/97
AFS SEGMENT POLLUTANT INFORMATION
TRANSACTION TYPE 41
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment ID
Pollutant Code/Chemical
Abstract Number
Emissions Type Indicator
Emissions Value
Decimal Position
Units Code
Method Code
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment ID
Pollutant Code/Chemical
Abstract Number
Primary Control Equipment
Secondary Control
Equipment
Control Equipment
Efficiency (%)
Method Code
Trace Element Percent
Trace Element Method Code
Emission Factor
Emission Factor Decimal
Emission Factor Origin
Emission Factor Source
Ash/Sulfur/Trace Code
SDE 8
Seasonal Adjustment Factor
Rule Effectiveness (%)
From
1
3
6
11
13
14
16
19
20
22
31
35
42
43
45
80
13
14
16
19
20
22
31
34
37
42
43
52
53
59
60
67
68
69
70
74
Thru
2
5
10
12
13
15
18
19
21
30
34
41
42
44
45
80
13
15
18
19
21
30
33
36
41
42
51
52
58
59
66
67
68
69
73
76
Field
Length
2
3
5
2
1
2
3
1
2
9
4
7
1
2
1
1
1
2
3
1
2
9
3
3
5
1
9
1
6
1
7
1
1
1
4
3
Remarks
Key
Key
Key
Key, Always 41
Key, Always 1
Key
Key
Key, Always E or M
Key
Key
Key*
Key, Always A, C, or D
Key, Always 2
Key
Key
Key, Always E or M
Key
Key
3 Decimal Positions
Assumed
7 Decimal Positions
Assumed
37
-------
Rev. 7/97
AFS SEGMENT POLLUTANT INFORMATION
TRANSACTION TYPE 41
(Continued)
Columns Field
Name of Field From
24
25
26
5
6
7
8
9
10
11
12
13
14
15
16
17
18
Rule Effectiveness Method
Code
State Private Indicator
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment ID
Pollutant Code/Chemical
Abstract Number
Primary Control Equipment
Manufacturer
Secondary Control Equipment
Manufacturer
Pollutant Form
Emission Limitation
Description
SIP Rule in Place
Year Regulated
Year Last Modified
Update Code
77
79
80
13
14
16
19
20
22
31
35
39
44
74
75
77
80
*Emissions Type Indicators:
Thru Length Remarks
77
79
80
13
15
18
19
21
30
34
38
39
73
74
76
78
80
ACTU
ALLW
BANK
CODA
CODW
ESTI
ESTW
LIME
MEAS
03DA
03DW
POTC
POTU
1
1
1 Key, Always A, C, or D
1 Key, Always 3
2 Key
3 Key
1 Key, Always E or M
2 Key
9 Key
4
4
1
30
1
2
2
1 Key, Always A, C, or D
- Actual uncontrolled
- Allowable
- Banked
- Peak CO Season W/0 R.E.
- Peak CO Season With R.E.
- Estimated W/0 R.E.
- Estimated With R.E.
- Emission Limitation
- Measured
- Pk Ozone Season W/0 R.E.
- Pk Ozone Season With R.E.
- Potential Controlled
- Potential Uncontrolled
38
-------
Rev. 7/97
AFS SEGMENT CHEMICAL
TRANSACTION TYPE 42
Name of Field
1 State Code
2 County Code
3 Plant ID
4 Transaction Type
5 Sequence Number
6 Emissions Inventory
Year of Record
7 Point ID
8 Compliance/Emissions
Indicator
9 Segment Number
10 Chemical Abstract Number
11 Chemical Density
12 Decimal Position
13 Chemical Weight Percent
14 State Private Indicator
15 Update Code
Columns
From Thru
1
3
6
11
13
14
16
19
20
22
31
36
37
79
80
2
5
10
12
13
15
18
19
21
30
35
36
40
79
80
Field
Length Remarks
2 Key
3 Key
5 Key
2 Key, Always 42
1 Key, Always 1
Key
Key
1 Key, Always E or M
2 Key
9 Key
5
1
4
2 Decimal Positions
Assumed
1 Key, Always A, C, or D
39
-------
Rev. 7/97
AFS SEGMENT PROJECTED POLLUTANT
TRANSACTION TYPE 43
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
5
6
7
8
9
10
11
12
13
14
15
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment Number
Pollutant Code/Chemical
Abstract Number
Projection Year
Projected Inventory Type
Projected Emissions Type
Indicator
Projected Value Type
Projected Emissions/
Limitation Value
Decimal Position
Unit Code
Method Code
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emission
Indicator
Segment Number
Pollutant Code/Chemical
Abstract Number
Projection Year
Projected Inventory Type
Projected Emissions Type
Indicator
Projected Emission
Limitation Description
Update Code
From
1
3
6
11
13
14
16
19
20
22
31
33
34
36
40
47
48
50
80
13
14
16
19
20
22
31
33
34
36
80
Thru
2
5
10
12
13
15
18
19
21
30
32
33
35
39
46
47
49
51
80
13
15
18
19
21
30
32
33
35
65
80
Field
Length
2
3
5
2
1
2
3
1
2
9
2
1
2
4
7
1
2
2
1
1
2
3
1
2
9
2
1
2
30
1
Remarks
Key
Key
Key
Key, Always 43
Key, Always 1
Key
Key
Key, Always E or M
Key
Key
Key
Key+
Key*
Key**
Key, Always A, C, or D
Key, Always 2
Key
Key
Key, Always E or M
Key
Key
Key
Key
Key
Key, Always A, C, or D
40
-------
Rev. 7/97
AFS SEGMENT PROJECTED POLLUTANT
TRANSACTION TYPE 43
(Continued)
Columns Field
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emission
Indicator
Segment Number
Pollutant Code/Chemical
Abstract Number
Projection Year
Projected Inventory Type
Projected Emissions Type
Indicator
Projected Primary
Control Equipment
Projected Secondary
Control Equipment
Projected Control
Equipment Efficiency
Projected Control Equip.
Efficiency Method
Projected Growth
Factor
Projected SIP Rule in
Place
Projected Year Regulated
Projected Rule
Effectiveness (%)
Projected Rule
Effectiveness Method (%)
Update Code
From
13
14
16
19
20
22
31
33
34
36
39
42
47
48
52
53
55
58
80
Thru Length
13
15
18
19
21
30
32
33
35
38
41
46
47
51
52
54
57
58
80
1
2
3
1
2
9
2
1
2
3
3
5
1
4
1
2
3
1
1
Remarks
Key, Always 3
Key
Key
Key, Always E or M
Key
Key
Key
Key+
Key*
3 Decimal Positions
Assumed
2 Decimal Positions
Assumed
Key, Always A, C, or D
Projected Inventory Type:
* Projected Emissions Type Indicators:
** Projected Value Type:
R - Reasonable
M - Modeling
GB - Growth and Base Year Controls
GN - Growth and New Year Controls
LB - Limit and Base Year Controls
LN - Limit and New Controls
PROJ - Projected Emissions
LIMP - Proj . Emission Limitation
41
-------
Rev. 7/97
AFS SEGMENT LEVEL COMMENT
TRANSACTION TYPE 47
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
12
13
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment Number
Comment Number
Comment Identifier
Comment
Enfrcmnt Sensitive Indie.
State Private Indicator
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment Number
Comment Number
Comment Identifier
Comment
Update Code
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance /Emissions
Indicator
Segment Number
Comment Number
Comment Identifier
Comment
Update Code
From
1
3
6
11
13
14
16
19
20
22
25
26
78
79
80
13
14
16
19
20
22
25
26
80
13
14
16
19
20
22
25
26
80
Thru Length
2
5
10
12
13
15
18
19
21
24
25
77
78
79
80
13
15
18
19
21
24
25
79
80
13
15
18
19
21
24
25
79
80
2
3
5
2
1
2
3
1
2
3
1
52
1
1
1
1
2
3
1
2
3
1
54
1
1
2
3
1
2
3
1
54
1
Remarks
Key
Key
Key
Key,
Key,
Key
Key
Key,
Key
Key
Key,
Key,
Key,
Key
Key
Key,
Key
Key
Key,
Key,
Key,
Key
Key
Key,
Key
Key
Key,
Key,
Always
Always
47
1
for Emissions
Always
Always
Always
Always
E or M
C or E
A, C, or D
2
for Emissions
Always
Always
Always
Always
E or M
C or E
A, C, or D
3
for Emissions
Always
Always
Always
E
C or E
A, C, or D
42
-------
Rev. 7/97
AFS SEGMENT PROJECTED POLLUTANT
TRANSACTION TYPE 47
(Continued)
9
10
11
12
13
Name of Field
Sequence Number
Emissions Inventory
Year of Record
Point ID
Compliance/Emissions
Indicator
Segment Number
Comment Number
Comment Identifier
Comment
Update Code
Columns
From Thru
13
14
16
19
20
22
25
26
80
13
15
18
19
21
24
25
79
80
Field
Length Remarks
1 Key, Always 4
2
3
1
2
3
1
54
Key for Emissions
Key
Key, Always E or M
Key
Key
Key, Always C, E or P
1 Key, Always A, C, or D
43
-------
Rev. 7/97
AFS ASBESTOS CONTRACTOR INFORMATION
TRANSACTION TYPE 50
Columns
1
2
3
4
5
6
3
4
5
6
7
3
4
5
6
7
8
9
Name of Field
State Code
Transaction Type
Sequence Number
Contractor ID
Contractor Name
Update Code
Sequence Number
Contractor ID
Contractor Street Address
County Code
Update Code
Sequence Number
Contractor ID
Contractor City
Contractor State
Abbreviation
Contractor Zip Code
Contractor Compliance
Status
Update Code
From
1
11
13
14
26
80
13
14
26
56
80
13
14
26
56
58
67
80
Thru
2
12
13
25
65
80
13
25
55
58
80
13
25
55
57
66
67
80
Field
Length
2
2
1
12
40
1
1
12
30
3
1
1
12
30
2
9
1
1
Remarks
Key
Key,
Key,
Key
Key,
Key,
Key
Key,
Key,
Key
Key,
Always 50
Always 1
Always A, C, or D
Always 2
Always A, C, or D
Always 3
Always A, C, or D
3 Sequence Number
4 Contractor ID
5 Contractor Dun &
Bradstreet Number
6 Contractor Listing
7 Contractor Delisting
8 Contractor Certification
9 Contractor Decertification 53
10 Update Code
13
14
26
35
41
47
53
80
13
25
34
40
46
52
58
80
1 Key, Always 4
12 Key
9
6
6
6
6
1 Key, Always A, C, or D
44
-------
Rev. 7/97
AFS ASBESTOS LANDFILL INFORMATION
TRANSACTION TYPE 51
Name of Field
1 State Code
2 Transaction Type
3 Sequence Number
4 Landfill EPA ID
5 Landfill Name
6 Update Code
Columns Field
From Thru Length Remarks
122 Key
11 12 2 Key, Always 51
13 13 1 Key, Always 1
14 25 12 Key
26 65 40
80 80 1 Key, Always A, C, or D
3 Sequence Number 13 13
4 Landfill EPA ID 14 25
5 Landfill EPA ID Street 26 55
Address
6 Update Code 80 80
1 Key, Always 2
12 Key
30
1 Key, Always A, C, or D
3 Sequence Number 13 13
4 Landfill EPA ID 14 25
5 Landfill EPA ID City 26 55
6 Landfill EPA ID State 56 57
Abbreviation
7 Landfill EPA ID Zip Code 58 66
8 Update Code 80 80
1 Key, Always 3
12 Key
30
2
1 Key, Always A, C, or D
45
-------
Rev. 7/97
AFS ASBESTOS PERFORMANCE INFORMATION
TRANSACTION TYPE 52
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
5
6
7
8
9
10
11
12
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Point Number
Compliance /Emission
Indicator
Contractor State
Contractor ID
Building Owner Operator
Building Owner State
Building Owner Zip Code
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Building Owner Street
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Building Owner City
Contractor Owner Operator
Update Code
From
1
3
6
11
13
14
17
18
20
32
57
59
80
13
14
17
18
20
32
80
13
14
17
18
20
32
56
80
Thru Length
2
5
10
12
13
16
17
19
31
56
58
67
80
13
16
17
19
31
61
80
13
16
17
19
31
55
79
80
2
3
5
2
1
3
1
2
12
25
2
9
1
1
3
1
2
12
30
1
1
3
1
2
12
24
24
1
Remarks
Key
Key
Key
Key,
Key,
Key
Always 52
Always 1
Always C or M
Key
Key
Key,
Key,
Key
Always A, C or D
Always 2
Always C or M
Key
Key
Key,
Key,
Key
Key,
Key
Key
Key,
Always A, C or D
Always 3
Always C or M
Always A, C or D
46
-------
Rev. 7/97
AFS ASBESTOS PERFORMANCE INFORMATION
TRANSACTION TYPE 52
(Continued)
Columns
5
6
7
8
9
10
11
12
13
14
15
16
17
5
6
7
8
9
10
11
12
5
6
7
8
9
10
11
Name of Field
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Asbestos Removed Linear
Feet
Asbestos Removed Square
Feet
Asbestos Removed Cubic Feet
Asbestos Removal Method 1
Asbestos Removal Method 2
Asbestos Removal Method 3
Disposal Site Unknown
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Asbestos Method Removal
Description
Landfill State
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Unauthorized Landfill Name
Update Code
From
13
14
17
18
20
32
39
46
53
54
55
56
80
13
14
17
18
20
32
57
80
13
14
17
18
20
32
80
Thru
13
16
17
19
31
38
45
52
53
54
55
56
80
13
16
17
19
31
56
58
80
13
16
17
19
31
71
80
Field
Length
1
3
1
2
12
7
7
7
1
1
1
1
1
1
3
1
2
12
25
2
1
1
3
1
2
12
40
1
Remarks
Key, Always 4
Key
Always C or M
Key
Key
Key, Always A, C or D
Key, Always 5
Key
Always C or M
Key
Key
Key, Always A, C or D
Key, Always 6
Key
Always C or M
Key
Key
Key, Always A, C or D
47
-------
Rev. 7/97
AFS ASBESTOS PERFORMANCE INFORMATION
TRANSACTION TYPE 52
(Continued)
Columns
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
5
6
7
8
9
10
11
12
Name of Field
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Landfill EPA ID 1
Landfill EPA ID 2
Landfill EPA ID 3
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Unauthorized Landfill
Street
Update Code
Sequence Number
Point Number
Compliance /Emissions
Indicator
Contractor State
Contractor ID
Unauthorized Landfill
Unauthorized Landfill
Code
Update Code
From
13
14
17
18
20
32
44
56
80
13
14
17
18
20
32
80
13
14
17
18
20
City 32
Zip 62
80
Thru
13
16
17
19
31
43
55
67
80
13
16
17
19
31
61
80
13
16
17
19
31
61
70
80
Field
Length
1
3
1
2
12
12
12
12
1
1
3
1
2
12
30
1
1
3
1
2
12
30
9
1
Remarks
Key, Always 7
Key
Always C or M
Key
Key
Key, Always A, C or D
Key, Always 8
Key
Always C or M
Key
Key
Key, Always A, C or D
Key, Always 9
Key
Always C or M
Key
Key
Key, Always A, C or D
48
-------
Rev. 7/97
AFS PLANT MERGE (ASSOCIATION) INFORMATION
TRANSACTION TYPE 60
Columns
1
2
3
4
5
6
7
8
Name of Field
State Code
County Code
Plant ID
Transaction Type
Sequence Number
Plant ID2
CDS/NEDS Indicator
Update Code
From
1
3
6
11
13
14
19
80
Thru
2
5
10
12
13
18
19
80
Field
Length
2
3
5
2
1
5
1
1
Remarks
Key
Key
Key
Key, Always 60
Always 1
Key
Key, Always C or E *1
Key, Always C
*1 C = Compliance, E = Emissions
49
-------
Rev. 2/02
AFS PLANT ARCHIVE INFORMATION
TRANSACTION TYPE 61
Name of Field
1 State Code
2 County Code
3 Plant ID
4 Transaction Type
5 Sequence Number
6 Update Code
Columns Field
From Thru Length Remarks
122 Key
353 Key
6 10 5 Key
11 12 2 Key, Always 61
13 13 1 Always 1
80 80 1 Key, Always C
50
-------
Rev. 7/97
AFS SOURCE/POINT SWAP INFORMATION
TRANSACTION TYPE 64
Columns Field
1
2
3
4
5
6
7
8
9
10
11
12
Name of Field
State Code
Old County Code
Old Plant ID
Transaction Type
Sequence Number
New County Code
New Plant ID
Old Point Number
Old CDS/NEDS Identifier
New Point Number
New CDS/NEDS Identifier
Update Code
From
1
3
6
11
13
14
17
22
25
26
29
80
Thru Length
2
5
10
12
13
16
21
24
25
28
29
80
2
3
5
2
1
3
5
3
1
3
1
1
Remarks
Key
Key
Key
Key,
Always
64
Always 1
Key
Key
Key
Key,
Key
Key,
Key,
Always
Always
Always
C, E or M *1
C, E or M *1
C
*1 C = Compliance, E = Emissions, M = Merged
51
-------
AFS POINT MERGE INFORMATION
TRANSACTION TYPE 65
Rev. 7/97
Name of Field
1 State Code
2 County Code
3 Plant ID
4 Transaction Type
5 Sequence Number
6 Point Number 1
7 Compliance/Emissions
Indicator
8 Point Number 2
9 Compliance/Emissions
Indicator
10 Update Code
Columns Field
From Thru Length Remarks
122 Key
353 Key
6 10 5 Key
11 12 2 Key, Always 65
13 13 1 Always 1
14 16 3 Key
17 17 1 Key, Always C or E *1
18 20 3 Key
21 21 1 Key, Always C or E *1
80 80 1 Key, Always C
*1 C = Compliance, E = Emissions
52
-------
AFS APPLICATION
TRANSACTION TYPE Al
Rev. 7/97
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
5
6
7
8
9
5
6
7
Name of Field
State Code
County Code
AFS Plant ID
Transaction Type
Sequence Number
Application
Application Category
Application Type
Partial Application
Indicator
Reported Compliance
Status
Reported Compliance
Reason
Permit Authority Staff 1
Update Code
Sequence Number
Application
Permit Authority Staff 2
Permit Authority Staff 3
Update Code
Sequence Number
Application
Permit Authority Data
From
1
3
6
21
23
24
39
41
42
43
44
46
80
23
24
39
64
80
23
24
39
Thru
2
5
20
22
23
38
40
41
42
43
45
70
80
23
38
63
79
80
23
38
78
Field
Length
2
3
15
2
1
15
2
1
1
1
2
25
1
1
15
25
16
1
1
15
40
Remarks
Key
Key
Key
Key, Always Al
Key, Always 1
Key
Always A, C, or D
Key, Always 2
Key
Always A, C, or D
Key, Always 3
Key
Element 1
Update Code
80
80
Always A, C, or D
5 Sequence Number 23 23 1
6 Application 24 38 15
7 Permit Authority Data 39 78 40
Element 2
8 Update Code 80 80 1
Key, Always 4
Key
Always A, C, or D
5 Sequence Number 23 23 1
6 Application 24 38 15
7 Permit Authority Data 39 78 40
Element 3
8 Update Code 80 80 1
Key, Always 5
Key
Always A, C, or D
53
-------
Rev. 7/97
AFS GENERAL INFORMATION - DRAFT PERMIT
TRANSACTION TYPE A2
Name of Field
1 Permit State Code
2 Transaction Type
3 Sequence Number
4 Permit
5 Permit Category
6 Permit Workfile
7 State Private Indicator
8 Update Code
Columns
From Thru
1
21
23
24
39
40
79
80
2
22
23
38
39
78
79
80
Field
Length
2
2
1
15
1
39
1
1
Remarks
Key
Key, Always A2
Key, Always 1
Key
Always A, C, or D
3 Sequence Number 23 23
4 Permit 24 38
5 Effective Date (YYYYMMDD) 39 46
6 Modification/Renewal 47 54
Effective Date (YYYYMMDD)
7 Expiration Date 55 62
(YYYYMMDD)
8 Update Code 80 80
1 Key, Always 2
15 Key
Always A, C, or D
3 Sequence Number 23 23 1
4 Permit 24 38 15
5 Permit Authority Data 39 78 40
Element 1
6 Update Code 80 80 1
Key, Always 3
Key
Always A, C, or D
3 Sequence Number 23 23 1
4 Permit 24 38 15
5 Permit Authority Data 39 78 40
Element 2
6 Update Code 80 80 1
Key, Always 4
Key
Always A, C, or D
3 Sequence Number 23 23 1
4 Permit 24 38 15
5 Permit Authority Data 39 78 40
Element 3
6 Update Code 80 80 1
Key, Always 5
Key
Always A, C, or D
54
-------
Rev. 6/2006
AFS APPLICATION ASSOCIATION - DRAFT PERMIT
TRANSACTION TYPE A7
Name of Field
Columns
From Thru
Field
Length
Remarks
1 State Code
2 County Code
3 AFS Plant ID
4 Transaction Type
5 Sequence Number
6 Permit
7 Application
8 Application
9 Update Code
1
3
6
21
23
24
39
54
80
2
5
20
22
23
38
53
68
80
2
3
15
2
1
15
15
15
1
Key
Key
Key
Key, Always A7
Key, Always 1
Key
Always A, C, or D
55
-------
Rev. 7/97
AFS EVENT TRACKING ACTION
TRANSACTION TYPE AS
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
5
6
7
8
9
10
11
12
13
5
6
7
8
9
10
11
5
6
7
8
9
10
11
Name of Field
State Code
County Code
AFS Plant ID
Transaction Type
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
EPA Code
Agency State Code
Local Control Region
Permit Staff Name
Update Code
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Results Code
Permit Date Achieved
(YYYYMMDD)
Permit Date Scheduled
(YYYYMMDD)
Update Code
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Complaint Id
Update Code
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Action Description
Update Code
From
1
3
6
21
23
24
39
54
56
59
61
63
65
80
23
24
39
54
56
59
61
69
80
23
24
39
54
56
59
80
23
24
39
54
56
59
80
Thru
2
5
20
22
23
38
53
55
58
60
62
64
79
80
23
38
53
55
58
60
68
76
80
23
38
53
55
58
68
80
23
38
53
55
58
79
80
Field
Length
2
3
15
2
1
15
15
2
3
2
2
2
15
1
1
15
15
2
3
2
8
8
1
1
15
15
2
3
10
1
1
15
15
2
3
21
1
Remarks
Key
Key
Key
Key, Always AS
Key, Always 1
Key
Key
Key
Key
Always A, C, or D
Key, Always 2
Key
Key
Key
Key
Always A, C, or D
Key, Always 3
Key
Key
Key
Key
Always, A, C, or D
Key, Always 4
Key
Key
Key
Key
Always A, C, or D
56
-------
AFS EVENT TRACKING ACTION
TRANSACTION TYPE AS
(Continued)
Rev. 7/97
Name of Field
5 Sequence Number
6 Application
7 Permit
8 Permit Action Type
9 Permit Action Number
10 Permit Action Data
Element 1
11 Update Code
Columns
From Thru
23
24
39
54
56
59
80
23
38
53
55
58
79
80
Field
Length
1
15
15
2
3
21
Remarks
Key, Always 5
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number 23 23 1
6 Application 24 38 15
7 Permit 39 53 15
8 Permit Action Type 54 55 2
9 Permit Action Number 56 58 3
10 Permit Action Data 59 79 21
Element 2
11 Update Code 80 80 1
Key, Always
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number
6 Application
7 Permit
8 Permit Action Type
9 Permit Action Number
10 Permit Action Data
Element 3
11 Update Code
23
24
39
54
56
59
23
38
53
55
58
79
1
15
15
2
3
21
80
80
Key, Always 7
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number 23 23
6 Application 24 38
7 Permit 39 53
8 Permit Action Type 54 55
9 Permit Action Number 56 58
10 EPA Agency Notified 59 60
11 Agency State Notified 61 62
12 Local Ctrl Region Notif. 63 64
13 Update Code 80 80
1
15
15
2
3
2
2
2
1
Key, Always 8
Key
Key
Key
Key
Always, A, C, or D
57
-------
Rev. 7/97
AFS PLANT PERMIT COMMENT
TRANSACTION TYPE B9
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
5
6
7
8
9
5
6
7
8
9
5
6
7
8
9
Name of Field
State Code
County Code
AFS Plant ID
Transaction Type
Sequence Number
Permit
Permit Comment Number
EPA Code
Agency State Code
Local Control Region
Permit Comment
Owner Private
Update Code
Sequence Number
Permit
Permit Comment Number
Permit Comment
Update Code
Sequence Number
Permit
Permit Comment Number
Permit Comment
Update Code
Sequence Number
Permit
Permit Comment Number
Permit Comment
Update Code
From
1
3
6
21
23
24
39
42
44
46
48
79
80
23
24
39
42
80
23
24
39
42
80
23
24
39
42
80
Thru
2
5
20
22
23
38
41
43
45
47
78
79
80
23
38
41
79
80
23
38
41
79
80
23
38
41
79
80
Field
Length
2
3
15
2
1
15
3
2
2
2
31
1
1
1
15
3
38
1
1
15
3
38
1
1
15
3
38
1
Remarks
Key
Key
Key
Key, Always B9
Key, Always 1
Key
Key
Always A, C, or
Key, Always 2
Key
Key
Always A, C, or
Key, Always 3
Key
Key
Always A, C, or
Key, Always 4
Key
Key
Always A, C, or
D
D
D
D
58
-------
Rev. 7/97
AFS EVENT TRACKING ACTION COMMENT
TRANSACTION TYPE Cl
Columns
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
5
6
7
8
9
10
11
13
5
6
7
8
9
10
11
12
Name of Field
State Code
County Code
AFS Plant ID
Transaction Type
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Comment Number
EPA Code
Agency State Code
Local Control Region
Owner Private
Update Code
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Comment Number
Permit Comment
Update Code
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Comment Number
Permit Comment
Update Code
From
1
3
6
21
23
24
39
54
56
59
62
64
66
79
80
23
24
39
54
56
59
62
80
23
24
39
54
56
59
62
80
Thru
2
5
20
22
23
38
53
55
58
61
63
65
67
79
80
23
38
53
55
58
61
79
80
23
38
53
55
58
61
79
80
Field
Length
2
3
15
2
1
15
15
2
3
3
2
2
2
1
1
1
15
15
2
3
3
18
1
1
15
15
2
3
3
18
1
Remarks
Key
Key
Key
Key, Always Cl
Key, Always 1
Key
Key
Key
Key
Key
Always A, C, or D
Key, Always 2
Key
Key
Key
Key
Key
Always A, C, or D
Key, Always 3
Key
Key
Key
Key
Key
Always A, C, or D
59
-------
AFS PERMIT ACTION COMMENT
TRANSACTION TYPE Cl
(Continued)
Rev. 7/97
Name of Field
5 Sequence Number
6 Application
7 Permit
8 Permit Action Type
9 Permit Action
10 Permit Comment Number
11 Permit Comment
12 Update Code
Columns
From Thru
23
24
39
54
56
59
62
80
23
38
53
55
58
61
79
80
Field
Length
1
15
15
2
3
3
18
1
Remarks
Key, Always 4
Key
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number
6 Application
7 Permit
8 Permit Action Type
9 Permit Action Number
10 Permit Comment Number
11 Permit Comment
12 Update Code
23
24
39
54
56
59
62
80
23
38
53
55
58
61
79
80
1
15
15
2
3
3
18
1
Key, Always 5
Key
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number 23 23
6 Application 24 38
7 Permit 39 53
8 Permit Action Type 54 55
9 Permit Action Number 56 58
10 Permit Comment Number 59 61
11 Permit Comment 62 79
12 Update Code 80 80
1 Key, Always 6
15 Key
15 Key
2 Key
3 Key
3 Key
18
1 Always A, C, or D
5 Sequence Number 23 23
6 Application 24 38
7 Permit 39 53
8 Permit Action Type 54 55
9 Permit Action Number 56 58
10 Permit Comment Number 59 61
11 Permit Comment 62 79
12 Update Code 80 80
1 Key, Always 7
15 Key
15 Key
2 Key
3 Key
3 Key
18
1 Always A, C, or D
-------
Rev. 7/97
AFS PERMIT ACTION COMMENT
TRANSACTION TYPE Cl
(Continued)
Columns
5
6
7
8
9
10
11
12
Name of Field
Sequence Number
Application
Permit
Permit Action Type
Permit Action Number
Permit Comment Number
Permit Comment
Update Code
From
23
24
39
54
56
59
62
80
Thru
23
38
53
55
58
61
79
80
Field
Length
1
15
15
2
3
3
18
1
Remarks
Key, Always 8
Key
Key
Key
Key
Key
Always A, C, or D
5 Sequence Number
6 Application
7 Permit
8 Permit Action Type
9 Permit Action Number
10 Permit Comment Number
11 Permit Comment
12 Update Code
23
24
39
54
56
59
62
80
23
38
53
55
58
61
79
80
1
15
15
2
3
3
18
1
Key,
Key
Key
Key
Key
Key
Aiwa
Always 9
C, or D
61
-------
AIRS User's Guide
AF3 AFS Data Storage
APPENDIX B
AFS GENERATE UNKNOWN COMPLIANCE UTILITY FLOWCHARTS
September 2005 Appendix B
-------
12/16/08
Generate Unknown Compliance Status Utility
STEP1: Determine if the
plant is part of the CMS
E|Se->
Exit utility
STEP 2: Determine the current
default compliance status of the Facility
Else-*
STEP 3: If CMSI
-Then->
—Then-)
Either
CMSC=OorZ
or
CMSI is equal to or greater
than the recommended
minimum frequencies
—Then-*
-Then*
STEP 4: Generate oldest possible
FCE date (BASELINE)
Subtract CMSI from the
current date giving the
FCE BASELINE date
(convert to FY)
-Then-* g,
3 to
sp 5
STEP 6: Generate FY for
Default Date of Latest FCE
(ACTUAL)
Generate FY
for DFD1
-Then-* ^
)to
P7
STEP 5: Determine if the CMS start date
keeps the plant in the Utility
Else-*
STEP 7: Is
the ACTUAL FCE past due?
Version 6.0
-------
12/18/07
Generate Unknown Compliance Status Utility
Generate
SIP air program (0)
air program status = O
Generate
ECAP=U
Generate
ECLP=A
Update the
record with JH1
& current date
Version 5.0
-------
12/18/07
Generate Unknown Compliance Status Utility
Generate
SIP air program (0)
air program status = O
Version 5.0
-------
APPROVED 11/6/03
Ungenerate Unknown Compliance Status Utility
Update the
record with
JH1 &
current date
THEN-
Has an FCE beerh
performed within the
appropriate CMS
timeframe?
-NO-
EXIT Utility
YES
THEN
THEN-
Update the
record with
JH1 &
current date
-THEN
THEN-
Version 1.3
-------
12/18/07
Effect on CMS Start Date
when CMSC is modified
Description
Blank to anything
Anything to blank
Downgrade to SM80 or Other
Upgrade to Major or Mega
Downgrade to Other
Upgrade to any value
j current value
| CMSC
blank
A, E, M, G, S, N,OorZ
A, E, MorG
SorN
s oFisi
OorZ
new value
CMSC
^^^
blank
_^jysLP^Lz^^
A, E, MorG
Oo'rZ
A,E, M.G.SorN
Effect on
CMS Start Date
change to current date
blank out
dojnotJTing
change to current date
dojnothing
..changjBjo_cjjrrent_dat_e_
version 5.0
------- |