This component is used to report release point identifiers to the EIS. These include both EIS and Agency identifiers, which are indicated by the Program System Code provided. If you intend to establish a new release point identifier or indicate that a release point identifier will no longer be used, you may either (1) submit this information using the ReleasePointIdentification components in your batch report or (2) update the identifier(s) using the EIS Gateway. Alternative identifiers for release points are also stored in the EIS.
Release Point Alternate identifiers. A release point may be known by additional identifiers within your local system(s). These alternate identifiers may be submitted for a release point but must be associated with your primary program system code. The same release point may have multiple alternate identifiers, but the release point must have an active identifier associated with the primary program system code as well as the submitted alternate identifiers.
Alternate identifiers will also be used to "report" alternate identifiers from other EPA systems, such as TRI or FRS. These identifiers are the responsibility of EPA and should not be reported by S/L/T submitters.
Impact of incomplete information or critical errors. If there are critical errors relating to the dates reported, the dates will not be stored; all other data in the record will be accepted.
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 |
|---|---|---|---|---|
| 99 | EIS Emission Release Point Identifier Exists | Must match an EIS emission release point identifier. | Conditional | Critical |
| 2370 | Release Point Level Agency ID Association Dependency | You may not edit existing Release Points that do not have an identifier for your Agency. In order for you to edit this Release Point, you must first have a Release Point ID associated with your Agency. | Conditional | Critical |
| 2372 | Agency Facility Identifier Not Found | You may not add a Release Point Identifier for this Agency because no Facility Identifier for this Agency was found at the associated Facility. | Conditional | Critical |
| 320 | EIS Release Point Identifier Matches Facility Site | The reported EIS release pointer identifier matched in the EIS is associated with the reported facility site. | Conditional | Critical |
| 1689 | Release Point Agency Identifier Unique | The combination of release point agency identifier and program system code must be unique within a facility. | Conditional | Critical |
| 253 | Identifier Data Type for Release Point Identification | Maximum allowable width of 20 characters. Longer submissions will be rejected. | Format | Critical |
| 1190 | Active Identifier per Program System Code for Release Point Identification Cardinality | A release point may only have one active identifier for each program system code. Active means the end date is null. Currently active identifiers with matching system codes will be automatically retired. | Cardinality | Warning |
| 1429 | Identifier Present for Release Point Identification | The identifier must be reported when reporting the release point identification component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 1434 | Release Point Alternate Identification Effective Date Present | The release point alternate identification effective date must be reported to be accepted. | Present | Critical |
| 1973 | Cardinality of Active Release Point Identifier in XML | Only one active release point identifier per program system code per release point is allowed in an XML submission. | Cardinality | Critical |
| 2089 | Release Point Identifier Exists for Identification | To use the release point identifier and program system code for identification, the release point identifier and system code combination must exist within the facility. | Conditional | Critical |
| 1296 | Release Point Alternate Identifier Protected | If the data in the EIS for identifier in release point alternate identification are protected, the data will not be stored. A request to unprotect the data can be made through the Gateway. | Conditional | Protected Warning |
| 150 | Duplicate Retired Alternate Release Point Identifier Exists for the same Program System Code | A duplicate retired Alternate Release Point Identifier exists for the same Program System Code. | Cardinality | Warning |
The code that represents the information management system which has responsibility for the data in a linked or interrelated information management system.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1430 | Program System Code Present for Release Point Identification | A program system code is required when reporting the release point identification component. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |
| 1431 | Program System Code Valid for Release Point Identification | Must match value in list of registered codes. | Code | Critical |
| 1190 | Active Identifier per Program System Code for Release Point Identification Cardinality | A release point may only have one active identifier for each program system code. Active means the end date is null. Currently active identifiers with matching system codes will be automatically retired. | Cardinality | Warning |
The date on which the identifier became effective.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 274 | Effective Date for Release Point Identification Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |
| 53 | Effective Date Range for Release Point Identification | The effective date range must be between 01/01/1900 to 12/31/2050. | Range | Critical |
The date on which the identifier is no longer applicable.
User Role AccessibilitySLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 367 | End Date for Release Point Identification Data Type | Date in the format of YYYY-MM-DD. | Format | Critical |
| 368 | End Date Range for Release Point Identification | The End Date range must be between 01/01/1900 to 12/31/2050. | Range | Critical |
| 52 | Effective Date and End Date Order for Release Point Identification | The effective date must be before the end date for a release point identification. | Range | Critical |
Indicator preventing the value of an alternate identifier from being modified.
User Role AccessibilityInventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1293 | Identifier Protected for Release Point Identification | If the data in the EIS for identifier in release point identification are protected, the data will not be stored. A request to unprotect the data can be made through the Gateway. | Conditional | Protected |
SLT, Inventory Developer
| Number | Name | Description | Type | Severity |
|---|---|---|---|---|
| 1432 | Emission Release Point Identifiers Present | Either the EIS emission release point identifier or the agency emission release point identifier is required when reporting the release point component. Both identifiers may be reported. The component and all dependent data will not be stored if there are missing required data. | Present | Critical |