Appendix 2: UIC Business Rules Requirements
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 |
|Aquifer Exemption |Well injects into an exempted aquifer |Required 2 & |Field Type: Alphanumeric |Class V wells may not inject into exempted aquifers but other |
|(AQUI_EXEMPT) | |Conditional |Field Length: 1 |Classes of wells may. |
| | | | | |
| | | |Required for non-Class V wells only. | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values. | |
|Total Depth |The vertical depth (in feet) from the |Required 2 & |Field Type: Numeric |See Appendix B to the Data Dictionary; well type codes with |
|(Class I and deep wells |surface to the bottom of injection well |Conditional |Field Length: Maximum 5 |asterisks indicate deep wells. Asterisks should not be included |
|only) (TOTAL_DEPTH) | | | |in the well codes for submission. |
| | | |Required for Class I & deep wells | |
|High Priority |High priority Class V wells include all |Required 2 & |Field Type: Alphanumeric |A WARNING message will be generated if the field fails to conform |
|(Class V only) |active motor vehicle waste disposal wells |Conditional |Field Length: 1 |to the specifications on data type, length, and acceptable values;|
|(HIGH_PRIORITY) |(MVWDWs) and large capacity cesspools | | |its content will be replaced with a blank; however, the file still|
| |regulated under the 1999 Class V rule, | |Required for Class V wells. |goes through EPA data system when the State/DI program submits it |
| |industrial wells, and all other Class V | |See Appendix C to the Data Dictionary for |to CDX. |
| |wells identified as high priority by State| |Acceptable Values. | |
| |Directors | | | |
|Contact ID (CONTACT_ID) |Unique identification of Contact table |Required 1 (Foreign |Field Type: Alphanumeric |A well must have contact information. |
| | |key) |Field Length: 1-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |ID must exist in table Contact | |
|Facility ID (FACILITY_ID) |Unique identification of Facility table |Required 1 (Foreign |Field Type: Alphanumeric |A well must have Facility information. |
| | |key) |Field Length: 1-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |ID Must exist in table Facility | |
|Geology ID (GEOLOGY_ID) |Unique identification for Geology record |1. Require 2 & |Field Type: Alphanumeric |A Class I or deep well should have Geology information. |
| | |conditional |Field Length: 1-20 |Otherwise, an alert message will be generated. |
| | | | |Foreign Key IDs in child table must exist in related parent table.|
| | |2. Required 1 (Foreign |Required for Class I & deep wells (Require|Otherwise, the entire submission will be rejected. |
| | |key) |2 & conditional) | |
| | | |If the non-blank value exists, that value | |
| | | |must also be in the table Geology | |
| | | |(Required 1) | |
|Well Site (Class III & IV,|Name of the area where many Class III, IV,|Required 2 & |Field Type: Alphanumeric |This applies to Class III, IV and V storm water drainage wells. |
|and Class V storm water |or V (storm water drainage) injection |Conditional |Field Length: maximum 50 |Class III and IV well site information must be provided for UIC |
|drainage wells only) |wells are physically located or operated | | |grant allocation. |
|(WELL_SITE) | | |Required for Class III, IV and V storm |See comments on High Priority for validation process. |
| | | |water drainage wells. | |
|Permit ID (PERMIT_ID) |Unique identification of Permit table |Required 1 (Foreign |Field Type: Alphanumeric |A well must have permit information |
| | |key) |Field Length: 1-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Must exist in table Permit | |
|Well State ID (W_STATE_ID)|The well identification assigned by |Required 1 |Field Type: Alphanumeric |State or DI program assigned Well ID. May be same as Well ID (the |
| |primacy state or DI program | |Field Length: 1-50 |primary key) above if the program does not have ID for individual |
| | | | |wells. |
| | | |Each value must be unique among reported | |
| | | |Well records | |
|State / Tribe (DI Programs|State (abbreviation) or tribal codes |Required 1 & |Field Type: Alphanumeric |For DI programs, the entire submission to CDX will be rejected if |
|only) (STATE_or_TRIBE) |(American Indian or Alaska Native) |conditional |Field Length: 2-3 |the field is blank or fails to conform to the specifications on |
| |regulated by EPA region (for DI programs) | | |field type, length, and acceptable values. A request to fix |
| | | |Required for DI Programs only (last 2 |errors and resubmit the file will be sent to the submitting |
| | | |characters of primacy agency code equal to|agency. |
| | | |‘DI’) | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values. | |
|Well in a Source Water |The well location in relation to the |Required 2 |Field Type: Alphanumeric |See comments on High Priority field for validation process. |
|Area (WELL_IN_SWA) |boundary of the ground water based source | |Field Length: 1 | |
| |water area (SWA) delineated by the primacy| | | |
| |state under the State Source Water | |See Appendix C to the Data Dictionary for | |
| |Assessment Program (SWAP). | |Acceptable Values. | |
|Well Name (WELL_NAME) |The name that designates the well |Required 2 |Field Type: Alphanumeric |The field can be populated with “NA” if the State/DI program has |
| | | |Field Length: Maximum 80 |no facility information. |
| | | | |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 |One or more well status records are |1. Well Status information must be reported for every well record.|
| | | |reported for each well. |If a well does not have any status information, the submission |
| | | |The well status date must be unique for |will be rejected. |
| | | |those records with the same well ID |2. If the submitting agency has a well with multiple well statuses|
| | | |A historical data of well status (changed |changed during the well history, the agency will map each well |
| | | |from one status to another) should be |status to each EPA Well Status record. These records will have |
| | | |populated |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. |
| | | | | |
|Well Status Date |Date that well status is determined |Required 1 |Field Type: Date |See Permit Action Date |
|(STATUS_DATE) | | |Format: 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. | |
|Well Operating Status |The current operating status of a well |Required 1 |Field Type: Alphanumeric |See Authorized Status for validation process. |
|(OPER_STATUS) | | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values. | |
|Well ID (WELL_ID) |Unique identification of Well table |Required 1 (Foreign |Field Type: Alphanumeric |This field must be populated. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Well ID exists in table Well | |
|3. Table Well Type |Well class and/or sub well class |Required 1 |One or more well type records are reported|Well type information must be reported for all wells. If a well |
| | | |for each well. |does not have well type information, the submission will be |
| | | |The well type date must be unique for |rejected. |
| | | |those records with the same well ID |If the submitting agency has a well with multiple well types |
| | | |A historical data of well type (changed |changed during the well history, the agency will map each well |
| | | |from one type to another) should be |type to each EPA Well Type record. These records will have the |
| | | |populated |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 (WELL_TYPE) |Type of injection wells located at the |Required 1 |Field Type: Alphanumeric |If an injection well is changed to non-injection (i.e., production|
| |listed facility. | |Field Length: 1 - 4 |well), use “CV” (converted to production) as well type, and record|
| | | | |well status change and the date of change in the Well Status |
| | | |See Appendix B to the Data Dictionary for |table. |
| | | |Acceptable Values. |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 |
| | | |(The first character is class number 1 – |using this field and the Well Type Date field. In addition, |
| | | |5, except “CV” (converted to production)) |report well status change and the date of change for the previous |
| | | | |well type and the status and date for the current well type. |
| | | | |Submission will be failed if the value doesn’t match the |
| | | | |acceptable list or is empty . |
|Well Type Date |Date that well type is determined. This |Required 1 & |Field Type: Date |This date is required when the type of well is changed from one |
|(WELL_TYPE_DATE) |field ONLY applies when the well changes |conditional |Format: 8 (YYYYMMDD) |injection type to another or from injection to production. If |
| |from one well type to another well type | | |there is no change in well type (i.e., only one well type record |
| |(e.g., converted from injection to | |Date should be within the inclusive data |for a well), then this field may be blank. |
| |production). | |range of 1901-01-01 through the current |If the requirements are not met, error messages will be generated |
| | | |date. |and the entire submission will be rejected. |
| | | | |See Permit Action Date for additional information on date |
| | | |If multiple well type records exist for |validation. |
| | | |one well, each well type date in every | |
| | | |record must be unique. | |
|Well ID (WELL_ID) |Unique identification of Well table. |Required 1 (Foreign |Field Type: Alphanumeric |This field must be populated. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Well ID exists in table Well | |
|4. Table LOCATION |GPS location of the well |Required 1 |One location should be reported for each |Submission will be rejected if no location information is reported|
| | | |well |for a well. |
|County (WELL_COUNTY) |The name of the U.S. county or county |Required 2 and |Field Type: Alphanumeric |If a well is on tribal land, the State/Tribe field in the well |
| |equivalent in which the regulated well is |conditional |Field Length: Maximum 35 |table would have a 3-letter code for the tribe. Otherwise, that |
| |physically located. | | |field would have a 2-letter USPS State code. |
| | | |Required for wells not located on tribal |See Facility Petition Status for validation process. |
| | | |land. | |
|Accuracy Value & Unit |Quantitative measurement of the amount of |Required 2 |Field Type: Numeric |Unit will not be included in the data |
|(ACC_VALUE) |deviation from true value in a measurement| |Field Length: Maximum 6 | |
| |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 | | | |
|Description Category |Code representing the category of the |Required 2 |Field Type: Alphanumeric |This field is also known as reference point in EPA data standard |
|(LOC_DESC) |feature referenced by the latitude and | |Field Length: 3 |and other databases. |
| |longitude. | | | |
| | | |See Appendix A to the Data Dictionary for | |
| | | |list of acceptable values | |
|Horizontal Datum |Code representing the reference standard |Required 2 and |Field Type: Alphanumeric |See comments on High Priority in the Well table for validation |
|(HORIZ_DATUM) |for three dimensional and horizontal |conditional |Field Length: 3 |process. |
| |positioning established by the U.S. | | | |
| |National Geodetic Survey (NGS) and other | |Applies to lat/long data obtained via GPS | |
| |bodies | |method only (Method of Collection is equal| |
| | | |to ‘GPS’); | |
| | | |See Appendix A to the Data Dictionary for | |
| | | |list of acceptable values | |
|Method of Collection |Code representing the method used to |Required 2 and |Field Type: Alphanumeric |See comments on High Priority in the Well table for validation |
|(METHOD) |determine the latitude/longitude. This |conditional |Field Length: 3 |process. |
| |represents the primary source of the data.| | | |
| | | |Required if latitude/longitude fields are | |
| | | |populated. | |
| | | |See Appendix A to the Data Dictionary for | |
| | | |list of acceptable values | |
|Point-Line-Area |Code representing the value indicating |Required 2 & |Field Type: Alphanumeric |See comments on High Priority in the Well table for validation |
|(POINT_LINE_AREA) |whether the latitude and longitude |conditional |Field Length: 3 |process. |
| |coordinates represent a point, multiple | | | |
| |points on a line, or an area. | |Required if latitude/longitude fields are | |
| | | |populated. | |
| | | |See Appendix A to the Data Dictionary for | |
| | | |list of acceptable values | |
|Source Scale |Code representing the scale of the map |Required 2 and |Field Type: Alphanumeric |See comments on High Priority in the Well table for validation |
|(SOURCE_SCALE) |used to determine the latitude and |conditional |Field Length: 2 |process. |
| |longitude coordinates. | | | |
| | | |Required if latitude/longitude fields are | |
| | | |populated. | |
| | | |See Appendix A to the Data Dictionary for| |
| | | |list of acceptable values | |
|Well ID (WELL_ID) |Unique identification of Well table |Required 1 (Foreign |Field Type: Alphanumeric |This field must be populated. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |ID Must exist in table Well | |
|Well Latitude (WELL_LAT) |Coordinate representation indicating a |Required 2 |Field Type: Numeric |The data format is for XML data transfer, not for data storage in |
| |location on the surface of the earth, | |Format: 10 (±DD.dddddd) |databases. (For database, the format may be Decimal (8, 6)). |
| |using the earth's Equator as the origin, | | | |
| |reported in decimal format. If an area | |1. The latitude shall be between | |
| |permit is being requested, give the | |-90.000000 and +90.000000, inclusive. [or:| |
| |latitude and longitude of the approximate | |between 0 and +90.000000] | |
| |center of the area. | | | |
| | | |2. If the value is positive, there should | |
| | | |be no plus sign (+) in front of the value.| |
|Well Longitude (WELL_LONG)|Coordinate representation indicating a |Required 2 |Field Type: Numeric |The data format is for XML data transfer, not for data storage in |
| |location on the surface of the earth, | |Format: 11(±DDD.dddddd) |databases. (For database, the format may be Decimal (9, 6)). |
| |using the Prime Meridian (Greenwich, | | | |
| |England) as the origin, reported in | |1. The longitude shall be between | |
| |decimal format. If an area permit is being| |-180.000000 and +179.999999, inclusive. | |
| |requested, give the latitude and longitude| | | |
| |of the approximate center of the area. | |2. If the value is positive, there should | |
| | | |be no plus sign (+) in front of the value.| |
|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 |
|Number of AOR wells |Number of wells identified in area of |Required 2 and |Field Type: Numeric | |
|(AOR_WELL) |review (AOR) requiring corrective action |Conditional |Field Length: Maximum 6 | |
| | | | | |
| | | |Required for Class I and II | |
|Authorized Status |Identification of whether well is |Required 1 |Field Type: Alphanumeric |The entire submission to CDX will be rejected if the field is |
|(AUT_STATUS) |permitted or rule authorized. If the well| |Field Length: 2 |blank or fails to conform to the specifications on field type, |
| |is permitted, the acceptable authorization| | |length, and acceptable values. A request to fix errors and |
| |types are individual, area, general, or | |See Appendix C to the Data Dictionary for |resubmit the file will be sent to the State/DI program. |
| |emergency permits. | |Acceptable Values. | |
|Ownership Type |Type of ownership for a UIC well |Required 2 |Field Type: Alphanumeric | |
|(OWNERSHIP_TYPE) | | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values | |
|Permit / Rule Authorized |Identification assigned by DI program or |Required 1 |Field Type: Alphanumeric |See Well State ID for validation process. |
|ID Assigned (P_STATE_ID) |primacy state to permitted or rule | |Field Length: 1-50 | |
| |authorized well | | | |
| | | |Unique among reported Permit records | |
|Submission Date |Date that State/DI programs update and | |Field Type: Date |This is the date that a UIC program actually uploads the xml file |
|(SUBMISSION_DATE) |submit data to National UIC database | |Format: 8 (YYYYMMDD) |to CDX. This field should be blank in the submission file. CDX |
| |system | | |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 |Required 1 and |One or more permit activity records are |The entire submission will be rejected if the requirements are not|
| |(authorization to inject) records |conditional |reported for each permit if the permit |met. |
| | | |authorization status field has any permit |Requirements for individual fields apply only when permit activity|
| | | |code (i.e., IP, AP, EP, GP, OP) |information is reported. |
| | | |No duplicate-by-data (record must be |Multiple fields uniqueness will be checked when data is loaded |
| | | |unique without Activity ID) |into the National UIC Database. |
|Permit Action Type |Type of permit action or authorization by |Required 1 |Field Type: Alphanumeric |See Authorized Status for validation process. |
|(ACT_TYPE) |rule | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values. | |
|Permit Action Date |The calendar date corresponding to each |Required 1 |Field Type: Date |The entire submission to CDX will be rejected if the field is |
|(ACT_DATE) |acceptable value of Permit Action Type | |Format: 8 (YYYYMMDD) |blank or fails to conform to the specifications on field type, |
| |includes: | | |length, and date range. The request to fix errors and resubmit |
| | | |Date should be within the inclusive data |the file will be sent to the State/DI program. |
| |- Application Date for Permit Issuance: | |range of 1901-01-01 through the current |The date format is for XML data transfer, not for date storage in |
| |Date of receipt of an application by state| |date. |databases. |
| |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 | | | |
|Permit ID (PERMIT_ID) |Unique identification of Permit table |Required 1 (Foreign |Field Type: Alphanumeric |This field must be populated. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Must exist in table Permit | |
|7. Table FACILITY |Facility information of the well |Required 1 |Facility information must be reported for |If there is no facility information (e.g., Class II wells), a |
| | | |all wells |facility record still needs to be created for submission and |
| | | | |populated as specified. |
| | | | |See Facility ID in table Well for validation information. |
|Facility City (FAC_CITY) |The name of the city, town, or village |Required 2 |Field Type: Alphanumeric |The field can be populated with “NA” if the State/DI program has |
| |where the facility is located. | |Field Length: Maximum 60 |no facility information. |
| | | | |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 |Required 1 |Field Type: Alphanumeric |The field can be populated with “NA” if the State/DI program has |
| |facility site (i.e., the full name that | |Field Length: 1-80 |no facility information. |
| |commonly appears on invoices, signs, or | | |The entire submission to CDX will be rejected if the field is |
| |other business documents, or as assigned | | |blank or fails to conform to the specifications on data field type|
| |by the state when the name is ambiguous). | | |and length. The request to fix errors and resubmit the file will |
| | | | |be sent to the State/DI program. |
|Facility Petition Status |Status of review of no-migration petition |Required 2 & |Field Type: Alphanumeric |See validation comments in High Priority field of Well table |
|(Class I) (PETIT_STAT) |(this is a technical demonstration |conditional |Field Length: 2 | |
| |required before Class I hazardous waste | | | |
| |injection facilities may begin operating) | |Required for facilities with a Class I Haz| |
| | | |well (Well Type is equal to ‘1H’). | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |Acceptable Values. | |
|Facility State (FAC_STATE)|The U.S. Postal Service abbreviation that |Required 2 |Field Type: Alphanumeric |An alert message will be generated if the field is blank. If the |
| |represents the state | |Field Length: 2 |field fails to conform to the data type, length, and acceptable |
| | | | |values, its content will be replaced with a blank field; however, |
| | | |See Appendix C to the Data Dictionary for |the file still goes through EPA data system when the State/DI |
| | | |Acceptable Values |program submits it to CDX. |
|Facility State ID |Facility identification assigned by direct|Required 1 |Field Type: Alphanumeric |State or DI program assigned Facility ID. May be same as Facility |
|(F_STATE_ID) |implementation (DI) program or primacy | |Field Length: 1-50 |ID above if the program has no Facility information. |
| |program | | |The entire submission to CDX will be rejected if the field is |
| | | |Unique among reported facility records |blank or fails to conform to the specifications on field type, |
| | | |within a Primacy Agency code |length and uniqueness. A request to fix errors and resubmit the |
| | | |Consistency required for a combination |file will be sent to the State/DI program. |
| | | |between FACILITY_ID and F_STATE_ID on each| |
| | | |submission | |
|Facility Street Address |The address that describes the physical |Required 1 |Field Type: String |The field can be populated with a “fire address” (i.e., for |
|(FAC_STREET) |(geographic) location of the main entrance| |Field Length: 1-150 |emergency responders) or “NA” if State/DI has no facility info. |
| |of a facility site, including urban-style | | |See #2 under Facility Name for validation process. |
| |street address or rural address, well | | | |
| |field entrance, etc.. | | | |
|Facility Type |Class I well waste is disposed in either |Required 2 & |Field Type: Alphanumeric |See Facility Petition Status for validation process. |
|(Class I only) (FAC_TYPE) |of two types of facilities: (1) |Conditional |Field Length: 1 | |
| |Commercial- where the waste is generated | | | |
| |offsite and transported to the disposal | |Required for facilities with a Class I | |
| |facility, or (2) Non-commercial-where the | |well. | |
| |waste is generated onsite and disposed | |See Appendix C to the Data Dictionary for | |
| |there also. | |Acceptable Values. | |
|North American Industry |The NAICS code that represents a |Required 2 |Field Type: Alphanumeric |Higher-level SIC and NAICS codes acceptable but as much detail as |
|Classification System Code|subdivision of an industry that | |Field Length: Maximum 6 |possible is preferred. |
|(NAICS_CODE) |accommodates user needs in the United | | |See #2 under Facility City for validation process. |
| |States (6-digits)-- (Only primary code) | | | |
|Standard Industrial |The code that represents the economic |Required 2 |Field Type: Alphanumeric |Can be empty if NAICS_Code is populated |
|Classification Code |activity of a company. (4-digits) -- (only| |Field Length: 4 | |
|(SIC_CODE) |the primary code) | | | |
|Facility Zip Code |The combination of the 5-digit Zone |Required 1 |Field Type: String |See #2 under Facility Name for validation process. |
|(FAC_ZIP) |Improvement Plan (ZIP) code and the | |Field Length: 5-14 | |
| |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. | | | |
|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 Phone (CON_PHONE) |The phone number of a contact for a well. |Required 2 |Field Type: Alphanumeric |See #2 under Facility City for validation process. |
| | | |Field Length: Maximum 15 | |
| | | | | |
|Contact Name (CON_NAME) |The legal and complete name of a contact |Required 1 |Field Type: String |See #2 under Facility Name for validation process. |
| |person (including first name, middle name | |Field Length: 1-70 | |
| |or initial, and surname) for the well. | | | |
|Contact City (CON_CITY) |The name of the city, town, or village of |Required 2 |Field Type: String |See #2 under Facility City for validation process. |
| |the contact for a well. | |Field Length: Maximum 30 | |
| | | | | |
|Contact State (CON_STATE) |The name of the state where the contact is|Required 2 |Field Type: Alphanumeric |See #2 under Facility City for validation process. |
| |located or the name of the country, if | |Field Length: maximum 50 | |
| |outside the U.S. | | | |
|Contact Street |The street address of the contact for a |Required 1 |Field Type: String |See #2 under Facility Name for validation process. |
|(CON_STREET) |well. This can be a physical location or | |Field Length: 1-150 | |
| |a mailing address. | | | |
|Contact Zip (CON_ZIP) |The combination of the 5-digit Zone |Required 1 |Field Type: Alphanumeric |See #2 under Facility Name for validation process. |
| |Improvement Plan (ZIP) code and the | |Field Length: 5-14 | |
| |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. | |Zero or more inspection records are |Inspections are related to either a facility or well record. |
| |Inspection could be for a well or a | |reported for each well or facility record.|Either value of Well ID or Facility ID is populated and can’t be |
| |facility where no well is found | |For facility inspections, the facility |both populated. |
| | | |should have NO injection wells associated |Multiple fields uniqueness will be checked when data is loaded |
| | | |with it. |into the National UIC Database. |
| | | |Inspection Date, Type, and Well | |
| | | |ID/Facility ID together should not be the | |
| | | |same for any two or more inspection | |
| | | |records | |
|Assistance (ASSISTANCE) |Compliance assistance provided by the |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only, but primacy |
| |inspector based on national policy: |Conditional |Field Length: 2 |states may report as well. |
| | | | | |
| |-- General Assistance: involves | |Required for DI programs (Last 2 | |
| |distributing prepared information on | |characters of primacy agency code equal to| |
| |regulatory compliance, P2 or other written| |‘DI’) | |
| |materials/websites | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
| |-- Site-specific Assistance: involves | | | |
| |on-site assistance by the inspector to | | | |
| |support actions taken to address | | | |
| |deficiencies | | | |
|Deficiency (DEFICIENCY) |Potential violations found by EPA |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only, but primacy |
| |inspector during inspection |Conditional |Field Length: 2 |states may report as well. |
| | | | | |
| | | |Required for DI programs (Last 2 | |
| | | |characters of primacy agency code equal to| |
| | | |‘DI’) | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Inspection Date (INS_DATE)|The date inspection action was completed |Required 1 |Field Type: Date |See Permit Action Date for validation process |
| | | |Format: 8 (YYYYMMDD) | |
| | | | | |
| | | |Date should be within the inclusive data | |
| | | |range of 1901-01-01 through the current | |
| | | |date. | |
|ICIS Compliance Monitoring|The reason for performing a Compliance |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only. |
|Action Reason |Monitoring action. |Conditional |Field Length: 2 | |
|(DI Programs only) |Agency Priority: The compliance monitoring| | | |
|(ICIS_REASON) |action was performed in furtherance of a | |Required for DI programs (Last 2 | |
| |priority or initiative of the Compliance | |characters of primacy agency code equal to| |
| |Monitoring Agency or a partner agency. | |‘DI’) | |
| | | |See Appendix C to the Data Dictionary for | |
| |Core Program: The compliance monitoring | |list of acceptable values. | |
| |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. | | | |
|ICIS Compliance Monitoring|Type of Compliance Monitoring taken by a |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only. |
|Type (DI Programs only) |regulatory Agency |Conditional |Field Length: 3 | |
|(ICIS_TYPE) | | | | |
| | | |Same as above | |
|ICIS Compliance Activity |Type of compliance activity taken by a |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only. |
|Type (DI Programs only) |regulatory agency. |Conditional |Field Length: 2 | |
|(ICIS_ACT_TYPE) | | | | |
| | | |Same as above | |
|ICIS MOA Priorities (DI |The name of Memorandum of Agreement (MOA) |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only. |
|Programs only) |associated with the activity |Conditional |Field Length: Maximum 50 | |
|(ICIS_MOA_PRIORITY) | | | | |
| | | |Required for DI programs (Last 2 | |
| | | |characters of primacy agency code equal to| |
| | | |‘DI’) | |
|ICIS Regional Priorities |The name of regional priority associated |Required 2 & |Field Type: Alphanumeric |This information is required for DI programs only. |
|(DI Programs only) |with the activity |Conditional |Field Length: Maximum 12 | |
|(ICIS_REG_PRIORITY) | | | | |
| | | |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 |Required 1 |Field Type: Alphanumeric |Use ‘No Well’ type for facility inspections that found no wells. |
| |conducted | |Field Length: 2 |See Authorized Status for validation process. |
| | | | | |
| | | |See Appendix C to the Data dictionary for | |
| | | |list of acceptable values | |
|Well ID (WELL_ID) |Unique identification of Well table |Required 1 & |Field Type: Alphanumeric |All inspections must be tied to a well and not a facility unless a|
| | |conditional (Foreign |Field Length: 5-20 |facility has no wells found during the inspection. |
| | |Key) | |Foreign Key IDs in child table must exist in related parent table.|
| | | |ID must exist in table Well. |Otherwise, the entire submission will be rejected. |
| | | |Only exists when Facility ID is blank | |
|Facility ID (FACILITY_ID) |Unique identification of Facility |Required 1 & |Field Type: Alphanumeric |An inspection record may be tied to either a well record or a |
| |table—This field ONLY applies for Class V |conditional (Foreign |Field Length: 5-20 |facility record. Inspections to facilities that have no wells |
| |“No Well” inspection |Key) | |should use this field (foreign key ID) to link to the facility |
| | | |ID must exist in table Facility. |inspected. The Well ID field above should be blank when this |
| | | |Only exists when Well ID is blank. |field is populated. |
| | | |Only exits when Class V Inspection Type is|Foreign Key IDs in child table must exist in related parent table.|
| | | |‘No Well”. |Otherwise, the entire submission will be rejected. |
|10. Table CORRECTION: |Corrective actions for deficiency found | |Only exists if inspection exists. |Deficiencies found during an inspection may or may not have any |
| |from an inspection | |Zero or more mechanical integrity test |corrective actions. |
| | | |records are reported for each well record.|The requirements to individual fields apply only when corrective |
| | | | |actions are reported. |
|Corrective Action Type |Type of actions taken to correct |Required 2 |Field Type: Alphanumeric |See Facility State for validation process. |
|(CORACT_TYPE) |deficiencies | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Comments (COMMENTS) |Narrative description of actions taken by |Required 2 & |Field Type: Alphanumeric |See validation comments in High Priority field of Well table |
| |the facility or assistance to help the |Conditional |Field Length: Maximum 200 | |
| |facility come into compliance | | | |
| | | |If Corrective Action Type is equal to | |
| | | |‘Other,’ then this field must be | |
| | | |populated. | |
|Inspection ID |The unique identification of Inspection |Required 1 (Foreign |Field Type: Alphanumeric |Corrective action must relate to an inspection. |
|(INSPECTION_ID) |table |key) |Field Length: 5-20 | |
| | | | | |
| | | |ID must exist in table Inspection | |
|11. Table (MI_TEST) |Historical data of mechanical integrity | |Zero or more mechanical integrity test |A well may or may not have any MITs. |
| |test | |records are reported for each well record.|The requirements to individual fields apply only when MIT |
| | | |MIT Date, Type, Result, and Well ID |information is reported. |
| | | |together must not be same for any two MIT |Multiple fields uniqueness will be checked when data is loaded |
| | | |records. |into the national UIC database. |
|MIT Date (MIT_DATE) |The date that mechanical integrity test |Required 1 |Field Type: Date |See Permit Action Date for date validation process. |
| |was completed | |Format: 8 (YYYYMMDD) | |
| | | | | |
| | | |Date should be within the inclusive data | |
| | | |range of 1901-01-01 through the current | |
| | | |date. | |
|MIT Result (MIT_RESULT) |The result of Mechanical Integrity Test on|Required 1 |Field Type: Alphanumeric |See Authorized Status for validation process. |
| |that date (see above) | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|MIT Type (MIT_TYPE) |Type of mechanical integrity test |Required 1 |Field Type: Alphanumeric |See Authorized Status for validation process. |
| | | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Remedial Action Date |The date (corresponding to Remedial Action|Required 1& Conditional|Field Type: Date |Remedial Action date must be present if Remedial Action Type is |
|(RA_DATE) |Type) when a well that failed an MI test | |Format: 8 (YYYYMMDD) |present and the date should be no earlier than MIT date. |
| |received successful remedial action | | |See Permit Action Date for additional information on date |
| | | |1. Must exist if Remedial Action type |validation. |
| | | |exists. | |
| | | |2. Date should be within the inclusive | |
| | | |data range of the MIT Date through the | |
| | | |current date. | |
|Remedial Action Type |Type of successful remedial action that |Required 2 and |Field Type: Alphanumeric |If MIT test result is ‘F’ (‘Failure’), then a remedial action |
|(RA_TYPE) |well has received on the remedial action |Conditional |Field Length: 2 |should be reported. If not reported, an alert message will be |
| |date | | |generated. |
| | | |1. Required if MIT Result is ‘F’. |See Facility Petition Status for additional information on |
| | | |2. See Appendix C to the Data Dictionary |validation process. |
| | | |for list of acceptable values. | |
|Well ID (WELL_ID) |Unique |Required 1 (Foreign |Field Type: Alphanumeric |This field must be populated. |
| |identification of Well table |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Well ID must exist in table Well | |
|12. Table VIOLATION |Historical data of violation | |Zero or more violation records are |Violation may be related to a facility or well record. The value |
| | | |reported for each well or facility record.|of facility ID and well ID can’t both exist in the Violation |
| | | |Violation Date, Type, and Well ID/Facility|record. |
| | | |ID together should not be same for any two|Multiple fields uniqueness will be checked when data is loaded |
| | | |violation records |into the National UIC Database. |
|Contamination |Well in noncompliance has allegedly |Required 2 |Field Type: Alphanumeric |See Facility City for validation process. |
|(CONTAMINATION) |contaminated an underground source of | |Field Length: 1 | |
| |drinking water (USDW) this year to date | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Endangering (ENDANGER) |A violation that results in the well |Required 2 |Field Type: Alphanumeric |See Facility City for validation process. |
| |potentially or actually endangering the | |Field Length: 1 | |
| |USDW. The endangering fluid contaminant | | | |
| |from the well is in violation of RCRA or | |See Appendix C to the Data Dictionary for | |
| |SDWA or applicable regulations | |Acceptable Values. | |
|Violation Return to |The calendar date, determined by the |Required 2 |Field Type: Date |Return to compliance date will be blank for wells that have not |
|Compliance Date |Responsible Authority, on which the | |Format: 8 (YYYYMMDD) |yet returned to compliance. |
|(RE_COMP_DATE) |regulated entity actually returned to | | |The return to compliance date should be no earlier than the |
| |compliance with respect to the legal | |Date should be within the inclusive data |violation date. |
| |obligation that is the subject of the | |range of 1901-01-01 through the current |See Permit Action Date for additional information on date |
| |violation determined date. | |date. |validation. |
| | | |Date should be on or after the Violation | |
| | | |Date for the same record | |
|Violation Significant |The indication whether or not the |Required 2 & |Field Type: Alphanumeric |If the contamination is ‘Y’, and this field is not ‘Y’, then an |
|(SNC) |violation is in Significant Non-Compliance|conditional |Field Length: 1 |alert message will be generated, and the submission will still be |
| |(SNC) | | |accepted. [Should this field be populated as ‘Y’ by the software |
| | | |Must be ‘Y’ if Contamination is equal to |in this case?] |
| | | |‘Y.’ |See Facility Petition Status for additional information on |
| | | |See Appendix C to the Data Dictionary for |validation process. |
| | | |list of acceptable values | |
|Violation Date (VIO_DATE) |The calendar date the Responsible |Required 1 |Field Type: Date |See Permit Action Date for date validation. |
| |Authority determines that a regulated | |Format: 8 (YYYYMMDD) | |
| |entity is in violation of a legally | | | |
| |enforceable obligation. | |Date should be within the inclusive data | |
| | | |range of 1901-01-01 through the current | |
| | | |date. | |
|Violation Type (VIO_TYPE) |The type of violation that is the subject |Required 1 |Field Type: Alphanumeric |See Authorized Status for validation process. |
| |of the Violation Date | |Field Length: 2 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Well ID (WELL_ID) |Unique identification of Well table |Required 1 & |Field Type: Alphanumeric |A violation record may be tied to either a well record or a |
| | |conditional (Foreign |Field Length: 5-20 |facility record. |
| | |key) | |Foreign Key IDs in child table must exist in related parent table.|
| | | |1. ID must exist in table Well |Otherwise, the entire submission will be rejected. |
| | | |2. Only exist when Facility ID is blank | |
|Facility ID (FACILITY_ID) |Unique identification of Facility |Required 1 & |Field Type: Alphanumeric |A violation record may be tied to either a well record or a |
| |table—This field ONLY applies for Class V |conditional (foreign |Field Length: 5-20 |facility record. Violations of Unauthorized Injection (UI), |
| |violations at FACILITY level (not to an |key) | |Mechanical Integrity (MI), Injection Pressure (IP), Plugging and |
| |individual well) | |1. ID must exist in table Facility |Abandonment (PA), and Operation and Maintenance (OM) should only |
| | | |2. Only exist when well ID is blank |happen at the well level, not at the facility level. |
| | | |3. Violation type is not “UI, MI, IP, PA, |Foreign Key IDs in child table must exist in related parent table.|
| | | |OM” as in the appendix C of data model |Otherwise, the entire submission will be rejected. |
|13. Table RESPONSE | |Required 1 and |One or more response record must exist for|The Response table is a link table between the violation and |
| | |conditional |each enforcement record. |enforcement tables. |
| | | | |The submission will be rejected if an enforcement record has no |
| | | | |related response record. |
|Violation ID |The unique identification of Violation |Required 1 (Composite |Field Type: Alphanumeric |This field uses a foreign key as a composite primary key. Foreign|
|(VIOLATION_ID) |table - The first four characters are |Primary Key; Foreign |Field Length: 5-20 |Key IDs in child table must exist in related parent table. |
| |primacy agency code (appendix D to the |key) | |Otherwise, the entire submission will be rejected. |
| |Data Dictionary). The rest is DI program | |ID must exist in table Violation | |
| |or State’s choice (letters and numbers | | | |
| |only) identifying unique violation (e.g. | | | |
| |08DI000905, …) | | | |
|14. Table ENFORCEMENT |Historical data of enforcement action | |All enforcement records must be related to|Enforcement actions may or may not exist for a violation. The |
| | | |one or more violation records. |requirements to individual fields apply only when enforcement |
| | | | |information is reported. |
| | | | |Enforcement action must be related to a violation through the |
| | | | |Response table. See Response table for validation. |
|Enforcement Action Date |The calendar date the enforcement action |Required 1 & |Field Type: Date |Submission will be rejected if the date is earlier than related |
|(ENF_DATE) |was issued or filed |Conditional |Format: 8 (YYYYMMDD) |violation date. |
| | | | |See Permit Action Date for additional information on date |
| | | |Date should be within the inclusive data |validation. |
| | | |range of 1901-01-01 through the current | |
| | | |date. | |
| | | |Date should be on or after related | |
| | | |Violation Date | |
|Enforcement Action Type |The type of action taken by the EPA or |Required 1 |Field Type: Alphanumeric |See Authorization Status for validation process. |
|(ENF_TYPE) |states | |Field Length: 3 | |
| | | | | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|15. Table GEOLOGY (Class I|Main geological data of a well |Required 2 and |Geology information should be reported for|See Geology ID in table Well for validation. |
|& other deep-wells | |conditional |Class I and other deep wells | |
|injection) | | | |Provide the main geology data if State/DI program has multiple |
| | | | |geology data for a well |
|Name of Confining Zone |Geologic formation name |Required 2 & |Field Type: Alphanumeric | |
|(CZ_NAME) | |conditional |Field Length: Maximum 100 | |
| | | | | |
| | | |Required for Class I & deep wells | |
|Top of Confining Zone |The top of the geologic arresting layer |Required 2 & |Field Type: Numeric | |
|(CZ_TOP) |that keeps injectate confined in the |conditional |Field Length: Maximum 6 digits | |
| |injection zone measured in feet below | | | |
| |surface | |Required for Class I & deep wells | |
|Bottom of Confining Zone /|The bottom of the geologic arresting layer|Required 2 & |Field Type: Numeric | |
|Top of Injection Zone |that keeps injectate confined in the |conditional |Field Length: Maximum 6 digits | |
|(CZ_BOTTOM) |injection zone | | | |
| |OR: | |Required for Class I & deep wells | |
| |The top of the vertical dimension of the | | | |
| |zone in which waste is injected. | | | |
| |-- measured in feet below surface | | | |
|Lithology of Confining |Confining zone data in the form of a |Required 2 & |Field Type: Alphanumeric | |
|Zone (CZ_LITHOLOGY) |simple lithologic description of the |conditional |Field Length: Maximum 100 | |
| |formation | | | |
| | | |Required for Class I & deep wells | |
|Name of Injection Zone |Geologic formation name for injection zone|Required 2 & |Field Type: Alphanumeric | |
|(IZ_NAME) | |conditional |Field Length: Maximum 100 | |
| | | | | |
| | | |Required for Class I & deep wells | |
|Bottom of Injection Zone |The bottom of the vertical dimension of |Required 2 & |Field Type: Numeric | |
|(IZ_BOTTOM) |the zone in which waste is injected, |conditional |Field Length: Maximum 6 digits | |
| |measured in feet below surface. | | | |
| | | |Required for Class I & deep wells | |
|Lithology of Injection |Injection zone data in the form of a |Required 2 & |Field Type: Alphanumeric | |
|Zone (IZ_LITHOLOGY) |simple lithologic description of the |conditional |Field Length: Maximum 100 | |
| |formation | | | |
| | | |Required for Class I & deep wells | |
|Top of Injection Interval |The top of the vertical dimension of the |Required 2 & |Field Type: Numeric | |
|(INT_TOP) |specific layer(s) of the Injection |conditional |Field Length: Maximum 6 digits | |
| | | | | |
| | | |Required for Class I & deep wells | |
|Bottom of Injection |The bottom of the vertical dimension of |Required 2 & |Field Type: Numeric | |
|Interval (INT_BOTTOM) |the specific layer(s) of the Injection |conditional |Field Length: Maximum 6 digits | |
| |Zone in which waste is authorized to be | | | |
| |injected into, measured in feet below | |Required for Class I & deep wells | |
| |surface. | | | |
|Injection Zone |The rate of diffusion of fluids (in this |Required 2 & |Field Type: Numeric | |
|Permeability |case liquid waste) under pressure through |conditional |Field Length: Maximum 6 digits | |
|(IZ_PERMEABILITY) |porous material (formation rock) that is | | | |
| |measured in millidarcies (md.) | |Required for Class I & deep wells | |
|Injection Zone Porosity |The percent of pore space the injection |Required 2 & |Field Type: Numeric | |
|(IZ_POROSITY) |zone formation rock contains (measured in |conditional |Field Length: Maximum 3 digits | |
| |%). | | | |
| | | |Required for Class I & deep wells | |
|USDW Depth (USDW_DEPTH) |The depth (in feet) to the base of the |Required 2 & |Field Type: Numeric | |
| |underground source of drinking water |conditional |Field Length: Maximum 6 digits | |
| |(USDW) | | | |
| | | |Required for Class I & deep wells | |
|16. Table ENGINEERING |Major engineering data of a well |Required 2 and |One or more Engineering records are |If no engineering information provided for Class I and deep wells,|
|(Class I & other deep-well| |conditional |reported for each Class I or other Deep |submission will be accepted and an alert message will be |
|injection) | | |well |generated. |
|Max Flow Rate (MAX_RATE) |Maximum flow rate of injectate in the |Required 2 & |Field Type: Numeric | |
| |current quarter measured in gallons per |conditional |Field Length: 7,2 | |
| |minute. | | | |
| | | |Required for Class I & deep wells | |
|Onsite Injection |Permitted on-site injected volume measured|Required 2 & |Field Type: Numeric | |
|(ON_INJECTION) |in million gallon per month |conditional |Field Length: 6,4 | |
| | | | | |
| | | |Required for Class I & deep wells | |
|Offsite Injection |Permitted off-site injected volume |Required 2 & |Field Type: Numeric | |
|(OFF_INJECTION) |measured in million gallon per month |conditional |Field Length: 6,4 | |
| | | | | |
| | | |Required for Class I & deep wells | |
|Well ID (WELL_ID) |Unique identification of an injection well|Required 1 |Field Type: Alphanumeric |Engineering information must relate to a Class I or other deep |
| | |(Foreign key) |Field Length: 5-20 |well. Otherwise, the entire submission will be rejected. |
| | | | | |
| | | |Well ID must exist in table Well. | |
|17. Table WASTE (Class I |Waste stream data of class 1 hazardous |Required 2 and |One or more waste record is reported for |If no waste information provided for Class I wells, submission |
|only) |wells |conditional |each Class I well. |will be accepted and an alert message will be generated. |
| | | |No duplicate waste by data (record must be|Multiple fields uniqueness will be checked when data is loaded |
| | | |unique without Waste ID) |into the National UIC Database. |
|Waste Code (WASTE_CODE) |The RCRA or state waste code included when|Required 2 & |Field Type: Alphanumeric | |
| |the constituent has been assigned a code |conditional |Field Length: Maximum 4 | |
| | | | | |
| | | |Required for Class I wells | |
|Waste Stream |A classification of the waste stream that |Required 2 & |Field Type: Alphanumeric | |
|(WASTE_STREAM) |contains various constituents and waste |conditional |Field Length: Maximum 100 | |
| |codes in various concentrations. These | | | |
| |are liquids waste approved to go down the | |Required for Class I wells | |
| |well. | | | |
|Well ID (WELL_ID) |Unique identification of an injection well|Required 1 (Foreign |Field Type: Alphanumeric |Waste information must relate to a well. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Well ID must exist in table Well. | |
|18. Table CONSTITUENT |Components of waste stream including |Required 2 and |One or more constituent records are |If waste information is reported but no constituent information |
|(Class I only) |chemicals, etc. |conditional |reported for each waste record. |provided, submission will be accepted and an alert message will be|
| | | |No duplicate constituent by data (record |generated. |
| | | |must be unique without Constituent ID) |Multiple fields uniqueness will be checked when data is loaded |
| | | | |into the National UIC Database. |
|Concentration Value |The concentration of the individual waste |Required 2 & |Field Type: Numeric | |
|(CONCENTRATION) |constituent as reported by EPA Regional |conditional |Field Length: 11,5 | |
| |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 |Required 2 & |Field Type: Alphanumeric | |
| |pCi/l) |conditional |Field Length: Maximum 5 | |
| | | | | |
| | | |Must exist if concentration exists. | |
| | | |Required for Class I | |
| | | |See Appendix C to the Data Dictionary for | |
| | | |list of acceptable values | |
|Constituent Name |The chemical name or a description of the |Required 2 & |Field Type: Alphanumeric | |
|(CONS_NAME) |waste, in accordance with EPA |conditional |Field Length: Maximum 50 | |
| |Chemical/Biological Internal Tracking Name| | | |
| |() | |Required for Class I | |
|Waste ID (WASTE_ID) |Unique identification for Waste records |Required 1 (Foreign |Field Type: Alphanumeric |Constituent information must relate to a waste. |
| | |key) |Field Length: 5-20 |Foreign Key IDs in child table must exist in related parent table.|
| | | | |Otherwise, the entire submission will be rejected. |
| | | |Waste ID must exist in table Waste | |
................
................
In order to avoid copyright disputes, this page is only a partial summary.
To fulfill the demand for quickly locating and searching documents.
It is intelligent file search solution for home and business.
Related searches
- 2 page business plan sample
- 2 page business proposal
- 2 sided business cards
- 2 sided business card template
- 2 page business plan template
- business analyst requirements document
- business analyst requirements tools
- business rules for intragovernmental transactions
- business rules for software development
- business rules format
- business rules software
- business license requirements california