Appendix 2: UIC Business Rules Requirements · Web viewRequired 1: Submission of the business...

UIC Business Rules Requirements (7/2/2010)Required 1: Submission of the business object or data element is mandatory. If a required object or element is missing (blank value), in an incorrect format, or has an unacceptable value, the data submission will be rejected by the data validation software and returned to the State/Region to be revised and re-submitted.

Required 2: Submission of the business object or data element is expected, but NOT mandatory. If a ‘Required 2’ object or element is missing (blank value), in an incorrect format, or has an unacceptable value, the data submission will be accepted. However, the validation software will strip the field of its value before it is accepted and produce a message to alert the submitting state/DI program that the expected data are missing or the value is not accepted.

There are 8 Inventory tables (of 18 tables totally) in the required-1 category: Facility, Contact, Permit, Permit Activity, Well, Well Type, Well Status, and Location. The other 10 tables are required- 2 category. Data collected from these tables is used to automate all UIC reporting requirements.

Data Type: Alphanumeric – letter, number, dash, and dot; Date – valid date in specified format; Numeric – number in specified format; String – letter, number and any special characters. Use Upper Case for values populated to each data field.

Name Definition Validation Type

Requirement Comment

1. Table WELL An injection well and its characteristics

Required 1 Each well must have one and only one facility, contact, and permit record. Geology information should be reported for Class I and specified wells (wells with *** in Data Dictionary.)

Each well must have one (at least) or more well status, well type, and location

Well ID (WELL_ID) Unique identification of Well table. The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique well (e.g. TXEQWDW366, …)

Required 1 (Primary key)

Field Type: AlphanumericField Length: 5-20

1. Unique among reported Well records.

2. First four characters in Primacy Agency code list (Appendix D to the Data Dictionary).

3. Unchanged from update to update.

1. The State/DI program should create the ID as described in the definition (e.g. DENR197590, TXEQWDW378).

2. CDX will reject the entire submission if this field is blank or fails to conform to the specifications on field type, length, and requirement 1 or 2. The request to fix errors and resubmit the file will be sent to the State/DI program.

3. Backend report will show the result of checking across submissions to ensure the consistency of Well ID throughout updates.

Aquifer Exemption (AQUI_EXEMPT)

Well injects into an exempted aquifer

Required 2 & Conditional

Field Type: AlphanumericField Length: 1

1. Required for non-Class V wells only.

2. See Appendix C to the Data Dictionary for Acceptable Values.

Class V wells may not inject into exempted aquifers but other Classes of wells may.

Total Depth(Class I and deep wells only) (TOTAL_DEPTH)

The vertical depth (in feet) from the surface to the bottom of injection well


Field Type: NumericField Length: Maximum 5

Required for Class I & deep wells

See Appendix B to the Data Dictionary; well type codes with asterisks indicate deep wells. Asterisks should not be included in the well codes for submission.

High Priority(Class V only) (HIGH_PRIORITY)

High priority Class V wells include all active motor vehicle waste disposal wells (MVWDWs) and large capacity cesspools regulated under the 1999 Class V rule, industrial wells, and all other Class V wells identified as high priority by State Directors



1. Required for Class V wells.2. See Appendix C to the Data

Dictionary for Acceptable Values.

A WARNING message will be generated if the field fails to conform to the specifications on data type, length, and acceptable values; its content will be replaced with a blank; however, the file still goes through EPA data system when the State/DI program submits it to CDX.

Contact ID (CONTACT_ID)

Unique identification of Contact table

Required 1 (Foreign key)


ID must exist in table Contact

1. A well must have contact information.2. Foreign Key IDs in child table must exist in

related parent table. Otherwise, the entire submission will be rejected.

Facility ID (FACILITY_ID)

Unique identification of Facility table



ID Must exist in table Facility

1. A well must have Facility information.2. Foreign Key IDs in child table must exist in


Geology ID (GEOLOGY_ID)

Unique identification for Geology record

1. Require 2 & conditional

2. Required 1 (Foreign key)


1. Required for Class I & deep wells (Require 2 & conditional)

2. If the non-blank value exists, that value must also be in the table Geology (Required 1)

1. A Class I or deep well should have Geology information. Otherwise, an alert message will be generated.

2. Foreign Key IDs in child table must exist in related parent table. Otherwise, the entire submission will be rejected.

Well Site (Class III & IV, and Class V storm water drainage wells only) (WELL_SITE)

Name of the area where many Class III, IV, or V (storm water drainage) injection wells are physically located or operated


Field Type: AlphanumericField Length: maximum 50

Required for Class III, IV and V storm water drainage wells.

1. This applies to Class III, IV and V storm water drainage wells. Class III and IV well site information must be provided for UIC grant allocation.

2. See comments on High Priority for validation process.

Permit ID (PERMIT_ID)

Unique identification of Permit table



Must exist in table Permit

1. A well must have permit information2. Foreign Key IDs in child table must exist in


Well State ID (W_STATE_ID)

