Managing Data As A National Asset 2008

1. Managing Data As A National Asset 2008 “Build to Share” Federal Data Architecture Subcommittee

2. Agenda • Introduction • FEA DRM Overview • Three Pillar DRM Implementation Strategy • FEA DRM Governance Strategy • DRM Implementation Example • Summary

3. FEA Reference Models Source: FEA PMO - The FEA Reference Models http://www.whitehouse.gov/omb/egov/a-2-EAModelsNEW2.html FEA Reference Models are interrelated and designed to facilitate inter-agency analysis of investments for collaboration.

4. Information Supply Chain Among the FEA Reference Models • Business Goals (PRM) • Business Strategies (BRM) • Business Intelligence (SRM & TRM) • Information (DRM) • Data (DRM) The DRM focuses on the business objectives (PRM) and aligns data needed for the business processes (BRM). The SRM and TRM are informed by the DRM. The purpose of the DRM is to facilitate information sharing across government.

5. FEA Data Reference Model Framework How do I exchange the data? Data Sharing Query Points and Exchange Packages How do I find the data and access it? What does the data mean? drive Business & Data Goals The Rule: All 3 pillars are required for an effective strategy. Data Description Data Context Governance Taxonomies Data Based on FEA DRM Version 2.0 Data Strategy Information Sharing/Exchange (Services) Data Architecture (Structure) Planning and ExecutingInformation Sharing Objectives FEA Data Reference Model Implementation Framework From Draft FEA DRM Management Strategy

6. FEA DRM Version 2.0 Overview

7. FEA DRM Concept How do I exchange the data? Data Sharing Query Points and Exchange Packages How do I find the data and access it? What does the data mean? Data Description Data Context Taxonomies Data Based on FEA DRM Version 2.0 http://www.whitehouse.gov/omb/egov/a-1-fea.html

8. FEA DRM Structure

9. FEA DRM Abstract Model(Guidance for Organizing Information About Agency Data)

10. Basic Data Sharing Concepts:Provision Services for Data • Types of Data Exchange Services: • Extract/Transform/Load • Publication • Entity/Relationship Extraction • Document Translation • Types of Data Access Services • Context Awareness • Structural Awareness • Transactional Services • Data Query • Content Search and Discovery • Retrieval, Subscription and Notification

11. Data Context: Figure out the Data that the Enterprise (aka Community of Interest) cares about. • Data Description: • Figure out the standards: • Standard Meanings • Standard Structures Data Sharing: Figure out the services required to share information The DRM Approach(Summary) • The DRM provides basic guidance on what to capture in each of these areas and how to capture it. (i.e., the Abstract Model) • Intentionally, the DRM does not delve into specific models or artifacts that the architects will create: • Organizations use different EA Frameworks. There are a lot of right ways. • The models/artifacts developed will depend on what’s needed • As we define best practices, we will consider more definitive guidance in the DRM • However, the objective is to provide actionable guidance to your programs: We should be building with data sharing in mind up front. - “Build to Share”

12. Example: Role of DRM

13. Implementing the DRM FEA DRM Three Pillar Data Strategy Framework

14. What the DRM Is Not • The DRM is not a government-wide data model, • Nor is it an all-encompassing set of XML schemas that describe the data of the government. • It is not meant to replace existing data structures within the agencies, rather to provide the means to compare data among agencies in order to exchange, re-use or integrate data.

15. The DRM Goal • As government transforms from being program-centric to citizen-centric, the demand for discoverable, accessible, and reliable information will naturally increase. Data must be managed as a stand-alone shareable asset to meet these demands.

16. Data Management Plays a Role • Key data management functions that come into play include: • Data governance and stewardship • Data Standardization • Metadata management • Data quality management • Master data management • Data security

17. Business & Data Goals drive The Rule: All 3 pillars are required for an effective data strategy. Governance Data Strategy Information Sharing/Exchange (Services) Data Architecture (Structure) The DRM Data Strategy Framework Goals drive; governance controls; structure defines; and services enable data strategy. Special thanks to Laila Moretto and Forrest Snyder, MITRE Corp.

18. Inventory Discovery Data Oversight Definitions/Semantics Policy & Procedures Structure Communities of Interest Education/Training Syntax Search Processes and Practices Pedigree Data Registries Issue Resolution Authoritative Sources Data Catalogs Metrics/Incentives Security/Protection Data Shared Spaces Data Transfer Standards Access Services Brokering Mediation Data Strategy Framework Elements(Example) Information Sharing/Exchange (Services) Data Architecture(Structure) Governance Use of specific elements depend on the goals

19. Mapping the Strategy to the DRM Data Contextenables… Data Descriptioncaptures… Data Sharingguides…

20. Governance Overview

21. Governance Strategy • Two Key Components of DRM Governance • Federal Data Architecture Subcommittee (DAS) • Inter-agency • Launched May 2006 • Communities of Interests (COI) • Discussed in Draft DRM Management Strategy • Examples include OMB LOBs, and E-Gov initiatives

22. Data Goals drive Gover-nance Data Strategy (Services) (Structure) FEA DRM Implementation Example E-Gov Initiative: Recreation One Stop

23. Business Goals drive Governance (Services) (Structure) About Recreation One Stop (Business & Data Goals) • One of the President’s E-Gov inter-agency Initiatives led by DOI & the most accessed government site by the public • Requirements: • Share data among multiple Federal, State, Local and Commercial partners • Share data across multiple business lines • Data standards must be easily extensible to accommodate new requirements • Data sharing standards must be translated to a database and XML

24. DOI Recreation Community of Interest (COI) USDA

25. Business Goals drive Gover-nance (Services) (Structure) E-Gov Initiative:Recreation One Stop(Challenge) Customers see too many sources for Federal recreation information.

