Date post: | 20-Dec-2015 |
Category: |
Documents |
View: | 218 times |
Download: | 2 times |
TheFacility Registry
System
IT FORUM
Boston, MA
The Facility Registry System
Facility Registry System
Creates a single, integrated set of facility identification information Environmental Interests Locational Coordinates Affiliation
Provides links to EPA’s media information systems
Conforms to the Data Standard
QA/QC
The Agency Repository of Places of Environmental Interest
Why is FRS Needed? FRS links facility data across program systems,
which satisfies EPA’s business need to identify: the regulated facilities within a particular sector the location of a facility the different permits and regulations that apply to a
particular facility all facilities owned by a particular corporation
FRS provides essential support for applications that rely on integrated views of facilities: Public Access (Envirofacts, EnviroMapper, ECHO) Enforcement (IDEA, OTIS)
High Level Data Model
IndividualIndividual
Organization
Mailing AddressAffiliationAffiliation
SIC/NAICSSIC/NAICS
Environmental Interest
Environmental Interest
GeographicCoordinatesGeographicCoordinates
Relationship:onemany
Facility/SiteFacility/Site
FRS – All about key identifiers
Name and Location Contact and Organization / Mailing Address Program Identifiers Latitude / Longitude Other key informational elements
HUC, Indian country, Federal Facilities
Environmental Justice Environmental Interest Type Industrial Codes
Online Targeting Information System
(OTIS)
National EmissionInventory
(NEI) Central DataExchange
(CDX)
Integrated Compliance Information System
(ICIS)
Integrated Data for Enforcement Analysis
(IDEA)
States
Envirofacts(Direct Connection)
Portal Project
Clean Air Markets Division Business System
(CAMDBS)
FederalFacilities
AIRS FacilitySubsystem
(AFS)
These activities rely on FRS data integration!These activities rely on FRS data integration!
FRS Dependencies
Goals Ultimate Goal
Improve Data Quality and Integration to better serve our Customers
Measured Goals for CY 200690% Lat Long
Currently at 62% documented
3 more National Data Sets Added 3 – BRAC, FRP, and NCES (Schools)
7 More State Exchanges Have 1 (AR), rest in the pipeline
FRS Goals CY 2006
Adding State and Program Exchanges
A
We’ve added AR this year and are moving towards Production in all States in Orange!
National Datasets:
DOD BRACs
Facility Response Plan
Schools
Working towards:
E-Grid
UIC, STORET
Early Snapshot of FRS Locational Data
Feb 2006
Snapshot of FRS Location Data
August 2006
Examples of Locational Information Captured in FRS
Collection Method Address Matching GPS Map interpolation
Accuracy Range 1 meter (GPS) and greater
Reference Point Description Plant Entrance Water Release Pipe Air Release Stack, etc
Locational Improvement
Inaccurate data impedes our work to complete the mission.
(No Longer Accept ZIP Code Centroids)
Better data equals better analysis
Strategies to Locational Improvement
Partnerships Leverage Exchange Network with States Work closely with Regions and Program Offices Work with other Agencies and Departments
Data Data Stewardship and Data Quality Reviews Target critical data for consolidated acquisition/access Integrated Error Correction Process
Tools and Technologies Improved Data Management Geo-Code Bounding Boxes
FRS Universe
1,684,896 FRS 1,913,469 FRS
May 2005 Baseline August,20 2006 Baseline
51% without latitude/longitude859,042 records
49% with latitude/longitude825,854 records
62% withlatitude/longitude1,157,041 records
37.5% withoutlatitude/longitude777,925 records
MASS CLEAN UPRemoved locational points outside of U.S.
Land/Territories and Zip Code centriod points previously entered by contractors
1.9M unique records linking to 2.6M+ program interests from:
PCS-Majors & Minors NEI-2002 CERCLIS NCES TRI RCRAInfo RMP P-track BRACs
AIRS-AFS Brownfields Properties RADInfo ICIS (Docket) NCDB AIRS/AQS SDWIS CAMDBS FRP
National Programs August 2006
State Programs CaSWIS ECOMAP FIS GEIMS HI-ECS HI-SW HI-UST HWTS-
DATAMART IDNR_EFD IN-FRS KS-FP MA-EPICS
MD-EPSC MD-PEMIS MD-RCRA ME-EFIS MN-DELTA MO-DNR MS-ENSITE MT-CEDARS NC-FITS ND-FP NE-IIS NH-DES NJ-NJEMS
NM-TEMPO OH-CORE OK-FMS OR-DEQ PA-EFACTS SC-EFIS SWIS UORS WA-DO EFSIS WI-ESR AR-FRS
Still Missing!
National Sets: ICIS- NPDES : A Current RefreshSTORETSDWIS: A Better Mapped FileUIC
States:FL, AL, GA, KY, TN, TX
Other Data Sets and Key Identifiers of Interest? RAD Sites Biological Waste Sites 100Km Border Flag Criminal Cases on Facilities Others?
Partners with Other Agencies/Gov’t Entities
Dept Homeland Security Interested in many of our
data types Department of Education
100K Schools SBA- Small Business Flag Interested in DOE, DOI,
DOD, USDA for sharing
Serving Our
Customers
Who are our Customers?
First Responders have Competing Needs:Layers versus IntegrationQuality versus AccessServices versus Databasing
Data Requirements: Are They Fully Known? Understood?
However, We Do Have Other!
Customer Expectations:Data Quality Vs. Access Sources Refreshes Validation
Feature Services Web Services Clip and Ship Node Clients FTP Account Access
Requests from First Responders
Break down Stove Pipe Ownership of Data - have the Programs buy into the Enterprise Architecture.
Improve data ownership - data received from critical EPA Data sets do not conform to adopted data standards.
Ensure data consistency - Program Data Managers creating different views of data depending on the sharing partners.
Provide timely and accurate data according to Emergency Priority.
Tools Assisting FRS FRS Is the Agency Architecture Enterprise
Solution to “Stovepiped” data Integrator of environmental data for places:
Tools FRS Merge Applications Manual Review of Duplicate Candidates by Data
Stewards Data Quality Validity Reports Enterprise Site Locator Tool Integrated Error Correction Process Query Tools Web Services- FRS US thru CDX Feature Services
FRS Feature and Web Services
Allows FRS data to be queried both spatially and non-spatially
Allows dynamic interface Clip and Ship capabilities
Production of Shapefiles that can be used to create of new feature instance of the dataset
Points and Polygons can (will) be stored.