The well identification assigned by primacy state or DI program

Required 1 Field Type: AlphanumericField Length: 1-50

Each value must be unique among reported Well records

State or DI program assigned Well ID. May be same as Well ID (the primary key) above if the program does not have ID for individual wells.

State / Tribe (DI Programs only) (STATE_or_TRIBE)

State (abbreviation) or tribal codes (American Indian or Alaska Native) regulated by EPA region (for DI programs)

Required 1 & conditional


1. Required for DI Programs only (last 2 characters of primacy agency code equal to ‘DI’)


For DI programs, the entire submission to CDX will be rejected if the field is blank or fails to conform to the specifications on field type, length, and acceptable values. A request to fix errors and resubmit the file will be sent to the submitting agency.

Well in a Source Water Area (WELL_IN_SWA)

The well location in relation to the boundary of the ground water based source water area (SWA) delineated by the primacy state under the State Source Water Assessment Program (SWAP).

Required 2 Field Type: AlphanumericField Length: 1

See Appendix C to the Data Dictionary for Acceptable Values.

See comments on High Priority field for validation process.

Well Name (WELL_NAME)

The name that designates the well

Required 2 Field Type: AlphanumericField Length: Maximum 80

1. The field can be populated with “NA” if the State/DI program has no facility information.

2. A WARNING message will be generated if the field fails to conform to the specifications on data type, length, and acceptable values; its content will be replaced with a blank ; however, the file still goes through EPA data system when the State/DI program submits it to CDX.

2. Table WELL STATUS

Operating status of a well Required 1 1. One or more well status records are reported for each well.

2. The well status date must be unique for those records with the same well ID

3. A historical data of well status (changed from one status to another) should be populated

1. Well Status information must be reported for every well record. If a well does not have any status information, the submission will be rejected.2. If the submitting agency has a well with multiple well statuses changed during the well history, the agency will map each well status to each EPA Well Status record. These records will have the same value of Well ID. Each record will have a unique date. So if a well changes different operating status in the same date, make sure to use a date before for the old well operating status and the current date for the new well operating status.

Status ID (STATUS_ID)

Unique identification of Well Status table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique well status (e.g. TXEQWDW369, …)

Required 1(Primary key)


1. Unique among reported Status records.

2. First four characters in Primacy Agency code list (Appendix D to the Data Dictionary)

CDX will reject the entire submission if this field is blank or fails to conform to the specifications on field type, length, and requirement 1 or 2. The State/DI will need to fix errors and resubmit the file to get thru the EPA database.

Well Status Date (STATUS_DATE)

Date that well status is determined

Required 1 Field Type: DateFormat: 8 (YYYYMMDD)

1. Date should be within the inclusive data range of 1901-01-01 through the current date.

2. If multiple well status records exist for one well, each well status date in every record must be unique.

See Permit Action Date

Well Operating Status (OPER_STATUS)

The current operating status of a well



See Authorized Status for validation process.

Well ID (WELL_ID) Unique identification of Well table Required 1 (Foreign key)


Well ID exists in table Well

1. This field must be populated. 2. Foreign Key IDs in child table must exist in


3. Table Well Type Well class and/or sub well class Required 1 1. One or more well type records are reported for each well.

2. The well type date must be unique for those records with the same well ID

3. A historical data of well type (changed from one type to another) should be populated

1. Well type information must be reported for all wells. If a well does not have well type information, the submission will be rejected.

2. If the submitting agency has a well with multiple well types changed during the well history, the agency will map each well type to each EPA Well Type record. These records will have the same value of Well ID. Each record will have a unique date. So if a well changes different types in the same date, make sure to use a date before for the old well type and the current date for the new well type.

Well Type ID (WELL_TYPE_ID)

Unique identification of Well Type table - The first four characters are the primacy agency code (appendix D). The rest is DI program or State’s choice (letters and numbers only) identifying unique well type (e.g. TXEQWDW369, …)



1. Unique among reported Well Type records.


See #2 under Well ID for validation process.

Well Type (WELL_TYPE)

Type of injection wells located at the listed facility.

Required 1 Field Type: AlphanumericField Length: 1 - 4

See Appendix B to the Data Dictionary for Acceptable Values.

(The first character is class number 1 – 5, except “CV” (converted to production))

1. If an injection well is changed to non-injection (i.e., production well), use “CV” (converted to production) as well type, and record well status change and the date of change in the Well Status table.

2. If an injection well is closed and re-opened as a different well type, and is recorded under the same well ID, report the change using this field and the Well Type Date field. In addition, report well status change and the date of change for the previous well type and the status and date for the current well type.

3. Submission will be failed if the value doesn’t match the acceptable list or is empty .

Well Type Date (WELL_TYPE_DATE)

Date that well type is determined. This field ONLY applies when the well changes from one well type to another well type (e.g., converted from injection to production).


Field Type: DateFormat: 8 (YYYYMMDD)


2. If multiple well type records exist for one well, each well type date in every record must be unique.

