1. Considering an Enterprise Architecture for the NSDI Doug Nebert FGDC Secretariat March 15, 2005

2. 2 Presentation Outline What is Enterprise Architecture? Converging on a common scope and terminology Proposal for a National Geospatial Enterprise Architecture (NGEA) Convening a multi-jurisdictional exploratory project on geospatial EA

3. 3 Definition Enterprise Architecture: the explicit description and documentation of the current and desired relationships among business and management processes and information technology OMB Circular A-130, revised 11/00

4. 4 Enterprise Architecture Defines a framework in which one describes the current and future work activities and justifies the investments (personnel, data, applications) of an “enterprise” A precursor to electronic government (e-gov) and business process re-engineering

5. 5 Goals of EA Provide a structured approach to business process assessment and re-engineering Classification of business processes, data concepts, standards, services (components and interfaces) for each organization Reference framework to store models that explain the services and data behind them Opportunity to improve efficiencies within an organization Identify potential for services and data re-use for multiple purposes

6. 6 Implementing EA Enterprise Architecture is a relatively new endeavor that has a wide variety of interpretation and deployment. It may range from: Taxonomy and classification of resources for reporting to a common authority Prototyping software systems intrinsically defined by organizational requirements Complex models that can be used and tested in computer simulation of business (not computing) processes

7. 7 More definitions Enterprise - the highest level of organization, or one that is trans-organizational Infrastructure - all supportive resources to getting the job done: people, processes, technology Model - a recreation or representation of the infrastructure Framework - the collection of the models suited to a specific enterprise

8. 8 Reference Models Business Reference Model (BRM) –define mission-critical lines of business, business processes, and functions Performance Reference Model (PRM) sometimes developed to define measures of performance Technical Reference Model (TRM) –identifies and describes the technology (components, interfaces) used to achieve the BRM Service Reference Model (SRM) defines the types and instances of services required to support processes Data Reference Model (DRM) – defines the data/information concepts, structures, definitions, and values or enumerations required by the BRM in the context of the TRM

9. 9 Zachman Framework Planner’s view Owner’s view Designer’s view Builder’s view Integrator’s view User’s view Modified from: http://apps.adcom.uci.edu/EnterpriseArch/Zachman/Resources/ZachmanTutorial.ppt

10. 10 Describing the Enterprise mission Work assignments Investments, Planning Software system design Data management work processes business modeling data

11. 11 Defining the Enterprise # participants, complexity workgroup office division department whole of government community

12. 12 Common misconception “Enterprise Architecture is just an IT endeavor.” According to the EA experts, most successful examples of EA are convened as elements of business process re-engineering, where issues of personnel, capital expenditure, and IT management are understood as co- equal and interdependent

13. 13 Another misconception “Enterprise architecture means buying one corporate software solution.” EA is not the same as an enterprise software licensing agreement, though agreements may be justified through analysis of business processes and workflows. The solutions should flow from the analysis of ‘what you do’ and ‘how you do it’ rather than being driven solely by ‘what you already have.’

14. 14 Why an EA for the National Spatial Data Infrastructure (NSDI)? Differences in understanding and implementing EA in various agencies Encourage communication between geospatial business professionals and IT/CIO offices within agencies Identify and publish best practices Identify opportunities to fortify and share common geospatial services across all levels of government “over the fence”

15. Integrated Data and Information “To Be State” Using the FEA-DRM Pollution Prevention & Control Energy Research Public Health Monitoring Recreational Resource Management & Tourism Consumer Health & Safety Consumer Safety DOE Emission DOI Natural Resource HHS USDA Health Recreation Shared lines of business Geospatial Overlay

16. 16 Transitional Process Standards US Approach to a Federal Enterprise Architecture Drivers Business Architecture Data Architecture Applications Architecture Technology Architecture Business Architecture Data Architecture Applications Architecture Technology Architecture Strategic Direction CurrentFuture Contextual Conceptual Logical Physical As Built Functioning Why Who When Where What How Models Adapted from “Federal Enterprise Architecture Framework”

