The FacilitySiteControl Component contains information about the type of control being defined at the facility. Each piece of control equipment will need to be reported separately. The FacilitySiteControl component has the following attributes:
The FacilitySiteControl components have the multiple sub-components defined as follows:
Code that identifies the piece of equipment or practice that is used to reduce one or more pollutants.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
227 | Control Measure Code Present | Required when reporting the control measure component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
Description of the control device used at a facility.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1033 | Control Approach Description Data Type | Maximum allowable width of 200 characters. Longer submissions will be truncated. | Format | Warning |
An estimate of the portion of the reporting period's activity for which the control device was operating as designed (regardless of whether the control measure is due to rule or voluntary).
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
129 | Percent Effectiveness Present | The percent effectiveness must be reported when reporting the site control identification component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
241 | Percent Control Approach Effectiveness Data Type | This element must be reported as a decimal, reported with a maximum precision of 5.1. | Format | Critical |
116 | Percent Control Approach Effectiveness Range | Should be greater than or equal to 1, and less than or equal to 100.0. | Range | Critical |
The date on which the control device was most recently updated.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
275 | Upgrade Date for Site Control Identification Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |
77 | Upgrade Date Range | The upgrade date range must be between 01/01/1900 to 12/31/2050. | Range | Critical |
Description of the control update performed for the control at a facility.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1034 | Control Upgrade Description Data Type | Maximum allowable width of 200 characters. Longer submissions will be truncated. | Format | Warning |
Code that identifies the operating status of the facility site.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1032 | Control Status Code Dependency for Site Controls | A site control status may not be changed if the facility site operating status is "Temporarily Shutdown" (TS) or "Permanently Shutdown" (PS). | Conditional | Critical |
1099 | Site Control Status Code and Year | If the site control status code is not "Operating" (OP), the site control status code year should be reported. | Conditional | Critical |
1448 | Site Control Status Code at Shutdown Facility | A site control at a facility site with operating status of "Temporarily Shutdown" (TS) or "Permanently Shutdown" (PS) may not have a status of "Operating" (OP). | Conditional | Critical |
184 | Control Operating Status Present for Site Control Identification | The control operating status is required when reporting the site control component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
123 | Control Status Code for Site Control Valid | Must match value in list of registered codes. | Code | Critical |
The year in which the operating status became applicable.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1092 | Site Control Status Code Year Data Type | This element must be reported as an integer. | Format | Critical |
1099 | Site Control Status Code and Year | If the site control status code is not "Operating" (OP), the site control status code year should be reported. | Conditional | Critical |
76 | Site Control Status Code Year Range | The year reported should be between 1900 to 2050. | Range | Critical |
The number of months per year the control operates.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
245 | Site Control Number of Operating Months Range | The number of operating months should be between 1 and 12; inclusive. | Range | Critical |
260 | Site Control Number of Operating Months Data Type | This element must be reported as an integer. | Format | Critical |
Day the control was made effective.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
140 | Effective Date Range for Site Control Identification | The effective date range must be between 01/01/1900 and 12/31/2050. | Range | Critical |
141 | Effective Date and End Date Order for Site Control Identification | The effective date must be before the end date for a site control identification. | Range | Critical |
Day the control was no longer used.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
146 | End Date Range for Site Control Identification | The end date range must be between 01/01/1900 and 12/31/2050. | Range | Critical |
145 | End Date for Site Control Identification Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |
Additional information about the control.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
1035 | Control Comment Data Type | Maximum allowable width of 400 characters. Longer submissions will be truncated. | Format | Warning |
Indicator defining that the control description information may not be altered.
User Role AccessibilityInventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
189 | Site Control Protected | If the data in EIS for Site Control are protected, the data will not be stored. A request to unprotect the data can be made through Gateway. | Conditional | Protected Warning |
Complex data type to define identifiers by which an entity is known or has been known.
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|
2415 | Agency Facility Identifier Not Found When Adding Site Control Identifier | You may not add a Site Control Identifier because no Facility Identifier for this Agency was found at the associated Facility. | Conditional | Critical |
2416 | Site Control Level Agency ID Association Dependency | You may not edit existing Site Controls that do not have an identifier for your Agency. In order for you to edit this Site Control, this control must have an alternate control identifier associated with your Agency. | Conditional | Critical |
2418 | New Site Control Alternate Identifier - Agency Dependency | You may not add a Site Control Alternate Identifier for your Agency, because no Site Control Identifier is currently reported at this Site Control for your Agency. In order for you to add an Alternate Identifier for this Site Control, you must first have an existing Site Control ID associated with your Agency. | Conditional | Critical |
158 | Identifier Present for Site Control Alternate Identification | The identifier is required when reporting the site control alternate identification component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
Complex data type to provide information on the pollutants being controlled by a collection of control devices
User Role AccessibilitySLT, Inventory Developer
Number | Name | Description | Type | Severity |
---|---|---|---|---|