3/25/2016
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED I
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
TABLE OF CONTENTS
1.0 GENERAL ..........................................................................................................................................................1
1.1 PURPOSE ..........................................................................................................................................................1
1.2 OVERVIEW .......................................................................................................................................................1
1.3 DOCUMENT STRUCTURE ..................................................................................................................................1
2.0 DATA WAREHOUSE DESIGN .......................................................................................................................2
2.1 REPORTING DATA WAREHOUSE DESIGN ASSUMPTIONS ..................................................................................2
2.2 REPORTING DATA WAREHOUSE ORGANIZATION/APPROACH...........................................................................2
2.3 CONTENT .........................................................................................................................................................3
2.4 COMMON FEATURES ........................................................................................................................................4
2.4.1 Bridge Tables .........................................................................................................................................4
2.4.2 Security Data Elements ..........................................................................................................................5
2.4.3 Contacts and Addresses .........................................................................................................................8
2.4.4 Activity Pollutants .................................................................................................................................9
2.4.5 Activity Programs ..................................................................................................................................9
2.4.6 Activity Comments ................................................................................................................................9
2.4.7 Standard Input Prompts ....................................................................................................................... 10
2.4.8 Date Dimension ................................................................................................................................... 12
2.5 SUBJECT AREAS ............................................................................................................................................. 12
2.5.1 Air Facility Subject Area ..................................................................................................................... 13
2.5.1.1 Air Facility Overview...................................................................................................................................... 13
2.5.1.2 Air Facility Data Warehouse Model ................................................................................................................ 15
2.5.1.3 Air Facility Subject Area Special Objects ....................................................................................................... 16
2.5.2 Compliance Monitoring Activity Subject Area ................................................................................... 18
2.5.2.1 Compliance Monitoring Activity Overview .................................................................................................... 18
2.5.2.2 Compliance Monitoring Activity Subject Area Special Objects ..................................................................... 20
2.5.3 Enforcement Action Subject Area ....................................................................................................... 20
2.5.3.1 Enforcement Action Overview ........................................................................................................................ 20
2.5.3.2 Enforcement Action Data Warehouse Model .................................................................................................. 22
2.5.3.3 Enforcement Action Subject Area Special Objects ......................................................................................... 24
2.5.4 Case File Subject Area ......................................................................................................................... 25
2.5.4.1 Case File Overview ......................................................................................................................................... 25
2.5.4.2 Case File Data Warehouse Model ................................................................................................................... 27
2.5.4.3 Case File Subject Area Special Objects .......................................................................................................... 28
3.0 EXTRACT, TRANSFORM, AND LOAD DESIGN ..................................................................................... 32
3.1 OVERVIEW ..................................................................................................................................................... 32
3.2 BATCH ETL AND INCREMENTAL ETL ............................................................................................................ 32
3.2.1 Batch ETL............................................................................................................................................ 32
3.2.2 ICIS Air Incremental ETL Workflows ................................................................................................ 34
3.2.2.1 ICIS-Air Stage Incremental Workflow............................................................................................................ 36
3.2.2.2 ICIS-Air Data Warehouse Incremental Workflow .......................................................................................... 38
3.2.2.3 Incremental ETL Supporting Workflows ........................................................................................................ 41
3.2.3 Email Status Workflow ........................................................................................................................ 41
3.3 FREQUENCY ................................................................................................................................................... 42
4.0 BUSINESS OBJECTS UNIVERSE DESIGN ............................................................................................... 43
4.1 BUSINESS OBJECTS OVERVIEW ...................................................................................................................... 43
4.2 DESIGN APPROACH ........................................................................................................................................ 44
4.3 SECURITY APPROACH .................................................................................................................................... 44
4.4 THE AIR FACILITY UNIVERSE ........................................................................................................................ 44
4.5 THE AIR COMPLIANCE MONITORING ACTIVITY UNIVERSE ............................................................................ 48
4.6 THE AIR ENFORCEMENT ACTIONS UNIVERSE ................................................................................................ 51
4.7 THE AIR CASE FILE UNIVERSE ....................................................................................................................... 56
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED II
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED III
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
LIST OF TABLES
Table 2-1 Contact & Address Types used in Each Subject Area ...................................................................................9
Table 2-2 Standard Input Prompts ............................................................................................................................... 10
Table 2-3 Facility Table Relationships ........................................................................................................................ 16
Table 2-4 Facilities Special Reporting Fields .............................................................................................................. 16
Table 2-5 Compliance Monitoring Activity Table Relationships ................................................................................ 20
Table 2-6 Compliance Monitoring Activity Special Reporting Fields ........................................................................ 20
Table 2-7 Enforcement Action Table Relationships .................................................................................................... 24
Table 2-8 Enforcement Action Special Reporting Fields ............................................................................................ 24
Table 2-9 Case File Table Relationships ..................................................................................................................... 28
Table 2-10 Case File Special Reporting Fields............................................................................................................ 28
Table 3-1: Incremental ETL Workflows ..................................................................................................................... 35
Table 4-1 Air Facility Universe Classes and Sub-Classes ........................................................................................... 46
Table 4-2 Air Facility Universe Prompts/Filters ......................................................................................................... 48
Table 4-3 Air Compliance Monitoring Universe Classes ............................................................................................ 50
Table 4-4 Air Compliance Monitoring Universe Prompts/Filters ............................................................................... 51
Table 4-5 Air Enforcement Actions Universe Classes ................................................................................................ 52
Table 4-6 Air Enforcement Actions Universe Prompts/Filters .................................................................................... 55
Table 4-7 Air Case File Universe Classes ................................................................................................................... 56
Table 4-8 Air Case File Universe Prompts/Filters ....................................................................................................... 57
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED IV
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
LIST OF FIGURES
Figure 2-1 Bridge Table Relationship Example ............................................................................................................4
Figure 2-2 Example of a Comments Table .................................................................................................................. 10
Figure 2-3 Date Dimension ......................................................................................................................................... 12
Figure 2-4 Air Facilities Subject Area Model .............................................................................................................. 15
Figure 2-5 Compliance Monitoring Subject Area Model ............................................................................................ 19
Figure 2-6 Enforcement Action Subject Area Model .................................................................................................. 23
Figure 2-7 Case File Subject Area Model.................................................................................................................... 27
Figure 3-1: ICIS-Air Batch ETL.................................................................................................................................. 33
Figure 3-2: ICIS-Air Batch ETL Workflow Order ..................................................................................................... 34
Figure 3-3: ICIS-Air Incremental ETL Flow ............................................................................................................... 36
Figure 3-4: ICIS-Air Stage Incremental Workflow ..................................................................................................... 37
Figure 3-5: ICIS Air Data Warehouse Incremental Workflow .................................................................................... 39
Figure 4-1 Universe Model (Air Facility Subject Area) .............................................................................................. 45
Figure 4-2 Universe Model (Air Compliance Monitoring Activity Subject Area) ...................................................... 49
Figure 4-3 Universe Model (Air Enforcement Action Subject Area) .......................................................................... 52
Figure 4-4 Universe Model (Air Case File Subject Area) ........................................................................................... 56
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED V
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED VI
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
1.0 GENERAL
1.1 PURPOSE
The purpose of this document is to provide a detailed technical description of the design of the
Environmental Protection Agency’s (EPA) Integrated Compliance Information System for Air
(ICIS-Air) data warehouse for use by the reporting tool for building reports from the data.
Included in this document are the database data model; the Extract, Transform, and Load (ETL)
design for populating the data warehouse; the Business Objects Universe design, and standard
reports designs that will be used for querying and analyzing data from an Air perspective.
1.2 OVERVIEW
ICIS-Air will allow federal, state, local, territorial, and tribal agencies with authorized air
enforcement and compliance programs to report required Air Stationary Source monitoring and
enforcement activity. This enforcement and compliance data is used regularly for monitoring
status at facilities, status of specific activities, and multiple other purposes. In order to do this, a
separate database structure is needed to facilitate simple querying of the data without impacting
the performance of the operational system. To meet these needs, ICIS-Air will have a data
warehouse (DW) to store data used for reporting purposes.
The ICIS-Air reporting data warehouse is designed based on industry leading best practices1 and
lessons learned from existing ICIS reporting solutions. The data model accounts for existing
ICIS-Air needs as well as leveraging common structures in the existing Interim ICIS Reporting
Solution (IIRS) database. This model lends itself to efficient mapping that will be incorporated
into an ETL process that uses industry leading technology to populate the ICIS-Air reporting
data warehouse. The ICIS-Air Business Objects Universes will contain all the reporting obects
from the ICIS-Air reporting data warehouse for use in standard and ad hoc reports.
1.3 DOCUMENT STRUCTURE
To facilitate review, this document is organized in five sections as follows:
• Section 1: Overview and Purpose – Summarizes the overview and purpose of this
document.
• Section 2: Data Warehouse Design – Details the overall ICIS-Air Data Warehouse
Architecture.
• Section 3: ETL Design – Provides an overview of the ETL architecture and details about
how the solution will be developed to move data from the ICIS operational database into
the ICIS-Air reporting data warehouse.
• Section 4: Universe Design – Provides a general overview of the structure and
organization of the Air Business Objects Universes to be used by the reporting tool.
• Section 5: Standard Reports Design – Identifies the methods for data capture and the
basic structure of the data in the reports.
1
Kimball Techniques – KimballGroup.com
Top 10 Best Practices for Building a Large Scale Relational Data Warehouse; MSDN.com
Best Practices for a Data Warehouse on Oracle Database 11g; c. 2010, Oracle White Paper
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 1
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
This section describes the data warehouse design, including assumptions, common features, and
designs for each subject area.
2.1 REPORTING DATA WAREHOUSE DESIGN ASSUMPTIONS
The following are the assumptions used in developing the reporting data warehouse design.
• While all the data elements displayed on the screens and some calculated fields will be in
the data warehouse, a few categories of data will not be included. These are:
Status columns from reference tables: these are used for development and are
available in the reference tables, but will not be pulled in with column descriptions
for the reporting areas. For example, if activity_type_code is part of a record, the
activity_type_desc and activity_group_code and activity_group_desc will be pulled in
from ref_activity_type and ref_activity_group respectively, but status_code will not.
Created/Updated columns for non-central tables: all operational tables in the
operational database will have created by/date and updated by/date columns.
Inclusion of all these columns can be confusing in a data warehouse when several
records are collapsed into a single row. Thus, only created/updated data for the key
tables (e.g., icis_enforcement, icis_facility_interest) will be included in the
datawarehouse. The design for each data area will identify which tables will have
their created/updated data included in the reporting warehouse.
• Simulated outer joins: If users want to pull in a data element from a child table they
generally want the option to see all the parent data, even those with no child data (e.g., if
they pull in Facility and Compliance Monitoring Strategy (CMS) data, all facilities
should show up, even those with no CMS data). Thus, the universes will have outer joins
from dimension tables such as Air_Facility to related data tables such as
Air_Facility_SIC and artificial inner joins from fact tables Air_Activity_Pollutant to
dimension tables using placeholder or “stub” records. This may lead at times to extra
“blank rows” being displayed in reports. Those can be eliminated using filters similar to
the IIRS data warehouse solution. If an outer join is simulated, a record is generally
returned in the results to reflect the blank row in the table with the outer join. Filters were
added to the IIRS Universe to allow users to easily filter out the blank rows from queries.
Those filters will also be created in the Air Universes.
2.2 REPORTING DATA WAREHOUSE ORGANIZATION/APPROACH
The warehouse is being designed with the assumption that several Air-related subject area
Universes will be developed to allow the user to report on all the data for a particular subject
area. For example, there will be a Universe for each of these areas:
• Air Facility
• Air Compliance Monitoring Activities
• Air Enforcement Actions
• Case File
The universes will have standard formats for geographic and activity objects and will contain
common reporting objects used for standard and ad hoc reporting. Within a universe, there will
be folders with summary information for all linked entities in each subject area. To support this
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 2
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
approach, the data warehouse will have fact and dimension tables for each subject area to link
entities to their children and to facilitate counts and analysis.
Special “bridge” tables will be used to link each activity to other activities such as Compliance
Monitoring records that link to Enforcement Actions, including others of the same type, such as
Compliance Monitoring records that link to other Compliance Monitoring records. These will
function between two dimension tables to help resolve the challenges with many-to-many (M:M)
relationships linking data. A second bridge table will be used to link a facility to all its activities
and to support cross-activity reporting such as “What activities at a facility have pollutants that
are not on the parent facility.”
Reporting objects will be created by the ETL in the data warehouse to facilitate reporting and
reduce universe query complexity. These will include objects such as:
• Current pollutant/program indicators for a facility or activity
• Activity pollutant not on parent facility indicator
• Air Facility Operating Status and Classification roll ups.
2.3 CONTENT
Data from the following modules will be included in the ICIS-Air data warehouse:
• Air Facility
• Programs, Pollutants,
• Compliance Monitoring Activities
Full Compliance Evaluations (FCE), Partial Compliance Evaluations (PCE),
including Stack Tests and Title V Annual Compliance Certifications (TV ACC)
Investigations
Information Requests
2
Offsite Record Reviews
• Enforcement Actions
• Case File.
Within any module included in the warehouse, all the records from ICIS operational database
will be copied over into the ICIS-Air data warehouse for that module, including records such as:
• Non-Air facility interests
• Non-Air activities
• NEI Case File data both Air and Non-Air.
The Universes will include objects for filtering records to return Air-only data. They will also
include objects for separating data that was entered into ICIS-Air and data that was migrated
from AFS.
“Dummy” records will be inserted into certain dimension tables to allow complex joins to return
a complete set of results. A dummy record may have a key value of -1 and “no data” for the
2
While Air Delegated Agency Compliance Monitoring Activities do not have Offsite Record Reviews, Federal
Compliance Monitoring Activities do, so they will be included.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 3
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
description field. Having this record allows multiple table joins to return data for all tables in the
join and alleviates the problem of having blank rows or columns displayed in reports.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 4
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 5
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Geo-Data
Data Warehouse Sensitive_Data Air_LCON_C Geographic
Table Name _Flag Region_Code State_Code ode _Access
AIR_FACILITY Derived from Derived from Derived from the Derived from If State_EPA_Flag
_RELATED_AC the the ICIS_ACTIVIT the = ‘E’ then copy
T ICIS_ACTIVIT ICIS_ACTIVIT Y row of the ICIS_ACTIVIT the Region_Code,
Y row of the Y row of the related activity. Y row of the else if
related activity. related activity. related activity. State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_CASE_FIL Copied from Copied from Copied from Copied from If State_EPA_Flag
E_DIM ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
Y. Y. Y. Y. the Region_Code,
else if
State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_CASE_FIL Derived from Derived from Derived from Derived from If State_EPA_Flag
E_FAC_ADV_V the ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
IOLAT ICIS_ACTIVIT Y row of each Y row of each Y row of each the Region_Code,
Y row of each Case File Case File Case File else if
Case File activity. activity. activity. State_EPA_Flag =
activity. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_CASE_FIL Derived from Derived from Derived from Derived from If State_EPA_Flag
E_VIOLATION the ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
ICIS_ACTIVIT Y row of each Y row of each Y row of each the Region_Code,
Y row of each Case File Case File Case File else if
Case File activity. activity. activity. State_EPA_Flag =
activity. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_CASE_FIL Derived from Derived from Derived from Derived from If State_EPA_Flag
E_PATHWAY the ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
ICIS_ACTIVIT Y row for each Y row for each Y row for each the Region_Code,
Y row for each Linked_Activit Linked_Activity Linked_Activit else if
Linked_Activit y_ID. _ID. y_ID. State_EPA_Flag =
y_ID. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_CASE_FIL Derived from Derived from Derived from the Derived from If State_EPA_Flag
E_RELATED_A the the ICIS_ACTIVIT the = ‘E’ then copy
CT ICIS_ACTIVIT ICIS_ACTIVIT Y row of the ICIS_ACTIVIT the Region_Code,
Y row of the Y row of the related activity in Y row of the else if
related activity related activity each row. related activity State_EPA_Flag =
in each row. in each row. in each row. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_EA_DIM Copied from Copied from Copied from Copied from If State_EPA_Flag
ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
Y. Y. Y. Y. the Region_Code,
else if
State_EPA_Flag =
‘S’ then copy the
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 6
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Geo-Data
Data Warehouse Sensitive_Data Air_LCON_C Geographic
Table Name _Flag Region_Code State_Code ode _Access
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_EA_COM Copied from Copied from Copied from Copied from If State_EPA_Flag
MENT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
Y_COMMENT Y_COMMENT Y_COMMENT. Y_COMMENT the Region_Code,
. . . else if
State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_EA_BIG_C Derived from Derived from Derived from the Derived from If State_EPA_Flag
ASE_PROJECTI the the ICIS_ACTIVIT the = ‘E’ then copy
ON ICIS_ACTIVIT ICIS_ACTIVIT Y row of each ICIS_ACTIVIT the Region_Code,
Y row of each Y row of each EA activity. Y row of each else if
EA activity. EA activity. EA activity. State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_EA_RELA Derived from Derived from Derived from the Derived from If State_EPA_Flag
TED_ACT the the ICIS_ACTIVIT the = ‘E’ then copy
ICIS_ACTIVIT ICIS_ACTIVIT Y row of the ICIS_ACTIVIT the Region_Code,
Y row of the Y row of the related activity in Y row of the else if
related activity related activity each row. related activity State_EPA_Flag =
in each row. in each row. in each row. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_COMP_MO Copied from Copied from Copied from Copied from If State_EPA_Flag
N_DIM ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
Y. Y. Y. Y. the Region_Code,
else if
State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_COMP_MO Copied from Copied from Copied from Copied from If State_EPA_Flag
N_COMMENT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT ICIS_ACTIVIT = ‘E’ then copy
Y_COMMENT Y_COMMENT Y_COMMENT. Y_COMMENT the Region_Code,
. . . else if
State_EPA_Flag =
‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
AIR_COMP_MO Derived from Derived from Derived from the Derived from If State_EPA_Flag
N_RELATED_A the the ICIS_ACTIVIT the = ‘E’ then copy
CT ICIS_ACTIVIT ICIS_ACTIVIT Y row of each ICIS_ACTIVIT the Region_Code,
Y row of each Y row of each related activity in Y row of each else if
related activity related activity each row. related activity State_EPA_Flag =
in each row. in each row. in each row. ‘S’ then copy the
State_Code, else if
State_EPA_Flag =
‘L’ then copy the
LCON_code.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 7
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Each subject area will have sensitive data columns at the following levels:
• The main subject area table (e.g., Air Comp Monitor)
• Each related activity table (e.g., Air Enforcement Actions Related Activities)
• Any other sensitive data tables (e.g., sensitive comments, CMS data).
The ICIS_USER table in the data warehouse will be populated from the ICIS and fill it will all
active users. Then we will create a new table for user access privileges called
SENSITIVE_USER_ACCESS that will be used to facilitate determining whether a sensitve user
has the geographic access to a particular piece of sensitive data. The table will have the
following two columns:
SENSITIVE_USER_ACCESS Table
Column Name Description
USER_ID User_ID from the ICIS_USER table; only users who
have the sensitive data privilege will have rows in
these tables.
GEOGRAPHIC_ACCESS Region, State, or LCON code for every geography to
which the user has access.
This table, in combination with the ICIS_USER data and the Sensitive Data Flag and Geographic
Access column in the data will be used to provision access to sensitive data. The WHERE clause
will then be applied simply to all universe queries when sensitive data are accessed:
If data_table.Sensitive_Data_Flag = ”Y” then
if data_table.Geographic_Access = USER_ACCESS.Geographic_Access then
allow access.
If the Sensitive Data Flag is “N”, then no additional restriction will be necessary.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 8
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Government contacts are similarly combined and added to each subject area. Address
information from organization and office tables are merged with fixed phone and email
information and added to a table such as Air_Comp_Mon_Gov_Contact_Addr in the
Compliance Monitoring subject area. The following table lists each module and which types of
contact and address information it includes.
Table 2-1 Contact & Address Types used in Each Subject Area
Subject Area Type of C&A
Facility Non-government contacts
Non-government addresses
Compliance Monitoring Government contacts
Non-government contacts
Non-government addresses
Enforcement Actions Government contacts
Case File Government contacts
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 9
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 10
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Subject Warehouse
Criteria Description Area Warehouse Table(s) Column(s) Comments
Facility Name Current or FACILITY AIR_FACILITY_DIM Facility_Name_FI
historical facility
name
Facility Acronym for the FACILITY AIR_FACILITY_DIM Pgm_sys_acrnm_F
Program system of record I
System for the facility
Acronym
Facility Programmatic FACILITY AIR_FACILITY_DIM Facility_pgm_sys_
Program Facility unique id_FI
System identifier
Identifier
FRS Identifier FRS unique FACILITY AIR_FACILITY_DIM Facility_UIN_FRS
facility site
identifier
Facility Current Default facility FACILITY AIR_CLASS_DIM Default_Air_Class Where
Default classification _Desc AIR_FACILITY_CLAS
Classification S_FACT
.Current_Flag=Y
Facility Current EPA facility FACILITY AIR_CLASS_DIM EPA_Air_Class_D Where
EPA classification esc AIR_FACILITY_CLAS
Classification S_FACT
.Current_Flag=Y
Facility Current Delegated Agency FACILITY AIR_CLASS_DIM State_Air_Class_D Where
Delegated facility esc AIR_FACILITY_CLAS
Agency classification S_FACT
Classification .Current_Flag=Y
Facility Current Pollutant(s) FACILITY AIR_POLLUTANT_ Pollutant_Desc Where
Pollutants associated with the DIM AIR_FACILITY_POLL
facility UT_CLASS_FACT.Cur
rent_Flag=Y
Facility Current Program(s) FACILITY AIR_FAC_PROG_SU Program_Desc Where
Air Programs associated with the BP_STATUS AIR_FAC_PROG_SUB
facility P_STATUS.Current_Fl
ag=Y
Facility Current Subparts FACILITY AIR_FAC_PROG_SU Air_Program_Sub Where
Subparts associated with the BP_STATUS part_Desc AIR_FAC_PROG_SUB
facility P_STATUS.Current_Fl
ag=Y
Facility Current Most “active” FACILITY AIR_FAC_OPERATI Air_Operating_Sta Where
Operating current operating NG_STATUS tus_Desc AIR_FAC_OPERATIN
Status status of the G_STATUS.Current_Fl
facility’s programs ag=Y
Facility Reporting FACILITY AIR_FACILITY_UNI Air_Universe_Des
Universe universe(s) VERSE c
associated with the
facility
Activity Input Prompts
Activity Region performing FACILITY AIR_FACILITY_REL Region_Code Includes HQ, 01-10
Performed By the activity (if an ATED_ACT
Region EPA activity)
Activity State performing FACILITY AIR_FACILITY_REL State_Code
Performed By the activity (if a ATED_ACT
State State activity)
Activity LCON performing FACILITY AIR_FACILITY_REL Air_LCON_Desc
Performed By the activity (if an ATED_ACT
LCON LCON activity)
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 11
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Subject Warehouse
Criteria Description Area Warehouse Table(s) Column(s) Comments
Activity Pollutant(s) FACILITY AIR_ACTIVITY_PO Pollutant_Desc
Pollutant associated with the LLUTANT
activity
Activity Program(s) FACILITY AIR_ACTIVITY_PR Program_Desc
Program associated with the OGRAM
activity
This approach will allow conformity among dimenions in the ICIS-Air data warehouse and allow
cross-drilling to gather information across activities that happen during the same period. In
addition, the database engine loads just one table (Date_Dim) into memory. As a result, query
performance is optimized when just one table’s index is hit rather than the index on multiple date
tables.
Figure 2-3 shows the structure of the date dimension table.
Figure 2-3 Date Dimension
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 12
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 13
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
For all three tables, the default status will always be the highest level classification
(aka the lowest rank-order, e.g., Major Emissions (10) trumps Synthetic Minor
Emissions (20))
If a facility has no pollutants, a default pollutant of -1 with the pollutant name of “No
Pollutants” will be assigned along with blank classifications
The system also will flag current pollutants and current facility classifications.
• Create FACT table for programs to show the program/sub part history: Facilities
have programs, and some programs have sub parts. A process in the ETL will build a
combined program/sub part history for the facilities and then a facility operating status
history will be derived from that table. If a facility has no programs, a default program of
-1 with the program name of “No Programs” will be assigned. If a program has no sub
parts (or equals No Programs), then a sub part of -1 with the sub part name of “No Sub
Parts” will be assigned. For the facility status history, the strongest operating status (aka
the lowest rank-order) will be used if multiple statuses could be applied at a given time
(e.g., Operating (10) trumps Seasonal (20)). The system also will flag current
programs/sub parts.
The Facility subject area will use the following common features:
• Facility and activities bridge table
• Non-government contacts and addresses
• Security data elements for CMS data
• Standard input prompts
• Date dimension.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 14
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 15
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Table 2-3 shows the relationships among the tables in the subject area.
Table 2-3 Facility Table Relationships
Dimension Snowflake/Fact Table Relationship
AIR_FACILITY_DIM AIR_FACILITY_NAICS_DIM 1 to 1-to-many
AIR_FACILITY_DIM AIR_FACILITY_SIC_DIM 1 to 0-to-many
AIR_FACILITY_DIM AIR_PORTABLE_SOURCE_DIM 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_INTEREST_HISTORY 1 to 0-to-many
AIR_FACILITY_DIM AIR_NAA 1 to 0-to-many
AIR_FACILITY_DIM AIR_CMS 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_NG_CONTACT_ADDR 1 to 0-to-many
AIR_FACILITY_DIM AIR_FAC_PROG_SUBP_STAT_FACT 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_STATUS_FACT 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_POLLUT_CLASS_FACT 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_CLASS_FACT 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_RELATED_ACT 1 to 0-to-many
AIR_FACILITY_DIM AIR_FACILITY_UNIVERSE 1 to 0-to-many
AIR_COMP_MONITOR_DIM AIR_FACILITY_RELATED_ACT 1 to 0-to-many
AIR_ENFORCEMENT_ACTION_DIM AIR_FACILITY_RELATED_ACT 1 to 0-to-many
AIR_ACTIVITY_POLLUTANT AIR_FACILITY_RELATED_ACT 1 to 0-to-many
AIR_ACTIVITY_PROGRAM AIR_FACILITY_RELATED_ACT 1 to 0-to-many
AIR_FAC_OPERATING_STATUS_DIM AIR_FAC_PROG_SUBP_STAT_FACT 1 to 0-to-many
AIR_FAC_OPERATING_STATUS_DIM AIR_FACILITY_STATUS_FACT 1 to 0-to-many
AIR_POLLUTANT_DIM AIR_FACILITY_POLLUT_CLASS_FACT 1 to 0-to-many
AIR_CLASS_DIM AIR_FACILITY_POLLUT_CLASS_FACT 1 to 0-to-many
AIR_CLASS_DIM AIR_FACILITY_CLASS_FACT 1 to 0-to-many
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 16
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Calculated records
FRV_Status Flags the facility based on the AIR_CASE_FILE_VI Unaddressed HPV are Warehouse
“worst” status of its non-resolved OLATION those with blank
HPV case files: Addressing and
- Unaddressed HPV Resolving milestones
- Addressed HPV
- Blank Addressed HPV are
those with populated
The worst compliance Addressing milestones
determination is: but blank Resolving
- Highest on the status milestones
hierarchy:
o Addressed Blank is all CSs are
o Unaddressed resolved or no CFs exist
- If more than one with the for facility
same status, the CF with the
latest ”Earliest HPV Day
Zero” date
- If more than one with the
same Earliest HPV Day
Zero date, the one with the
largest activity ID
Facility classification History of the facility’s AIR_FACILITY_CLA Includes Begin and End Warehouse
history classification as derived from its SS_FACT Date; EPA, DA, Default
pollutant records status codes and
descriptions
Facility operating History of the facility’s operating AIR_FACILITY_STA Includes Begin and End Warehouse
status history status as derived from its TUS_FACT Date; Program codes and
program records descriptions, Sub Part
Codes and descriptions
Other
Air facility flag Indicates whether the facility is AIR_FACILITY_DIM If facility interest pgm Universe
an air facility or not (Y/N) sys acrnm = AIR, set to
Yes, else No
Facility on a CMS Indicates whether the facility AIR_FACILITY_DIM If any records in Warehouse
plan currently has an active CMS air_cms_dim have plan
record. Needed because the CMS removal date null or in
record itself is sensitive, but the the future, set to Yes,
fact that a record is on a CMS else No
plan is not sensitive.
Primary NAICS Indicates the primary NAICS AIR_FACILITY_DIM Primary_NAICS_Code_ Warehouse
Code code FI
Primary NAICS Desc Indicates the primary NAICS AIR_FACILITY_DIM Primary_NAICS_Desc_F Warehouse
description I
Primary SIC Code Indicates the primary SIC code AIR_FACILITY_DIM Primary_SIC_Code_FI Warehouse
Primary SIC Desc Indicates the primary SIC AIR_FACILITY_DIM Primary_SIC_Desc_FI Warehouse
description
Facility Ownership Indicates whether the Air facility AIR_FACILITY_DIM Air_fac_geography_indic Warehouse
is “owned” by a State or an ator
LCON
If the pgm_sys_acrnm =
AIR:
ELSE State
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 17
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Facility Compares the current default AIR_FACILITY_DIM Use logic in Compliance Warehouse
Classification does facility classification to the Monitoring Strategy
not match CMS current year CMS category to (CMS) document to
category see if the CMS category value is determine whether the
compatible with the default value facility’s classification
matches, “Yes” if it is
compatible, and “No” if
it is not
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 18
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The following is the Air Compliance Monitoring subject area model for the Air reporting data warehouse.
Figure 2-5 Compliance Monitoring Subject Area Model
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 19
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the relationships between the tables in the subject area.
Table 2-5 Compliance Monitoring Activity Table Relationships
Dimension Snowflake/Fact Table Relationship
AIR_FACILITY_DIM AIR_FACILITY_NAICS_DIM 1 to 1-to-many
AIR_COMP_MON_DIM AIR_STACK_TEST_DIM 1 to 0 to many
AIR_COMP_MON_DIM AIR_TVACC_DIM 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_LAW_SECTION 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_NAICS 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_SIC 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_PROGRAM 1 to 1
AIR_COMP_MON_DIM AIR_COMP_MON_CROSS_MEDIA 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_TYPE 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_COMMENT 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_DEFICIENCY 1 to 0 or 1
AIR_COMP_MON_DIM AIR_COMP_MON_POLLUTANT 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_REPORT 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_PURPOSE 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_OUTCOME 1 to 0 to many
AIR_COMP_MON_DIM AIR_COM_MON_RELATED_ACT 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_NG_CONTACT_ADDR 1 to 0 to many
AIR_COMP_MON_DIM AIR_COMP_MON_GOV_CONTACT_ADDR 1 to 0 to many
AIR_STACK_TEST_DIM AIR_STACK_TEST_RESULT 1 to 0 to many
Other
Air_LCON_Code Geo data is used in conjunction AIR_COMP_MON_D Warehouse
State_Code with the Sensitive_Flag in the IM
Region_Code AIR_COMP_MON_DIM table
to filter sensitive data.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 20
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
• Leverage the AIR_FACILITY_DIM table created in the Facility subject area. The
Enforcement Actions subject area connects data stored in the main activity table
(AIR_EA_DIM) with Facility Interest data from the ICIS_FACILITY_INTEREST and
FRS_FACILITY_SITE tables through the use of a combined Facility Interest table
(AIR_FACILITY_DIM) that was created for the Facility subject area. The table is
populated through ETL for the Facility subject area and reused here.
• Create a single dimension table for all EA activity data. A single table combines the
data from ICIS_ACTIVITY with ICIS_ENFORCEMENT. Small reference data from
REF_ACTIVITY_TYPE and REF_ENF_OUTCOME is also included.
• Create FACT tables for leveraging pollutant data stored in a reusable dimension
table. For reporting purposes, a single dimension table was created
(AIR_POLLUTANT_DIM) that could be used across all subject areas. To leverage this
data, small FACT tables were created to connect the main dimension data with this
pollutant table. In the, Enforcement Actions subject area, there are two tables for this.
The first one (AIR_EA_POLLUTANT_FACT) links the main EA activity data in
AIR_EA_DIM with pollutants and the second one (AIR_EA_FO_POLLUTANT_FACT)
links the EA’s Final Order with the pollutants involved.
• Create a special bridge table for connecting Enforcement Actions to other activities.
The EA subject area leverages a design feature of this data warehouse, called “activity
bridge tables” that store the links to dimension data for this activity as well as other
related activities. The EA bridge table (AIR_EA_RELATED_ACT) contains the database
keys for the EA activities, Compliance Monitoring, Case File, as well as other related EA
activities. The ETL process will also store data from the ICIS table called
ICIS_RELATED_ENF in this table.
The Enforcement Action subject area will use the following common features:
• Related activities bridge table (AIR_EA_RELATED_ACT)
• Security data elements for EA data
• Facility Interest table from the Facility subject area.
• Standard input prompts
• Date dimensions.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 21
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
EA DW Model.pdf
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 22
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 23
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the relationships between the tables in the subject area.
Table 2-7 Enforcement Action Table Relationships
Dimension Snowflake/Fact Table Relationship
AIR_EA_DIM AIR_EA_DEFENDANT_DIM 1-to-many
AIR_EA_DIM AIR_EA_SUB_ACTIVITY 1-to-many
AIR_EA_DIM AIR_EA_BIG_CASE_PROJECTION 1-to-many
AIR_EA_DIM AIR_EA_CITATION 1-to-many
AIR_EA_DIM AIR_EA_LAW_SECTION 1-to-many
AIR_EA_DIM AIR_EA_COMMENT 1-to-many
AIR_EA_DIM AIR_EA_RELIEF 1-to-many
AIR_EA_DIM AIR_EA_CROSS_MEDIA 1-to-many
AIR_EA_DIM AIR_EA_PROGRAM 1-to-1
AIR_EA_DIM AIR_EA_ENF_TYPE 1-to-many
AIR_EA_DIM AIR_EA_FO_DIM 1-to-many
AIR_EA_DIM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_EA_DIM AIR_EA_RELATED_ACT 1-to-many
AIR_EA_DIM AIR_EA_POLLUTANT_FACT 1-to-many
AIR_POLLUTANT_DIM AIR_EA_POLLUTANT_FACT 1-to-many
AIR_FACILITY_DIM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_POLLUTANT_DIM AIR_EA_FO_POLLUTANT_FACT 1-to-many
AIR_ACTIVITY_PROGRAM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_FACILITY_RELATED_ACT AIR_EA_FACILITY_EJ 1-to-many
AIR_POLLUTANT_DIM AIR_FACILITY_POLLUT_CLASS_FACT 1-to-many
AIR_FACILITY_DIM AIR_FACILITY_POLLUT_CLASS_FACT 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_COMP_ACTION 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_POLLUTANT_FACT 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_DEFENDANT 1-to-many
AIR_EA_FO_DIM AIR_EA_COMP_SCHEDULE 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_STATUTE_LAW 1-to-many
AIR_EA_FO_DIM AIR_EA_ENV_IMPACT 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_COMP_STATUS 1-to-many
AIR_EA_FO_DIM AIR_EA_FO_SEP_FACT 1-to-many
AIR_EA_FO_DIM AIR_EA_SEP_DIM 1-to-many
AIR_EA_FO_STATUTE_LAW AIR_EA_FO_PENALTY 1-to-many
AIR_EA_FO_STATUTE_LAW AIR_EA_FO_COST_RECOVERY 1-to-many
AIR_EA_FO_COMP_STATUS AIR_EA_FO_SEP_FACT 1-to-many
AIR_EA_SEP_DIM AIR_EA_FO_SEP_FACT 1-to-many
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 24
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Count of Sub Count the number of sub AIR_EA_SUB_ACTI Count(Sub Activity Key) Universe
Activities activities associated with each VITY for EA
EA.
Calculated records
Other
Air_LCON_Code Geo data is added to the AIR_EA_BIG_CASE Copy data from Warehouse
State_Code AIR_EA_BIG_CASE_PROJEC _PROJECTION ICIS_ACTIVITY for
Region_Code TION table from the each EA
ICIS_ACTIVITY table to be
used for filtering sensitive data
based on the Sensitivity_Level
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 25
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 26
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 27
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the relationships between the tables in the Case File subject area.
Table 2-9 Case File Table Relationships
Dimension Snowflake/Fact Table Relationship
AIR_CASE_FILE_DIM AIR_CASE_FILE_PRIORITY 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_CONSULTATION 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_FAC_ADV_VIOLAT 1-to-1
AIR_CASE_FILE_DIM AIR_CASE_FILE_VIOLATION 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_PATHWAY 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_RELATED_ACT 1-to-many
AIR_CASE_FILE_DIM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_PROGRAM 1-to-many
AIR_CASE_FILE_DIM AIR_CASE_FILE_POLLUTANT 1-to-many
AIR_EA_DIM AIR_EA_FO_DIM 1-to-many
AIR_EA_DIM AIR_EA_TYPE 1-to-many
AIR_EA_DIM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_COMP_MON_DIM AIR_COMP_MON_TYPE 1-to-many
AIR_COMP_MON_DIM AIR_FACILITY_RELATED_ACT 1-to-many
AIR_FACILITY_DIM AIR_FACILITY_RELATED_ACT 1-to-many
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 28
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Number of days from Calculate the number of days AIR_CASE_FILE_DI Resolving Date - Earliest Warehouse
HPV Day Zero to from the HPV day zero date to M HPV Day Zero Date; if
resolved the resolved date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Notification Date - Warehouse
FRV Determination from the FRV determination date M Determination Date; if
to notification to the notification date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Addressing Date - Warehouse
FRV Determination from the FRV determination date M Determination Date; if
to addressed to the addressing date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Resolving Date - Warehouse
FRV Determination from the FRV determination date M Determination Date; if
to resolved to the resolved date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Addressing Date - Warehouse
notification to from the notification date to the M Notification Date; if
addressed addressing date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Resolving Date - Warehouse
notification to from the notification date to the M Determination Date; if
resolved resolved date. either date is null,
populate as null
Number of days from Calculate the number of days AIR_CASE_FILE_DI Resolving Date - Warehouse
addressed to resolved from the addressing date to the M Addressing Date; if
resolved date. either date is null,
populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Warehouse
discovery (today – from the discovery date to today. M Discovery Date. If
discovery date) Discovery Date is null,
populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Warehouse
notification from the notification date to M Notification Date. If
today. Notification Date is null,
populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Warehouse
addressed from the Addressed date to M Addressing Date. If
today. Addressing Date is null,
populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Resolving Warehouse
resolved from the Resolved date to today. M Date. If Resolving Date
is null, populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Warehouse
FRV Determination from the FRV Determination M Determination Date. If
date to today. Determination Date is
null, populate as null
Number of days since Calculate the number of days AIR_CASE_FILE_DI Today’s date – Earliest Warehouse
HPV Day Zero from the HPV Day Zero date to M HPV Day Zero Date. If
today. Earliest HPV Day Zero
Date is null, populate as
null
Calculated records
Pathway Activity Activity Type Code of the AIR_CASE_FILE_PA Copy Warehouse
Type Code pathway activity THWAY ACTIVITY_TYPE_CO
DE from
ICIS_ACTIVITY
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 29
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Pathway Activity Activity Type Description of the AIR_CASE_FILE_PA Copy Warehouse
Type Description pathway activity THWAY ACTIVITY_TYPE_DES
C from
REF_ACTIVITY_TYPE
Pathway Activity Activity Name for the pathway AIR_CASE_FILE_PA Copy Warehouse
Name activity THWAY ACTIVITY_NAME
from ICIS_ACTIVITY
Pathway Activity Activity unique identifier for the AIR_CASE_FILE_PA Warehouse
UID pathway activity THWAY
Pathway Activity AIR_CASE_FILE_PA Warehouse
Source THWAY
Earliest_HPV_Day_ For violations with multiple AIR_CASE_FILE_DI Get the minumun Warehouse
Zero_Date HPV-Day-Zero dates, this holds M HPV_Day_Zero_Date
the earliest date. from the
AIR_CASE_FILE_VIOL
ATION table for every
Case File.
Other
Air_LCON_Code Geo data is added to the AIR_CASE_FILE_FA Copy data from Warehouse
State_Code AIR_CASE_FILE_FAC_ADV_ C_ADV_VIOLAT ICIS_ACTIVITY for
Region_Code VIOLAT table from the each Case File Violation
ICIS_ACTIVITY table to be where the Facility was
used for filtering sensitive data advised.
based on the
Sensitive_Data_Flag
Air_LCON_Code Geo data is added to the AIR_CASE_FILE_VI Copy data from Warehouse
State_Code AIR_CASE_FILE_VIOLATION OLATION ICIS_ACTIVITY for
Region_Code table from the ICIS_ACTIVITY each Case File Violation
table to be used for filtering where the Facility was
sensitive data based on the advised.
Sensitive_Data_Flag
Air_LCON_Code Geo data is added to the AIR_CASE_FILE_RE Copy data from Warehouse
State_Code AIR_CASE_FILE_RELATED_ LATED_ACTIVITY ICIS_ACTIVITY for
Region_Code ACT table from the each Case File Violation
ICIS_ACTIVITY table to be where the Facility was
used for filtering sensitive data advised.
based on the
Sensitive_Data_Flag
Determination_Date This will be either AIR_CASE_FILE_DI Warehouse
Comp_Determination_Date, or if M
that’s null, the earliest FRV
determination date from the
violations table.
Pathway_Discovery_ This is the AIR_CASE_FILE_DI Copy Warehouse
Date Pathway_Activity_Date from M Pathway_Activity_Date
AIR_CASE_FILE_PATHWAY from
where Pathway_Category_Code AIR_CASE_FILE_PAT
= DSCV HWAY where
Pathway_Category_Code
= DSCV
Pathway_Notification This is the AIR_CASE_FILE_DI Copy Warehouse
_Date Pathway_Activity_Date from M Pathway_Activity_Date
AIR_CASE_FILE_PATHWAY from
where Pathway_Category_Code AIR_CASE_FILE_PAT
=NTFC HWAY where
Pathway_Category_Code
= NTFC
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 30
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Warehouse
Object Name Object Description Table Object Pseudo code or Universe
Pathway_Addressing This is the AIR_CASE_FILE_DI Copy Warehouse
_Date Pathway_Activity_Date from M Pathway_Activity_Date
AIR_CASE_FILE_PATHWAY from
where Pathway_Category_Code AIR_CASE_FILE_PAT
=ADDR HWAY where
Pathway_Category_Code
= ADDR
Pathway_Resolving_ This is the AIR_CASE_FILE_DI Copy Warehouse
Date Pathway_Activity_Date from M Pathway_Activity_Date
AIR_CASE_FILE_PATHWAY from
where Pathway_Category_Code AIR_CASE_FILE_PAT
=RSLV HWAY where
Pathway_Category_Code
= RSLV
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 31
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
3.1 OVERVIEW
Extract, Transform, and Load (ETL) processes can be simple or complex. The purpose of an
ETL is to take source data (extract) and manipulate (transform) that data to load the target. The
complexities are introduced in the volume and frequency of the extract and the business rules or
reporting requirements in transforming and loading the data to the target.
ETLs can vary based on reporting requirements. Some ETL processes involve complex
transformations that require custom code like the current transformation used by IIRS or
commercial off-the-shelf (COTS) products like Informatica to transform the source data into
target data format.
The frequency of transformation and volume of data to be transformed will influence the ETL
process design and development significantly. In addition, ETL processes can be developed in
multiple ways such as using custom developed PL/SQL or using tools like Informatica’s
PowerCenter and PowerExchange. The purpose of this section is to discuss the specific details of
the ETL processes for the ICIS-Air data warehouse.
3.2 BATCH ETL AND INCREMENTAL ETL
The ICIS-Air data warehouse is populated by two ETL processes: batch and incremental. These
processes vary primarily on the volume and type of data extracted from the source. They diverge
in purpose as the Batch ETL is a complete replacement of the data warehouse and is used when
all data must be completely recovered for example during an outage or when the source database
is rebuilt. The Incremental ETL’s purpose is to update the existing data warehouse data with
changed data. The ETLs also vary technically in the way the data is extracted and loaded to the
data warehouse. They share the same business rules, which makes the majority of
transformations the same between the processes.
3.2.1 Batch ETL
The ICIS-Air Batch ETL was developed prior to the incremental ETL and is based in large part
on the ICIS Interim Reporting Solution (IIRS) ETL. The purpose of the Batch ETL is to drop
the entire ICIS-Air data warehouse dataset and replace it with data from the ICIS Production
Operational dataset. This is typically done when resetting the Air Data Warehouse after a major
release when the source database has archive log mode off, in cases of recovery where servers
may be taken offline unexpectedly, or if the source database is rebuilt. The operational data is
extracted nightly using Oracle export and import functionality which places the data in an ICIS
schema on an Air Data Warehouse database instance (i.e. AIRDWP). This data (source data) are
then transformed and loaded to the target schema (AIR_REPORTS) in the same Air Data
Warehouse database using Informatica PowerCenter. Figure 3-1 illustrates the flow of data for
the Batch ETL.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 32
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Similar to the IIRS ETL, the Batch ETL was developed based on the target Air Data Warehouse
tables. Each target table was mapped from one or more sources using Informatica mappings that
transform the data. The naming convention used for the Informatica mapping is the name of the
target table. For example, the Informatica mapping, “m_load_air_facility_dim_batch” signifies
that it is used to load the AIR_FACILITY_DIM table. This limits the Batch ETL to 74
transformational sessions to load data to the data warehouse (1 for each target table) with 8
administrative sessions in 1 primary workflow (wf_load_dw_batch). The sessions that populate
the data warehouse can operate relatively independent of each other and execute at the same time
in most cases. The exceptions are parent tables that must be populated with primary keys before
the child table is populated in the data warehouse. Since the Batch ETL is a complete
replacement of data, constraints and indexes are disabled or dropped on the data warehouse
before loading and enabled or created as each session completes the load to the target table.
In addition to the wf_load_dw_batch workflow, the Batch ETL has 2 supporting workflows: one
to identify when the Oracle Extract is complete and generate a wait file (wf_air_extraction), and
one to add constraints and indexes to all data warehouse tables, 15 minutes after the primary
workflow completes (wf_add_all_ICIS_DW_constraints). The 15 minute delay is to allow any
table locks in Oracle due to commits to clear out before enabling constraints and creating
indexes. The workflow execution order for Batch ETLis identified in Figure 3-2.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 33
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 34
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 35
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 36
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 37
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 38
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 39
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 40
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 41
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
3.3 FREQUENCY
The frequency of an ETL process depends on the volume of data to be transformed, the
transform and load throughput, the needs of the stakeholders, and its impact on the ICIS
operational database and ICIS-Air reporting system. The current IIRS ETL and ICIS-Air Batch
ETL process uses a full extract of the entire ICIS schema. This process is run off-hours to
minimize the impact on the operational database. By leveraging Oracle’s redo logs and using the
PowerExchange and PowerCenter tools, the ICIS-Air ETL could be run on a more frequent basis
during business hours. The wf_stg_incremental_table_load is currently run every hour to grab
changed data and load to the AIR_STAGE schema in the Air Data Warehouse. The
wf_dw_incremental_table_load updates the AIR_REPORTS schema in the Air Data Warehouse
once daily, but can be run more frequently depending on the need. If run more frequently, the
supporting workflow wf_stg_reset_export should also run at the same frequence to reduce
volume and improve performance.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 42
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Reporting function in ICIS-Air will allow users to retrieve and display data in either
standard reports or through ad hoc reporting and querying. ICIS-Air users will have the ability to
report on Air data alone or in combination with FE&C and/or NPDES data.
Ad hoc reporting allows users to define their own report parameters, displaying information that
caters to their specific needs or requirements. This provides users with a set of predefined objects
that can be readily used in developing reports. Users can create customized queries and format
and filter the results in the resulting screen to facilitate data analysis.
ICIS-Air will use Business Objects to satisfy the requirements for the ad hoc reporting
capability. The following is a list of reporting features that will be available using Business
Objects:
• A user-friendly interface
• The ability to schedule, share, and send reports
• The ability to share report queries
• The ability to drill-down to the report details
• Complex “where-clause” logic
• The ability to export report results to formats such as PDF, Excel, Comma-Separated
Value (CSV), and XML
• The ability to create temporary variables and reporting objects
• The ability to view object definitions
• The ability to view valid values in query objects.
ICIS-Air Ad Hoc reporting will allow users to create customized reports not available as
standard reports by using data elements from the reporting universe. The use of a reporting
universe will allow users to create customized reports without having to possess technical
knowledge of the complexities of the database. Additionally, pre-built filters/prompts will allow
users to easily narrow queries by certain criteria (e.g., geography, data owner, or program). The
universes will allow users to retrieve the data that interests them by using familiar business
terminology.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 43
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The ICIS-AIR reporting system will include separate Universes for each of the ICIS-Air subject
areas:
• Air Facility
• Air Compliance Monitoring Activities
• Air Enforcement Actions
• Air Case File
Universes will apply a consistent design to allow for ease of use across all universes. The
following standards will be utilized to achieve this:
• Standard formats for objects in each Universe that return information on geography and
activity.
• Standardized naming conventions and placement of objects in each Universe.
• A set of folders with standard summary information for all linked entities in each subject
area.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 44
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Sensitive data in the Air Facility Universe are the Compliance Monitoring Strategy (CMS) data.
These records are always sensitive. Related Activities data is also sensitive. The Sensitive data
restrcitions are applied at the table level by creating derived tables within the universe.
The Description objects throughout the universe comes from Reference tables. Metrics folder
will contain all the calculated objects created in the universe. Prompts and Filter folder will have
all the prompts and filters created in the universe.
Figure 4-1 shows the Air Facility universe high-level model.
Figure 4-1 Universe Model (Air Facility Subject Area)
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 45
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Error! Reference source not found.1 lists the Air Facility Universe classes and their
descriptions.
Table 4-1 Air Facility Universe Classes and Sub-Classes
Class Name Parent Class Class Description
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 46
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Air Facility universe will have the facility input prompts/filters listed in Error! Reference
source not found..
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 47
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Filter or
Filter/Prompt Name Prompt Filter/Prompt Description
Air Facilities Only Filter Pulls facilities where the pgm_sys_acrnm = AIR
AFS Migrated Data Only Filter Brings data where created_by like 'AFS_MIG%'
PCS Migrated Data Only Filter Brings data where created_by like 'PCS_MIG%'
Exclude AFS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'
Exclude PCS Migrated Data Filter Excludes data where created_by like 'PCS_MIG%'
Exclude AFS and PCS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'or
'PCS_MIG%'
Exclude AFS and PCS Migrated Data? Prompt Asks for user input whether to Excludes data where
created_by like 'AFS_MIG%'or 'PCS_MIG%'
Exclude AFS Migrated Data? Prompt Asks for user input whether to Excludes data where
created_by like 'AFS_MIG%'
Exclude PCS Migrated Data? Prompt Asks for user input whether to Excludes data where
created_by like 'PCS_MIG%'
Facility Site Name (pattern search)? Prompt Prompt to search Facility Site Name allowing search
pattern to use wildcard '%'
Facility City (free text) (pattern search)? Prompt Prompt to search Facility City allowing search pattern to
use wildcard '%'
Facility City (GNIS)? Prompt Prompt for Facility City (GNIS)
Facility Region? Prompt Prompt for Facility Region
Facility State? Prompt Prompt for Facility State
Facility LCON? Prompt Prompt for Facility LCON
Facility County? Prompt Prompt for County
Tribal Land? Prompt Prompt for Land
Non-Attainment Area? Prompt Prompt for Non-Attainment Area
Programmatic System? Prompt Prompt for Programmatic System
Program ID? Prompt Prompt for Program ID
FRS Identifier? Prompt Prompt for FRS Identifier
Facility Current Default Classification? Prompt Prompt for Facility Current Default Classification
Facility Current EPA Classification? Prompt Prompt for Facility Current EPA Classification
Facility Current Delegated Agency Prompt Prompt for Facility Current Delegated Agency
Classification? Classification
Facility Current Pollutant? Prompt Prompt for Current Pollutant for a facility
Facility Current Program? Prompt Prompt for Facility Current Program
Facility Active Subpart? Prompt Prompt for Active Subpart
Facility Current Operating Status? Prompt Prompt for Current Operating Status for a facility
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 48
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure 4-12 shows the Air Compliance Monitoring Activity Universe high-level model.
Figure 4-2 Universe Model (Air Compliance Monitoring Activity Subject Area)
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 49
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Error! Reference source not found. lists the Air Compliance Monitoring Universe classes their
descriptions, and their source tables.
Table 4-3 Air Compliance Monitoring Universe Classes
Class Name Parent Class Class Description
Compliance Monitoring Common Report Basic CM information that has a one
Objects to one relationship with the CM
activity (e.g., location address,
geography, identifiers).
Compliance Monitoring Important Compliance Monitoring Common Report
Dates Objects
Compliance Monitoring Citations Compliance Monitoring Common Report
Objects
Compliance Monitoring Sensitive Compliance Monitoring Common Report
Comments Objects
Compliance Monitoring Non-Sensitive Compliance Monitoring Common Report
Comments Objects
Compliance Monitoring Programs Compliance Monitoring Common Report Programs associated with the
Objects activity
Compliance Monitoring Law Sections Compliance Monitoring Common Report
Objects
Compliance Monitoring Types Compliance Monitoring Common Report
Objects
Compliance Monitoring Action Reasons Compliance Monitoring Common Report
Objects
Compliance Monitoring Agencies Compliance Monitoring Common Report
Objects
Other Agency Types Compliance Monitoring Agencies
Compliance Monitoring Initiatives Compliance Monitoring Common Report All CM Initiatives details
Objects
Compliance Monitoring Deficiencies Compliance Monitoring Common Report CM reported deficiencies including
Objects state & region data
Compliance Monitoring Corrective Compliance Monitoring Common Report
Actions Objects
Compliance Monitoring Pollutants Compliance Monitoring Common Report Pollutant details associated with this
Objects activity
Compliance Monitoring SICs Compliance Monitoring Common Report All SICs associated with the
Objects activity, including the primary SIC
Compliance Monitoring NAICS Compliance Monitoring Common Report All NAICS associated with the
Objects activity, including the primary
NAICS
Compliance Monitoring Outcome Compliance Monitoring Common Report All CM activity outcome including
Objects outcome text and dates
Compliance Monitoring Cross Media Compliance Monitoring Common Report All CM cross media details
Indicators Objects
Compliance Monitoring TV ACC Compliance Monitoring Common Report
Objects
TV ACC Reviews Compliance Monitoring TV ACC
Compliance Monitoring Stack Tests Compliance Monitoring Common Report All Stack Test data and results
Objects
Stack Test Observed By Compliance Monitoring Stack Tests
Stack Test Purpose Compliance Monitoring Stack Tests
Stack Test Results Compliance Monitoring Stack Tests
Compliance Monitoring Facilities All CM Facilities data
Programs and Subparts Compliance Monitoring Facilities All Programs and Subparts CM
Facility data
Programs and Subparts Current Only Compliance Monitoring Facilities Programs and Subparts CM Facility
Current only data
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 50
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Air Compliance Monitoring universe will have the standard CM input prompts /filters as
listed in Error! Reference source not found..
Table 4-4 Air Compliance Monitoring Universe Prompts/Filters
Filter or
Filter/Prompt Name Prompt Filter/Prompt Description
PCS Migrated Data Only Filter Brings data where created_by like 'PCS_MIG%'
AFS Migrated Data Only Filter Excludes data where created_by like 'AFS_MIG%'
Exclude PCS Migrated Data Filter Excludes data where created_by like 'PCS_MIG%'
Exclude AFS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'or 'PCS_MIG%'
Exclude PCS and AFS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'or 'PCS_MIG%'
Exclude AFS Migrated Data Prompt Prompt Asks for user input whether to Excludes data where created_by like
'AFS_MIG%'
Exclude PCS and AFS Migrated Data Prompt Asks for user input whether to Excludes data where created_by like
Prompt 'AFS_MIG%'or 'PCS_MIG%'
CM Related Activity Type Prompt Prompt Asks for user input for a CM Related activity
Exclude CM Related Activity Type Prompt Prompt Asks for user input whether to exclude a CM Related activity type
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 51
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Error! Reference source not found. lists the Air Enforcement Actions Universe classes and
their descriptions.
Table 4-5 Air Enforcement Actions Universe Classes
Class Name Parent Class Class Description
Enforcement Action Common Report Air Enforcement Actions common report
Objects objects
Enforcement Action Type Enforcement Action Common Report Objects Enforcement Action Types associated with
EAs
Enforcement Action Agencies Enforcement Action Common Report Objects Enforcement Action Agencies
Other Agency Types Enforcement Action Agencies
Enforcement Action Initiatives Enforcement Action Common Report Objects
Enforcement Action Law Sections Enforcement Action Common Report Objects
Enforcement Action Programs Enforcement Action Common Report Objects
Enforcement Action Enforcement Action Common Report Objects
Respondents/Defendants
Enforcement Action Pollutants Enforcement Action Common Report Objects
Enforcement Action Court Docket Numbers Enforcement Action Common Report Objects
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 52
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 53
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 54
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Air Enforcement Actions universe will have input prompts /filters as listed in Error!
Reference source not found..
Table 4-6 Air Enforcement Actions Universe Prompts/Filters
Filter or
Filter/Prompt Name Prompt Filter/Prompt Description
EA Sensitive Data Prompt Prompt Asks user input whether to display sensiitive data for EA
Big Case Projection Sensitive Data Prompt Prompt Asks user input whether to display sensiitive data for Big Case
Projection data of EA
Sensitive Comment Sensitive Data Prompt Prompt Asks user input whether to display sensiitive Comments for EA
Related Activity Sensitive Data Prompt Prompt Asks user input whether to display Related Activity sensiitive
data for EA
PCS Migrated Data Only Filter Brings data where created_by like 'PCS_MIG%'
AFS Migrated Data Only Filter Brings data where created_by like 'AFS_MIG%'
Exclude PCS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'
Exclude AFS Migrated Data Filter Excludes data where created_by like 'PCS_MIG%'
Exclude PCS and AFS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'or
'PCS_MIG%'
Exclude AFS Migrated Data? Prompt Asks for user input whether to Excludes data where created_by
like 'AFS_MIG%'
Exclude PCS and AFS Migrated Data? Prompt Asks for user input whether to Excludes data where created_by
like 'AFS_MIG%'or 'PCS_MIG%'
EA Related Activity Type? Prompt Asks for user input for a CM Related activity
Exclude EA Related Activity Type? Prompt Asks for user input whether to exclude a CM Related activity
type
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 55
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Error! Reference source not found. lists the Air Case File Universe classes and their
descriptions.
Table 4-7 Air Case File Universe Classes
Class Name Parent Class Class Description
Case File Common Report Objects Case file common reporting objects based on
Air_Case_File_Dim
Air Case File Dates Case File Common Report Objects
Air Case File Pathways Case File Common Report Objects
Pathway Original Data Air Case File Pathways
Air Violations Case File Common Report Objects Air Case File Violations
Air Facility Violation Advisement Case File Common Report Objects
Case File Consultations Case File Common Report Objects Air Case File Consultations details
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 56
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Air Case File universe will have input prompts /filters as listed in Error! Reference source
not found..
Table 4-8 Air Case File Universe Prompts/Filters
Filter or
Filter/Prompt Name Prompt Filter/Prompt Description
PCS Migrated Data Only Filter Brings data where created_by like 'PCS_MIG%'
AFS Migrated Data Only Filter Brings data where created_by like 'AFS_MIG%'
Exclude PCS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'
Exclude AFS Migrated Data Filter Excludes data where created_by like 'PCS_MIG%'
Exclude PCS and AFS Migrated Data Filter Excludes data where created_by like 'AFS_MIG%'or 'PCS_MIG%'
Exclude PCS and AFS Migrated Data? Prompt Asks for user input whether to Excludes data where created_by like
'AFS_MIG%'or 'PCS_MIG%'
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 57
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the source tables and columns from the ICIS-Air operational data source
along with the target tables and columns in the ICIS-Air data warehouse for data in the Facilities
subject area. The last column contains comments that describe the business rules or other criteria
used to generate that column. This is the primary source of instructions for building the
Informatica processes.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 58
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 59
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 60
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 61
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 62
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 63
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 64
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 65
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 66
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 67
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 68
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 69
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 70
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 71
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 72
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
AIR_FACILITY_CLASSIF_HISTORY Air_Classif_History_Key
AIR_FACILITY_INTEREST_HISTOR Air_Facility_Interest_Hist_Key
Y
AIR_FACILITY_NAICS Air_Facility_NAICS_Key Create new keys in
AIR_FACILITY_SIC Air_Facility_SIC_Key these tables
AIR_NAA Air_NAA_Key
AIR_OPERATING_STATUS_HISTO Air_Operating_Status_Hist_Key
RY
AIR_FACILITY_DIM Facility_Key AIR_NAA Facility_Key
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_SIC Facility_Key
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_NAICS Facility_Key
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_PROGRAM Facility_Key
AIR_FACILITY_DIM Facility_Key AIR_CMS Facility_Key Replace
AIR_FACILITY_DIM Facility_Key AIR_POLLUTANT_DIM Facility_Key ICIS_Facility_Interest_
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_INTEREST_HISTOR Facility_Key ID in AIR_NAA. Use
Y Facility_Key as a non-
AIR_FACILITY_DIM Facility_Key AIR_NAA Facility_Key identifying key (FK) in
AIR_FACILITY_DIM Facility_Key AIR_OPERATING_STATUS_HISTO Facility_Key these tables.
RY
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_CLASSIF_HISTORY Facility_Key
AIR_FACILITY_DIM Facility_Key AIR_FACILITY_NG_CONTACT_AD Facility_Key
DR
AIR_FACILITY_NG_CONTACT_AD Current_Flag Set to ‘Y’ if
DR Begin_Date_Cont is <=
today and
End_Date_Cont >
today or is NULL, else
set to ‘N’
AIR_POLLUTANT_DIM Pollutant_Not_on_Facility_Flag Set default to ‘Y’ when
row is created.
Change to ‘N’ if
pollutant is associated
with a facility.
AIR_FACILITY_CLASS_FACT Current_Flag Set to ‘Y’ if
Begin_Date <= today
and End_Date > today
or blank, else, set to
‘N’
AIR_FACILITY_POLLUT_CLASS_FA Current_Flag Set to ‘Y’ if
CT Begin_Date <= today
and End_Date > today
or blank, else, set to
‘N’
AIR_FAC_PROG_SUBP_STAT_FAC Current_Flag Set to ‘Y’ if
T Begin_Date_Program
<= today and
End_Date_Program >
today or blank, else,
set to ‘N’
AIR_FACILITY_STATUS_FACT Current_Flag Set to ‘Y’ if
Begin_Date <= today
and End_Date > today
or blank, else, set to
‘N’
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 73
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 74
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the source tables and columns from the ICIS-Air operational data source
along with the target tables and columns in the ICIS-Air data warehouse for data in the
Compliance Monitoring subject area. The last column contains comments that describe the
business rules or other criteria used to generate that column. This is the primary source of
instructions for building the Informatica workflows.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 75
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Operational Source table & column Data Warehouse target table and column
Source Table Source Column Target Table Target Column Comment
AIR_COMP_MON_DIM Air_Comp_Mon_Key Uniquely created with
row
ICIS_ACTIVITY Activity_Type_Code AIR_COMP_MON_DIM Activity_Type_Code
ICIS_ACTIVITY Region_Code AIR_COMP_MON_DIM Region_Code
ICIS_ACTIVITY Air_LCON_Code AIR_COMP_MON_DIM Air_LCON_Code
ICIS_ACTIVITY Activity_Name AIR_COMP_MON_DIM Activity_Name
ICIS_ACTIVITY State_Code AIR_COMP_MON_DIM State_Code
ICIS_ACTIVITY Comp_Incentive_Code AIR_COMP_MON_DIM Comp_Incentive_Code
ICIS_ACTIVITY Fiscal_Year AIR_COMP_MON_DIM Fiscal_Year
ICIS_ACTIVITY Activity_Status_Code AIR_COMP_MON_DIM Activity_Status_Code
ICIS_ACTIVITY Activity_Status_Date AIR_COMP_MON_DIM Activity_Status_Date
ICIS_ACTIVITY Actual_Begin_Date AIR_COMP_MON_DIM Actual_Begin_Date
ICIS_ACTIVITY Planned_Begin_Date AIR_COMP_MON_DIM Planned_Begin_Date
ICIS_ACTIVITY Actual_End_Date AIR_COMP_MON_DIM Actual_End_Date
ICIS_ACTIVITY Planned_End_Date AIR_COMP_MON_DIM Planned_End_Date
ICIS_ACTIVITY Cancellation_Date AIR_COMP_MON_DIM Cancellation_Date
ICIS_ACTIVITY Cancellation_Reason_Code AIR_COMP_MON_DIM Cancellation_Reason_Code
ICIS_ACTIVITY Duration AIR_COMP_MON_DIM Duration
ICIS_ACTIVITY Multimedia_Flag AIR_COMP_MON_DIM Multimedia_Flag
ICIS_ACTIVITY Sensitive_Data_Flag AIR_COMP_MON_DIM Sensitive_Data_Flag
ICIS_ACTIVITY Internal_Review_Flag AIR_COMP_MON_DIM Internal_Review_Flag
ICIS_ACTIVITY Coordinated_Flag AIR_COMP_MON_DIM Coordinated_Flag
ICIS_ACTIVITY Consolidated_Flag AIR_COMP_MON_DIM Consolidated_Flag
ICIS_ACTIVITY Epa_Assist_Flag AIR_COMP_MON_DIM EPA_Assist_Flag
ICIS_ACTIVITY State_Epa_Flag AIR_COMP_MON_DIM State_EPA_Flag
ICIS_ACTIVITY Air_Lead_Agency_Type_Code AIR_COMP_MON_DIM Air_Lead_Agency_Type_Code
ICIS_ACTIVITY Created_By AIR_COMP_MON_DIM Activity_Created_By
ICIS_ACTIVITY Created_Date AIR_COMP_MON_DIM Activity_Created_Date
ICIS_ACTIVITY Updated_By AIR_COMP_MON_DIM Activity_Updated_By
ICIS_ACTIVITY Updated_Date AIR_COMP_MON_DIM Activity_Updated_Date
ICIS_COMP_MONITOR Area_Of_Evaluation AIR_COMP_MON_DIM Area_Of_Evaluation
ICIS_COMP_MONITOR Weather_Condition AIR_COMP_MON_DIM Weather_Condition
ICIS_COMP_MONITOR Field_Description AIR_COMP_MON_DIM Field_Description
ICIS_COMP_MONITOR Recommendation AIR_COMP_MON_DIM Recommendation
ICIS_COMP_MONITOR Comp_Monitor_Text AIR_COMP_MON_DIM Comp_Monitor_Text
ICIS_COMP_MONITOR Total_Hours AIR_COMP_MON_DIM Total_Hours
ICIS_COMP_MONITOR Communicate_Facility_Flag AIR_COMP_MON_DIM Communicate_Facility_Flag
ICIS_COMP_MONITOR General_Comp_Assistance_Flag AIR_COMP_MON_DIM General_Comp_Assistance_Flag
ICIS_COMP_MONITOR Communicate_Deficiency_Flag AIR_COMP_MON_DIM Communicate_Deficiency_Flag
ICIS_COMP_MONITOR Facility_Action_Flag AIR_COMP_MON_DIM Facility_Action_Flag
ICIS_COMP_MONITOR Comp_Assistant_Tier_Flag AIR_COMP_MON_DIM Comp_Assistant_Tier_Flag
ICIS_COMP_MONITOR Report_Future_Action_Flag AIR_COMP_MON_DIM Report_Future_Action_Flag
ICIS_COMP_MONITOR Nmbr_Of_Day AIR_COMP_MON_DIM Number_Of_Day
ICIS_COMP_MONITOR Joint_Inspection_Flag AIR_COMP_MON_DIM Joint_Inspection_Flag
ICIS_COMP_MONITOR Joint_Lead_Flag AIR_COMP_MON_DIM Joint_Lead_Flag
ICIS_COMP_MONITOR Insp_Rating_Code AIR_COMP_MON_DIM Insp_Rating_Code
ICIS_COMP_MONITOR Observed_Deficiency_Flag AIR_COMP_MON_DIM Observed_Deficiency_Flag
ICIS_COMP_MONITOR Specific_Comp_Assistance_Flag AIR_COMP_MON_DIM Specific_Comp_Assistance_Flag
ICIS_COMP_MONITOR Cafo_Classification_Code AIR_COMP_MON_DIM CAFO_Classification_Code
ICIS_COMP_MONITOR Activity_Outcome_Code AIR_COMP_MON_DIM Activity_Outcome_Code
ICIS_COMP_MONITOR Media_Code AIR_COMP_MON_DIM Media_Code
ICIS_COMP_MONITOR Comp_Monitor_Category_Code AIR_COMP_MON_DIM Comp_Monitor_Category_Code
ICIS_COMP_MONITOR Comp_Assistance_Flag AIR_COMP_MON_DIM Comp_Assistance_Flag
ICIS_COMP_MONITOR Agency_Code AIR_COMP_MON_DIM Agency_Code
ICIS_COMP_MONITOR Joint_Inspection_Purpose_Code AIR_COMP_MON_DIM Joint_Inspection_Purpose_Code
ICIS_COMP_MONITOR State_Statute_Text AIR_COMP_MON_DIM State_Statute_Text
ICIS_COMP_MONITOR Biomonitoring_Method_Code AIR_COMP_MON_DIM Biomonitoring_Method_Code
ICIS_COMP_MONITOR Other_Agency_Initiative_Text AIR_COMP_MON_DIM Other_Agency_Initiative_Text
ICIS_COMP_MONITOR Comp_Monitor_UID AIR_COMP_MON_DIM Comp_Monitor_UID
ICIS_COMP_MONITOR Created_By AIR_COMP_MON_DIM Comp_Mon_Created_By
ICIS_COMP_MONITOR Created_Date AIR_COMP_MON_DIM Comp_Mon_Created_Date
ICIS_COMP_MONITOR Updated_By AIR_COMP_MON_DIM Comp_Mon_Updated_By
ICIS_COMP_MONITOR Updated_Date AIR_COMP_MON_DIM Comp_Mon_Updated_Date
ICIS_CORRECTIVE_ACTION Corrective_Action_Id AIR_COMP_MON_DIM Corrective_Action_ID Duplicate CM record
ICIS_CORRECTIVE_ACTION Corrective_Action_Code AIR_COMP_MON_DIM Corrective_Action_Code for each associated
corrective action.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 76
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 77
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 78
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 79
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 80
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 81
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 82
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 83
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 84
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the source tables and columns from the ICIS-Air operational data source
along with the target tables and columns in the ICIS-Air data warehouse for data in the
Enforcement Actions subject area. The last column contains comments that describe the business
rules or other criteria used to generate that column. This is the primary source of instructions for
building the Informatica workflows.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 85
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Operational Source table & column Data Warehouse target table and column
Source Table Source Column Target Table Target Column Comment
AIR_EA_DIM Air_EA_Key Uniquely created with
row
ICIS_ACIVITY Activity_ID AIR_EA_DIM Activity_ID
ICIS_ACIVITY Activity_Type_Code AIR_EA_DIM Activity_Type_Code
ICIS_ACIVITY Air_LCON_Code AIR_EA_DIM Air_LCON_Code
ICIS_ACIVITY Activity_Name AIR_EA_DIM Activity_Name
ICIS_ACIVITY State_Code AIR_EA_DIM State_Code
ICIS_ACIVITY Comp_Incentive_Code AIR_EA_DIM Comp_Incentive_Code
ICIS_ACIVITY Fiscal_Year AIR_EA_DIM Fiscal_Year
ICIS_ACIVITY Activity_Status_Code AIR_EA_DIM Activity_Status_Code
ICIS_ACIVITY Actual_Begin_Date AIR_EA_DIM Actual_Begin_Date
ICIS_ACIVITY Activity_Status_Date AIR_EA_DIM Activity_Status_Date
ICIS_ACIVITY Planned_Begin_Date AIR_EA_DIM Planned_Begin_Date
ICIS_ACIVITY Actual_End_Date AIR_EA_DIM Actual_End_Date
ICIS_ACIVITY Planned_End_Date AIR_EA_DIM Planned_End_Date
ICIS_ACIVITY Cancellation_Date AIR_EA_DIM Cancellation_Date
ICIS_ACIVITY Cancellation_Reason_Code AIR_EA_DIM Cancellation_Reason_Code
ICIS_ACIVITY Duration AIR_EA_DIM Duration
ICIS_ACIVITY Total_Hours AIR_EA_DIM Total_Hours
ICIS_ACIVITY Multimedia_Flag AIR_EA_DIM Multimedia_Flag
ICIS_ACIVITY Sensitive_Data_Flag AIR_EA_DIM Sensitive_Data_Flag
ICIS_ACIVITY Internal_Review_Flag AIR_EA_DIM Internal_Review_Flag
ICIS_ACIVITY Coordinated_Flag AIR_EA_DIM Coordinated_Flag
ICIS_ACIVITY Consolidated_Flag AIR_EA_DIM Consolidated_Flag
ICIS_ACIVITY EPA_Assist_Flag AIR_EA_DIM EPA_Assist_Flag
ICIS_ACIVITY State_EPA_Flag AIR_EA_DIM State_EPA_Flag
ICIS_ACIVITY Air_Lead_Agency_Type_Code AIR_EA_DIM Air_Lead_Agency_Type_Code
ICIS_ACIVITY Created_By AIR_EA_DIM Created_By
ICIS_ACIVITY Created_Date AIR_EA_DIM Created_Date
ICIS_ACIVITY Updated_By AIR_EA_DIM Updated_By
ICIS_ACIVITY Updated_Date AIR_EA_DIM Updated_Date
ICIS_ENFORCEMENT Referred_Office_ID AIR_EA_DIM Referred_Office_ID
ICIS_ENFORCEMENT Penalty_Sought_Amt AIR_EA_DIM Penalty_Sought_Amt
ICIS_ENFORCEMENT Judicial_District_Code AIR_EA_DIM Judicial_District_Code
ICIS_ENFORCEMENT Cost_Recovery_Sought_Amt AIR_EA_DIM Cost_Recovery_Sought_Amt
ICIS_ENFORCEMENT Enf_Name AIR_EA_DIM Enf_Name
ICIS_ENFORCEMENT Enf_Identifier AIR_EA_DIM Enf_Identifier
ICIS_ENFORCEMENT Court_Ent_Name AIR_EA_DIM Court_Ent_Name
ICIS_ENFORCEMENT DOJ_Docket_Nmbr AIR_EA_DIM DOJ_Docket_Number
ICIS_ENFORCEMENT DOJ_Enf_Name AIR_EA_DIM DOJ_Enf_Name
ICIS_ENFORCEMENT Cost_Of_Hearing_Proposed AIR_EA_DIM Cost_Of_Hearing_Proposed
ICIS_ENFORCEMENT Cost_Of_Hearing_Actual AIR_EA_DIM Cost_Of_Hearing_Actual
ICIS_ENFORCEMENT Legal_ID AIR_EA_DIM Legal_ID
ICIS_ENFORCEMENT Enf_Outcome_Code AIR_EA_DIM Enf_Outcome_Code
ICIS_ENFORCEMENT Geo_Initiative_Narrative AIR_EA_DIM Geo_Initiative_Narrative
ICIS_ENFORCEMENT Voluntary_Self_Disclosure_Flag AIR_EA_DIM Voluntary_Self_Disclosure_Flag
ICIS_ENFORCEMENT Enf_Summary_Text AIR_EA_DIM Enf_Summary_Text
ICIS_ENFORCEMENT Total_Penalty_Assessed_Amt AIR_EA_DIM Total_Penalty_Assessed_Amt
ICIS_ENFORCEMENT Total_Cost_Recovery_Amt AIR_EA_DIM Total_Cost_Recovery_Amt
ICIS_ENFORCEMENT Total_Comp_Action_Amt AIR_EA_DIM Total_Comp_Action_Amt
ICIS_ENFORCEMENT Core_Flag AIR_EA_DIM Core_Flag
ICIS_ENFORCEMENT Overfile_Flag AIR_EA_DIM Overfile_Flag
ICIS_ENFORCEMENT Multiregional_Flag AIR_EA_DIM Multiregional_Flag
ICIS_ENFORCEMENT Archive_Flag AIR_EA_DIM Archive_Flag
ICIS_ENFORCEMENT Referred_Date AIR_EA_DIM Referred_Date
ICIS_ENFORCEMENT Filed_Date AIR_EA_DIM Filed_Date
ICIS_ENFORCEMENT Notice_Pleading_Flag AIR_EA_DIM Notice_Pleading_Flag
ICIS_ENFORCEMENT Last_Updated_By AIR_EA_DIM Last_Updated_By
ICIS_ENFORCEMENT Last_Updated_Date AIR_EA_DIM Last_Updated_Date
ICIS_ENFORCEMENT Agency_Name AIR_EA_DIM Agency_Name
ICIS_ENFORCEMENT State_Law_Section_Violated AIR_EA_DIM State_Law_Section_Violated
ICIS_ENFORCEMENT Other_Water_Program_Violated AIR_EA_DIM Other_Water_Program_Violate
d
ICIS_ENFORCEMENT Achieved_Date AIR_EA_DIM Achieved_Date
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 86
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 87
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 88
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 89
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 90
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 91
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 92
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 93
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The table below shows the source tables and columns from the ICIS-Air operational data source
along with the target tables and columns in the ICIS-Air data warehouse for data in the Case File
subject area. The last column contains comments that describe the business rules or other criteria
used to generate that column. This is the primary source of instructions for building the ELT
workflows.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 94
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Operational Source table & column Data Warehouse target table and column
Source Table Source Column Target Table Target Column Comment
AIR_CASE_FILE_DIM Air_Case_File_Key Uniquely created with
row
ICIS_ACITVITY Activity_Type_Code AIR_CASE_FILE_DIM Activity_Type_Code
ICIS_ACITVITY Region_Code AIR_CASE_FILE_DIM Region_Code
ICIS_ACITVITY Air_LCON_Code AIR_CASE_FILE_DIM Air_LCON_Code
ICIS_ACTIVITY Activity_Name AIR_CASE_FILE_DIM Activity_Name
ICIS_ACITVITY State_Code AIR_CASE_FILE_DIM State_Code
ICIS_ACITVITY Comp_Incentive_Code AIR_CASE_FILE_DIM Comp_Incentive_Code
ICIS_ACTIVITY Fiscal_Year AIR_CASE_FILE_DIM Fiscal_Year
ICIS_ACITVITY Activity_Status_Code AIR_CASE_FILE_DIM Activity_Status_Code
ICIS_ACITVITY Actual_Begin_Date AIR_CASE_FILE_DIM Actual_Begin_Date
ICIS_ACTIVITY Activity_Status_Date AIR_CASE_FILE_DIM Activity_Status_Date
ICIS_ACITVITY Planned_Begin_Date AIR_CASE_FILE_DIM Planned_Begin_Date
ICIS_ACITVITY Actual_End_Date AIR_CASE_FILE_DIM Actual_End_Date
ICIS_ACTIVITY Planned_End_Date AIR_CASE_FILE_DIM Planned_End_Date
ICIS_ACITVITY Cancellation_Date AIR_CASE_FILE_DIM Cancellation_Date
ICIS_ACITVITY Cancellation_Reason_Code AIR_CASE_FILE_DIM Cancellation_Reason_Code
ICIS_ACTIVITY Duration AIR_CASE_FILE_DIM Duration
ICIS_ACITVITY Total_Hours AIR_CASE_FILE_DIM Total_Hours
ICIS_ACITVITY Multimedia_Flag AIR_CASE_FILE_DIM Multimedia_Flag
ICIS_ACTIVITY Sensitive_Data_Flag AIR_CASE_FILE_DIM Sensitive_Data_Flag
ICIS_ACITVITY Internal_Review_Flag AIR_CASE_FILE_DIM Internal_Review_Flag
ICIS_ACITVITY Coordinated_Flag AIR_CASE_FILE_DIM Coordinated_Flag
ICIS_ACTIVITY Consolidated_Flag AIR_CASE_FILE_DIM Consolidated_Flag
ICIS_ACITVITY Epa_Assist_Flag AIR_CASE_FILE_DIM EPA_Assist_Flag
ICIS_ACITVITY State_Epa_Flag AIR_CASE_FILE_DIM State_EPA_Flag
ICIS_ACITVITY Air_Lead_Agency_Type_Code AIR_CASE_FILE_DIM Air_Lead_Agency_Type_Code
ICIS_COMP_DETERMINATION Activity_ID AIR_CASE_FILE_DIM Activity_ID
ICIS_COMP_DETERMINATION Comp_Determination_Type_Code AIR_CASE_FILE_DIM Comp_Determination_Type_Code
ICIS_COMP_DETERMINATION Geographic_Issue_Code AIR_CASE_FILE_DIM Geographic_Issue_Code
ICIS_COMP_DETERMINATION Followup_Action_Code AIR_CASE_FILE_DIM Followup_Action_Code
ICIS_COMP_DETERMINATION Discovery_Method_Code AIR_CASE_FILE_DIM Discovery_Method_Code
ICIS_COMP_DETERMINATION Violation_Class_Code AIR_CASE_FILE_DIM Violation_Class_Code
ICIS_COMP_DETERMINATION Estimated_Cost_To_Comply AIR_CASE_FILE_DIM Estimated_Cost_To_Comply
ICIS_COMP_DETERMINATION NPL_Flag AIR_CASE_FILE_DIM NPL_Flag
ICIS_COMP_DETERMINATION Comp_Determination_Date AIR_CASE_FILE_DIM Comp_Determination_Date
ICIS_COMP_DETERMINATION Delegated_State_Flag AIR_CASE_FILE_DIM Delegated_State_Flag
ICIS_COMP_DETERMINATION Discovery_Date AIR_CASE_FILE_DIM Discovery_Date
ICIS_COMP_DETERMINATION Enf_Admin_Order_Flag AIR_CASE_FILE_DIM Enf_Admin_Order_Flag
ICIS_COMP_DETERMINATION Description_Text AIR_CASE_FILE_DIM Description_Text
ICIS_COMP_DETERMINATION Addr_Ctrl_Action_Type_Date AIR_CASE_FILE_DIM Addr_Ctrl_Action_Type_Date
ICIS_COMP_DETERMINATION No_Further_Action_Type_Date AIR_CASE_FILE_DIM No_Further_Action_Type_Date
ICIS_COMP_DETERMINATION Initiated_Action_Type_Date AIR_CASE_FILE_DIM Initiated_Action_Type_Date
ICIS_COMP_DETERMINATION Hq_Action_Ctrl_Approval_Flag AIR_CASE_FILE_DIM HQ_Action_Ctrl_Approval_Flag
ICIS_COMP_DETERMINATION Hq_Action_Ctrl_Approval_Date AIR_CASE_FILE_DIM HQ_Action_Ctrl_Approval_Date
ICIS_COMP_DETERMINATION Nei_Comment_Text AIR_CASE_FILE_DIM NEI_Comment_Text
ICIS_COMP_DETERMINATION Comp_Determination_UID AIR_CASE_FILE_DIM Comp_Determination_UID
ICIS_COMP_DETERMINATION Other_Program_Text AIR_CASE_FILE_DIM Other_Program_Text
ICIS_COMP_DETERMINATION Superseded_By AIR_CASE_FILE_DIM Superseded_By
ICIS_COMP_DETERMINATION Enf_Response_Policy_Code AIR_CASE_FILE_DIM Enf_Response_Policy_Code
ICIS_COMP_DETERMINATION Created_By AIR_CASE_FILE_DIM Created_By_Comp_Det
ICIS_COMP_DETERMINATION Created_Date AIR_CASE_FILE_DIM Created_Date_Comp_Det
ICIS_COMP_DETERMINATION Updated_By AIR_CASE_FILE_DIM Updated_By_Comp_Det
ICIS_COMP_DETERMINATION Updated_Date AIR_CASE_FILE_DIM Updated_Date_Comp_Det
AIR_CASE_FILE_VIOLATION HPV_Day_Zero_Date AIR_CASE_FILE_DIM Earliest_HPV_Day_Zero_Date Get the minimum
HPV_Day_Zero_Date
from the rows in the
AIR_CASE_FILE_VIOLA
TION table using the
get_min_hpv_day_zer
o_date stored proc.
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 95
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 96
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 97
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 98
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 99
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 100
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 101
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 102
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 103
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 104
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 105
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 106
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
APPENDIX B: STANDARD REPORTS LAYOUTS
The following are the notional standard design layouts for the Standard Reports described in Section 5. These layouts show the relative placement of
the elements in the report and do not represent the final formatting.
The follow is the list of Standard reports that will be developed first:
• Figure B.1 - Critical Data Element Report
• Figure B.2 - Comprehensive Compliance Monitoring Strategy (CMS) Report
• Figure B.3 - Sources with No CMS Flag Report
• Figure B.4 - Universe of Federally Reportable Facilities Reports
• Figure B.5 - Sources within Nonattainment Areas
• Figure B.6 - Activities Report
• Figure B.7 - Facilities Reporting Violations
• Figure B.8 - List of Active HPVs/FRVs/Non-FRVs
• Figure B.9 - Notice of Violation Report
• Figure B.10 - Enforcement Action Report
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 107
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 1 Critical Data Element Report
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Added Facilities
Facility Name: Facility 1 Facility ID: 1234567890 FRS ID: 1234567890
Default Classification: 123ABC, Non-Critical
Primary SIC: ABC, SIC Name
Primary NAICS: XYZ, NAICS Name
Government Ownership: 987, EPA XYZ
Current Default Classification: 123ABC, Non-Critical
Current Programs
Current Operating Current Shutdown
Air Program Status Current Start Date Date
Program 1 Active 02/01/2002 12/31/2015
Program 2 Active 02/02/2002 12/31/2015
Program 3 Active 02/03/2002 12/31/2015
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 109
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Updated Facilities
Facility ID: 1234509876 FRS ID: 1234509876 Facility Name History
Default Classification: 123ABC, Non-Critical Previous Facility Name Date Name Changed
Facility Name: Facility 4 Facility A 06/01/2002
Facility B 01/01/2005
Primary SIC: ABC, SIC Name Facility C 12/31/2007
Primary NAICS: XYZ, NAICS Name
Government Ownership: 987, EPA XYZ
Current Default Classification: 123ABC, Non-Critical
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 110
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Current Operating Current Shutdown
Program Name Current Start Date Status Date
Program 2 01/01/2002 Stat 2 12/31/2015
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 111
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 112
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Updated CMS
Date
Reason for CMS Active on Removed CMS CMS Current Reason for
CMS Source Changing Minimum CMS Effective Agency from Agency Origination CMS Start Next FCE Start CMS Changing
Category CMS Frequency Frequency CMS Plan CMS Plan Date Date Due Date Date Status CMS
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 113
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Law/Section/Program
Federal Statute Law Section Program
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 114
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 115
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Agency Sensitive Data? No
Integrated Compliance Information System ICIS-Air
Critical Data Element Report
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Milestones
Milestone
Enforcement Action Milestone Actual Date
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 116
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 2 Comprehensive CMS Report
The Environmental Protection Sensitive Data? No
Agency
Comprehensive Compliance ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 118
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Sensitive Data? No
Agency
Comprehensive Compliance ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 119
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Sensitive Data? No
Agency
Comprehensive Compliance ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Facility Default CMS Date Last CMS CMS CMS Reason for CMS CMS Effective
Facility ID Name Classification Category FCE Identifier Category Status Changing CMS Frequency Frequency
1234567890 Facility 4 123ABC, Non- S 80% 06/01/2013 CMS M, Mega- Active Added New Info 2 years 2 years
Critical Synthetic ID123 Site
Minor
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 120
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Report
FACILITY NAME: <Facility Name> CITY: <City> REPORT DATE: 08/15/2013
FACILITY ID: <Facility ID> STATE: <State> MODIFIED DATE: 08/10/2013
FACILITY TYPE: <Facility Type> COUNTY: <County> CREATED BY: Scott Tiger
LCON: <LCON> REGION: <Region> START DATE: 01/01/2013
CURRENT OPERATING STATUS: <Operating Status> TRIBAL LAND: <Tribal Land> END DATE: 12/12/2013
CURRENT DEFAULT <Classification> NONATTAINMENT <Nonattainment area>
CLASSIFICATION: AREA:
CURRENT EPA <EPA Classification> CURRENT <Pollutant>
CLASSIFICATION: POLLUTANTS:
DELEGATED AGENCY <DA Classification> AIR PROGRAMS & <Program>
CLASSIFICATION: SUBPARTS: <Subpart>
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 121
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 4 Universe of Federally Reportable Facilities Report
The Environmental Protection Sensitive Data? No
Agency
Universe of Federally ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 122
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 5 Sources within Nonattainment Areas
The Environmental Protection Sensitive Data? No
Agency
Sources within ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Nonattainment Areas
FACILITY NAME: <Facility Name> CITY: <City> REPORT DATE: 08/15/2013
FACILITY ID: <Facility ID> STATE: <State> MODIFIED DATE: 08/10/2013
FACILITY TYPE: <Facility Type> COUNTY: <County> CREATED BY: Scott Tiger
LCON: <LCON> REGION: <Region> START DATE: 01/01/2013
CURRENT OPERATING STATUS: <Operating Status> TRIBAL LAND: <Tribal Land> END DATE: 12/12/2013
CURRENT DEFAULT <Classification> NONATTAINMENT <Nonattainment area>
CLASSIFICATION: AREA:
CURRENT EPA <EPA Classification> CURRENT <Pollutant>
CLASSIFICATION: POLLUTANTS:
DELEGATED AGENCY <DA Classification> AIR PROGRAMS & <Program>
CLASSIFICATION: SUBPARTS: <Subpart>
Pollutants
Attainment/Nonattainment Date of Extraction from
Pollutant Indicator Greenbook
Ozone 020 Nonattainment 02/01/2013
Carbon Dioxide 020 Nonattainment 03/15/2013
Chlorine 020 Nonattainment 04/30/2013
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 123
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 6 Activities Report
The Environmental Protection Sensitive Data? No
Agency
Activities Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Air Facility
Facility ID: 1234567890 FRS ID: 1234567890 Current Programs
Default Classification: 123ABC, Non-Critical Current Current
Facility Name: Facility 1 Operating Current Shutdown Default Applicable
Air Program Status Start Date Date Classification Subparts
Program 1 Active 02/01/2002 12/31/2015
Program 2 Active 02/02/2002 12/31/2015
Program 3 Active 02/03/2002 12/31/2015
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 124
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Sensitive Data? No
Agency
Activities Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Air Programs
Program not on
Facility
Program Indicator
Program 1 N
Program 2 Y
Program 3 N
Program 4 N
Pollutants
Pollutant not
on Facility
Pollutant Indicator
Pollutant 1 Y
Pollutant 2 N
Pollutant 3 Y
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 125
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Sensitive Data? No
Agency
Activities Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Stack Tests
Data
Stack Test Date Test Imported
Unique Results were from External
Identifier Reviewed System Pollutant Tested Test Result
ST09987676 08/01/2013 001 Pollutant 1 001 Negative
Air Programs
Program not on
Facility
Program Indicator
Program 1 N
Program 2 Y
Program 3 N
Program 4 N
Pollutants
Pollutant not
on Facility
Pollutant Indicator
Pollutant 1 Y
Pollutant 2 N
Pollutant 3 Y
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 126
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
The Environmental Protection Sensitive Data? No
Agency
Activities Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Air Programs
Program not on
Facility
Program Indicator
Program 1 N
Program 2 Y
Program 3 N
Program 4 N
Pollutants
Pollutant not
on Facility
Pollutant Indicator
Pollutant 1 Y
Pollutant 2 N
Pollutant 3 Y
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 127
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 7 Facilities Reporting Violations
The Environmental Protection Sensitive Data? No
Agency
Facilities Reporting Violations ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Violation Types
Violation Enforcement
Violation Type Response Policy Start Date End Date
AVF Type 1 AVF TPI 1 02/01/2013 05/30/2013
AVF Type 2 AVF TPI 2 03/15/2013 06/16/2013
AVF Type 3 AVF TPI 3 04/30/2013 08/05/2013
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 128
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 8 List of Active HPVs-FRVs-Non FRVs
The Environmental Protection Sensitive Data? No
Agency
List of ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Violations
Enforcement Response Other Program Program not on Pollutant not on
Violation Type Policy Program Text Facility Indicator Pollutant Facility Indicator Start Date End Date
AVF Type 1 AVF TPI 1 Program 1 N Pollutant 1 Y 02/01/2013 05/30/2013
AVF Type 2 AVF TPI 2 Program 2 Y Pollutant 2 N 03/15/2013 06/16/2013
AVF Type 3 AVF TPI 3 Program 3 N Pollutant 3 Y 04/30/2013 08/05/2013
National Initiatives
National Initiatives
Nat Init 1
Nat Init 2
Nat Init 3
Pathway Data
Discovery Action Discovery Action Notification Action Notification Action Addressing Action Addressing Action Resolving Action Resolving Action
Type Date Type Date Type Date Type Date
Disc Act Type 1 01/01/2013 Not Act Type 1 01/15/2013 Addr Act Type 1 02/01/2013 Res Act Type 1 02/15/2013
Disc Act Type 2 05/01/2013 Not Act Type 2 06/01/2013 Addr Act Type 2 07/15/2013 Res Act Type 2 08/15/2013
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 129
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Additional Data
User Defined Field User Defined Field User Defined Field User Defined Field User Defined Field User Defined Field
Comments 1 2 3 4 5 6
Comment 1
Comment 2
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 130
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 9 Notice of Violation Report
The Environmental Protection Sensitive Data? No
Agency
Notice of Violation Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Notices
Notification
Notification Milestone
Notification Action Type Action Date Indicator
Action Type 1 02/01/2013 Yes
Action Type 2 03/15/2013 Yes
Action Type 3 04/30/2013 No
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 131
OFFICE OF ENFORCEMENT AND COMPLIANCE ASSURANCE
Figure B- 10 Enforcement Action Report
The Environmental Protection Sensitive Data? No
Agency
Enforcement Action Report ICIS-Air
INTEGRATED COMPLIANCE INFORMATION SYSTEM
Air Programs
Program not on Applicable
Program Facility Indicator Subparts
Program 1 N Subpart 1
Program 2 Y Subpart 2
Program 3 N Subpart 3
Program 4 N Subpart 4
Pollutants
Pollutant not on
Pollutant Facility Indicator
Pollutant 1 Y
Pollutant 2 N
Pollutant 3 Y
Milestones
Milestone Action
Milestone Type Date
Milestone Type 1 02/01/2013
Milestone Type 2 03/15/2013
Milestone Type 3 04/30/2013
ICIS-AIR DW, ETL, BO UNIVERSE, AND STANDARD REPORTS DETAILED DESIGN DOCUMENT REVISED 132