DRM Implementation Guide: IAC White papers

1www.actgov.org

DRM Implementation Guide: IAC White papers

-DAS Support Status and Working GroupDecember 3, 2007

2www.actgov.org

Goals drive; governance controls; structure defines; and services enable data strategy.

Business &Data Goals

drive

Information Sharing/Exchange

(Services)

Governance

Data Strategy

Data Architecture(Structure)

The Rule: All 3 pillars are requiredfor an effectivedata strategy.

Information Sharing/Exchanges key Pillar of Data Strategy

3www.actgov.org

Bringing Order to the Many Elements

Governance

Data Transfer Standards

Pedigree

Authoritative Sources

Security/Protection Data

Discovery Data

Inventory

Definitions/Semantics

Structure

Syntax

Data Architecture (Structure)


(Services)

Oversight

Policy & Procedures

Processes and Practices

Education/Training

Issue Resolution

Metrics/Incentives

Access Services

Brokering

Shared Spaces

Data Catalogs

Data Registries

Communities of Interest

Search

Mediation

4www.actgov.org

Mapping the Strategy to the DRM

Data Contextenables…

Data Contextenables…

Data Descriptioncaptures…

Data Descriptioncaptures…

Data Sharingguides…

Data Sharingguides…

Our Focus!

5www.actgov.org

The DRM is Business-Driven

COI

Org 2

Org 3Org 1

Agility

Increased Information Sharing

Common Understanding

Improved DiscoveryRapid Harmonization

Consistent Models

ScreeningEmergency ManagementLaw Enforcement

…Intelligence

COIs are bothIntra and Inter-Organization

BRM DRM

Cross-AgencyBusiness

Need

6www.actgov.org

• What are the organizations that must share information

• Amount of data by topic areas• Complexity• Number of users with • Cross Enterprise Sharing

Information Sharing/Exchange Summary

Challenges Faced

Information Sharing Techniques used

Results & Lessons Learned

• What was big problem you faced? (Pain Points)• How was it overcome? (Coping Strategies)• What would you recommend? For those starting?

Those mature organizations?• What should be avoided?

• What are the current results?• What are the long term expected results?• How did it effect the performance on given areas?• What are some of the lessons learned?• What are key success factors?

• Describe the solution• Describe the set of practices that have been used….. • Any special technology used- ontologies, translators,

policy management, meta data management?

Quote on Success………………………… and lessons learned.” - XXXXXX, CIO, YYYYYYY

LogosType of Practice

Information Exchange Summary

7www.actgov.org

Information Sharing and Exchange Projects

• Global Justice Network and NIEM• Environmental Data Network• Army-NATO Exchange• National Health Interoperability Network (NHIN)• IC Information Sharing • Others……many….

8www.actgov.org

THE END

9www.actgov.org

DRM Implementation White Papers

• DRM Getting Started Task– Issues involved with getting started- what, why and how– Draft SOW to bring on your Data Architecture Contractor– Getting Management Engaged and interested– Getting Started Workshop– Business and Data Process Scenarios and Data Architecture Planning– Assessment and Information Gathering Templates– Strategic Data and Information Value Analysis– Early Data Governance- a little data governance goes along way- focus!

• DRM Value Trade-offs and Proposition– Data Value aligned with Strategic Direction– Balancing Modeling and Strategic Data Management versus tools and techniques for

data services, data integration and transformation– Measuring your Data Transformation: Progress and Outcomes– Data Architecture early and often results- success stories

10www.actgov.org

DRM Implementation White Papers

Interoperability and Information Sharing Practices– Planning for What you have and what you want– Analysis with the NIEM- IEPD and other techniques– Meta Data Patterns and their use– Standard set of data services for data and data services

connecting with policy, identity, and entitlement-based security– Interoperable Data Reference Model – having consistent

standards first data references with a master data management– Identifying and resolving conflicts early with a verification and

validation process built in.

11www.actgov.org

Data Architecture Support for DRM Start-Up

How Data Architecture can support DRM during the critical

Start-Up Phase

12www.actgov.org

Project Initiation:

DA Sub-phase

Charter:Value Proposition Precipitating

Events

Select:Situation Focused

Data Models and Design Early

Discovery &Definition

EarlyDesign &Focused Data Model/Implementation

Data Architecture Quick Start Initiatives

4- 6 months………

Leverage:Situation

Focused SolutionAlignment

Early Results:Outcomes and

Next Steps

BRM:SRM:Alignment& Linking

Selected ProjectIntegration

13www.actgov.org

Project Initiation: DA Sub-phase

• Objective:– To ensure project scope is well defined, and that

important roles are defined– Provide a “quick start” 4-6 months with early results

for a “sponsors” key concerns and value from Data Architecture.

– Develop Project Charter• Identify Project Sponsor• Define Project Scope, Objectives• Identify Key Resources (high level)

14www.actgov.org

Kickoff of Data Architecture Phase