1. This date is required when the type of well is changed from one injection type to another or from injection to production. If there is no change in well type (i.e., only one well type record for a well), then this field may be blank.

2. If the requirements are not met, error messages will be generated and the entire submission will be rejected.

3. See Permit Action Date for additional information on date validation.

Well ID (WELL_ID) Unique identification of Well table.



Well ID exists in table Well

1. This field must be populated.2. Foreign Key IDs in child table must exist in


4. Table LOCATION

GPS location of the well Required 1 One location should be reported for each well

Submission will be rejected if no location information is reported for a well.

Location ID (LOCATION_ID)

Unique identification of Location table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique location (e.g. 03DI0000000000M00905, …)



1. Unique among reported Location records.



County (WELL_COUNTY)

The name of the U.S. county or county equivalent in which the regulated well is physically located.

Required 2 and conditional

Field Type: AlphanumericField Length: Maximum 35

Required for wells not located on tribal land.

1. If a well is on tribal land, the State/Tribe field in the well table would have a 3-letter code for the tribe. Otherwise, that field would have a 2-letter USPS State code.

2. See Facility Petition Status for validation process.

Accuracy Value & Unit (ACC_VALUE)

Quantitative measurement of the amount of deviation from true value in a measurement for latitude or longitude (estimate of error). It describes the correctness of the latitude/longitude measurement, in meters. Only the least accurate measurement is recorded, regardless whether it is for longitude or latitude

Required 2 Field Type: NumericField Length: Maximum 6

Unit will not be included in the data

Description Category (LOC_DESC)

Code representing the category of the feature referenced by the latitude and longitude.


See Appendix A to the Data Dictionary for list of acceptable values

This field is also known as reference point in EPA data standard and other databases.

Horizontal Datum (HORIZ_DATUM)

Code representing the reference standard for three dimensional and horizontal positioning established by the U.S. National Geodetic Survey (NGS) and other bodies



1. Applies to lat/long data obtained via GPS method only (Method of Collection is equal to ‘GPS’);

2. See Appendix A to the Data Dictionary for list of acceptable values

See comments on High Priority in the Well table for validation process.

Method of Collection (METHOD)

Code representing the method used to determine the latitude/longitude. This represents the primary source of the data.



1. Required if latitude/longitude fields are populated.



Point-Line-Area (POINT_LINE_AREA)

Code representing the value indicating whether the latitude and longitude coordinates represent a point, multiple points on a line, or an area.






Source Scale (SOURCE_SCALE)

Code representing the scale of the map used to determine the latitude and longitude coordinates.






Well ID (WELL_ID) Unique identification of Well table Required 1 (Foreign key)


ID Must exist in table Well



Well Latitude (WELL_LAT)

Coordinate representation indicating a location on the surface of the earth, using the earth's Equator as the origin, reported in decimal format. If an area permit is being requested, give the latitude and longitude of the approximate center of the area.

Required 2 Field Type: NumericFormat: 10 (±DD.dddddd)

1. The latitude shall be between -90.000000 and +90.000000, inclusive. [or: between 0 and +90.000000]

2. If the value is positive, there should be no plus sign (+) in front of the value.

The data format is for XML data transfer, not for data storage in databases. (For database, the format may be Decimal (8, 6)).

Well Longitude (WELL_LONG)

Coordinate representation indicating a location on the surface of the earth, using the Prime Meridian (Greenwich, England) as the origin, reported in decimal format. If an area permit is being requested, give the latitude and longitude of the approximate center of the area.

Required 2 Field Type: NumericFormat: 11(±DDD.dddddd)

1. The longitude shall be between -180.000000 and +179.999999, inclusive.

2. If the value is positive, there should be no plus sign (+) in front of the value.

The data format is for XML data transfer, not for data storage in databases. (For database, the format may be Decimal (9, 6)).

5. Table PERMIT Current authorization for the injection

Required 1 Each well must have one Permit record

Report the current authorization for a well to inject. This could be a new permit (i.e., IP, AP, GP, EP, OP) or a rule authorized (i.e., RA). If a well is identified without an authorization to inject, select the value NO


Unique identification of Permit table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique permit (e.g. 04DI0000000000WDW366)



1. Unique among reported Permit records.


3. Unchanged from update to update

See #2 and #3 under Well ID for validation process.

Number of AOR wells (AOR_WELL)

Number of wells identified in area of review (AOR) requiring corrective action

Required 2 and Conditional

Field Type: NumericField Length: Maximum 6

Required for Class I and IIAuthorized Status (AUT_STATUS)

Identification of whether well is permitted or rule authorized. If the well is permitted, the acceptable authorization types are individual, area, general, or emergency permits.



The entire submission to CDX will be rejected if the field is blank or fails to conform to the specifications on field type, length, and acceptable values. A request to fix errors and resubmit the file will be sent to the State/DI program.

Ownership Type (OWNERSHIP_TYPE)

