fgdc homeland security working group dhs enterprise modeling briefing

FGDC Homeland Security Working GroupDHS Enterprise Modeling Briefing

April 27, 2006

Geospatial Enterprise Data Modeling 2

GMOGMO

Outline Business Requirements Technical Approach Modeling Considerations Task Description Vetting Process Proposed Schedule Group Discussion


GMOGMO

Business Requirements Support DHS Business Missions Enable Data Exchange among DHS Components Enable ETL Processes with States & Locals Comply with FGDC Standards and Guidelines Align with FEA Geospatial Profile Align with DHS Enterprise Architecture (EA) Align with DHS Geospatial Enterprise Architecture (GEA) Align with DHS Geospatial Data Warehousing Strategy Be Public Accessible (Not FOUO) Leverage Existing Data Models Have Sufficient Documentation for Future Implementation


GMOGMO

Technical Approach Start with ESRI Bluebook Data Model Use FGDC Framework Model to Describe 7 Framework Data Layers:

Cadastral data describe the geographic extent of past, current, and future right, title, and interest in real property, including above, surface, and below ground and water, and the conceptual structure to support the description of that geographic extent

Digital Orthoimages are georeferenced images of the Earth's surface for which image object displacement caused by sensor orientation, sensor distortions, and terrain relief has been removed.

Elevation data may be modeled in various forms, such as in an evenly spaced grid or as irregularly spaced points (triangulated irregular network, hypsography, or mass points).

Geodetic control provides a common, consistent, and accurate reference system for establishing coordinates for all geographic data.

Governmental Unit Boundaries and other geographic area boundaries establishes the content requirements for the collection and interchange of governmental unit and other legal entity boundary data to facilitate the maintenance and use of that information.

Hydrology includes surface water features such as lakes, ponds, streams or rivers, canals, oceans, and shorelines.

Transportation data are used to model the geographic locations, interconnectedness, and characteristics of the transportation system.


GMOGMO

Technical Approach Use NIEM/URISA Address Data Model to Describe

Addresses and Names Use NIEM/EDXL Data Model to Describe Emergency

Operations Leverage HSIP/NADB/NIEM Data Model to Describe

Structure and Critical Infrastructure Adopt the Bluebook Data Model (assuming it is latest

and greatest from ESRI) for the rest of the Relevant Data Layers


GMOGMO

Modeling Considerations Select National Standard-based Data Constructs over Proprietary Data

Constructs Select Semantic Rich Data Constructs (see examples) Use UML (Unified Modeling Language) for Logical Model

FGDC Guideline: “The use of UML class diagrams is an application-neutral approach to depict the inherent

description of and relationships among data entities. These diagrams should neither be interpreted as requiring object-oriented implementation – methods or interfaces are not typically shown on these data classes – nor should they be interpreted as representing tables in relational databases. Instead, the UML classes should be used as the basis for translation to and from internal organization data stores and applications. UML modeling environments typically support conversion of logical UML models into implementations in various programming environments through rule-based transforms.”

Each of the FGDC Framework schema expressed in the Unified Modeling Language (UML) according to ISO 19109, Geographic information – Rules for application schema, and its normative references. The application schema specifies, as appropriate, the feature types, attribute types, attribute domain, feature relationships, spatial representation, data organization, and metadata that define the information content of a dataset.

Follow UML Practices in the FGDC Framework Standard, e.g. use <<stereotype>> as an semantic extension mechanism for existing UML concepts.

Follow Guideline of ISO 19103 (Conceptual Schema Language) ISO 19103 provides rules and guidelines for the use of a conceptual schema language. The

chosen conceptual schema language is the Unified Modeling Language (UML). It provides a profile of UML for use with geographic information. In addition, it provides guidelines on how UML should be used to create standardized geographic information and service models.

The Logical Model has a package of packages hierarchical structure following FGDC practice.


GMOGMO

Example 1: Government Unit Constructs

FGDC Framework ESRI Bluebook


GMOGMO

Example 2: Transportation Constructs

FGDC Framework ESRI Bluebook


GMOGMO

Task Description Construct Logical Data Model in UML Convert UML Model into Implementable Relational Data

Model with Constraints Produce Modeling Associated Documentation

UML Diagram XML Schema E-R Diagram (Optional) Data Dictionary following FGDC Guidance and ISO 11179-3 Model Description Document


GMOGMO

Vetting Process The Data Model will be vetted through FGDC HSWG

Info Content Sub-Group The Data Model will be Recommended to FGDC HSWG

for Draft Endorsement


GMOGMO

Vetting Process FGDC HSWG Info Content Sub-Group needs to establish a

checklist of expected content and document any perceived discrepancies

1. Parcel Boundaries 2. Road Centerlines with Address Ranges 3. Water Supply/Storage/Treatment Facilities/Lines 4. Water Bottling Locations 5. Wastewater Facilities/Collection Areas/Collection Lines 6. Oil Storage Facilities and Retailers Including Gasoline (required for two reasons - shortage issues and pollution issues) 7. Telecommunication Service Areas, Facilities, and Towers (Land Line and Cell Phone) 8. Imagery 9. Power Plants/Service Provider Areas/Electric Grid/Transmission Lines 10. Natural Gas Plants/Service Provider Areas/Transmission Lines 11. Telecommunication Provider Service Areas (both land line and cell phone) 12. Banks and Financial Institutions 13. Bus Transport Companies 14. Storm water Drainage Lines and Pumping Stations 15. Topography 16. Common USAR Grid 17. Hospitals/Walk-in clinics/In-patient Residential Facilities w/Emergency Contact Information 18. EMS 19. Police 20. Fire & Rescue 21. Response Team Staging Areas (e.g. USAR) 22. Shelter/Victim Relocation Areas 23. Intersection Points (with Lat/Long coordinates) 24. Neighborhoods/Subdivisions/Parishes/Districts


GMOGMO

Proposed Schedule

April1W

April2W

April3W

April4W

May1W

May2W

May3W

May4W

June1W

June2W

June3W

June4W

Define Modeling Scope and Approach

Work on the First Draft of the Model

Develop Required Documentation for Review

Draft Release

DHS Component Pilot Implementation

FGDC HSWG Review and Endorse the Proposed Model


GMOGMO

For More Information For general information about this modeling task, please

contact Bob Philips and Mike Lee at FGDC HSWG For any technical question or comment, please contact

Dr. David Li at [email protected]

fgdc homeland security working group dhs enterprise modeling briefing

Documents