• Probably the most important event in assuring the success of the project!

• The Project Sponsor will be heavily involved (with the Leader of the Project)

• The Project Sponsor will make clear the importance of the project to the organization

• He will also make clear the level of support expected from the various levels of the organization

15www.actgov.org

Roles in Introducing Data Architecture

• The Leader• Sponsor (from Senior Management)• The Team• Important supporting Players; Subject Matter

Experts (SMEs)

16www.actgov.org

Data Architecture: the Key Part

• Data is a valuable corporate asset, that• Must support business mission/ objectives• Strategic Alignment of Data and Information

Goals• Surveys-Information Gathering• Data and Information Contexts- connecting into

Business Processes and Models• See FEA Framework (next Page)

17www.actgov.org

Federal Enterprise Architecture Framework (FEA)

• Add Graphic to illustrate key role of DRM in the FEA

• Note that the FEA is Federally mandated in OMB300 funding applications

18www.actgov.org

The Project Charter

• Identify Scope,

• Identify Project Sponsor

• Define Objectives

• Identify Key Resources (high level)

19www.actgov.org

Outline: Data Architecture Sub-task

• Project Initiation– Kickoff of Data Architecture Sub-task– The Project Charter: Scope, Other Things– The Project Sponsor– The Precipitating Event

• Project Planning– Project Organization– Current and Target Architecture

• Project Execution• Project Monitoring and Control• Project Closure

20www.actgov.org

Readiness-Acceptance Planning

• Add graphic from document

21www.actgov.org

Promote Importance of Enterprise Architecture and Data

• Do Data Profiling to quickly assess the impact that high quality data can have in the future (and conversely, the impact of poor quality data

• Use these results to promote the role of Enterprise Architecture Plan and Roadmap to both Senior Management and Implementers of systems

22www.actgov.org

Why is Data Architecture Not Perceived as High Value ?

• Data IS a valuable corporate asset – often not seen as such!!!

• Strategic Initiatives may be dependent on high quality data, but someone must make that connection!!!!

23www.actgov.org

Value Proposition

• Data Architecture must offer a compelling value proposition;

• Many competing projects will offer a) high returns, or b) are “must do” projects for strategic reasons

• Very often, Data Architecture not initially perceived to fit into either category!!!

24www.actgov.org

What Are the Parts of the Information Architecture

2629-06—012

MITA Framework

Business Architecture

State Self-AssessmentBusiness Capability MatrixBusiness Process ModelMaturity ModelConcept of Operations

Data StandardsLogical Information Model

Conceptual Information Model

Data Management Strategy

Information Architecture Technical Architecture

TechnologyStandards

Application ArchitectureTechnical Services

Technical Capability MatrixBusiness Services

Solution Sets

25www.actgov.org

Data Governance

• DRM and Data Architecture programs should seek out ongoing Data Governance programs

• Models and data definitions will be much more easily and rapidly finalized– since SMEs (Subject Matter Experts) will already be identified, with responsibilities assigned, etc.

• If a program is not in place, the functions normally performed will need to be performed, and may be more difficult, than if supported in an ongoing program

26www.actgov.org

The Precipitating Event

• There will often be a Precipitating Event that will force the move to DRM (and Data Architecture)

• Data (and DRM) has not historically been a area for which funds were easily justified, when related to other priorities

• Precipitating Events are usually high profile, such that a major change of direction from senior management occurs, and there are then few issues with funding the project or getting the “right” people assigned.

27www.actgov.org

Precipitating Events:Examples

• If your agency has data-related issues that result in:– Embarrassing questions asked in Congress – An article on page one of the Washington Post– Inability of government-sponsored financial

institution to produce timely financial statements

– These examples are all from real life!

28www.actgov.org

The Project Sponsor

• Not the day-to day leader of the project• An executive level manager, who is “at the table” and is

willing and able to support the project when difficulties arise (and they will . . .)

• The Project Sponsor must be someone who “gets it”, as to the importance of the DRM program (and Data Architecture) to the organization

29www.actgov.org

Project Planning

• Confirm Scope and Objectives and Readiness • Review Prior Work• Establish Project Organization • Tailor Project Approach • Develop and Document Project Plan • Establish Project Infrastructure • Plan Project Team

30www.actgov.org

Project Execution (1)

• Establish Project Infrastructure • (Tools/ Team/ Support)

• Orient and Train Project Team • Understand Current Architecture and Creating a

Portfolio Analysis• Review Architecture Source Materials• Obtain Tools

• Metadata Management/ Modeling• Metadata capture from existing data, using capture tools• Obtain Orientation/Training for new Tools

• Document Current Business Architecture and Linkage to Data Models and Data Services

31www.actgov.org

Project Execution (2)• Document Current Projects- What are their Data

Approaches?

• Create Portfolio Analysis: Data Portfolio of Data

Models and Data Services • Develop Target Data Architecture

– Support for New Business Strategies– New Business Rules

