RAPIDS evaluation project report

120 Pages·2000·17.7 MB·English

by  Alberta. Environmental Sciences Division

fl-L.5L^200|-35
Cl 3^
ydlberra
ENVIRONMENT
Digitized by the Internet Archive
in 2016
https://archive.org/details/rapidsevaluationOOalbe
/diberra
ENVIRONMENT

RAPIDS Evaluation
Project Report
Prepared for:
By
Science and Technology Branch
Environmental Sciences Division
Alberta Environment
LGS Group Inc.
March, 2000
Pub. No. T/561
ISBN: 0-7785-1 391 -2 (Printed Version)
ISBN: 0-7785-1 393-9 (On-Line Version)
Web Site: http://www.gov.ab.ca/env/protenf/publications
Although prepared with funding from Alberta Environment (AENV), the contents of this
report/document do not necessarily reflect the views or policies of AENV, nor does mention of
trade names or commercial products constitute endorsement or recommendation for use.
Any questions on this document may be directed to:
Environmental Sciences Division
Alberta Environment
4^^ Floor, Oxbridge Place
9820 - l Oe^'^ Street
Edmonton, Alberta T5K 2J6
Phone: [phone]
Fax: (780) 422-4192
Email: [email protected]
Additional copies of this document may be obtained by contacting:
Information Centre
Alberta Environment
Main Floor, Great West Life Building
9920-108'^ Street
Edmonton, Alberta T5K 2M4
Phone: [phone]
Fax: [phone]
Email: [email protected]
SUMMARY
Alberta Environment (AENV) is seeking a s ystem that will satisfy its current and identified
future emission inventory requirements.
This project evaluates the Regional Air Pollutant Inventory Development System (RAPIDS) to
determine its applicability, its usability, and how electronic data transfer of emissions and other
data can be facilitated.
RAPIDS was found to be generally suitable as an emissions inventory system. It p rovides an
excellent data framework to manage emissions inventory information for AENV. It can ensure
consistency of information, and it p rovides standardised methodologies for estimating and
reporting emissions. Because RAPIDS was developed and is supported by the Great Lakes
Commission to serve as a c ommon emission inventory system for agencies, AENV can
potentially participate in a c ommon support and development process for RAPIDS.
As part of the evaluation RAPIDS was presented to selected industry representatives through a
one-day workshop and feedback was solicited. RAPIDS can serve as a c ommon emissions
inventory system for both AENV and industry, and some participants expressed interest in using
RAPIDS as their facility emissions management system.
RAPIDS has the capability to export from one user’s system to another, so the submission
process can be very straightforward. If some users wish to maintain their own data management
system and not use RAPIDS, then a s tandard data format can be derived.
Through the workshop, RAPIDS was found to be complex to use, and in its current form it m ay
not satisfy industry’s need to streamline their emission information reporting process. It was
also noted that some industries either had their own software or were intending to develop
software for maintaining this type of information for submission to AENV
For RAPIDS to be effective for use by AENV, it must be linked with other AENV systems and
specific interfaces for information submission and access must be developed. Should RAPIDS
not be adopted, these same standards must also apply to an alternate.
RAPIDS Evaluation Project Report i
RAPIDS Evaluation Project Report ii
TABLE OF CONTENTS
SUMMARY I
1 PROJECT OVERVIEW 1
1 . 1 Obj ecti ve of Proj ect 1
1 .2 Overview of Emission Inventory Status 1
1 .3 Influencing Factors 2
1.4 Project Goals 2
1. 4. 1 Suitability as Emissions Estimation and Compliance Tool 3
1. 4. 2 Determine RAPIDS Software Usability 3
1.4.3 Suitability of R APIDS for CEM Data 3
1.4.4 Set Standards for Electronic Data Transfer 4
1 .5 Approach to Project 4
2 ASSESSMENT OF RAPIDS 5
2.1 Overview of RAPIDS 5
2.2 Suitability as an Emissions Estimator for AENV 6
2. 2. 1 Assessment of R APIDS informational capability 6
2. 2. 2 Definition of A ENV Requirements 8
2.2.3 Specific Applicability of R APIDS for AENV / 1
2.3 RAPIDS Usability 14
2. 3. 1 Workshop Example Description 15
2. 3. 2 RAPIDS - U sabil ity Overview 16
2. 3. 3 RAPIDS - E ase of Use as an Emission Estimation Tool 16
2. 3. 4 RAPIDS - E ase of Use as a C ompliance Data Submission Tool 17
2. 3. 5 Strengths of R AP IDS 17
2. 3. 6 Deficiencies in RAPIDS 18
2. 3. 7 Integration with Existing Industry Data Systems 19
3 MECHANISMS FOR ELECTRONIC DATA TRANSMISSION 20
3 . 1 Summary of Current Electronic Data Transfer Mechanisms 20
3. 1. 1 Summary of D ata Transfer Mechanisms Currently Used by EMS 20
3.1.2 Summary of I ndustry Technical Environment Capability 21
3.1.3 Summary of R APIDS Ability to Provide a M echanism for Electronic Data Transmission 23
3.2 Identified Requirements 23
3. 2. 1 Reporting Specifications 24
3. 2. 2 Electronic Data Transmission Mechanisms 24
3. 2. 3 Encryption 25
3.2.4 Data Validation 25
3.2.5 Data Access 26
3. 2. 6 Data Confidentiality 26
3.3 Conceptual Architecture 27
4 NEXT STEPS 29
APPENDIX I: WORKSHOP MATERIALS A1
APPENDIX II: QUESTIONNAIRE AND CONSOLIDATED INDUSTRY
FEEDBACK A2
RAPIDS Evaluation Project Report iii
LIST OF TABLES
Table 1 AENV Emission Inventory Data (Approved Industrial Operations) 10
LIST OF FIGURES
Figure 1 Workshop Example 15
Figure 2 Conceptual Architecture 28
RAPIDS Evaluation Project Report iv