26. Business Goals drive Gover-nance (Services) (Structure) E-Gov Initiative:Recreation One Stop(Governance) • COI is Federal Recreation providers • Recreation Executive Council • Members are deputy assistant secretary level (DOI, USDA, & DOD) • Provides strategic perspective • Provides adjudication • Recreation Managers Committee • Senior level Recreation managers • Sets priorities • Members include Smithsonian, DOT, and 16 other agencies • Various implementation groups • One group is responsible for the adoption of data standards • Another group stewards the data • Another group responsible for data implementation

27. Business Goals drive Governance (Services) (Structure) Major subject areas of data that need to be shared with other business areas of the enterprise. (Structure)

28. Permit Organization Sale Location Vendor Geospatial- Location Financial-Transaction Person Postal- Location Recreation Area Recreation Facility Reservation (Blue = Shared Data Concept) Descriptive- Location Recreation Activity Business Goals Country State River Trail Event/Incident drive Governance (Services) (Structure) E-Gov Initiative:Recreation One Stop Structure: High Percentage of Data Reuse Identified

29. Subject Area: RECREATION Information Class: RECREATION ACTIVITY Information Exchange Package: RECREATION ACTIVITY QUERY Data Object: DOI Conceptual Data Entities (Standardized) RECREATION-AREA CREATE TABLE RECAREA (RECAREA_ID CHAR(12) NOT NULL, RECAREA_NM VARCHAR(50) NOT NULL PRIMARY KEY (RECAREA_ID)); CREATE UNIQUE INDEX XPKRECAREA ON RECAREA ( RECAREA_ID ASC); CREATE TABLE RECAREA_ACT (RECAREA_ID CHAR(12) NOT NULL, RECAREA_ACT_CD CHAR(2) NOT NULL, RECAREA_ACT_DESC VARCHAR(240) NULL, RECAREA_ACT_FEE VARCHAR(240) NULL); CREATE UNIQUE INDEX XPKRECAREA_ACT ON RECAREA_ACT ( RECAREA_ID ASC, RECAREA_ACT_CD ASC); Data Property: DOI Conceptual Data Elements (Standardized) Physical Model Schema (RIDB) RECREATION-AREA DENTIFIER RECREATION-AREA-ACTIVITY RECREATION-AREA NAME RECREATION-AREA MAP URL TEXT Data Element Description RECREATION-AREA IDENTIFIER (FK) RECREATION-ACTIVITY TYPE CODE Data Representation: RECREATION-AREA-ACTIVITY DESCRIPTION TEXT RECREATION-AREA-ACTIVITY FEE DESCRIPTION TEXT XML Schema Business Goals METADATA REGISTRY/REPOSITORY Glossary of Metadata DOMAIN: RECREATION-ACTIVITY TYPE CODE <?xml version="1.0" ?> <xsd:Schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xs:element name="RecAreaActivity"> <xs:annotation> <xs:documentation>A recreational activity available at a Recreation Area. </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="RecAreaActivityType" type="xs:string"> <xs:annotation> <xs:documentation>The code that denotes a specific kind of Recreational Activity.</xs:documentation> </xs:annotation> </xs:element> drive A1|AIR-HANG GLIDING B1|BOATING-SAILING B2|BOATING-CANOEING B3|BOATING-KAYAKING C1|CAMPING-CAMP SITES C2|CAMPING-FREE SPACE H1|HIKING-TRAILS H2|HIKING-FREE RANGE S1|SWIMMING-LAKE, POND S2|SWIMMING-POOL REGISTRY ENTRY: RECREATION-ACTIVITY TYPE CODE DATA TYPE: CHARACTER LENGTH: 2 DEFINITION: The code that denotes a specific kind of Recreational Activity CLASS WORD: CODE Governance (Services) (Structure) E-Gov Initiative:Recreation One Stop Services: RecML is based on standards described in Recreation ERD

30. Ultimately, a model was assembled to illustrate what components were necessary to procure to streamline systems, data, and technologies. SOA

31. Ultimately, a model was assembled to illustrate what components were necessary to procure to streamline systems, data, and technologies. A Federal source of record was established and constructed for Recreation data. SOA

32. Ultimately, a model was assembled to illustrate what components were necessary to procure to streamline systems, data, and technologies. SOA Quality is ensured through a reporting service.

33. Ultimately, a model was assembled to illustrate what components were necessary to procure to streamline systems, data, and technologies. Data is shared to the NRRS contractor via web service. SOA

34. Business Goals drive Governance (Services) (Structure) E-Gov Initiative:Recreation One Stop(In Action) http://www.rec.gov RecML Document Response Query Query Point Point RIDB RIDB http:// http:// www.recreation.gov/detail.cfm?ID www.recreation.gov/detail.cfm?ID =1577 =1577 For list of information sharing partners see: http//www.recdata.gov Services: Information Sharing Result

35. Summary

36. Summary • The FEA DRM is one of five inter-related reference models designed to facilitate inter-agency analysis and collaboration. • The FEA DRM consists of three basic concepts: Context, Description, and Information Sharing. • Three basic concepts of the draft FEA DRM Implementation Strategy consists of: Governance, Structure, and Services. • Agencies and COIs can implement the FEA DRM in many ways, but must follow the three pillar data strategy to be successful. • The Federal Data Architecture Subcommittee was established to provide agencies additional guidance on FEA DRM implementation.

37. Questions Contact info: Suzanne Acar: U.S. Department of the Interior Senior Information Architect, and Co-Chair Federal Data Architecture Subcommittee E-mail: suzanne_acar@ios.doi.gov Adrian Gardner: U.S. National Weather Service Chief Information Officer, and Co-Chair Federal Data Architecture Subcommittee E-mail: adrian.gardner@noaa.gov