• Define Data Requirements – Use Tools to extract existing Data and Metadata– Use Data Governance (access to SMEs)

32www.actgov.org

Data, Business Processes, and Capability Levels

Messages Shared Data Information Models (Triggers and Results) + =

(Conceptual and Logical)

Shareddata

Shared data

Message

BusinessProcess B

BusinessProcess A

BusinessProcess C

BusinessProcess D

BusinessProcess E

Message

Message

Message

Message Message

Message

Message

Message

Message Message

Message

Message

Shared data

Shared data

Message

Conceptual Information

Model

Logical Information

ModelXML Schemas

33www.actgov.org

L4BusinessProcess

Data and Business Processes

Shareddata

Shared data

Message

BusinessProcess B

BusinessProcess A

BusinessProcess C

BusinessProcess D

BusinessProcess E

Message

Message

Message

Message Message

Message

34www.actgov.org

LogicalInformation Model

Logical Model Is the Serializable Object Model, Vocabulary, Data Types, and Interactions that Comprise the Service Definition Payload

Object Model Supported Interactions Vocabulary and Code Sets

Data Types

35www.actgov.org

LIM Development Process

• LIM based on the MITA CIM, a subset of early adopter data models and HL7’s Reference Information Model (RIM)

• Validate the harmonized LIM against the business process requirements

• Distribute the draft LIM to early adopters for review• Update the model with comments • Submit the model for second review to early adopters

and then to all States• Submit the updated model to MITA for adoption as the

standard MITA LIM

36www.actgov.org

The CIM Is Comprised of a “Static” Concept Model and a “Dynamic” Activity Diagram

cd Logical Model

«process»ControlActProcess

+/ «stereotype» ControlAct: ControlActProcess+/ «type» ActMoodIntentEvent: ControlActProcess+ «list» id: SET<II> [0..1]+ «trigger» TriggerEventCode: char [0..1]- «type» text: encapsulated data [0..1]+ «set» ActReason: reasonCode [0..1]- «languageCode» Human_Language: char [0..1]

QueryByParameter

«interface»QueryAcknow ledgement

- «l ist» queryid: char [0..1]+ «type» QueryStatusCode: char [0..1]+ «type» QueryResponse: char- «quantity» resultTotalQuantity: int [0..1]- «quantity» resultCurrentQuantity: int- «quantity» resultRemainingQuantity: int [0..1]

NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

MMIS

Requestor

NPSResponseResults

QueryContent

NPSResponseRequirements

requires

queryByParameter0..1

1...1{Mandatory}

queryAck

ad Activ ity Diagram

MMIS NPS

Initiate NPS Query Interface

NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Prov ider Record

Provider Indenti ty Confi rmed?

Prov ider Enroll Info

Reject Query

Receive Reject Query

Provider Enrol lment Rejection

AggregateNPS Data

Query Response

Receive Query

Response

NPS PT Al ign with MITA PT?

«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI

Provider Enrol lment Accepted

Activi tyFinal

Yes

No

Yes

Formalized Business Process Model

Static Concept Model

Dynamic Activity Diagram

Conceptual Information Model

37www.actgov.org

BusinessProcess

Level 1

Level 3Level 2Level 1 Level 4 Level 5

cd Logical M odel


+/ «stereotype» Contro lAct: Contro lActProcess+/ « type» ActM oodIntentEvent: Contro lActProcess+ « l ist» id : SET <II> [0 ..1 ]+ « trigger» T riggerEventCode: char [0 ..1 ]- « type» text: encapsula ted data [0 ..1 ]+ «set» ActReason: reasonCode [0 ..1 ]- « languageCode» Hum an_Language: char [0 ..1 ]

QueryByParameter

«in terface»QueryAcknow ledgement

- « l ist» queryid : char [0 ..1 ]+ « type» QueryStatusCode: char [0 ..1 ]+ « type» QueryResponse: char- «quanti ty» resu l tT ota lQuanti ty: in t [0 ..1 ]- «quanti ty» resu l tCurrentQuanti ty: in t- «quanti ty» resu l tRem ain ingQuanti ty: in t [0 ..1 ]

NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

M M IS

Requestor

NPSResponseResults

QueryContent


requires

queryByParam eter0..1

1...1{M andatory}

queryAck


MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»




Reject Query



AggregateNPS Data

Query Response

Receive Query

Response

NPS PT Al ign wi th MITA PT?

«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI


Activi tyFinal

Yes

No

Yes

Level 2 Level 3 Level 4 Level 5BusinessProcess Capabilities

BusinessProcess Model

FormalBusinessProcess Model

BusinessProcess StaticConceptModel

cd Logical M odel



QueryByParameter



NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

M M IS

Requestor

NPSResponseResults

QueryContent


requires


1...1{M andatory}

queryAck


MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»




Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI


Activi tyFinal

Yes

No

Yes

cd Logical M odel



QueryByParameter



NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

