Overview of FEA Geospatial Profile, Version 0.3 Doug Nebert FGDC Secretariat

2 Profile scope Introduction to Geospatial concepts and its pervasive nature Performance Reference Model Business Reference Model Technology Reference Model Service Component Reference Model Data Reference Model

3 Performance RM Guidance WHAT does geospatial contribute to performance within the line of business HOW do information or technology elements in the line of sight relate geospatially? Outlines measures associated with a NASA ROI study on value of interoperability planning

4 Performance Model: WHAT Once geospatial relevancy is established, the geospatial services and analyses to support the IT business and operational functions can be demonstrated, benchmarked, and documented — specifically how the geospatial initiative can enhance, enable, leverage, and visualize or provide support services for integration initiatives.

5 Performance Model: HOW Disparate data can be functionally linked through their location on the Earth’s surface. Using this spatial attribute of data can allow for data to be queried, accessed, analyzed, summarized, and visualized with in the context of location. Specific guidance is lacking, performance must be addressed case-by-case.

6 Geospatial Interoperability Maturity Model (GIMM) Not exactly a PRM item, but more evaluation of maturity of execution of integrated geospatial capabilities Needs to be reconciled with the new Enterprise Architecture Assessment Framework (EAAF, Version 2.0) just released

7

8 Business Reference Model Geospatial is not a Line Of Business Three main LoB identified in Profile: Service for Citizens Support Delivery of Services Management of Government Resources but … 20 LoB (64%) have primary geospatial elements, all 32 LoB benefit from geospatial Geospatial activities listed in Appendix E

9 Geospatial Business Language Business statements to evaluate how a business process may reveal geospatial capabilities GBL includes: Application Data Function Process Technology

10 Data Reference Model Context – taxonomies, references locational taxonomies, topic cateogries from ISO Sharing – OGC specifications for discovery, encoding, and transmission as applied to geospatial data Description – FGDC and ISO Metadata Standards in force

11 Service Component RM Current FEA lumps most geospatial service in one ‘component’: Domain: Business Analytical Services Service Type: Visualization Component: Mapping, geospatial (GIS), elevation, GPS Approach to extend the SRM specificity to implementable service components Service components listed in Appendix G

12 Desired Features of a Service Component Encapsulation - A component should clearly separate the definition of the services that it provides from its implementation of those services. Consumability – can be chained and minimally dependent on other services Extensibility - to adapt to changes in the business and data while at the same time preserving services provided to existing consumers. Standards-based

13 Service characteristics, cont’d Industry best practices and patterns Well-documented Cohesive Set of Services - Components should be factored in such a way that they provide a cohesive set of services. Well-Defined and Broadly Available Licensing or SLA - A software component should be accompanied by a well-defined license or service-level agreement (SLA).

14 Technology Reference Model Specific standards with geospatial relevance relative to SRM/TRM component framework: Data types / validation Data transformation Service discovery Service description / interface Content rendering Wireless/Mobile/Voice Data interchange Middleware integration Data format/classification Additional geospatial standards in Appendix H

15 Reviews to-date on Version federal and commercial responses received Recurrent points: Generally helpful for raising awareness Request more specific implementation guidance Clarification of scope and focus, link to NSDI Make less focused on FEA, appealing to non-feds More links to Best Practices and external artifacts

16 Timetable Pilot project kickoff meeting Thursday, Dec 8 th, 2:30-4:30pm DOI, Room TBD Comments on Version 0.3 being processed Draft for technical editing will be produced December 15 th Draft Version 1.0 will be submitted to OMB and agencies in early January