FEA DRM Success Strategy. Michael C. Daconta Metadata Program Manager February 3, 2005. DHS Metadata Program Manager DHS Data Management Strategy Expose and Exchange Standardize and Govern Integrate and Federate Technical Lead of the DRM Working Group
Michael C. DacontaMetadata Program ManagerFebruary 3, 2005
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
See latest article on Formal Taxonomies at XML.comSpeaker Introduction
We had it all wrong…
In the beginning…
Put the “smarts” in the data… watch what happens…
Strengthening the Sharing of Terrorism Information to Protect Americans
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
Foster Broad Government and Vendor AdoptionScope (3)
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
Please share with us your Measures of Success and Performance MetricsMeasures of Success
Working Group Structure it is successful?
Working Group Collaboration
Broaden the Scope
Metrics and Feedback LoopImplementation Plan (1)
Three tiers it is successful?
Quarterly F2F Forums
Stakeholders, Team Leads/Editors
Business Sponsor Group
Weekly MeetingsPlan: Working Group Structure
Wiki it is successful?
Team Site and Public Site
The “writable” web
Registry (or Registries)
Send us your registry requirements!Plan: Working Group Collaboration
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.1Plan: Transparency
Plan: Revised DRM Structure after successful practices of other groups.
Data Element Description
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.
State and Local Participation through multiple avenues
Susan Turnbull coordinating.Plan: Broad Scope
Change the volume strategy from the current plan by creating cohesive volumes around functional lines.
Exchange (possibly broadened to Information Sharing)
Sections in each of the above on Security & Privacy
Given broad virtual participation and active Stakeholder involvement, execute the volumes in parallel
Let’s try and see what happens…Plan: Volume Strategy
Objective: Enable Consistent Implementation of the DRM cohesive volumes around functional lines.
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)Plan: Implementation Strategy
Plan: XML Profile of the DRM cohesive volumes around functional lines.
XML Topic Map
& OWL Lite
Data Element Description
Core XML Schema
Principle: “What is Measured, Improves.” cohesive volumes around functional lines.
Separate part of site and group dedicated to quantifiable metrics.
# 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 outcomesPlan: Metrics and Feedback Loop
NOTES cohesive volumes around functional lines.:
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 CompleteStrawman: Schedule/Milestones
All: Get in your DRM Comments! cohesive volumes around functional lines.
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).
“DRM-Ready” products (goal: certification)
Comment on this Success Strategy
Email: [email protected]How you can help!