M M IS

Requestor

NPSResponseResults

QueryContent


requires


1...1{M andatory}

queryAck


MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»




Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI


Activi tyFinal

Yes

No

Yes

cd Logical M odel



QueryByParameter



NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

M M IS

Requestor

NPSResponseResults

QueryContent


requires


1...1{M andatory}

queryAck


MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»




Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI


Activi tyFinal

Yes

No

Yes

cd Logical M odel



QueryByParameter



NPSSystem

Responder

Person

DataEnterer

Receipient

NPSInquiryEv ent

CerificationAct

M M IS

Requestor

NPSResponseResults

QueryContent


requires


1...1{M andatory}

queryAck


MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»




Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Prov ider Record

Xw alk toMITA PT

Activi tyFinal

Load NPI


Activi tyFinal

Yes

No

Yes

BusinessProcess DynamicActivityModel

BusinessProcess ObjectModel

BusinessProcess DataTypes

BusinessProcess Vocabulary

38www.actgov.org

Data and Information Reference Model (DRM)

• Add graphic from document on the DRM

39www.actgov.org

BusinessProcessModel

LogicalInformationModel

ConceptualInformationModel

Level 1

Level 3

Level 2

Level 1

Level 4

Level 5

c d L o g ic a l M o d e l

« p ro ce ss»

C o n tro lA c tP ro c e s s

+ / « ste re o typ e » C o n tro l A c t: C o n tro l A c tP ro ce ss

+ / « typ e » A c tM o o d In te n tE ve n t: C o n tro l A c tP ro ce ss

+ « l i st» i d : S E T < II> [0 . .1 ]

+ « tri g g e r» T ri g g e rE ve n tC o d e : ch a r [0 . .1 ]

- « typ e » te x t : e n ca p su l a te d d a ta [0 . .1 ]

+ « se t» A c tR e a so n : re a so n C o d e [0 . .1 ]

- « l a n g u a g e C o d e » H u m a n _ L a n g u a g e : ch a r [0 . .1 ]

Q u e ryB yP a ra m e te r

« i n te rfa ce »

Q u e ryA c k n o w le d g e m e n t

- « l i st» q u e ry i d : ch a r [0 . .1 ]

+ « typ e » Q u e ryS ta tu sC o d e : ch a r [0 . .1 ]

+ « typ e » Q u e ryR e sp o n se : ch a r

- « q u a n t i ty» re su l tT o ta l Q u a n t i ty : i n t [0 . .1 ]

- « q u a n t i ty» re su l tC u rre n tQ u a n t i ty : i n t

- « q u a n t i ty» re su l tR e m a i n i n g Q u a n t i ty : i n t [0 . .1 ]

N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t

N P S In q u iryE v e n t

C e rific a tio n A c t

M M IS

R e q u e s to r

N P S R e s p o n s e R e s u lts

Q u e ryC o n te n t

N P S R e s p o n s e R e q u ire m e n ts

re q u ire s

q u e ryB yP a ra m e te r0 . .1

1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»NPS Provider

Record

Provider Indentity Confirmed?

Provider Enroll Info

Reject Query


Provider Enrollment Rejection

AggregateNPS Data

Query Response

Receive Query

Response

NPS PT Align with MITA PT?

«datastore»Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI

Provider Enrollment Accepted

ActivityFinal

Yes

No

Yes

Level 2

Level 3

Level 4

Level 5


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

Level 1

Level 3

Level 2

Level 1

Level 4

Level 5


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

Level 2

Level 3

Level 4

Level 5


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

Level 1

Level 3

Level 2

Level 1

Level 4

Level 5


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

Level 2

Level 3

Level 4

Level 5


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro ce ss»




+ « l i st» i d : S E T < II> [0 . .1 ]






« i n te rfa ce »








N P S S yste m

R e s p o n d e r

P e rso n

D a ta E n te re r

R e c e ip ie n t



M M IS

R e q u e s to r




re q u ire s


1 . . .1{M a n d a to ry }

q u e ryA ck

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT


Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response



Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

BP-2 BP-78 BP-79

Level 1

Level 3

Level 2

Level 1

Level 4

Level 5


« p ro c e ss»

C o n tr o lA c tP r o c e s s

+ / « ste re o ty p e » C o n t ro l A c t : C o n t ro l A c tP ro c e ss

+ / « ty p e » A c tM o o d In te n tE v e n t : C o n t ro l A c tP ro c e ss

+ « l i st» i d : S E T [0 . .1 ]

+ « t ri g g e r» T ri g g e rE v e n tC o d e : c h a r [ 0 . .1 ]

- « ty p e » te x t : e n c a p su l a te d d a ta [0 . . 1 ]


- « l a n g u a g e C o d e » H u m a n _ L a n g u a g e : c h a r [0 . .1 ]

Q u e r yB yP a r a m e te r

« i n te rfa c e »

Q u e r yA c k n o w le d g e m e n t

