CAA Pipeline Download Summary

The Enforcement and Compliance History Online (ECHO) system pipeline analysis of data from the Clean Air Act (CAA) shows links between Compliance Monitoring Activities (CMA) to any related violations and/or enforcement actions.

The terms "Compliance Monitoring Activities" and "Evaluations" will be used interchangeably on this page.

The download contains the following file:


PIPELINE_CAA_00_COMPLETE

 

ElementData TypeLengthNotes
SORT_ORDERNumber A generated field to aid in the linkage creation.
SORT_DATEDate A linkage creation helper field to help get the proper display order by date.
SOURCE_IDChar30The Clean Air Act facility identification number.
REGISTRY_IDChar50The Federal Registry Identification number.  Software programs reading the CVS may attempt to convert this to scientific notation.  This is a character field to preserve leading zeros.
AIR_NAMEChar200The facility name.
PIPELINE_FLAGChar1An internally generated flag to indicate at least violation (VIOL_ACTIVITY_ID) linked to an evaluation and/or enforcement action.  A value of "Y" means "Yes a link does exist" and the pipeline table should render on the ECHO DFR page.
OFFICIAL_FLAGChar1This flag is set to 'Y' when an entry is counted as compliance monitoring strategy activities. Programs without compliance monitoring strategies will have this flag set to null and are not counted as on-site activities within EPA’s Annual Results.
EVAL_FLAGChar1An internally generated flag to indicate if there is at least one Compliance Monitoring Activity (CMA) (evaluation) to the violation activity id (VIOL_ACTIVITY_ID).
EVAL_SORT_ORDERNumber An internally generated field to help with the sort order of the evaluations data.
EVAL_ACTIVITY_IDNumber The evaluation activity identification value.
EVAL_TYPE_DESCChar100The description of the evaluation type.
EVAL_LEAD_AGENCYChar5The agency responsible for evaluation.
EVAL_DATEDate The date of the evaluation.
VIOL_FLAGChar1A system generated flag indicating a violation is present.  Entries noted as violation not found with have a generated VIOL_ACTIVITY_ID to use as links between Evaluations and Enforcement Actions.  A generated VIOL_ACTIVITY_ID starts with either "9906" or "9913".
VIOL_SORT_ORDERNumber An internally generated value to aid with the proper ordering of the identified violations.
FOUND_VIOLATIONChar1A flag indicating if a violation was found.
VIOL_ACTIVITY_IDNumber The key linking all violations to their Compliance Monitoring Activities (CMA) and/or Enforcement Actions (EA).  This is a number, and should NOT be converted to scientific notation.  Values that start with either "9906" or "9913" did not have an actual violation activity identification number, so these are system generated for purposes of creating the pipeline table.
VIOL_TYPEChar40A description of the found violation type.
VIOL_TYPE_SORTNumber A generated field providing a sort order of the violation types found.
VIOL_LEAD_AGENCYChar6The agency responsible for identifying the violation.
VIOL_PROGRAMSChar4000The programs under which the violation is defined.
VIOL_POLLUTANT_CODESChar4000A list of the pollutant codes of the violation
VIOL_POLLUTANT_DESCSChar4000A list of the pollutant descriptions of the violation
VIOL_START_DATEDate The start date of the violation
VIOL_END_DATE_DATEDate The end date of the violation.
VIOL_END_DATEChar40A character representation of the violation end date.  This is the value represented in the Pipeline table on the ECHO DFR
EA_FLAGChar1A system generated flag indicating if there is an enforcement action.
EA_SORT_ORDERNumber A system generated sort order for proper displaying of the enforcement action.
EA_ACTIVITY_IDNumber The enforcement action activity identification
EA_FEA_ACTIVITY_IDNumber The formal enforcement activity id
EA_TYPEChar100The type of enforcement action
EA_DATEDate Date of the Enforcement Action
FEA_ISSUE_DATE_FLAGChar1A flag indicating there is a formal enforcement date of issue
EA_PENALTY_AMTNumber The enforcement action penalty amount