What Does the DRM Mean to Me? – The FEA DRM Management Strategy 19 July 2006

1. What Does the DRM Mean to Me? – The FEA DRM Management Strategy19 July 2006 “Build to Share” Federal Data Architecture Subcommittee Co-chairs: • Suzanne Acar, DOI • Bryan Aucoin, DNI

2. Agenda • FEA DRM Concept • Three Pillar Strategy • Governance for Managing Data As a National Asset • Implementation Examples • Summary

3. FEA DRM Concept

4. DRM Purpose • The Data Reference Model provides a structure that facilitates: • the development of government data • sharing within and across agency boundaries • improvement of mission performance and services to citizens.

5. Goals • Provide data to support business needs • Reduce data redundancy and inconsistency within and across communities of interest

6. Data Sharing Query Points and Exchange Packages Data Description Data Context Taxonomies (Categories) Data Elements FEA DRM Concepts How do I exchange the data? What does the data mean? How do I find and access the data?

7. Data Element Data Object Data Property Data Representation FEA DRM Structure Data Context How do I find and access the data? The broad categories of data that support business processes of a line of business or community of interest. Business Context Subject Area The sub-categories of data used for mapping data groupings of many lines of business or communities of interest. Information Class How do I exchange the data? Data Sharing Information that is generated or required by a Unit of Work and is subsequently passed to another Unit of Work. Units of Work consume and produce data. Information Exchange & Query Points What does the data mean? Data Description Data Representation The organized description of data to convey semantic understanding usually through an entity relationship diagram. Structured Semi-structured Data that has characteristics of both structured and unstructured data, such as an e-mail. Unstructured Data that is of more free-form format, such as multimedia files, images, sound files, or unstructured text. Based on FEA DRM Version 1.0 and 2.0

8. 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(A Reader’s Digest Version) • 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”

9. FEA Data Reference Model (DRM) Relationship with other FEA Reference Models Data Reference Model (DRM) Performance Reference Model (PRM) • Maps data to inputs and outputs that support Performance Outcomes • Maps data to processes by Lines of Business • Maps data to Service Components by information flows • Maps data to the infrastructure to plan for interoperability • Inputs, Outputs, and Outcomes • Uniquely Tailored Performance Indicators Business Reference Model (BRM) • Lines of Business • Agencies, Customers, Partners Service Component Reference Model (SRM) • Service Domains, Service Types • Business and Service Components Technical Reference Model (TRM) • Service Component Interfaces, Interoperability • Technologies, Recommendations • The DRM relates to each of the other FEA Reference Models

10. Three Pillar Strategy

11. 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 Data Strategy Framework Goals drive; governance controls; structure defines; and services enable data strategy.

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

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

14. DRM Governance Strategy for Managing Data as a National Asset

15. The Basics • Establishing Federal level governance structure • Building process for formally chartered COIs • DRM provides guidance to establish the 3 pillars • Business-driven, outcome-oriented resolution of issues and opportunities related to data or information management • Elevate best practices to a National and Federal level • Harmonizing between COIs

16. Governance Strategy Introduction of two roles: • Federal Data Architecture Subcommittee (DAS) • Chartered by Federal CIOC’s AIC • 2 Co-chairs appointed by AIC • Suzanne Acar – DOI • Bryan Aucoin – DNI • Membership CIO representation • Various work groups • Communities of Interest (COIs) • Formal or informal collaborative groups of users/organizations • Aligned to a line of business or issues of common concern

17. Data Architecture SubcommitteeVision • Engage COIs in advancing the management of Federal data as a valued national asset. • Authoritative knowledge center for: • Best practices • DRM Implementation solutions • Strategies • Frameworks • Standards • Policies, procedures, and other guidance • Stewards of the FEA DRM and related documents • Federal Data Broker

18. Business & Data Goals drive Governance Data Strategy Information Sharing/Exchange (Services) Data Architecture (Structure) Communities of Interest (COI)Vision Each COI will implement the 3 pillar framework strategy.

19. Implementation • Examples

20. One Approach: Intelligence Community (IC) EA Relationship to the FEA Data Reference Model IC EA Products FEA DRM Dimensions IC EA Artifacts IC Data Architecture • Entities of Interest • Subject Areas Context IC Conceptual Data Model IC Logical Data Models • Person(TWPDES) • Organization (TBR) • Facility (TBR) • … Description IC Metadata Standards IC Technical Architecture • Implementation Specifications and Guidance • Search • Retrieval • Subscription • Notification • … Apps. Ref Architecture Sharing Data Services Ref. Architecture

21. From Context to Description to Shared Data at Recreation One Stop Subject Area: RECREATION Information Class: RECREATION ACTIVITY Information Exchange Package: RECREATION ACTIVITY QUERY 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); RECREATION-AREA Data Object: DOI Conceptual Data Entities (Standardized) Physical Model Schema (RIDB*) RECREATION-AREA IDENTIFIER RECREATION-AREA NAME RECREATION-AREA MAP URL TXT RECREATION-AREA-ACTIVITY Data Property: DOI Conceptual Data Elements (Standardized) RECREATION-AREA IDENTIFIER (FK) RECREATION-ACTIVITY TYPE CODE Data Element Description RECREATION-AREA-ACTIVITY DESCRIPTION TEXT RECREATION-AREA-ACTIVITY FEE DESCRIPTION TEXT XML Schema Data Representation: <?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> METADATA REGISTRY/REPOSITORY Glossary of Metadata DOMAIN: RECREATION-ACTIVITY TYPE CODE 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 *RIDB = Recreation Information Database

22. Outcomes DOI DRM Recreation Implementation Summary Requirements & Challenges DOI DRM Role Outcomes Needed a basis for data sharing among multiple Federal, State, Local & Commercial parties Provided a basis for requirements gathering and data analysis – Rapid Standardization All parties agree to data sharing requirements – greatly increased collaboration Integrated data requirements and data sharing across business lines Provided a mechanism for discussion and validation amongst data sharing partners Share data from multiple business lines Extensibility proven through inclusion of Trails and Museum data standard Must be easily extensible to accommodate new requirements Identification of data sharing opportunities Implemented single source of Recreation data and an XML Schema Translation of conceptual analysis into database and XML Schema Translate data sharing to a database and XML

23. Summary

24. Summary • Consistent implementation of the 3 pillar framework strategy among COIs • Governance establishment are comprised of key roles: DAS and COIs • Launched first monthly meeting of DAS in May 2006

25. Questions