- « l i st» q u e ry i d : c h a r [0 . .1 ]

+ « ty p e » Q u e ry S ta tu sC o d e : c h a r [ 0 . . 1 ]

+ « ty p e » Q u e ry R e sp o n se : c h a r

- « q u a n t i t y » re su l tT o ta l Q u a n t i t y : i n t [ 0 . . 1 ]

- « q u a n t i t y » re su l tC u rre n tQ u a n t i t y : i n t

- « q u a n t i t y » re su l tR e m a i n i n g Q u a n t i t y : i n t [ 0 . .1 ]

N P S S y ste m

R e s p o n d e r

P e rso n

D a ta E n te r e r

R e c e ip ie n t

N P S In q u i r yE v e n t

C e r i fic a tio n A c t

M M IS

R e q u e s to r

N P S R e s p o n s e R e s u l ts

Q u e r yC o n te n t

N P S R e s p o n s e R e q u i r e m e n ts

r e q u i r e s

q u e ry B y P a ra m e te r0 . .1

1 . . . 1{M a n d a to ry }

q u e ry A c k

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Provider Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

Level 2

Level 3

Level 4

Level 5


« p ro c e ss»




+ « l i st» i d : S E T [0 . .1 ]














N P S S y ste m

R e s p o n d e r

P e rso n

D a ta E n te r e r

R e c e ip ie n t



M M IS

R e q u e s to r




r e q u i r e s


1 . . . 1{M a n d a to ry }

q u e ry A c k

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Provider Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro c e ss»




+ « l i st» i d : S E T [0 . .1 ]














N P S S y ste m

R e s p o n d e r

P e rso n

D a ta E n te r e r

R e c e ip ie n t



M M IS

R e q u e s to r




r e q u i r e s


1 . . . 1{M a n d a to ry }

q u e ry A c k

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Provider Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro c e ss»




+ « l i st» i d : S E T [0 . .1 ]














N P S S y ste m

R e s p o n d e r

P e rso n

D a ta E n te r e r

R e c e ip ie n t



M M IS

R e q u e s to r




r e q u i r e s


1 . . . 1{M a n d a to ry }

q u e ry A c k

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Provider Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes


« p ro c e ss»




+ « l i st» i d : S E T [0 . .1 ]














N P S S y ste m

R e s p o n d e r

P e rso n

D a ta E n te r e r

R e c e ip ie n t



M M IS

R e q u e s to r




r e q u i r e s


1 . . . 1{M a n d a to ry }

q u e ry A c k

ad Activity Diagram

MMIS NPS


NPS Query

Receive Query

Find NPI & PT

«datastore»

NPS Provider Record



Reject Query



AggregateNPS Data

Query Response

Receive Query

Response


«datastore»

Provider Record

Xwalk toMITA PT

ActivityFinal

Load NPI


ActivityFinal

Yes

No

Yes

BP-1

Enroll Provider

Detail of the MITA Information Model

40www.actgov.org

Define Security and Privacy (S&P) Requirements and

their Data Alignment

• Design Security Architecture• Include Requirements for

• Authorization• Authentication

• Review to ensure Requirements support organization, without being too costly or complex.

41www.actgov.org

Define Security and Privacy (S&P) Requirements


42www.actgov.org

Develop Enterprise Transition Strategy

• Develop Legacy Transformation Strategy• Define Sequencing Plan • Develop Estimates• Allocate Systems and Interfaces to Releases• Allocate Systems and Interfaces to Projects• Coordinate With Budgeting Process• Define Intermediate Release Architectures • Package Enterprise Transition Strategy (ETS)

for Review

43www.actgov.org

Project Monitoring and Controlling

• Monitoring based on Project Plan• Reporting Schedule for Sponsor, and important

Committees• Escalation procedures for project Issues

44www.actgov.org

Package Target EA for Review

• Provide a series of milestone reviews• Review with Sponsor• Review with other Stakeholders

• Review Target Enterprise Architecture

45www.actgov.org

Review of Target Common

Services / Infrastructure Strategy

• Review for Compatibility with SRM, components under development within e-government projects: e-grants, e-benefits, e-authentication, etc.

46www.actgov.org

Review with Service

Component Reference Model (SRM)

• The SRM Identifies and classifies horizontal and vertical IT service components that support Federal agencies. SRM will aid in recommending service capabilities to support the reuse of business components and services across the Federal Government.

47www.actgov.org

Service Component Reference Model (SRM)


48www.actgov.org

Project Closure

• Assessment of Project Objectives, Goals Reached

• Lessons Learned: Difficulties Encountered

• Suggestions for Next Project Phase; – Based on additional important Subject Areas

significant to the organization

49www.actgov.org

FEA DRM Concepts

Data Sharing

Query Points and Exchange Packages

Query Points and Exchange Packages

Data Description

Data Elements Data Elements

Data Context

Taxonomies (Categories)Taxonomies (Categories)

How do I exchange the data?