17. 17 Information Community Producers Users Portals Mapping and Exploratory Software Linked Data Problem- Solving Software

18. 18 Geospatial Services Increasingly, geospatial data can be accessed in real-time over local area networks and the Internet as if it were local data Multiple organizations can benefit from the data being staged and maintained once and used many times, or replicated in intentional ways Desktop software and portals can use these services, and the data behind them, over the Web

19. 19 Geospatial Semantics Location implies special semantics Place names Locational hierarchies, aliases Geographic geometries Special operations Topologic operators: encloses, adjacent, touch, intersect Point-in-area, area intersection/union Routing along networks, across surfaces

20. 20 Geospatial Data Feature-oriented data constructs Real-world object has properties including geometry, identity, others Thematic data models for basic, common re-use data called “Framework” Features may participate in networks and relationships

21. 21

22. 22 Conceptual NSDI Service Network Hazard Model Citizen Service Portal Desktop GIS Planning System Clients Service and Data Catalog Placename Service Symbolization Service Routing Service Transformation Services Common NSDI Services Data Common Data Services

23. 23 Proposed Initiative Establish an ad hoc management advisory council to advise the inclusion of geospatial resources in governmental Enterprise Architectures (National GEA) Through an ad hoc technical working group, begin a reconnaissance and evaluation of existing GEA terminology, use cases, and models to define and promote best practices and common resources within the community

24. 24 NGEA Management Advisory Council Convene a council of federal and non- federal managers to coordinate and communicate geospatial issues in the context of EA, and FEA Work with/through CIO Council Work with/through coordination entities such as the FGDC and its stakeholders in all levels of government Approve and oversee technical activities

25. 25 NSDI EA Project Proposal Conduct a project to initiate a Geospatial Enterprise Architecture in the context of the NSDI to help identify geospatial data / service producers and consumers, and create opportunities to align enterprise architectures within and across agency lines: Involve multiple jurisdictions, state/local, and federal entities Adopt common reference terminology and scope Develop consensus on the ‘results’ of such an EA exploration: Reference models? Best practices?

26. 26 Suggested Workplan Build consensus on common terminology, concepts, and scope of project Request and synthesize existing geospatial EA contributions from interested contributing organizations Highlight scenarios (archetypal business processes) that address and justify critical provider and user processes and the data behind them

27. 27 Workplan, continued Evaluate existing EA artifacts with respect to formal Service, Data and Technology Reference models, consistent with FEA Validation of Reference Models via active prototyping and demonstration of services in support of multiple organizations Document best practices for incorporating geospatial aspects of existing EA A consensus process to evolve reference models and best practices via broader NSDI community involvement

28. 28 Approach in Three Phases Phase I: Establish common understanding of objectives and terminology, acquire existing EA materials, develop key scenarios for geospatial, establish EA Reference Models for NSDI that ties to agency-supplied FEA Lines of Business and equivalent Reference Model concepts Phase 2: Mature data and technical reference models, best practices Phase 3: Validate reference models and best practices via experimentation and prototyping

29. 29 Opportunities for partnership E-government initiatives including recreation.gov and geodata.gov Department of Interior EGIM members Group on Earth Observations (GEO) partners NASA Department of Homeland Security Environmental Protection Agency USDA Key state and local government agencies

30. 30 Beginning the exploration NSF-hosted Collaboration Expedition on March 15, 2005, in Ballston, VA will focus on the geospatial aspects of EA. Contact Susan.Turnbull@gsa.govSusan.Turnbull@gsa.gov Planning work-session on March 16 th, 11:00am at USGS, Reston, VA to initiate follow-on tasks and commitments. Contact: klcovert@fgdc.govklcovert@fgdc.gov

31. 31 For more information, contact: Doug Nebert FGDC Secretariat ddnebert@fgdc.gov (703) 648-4151