Overview of the RAPIDS System

RAPIDS is a client/server system consisting of an ORACLE back-end database (version 7.0), designed using ORACLE CASE tools, and a suite of front-end applications developed using various software tools (e.g., primarily PowerBuilder and SAS). The RAPIDS system includes the following components:

• RAPIDS Database
• FIRE Upload client/application
• Data Import and Data Export client applications
• Query
• QC Checker client/application
• Report Generator
• Data Converter client/application
• Emission Estimator client/application

The RAPIDS Database

The RAPIDS database includes the following components:

• An ORACLE back-end database consisting of various ORACLE data tables of emissions data and estimates located on a separate (i.e., separate from the front-end client applications) file server at each participating state;



• A set of Data Entry client/applications developed in PowerBuilder that consists of various forms/screens to enter various types of emissions data, and emission estimates derived external to RAPIDS;



• A set of ORACLE data tables of emissions data and estimates located at the Great Lakes National Program Office (GLNPO) containing emissions data and estimates obtained from each of the participating states (i.e., a regional database of emissions data and estimates). RAPIDS includes a client/application that uploads (GLNPO Upload) each state's set of ORACLE tables to the regional repository located at GLNPO.

RAPIDS Data Model

The RAPIDS data model is the cornerstone of the RAPIDS system and includes entities that are shared by most mission critical applications. As more applications are added to the RAPIDS system, the core data model will be extended to support them.

FIRE Upload

A FIRE Upload client/application (this application is under development) that will upload the emission factors contained in FIRE into a reference table used to calculate emissions. The Factor Information Retrieval System or FIRE is an emission factor database repository developed by U.S. EPA. The emission factors contained in FIRE have been incorporated into RAPIDS and used within the system to compute emission estimates for certain source categories.)

Data Import and Data Export

Data Import and Data Export client applications facilitate the import of emissions data and estimates maintained by the states external to RAPIDS into the back-end database, and the export of data from the back-end database into ASCII files (i.e., import file format).

Query

The QUERY application provides the user with access to InfoMaker (the InfoMaker software is not provided with RAPIDS), a powerful, easy-to-use ad-hoc reporting tool that lets users query the RAPIDS database and create custom reports of data. This ad-hoc query and reporting tool supplements the pre-defined reports created by the Reporting client/application.

QC Checker

A QC Checker client/application that perform various statistical checks on the emissions data and estimates contained in the ORACLE back-end database. A sample QC Checker screen shows the various options available to the user for performing these statistical checks. Additional statistical checks are expected to be added to the QC Checker application over time.

Report Generator

A Report Generator consisting of various client/applications that generate summary reports of the emissions data and estimates contained in the ORACLE back-end database. A sample Tier 1, 2, 3 Reporting screen shows the various reporting options available to the user for this particular report.

Data Converter

A Data Converter client/application converts the emissions data and estimates into U.S. EPA's AIRS Facility Subsystem (AFS) transaction records. A sample AIRS Converter screen shows the various options available to the user for creating AFS transaction record from RAPIDS.

Emission Estimator

An Emission Estimator client/application allows the user to compute emission estimates using a variety of emission estimation techniques [e.g., product of activity data and an approved emission factor, speciation of either particulate matter (PM) or VOC emission estimates or user-defined algorithms] that match pre-established SCC/compound-specific methodologies listed in the Air Toxics Protocol. (The protocol is a comprehensive document that describes the methodologies the participating states will use to compile the regional inventory, including the procedures to resolve differences of opinion). A sample emission estimation screen shows the various options available to the user for estimating emissions.

RAPIDS software was designed with several features:

• An easy-to-use Windows format built with state-of-the-art database management tools.



• A menu-oriented design with an interface that maintains a consistent "look and feel" throughout the various system modules.



• Data storage and management for point source and area source emissions estimates. Although a fugitive emissions data model is not presently a RAPIDS feature, the system is designed to accommodate this component at a later date.



• Specific emissions estimates for states, facilities, devices, processes or streams can be incorporated.



• Source-specific emission factors can be stored and used to calculate emission estimates.



• Batch and interactive emission estimation capabilities, using emission factors, activity data, mass balance and speciation.



• Batch input and on-line updates.



• Various QA/QC checks and routines on the emissions data and estimates are performed, including range checks, outlier checks, acceptable value checks, missing value flags and other techniques, to identify suspicious or unacceptable data.



• Point and area source data and estimates stored in RAPIDS are converted into the U.S. EPA's Aerometric Information Retrieval System (AIRS) transaction format.



• Emissions summary report generation.