What does the data mean?

How do I find the data?

50www.actgov.org

FEA DRM Structure

Based on FEA DRM Version 1.0 and 2.0

Data Sharing

Data Context

Business ContextBusiness Context

Subject AreaSubject Area

Information ClassInformation Class

Information Exchange & Query Points

Information Exchange & Query Points

Data Description

Data Representation Data Representation

StructuredStructured

Semi-structuredSemi-structured

UnstructuredUnstructured

The broad categories of data that support business processes of a line of business or community of interest.

The broad categories of data that support business processes of a line of business or community of interest.

The sub-categories of data used for mapping data groupings of many lines of business or communities of interest.

The sub-categories of data used for mapping data groupings of many lines of business or communities of interest.

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 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.

The organized description of data to convey semantic understanding usually through an entity relationship diagram.

The organized description of data to convey semantic understanding usually through an entity relationship diagram.

Data that has characteristics of both structured and unstructured data, such as an e-mail.Data that has characteristics of both structured and unstructured data, such as an e-mail.

Data that is of more free-form format, such as multimedia files, images, sound files, or unstructured text.

Data that is of more free-form format, such as multimedia files, images, sound files, or unstructured text.

How do I find the data?

How do I exchange the

data?

What does the data mean?

Data ElementData Element

Data ObjectData Object

Data PropertyData Property

Data RepresentationData Representation

51www.actgov.org

What is the Exchange Network?

An Internet and standards-based method for exchanging environmental information between partners

Key Components•Data Standards•Nodes•XML Schema/Registry•Trading Partner Agreements•Grant Program

52www.actgov.org

Exchange Network

• Objectives

– Promote better environmental decisions through improved data quality and data access

– Provide a common method for automating, publishing and exchanging data among states, tribes, and EPA

– Promote efficient business processes and standard technologies to reduce operational costs

53www.actgov.org

Network Governance

Network Policy and Resources Group (NPRG)*

Day to Day Policy and Resource Activities

Network Technical Group (NTG)*Day to Day Operational and

Technical Support

Network Operations Board (NOB)

Registry Etc.Help Desk

*Example Sub -Groups

Policy/ Strategic Planning

Standards Teams*Standards Design and

Development

Network Partnership and Resources Group (NPRG)*Day to Day Policy and

Resource Activities

Network Technical Group (NTG)*Day to Day Operational and

Technical Support

ExecutiveCoordinator

Operations Oversight

Registry Etc.Help Desk Registry Etc.Help Desk

*Example Sub -Groups

Exchange Network Leadership Council (ENLC)

Standards Teams*Standards Design and

Development

54www.actgov.org

55www.actgov.org

Security Architecture / Services

CDXXML

FireWall

NetworkAuthentication

Service

NetworkIdentity

ManagementService

Integrated SecurityManagements

UserManagement

PolicyManagement

IntrusionManagement

VulnerabilityManagement

NAASWeb Service

Interface(SOAP 1.1,SOAP 1.2)

Security PolicyStore

User IdentityStore

Intrusion DetectionRules

NetworkAuthorization

Service

NetworkKey

ManagementServices

(XKMS 2.0)

NetworkCertificateAuthority Key and Certificate

Store

CDXXML

FireWall

Reponse

Request

XMLEncryption

XMLSignature

WS-Security

NetworkSAML

Service

56www.actgov.org

Discovery ServicesDiscovery Services What can I do with it? What can I do with it?

• Embed within an applicationEmbed within an application• Surf with a browserSurf with a browser• Use in a PDA/Smart PhoneUse in a PDA/Smart Phone

57www.actgov.org

Create SQL Query called GetFacilitybyZip

1. 2.

.NET Application Server

FRS Database

Put DB Names into Schema Structure

<FacilitySiteList xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="http://www.epa.gov/enviro/html/frs_demo/FACID_FacilitySiteAll_v2.xsd">[foreach record] <FacilitySiteDetails stateFacilitySystemAcronymName="TestName01" stateFacilityIdentifier="[DatabaseFieldName]"> <FacilitySite> <FacilitySiteName>[DatabaseFieldName]</FacilitySiteName> </FacilitySite> <LocationAddress> <LocationAddressText>[DatabaseFieldName]</LocationAddressText> <SupplementalLocationText>[DatabaseFieldName]</SupplementalLocationText> <LocalityName>[DatabaseFieldName]</LocalityName> <StateUSPSCode>[DatabaseFieldName]</StateUSPSCode> <LocationZIPCode>[DatabaseFieldName]</LocationZIPCode> </LocationAddress> </FacilitySiteDetails>[endforeach]</FacilitySiteList>

Select FacilitySiteName,F.stateFacilityIdentifier,LocationAddressText,SupplementalLocationText,LocalityName,StateUSPSCode,LocationZipCode from FacilitySite F,LocationAddress L Where F.StateFacilityIdentifier = L.StateFacilityIdentifier and StateUSPSCode='$_1'(QueryParameters)order by F.FacilitySiteName

