An emissions process, characterized by an SCC, must be established for each activity that produces emissions at a unit at a facility site. Use the EmissionsProcess component to report the processes or activities that include: Identification; DeleteReportingPeriod; Reporting Period. The key element of the Emissions Process component is the SCC. Each facility site must have at least one unit and one emissions process defining the activity by SCC for that unit.
List of acceptable SCCs for point emissions. EPA has defined a list of SCCs which represent the expected processes and activities for point emissions. If you report SCCs that are not on the list of acceptable codes, they will be rejected. If you would like to request that an SCC be added for a particular point emissions process, submit a support request through the EIS Gateway. EPA will review and respond to this request within five business days.
Multiple processes for a unit. A unit may have more than one process, either historically (for different inventory cycles) or within the same inventory cycle. For example, a boiler could have two processes, one burning coal and one burning natural gas.
Completeness. There is no single list of processes and activities that would be applicable to a specific facility that can be used as a definitive check of submission completeness. Information may be provided as part of the quality assurance checks if expected SCCs or previously reported SCCs are not reported for a facility site.
Adding a new process to a unit. To add a new process to an emissions unit, provide the SCC, Program System Code, Process Identifier, Process Description (optional) Process Operating Status and Operating Status Year (if relevant), Release Point and an optional comment. The EIS will check to make sure that the SCC is not already in the EIS for that specific unit and, if not, will add the process to the EIS for that unit.
Updating process information. If you would like to update the information about a process that you know has already been reported for the unit, report the Process Identifier along with the SCC and all of the data elements in this component that you would like updated in the EIS. If you wish to completely change an SCC (such as moving from a generic SCC to a more detailed SCC) you will need to end the previous process by reporting a Process Operating Status and Process Operating Status Year for it, and then report the new process with the corrected SCC.
Impact of incomplete information or critical errors. If there are critical errors relating to the SCC, all data in the component will be rejected.
EPA Source Classification Code that identifies an emissions process.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
187 | SCC Present for Process | A source classification code is required when reporting the emissions process component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
90 | SCC Valid for all future years | SCC must exist in code list and have a null Last Inventory Year. | Code | Critical |
95 | SCC is scheduled to be retired | The SCC specified will not accept emissions for inventory years greater than {the last inventory year of the SCC}. | Present | Warning |
96 | Emissions Exist for Retired SCC | Emissions exist for this process for an inventory year beyond when the specified SCC is valid. | Present | Critical |
1789 | SCC in Correct Data Category | The SCC must match the Data Category provided in the Exchange Header. | Conditional | Critical |
1829 | SCC is Associated with Correct Process | The reported SCC must be associated with the reported emissions process identifier. | Conditional | Critical |
2324 | Active Point Processes in same county for special SCC. | Supplied NP data with SCC 2285002010 has active point processes in the same county as SCC 28500201. | Present | Warning |
Defines the type of emissions produced by Onroad and Nonroad sources. Used for Mobile sources only. Examples include exhaust, evaporative and tire wear.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
613 | Maximum allowable width of 400 characters. Longer submissions will be truncated. | Required when reporting the process component for nonroad. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
614 | Emissions Type Code Valid | Must match value in code list. | Code | Critical |
Identifies the combination of aircraft and engine type for airport emissions.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1484 | Aircraft Engine Type Code Valid | Must match active value in code list. The SCC assigned to the code must match the SCC of the process to which it is assigned. | Code | Critical |
2325 | Airport Uniqueness SCC - AETC conflict. | SCC and Aircraft Engine Type Code combination for supplied Airport Facility is not unique. | Present | Critical |
2316 | Aircraft Engine Type Code Present | Required when reporting the process component for aircraft. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
A text description of the emissions process.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
268 | Process Description Data Type | Maximum allowable width of 200 characters. Longer submissions will be truncated. | Format | Warning |
Code that identifies the operating status of the emissions process.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
186 | Process Status Code Present | The process operating status is required when reporting the EmissionsProcess component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
The year in which the process status became applicable.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
2392 | Emissions Process Status Code Year in Range | The year reported should be between 1900 to 2050. | Range | Critical |
2393 | Emissions Process Status Code and Year | If emissions process status code is not "Operating" (OP), the emissions process status code year must be reported. | Conditional | Critical |
2394 | Emissions Process Status Code Year Data Type | This element must be reported as an integer | Format | Critical |
Any comments regarding the emissions process.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
270 | Process Comment Data Type | Maximum allowable width of 400 characters. Longer submissions will be truncated. | Format | Warning |
Indicator that the process information cannot be changed.
User Role AccessibilityInventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
2354 | Emissions Process Protected | If the data in the EIS for emissions process is protected, the data will not be stored. A request to unprotect the data can be made through the Gateway. | Conditional | Critical |
Complex data type to define identifiers by which an entity is known or has been known.
Number | Name | Description | Type | Severity |
---|---|---|---|---|
Complex data type which identifies regulatory programs that are applicable to an emissions unit activity or process.
Number | Name | Description | Type | Severity |
---|---|---|---|---|
Complex data type which identifies the reporting period for which emissions and related activity data are submitted.
Number | Name | Description | Type | Severity |
---|---|---|---|---|
SLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1132 | Release Point Present for Process | A process must go to at least one release point. | Present | Critical |
1486 | Program System Code for Process Valid | Must match value in list of registered codes. | Code | Critical |
1809 | EIS Process Exists in Correct Unit | The reported EIS emissions process identifier matched in the EIS is associated with the reported emissions unit. | Conditional | Critical |
1930 | Pollutant Not Repeated Within Process | When reporting emissions, a pollutant may not reported multiple times under a single reporting period. | Cardinality | Critical |