Proposed Changes to the Consolidated
Emissions Reporting Schema (CERS)
for the 2020 National Emissions
Inventory
Created by the Office of Air Quality Planning and Standards
Outreach and Information Division
National Air Data Group
December 17, 2019
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Table of Contents
Contents
Overview 4
CERS Components 4
General Notes 6
Description of Roles Within EIS 6
Changes Listed by Component 6
New Fugitive Release Point Types 10
Fugitive 3-Dimentational Fugitive Release Point Type 10
Fugitive 2-Dimentational Fugitive Release Point Type 10
"Traditional" Fugitive Release Point Type 12
Low Flow Vent 12
About Controls 13
Control Components 13
Control Path Example 1 - Single Control 15
Defining the Control Path 16
Associating the Control Path with a Release Point Apportionment 17
Example 1 Sample XML 17
Control Path Example 2 -Controls Connected in Series 19
Associating the Control Path with a Release Point Apportionment 21
Example 2 Sample XML 21
Control Path Example 3 -Controls Connected in Parallel 22
Summary of Controls 26
Appendix A - Proposed CERS Attribute List 27
FacilitySite Component 27
Facilityldentification Component 27
FacilityNAICS Component 28
FacilitySiteAddress Component 29
FacilitySiteGeographicCoordiantes and ReleasePointGeographicCoordinates Components 29
FacilitySiteControls Component (New Component) 30
FacilitySiteControls Component (New Component) 30
ControlPollutants Component (New Component) 30
Pg- 2
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Controlldentification Component (New Component) 31
Controlldentification Component (New Component) 31
FacilitySiteControlPaths Component (New Component) 31
ControlPathldentification Component (New Component) 31
ControlPathDefinition Component (New Component) 31
ControlPathDefinitionPathldentification Component (New Component) 32
ControlPathDefinitionControlldentification Component (New Component) 32
ReleasePoint Component 32
ReleasePointldentification Component 33
EmissionsUnit Component 33
Unitldentification Component 34
UnitRegulation and ProcessRegulation Components 34
UnitEmissionsProcess Components 34
Processldentification Component 34
ReleasePointApportionmentPathldentification Component (New Component) 34
Pg- 3
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Overview
The Consolidated Emissions Reporting Schema (CERS) is used by the Emissions Inventory System (EIS) to
provide a standardized structure for submitting emissions inventory data to the United States
Environmental Protection Agency (EPA). CERS has remained relatively unchanged since being adopted
by EIS in 2008. Due to changes in program requirements, requests from our user community, and
changes in the goals of data sharing within EPA, there is a need to make changes to the CERS to support
these additional needs. This document outlines and describes these proposed changes. Final changes
to the CERS will be announced in spring of 2020.
This document will describe changes, deletions, and additions to each of the components of the CERS.
This includes which user groups are impacted by the changes. A separate document outlining the
quality assurance edit checks that will be performed by EIS will be developed once a final version of the
CERS changes is published. This document is not intended to serve as guidance for how the CERS will
change, but rather provide an opportunity for the EIS community to review and comment on changes
that are being proposed.
It is important to remember that EIS is only one user of the CERS. Consequently, there are elements
within the CERS that EIS currently does not utilize that will remain within the CERS. These will be noted
in the reference materials.
Most of the changes being considered apply to the Facility Inventory data category.
All comments for the content of this document should be directed to Jonathan Miller
(miller.ionathan@epa.gov) of the National Air Data Group.
Facility Inventory CERS Components
"Figure - 1" below shows the relational hierarchy of the components within the Facility Inventory
structure of the CERS. The items noted with an asterisk (*) are components that are not used by EIS but
will continue to be part of the CERS schema. If this information is submitted to EIS, no errors will be
generated, but EIS will not retain the provided information for these components.
There are a few items to note:
1) There is no longer a UnitControlApproach or ProcessControlApproach component. Due to a
change in the requirements of information to be stored related to controls for EIS, a substantial
change was required. These changes to the controls will be discussed in greater detail later in
the document (See "About Controls").
2) There are several new components (also related to controls) that have been added:
a. FacilitySiteControls
i. ControlPollutants
ii. Controlldentification
b. FacilitySiteControlPaths
i. ControlPathDefinition
ii. ControlPathldentification
Pg- 4
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Fa cilitySite
FacilityNAICS
Facilityldentification
AlternateFa cilityNa me
Emissionsllnit
ReleasePoint
Fa cilitySite Affiliation
Fa cilitySite
GeographicCoordinates
Fa cilitySite Address
Fa cilitySite Controls
Fa cilitySite Control Paths
Fa cilitySite Quality
Identification*
Fa cilitySite Attached File*
U nitQua I itylde nt if ica tion
Unitldentification
UnitRegulation
FmissionsUnitProcess
ReleasePointTest
ReleasePointldentification
ReleasePoint
GeographicCoordinates
AffiliationOrganization
Affiliat ionlndivid u al *
ControlPollutants
Control Identification
Control Pathldentification
Control PathDefinit ion
Processl dent if icatio n
ProcessRegulation
ReleasePoint
Apportionment
Control PathDefinit ion
Cont rol I dent ificat ion
Control PathDefinit ion
Pathldentification
- Component Not Used By EIS
ReleasePoint
Apportionment
Identification
ReleasePoint
Apportionment Path
Identification
Figure 1: CERS Components
The following sections will describe in greater detail changes to each of these components.
Pg- 5
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
General Notes
The following sections describe changes to the existing CERS and will not contain all attributes contained
within the component. It may be assumed that if an attribute is not listed within each component, the
current names, definitions, and rules about that attribute are unchanged. This section does not address
the new components associated with controls. Those elements will be discussed in a separate section of
this document.
Please refer to "Appendix A: Proposed CERS Attribute List" to see the order of where each of these
attributes appear within the component.
Description of Roles Within EIS
There are several roles that a user may have within EIS. The role assigned to a user dictates what fields
are accessible and, in some cases, determine what quality assurance checks are applied. For purposes
of this document, the two roles of note are
Role Name
Role Description
Inventory Developer
This role is usually a representative of OAQPS' Emissions Inventory
Assessment Group. This role has the overview responsibility for the data
provided to EIS. Inventory Developers can view all facility site information
contained within EIS, may set values that are used in quality assurance
checks, and have the ability to "lock" specific fields or records within the
facility inventory. Data that has been locked cannot be modified by anyone
until the lock is removed.
SLT User
An acronym meaning "State, Local, or Tribal User". SLT Users provide data
from their organization to the EPA. SLT Users may only provide data for the
facilities and locations that their agencies have been granted access.
Changes Listed by Component
The highlighted items listed are accessible by all users. Those fields without highlights are only accessible
by Inventory Developers. If an SLT user tries to use one of these fields, a "warning" message will appear
on their feedback report indicating that the user does not have access to these fields and the
information will be ignored. All other information about the submitted record will be processed.
Most of the new fields are additions to existing components and are not required. There are some
notable exceptions:
1. When providing a FacilityNAICS component, you must provide a NAICSPrimarylndicator.
Historically, EIS has only carried the "PRIMARY" NAICS indicator. Going forward, you must still
provide 1 and only 1 "PRIMARY" type of NAICS indicator for a new facility. You may also provide
as many "SECONDARY" or "TERTIARY" NAICS values as you would like. No "SECONDARY" or
"TERTIARY" NAICS values are required. However, any provided SECONDARY or TERTIARY NAICS
code definitions must be unique.
2. Within the EmissionsProcess component, the LastlnventoryYear field will no longer be used by
EIS. Instead, ProcessStatusCode and ProcessStatusCodeYear will be used to define the status of
a given emissions process. The ProcessStatusCode is a required column for new emission
Pg- 6
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
processes. The ProcessStatusCodeYear is required if the ProcessStatusCode is not "OP"
("operational"). This is consistent with other facility component types.
Component
Attribute
Notes
FacilitySite
FacilitySourceTypeCode
New item only accessible by Inventory
Developers
FacilitySite
HAPFacilityCategoryCode
New item only accessible by Inventory
Developers
FacilitySite
CoordinateTolerance
New item only accessible by Inventory
Developers
FacilitySite
FacilityNamelsReadOnly
New item only accessible by Inventory
Developers
FacilitySite
LocationlsReadOnly
New item only accessible by Inventory
Developers
Facilityldentification
Alternative! DIsReadOnly
New item only accessible by Inventory
Developers
FacilityNAICS
NAICSPrimarylndicator
This field already exists in the CERS but
will now be available to EIS. It is
available to all users. Allowable values
will be "PRIMARY", "SECONDARY",
"TERITIARY". A facility must have 1
PRIMARY NAICS. Multiple NAICS of
other types may be specified but are
not required.
FacilitySiteAddress
LocationAddresslsReadOnly
New item only accessible by Inventory
Developers
FacilitySiteAddress
LocalitylsReadOnly
New item only accessible by Inventory
Developers
FacilitySiteAddress
PostalCodelsReadOnly
New item only accessible by Inventory
Developers
FacilitySiteGeographic
Coordinates
GeographicCoordinatelsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
GeographicCoordinates
MidPoint2LatitudeMeasure
New item for all users. Required for
new "2-Dimentional Fugitive" Release
Point Type. Not allowed otherwise.
Not used for FacilitySiteGeographic
Coordinates component. See "New
Fugitive Release Point Types" below for
more information.
ReleasePoint
GeographicCoordinates
MidPoint2LongitudeMeasure
New item for all users. Required for
new "2-Dimentional Fugitive" Release
Point Type. Not allowed otherwise.
Not used for FacilitySiteGeographic
Coordinates component. See "New
Fugitive Release Point Types" below for
more information.
Pg-1
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Component
Attribute
Notes
ReleasePoint
GeographicCoordinatelsReadOnly
New item only accessible by Inventory
GeographicCoordinates
Developers
EmissionsUnit
PermitStatusCode
New item for all users. This field is not
required.
EmissionsUnit
PermitStatusBeginYear
New item for all users. This field is not
required.
EmissionsUnit
PermitStatusEndYear
New item for all users. This field is not
required.
EmissionsUnit
DesignCapacitylsReadOnly
New item only accessible by Inventory
Developers
EmissionsUnit
UnitlsReadOnly
New item only accessible by Inventory
Developers
Unitldentification
UnitlDlsReadOnly
New item only accessible by Inventory
Developers
UnitRegulation
RegulationlsReadOnly
New item only accessible by Inventory
Developers
ProcessRegulation
RegulationlsReadOnly
New item only accessible by Inventory
Developers
EmissionsProcess
ProcessStatusCode
New item for all users. This field is
required.
EmissionsProcess
ProcessStatusCodeYear
New item for all users. This field is
conditionally required.
EmissionsProcess
ProcesslsReadOnly
New item only accessible by Inventory
Developers
EmissionsProcess
LastEmissionsYear
DELETED FOR EIS - This item will no
longer be available for EIS. The fields
ProcessStatusCode and
ProcessStatusCodeYear will replace the
function of this "LastEmissionsYear" for
a process.
Processldentification
EffectiveDate
New item for all users. This field is not
required.
Processldentification
EndDate
New item for all users. This field is not
required.
Processldentification
ProcesslDlsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
ReleasePointApportionment
New item for all users. This field is not
Apportionment
Pathldentifier
required. Will be discussed further in
Pathldentification
the "About Controls" portion of the
document.
ReleasePoint
ProgramSystemCode
New item for all users. This field is not
Apportionment
required.
Pathldentification
ReleasePoint
StackHeightlsReadOnly
New item only accessible by Inventory
Developers
Pg- 8
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Component
Attribute
Notes
ReleasePoint
StackDiameterlsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
ExitGasVelocitylsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
ExitGasFlowRatelsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
ExitGasTemperaturelsReadOnly
New item only accessible by Inventory
Developers
ReleasePoint
Identification
EffectiveDate
New item for all users. This field is not
required.
ReleasePoint
Identification
EndDate
New item for all users. This field is not
required.
ReleasePoint
Identification
ReleasePointlDlsReadOnly
New item only accessible by Inventory
Developers
Pg- 9
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
New Fugitive Release Point Types
From suggestions made by the Sectors, Policy, and Programs Division (SPPD), two new types of fugitive
types and a new "low flow vent" stack type will be available. This new method of defining fugitive
information is designed to be easier to collect, report, and interpret. These new stack types are:
Release Point Type Code
Release Point Type
Description
Release Point Type
7
Fugitive 3-Dimentional
Fugitive
8
Low Flow Vent
Stack
9
Fugitive 2-Dimentional
Fugitive
All other release point types that are currently available in EIS will continue to be available. However,
these new fugitive types of release points do require different types of information. See below for more
details.
Fugitive 3-Dimentational Fugitive Release Point Type
Fugitive three-dimensional source usually have multiple release vents. A few examples would be a
building with many wall and roof vents or an outdoor material storage pile. Required parameters are:
• side length (ft) [length and width are equal with three-dimensional sources]
• One set of coordinates (latitude and longitude) representing the center of the footprint of the
square
• height of the three-dimensional source
A three-dimensional shape with equal length
and width (Length = Width) and a specified
height. The Coordinates represent the
center of the footprint (or bottom face of
the shape.
Fugitive 2-Dimentational Fugitive Release Point Type
Fugitive two-dimensional source (>10sqft) is an emission release on one plane. For example, an
elongated roof vent or a wastewater holding pond. Required parameters are:
pg. 10
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
• Two sets of Coordinates. Pick the midpoints of two opposing sides of the source and enter the
coordinates for these two midpoints.
• A width is also required, which is the distance between the remaining two sides of the source
(that is, the width is perpendicular to the line between the two midpoints). For irregularly
shaped sources, first create a rectangle that best approximates the shape of the actual source,
then determine the parameters described above. Also, estimate the height where the release
occurs.
Width (ft)
Midpoint 1 - Latitude and Longitude
Note: Height of
release required
Midpoint 2 - Latitude and Longitude
Note: Height of
release required
\
Midpoint 1 - Latitude and
Longitude
Width (ft)
Midpoint 2 - Latitude and
Longitude
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
"Traditional" hugitive Release Point Type
You will be allowed to continue to report fugitive data as it has in the past (using release point type code
= "1"). This is an emission release on one plane. For example, an elongated roof vent or a wastewater
holding pond. Required parameters description:
• Although coordinates are optional, If you enter coordinates they wiil represent the southwest
corner of the release. The figure below shows examples of how fugitive area source rectangles
are created. The red dashed lines represent the coordinate plane with north towards the top.
The purple SW points to the southwest corner to show correct location of fugitive coordinates.
• The L and W represent fugitive length and width.
• The rotation of each angle is also shown. You may wish to review your coordinates and fugitive
areas in a GIS program or Google Earth to verify the accuracy.
NORTH
Angle = O0
Angle = 45
Angle = 45"
Angle = O"
Low Flow Vent
The new "Low Flow Vent" stack type is designed to provide a more descriptive alternative for vents that
have low flow associated with them. This is considered a "stack" type of parameter because the
information that you collect and what is required for this type of a release point are identical to regular
types of stack parameters.
pg. 12
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
About Controls
One of the new elements being introduced is how emissions control equipment is being tracked and
used within EIS. The new control modules perform the following functions:
1) Allow the same control to be used by many different processes. This is to reduce the number of
times that the control information needs to be entered.
2) Allow the ability to determine the configuration of how the controls are connected to each
other at the facility. This includes the ability to model controls that are connected in a series or
in parallel (the stream is split into multiple control streams).
3) Retain the ability to be able to calculate the percent emissions reduction for a given pollutant as
the emissions stream travels from the generating emissions process to the emissions release
point.
Control Components
In order to meet these needs, significant changes to what is stored within EIS were required. You will
notice in Figure 1 - CERS Components (page 4) there are several new components listed under the
FacilitySite component:
• FacilitySiteControls
Contains information about the type of control being defined at the facility. Each piece of
control equipment will need to be reported separately. The FacilitySiteControls component has
the following attributes:
Attribute
Notes
ControlMeasureCode
Required item. Must exist in the EIS Control Measures Code table.
ControlDescription
Optional
ControlCaptureEfficiency
Required.
Control Effectiveness
Optional, but will be set to 100 if not specified.
ControlUpgradeDate
Optional
ControlUpgradeDescription
Optional
ControlStatusCode
Required.
ControlStatusYear
Required if the ControlStatusCode is not "OP"
ControlNumberOperatingMonths
Optional. Must be an integer between 1 and 12 if specified
ControlStartDate
Optional.
ControlEndDate
Optional
ControlComment
Optional
ControllsReadOnly
May only be populated by Inventory Developers.
The FacilitySiteControls components have multiple sub-components:
o ControlPollutants - Provides a list of pollutants the piece of control equipment is
designed to control. At least 1 pollutant must be defined for each piece of control
equipment defined. This component has the following attributes:
pg. 13
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Attribute
Notes
PollutantCode
Required item. Must exist in the EIS Control Measures Code table.
PercentControlReductionEfficiency
Required.
o Controlldentification - The agency identifier used to track the piece of control
equipment. Each agency must provide an identifier for the piece of control equipment.
This component has the following attributes:
Attribute
Notes
Controlldentifier
Required.
ProgramSystemCode
Required. Must exist within the EIS Program System Code table.
EffectiveDate
Optional
EndDate
Optional
Alternative! DIsReadOnly
May only be populated by Inventory Developers.
• FacilitySiteControlPaths
The Control Path is used to define a configuration of controls used at the facility. The
component has the following attributes:
Attribute
Notes
PathName
Required.
PathDescription
Optional
PathlsReadOnly
May only be populated by Inventory Developers.
o PathDefinition - Determines how the FacilitySiteControls relate to each other at the
facility. The order of the controls must be specified. In cases where the emissions
stream splits, the percentage of the emissions stream must be specified. This splitting
of the emissions stream will cause the controls to be working in parallel until the stream
meet later in the path definition. Due to the potential complicated configurations of
controls, a given path definition may utilize site controls or other path definitions.
Please see the examples below for an illustration of how these situations are handled.
The component has the following attributes:
Attribute
Notes
SequenceNumber
Required. You may use the same SequenceNumber within a single
PathDefinition to indicate that the control stream has split into
multiple streams. The total of all AveragepercentApportionment
values with the same SequenceNumber must add to be 100.
AveragePercentEmissionsFlow
Required. Must be a value between 1 and 100. The sum of all
AveragepercentApportionment values having the same
SequenceNumber must equal 100.
pg. 14
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
o ControlPathldentification - The agency identifier used to track the given path. Each
agency must provide an identifier for each path to be defined. The component has the
following attributes:
Attribute
Notes
Pathldentifier
Required.
ProgramSystemCode
Required. Must exist within the EIS Program System Code table.
EffectiveDate
Optional
EndDate
Optional
Alternative! DIsReadOnly
May only be populated by Inventory Developers.
Once the FacilitySiteControls and FacilitySiteControlPaths have been defined, you must link the
completed FacilitySiteControlPaths to the ReleasePointApportionment item that utilizes the controls in
the given path.
Control Path Example 1 - Single Control
In the current EIS method of defining controls, over 90% of the control approaches have one control
within the control approach. This corresponds in the new model to say there is a single control within
the control path. Fortunately, these are the easiest types of scenarios to construct. For this example,
we will consider a facility with a thermal spray booth that performs plasma arc spraying of powdered
metal (source classification code (SCC) = "30904020"). This facility also has an annular ring filter control
device (EIS control device code = "64") with the following properties:
• State agency Control identifier = "SLTDNR - TORIT1"
• Control Measure = Annular ring filter (Code = 64)
• Control Description = "one Torit Cartridge filter"
• Percent Capture Efficiency = 100
• Percent Effectiveness (the percent of time the control device is operating) = 100
• Upgrade Date = [blank]
• Upgrade Description = [blank]
• Control Status Code = Operating (EIS Operational Code = "OP")
• Control Status Year = 2008
• Number of Operating Months = 12
• Start Date = January 1, 2008
• End Date = [blank]
• Control Comment = "Example 1 Test Control Device"
• Pollutants Controlled:
o PM25-PRI - 99.9% Reduction Efficiency
o PM10-PRI - 99.9% Reduction Efficiency
The control device is utilized by three different processes at the facility and the control device is
connected to one release point. See Figure 2 - Controls Example 1 for a visual representation of this
sample facility.
pg. 15
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
(SI
<—1
<—1
+¦>
c
*0
Q.
0J
W)
ro
_QJ
QJ
DC
LU
Sample Facility
EIS ID = 111
EIS Path 116
Agency ID: SLTDNR-PATH1
Path Description: Sample path to illustrate a
path utilizing a single control device
EIS Control 115 |~~
Agency ID: SLTDNR-TORIT1 1
<—w
Release Point Apportionment
Process Rel. Pt. Path ID % ADDrt
114 112 116 100
214 112 116 100
314 112 116 100
EIS Unit 113
Agency ID: SLTPSC-U1
Description: Spray Booth
1
EIS Process 114 EIS Process 214 EIS Process 314
Agency ID: SLTDNR-P1 Agency ID: SLTDNR-P2 Agency ID: SLTDNR-P3
SCC = 30904020 SCC = 30904020 SCC = 30904020
Normal Operation ES1-4 Normal Operation ES1-3 Normal Operation ES1-2
Figure 2 - Controls Example 1
EIS utilizes control paths to organize and determine how controls at the site are related to each other
and how they connect to processes and release points. This is accomplished in two steps:
1) Defining the Control Path. This defines which controls (or possibly other path definitions) are
within the path and, if there are multiple, how they related to each other within the path.
2) Associating the Control Path with a Release Point Apportionment record. This sets the
relationship between processes and release points utilizing a given control path. Please note
that the same path may be used by multiple Release Point Apportionment records.
Defining the Control Path
We will first consider defining the Control Path. For this example, we will need to create a path. It is
important to remember that paths and controls are properties of the facility and can be shared by all
components of the facility. For this example, the path will have the following characteristics:
pg. 16
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
• Agency Path ID: SLTDNR-PATH1
• Path Name (Required): PathExamplel
• Path Description: Sample path to illustrate a path utilizing a single control device
A path may consist of one or more controls that exist at the facility, one or more paths that exist as the
facility, or a combination of controls and paths that exist at the facility. For this first example, we only
need to assign one control to the path.
Site Path ID
Assigned Control ID
Assigned Path ID
Sequence #
Average %
Emissions Flow
SLTDNR-PATH1
SLTDNR-C1
[none]
1
100
Definitions:
Site Path ID: This is the identifier of the path which is being defined. You may reference this ID
by either the agency path identifier or by the EIS path identifier.
Assigned Control ID: The identifier of the control device that exists within the path. This may
be either the agency control identifier or the EIS control identifier.
Assigned Path ID: The identifier of the path that exists within the path. This may be either the
agency path identifier or the EIS path identifier.
Sequence #: Defines the order in which the assigned control or path are encountered by the
emissions flow from the process generating the emissions. The same sequence number may be
specified multiple times within the same path definition. If a path definition has the same
sequence number occurring more than once, this indicates the emissions stream has been split
between multiple devices.
Average % Emissions Flow: The percentage of the emissions flow that goes through the defined
control device or assigned path. For a given sequence number for a path definition, the sum of
all provided "Average % Emissions Flow" values must equal 100.
Associating the Control Path with a Release Point Apportionment
Once you have a Control Path defined, you can now associate the path with a release point
apportionment record using the new ReleasePointApportionmentPathldentification component. That
will associate a given process and release point with a control path.
Example 1 Sample XML
The way this information would be conveyed in a CERS submission is provided below. The following
assumptions:
1) The Facility, Unit, Release Point, and processes all exist and do not need to be defined.
2) The controls, path, and path definitions currently do not exist at the facility and need to be
defined.
3) The CERS header and closing XML tags are not provided in this example. This is intended to only
provide examples of the new components related to control information in EIS.
Pg- 17
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Defining the Controls for the Facility
The first component to define are the controls for the facility.
111
EIS
99123
64
one Torit Cartridge filter
100
100
OP
2008
12
2008-01 -01
Example 1 Test Control Device
PM25-PRI
99.9
PM10-PRI
99.9
TORIT 1
SLTDNR
Defining the Paths for the Facility
After the controls have been established, you may now set up the paths for the facility. Note that in the
defining the path, there is a reference to the control device we have just established.
PathExample1
Sample path to illustrate a path utilizing a single control device
1
100
TORIT1
SLTDNR
PATH1
SLTDNR
pg. 18
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Connect the Path to the Release Point Apportionment
U1
SLTDNR
P1
SLTDNR
100
112
EIS
PATH1
SLTDNR
This section can be repeated for the other processes (P2 and P3) that reference the exact same path.
Then the closing tags for the Emissionsilnit and FacilitySite can be closed:
Control Path Example 2 -Controls Connected in Series
Another very common situation is for a few controls to be connected in series. That is, the entire
emissions stream moves from one control device to another. For this example, we will consider a facility
with a generic chemical manufacturing process (SCC = 30199998). The emissions stream goes through 3
different control devices:
• First: Thermal Oxidizer
• Second: Baghouse
• Third: Wet Scrubber
Each of these controls (along with their agency identifiers and pollutants they cover) must be defined for
the facility site in a similar manner to what is described in Example 1. However, this example will
assume that all necessary controls have been defined (along with their ControlPollutant and
Controlldentification components). We will, however, fully define the path definitions needed to
describe this configuration. See "Figure 3" for a diagram of the facility being considered.
pg. 19
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Sample Facility
EIS ID = 211
EIS Unit 213
Agency ID: SLTPSC-U1
Description: Beta Rotary Calciner
EIS Process 414
Agency ID: SLTDNR-P3
SCC = 30199998
Process Emissions to
Controls
Release Point Apportionment
Process Rel.Pt. Path ID % Aoort
EIS Path 216
Agency ID: SLTDNR-PATH_EX2
Path Description: Sample path to illustrate a path utilizing multiple control devices connected in
series.
E IS Co ntrol 215 E IS Co ntrol 315 E IS Co ntrol 415
Agency ID: SLTDNR-C1 Agency ID: SLTDNR-C2 Agency ID: SLTDNR-C3
Control: Thermal Oxidizer^^^^. Control: Baghouse Control: Wet Scrubber
(code = 319) (code = 127) (code = 141)
Figure 3 - Controls Example 2
The path definition for this example will consist of multiple rows. Each row will represent one of the
controls in the diagram. The sequence number will reflect the order in which the control in
encountered.
Site Path ID
Assigned Control ID
Assigned Path ID
Sequence #
Average %
Emissions Flow
SLTDNR-PATH1
SLTDNR-C1
[none]
1
100
SLTDNR-PATH1
SLTDNR-C2
[none]
2
100
SLTDNR-PATH1
SLTDNR-C3
[none]
3
100
It should be noted that the sequence number provided does not have to be in order. You could, for
example, define the sequence number as "10", "20", "30" instead of "1", "2", "3". The only requirement
is for the values to be integers appearing in numerical order.
pg. 20
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Associating the Control Path with a Release Point Apportionment
Once you have a Control Path defined, you can now associate the path with a release point
apportionment record using the new ReleasePointApportionmentPathldentification component. This
step is identical as in "Example 1".
Example 2 Sample XML
In this example we assumed that the control definitions already existed for the facility for these three
control devices. Please refer to "Example 1" if you have questions as to how the facility control
information is defined. This is how to describe the path definitions for this example.
Defining the Paths for the Facility
After the controls have been established, you may now set up the paths for the facility.
211
EIS
PathExample2
Sample path to illustrate a path utilizing multiple control devices connected in se es<-/PathDescription^
1
100
C1
SLTDNR
2
100
C2
SLTDNR
3
100
C3
SLTDNR
PATH_EX2
SLTDNR
Connect the Path to the Release Point Apportionment
pg- 21
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
U1
SLTDNR
P3
SLTDNR
100
212
EIS
PATH_EX2
SLTDNR
Then the closing tags for the Emissionsilnit and FacilitySite can be closed:
Control Path Example 3 -Controls Connected in Parallel
This example is to illustrate the flexibility of the new control components. In this example, there will be
5 controls that exist at a facility. However, if you example "Figure 4" you will see that the emissions
stream splits and then later converges before being released. So for the portion of the time that the
stream is split, the control devices are considered operating in parallel. That is, part of the total
emissions stream moves through one series of control devices, and the other part of the emissions
stream moves through a separate series of control devices. For this example, we will consider a facility
with a wood fired boiler (SCC = 10200903). The emissions stream goes through 5 different control
devices:
• First: Cyclone
• Second: The stream is split
o 60% goes to an electrostatic precipitator
o 40% goes to a non-catalytic reduction followed by a screen
• Third: The streams meet up again and go through a baghouse
Each of these controls (along with their agency identifiers and pollutants they cover) must be defined for
the facility site in a similar manner to what is described in Example 1. However, this example will
assume that all necessary controls have been defined (along with their ControlPollutant and
Controlldentification components). We will, however, fully define the path definitions needed to
describe this configuration. See "Figure 4" for a diagram of the facility being considered.
Pg- 22
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Sample Facility
EIS ID = 311
EIS Unit 313
Agency ID: SLTPSC-U1
Description: Beta Rotary Calciner
EIS Process 514
Agency ID: SLTDNR-P3
SCC= 30199998
Process Emissions to
Controls
Release Point Apportionment
Process Rel. Pt. Path ID % Aoort
EIS Path 416
Agency ID: SLTDNR-PATH_EX3
Path Description: Outer path to illustrate parallel control configuration.
EIS Path 516
Agency ID: SLTDNR-SUBPATH_EX3
Path Description: Internal Path for "Path in Path" example.
40%
EIS Control 715
Agency ID: SLTDNR-C4
Control: Non-Catalytic
Reduction
(code =310)
EIS Control 515
Agency ID: SLTDNR-C1
Control: Cyclone
(code =121)
EIS Control 815
Agency ID: SLTDNR-C5
Control: Screen
(code = 157)
EIS Control 615
Agency ID: SLTDNR-C2
^—60%^- Control: Electrostatic
Precipitator
(code = 128)
EIS Control 915
Agency ID: SLTDNR-C3
Control: Baghouse
(code = 127)
Figure 4 - Controls Example 3
One important distinction here is to notice the inner path. This is needed because of controls SLTDNR-
C2 is working in parallel with both SLTDNR-C4 and SLTDNR-C5. When you define a split of the emissions
stream, you can only represent the percentage of the stream that follows one route or the other. So,
pg. 23
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
the way that you represent 1 item that contains multiple controls is by defining another path (in this
case path SLTDNR-SUBPATH_EX3) within the larger path (SLTDNR-PATH_EX3).
Defining the Paths for the Facility
First, create the inner path definition. Note that this looks like the Example 2 of creating a series of
controls. This is exactly what we are trying to accomplish. When you have parallel configurations of
controls, we need to evaluate them as a set of series of controls. Each of these sets will need to have
their own path definitions.
311
EIS
SUBPATH_EX3
lnternal path for "Path in Path" Example
1
100
C4
SLTDNR
2
100
C5
SLTDNR
SUBPATH_EX3
SLTDNR
Now create the outer path. Notice that there are 2 sequence "2" records, but their total of emissions
stream percentages equals 100%. Also notice that the definition of one of these series is referencing the
path we created above. In order to reference path definition within the main path, be sure the
component ControlPathDefinitionPathldentification is used.
MAINPATH_EX3
Outer path to illustrate parallel control configuration.
1
100
C1
SLTDNR
pg. 24
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
2
60
C2
SLTDNR
2
40
SUBPATH_EX3
SLTDNR
3
100
C3
SLTDNR
PATH_EX3
SLTDNR
Connect the Path to the Release Point Apportionment
U1
SLTDNR
P3
SLTDNR
100
112
EIS
PATH_EX3SLTDNR
pg. 25
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Summary of Controls
The intent of the changes made to the control information were to provide a method to fully describe
how the controls interacted with each other to provide a more complete picture of how the facility
operates. These modules also provide the ability to define one time for a facility and then reference
these components by any number of emissions processes (through the ReleasePointApportionment
component). Having identifiers on each of the components also allow for more targeted changes to the
definitions and descriptions of the components.
pg. 26
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Appendix A - Proposed CERS Attribute List
This section shows the proposed order of the columns (existing and new) as they will appear in the new
CERS Schema.
There are no changes in the following Facility Inventory components:
• AlternateFacilityName
• FacilitySiteAffiliation
• AffiliationOrganization
Other notes:
• Point and Non-Point Emissions
o Only Changed item: The SupplementalCalculationParameterValue of the
SupplementalCalcuationParameter component will be defined as a 5.5 float value
allowing for a minimum value of 0.00001 (for ultra-low sulfur),
o New Component: DeleteReportingPeriod
Only elements relevant to EIS are listed in the tables below:
FacilitySite Component
Data Element Name
Notes
FacilityCategoryCode
FacilitySiteName
FacilitySiteDescription
FacilitySourceTypeCode
New element - Only available to Inventory Developers
FacilitySiteStatusCode
FacilitySiteStatusCodeYear
HAPFacilityCategoryCode
New element - Only available to Inventory Developers
CoordinateTolerance
New element - Only available to Inventory Developers
FacilitySiteComment
FacilityNamelsReadOnly
New element - Only available to Inventory Developers
LocationlsReadOnly
New element - Only available to Inventory Developers
FacilityIdentification Component
Data Element Name
Notes
FacilitySiteldentifier
ProgramSystemCode
StateAndCountyFIPSCode
TribalCode
StateAndCountryFIPSCode
EffectiveDate
EndDate
Alternative! DIsReadOnly
New element - Only available to Inventory Developers
Pg- 27
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
FacilityNAICS Component
Data Element Name
Notes
NAICSCode
NAICSPrimarylndicator
Element now to be used by EIS. Must have 1 "Primary" type. May have
any number of other NAICS Indicator Codes ("SECONDARY", "TERTIARY")
NAICSIsReadOnly
New element - Only available to Inventory Developers
pg. 28
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
FacilitySiteAddress Component
Data Element Name
Notes
Location Add ressT ext
SupplementalLocationText
LocalityName
LocationAddressStateCode
LocationAddressPostalCode
LocationAddressCountryCode
AddressComment
LocationAddresslsReadOnly
New element - Only available to Inventory Developers
LocalitylsReadOnly
New element - Only available to Inventory Developers
PostalCodelsReadOnly
New element - Only available to Inventory Developers
FacilitySiteGeographicCoordiantes and ReleasePointGeographicCoordinates Components
Data Element Name
Notes
LatitudeMeasure
LongtitudeMeasure
MidPoint2LatitudeMeasure
New Element - Only valid for Release Point Coordinates and
only for release point types of "2-Dimentional Fugitive"
MidPoint2LongitudeMeasure
New Element - Only valid for Release Point Coordinates and
only for release point types of "2-Dimentional Fugitive"
SourceMapScaleNumber
HorizontalAccuracyMeasure
HorizontalAccuracyUnitOf Measure
HorizontalCollectionMethodCode
HorizontalReferenceDatumCode
GeographicReferecePointCode
DataCollectionDate
GeographicComment
VerticalMeasure
VerticalUnitOfMeasureCode
VerticalCollectionMethodCode
VerticalReferenceDatumCode
VerticalMethodCode
CoordinateDataSourceCode
GeometricTypeCode
GeographicCoordinatelsReadOnly
New element - Only available to Inventory Developers
pg. 29
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
FacilitySiteControls Component (New Component)
Data Element Name
Notes
ControlMeasureCode
New Item
ControlDescription
New Item
ControlCaptureEfficiency
New Item
Control Effectiveness
New Item
ControlUpgradeDate
New Item
ControlUpgradeDescription
New Item
ControlStatusCode
New Item
ControlStatusYear
New Item
ControlNumberOperatingMonths
New Item
ControlStartDate
New Item
ControlEndDate
New Item
ControlComment
New Item
ControllsReadOnly
New Item - Only available to Inventory Developers
FacilitySiteControls Component (New Component)
Data Element Name
Notes
ControlMeasureCode
New Item
ControlDescription
New Item
ControlCaptureEfficiency
New Item
Control Effectiveness
New Item
ControlUpgradeDate
New Item
ControlUpgradeDescription
New Item
ControlStatusCode
New Item
ControlStatusYear
New Item
ControlNumberOperatingMonths
New Item
ControlStartDate
New Item
ControlEndDate
New Item
ControlComment
New Item
ControllsReadOnly
New Item - Only available to Inventory Developers
ControlPollutants Component (New Component)
Data Element Name
Notes
PollutantCode
New Item
PercentControlReductionEfficiency
New Item
pg. 30
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Controlldentification Component (New Component)
Attribute
Notes
Controlldentifier
New Item
ProgramSystemCode
New Item
EffectiveDate
New Item
EndDate
New Item
Alternative! DIsReadOnly
New Item - May only be populated by Inventory Developers.
Controlldentification Component (New Component)
Attribute
Notes
Controlldentifier
New Item
ProgramSystemCode
New Item
EffectiveDate
New Item
EndDate
New Item
Alternative! DIsReadOnly
New Item - May only be populated by Inventory Developers.
FacilitySiteControlPaths Component (New Component)
Attribute
Notes
PathName
New Item
PathDescription
New Item
PathlsReadOnly
New Item - May only be populated by Inventory Developers.
ControlPathldentification Component (New Component)
Attribute
Notes
Pathldentifier
New item
ProgramSystemCode
New item
EffectiveDate
New item
EndDate
New item
Alternative! DIsReadOnly
New item - May only be populated by Inventory Developers.
ControlPathDefinition Component (New Component)
Attribute
Notes
SequenceNumber
New item
AveragePercentEmissionsFlow
New item
pg. 31
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
ControlPathDefinitionPathldentification Component (New Component)
Attribute
Notes
Pathldentifier
New item
ProgramSystemCode
New item
EffectiveDate
New item
EndDate
New item
ControlPathDefinitionControlldentification Component (New Component)
Attribute
Notes
Controlldentifier
New item
ProgramSystemCode
New item
EffectiveDate
New item
EndDate
New item
ReleasePoint Component
Attribute
Notes
ReleasePointTypeCode
ReleasePointDescription
ReleasePointStackHeightMeasure
ReleasePointStackHeightUnitOf
MeasureCode
ReleasePointStackDiameterMeasure
ReleasePointStackDiameterUnit
OfMeasureCode
ReleasePointExitGasVelocity
Measure
ReleasePointExitGasVelocity
UnitOf MeasureCode
ReleasePointExitGasFlowRate
Measure
ReleasePointExitGasFlowRate
UnitOf MeasureCode
ReleasePointExitGasTemperature
Measure
ReleasePointFenceLineDistance
Measure
ReleasePointFenceLineDistance
UnitOf MeasureCode
ReleasePointFugitiveHeightMeasure
ReleasePointFugitiveHeighUnitOf
MeasureCode
ReleasePointFugitiveWidthMeasure
ReleasePointFugitiveWidthUnitOf
MeasureCode
pg. 32
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Attribute
Notes
ReleasePointFugitiveLengthMeasure
ReleasePointFugitiveLenghtUnit
OfMeasureCode
ReleasePointFugitiveAngleMeasure
ReleasePointComment
ReleasePointStatusCode
ReleasePointStatusCodeYear
StackHeightlsReadOnly
New item - May only be populated by Inventory Developers.
StackDiameterlsReadOnly
New item - May only be populated by Inventory Developers.
ExitGasVelocitylsReadOnly
New item - May only be populated by Inventory Developers.
ExitGasFlowRatelsReadOnly
New item - May only be populated by Inventory Developers.
ExitGasTemperaturelsReadOnly
New item - May only be populated by Inventory Developers.
ReleasePointldentification Component
Attribute
Notes
ReleasePointldentifier
ProgramSystemCode
EffectiveDate
Item now available to EIS - Not Required
EndDate
Item now available to EIS - Not Required
ReleasePointlDlsReadOnly
New item - Only available to Inventory Developers
Emissionsllnit Component
Data Element Name
Notes
UnitDescription
UnitTypeCode
UnitDesignCapacity
UnitDesignCapacityUnitOf
MeasureCode
UnitStatusCode
UnitStatusCodeYear
UnitOperationDate
PermitStatusCode
New item. Not required.
PermitStatusBeginYear
New item. Only required if the PermitStatusCode <> "OP"
PermitStatusEndYear
New item. Only required if the PermitStatusCode <> "OP"
UnitComment
DesignCapacitylsReadOnly
New item - Only available to Inventory Developers
UnitlsReadOnly
New item - Only available to Inventory Developers
pg. 33
-------
Proposed Changed to the CERSfor the 2020 National Emissions Inventory
Unitldentification Component
Data Element Name
Notes
Unitldentifier
ProgramSystemCode
EffectiveDate
EndDate
UnitlDlsReadOnly
New item - Only available to Inventory Developers
UnitRegulation and ProcessRegulation Components
Data Element Name
Notes
RegulatoryCode
AgencyCodeText
RegulatoryStartYear
RegulationComment
RegulationlsReadOnly
New item - Only available to Inventory Developers
UnitEmissionsProcess Components
Data Element Name
Notes
SourceClassificationCode
AircraftEngineTypeCode
ProcessDescription
ProcessStatusCode
New item - Replaces function of "LastlnventoryYear"
ProcessStatusCodeYear
New item - Replaces function of "LastlnventoryYear"
ProcesslsReadOnly
New item - Only available to Inventory Developers
Process Identification Component
Data Element Name
Notes
Processldentifier
ProgramSystemCode
EffectiveDate
New item
EndDate
New item
ProcesslDlsReadOnly
New item - Only available to Inventory Developers
ReleasePointApportionmentPathldentification Component (New Component)
Data Element Name
Notes
Pathldentifier
New item
ProgramSystemCode
New item
pg. 34
------- |