1. Unification & Simplification Through: C ooperation I nnovation O pportunity Interior Data Reference Model Overview September 30, 2004 Presented by: Suzanne Acar, OCIO

2. “Achieving Information Excellence” 1 INTRODUCTION Getting Organized Data Architecture Framework & Approach Relationship to the FEA DRM Data Standardization Concepts & Approach Implementing the IDRM Benefits Communication, Data Governance, & EA Summary Getting Organized Data Architecture Framework & Approach Relationship to the FEA DRM Data Standardization Concepts & Approach Implementing the IDRM Benefits Communication, Data Governance, & EA Summary

3. “Achieving Information Excellence” 2 Guidance Documents Data Resource Management & Standardization Program Enterprise Data Model Formal Stewards Body A Data Registry Data Architecture Components GUIDANCE STEWARDS DATA REGISTRY ENTERPRISE DATA MODEL

4. “Achieving Information Excellence” 3 The Major Mandates Clinger Cohen Act OMB Circular A-130 FEA PMO Guidance Documents (Emerging guidance for Data and Information DOI declared as proof-of concept)

5. “Achieving Information Excellence” 4 7 Initial Business Lines Recreation Wild Land Fire Management Law Enforcement Indian Trust Data Finance Geospatial Facilities Management Start points for building the Interior Data Architecture: Limited EA funding drove the decision to pick priority business lines. The data architecture work on these business lines is accomplished in phases as funding permits. Those in Red are DOI EA priorities.

6. “Achieving Information Excellence” 5 The DOI Data Complexity Challenge Same Data Requirement Same Data Requirement Different Functional/Business Needs and Different Data Descriptions Records Management Facility Management Law Enforcement Geospatial Indian Trust Finance Fire Management Recreation Land Management

7. “Achieving Information Excellence” 6 Law Enforcement Geospatial Recreation Indian Trust Finance Fire Management Shared & Distributed Data (thru data standardization including reuse of external standards) Records Management Requires culture change, planning, and implementation know how to be effective Facility Management Land Management THE VISION: Enabling Business Lines with Shareable Data

8. “Achieving Information Excellence” 7 IDRM Roles and Relationships DRMSG DOI Data ArchitectDOI Principal Data Stewards Bureau Data Architect Database Administrator IAWG or ? DOI Data Architecture Guidance Body Business Data Steward Subject Matter Expert Executive Sponsor Appoints Principals & ensures adequate funding Coordinates the creation or review of proposed data standards with all business data stewards & Bureau Data Architects for a business line. Maintains current DOI data Standards for their respective business line. Submits proposed data Standards to DOI Data Architect for formal review process. Coordinates implementation of new Data standards with SME and DBA in systems supporting a business line. Ensures data security & data quality requirements for each data Standard. Maintains & publishes the IDRM in coordination with Principal Data Stewards and Bureau Data Architects. Promotes the Data Program. Assists the DOI Data Architect in the implementation of the Data Program among Bureaus in coordination with Principal Data Stewards and Business Data Stewards. Maintains Bureau unique data standards in coordination with business data Stewards.

9. “Achieving Information Excellence” 8 Development of Formal Lead Data Stewards (Current Status) Law Enforcement Recreation Indian Trust Finance Fire Management Records Management Recreation Program Mgr Trust Architect ??? NPS Deputy CIO E-GIM Team ??? Interior RM Mgr Principal Data Steward for Each Business Line Facility Management Geospatial ??? Acting Dept Mgr

10. “Achieving Information Excellence” 9 Interior Data Resource Management Goals Reduce the life cycle cost of data through integration, data standards, and the use of authoritative reference data sources. Provide a data reference model which addresses both Information requirements and data capabilities. Provide a data resource management infrastructure to ensure information integrity, quality, and security. Provide a metadata registry to support data standardization and re-use.

11. “Achieving Information Excellence” 10 Portals External Interfaces External InterfacesDeliveryMechanism (e.g. XML) Info Exchange/ Info Sharing Requirements DataStandardization E-Gov Applications E-Gov Applications Legacy Migration Policy XML Policy DOI Lines of Business Other Gov’t Agencies DOI Partners Synchronization & Implementation Support Data Resource Management Data Resource Management Policy DOI Data Architecture Framework

