1. Unification & Simplification Through: C ooperation I nnovation O pportunity Implementing the Interior Data Reference Model November 29, 2004

2. “Achieving Information Excellence” 1 Organizational Context The Department of the Interior manages one of every five acres of land in the United States, providing opportunities for wilderness, wildlife protection, recreation, and resource development; We supply water for much of the West so that farmers can grow food and people can turn on their taps; We provide access to energy and minerals so that people can warm and cool their homes, and drive to their jobs; We honor our special responsibilities to American Indians, Alaska Natives, and affiliated Island communities; and We protect wildlife and improve the environment.

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

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

5. “Achieving Information Excellence” 4 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

6. “Achieving Information Excellence” 5 * 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

7. “Achieving Information Excellence” 6 IDRM Mapping to 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

8. “Achieving Information Excellence” 7 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

9. “Achieving Information Excellence” 8 Framework Components 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 Repository 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

10. “Achieving Information Excellence” 9 DOI Data Architecture Approach (Data Traceability) Business Architecture Products Information Requirements Identify and Define Structure & Standardize Implemented Data Structures Operational Systems Map, Assess, & Re-engineer New Systems Register Metadata Interior Data Reference Model Interior Metadata Repository Data that is sharable & usable by multiple business units across the Enterprise

11. “Achieving Information Excellence” 10 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

12. “Achieving Information Excellence” 11 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

13. “Achieving Information Excellence” 12 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).

14. “Achieving Information Excellence” 13 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

15. “Achieving Information Excellence” 14 DOI Data Architecture Role in Modernization Blueprints 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

16. “Achieving Information Excellence” 15 DOI 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

17. “Achieving Information Excellence” 16 Relationship of Interior DRM to other 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 Erwin Oracle XML Etc. 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 (IAWG) Subject Area RECREATION Interior Architecture Review Board

18. “Achieving Information Excellence” 17 Data Resource Management Roles and Relationships DRMSG DOI Data ArchitectPrincipal Data Stewards Bureau Data Architect Database Administrator (DBA- provides access and designs/develops interfaces and connections) DOI Data Architecture Guidance Body Subject Matter Expert (SME - analyzes and defines data requirements) 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. (Data Resource Mgmt Steering Group) Business Data Steward

19. “Achieving Information Excellence” 18 IDRM Implementation - Recreation Requirements & ChallengesIDRM RoleOutcomes Needed a basis for data sharing among 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

20. “Achieving Information Excellence” 19 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

21. “Achieving Information Excellence” 20 IDRM Implementation – Trust Requirements & ChallengesIDRM Role Outcomes Needed to identify and analyze common data across all Trust systems Provide data requirements for procurement of modernized Trust systems Needed to identify redundancies Provide a standard for reverse engineering and data standard gathering Provide a means to map data standards to system records and fields and report on redundancies Served to provide a consistent set of data requirements to be included in procurement requirements Provided a clear set of non- redundant, consistent data standards across the Trust business line Most Trust systems were mapped to the IDRM Trust data standard. Redundancies were easily identified IDRM continues to provide sets of data requirements as procurement proceeds

22. “Achieving Information Excellence” 21 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

23. “Achieving Information Excellence” 22 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

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