Use the Regulation component to report that the emissions process is subject to a Federal, Tribal, State or Local regulation. Reporting of the Regulation component is voluntary but strongly encouraged by EPA. Regulatory information was reported in previous inventories only for MACT regulations. The capability has been extended in the EIS to include Federal criteria pollutant regulations and non-Federal regulations. Regulations are reported separately from the site controls that control emissions.
Regulations may be reported at either the emissions unit or the process level. Reporting at the unit level indicates that the regulation applies to all the processes at that unit. You cannot report the same regulation for both an emissions unit and a process for that unit. If the regulation is a non-Federal regulation, use AgencyCodeText to provide a description of the regulation. EPA encourages you to use standardized AgencyCodeText descriptions for each regulation within your jurisdiction, perhaps based on regulatory program descriptions or codes used in your local system.
Reporting multiple regulations. You may report one or more regulations to which your emissions unit is subject. However, each unit-regulation combination must be unique. That is, you cannot submit the same regulation for the same unit twice. As noted above, you cannot submit the same regulation for both a unit and a process for that unit.
Regulation affects multiple pollutants. It is assumed that a regulation applied to a process category may be directed at one or more pollutants. The regulated pollutants for the process category are identified in the rules themselves and are not reported.
Impact of incomplete information or critical errors. If there are critical errors, the data in the component will be rejected.
The code that describes the regulation applicable to the emissions unit activity or process.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 221 | Regulatory Code Present | The regulatory code is required when reporting the regulation component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 110 | Regulatory Code Valid | Must match value in code list. | Code | Critical |
| 111 | Agency Code Text for Regulations | If the regulatory code indicates it is a non Federal or a State program then the agency code text is required. | Conditional | Critical |
| 1269 | Process Level Regulation | Only regulations indicated to be reported at the process level should be reported at the process level. | Conditional | Critical |
Text describing the non-federal regulation applicable to the emissions unit or process.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 111 | Agency Code Text for Regulations | If the regulatory code indicates it is a non Federal or a State program then the agency code text is required. | Conditional | Critical |
| 247 | Agency Code Text for Regulations Data Type | Maximum allowable width of 100 characters. Longer submissions will be truncated. | Format | Critical |
The year in which the emissions unit or process became subject to the regulation.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1087 | Regulatory Start Year Relative Range | The regulatory start year must be less than or equal to the regulatory end year. | Range | Critical |
| 1090 | Regulatory Start Year Data Type | Year in the format of YYYY. | Format | Critical |
| 1091 | Regulatory Start Year Range | The regulatory start year must be between 1900 and 2050. | Range | Critical |
The year in which the emissions unit or process was no longer effected by the regulation.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1089 | Regulatory End Year Data Type | Year in the format of YYYY. | Format | Critical |
| 1093 | Regulatory End Year Range | The regulatory end year must be between 1900 and 2050. | Range | Critical |
Comments regarding the regulation.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 248 | Regulation Comment Data Type | Maximum allowable width of 400 characters. Longer submissions will be truncated. | Format | Warning |
An indicator defining that no data for the regulation may be changed.
User Role AccessibilityInventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1251 | Process Regulation Protected | Regulation Protected If the data in the EIS for emissions process regulation are protected, the data will not be stored. A request to unprotect the data can be made through the Gateway. | Conditional | Protected Warning |
| Number | Name | User Role Accessibility | Description | Type | Severity |
|---|---|---|---|---|---|
| 218 | Regulation Reported at Multiple Levels | SLT, Inventory Developer | A regulation should only be reported for either the emissions unit or the emissions process but not both for the same emissions unit. | Cardinality | Warning |
| 220 | Distinct Regulations for Emissions Process | Emissions Process SLT, Inventory Developer | An active regulation may only be reported once for an emissions process. | Cardinality | Critical |