FEA DRM Success Strategy

Michael C. DacontaMetadata Program Manager

February 3, 2005

2Michael C. Daconta February 3, 2005

Speaker Introduction DHS Metadata Program Manager

DHS Data Management Strategy

Expose and Exchange

Standardize and Govern

Integrate and Federate

Technical Lead of the DRM Working Group

In conjunction with the FEA PMO and CIO Council

See Karen Evans memo to CIO Council dated 12/22/2004

DHS Data Standards Representative for: EO 13356 and HSPD 5, 6, 11

Author

See latest article on Formal Taxonomies at XML.com

3Michael C. Daconta February 3, 2005

Agenda

The Big Picture …

Scope

Measures of Success

Implementation Plan

Schedule/Milestones

How you can Help!

4Michael C. Daconta February 3, 2005

Copernican Shift

Apps

Data

We had it all wrong…In the beginning…

Put the “smarts” in the data… watch what happens…

Apps

Apps

Apps

5Michael C. Daconta February 3, 2005

Scope (1): Where we are today… Volume 1 is released.

http://www.feapmo.gov

Agency comments have been collectedSend your comments to

susan.turnbull@gsa.govWe plan on posting comments (without

attribution) to a public site

DRM Working Group planning is underwayBroad participation including State and

LocalAddress Business and Technical IssuesFoster broad adoption and

implementationSatisfy the Presidential Orders/Directives

6Michael C. Daconta February 3, 2005

Scope (2) : EO 13356Strengthening the Sharing of Terrorism Information to Protect Americans

Section 1. Policy: “Agencies shall … give the highest priority to … interchange of terrorism information among between agencies and appropriate authorities of States and local governments [while protecting] the freedom … of Americans….”

Section 3. Preparing Terrorism Information for Maximum Distribution within Intelligence Community. IC Agencies shall set forth “standards for sharing of terrorism information by agencies within the Intelligence Community with [through DHS] appropriate authorities of State and local governments.”

Section 4. Requirements for Collection of Terrorism Information Inside the United States. Attorney General, Secretary for Homeland Security, and the DCI shall jointly submit their “recommendation on the establishment of executive branch-wide collection and sharing requirements, procedures, and guidelines for terrorism information to be collected within the United States, including, but not limited to, from publicly available sources, including nongovernmental databases.

Section 5. Establishment of the Information Systems Council. “The mission of the Council is to plan for and oversee the establishment of an interoperable terrorism information sharing environment to facilitate automated sharing of terrorism information among appropriate agencies….”

7Michael C. Daconta February 3, 2005

Scope (3) What are we trying to accomplish?

Revise DRM Volume 1

Respond to all comments

Add a glossary

Make Volume 1: Complete, Consistent and Cohesive. See DRM for Information Sharing Brief

Complete the DRM

Volumes 2, 3 and 4

Correct Volume Strategy? Enable Implementation of the DRM

Implementation Profiles Foster Broad Government and Vendor Adoption

8Michael C. Daconta February 3, 2005

Measures of Success Two years after completion of the DRM, how will we decide if it is

successful? Enables Tangible Business Outcomes

EO 13356 and HSPD-11 are successfully implemented. Shared spaces are more than portals

Number of interagency exchanges has increased dramatically Taxonomies will be tailored to specific, narrow user communities. Core registry is operational and effective in promoting reuse Leaders can ask “Enterprise Questions” and get accurate cross-domain, cross-agency

answers How else will it improve Discovery, Integration, Relevance and Reuse?

See XML 2004 keynote slides Real-time Relevance?

Please share with us your Measures of Success and Performance Metrics

9Michael C. Daconta February 3, 2005

Implementation Plan (1)

Working Group Structure

Working Group Collaboration

Transparency

Broaden the Scope

Volume Strategy

Implementation Strategy

Metrics and Feedback Loop

10Michael C. Daconta February 3, 2005

Plan: Working Group Structure Three tiers

Public participation

Virtual “Wiki” Quarterly F2F Forums

Team participation

Stakeholders, Team Leads/Editors

Bi-Weekly Meetings Business Sponsor Group

Executive Committee

Dispute Resolution Weekly Meetings

Public

Teams

Exec

11Michael C. Daconta February 3, 2005

Plan: Working Group Collaboration Wiki

Team Site and Public Site The “writable” web

File Upload/Download

List-servs drm-public drm-team drm-business drm-mgt

Registry (or Registries) Core.gov Send us your registry requirements!

12Michael C. Daconta February 3, 2005

Plan: Transparency

Principle: the group will operate in an open manner modeled after successful practices of other groups. Example, open resolution of all comments on DRM Volume 1.

Comments will be given an identifier and posted on public wiki (without attribution).

Tiered structured is for logistics management and stakeholder responsibility; not for closed discussion on technical issues.