Type of ownership for a UIC well Required 2 Field Type: AlphanumericField Length: 2

See Appendix C to the Data Dictionary for Acceptable Values

Permit / Rule Authorized ID Assigned (P_STATE_ID)

Identification assigned by DI program or primacy state to permitted or rule authorized well


Unique among reported Permit records

See Well State ID for validation process.

Submission Date (SUBMISSION_DATE)

Date that State/DI programs update and submit data to National UIC database system


This is the date that a UIC program actually uploads the xml file to CDX. This field should be blank in the submission file. CDX will submit the file to UIC node with a header which includes the date the program submitted the file (e.g., 2006-11-08). Or, the date will be included in the file name.

6. Table PERMIT ACTIVITY

Historical activities for permit (authorization to inject) records


1. One or more permit activity records are reported for each permit if the permit authorization status field has any permit code (i.e., IP, AP, EP, GP, OP)

2. No duplicate-by-data (record must be unique without Activity ID)

2. The entire submission will be rejected if the requirements are not met.

3. Requirements for individual fields apply only when permit activity information is reported.

4. Multiple fields uniqueness will be checked when data is loaded into the National UIC Database.

Activity ID (ACTIVITY_ID)

Unique identification of Permit Activity table- The first four characters are primacy agency code (Appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique permit activity (e.g. TXRC0000000000WDW567)

Required 1 (Primary Key)


1. Unique among reported Activity records.



Permit Action Type (ACT_TYPE)

Type of permit action or authorization by rule




Permit Action Date (ACT_DATE)

The calendar date corresponding to each acceptable value of Permit Action Type includes:

- Application Date for Permit Issuance: Date of receipt of an application by state or DI program for permit issued

- Application Date for Major Permit Modification: Date of receipt of an application by the state or DI program for major permit modification

- Permit Issued Date: Date of signature (approval) by State/DI program official for the issuance/denial/ withdrawal of permit.

- Permit Denied/Withdrawn Date: Date of signature by state/DI program official for the denial/withdrawal of permit.

- Approved Major Permit Modification Date: Approval date of a major permit modification. This is a date where an approved major modification requires a complete technical review, public notification or review, and a final decision document signed by the regulating authority.

- File Review Date: Date of rule-authorized file review to determine whether the well is in compliance with UIC regulatory requirements



1. The entire submission to CDX will be rejected if the field is blank or fails to conform to the specifications on field type, length, and date range. The request to fix errors and resubmit the file will be sent to the State/DI program.

2. The date format is for XML data transfer, not for date storage in databases.


Unique identification of Permit table



Must exist in table Permit



7. Table FACILITY Facility information of the well Required 1 Facility information must be reported for all wells

1. If there is no facility information (e.g., Class II wells), a facility record still needs to be created for submission and populated as specified.

2. See Facility ID in table Well for validation information.


Unique identification of the Facility table - The first four characters are primacy agency code (Appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique facility (e.g. DENR0000197590)



1. Unique among reported facility records.

2. First four characters in Primacy Agency code list (Appendix D to the Data Dictionary).

3. Unchanged from update to update.

See comments under Well ID for validation process

If Facility ID exists for a “no well” inspection type, it should have NO value of well_ID in the Well table

Facility City (FAC_CITY)

The name of the city, town, or village where the facility is located.



4. An alert message will be generated if the field is blank. If the field fails to conform to the data type and length, its content will be replaced with a blank field; however, the file still goes through the EPA data system when the State/DI program submits it to CDX.

Facility Name (FAC_NAME)

The public or commercial name of a facility site (i.e., the full name that commonly appears on invoices, signs, or other business documents, or as assigned by the state when the name is ambiguous).



2. The entire submission to CDX will be rejected if the field is blank or fails to conform to the specifications on data field type and length. The request to fix errors and resubmit the file will be sent to the State/DI program.

Facility Petition Status (Class I) (PETIT_STAT)

Status of review of no-migration petition (this is a technical demonstration required before Class I hazardous waste injection facilities may begin operating)



1. Required for facilities with a Class I Haz well (Well Type is equal to ‘1H’).


See validation comments in High Priority field of Well table

Facility State (FAC_STATE)

The U.S. Postal Service abbreviation that represents the state


See Appendix C to the Data Dictionary for Acceptable Values

An alert message will be generated if the field is blank. If the field fails to conform to the data type, length, and acceptable values, its content will be replaced with a blank field; however, the file still goes through EPA data system when the State/DI program submits it to CDX.

Facility State ID (F_STATE_ID)

Facility identification assigned by direct implementation (DI) program or primacy program


1. Unique among reported facility records within a Primacy Agency code

2. Consistency required for a combination between FACILITY_ID and F_STATE_ID on each submission

1. State or DI program assigned Facility ID. May be same as Facility ID above if the program has no Facility information.

2. The entire submission to CDX will be rejected if the field is blank or fails to conform to the specifications on field type, length and uniqueness. A request to fix errors and resubmit the file will be sent to the State/DI program.

Facility Street Address (FAC_STREET)

The address that describes the physical (geographic) location of the main entrance of a facility site, including urban-style street address or rural address, well field entrance, etc..

Required 1 Field Type: StringField Length: 1-150

1. The field can be populated with a “fire address” (i.e., for emergency responders) or “NA” if State/DI has no facility info.

2. See #2 under Facility Name for validation process.

Facility Type (Class I only) (FAC_TYPE)

Class I well waste is disposed in either of two types of facilities: (1) Commercial- where the waste is generated offsite and transported to the disposal facility, or (2) Non-commercial-where the waste is generated onsite and disposed there also.



1. Required for facilities with a Class I well.


See Facility Petition Status for validation process.

North American Industry Classification System Code (NAICS_CODE)

The NAICS code that represents a subdivision of an industry that accommodates user needs in the United States (6-digits)-- (Only primary code)


1. Higher-level SIC and NAICS codes acceptable but as much detail as possible is preferred.

2. See #2 under Facility City for validation process.

Standard Industrial Classification Code (SIC_CODE)

The code that represents the economic activity of a company. (4-digits) -- (only the primary code)


Can be empty if NAICS_Code is populated

Facility Zip Code (FAC_ZIP)

The combination of the 5-digit Zone Improvement Plan (ZIP) code and the four-digit extension code (if available) that represents the geographic segment that is a subunit of the ZIP Code, assigned by the U.S. Postal Service to a geographic location.


See #2 under Facility Name for validation process.

8. Table CONTACT

A contact for a well Required 1 Each well must have one Contact

See Contact ID in table Well for validation.

Contact ID (CONTACT_ID)

Unique identification of Contact table - The first four characters are primacy agency code (Appendix D to the Data Dictionary). The rest is DI program or State’s choice (letter and numbers only) identifying unique Contact for a well (e.g. NMNR30005003490000, …)



1. Unique among reported contact records.



Contact Phone (CON_PHONE)

The phone number of a contact for a well.


See #2 under Facility City for validation process.

Contact Name (CON_NAME)

The legal and complete name of a contact person (including first name, middle name or initial, and surname) for the well.



Contact City (CON_CITY)

The name of the city, town, or village of the contact for a well.

Required 2 Field Type: StringField Length: Maximum 30


Contact State (CON_STATE)

The name of the state where the contact is located or the name of the country, if outside the U.S.

Required 2 Field Type: AlphanumericField Length: maximum 50


Contact Street (CON_STREET)

The street address of the contact for a well. This can be a physical location or a mailing address.



Contact Zip (CON_ZIP)

The combination of the 5-digit Zone Improvement Plan (ZIP) code and the four-digit extension code (if available) that represents the geographic segment that is a subunit of the ZIP Code, assigned by the U.S. Postal Service to a geographic location to facilitate mail delivery; or the postal zone specific to the country, other than the U.S., where the mail is delivered.



9. Table INSPECTION:

Historical data of inspections. Inspection could be for a well or a facility where no well is found

1. Zero or more inspection records are reported for each well or facility record.

2. For facility inspections, the facility should have NO injection wells associated with it.

3. Inspection Date, Type, and Well ID/Facility ID together should not be the same for any two or more inspection records

1. Inspections are related to either a facility or well record. Either value of Well ID or Facility ID is populated and can’t be both populated.


Inspection ID (INSPECTION_ID)

The unique identification of Inspection table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique inspection (e.g. WYEQ00000566, …)



1. Unique among reported Inspection records.

2. First four characters in Primacy Agency code list (see Appendix D to the Data Dictionary)


Assistance (ASSISTANCE)

Compliance assistance provided by the inspector based on national policy:

-- General Assistance: involves distributing prepared information on regulatory compliance, P2 or other written materials/websites

-- Site-specific Assistance: involves on-site assistance by the inspector to support actions taken to address deficiencies



1. Required for DI programs (Last 2 characters of primacy agency code equal to ‘DI’)

2. See Appendix C to the Data Dictionary for list of acceptable values

This information is required for DI programs only, but primacy states may report as well.

Deficiency (DEFICIENCY)

Potential violations found by EPA inspector during inspection





This information is required for DI programs only, but primacy states may report as well.

Inspection Date (INS_DATE)

The date inspection action was completed


Date should be within the inclusive data range of 1901-01-01 through the current date.

See Permit Action Date for validation process

ICIS Compliance Monitoring Action Reason (DI Programs only) (ICIS_REASON)

The reason for performing a Compliance Monitoring action.Agency Priority: The compliance monitoring action was performed in furtherance of a priority or initiative of the Compliance Monitoring Agency or a partner agency.

Core Program: The compliance monitoring action was performed as part of the Compliance Monitoring Agency's core programmatic activities

Selected Monitoring Action: The Compliance Monitoring Agency selected the facility or regulated entity for compliance monitoring in response to a referral from another unit.




2. See Appendix C to the Data Dictionary for list of acceptable values.

This information is required for DI programs only.

ICIS Compliance Monitoring Type (DI Programs only) (ICIS_TYPE)

Type of Compliance Monitoring taken by a regulatory Agency



Same as above


ICIS Compliance Activity Type (DI Programs only) (ICIS_ACT_TYPE)

Type of compliance activity taken by a regulatory agency.



Same as above


ICIS MOA Priorities (DI Programs only) (ICIS_MOA_PRIORITY)

The name of Memorandum of Agreement (MOA) associated with the activity



Required for DI programs (Last 2 characters of primacy agency code equal to ‘DI’)


ICIS Regional Priorities (DI Programs only) (ICIS_REG_PRIORITY)

The name of regional priority associated with the activity



Required for DI programs (Last 2 characters of primacy agency code equal to ‘DI’)


Inspection Type (INS_TYPE)

The type of inspection action that was conducted


See Appendix C to the Data dictionary for list of acceptable values

1. Use ‘No Well’ type for facility inspections that found no wells.

2. See Authorized Status for validation process.

Well ID (WELL_ID) Unique identification of Well table Required 1 & conditional (Foreign Key)


1. ID must exist in table Well.2. Only exists when Facility

ID is blank

1. All inspections must be tied to a well and not a facility unless a facility has no wells found during the inspection.



Unique identification of Facility table—This field ONLY applies for Class V “No Well” inspection

Required 1 & conditional (Foreign Key)


1. ID must exist in table Facility.

2. Only exists when Well ID is blank.

3. Only exits when Class V Inspection Type is ‘No Well”.

1. An inspection record may be tied to either a well record or a facility record. Inspections to facilities that have no wells should use this field (foreign key ID) to link to the facility inspected. The Well ID field above should be blank when this field is populated.


10. Table CORRECTION:

Corrective actions for deficiency found from an inspection

1. Only exists if inspection exists.

2. Zero or more mechanical integrity test records are reported for each well record.

1. Deficiencies found during an inspection may or may not have any corrective actions.

2. The requirements to individual fields apply only when corrective actions are reported.

Correction ID (CORRECTION_ID)

Unique identification of Correction table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique corrective action (e.g. 04DI00000139, …)



1. Unique among reported Correction records.



Corrective Action Type (CORACT_TYPE)

Type of actions taken to correct deficiencies


See Appendix C to the Data Dictionary for list of acceptable values

See Facility State for validation process.

Comments (COMMENTS)

Narrative description of actions taken by the facility or assistance to help the facility come into compliance



If Corrective Action Type is equal to ‘Other,’ then this field must be populated.

See validation comments in High Priority field of Well table

Inspection ID (INSPECTION_ID)

The unique identification of Inspection table



ID must exist in table Inspection

Corrective action must relate to an inspection.

11. Table (MI_TEST)

Historical data of mechanical integrity test

1. Zero or more mechanical integrity test records are reported for each well record.

2. MIT Date, Type, Result, and Well ID together must not be same for any two MIT records.

1. A well may or may not have any MITs.2. The requirements to individual fields apply only

when MIT information is reported.3. Multiple fields uniqueness will be checked when

data is loaded into the national UIC database.

Mechanical Integrity Test (MIT) ID (MIT_ID)

Unique identification of Mechanical Integrity Test table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique mechanical integrity test (e.g. 03DIVA000235, …)



1. Unique among reported MIT records.



MIT Date (MIT_DATE)

The date that mechanical integrity test was completed



See Permit Action Date for date validation process.

MIT Result (MIT_RESULT)

The result of Mechanical Integrity Test on that date (see above)




MIT Type (MIT_TYPE)

Type of mechanical integrity test Required 1 Field Type: AlphanumericField Length: 2



Remedial Action Date (RA_DATE)

The date (corresponding to Remedial Action Type) when a well that failed an MI test received successful remedial action

Required 1& Conditional


1. Must exist if Remedial Action type exists. 2. Date should be within the inclusive data range of the MIT Date through the current date.

1. Remedial Action date must be present if Remedial Action Type is present and the date should be no earlier than MIT date.


Remedial Action Type (RA_TYPE)

Type of successful remedial action that well has received on the remedial action date

Required 2 and Conditional


1. Required if MIT Result is ‘F’. 2. See Appendix C to the Data Dictionary for list of acceptable values.

1. If MIT test result is ‘F’ (‘Failure’), then a remedial action should be reported. If not reported, an alert message will be generated.

2. See Facility Petition Status for additional information on validation process.

Well ID (WELL_ID) Unique identification of Well table



Well ID must exist in table Well

1. This field must be populated. 2. Foreign Key IDs in child table must exist in


12. Table VIOLATION

Historical data of violation 1. Zero or more violation records are reported for each well or facility record.

2. Violation Date, Type, and Well ID/Facility ID together should not be same for any two violation records

1. Violation may be related to a facility or well record. The value of facility ID and well ID can’t both exist in the Violation record.


Violation ID (VIOLATION_ID)

The unique identification of Violation table. The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique violation (e.g. 08DI000366, …)



1. Unique among reported violation records


See #2 under Facility ID for validation process.

Contamination (CONTAMINATION)

Well in noncompliance has allegedly contaminated an underground source of drinking water (USDW) this year to date



See Facility City for validation process.

Endangering (ENDANGER)

A violation that results in the well potentially or actually endangering the USDW. The endangering fluid contaminant from the well is in violation of RCRA or SDWA or applicable regulations



See Facility City for validation process.

Violation Return to Compliance Date (RE_COMP_DATE)

The calendar date, determined by the Responsible Authority, on which the regulated entity actually returned to compliance with respect to the legal obligation that is the subject of the violation determined date.



2. Date should be on or after the Violation Date for the same record

1. Return to compliance date will be blank for wells that have not yet returned to compliance.

2. The return to compliance date should be no earlier than the violation date.


Violation Significant (SNC)

The indication whether or not the violation is in Significant Non-Compliance (SNC)



1. Must be ‘Y’ if Contamination is equal to ‘Y.’


1. If the contamination is ‘Y’, and this field is not ‘Y’, then an alert message will be generated, and the submission will still be accepted. [Should this field be populated as ‘Y’ by the software in this case?]

2. See Facility Petition Status for additional information on validation process.

Violation Date (VIO_DATE)

The calendar date the Responsible Authority determines that a regulated entity is in violation of a legally enforceable obligation.



See Permit Action Date for date validation.

Violation Type (VIO_TYPE)

The type of violation that is the subject of the Violation Date




Well ID (WELL_ID) Unique identification of Well table Required 1 & conditional (Foreign key)


1. ID must exist in table Well2. Only exist when Facility ID is blank

1. A violation record may be tied to either a well record or a facility record.



Unique identification of Facility table—This field ONLY applies for Class V violations at FACILITY level (not to an individual well)

Required 1 & conditional (foreign key)


1. ID must exist in table Facility2. Only exist when well ID is blank3. Violation type is not “UI, MI, IP, PA, OM” as in the appendix C of data model

1. A violation record may be tied to either a well record or a facility record. Violations of Unauthorized Injection (UI), Mechanical Integrity (MI), Injection Pressure (IP), Plugging and Abandonment (PA), and Operation and Maintenance (OM) should only happen at the well level, not at the facility level.


13. Table RESPONSE


One or more response record must exist for each enforcement record.

1. The Response table is a link table between the violation and enforcement tables.

2. The submission will be rejected if an enforcement record has no related response record.

Enforcement Action ID (ENFORCEMENT_ID)

Unique identification for Enforcement table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique enforcement action (e.g. 08DI000766, …)

Required 1 (Composite Primary Key; Foreign key)


ID must exist in table Enforcement

This field uses a foreign key as a composite primary key. Foreign Key IDs in child table must exist in related parent table. Otherwise, the entire submission will be rejected.

Violation ID (VIOLATION_ID)

The unique identification of Violation table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique violation (e.g. 08DI000905, …)

Required 1 (Composite Primary Key; Foreign key)


ID must exist in table Violation

This field uses a foreign key as a composite primary key. Foreign Key IDs in child table must exist in related parent table. Otherwise, the entire submission will be rejected.

14. Table ENFORCEMENT

Historical data of enforcement action

All enforcement records must be related to one or more violation records.

1. Enforcement actions may or may not exist for a violation. The requirements to individual fields apply only when enforcement information is reported.

2. Enforcement action must be related to a violation through the Response table. See Response table for validation.

Enforcement Action ID (ENFORCEMENT_ID)

Unique identification for Enforcement table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique enforcement action (e.g. 08DI000566, …)



1. Unique among reported Enforcement records



Enforcement Action Date (ENF_DATE)

The calendar date the enforcement action was issued or filed




2. Date should be on or after related Violation Date

1. Submission will be rejected if the date is earlier than related violation date.


Enforcement Action Type (ENF_TYPE)

The type of action taken by the EPA or states



See Authorization Status for validation process.

15. Table GEOLOGY (Class I & other deep-wells injection)

Main geological data of a well Required 2 and conditional

Geology information should be reported for Class I and other deep wells

See Geology ID in table Well for validation.

Provide the main geology data if State/DI program has multiple geology data for a well

Geology ID (GEOLOGY_ID)

Unique identification for Geology table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique geology information (e.g. 04DI0000000000000566, …)



1. Unique among reported Geology records.

2. First four characters in Primacy Agency code list (see Appendix D to the Data Dictionary).


Name of Confining Zone (CZ_NAME)

Geologic formation name Required 2 & conditional



Top of Confining Zone (CZ_TOP)

The top of the geologic arresting layer that keeps injectate confined in the injection zone measured in feet below surface


Field Type: NumericField Length: Maximum 6 digits


Bottom of Confining Zone / Top of Injection Zone (CZ_BOTTOM)

The bottom of the geologic arresting layer that keeps injectate confined in the injection zoneOR: The top of the vertical dimension of the zone in which waste is injected.-- measured in feet below surface




Lithology of Confining Zone (CZ_LITHOLOGY)

Confining zone data in the form of a simple lithologic description of the formation




Name of Injection Zone (IZ_NAME)

Geologic formation name for injection zone




Bottom of Injection Zone (IZ_BOTTOM)

The bottom of the vertical dimension of the zone in which waste is injected, measured in feet below surface.




Lithology of Injection Zone (IZ_LITHOLOGY)

Injection zone data in the form of a simple lithologic description of the formation




Top of Injection Interval (INT_TOP)

The top of the vertical dimension of the specific layer(s) of the Injection




Bottom of Injection Interval (INT_BOTTOM)

The bottom of the vertical dimension of the specific layer(s) of the Injection Zone in which waste is authorized to be injected into, measured in feet below surface.




Injection Zone Permeability(IZ_PERMEABILITY)

The rate of diffusion of fluids (in this case liquid waste) under pressure through porous material (formation rock) that is measured in millidarcies (md.)




Injection Zone Porosity (IZ_POROSITY)

The percent of pore space the injection zone formation rock contains (measured in %).




USDW Depth (USDW_DEPTH)

The depth (in feet) to the base of the underground source of drinking water (USDW)




16. Table ENGINEERING (Class I & other deep-well injection)

Major engineering data of a well Required 2 and conditional

One or more Engineering records are reported for each Class I or other Deep well

If no engineering information provided for Class I and deep wells, submission will be accepted and an alert message will be generated.

Engineering ID (ENGINEERING_ID)

Unique identification of Engineering table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique engineering information (e.g. WYEQ00000543, …)

Required 1(Primary key)


1. Unique among reported Engineering records.



Max Flow Rate (MAX_RATE)

Maximum flow rate of injectate in the current quarter measured in gallons per minute.


Field Type: NumericField Length: 7,2


Onsite Injection (ON_INJECTION)

Permitted on-site injected volume measured in million gallon per month



Required for Class I & deep wellsOffsite Injection (OFF_INJECTION)

Permitted off-site injected volume measured in million gallon per month




Well ID (WELL_ID) Unique identification of an injection well



Well ID must exist in table Well.

Engineering information must relate to a Class I or other deep well. Otherwise, the entire submission will be rejected.

17. Table WASTE (Class I only)

Waste stream data of class 1 hazardous wells


1. One or more waste record is reported for each Class I well.

2. No duplicate waste by data (record must be unique without Waste ID)

1. If no waste information provided for Class I wells, submission will be accepted and an alert message will be generated.


Waste ID (WASTE_ID)

Unique identification of Waste table- The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique waste information (e.g. WYEQ00000793, …)



1. Unique among reported Waste records.



Waste Code (WASTE_CODE)

The RCRA or state waste code included when the constituent has been assigned a code



Required for Class I wells Waste Stream (WASTE_STREAM)

A classification of the waste stream that contains various constituents and waste codes in various concentrations. These are liquids waste approved to go down the well.



Required for Class I wells

Well ID (WELL_ID) Unique identification of an injection well



Well ID must exist in table Well.

1. Waste information must relate to a well.2. Foreign Key IDs in child table must exist in


18. Table CONSTITUENT (Class I only)

Components of waste stream including chemicals, etc.


1. One or more constituent records are reported for each waste record.

2. No duplicate constituent by data (record must be unique without Constituent ID)

1. If waste information is reported but no constituent information provided, submission will be accepted and an alert message will be generated.


Constituent ID (CONSTITUENT_ID)

Unique identification for Constituent table - The first four characters are primacy agency code (appendix D to the Data Dictionary). The rest is DI program or State’s choice (letters and numbers only) identifying unique constituent information (e.g. WYEQ0000000000000389, …)



1. Unique among reported Constituent records.



Concentration Value (CONCENTRATION)

The concentration of the individual waste constituent as reported by EPA Regional staff and/or state agency staff (measured in mg/l or pCi/l)



1. Must exist if constituent name is not blank 2. Required for Class I

Concentration Unit (UNIT)

Unit of measuring concentration (mg/l or pCi/l)



1. Must exist if concentration exists.

2. Required for Class I3. See Appendix C to the Data

Dictionary for list of acceptable values

Constituent Name (CONS_NAME)

The chemical name or a description of the waste, in accordance with EPA Chemical/Biological Internal Tracking Name (http://www.epa.gov/srs/)



Required for Class I

http://www.epa.gov/srs/

Waste ID (WASTE_ID)

Unique identification for Waste records



Waste ID must exist in table Waste

1. Constituent information must relate to a waste.2. Foreign Key IDs in child table must exist in


Appendix 2: UIC Business Rules Requirements · Web viewRequired 1: Submission of the business...

Documents

Transcript of Appendix 2: UIC Business Rules Requirements · Web viewRequired 1: Submission of the business...