12. “Achieving Information Excellence” 11 Framework Pillars Amplified (Sample products and services) DataStandardization TransportMechanism (e.g. XML) Info Exchange/ Info Sharing Requirements Synchronization & Implementation Support Interior Data Reference Model (IDRM) Common Data Standardization Procedures Data Registry Data Stewards Roster Interface Requirements Information Exchange Data Models Data Transformation Models Re-usable Reference Data Sets Re-usable XML Tags & Schemas Replication Support Transformation These activities are imperative to achieve and maintain traceability of the data from the business need to data in the systems including XML.

13. “Achieving Information Excellence” 12 The Data & Information Sharing Approach Identify data and information most important to share Standardize the data in collaboration forums following Department procedures Publish and promote use of the official standard data

14. “Achieving Information Excellence” 13 * SUBJECT AREA : Public Health Business Sub-Functions: Public Health Monitoring Community of Practice - Agencies that need to solve a common problem - Agencies that need to share data - Agencies that perform similar processes Topic of interest * SUPER-TYPES: Categories of data used to perform business operations and shared by business functions * INFORMATION EXCHANGE: Packages of meaningful data used as an input to decisions or generated as an output during process execution Object Description Relational Table XML Schema Facility Location Person Disease Business Process External Request Information Exchange * DATA ELEMENT DESCRIPTION Agencies define their information and processing needs. This can be applied to the most granular level of information passed. FEA DRM CONCEPT

15. “Achieving Information Excellence” 14 IDRM Implementation of FEA DRM (Illustration Example: RECREATION) Physical Model Schema (SQL) CREATE TABLE RECAREA (RECAREA_IDCHAR(12) NOT NULL, RECAREA_NMVARCHAR(50) NOT NULL PRIMARY KEY (RECAREA_ID)); CREATE UNIQUE INDEX XPKRECAREA ON RECAREA ( RECAREA_ID ASC); CREATE TABLE RECAREA_ACT (RECAREA_IDCHAR(12) NOT NULL, RECAREA_ACT_CDCHAR(2) NOT NULL, RECAREA_ACT_DESCVARCHAR(240) NULL, RECAREA_ACT_FEEVARCHAR(240) NULL); CREATE UNIQUE INDEX XPKRECAREA_ACT ON RECAREA_ACT ( RECAREA_IDASC, RECAREA_ACT_CDASC); * Information Exchange Package: PUBLIC RECREATION AMENITY REQUEST * Subject Area: RECREATION * Super Type: RECREATION AREA XML Schema A recreational activity available at a Recreation Area. The code that denotes a specific kind of Recreational Activity. RECREATION-AREA RECREATION-AREA DENTIFIER RECREATION-AREA NAME RECREATION-AREA MAP URL TEXT RECREATION-AREA IDENTIFIER (FK) RECREATION-ACTIVITY TYPE CODE RECREATION-AREA-ACTIVITY DESCRIPTION TEXT RECREATION-AREA-ACTIVITY FEE DESCRIPTION TEXT RECREATION-AREA-ACTIVITY 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 DOMAIN: RECREATION-ACTIVITY TYPE CODE Data Object: DOI Conceptual Data Entities (Standardized) 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 METADATA REGISTRY/REPOSITORY Glossary of Metadata Data Property: DOI Conceptual Data Elements (Standardized) Data Representation: * Data Element Description

16. “Achieving Information Excellence” 15 Basic Standardization Framework EngineerArchitectSME Steward(s)DOI Data Architect Consumer Integrate & Refine Publish & View Harvest Or Design Update Analyze & Refine Formal Review People Stages Use in Integrated Systems

17. “Achieving Information Excellence” 16 Standardization Framework Applied (Illustration Example: Recreation) ArchitectSME Steward(s)DOI Data Architect Consumer Engineer Integrate & Refine Publish & View Harvest Or Design Update Analyze & Refine Formal Review) Previous RecML Iterative Facilitated Modeling Sessions (Multi-Department and Agency) Introduce Cross-Departmental Data Standards Develop Transformation Model Access Repository Artifacts Harvest Metadata RecML Review Package Draft New RecML V1.0 RecML Schema Access Repository Artifacts Working Transformation Model Working RecML Working Recreation Model Recreation Conceptual Model V1.0 Use RecML Schema Use Information Knowledge and Requirements Artifact Reuse and Integration Pointers to accessible, integrated e-Gov Data Store Repository Artifacts Repository Standardization Management Facility DRM Program Performance Measurements Implement Physical Standards Model Review Package People Stages Use in Integrated Systems Update Repository Artifacts

