MI - Monitor Regulatory Compliance¶
This transaction captures information about monitors that have been assessed with respect to their compliance status with regulations.
Examples:
MI|I|02|090|0010|81102|1|QC||19880201
MI|I|TT|183|0001|81102|1|ST|Y|19990501
Format¶
Seq. |
Name |
Description |
Formatting Rules |
Required |
Key |
---|---|---|---|---|---|
1 |
Monitor Regulatory Compliance transaction identifier. |
Must = MI |
Always |
||
2 |
Indicator for Insert, Update, or Delete action. |
Must = I, U, or D |
Always |
||
3 |
The FIPS state code of the monitor, or “TT” to indicate that the next field on the transaction is a Tribal code. |
Must exist in STATES Reference Table or be ‘TT’ for Tribal Site |
Always |
Y |
|
4 |
The FIPS County Code of the site. If the previous field on the transaction contains “TT”, then the Tribal Code of the site. |
Must exist in COUNTIES (for state) or TRIBAL_AREAS Reference table |
Always |
Y |
|
5 |
Four digit number to uniquely identify site in county and/or tribe. |
Must exist in SITES table with {State Code, county Code} or Tribal Code |
Always |
Y |
|
6 |
The AQS parameter code assigned to the monitor in AQS. |
Must exist in PARAMETERS reference table. |
Always |
Y |
|
7 |
Parameter Occurrence Code: One or two digit number identifying a specific monitor for a parameter at the site. |
Must exist in MONITOR table for non-Insert actions. |
Always |
Y |
|
8 |
Identification of an EPA regulation for which compliance documentation is required. |
Must exist in PARAMETER REGULATIONS reference table. |
Always |
Y |
|
9 |
The compliance status of a monitor with respect to an EPA regulation. |
Must = Y or N. |
No |
Y |
|
10 |
The date on which the current status of the monitor’s compliance with the regulation was achieved. |
YYYYMMDD. |
No |