This group will learn as it goes and be willing to adjust course upon the introduction and agreement on better ideas.

Initial Focus: DRM Volume 1.1

13Michael C. Daconta February 3, 2005

Plan: Revised DRM Structure

Subject Context Security ContextService Context

Information Access

Data Element Description Resource Description

Subject Area

Association

Query ClassAssociation

Resource Class

AssociationData Property

Data Class

Unique Identifiers

Association

Security Class

AssociationSubject ClassAssociation

Input/OutputService Class

Who What When Where Why

Context

Information Exchange

Exchange PayloadAssociation

Exchange Class

Sharing

Description

Structured

Semi-Structured

Unstructured

14Michael C. Daconta February 3, 2005

Plan: Broad Scope

Objective: Broaden participation by State and Local governments and create Performance Measures for the DRM around the Homeland Security mission. Horizontal Information Sharing

Vertical Information Sharing

Address Business Issues and Technical Issues DHS Information Sharing and Collaboration Program (ISCP) will lead a DRM

Business Sponsors Group in conjunction with the OMB and other Stakeholders.

drm-business listserv

State and Local Participation through multiple avenues Susan Turnbull coordinating.

15Michael C. Daconta February 3, 2005

Plan: Volume Strategy

Change the volume strategy from the current plan by creating cohesive volumes around functional lines. Context

Exchange (possibly broadened to Information Sharing)

Description

Data Governance

Sections in each of the above on Security & Privacy

Given broad virtual participation and active Stakeholder involvement, execute the volumes in parallel Too ambitious?

Let’s try and see what happens…

16Michael C. Daconta February 3, 2005

Plan: Implementation Strategy Objective: Enable Consistent Implementation of the DRM

Implementation Profiles

As-Is (RDBMS, Messaging, Portal Taxonomy, etc.)

XML Profile (Led by XML COP)

Semantic Technologies Profile (led by SiCOP) Implementation Workshops and Pilots

Leverage Emerging Technology Workshops Capture Implementation artifacts in a Core Metadata Registry

Several registry options…

Possibly Core.gov (if it satisfies the group’s requirements)

Build capacity of agencies to manage data Work with universities

Vendor participation and support of DRM (i.e. “DRM-Ready” products)

17Michael C. Daconta February 3, 2005

Plan: XML Profile of the DRMSubject Context Security ContextService Context

Information Access

Data Element Description Resource Description

Who What When Where Why

Context

Information ExchangeSharing

DescriptionStructured

Semi-Structured

Unstructured

XML Topic Map& OWL Lite

Web ServiceEntry (UDDI)

IC InformationSecurity Marking

“Message” XMLSchemas

Federated Query& RSS

DODDiscovery

Medata Spec

Core XML SchemaTypes

XLINK

XLINK

XLINK

18Michael C. Daconta February 3, 2005

Plan: Metrics and Feedback Loop

Principle: “What is Measured, Improves.” Separate part of site and group dedicated to quantifiable metrics.

Some suggestions:

# of organizations implementing the DRM Measure: Formal Data Management programs

# of products that are “DRM-Ready”

# of artifacts in a Core Registry # of cross-domain exchanges

Caution: Outcomes versus Actions Business group will also develop metrics for concrete outcomes

19Michael C. Daconta February 3, 2005

Plan: Applying the DRM (non-normative)

Description

Sharing

Context

Org 1Org 2

DataElems

DataElems

Exchange

packages

Registry

COI Context

Core Context

20Michael C. Daconta February 3, 2005

Strawman: Schedule/Milestones NOTES:

NOTE1: Schedule is for Initial Suggestion ONLY – this WILL change after vetting/discussion in initial team meetings.

NOTE2: Progress will be transparent. NOTE3: YOU can influence (read “speed up”) the schedule

4/2005 – Selection of Volume Leads and Multiple Editors. Start the nominations NOW!

(Volume Leads – Government only, Volume Editors – Government or Contractor). “It’s all about Expertise”

8/2005 -- DRM Volume 1.1 (Volume Lead: Michael Daconta, Editors: Michael Daconta & ??? & ???)

2/2006 -- Initial Drafts Volume 2,3,4

8/2006 – Initial Drafts Implementation Profiles

2/2007 – Volumes 2,3,4 Complete

8/2007 – Implementation Profiles Complete

21Michael C. Daconta February 3, 2005

How you can help!

All: Get in your DRM Comments!

Stakeholders – participate on a team! Note: only 1 “working” representative per organization.

Stakeholders MUST have “skin in the game.” i.e. willing to work and willing to implement.

Vendors – participate virtually (or as part of the team if sponsored by a stakeholder). Whitepapers

“DRM-Ready” products (goal: certification)

Comment on this Success Strategy Email: michael.daconta@dhs.gov