POOF! - New GetFacilitybyZip service is available

3.

D y n a m i c D a t a P u b l i s h i n g

HSP DLL

Programming

Network Query

GetFacilitybyZip w/ QueryParameters

Deployment

Database Connection

Simplified Data Service PublishingSimplified Data Service PublishingEmpower Data Stewards to Publish their DataEmpower Data Stewards to Publish their Data

58www.actgov.org

Web Forms

Help Desk &Operations

Support

Hosted &Distributed IntegrationServices

Security ServicesData Quality

Services

Central Data Exchange

eGov Initiative Partners

Pay.gov Grants.gov

E-AuthenticationFederation

Industry Partners

Water Utilities&

Power Plants

ChemicalProducers

OilRefineries

AutomobileManufacturers EPA Program Office

Partner Systems

eIUR

AQS

SDWIS

EnviroFlash AIRNow

TRI FRS

EPA Regional Partners

Region 4 - CAFO

Region 5 - GeoExchange

General Public

Tribal Partners

Eastern Band of Cherokees

Wind River

State Partners

CaliforniaAir Resource

Board

IndianaEMITS

Internet

Web Services

CDX & Exchange Network Partners

St. Regis Mohawk

RCRAInfo

NEI

WQX/STORET

BMS/ACRES

ICTS

LT2

RMP

Yurok

ODS

OTAQVERIFY

RADNESHAPS

SRS

TSCA

IGMSNOI

PCSRADNET EAB

59www.actgov.org

Universities

Tribes

Analysis and Access Systems

Program Data Repositories & Data Warehouses

RegistriesProgram Silo 50+

Front End Data Collection Systems

Program Information Consumers



RegistriesProgram Silo 1






























Registries Program Silo 7




































































Industry

States

Local Govt

Citizens

Policy Makers

Legislators

Unmanageable Complexity

>150 data flows

1000’s of reports

Dozens formats/ models

Problem Solved by CDX / the Exchange Network

60www.actgov.org

Value Proposition Interlude – DHS (Any Federal Agency) Today

Currently in development, Services rolling

out to help

Legacy systems

Legacy systems

DHSConceptual/

Logical Data Model

DHS SOA Service

Bus

DHS Information

Sharing Environment

Maybe 10% Done

Extremely expensive and timely to develop

Is there one? Lots of activity for defining information in between

components or individual systems or inside systems, but not being

captured for reuse

Working on info sharing to (DHS

example: connect 40+ systems/data

sources related to person

screening )

Enterprise Architecture Status

• Behind on DRM implementation

• Lack Information Sharing Foundation

• EA based SOA is ready for data exchange definition

61www.actgov.org

Scope

NIEM is Payload – Specifications for Data in Business Context

62www.actgov.org

Fit With Federal Enterprise Architecture

Policy

Performance

Business

Data

Services

Technology

Scopeof

FEA

Information ExchangeArchitectural Profile

• Business – standard information exchanges– Focus on reuse and modification

– Authoritative vs. non-authoritative

– Discover / register exchanges via repository

• Data – common vocabulary for building information exchanges– Focus on reuse

– Federated, hierarchical domain structure

– Optional and over-inclusive augmentation

• Performance – measure information sharing– Use/reuse of information exchanges

– Use/reuse of data components (in/out of model)

– Line of sight provides actionable feedback

Focus ofNIEM

InfluencedBy NIEM

63www.actgov.org

Communities of Interest (COI)Vision

Each COI will implement the 3 pillar framework strategy.

Business &

Data Goals drive


(Services)

Governance

Data StrategyData Architecture

(Structure)

64www.actgov.org

Business Driven Information Exchanges

• An Information Exchange Package (IEP) begins with a business need for a particular exchange.

• IEP Documentation (IEPD) describes how that exchange should be expressed using the NIEM.

• The IEPD is a key point for introducing new elements to NIEM and for reusing existing ones.

• An IEPD itself can also be reused in whole or in part to speed development and lower the cost of sharing information.

65www.actgov.org

L2 data

BusinessProcess F

L2

BusinessProcess B

L4

L4BusinessProcess

BusinessProcess A

L3

L4 data L4 BusinessProcess

L4BusinessProcess

L3 data

L4 data

L4 data

SSA, Business, and Information Relationships

BusinessProcess B

L2

BusinessProcess D

L2

BusinessProcess C

L2

L2 data

L2 data

L2 data

BusinessProcess A

L2

BusinessProcess E

L2

BusinessProcess F

L1

L2 data

L1 dataBusinessProcess B

BusinessProcess A

BusinessProcess C

BusinessProcess D

BusinessProcess E

BusinessProcess F

Prior to Self Assessment; 6 Business ProcessesAfter Self Assessment: 5 Level 2 and 1 Level 1 processInitial upgrade Plan; 4 level 2, 1 Level 3 and 1 Level 4Upgrade Plan After looking at Data dependencies; 1 level 2, 1 level 3 and 4 Level 4 processes

