1 / 15

The FEA Data Reference Model V2.0

The FEA Data Reference Model V2.0. Michael C. Daconta, DRM Working Group Lead Susan Turnbull, AIC Representative Mary McCaffery, FEA PMO Representative. Agenda. Background The Problem The Solution: Communities of Interest (COI) DRM Support to COIs Agency Implementation Conclusion.

abie
Download Presentation

The FEA Data Reference Model V2.0

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The FEA Data Reference Model V2.0 Michael C. Daconta, DRM Working Group Lead Susan Turnbull, AIC Representative Mary McCaffery, FEA PMO Representative

  2. Agenda • Background • The Problem • The Solution: Communities of Interest (COI) • DRM Support to COIs • Agency Implementation • Conclusion

  3. EO13356 HSPD-11 Wiki Background • Three part working group • DRM Volume 1.0 – Dec. 2004 • Initial meeting: February 7th, 2005 • Agency participation: 124 • Designated Agency Reps: 30 • Open working group • # of Documents on Wiki: 240 • # participants in workshops: 543 • Highly interactive • # vendor product demonstrations on draft specifications: 4 • We are proud to present the product of your best data architects!

  4. “The biggest impediment to all-source analysis—to a greater likelihood of connecting the dots—is the human or systemic resistance to sharing information.”- 9-11 Commission Report, Pg 416, July 22, 2004 “This area has received increased attention but the federal government still faces formidable challenges sharing information among stakeholders in an appropriate and timely manner to minimize risk.” - GAO, “HIGH-RISK SERIES, An Update”, January 2005, “Equally problematic, individual departments and agencies continue to act as though they own the information they collect, forcing other agencies to pry information from them.” - Commission on Intelligence Capabilities of the US in regard to WMD, Pg 14. March 31, 2005 “Bush’s choice to run Information Sharing Environment draws criticism” - GCN Article, June 3, 2005 “Info Sharing still the missing link.” - Federal Computer Week Article, June 6, 2005 “Intelligence Changes Still Thwarted By Lack Of Information Sharing.” - Information Week Article, June 7, 2005 “This committee has long been concerned about the lack of information sharing and analysis within the government and among the relevant public and private sector parties.” - Rep. Tom Davis, House Government Reform Committee. June 9, 2005. “But we're not as convinced that information sharing between agencies, and the computer technology needed to analyze it, has improved.” - Boston Herald editorial staff, Saturday, June 11, 2005 The Problem • The DRM is a framework whose primary purpose is to enable information sharing and reuse across the federal government via the standard description and discovery of common data and the promotion of robust data management practices.

  5. Communities of Interest • Definition: A collaborative group of users that must exchange information in pursuit of its shared goals, interests, missions, or business processes and therefore must have shared vocabulary for the information it exchanges. • DOD Directive 8320.2

  6. BRM DRM Common Understanding Consistent Models COI Cross-Agency Business Need Improved Discovery Rapid Harmonization Increased Information Sharing Org 1 Org 3 Org 2 Screening Emergency Management COIs are both Intra and Inter- Organization Law Enforcement Intelligence Agility … The DRM is Business-Driven

  7. Data Integration and Interoperability

  8. Data Discovery and Authoritative Sources

  9. Data Sharing of Fixed and Dynamic Business Transactions

  10. DRM Architectural Pattern

  11. How do I implement the Data Description Guidance? • Define COIs • Define Common Data • Conceptual Data Model • Logical Data Model • Precise Definitions • Register Common Data

  12. How do I implement the Data Context Guidance? • Create a Data Asset Inventory • COIs categorize Data Assets • Develop other contexts • Security • Privacy • Service

  13. How do I implement the Data Sharing Guidance? • Only for COI participants • Model Business Transactions • Distinguish between fixed and dynamic transactions • Provision Data Services

  14. Next 20 Days • Due Nov 4: send comments through your representative and/or http://red-team@cosine.cim3.net • Contact Susan Turnbull to arrange on-site briefing or participation in virtual workshops: 10-noon Oct. 26, Nov. 1 and 3, 202-501-6214, susan.turnbull@gsa.gov

  15. Strategic Dialogue • Initial thoughts, reflections … • Implications of DRM for your setting? • Priorities for Harmonization through COIs in FY06? • Potential Pilots for Validation and Testing of DRM? • How COIs Can Reinforce Shared Mission Purposes? • Learning Opportunities for Staff? • Collaborative Roadmap for High Performance on EA 2.0 Framework? • How quickly can the DRM Architectural Pattern improve shared understanding among business and technical perspectives?

More Related