18. “Achieving Information Excellence” 17 Interior Data Reference Model (IDRM) Views All View Common View Lines of Business View

19. “Achieving Information Excellence” 18 Data Standardization Process Key attribute Standard element Proposed element Standard element Proposed element Proposed DOI DRM Extraction Integrated Business Line Views Review period with Business Data Stewards facilitated by the Interior Data Architect Upon review completion of a submission Package for a business line, proposed data become official DOI standards and published in various highly accessible sources. Integrate DRM Submission Package

20. “Achieving Information Excellence” 19 NAMING STRUCTURE (Maps to ISO 11179 Guidance) Prime Word (subject/entity) ModifierClass Word + + Amount Rate Angle Temperature Area Text Code Time Coordinate Volume Date Weight Dimension Identifier Mass Name Number Quantity EXAMPLES: - DOCUMENT APPROVED DATE - CONTRACT PAYMENT RATE - PERSON NAME

21. “Achieving Information Excellence” 20 Some Rules to Follow (Consistent with ISO 11179 guidance) NAMING RULES RULES FOR DEFINITIONS Name is always unique Be clear, accurate, and self explanatory Name is always singular Always end with a class word Include only alphabetic characters, and spaces Unless commonly used, spell out all acronyms Don’t repeat the name in the definition Describe the “what”, not the “how”, “when”, “where”, or “who” Data elements must have only one meaning. Avoid multiple meanings and concepts Have only one interpretation Avoid ambiguity Describe purpose & usefulness without using physical qualities

