# Presentation: 751535

## DOI Data Resource Management

**POC:  Craig Tanner, IT Pioneers, L.L.C., 703-626-2730, e-mail: craig@itpioneers.com**

**March 17, 2004**

- Recreation One Stop
- Standardization Pilot

## Recreation.gov

- The Goal:  to collect recreational data efficiently from the various agencies who managed facilities across the country and to satisfy the various requests from the consumers of this data.
- The Approach:  to develop an xml based solution for data interchange
- The Problem:  There was an initial rush to implement a solution.  Data owners were frustrated with the initial attempt at implementation.  The way they thought about their data was different than the process for collecting it.  The project stalled.
- The Solution:  Step back and start from the beginning...

## Background

- Multi-Department, multi-agency, including Federal, State, Local Govt. and great interest from private sector
- Recreation.gov was stuck – Couldn’t make significant progress.  Lacked an approach
- Published XML Schema but no data integration
- An Enterprise Architecture Approach – FEA provided a formal “business oriented’ approach business owners could buy into.
- Community of Practice Approach – Information Exchange Drivers with Modernization Blueprint Drivers
- Data modeling and re-issuing of the XML brought all parties back to the table

## Data Modeling Control: Business Architecture

- The DOI Recreation LOB fits within the Federal Enterprise Architecture by tying to the Federal “Natural Resources” LOB.  Within the Federal LOB, the DOI Recreation LOB ties to the “Recreational Resource Management and Tourism” sub-function.

**Recreation Resource Management **

**Recreation Resource Education and Outreach **

**Recreation Operations**

**Recreation Information Management**

**Recreation Resource Permits **

**Recreation Resource Planning **

**Recreational Resource Management and Tourism**
**(Federal Sub-function) **

**Natural Resources**
**(Federal Line of Business) **

- DOI Activities

## Data Modeling Control: Business Architecture

**Recreation**
**Resource Management **

**Recreation Resource Education and Outreach **

**Recreation Operations**

**Recreation Information Management**

**Recreation Resource Permits **

**Recreation Resource Planning **

- H8 - Collect Data for Recreation Resources

- Manage Recreation Reservation and Information Services

- T2 - Oversee Concessions Operations

- 5T - Operate Recreation Sites And Campgrounds

- 1S - Manage Commercial Activities

- H7 - Evaluate Recreation Areas

- R1 - Manage Cultural And Natural Resources Exhibits and Information

- Z1 - Provide Technical Assistance for Recreation

- S3 - Provide Education and Interpretation Products

- H8 - Collect Data for Recreation Resources

- 51 - Manage Recreation

- 8P - Manage Wildlife for Recreation

- 1S - Manage Commercial Activities

- Manage Recreation Reservation & Information Services

- 1P - Issue and Manage Special Recreation Permits for Non Commercial Use

- 1Q - Issue and Manage Recreation Use Permits

- 1R - Issue and Manage Special Recreation Permits For Commercial Users

- 3A - Inspect Commercial Special Recreation Permits For Compliance

- H7 - Evaluate Recreation Areas

- J0 - Assess Linear Recreation Resources

- 8X - Conduct Environmental Reviews for Recreation - Fish & Wildlife Service

- 26 - Prepare and Revise Recreation Activity Plans

## Data Exchange Potential

**Systems from the following categories have been identified as being in contact with Recreation data:**
-  E-Government
-  Geospatial Systems
-  Inventory, Content, and Metrics
-  Permitting
-  Learning Systems/Portals
-  General Support Systems

## XML Based on a Data Reference Model 

**RECREATION-AREA**

**RECREATION-AREA-ACTIVITY**

***Information Exchange Package:***** PUBLIC RECREATION AMENITY REQUEST**

***Subject Area:***** RECREATION**

***Super Type:***** RECREATION AREA**

***Data Object:***
***DOI Conceptual Data Entities (Standardized)***

***Data Property:***
***DOI Conceptual Data Elements (Standardized)***

***Data Representation:***

**Notional**

**Notes:**
Reusable database schema, lookup data, and XML Schema necessary to support applications
Represent shareable data concepts (Billing Code, Country Code, State Code, Resource Code, etc.)

## Basic Standardization Framework

**Architect**

**SME**

**Steward(s)**

**Chief Data Architect**

**Consumer**

**Use in **
**Integrated **
**Systems &**
**Information**
**Exchange**

**Integrate &**
**Refine**

**Publish & ****View**

**Harvest**
**Or Design**

**Update**

**Analyze &**
**Refine**

**Review**
**(Technical**
**& Cross**
**Functional**

**Basic Standardization Framework**

**People**

**States**

## Basic Standardization Framework-In Practice

**SME**

**Steward(s)**

**Data Architect**

**Consumer**

**Engineer**

**Integrate &**
**Refine**

**Publish****& ****View**

**Harvest**
**Or Design**

**Update**

**Analyze &**
**Refine**

**Review**
**(Technical**
**& Cross**
**Functional**

**Basic Standardization Framework-In Practice**

- 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

- Recreation.gov 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**

**States**

**Use in **
**Integrated **
**Systems &**
**Information**
**Exchange**

- Update Repository Artifacts

- Working Recreation Model

## DRM Coordination and Evolution

**DRM Coordination and Evolution**

**Initial**
**DOI-DRM**
**V1**

**Candidate**
**DOI-DRM**
**Vx+1**

**Approved**
**DOI-DRM**
**Rel x+1**

***DOI-DRM Published Release***

**Recreation Subject Area Transformation Model**

**Original RecML**

**Review RecML**

**Release 1.0  RecML**

**Approved**
**DOI-DRM**
**Rel 1**

**Candidate**
**DOI-DRM**
**Vx+2**

**Recreation Subject Area Logical Data Model – Vx +1**

**Recreation Subject Area Logical Data Model V1**

## Primary Concepts in RecML

- Address
- Event
- Facility
- Facility Activity
- Facility Association
- Facility Covers
- Facility Event
- Organization
- Organization Facility Role
- Organization Recreation Area Role

- Recreation Area
- Recreation Area Activity
- Recreation Area Advisory
- Recreation Area Association
- Recreation Area Covers
- Recreation Area Event
- Recreation Area Facility
- Recreational Activity
- Vendor
- Vendor Activity

## Recreation High Level To-Be Systems Architecture (with DOI systems)