1 I n t e g r i t y - S e r v i c e - E x c e l l e n c e The Air Emissions Inventory (AEI) The Air Emissions Inventory (AEI) Project: Project: An Update on a Universal Schema An Update on a Universal Schema Darren Carpenter, APIMS Program Management Office Support [email protected]Dennis Burling, Nebraska Department of Environmental Quality [email protected]
18
Embed
1 I n t e g r i t y - S e r v i c e - E x c e l l e n c e The Air Emissions Inventory (AEI) Project: An Update on a Universal Schema Darren Carpenter,
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1I n t e g r i t y - S e r v i c e - E x c e l l e n c e
The Air Emissions Inventory (AEI) Project: The Air Emissions Inventory (AEI) Project:
An Update on a Universal SchemaAn Update on a Universal Schema
5I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Background
• Overwhelming majority of APIMS users have some form of an annual emission inventory requirement
• 62 CONUS facilities meet this requirement in ≈ 50 different formats which leads to substantial costs
• These factors have led to the current study6I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Study Goals
• Develop a universal schema for submission of emission inventories– Working with partner States to ensure that the
schema can be used by industrial and military facilities
• Utilize all available technologies to maximize cost savings for all participants– Exploit the current Exchange Network
Technologies and Services (i.e. Node Architecture, Schematron, Web Services, etc.)
7I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Study Goals
8I n t e g r i t y - S e r v i c e - E x c e l l e n c e
• Establish the Air Force node on the Exchange Network– Allows data flow from Air Force through CDX
and to the appropriate State & Local agencies
• Replace current AEI submission formats with electronic submission via the CDX using the Universal Schema for all APIMS users in the participating States.
Study Participants
9I n t e g r i t y - S e r v i c e - E x c e l l e n c e
• Air Force / APIMS PMO– Total of 15 facilities using APIMS spread across
the participating States• Nebraska• North Carolina• Texas• Utah• Washington• Maine
• OAQPS providing guidance and facilitation
10I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Progress To Date
• Universal Schema has been developed– Reviewed by participating States and the APIMS
PMO to ensure that the States’ needs, as well as the Air Force needs, were addressed
– Developed according to the data model structure of the Facility and Point Inventory Schema (EIS)
– Utilizes a hierarchical, integrated structure instead of individual data element submissions
11I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Universal Schema Conceptual
DiagramFacilitySiteCollection
EmissionUnitCollection
EmissionReleasePointCollection
EmissionProcessCollection
OperatingParametersCollection
EmissionsCollection
ControlMeasureCollection
ApplicableRegulationCollection
12I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Universal Schema Details
• Comprised of 9 “collections” of data– Facility/Site
– Emission Unit
– Emission Release Point
– Emission Process
– Operating Parameters
– Emissions
– Control Measures
– Applicable Regulations
13I n t e g r i t y - S e r v i c e - E x c e l l e n c e
• Integrated the Exchange Network Shared Schema Components (SSC) into the Universal Schema
• Hierarchical Structure – Eliminates data redundancy• Strict Data Validation – Results in cleaner data• Flexible Architecture implemented to allow differences
in the number of elements that an entity desires to submit (i.e. Sites, Control Measures)
• Built so that Data Lengths, and even Data Types, can be modified relatively easily
• Designed and built to be Universal (Industry or Military)
Universal Schema Details
14I n t e g r i t y - S e r v i c e - E x c e l l e n c e
• Create a Memorandum of Understanding (MOU) with all study partners– Initial draft created in May 2006– Finalized before data is passed from APIMS to the
respective partner
• Create a Schematron process against the universal schema– Will be reviewed and modified as needed during
the schema testing process
Remaining Study Milestones
15I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Remaining Study Milestones
• Develop Flow Configuration Document– Will serve as the road map for data exchange
between the Air Force and all participating partners
• Universal Schema Testing– Verify export from APIMS in universal schema
format– Verify transfer from Air Force Node to each State
node– Investigate options for electronic signature
16I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Remaining Study Milestones
• State review of submission package– Completed in parallel with universal schema testing– Review package to ensure all needed data is
included
• Develop converters for each State– Converters will allow transformation of data from
the universal schema to an easier format for review
17I n t e g r i t y - S e r v i c e - E x c e l l e n c e
Remaining Study Milestones
• Move data exchange into full production– Dependent on successful completion of each
previous milestone
• Eliminate previous AEI Submission procedures– Dependent on verification of successful AEI
submission via the CDX using the Universal Schema
18I n t e g r i t y - S e r v i c e - E x c e l l e n c e