22. “Achieving Information Excellence” 21 Data Architecture Communication (http://www.doi.gov/ocio/architecture/index.html) IDRM Artifacts posted on Interior’s EA web page. High level Data Architecture (i.e. data subject areas) and data models are in the Department’s EA Repository (DEAR).

23. “Achieving Information Excellence” 22 Interim DOI Data Repository (MS Access Database) Easier to track data life cycle, search, sort, parse, and/or map data elements for analysis work with MS Access DB

24. “Achieving Information Excellence” 23 Data Architecture Role in Modernization Blueprint Analysis Discovery of data sharing opportunities and redundancies begins by mapping systems to Data Subject Areas and Super Types. Financial System A Recreation System B Fire Management System C Super Type A Super Type B Super Type C BRM Business Need Data Sharing Opportunities Identify Common Data Data Subject Area AB

25. “Achieving Information Excellence” 24 DOI Data Subject Areas (Sample) DOI Data Subject Areas and Super Types Report September 13, 2004 This document contains the high level classification of data subject areas and super types approved by the Data Resource Management Steering Group. The purpose of this document is to facilitate the discovery of data sharing opportunities and redundant data across the DOI enterprise. It also supports various data analysis activities. Subject AreaDefinitionSuper-Types Community ServiceInformation about relations and services provided to improve the quality of life for the communities that DOI serves.  Public Affairs  Indian Affairs  Education  Economic Growth  Community & Regional Development  Social Services Controls and OversightInformation about supervision, overseeing, and administration operations and programs of DOI and its external partners that ensure compliance with applicable laws and regulations, and to prevent waste, fraud and abuse. Evaluation of conformance with policy, guidance, and standards; meeting statutory requirements; and providing a means of evaluating the overall quality of the products and services being produced.  Permits  Licenses  Audit  Inspections  Standards  Performance  Program Evaluation  Program Monitoring EnergyInformation about all actions performed by DOI to ensure the procurement and management of energy resources, including production, sale and distribution of energy, as well as the management of spent fuel resources. Energy management includes all types of mass-produced energy (e.g. hydroelectric, nuclear, wind, solar, or fossil fuels).  Energy Resource Mgmt  Energy Supply  Energy Conservation FacilityInformation about real property consisting of one or more of the following: a building, a structure, a utility system, pavement, and underlying land.  Asset  Improvement  Facility  Real Property  Utility

26. “Achieving Information Excellence” 25 Data Subject Area Mapping Process Identify and Define Data Subject Areas and Super Types 1 Existing Bureau and External Data Subject Areas DOI Data Architecture Contractor and DRMSG Acquire System Artifacts and SME Knowledge 2 DEAR System Info. Database Schemas (Rec.) DRMSG DOI Data Architecture Contractor and DRMSG Develop maps between Systems and Subject Areas 3 Artifacts Data Subject Area Definitions

27. “Achieving Information Excellence” 26 IDRM Implementation - Recreation Requirements & ChallengesIDRM RoleOutcomes Needed a basis for data sharing amongst multiple Federal, State, Local & Commercial parties Share data from multiple business lines Translate data sharing to a database and XML Must be easily extensible to accommodate new requirements Provided a basis for requirements gathering and data analysis – Rapid Standardization Provided a mechanism for discussion and validation amongst data sharing partners Identification of data sharing opportunities Translation of conceptual analysis into database and XML Schema All parties agree to data sharing requirements – greatly increased collaboration Integrated data requirements and data sharing across business lines Extensibility proven through inclusion of Trails data standard Implemented database and XML Schema $ $ $ $

28. “Achieving Information Excellence” 27 IDRM Implementation – Law Enforcement Requirements & ChallengesIDRM RoleOutcomes Needed to develop comprehensive set of data requirements for new LE Systems Procurement Provide an extensible standard for the concept of an Incident, whether it is LE, Emergency Management, Search & Rescue, etc. Must integrate with Department of Justice XML Schema Provided a basis for requirements gathering and data analysis Model provided platform for integration of Justice standards and DOI requirements Inclusion of an extensible concept for an “incident.” Provided a clear set of data requirements to be included in procurement documents Justice XML data standards have been included. Provides ability for data exchange using emerging standard Model currently being extended to include Emergency Management, Security and Organizations $ $ $

29. “Achieving Information Excellence” 28 IDRM Implementation – Records Mgmt Requirements & ChallengesIDRM RoleOutcomes Needed to identify the core data requirements necessary to conduct the Records Management business process Provide for possible data reference model across the Federal Government Provide for future analysis of data sharing opportunities and reduction of redundancies Provided a basis for requirements gathering and data analysis IDRM Methods and Techniques provide a flexible mechanism for data sharing analysis IDRM Methods and Techniques are based on ISO 11179 and other standards, ensuring a basis for Federal-wide analysis With one analysis session, provided an extension to the IDRM that clearly captures the core data requirements for Records Management. Model to be used as a basis for analysis of data sharing and redundancies Model has been circulated among several Federal Agencies $ $ $

30. “Achieving Information Excellence” 29  Reduces Costs – Control redundancy thru data standardization & integration – Re-use opportunities improved – Interface development/maintenance costs reduced  Traces data and information in systems to the business need  Takes advantage of existing information planning efforts  Common language, common definitions  Meets OMB/Federal Enterprise Architecture (FEA) and DOI Architecture mandates IDRM Benefits

31. “Achieving Information Excellence” 30 Interior EA Components & Governance Teams DRM BRM LINES OF BUSINESS Subfunctions Recreation Finance Law Enforcement Recreation-Amenity Recreation-Amen Name Recreation-Amen Description Text Facility Agency Code Provides TRM SRM Product Name Vendor Visio Microsoft Erwin CA Int’l Oracle XML Altova Data Marts Data Warehouses Information Systems Knowledge Management Records Management Interior Business Architecture Team (IBAT) Domain Arch. Teams (DAT’s) Data Resource Mgmt Steering Group (DRMSG) PRM Facility Name Facility Type Code Facility Facility Identifier Interior Architecture Work Group Subject Area RECREATION Interior Architecture Review Board

32. “Achieving Information Excellence” 31 Summary DOI Data Architecture work is evolutionary and maps to the concepts in FEA DRM and ISO 11179 IDRM development tied to DOI EA priority business lines IDRM serves as the basis for database design, data integration, and XML artifacts (RECREATION proof-of-concept) Effective Data Stewardship is critical to success “I am careful not to confuse excellence with perfection. Excellence I can reach for, perfection is God’s business.” ---- Michael J. Fox

33. “Achieving Information Excellence” 32 QUESTIONS Suzanne Acar Enterprise Data Architect Department of the Interior Office of the Chief Information Officer Phone: 202-208-3216 E-mail: suzanne_acar@ios.doi.gov