66www.actgov.org

NIEM Federated Domain ArchitectureData component - fundamental building block of NIEM. Data components are either Universal, Common, or Domain-specific.

Universal components - data components commonly understood and reused among all domains; subject to NIEM governance.

Common components - data components understood and potentially reused between two or more domains; subject to NIEM governance.

Domain-Specific - components managed by a specific Community of Interest (may be reused with COI, available for reuse by others).

67www.actgov.org

Data Model Maturity Lifecycle

68www.actgov.org

Web site – www.niem.gov

69www.actgov.org

One Approach: Intelligence Community (IC) EA Relationship to the FEA Data Reference Model

IC Data ArchitectureIC Data Architecture

IC Conceptual Data Model

IC Conceptual Data Model

IC Logical Data Models

IC Logical Data Models

IC Metadata Standards

IC Metadata Standards

FEA DRMDimensions

IC EAProducts

Context

Description

Sharing

IC Technical ArchitectureIC Technical Architecture

Apps. Ref Architecture

Apps. Ref Architecture

Data Services Ref. Architecture

Data Services Ref. Architecture

IC EAArtifacts

• Entities of Interest

• Subject Areas

• Entities of Interest

• Subject Areas

• Person(TWPDES)

• Organization (TBR)

• Facility (TBR)• …

• Person(TWPDES)

• Organization (TBR)

• Facility (TBR)• …

• Implementation Specifications and Guidance

• Search• Retrieval• Subscription• Notification• …

• Implementation Specifications and Guidance

• Search• Retrieval• Subscription• Notification• …

70www.actgov.org

DOI DRM Recreation Implementation Summary

Requirements & Challenges DOI DRM Role Outcomes

Needed a basis for data sharing among multiple Federal, State, Local &

Commercial parties

Needed a basis for data sharing among multiple Federal, State, Local &

Commercial parties

Share data from multiple business lines

Share data from multiple business lines

Translate data sharing to a database and XML

Translate data sharing to a database and XML

Must be easily extensible to accommodate new

requirements

Must be easily extensible to accommodate new

requirements

Provided a basis for requirements gathering and

data analysis – Rapid Standardization

Provided a basis for requirements gathering and

data analysis – Rapid Standardization

Provided a mechanism for discussion and validation

amongst data sharing partners

Provided a mechanism for discussion and validation

amongst data sharing partners

Identification of data sharing opportunities

Identification of data sharing opportunities

Translation of conceptual analysis into database and XML

Schema

Translation of conceptual analysis into database and XML

Schema

All parties agree to data sharing requirements – greatly

increased collaboration

All parties agree to data sharing requirements – greatly

increased collaboration

Integrated data requirements and data sharing across business

lines

Integrated data requirements and data sharing across business

lines

Extensibility proven through inclusion of Trails and Museum

data standard

Extensibility proven through inclusion of Trails and Museum

data standard

Implemented single source of Recreation data and an XML

Schema

Implemented single source of Recreation data and an XML

Schema

71www.actgov.org

From Context to Description to Shared Data at Recreation One Stop

Physical Model

Schema(RIDB*)

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);

XML Schema<?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>

Information Exchange Package: RECREATION ACTIVITY QUERY

Subject Area: RECREATION

Information Class: RECREATION ACTIVITY

RECREATION-AREA

RECREATION-AREA IDENTIFIER

RECREATION-AREA NAMERECREATION-AREA MAP URL TXT

RECREATION-AREA IDENTIFIER (FK)RECREATION-ACTIVITY TYPE CODE

RECREATION-AREA-ACTIVITY DESCRIPTION TEXTRECREATION-AREA-ACTIVITY FEE DESCRIPTION TEXT

RECREATION-AREA-ACTIVITY

A1|AIR-HANG GLIDINGB1|BOATING-SAILINGB2|BOATING-CANOEINGB3|BOATING-KAYAKINGC1|CAMPING-CAMP SITESC2|CAMPING-FREE SPACEH1|HIKING-TRAILSH2|HIKING-FREE RANGES1|SWIMMING-LAKE, PONDS2|SWIMMING-POOL

DOMAIN:RECREATION-ACTIVITY TYPE CODE

Data Object:

DOI Conceptual Data Entities (Standardized)

REGISTRY ENTRY:RECREATION-ACTIVITY TYPE CODE

DATA TYPE: CHARACTERLENGTH: 2DEFINITION:

The code that denotes a specific kind of Recreational Activity

CLASS WORD: CODE

METADATA REGISTRY/REPOSITORYGlossary of Metadata

Data Property:

DOI Conceptual Data Elements (Standardized)

Data Representation:

Da

ta E

lem

en

t D

es

cri

pti

on

*RIDB = Recreation Information Database

Documents

DRM Implementation Guide: IAC White papers