Cross Program Data Exchanges

1. Cross Program Data Exchanges Facility Identification (FACID) 3.0 These are the titles of the session and then the FRS presentationThese are the titles of the session and then the FRS presentation

2. FACID 3.0 Overview Supports all existing (FACID 2.3) Facility Identification Network web service capabilities Add new Network web services for publishing applications Being Used for Facility Data Cleanup Tool exchange to and from FRS to data stewards Updated schema Better use of shared components More modular approach Support for complex geometries (polygons and lines in addition to points) in the Exchange Network recommended geospatial format (GeoRSS GML) All of the service capabilities from the FACID 2.3 services are supported in 3.0 The existing query service functionality is encompassed within the 3.0 services (i.e., 2.3 had GetFacilityByZipCode/CityName/SICCode, but all of those are covered by the 3.0 GetFacility with the option to specify zip code, city, and/or SIC code The only exception is data content where 3.0 does not have parent company and DUNS data elements (don�t know if we want to talk about that here or not) In addition to supporting the existing services, there are new services that return a much smaller payload to support real-time mapping and query applications � For example: GetFacilityList provides just the name, address, location (point), and URL for a �click through� functionality GetFacilityCount provides a count of facilities that match the query The new regional ArcGIS tool for QA and location/address correction will use FACID 3.0 and the Exchange Network to both extract data from FRS and to send it back to FRS Updated Schema As one of the first adopters in the Exchange Network, many new shared components and standards have been adopted since FRS was first in the EN and this update makes use of those new standards where possible. The schema was streamlined to take advantage of the shared components and reuse those components in multiple places within the schema The EN�s new geospatial guidelines provide a ready-made module to incorporate the GeoRSS GML shared component which not only supports the current point geometry in FRS but also the lines and polygons (complex geometry) to support the higher quality data collected by data stewards All of the service capabilities from the FACID 2.3 services are supported in 3.0 The existing query service functionality is encompassed within the 3.0 services (i.e., 2.3 had GetFacilityByZipCode/CityName/SICCode, but all of those are covered by the 3.0 GetFacility with the option to specify zip code, city, and/or SIC code The only exception is data content where 3.0 does not have parent company and DUNS data elements (don�t know if we want to talk about that here or not) In addition to supporting the existing services, there are new services that return a much smaller payload to support real-time mapping and query applications � For example: GetFacilityList provides just the name, address, location (point), and URL for a �click through� functionality GetFacilityCount provides a count of facilities that match the query The new regional ArcGIS tool for QA and location/address correction will use FACID 3.0 and the Exchange Network to both extract data from FRS and to send it back to FRS Updated Schema As one of the first adopters in the Exchange Network, many new shared components and standards have been adopted since FRS was first in the EN and this update makes use of those new standards where possible. The schema was streamlined to take advantage of the shared components and reuse those components in multiple places within the schema The EN�s new geospatial guidelines provide a ready-made module to incorporate the GeoRSS GML shared component which not only supports the current point geometry in FRS but also the lines and polygons (complex geometry) to support the higher quality data collected by data stewards

3. Facility Data Submission to FRS Both the FACID 2.3 and the FACID 3.0 schemas will be supported for the immediate future, with a planned phase out of FACID 2.3 after partners have converted Complex geometries can be submitted via GeoRSS GML standard Enhanced submission feedback for FACID 3.0 submissions 42 states and 3 tribes currently exchange data with FRS via the Exchange Network

4. States Exchanging Data with FRS Plus Hawaii but not AlaskaPlus Hawaii but not Alaska

5. Exchange Network Facility Query New web service requests to facilitate real time query and mapping through the Exchange Network �Lite� schema for improved performance Get Facility Count Returns just the number of facilities Get Facility List Returns only name, address, location, and URL link to a report with detailed information Full support for �heavy� schema also for full data exchange of all data elements

7. Why Move to 3.0? Real-time query and mapping with lightweight payloads Ability to support regional query and mapping applications directly from state facility databases Support for complex geometry Supports multiple alternative names and multiple geometries for each facility or interest Improved feedback for data submissions 2.3 will be phased out eventually

8. What�s Next? Assistance to convert from FACID 2.3 to FACID 3.0 FACID 3.1 Adding optional additional components to support: Facility DUNS number Parent company information Geospatial data for sub-facility elements (i.e., particular stacks or pipes or other environmental interests) Will not have any impact on plug-ins for FACID 3.0; all elements will be optional and additive meaning any 3.0 compliant document will also be 3.1 compliant