DRM Evolution 2005 03 17

499 views
443 views

Published on

OMB Federal Enterprise Architecture Data Reference Model

Published in: Business, Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
499
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • DRM Evolution 2005 03 17

    1. 1. Policy Awareness & Data Reference Model (DRM) Amit K. Maitra AF CIO-Architecture Inter-Agency DRM Working Group March 21, 2005
    2. 2. CONTEXT <ul><li>Global Environment </li></ul><ul><li>Changing Technologies </li></ul><ul><li>Revolutionary Moments: The Mandate </li></ul><ul><li>Leadership </li></ul><ul><ul><li>Decisions </li></ul></ul><ul><ul><li>Processes </li></ul></ul><ul><ul><li>Department of Homeland Security </li></ul></ul><ul><ul><li>Department of Air Force </li></ul></ul>
    3. 3. Underlying Theme <ul><li>Fully integrated information systems for a shared data environment </li></ul>
    4. 4. Focus <ul><li>Information, Access, Authorization, Emerging Technologies </li></ul><ul><ul><li>Data Accessibility, Commonality, and Compatibility Design </li></ul></ul><ul><ul><li>Data Dictionary </li></ul></ul><ul><ul><li>Data Locale </li></ul></ul><ul><ul><li>Security & Privacy Assurance </li></ul></ul>
    5. 5. Global Environment <ul><li>Characteristics </li></ul><ul><ul><li>Geographically distributed, dissimilar elements of varying capabilities and responsibilities </li></ul></ul><ul><ul><li>Data distributed to and redistributed among system facilities, interconnected by both private and shared public communications networks </li></ul></ul>
    6. 6. Changing Technologies <ul><li>A Gentle Transition From XML to Resource Description Framework (RDF) </li></ul><ul><li>The purpose of RDF is to give a standard way of specifying data “about” something </li></ul><ul><li>Advantage of using RDF </li></ul><ul><ul><li>If widely used, RDF will help make XML more interoperable </li></ul></ul><ul><ul><ul><ul><ul><li>Promotes the use of standardized vocabularies ... standardized types (classes) and standardized properties </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Provides a structured approach to designing XML documents </li></ul></ul></ul></ul><ul><ul><ul><ul><li>The RDF format is a regular, recurring pattern </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Quickly identifies weaknesses and inconsistencies of non-RDF-compliant XML designs </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><li>Helps us better understand our data! </li></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Positions data for the Semantic Web! </li></ul></ul></ul></ul></ul>
    7. 7. Changing Technologies: Web Ontology Language (OWL) <ul><li>RDF has limited expressive capability </li></ul><ul><li>-- Mostly limited to taxonomic descriptions </li></ul><ul><li>The things we model have complex relationships so we need to capture many different facets, or restrictions on class and property descriptions </li></ul>
    8. 8. Revolutionary Moments: The Mandate “ Our success depends on agencies working as a team across traditional boundaries to serve the American people, focusing on citizens rather than individual agency needs.” ~ President George W. Bush
    9. 9. <ul><li>No common framework or methodology to describe the data and information that supports the processes, activities, and functions of the business </li></ul><ul><li>No definition of the handshake or partnering aspects of information exchange </li></ul><ul><li>Existing systems offer diffused content that is difficult to manage , coordinate, and evolve </li></ul><ul><li>Information is inconsistent and/or classified inappropriately </li></ul><ul><li>Without a common reference, data is easier to duplicate than integrate </li></ul><ul><li>No common method to share data with external partners </li></ul><ul><li>Limited insight into the data needs of agencies outside the immediate domain </li></ul><ul><li>Data and Information context is rarely defined </li></ul><ul><li>Stove piped boundaries , no central registry </li></ul><ul><li>Lack of funding and incentive to share </li></ul><ul><li>Data sensitivity and security of data </li></ul><ul><li>New laws/issues result in continuous adding of databases that can not share data </li></ul>Primary Issues and Information Sharing Barriers The Current Situation : The Federal Government is less than efficient in performing its business and meeting customer needs due to data sharing inefficiencies caused by stove-piped data boundaries Stove-Piped Data Boundaries “ As Is State” Have Created HHS INDUSTRY Illustrative CDC DHS TSA USDA DOI ENERGY LABOR FDA INS Denotes data and information sets within agencies.
    10. 10. The Solution: The Data Reference Model (DRM) The DRM provides: <ul><li>A framework to enable horizontal and vertical information sharing that is independent of agencies and supporting systems </li></ul><ul><li>A framework to enable agencies to build and integrate systems that leverage data from within or outside the agency domain </li></ul><ul><li>A framework that facilitates opportunities for sharing with citizens, external partners and stakeholders </li></ul>Subject Area Data Object Data Property Data Representation Data Classification
    11. 11. MODEL DRIVEN ARCHITECTURE <ul><li>A virtual representation of all physical data sources: </li></ul><ul><ul><li>- Applications are to be decoupled from data sources </li></ul></ul><ul><ul><li>- Details of data storage and retrieval are to be abstracted </li></ul></ul><ul><ul><li>- Are to be easily extended to new information sources </li></ul></ul>The Architecture
    12. 12. The Structure META OBJECT FACILITY
    13. 13. The Tools
    14. 14. Department of Homeland Security and Federated Data Management Approach
    15. 15. The Result: Interagency Information Federation
    16. 16. Paradigm Shift <ul><li>MDA is fundamental change </li></ul><ul><li>MDA rests on MOF </li></ul><ul><li>It is the best architecture for integration </li></ul><ul><li>It shifts data architecture from Entity Relationship Diagramming (ERD) to a Business Context (Interoperability/Information Sharing) </li></ul>Business & Performance Driven Approach
    17. 17. Concerns <ul><li>To what extent the government agencies, Customers, Partners are willing to participate along the Lines of Business (LOB), thereby underscoring the importance of working toward a common goal: Collective Action IAW National Security/National Interests criteria </li></ul><ul><li>These need to be tested and validated against uniquely tailored performance indicators: Inputs, Outputs, and Outcomes </li></ul>
    18. 18. Leadership at DoD <ul><li>Decisions </li></ul><ul><li>Processes </li></ul>
    19. 19. Decisions “ Net-Centric Data Strategy & Communities of Interest (COI)”
    20. 20. The DoD Net-Centric Data Strategy aims at breaking down barriers to information sharing… B A R R I E R B A R R I E R B A R R I E R B A R R I E R “ What data exists?“ “ How do I access the data?” “ How do I know this data is what I need?” “ How can I tell someone what data I need?” “ How do I share my data with others?” “ How do I describe my data so others can understand it?” Organization “A” Organization “B” Organization “C” User is unaware this data exists User knows this data exists but cannot access it because of organizational and/or technical barriers ? User knows data exists and can access it but may not know how to make use of it due to lack of under- standing of what data represents End-User Consumer End-User Producer
    21. 21. The Net-Centric Data Strategy is a key enabler of the Department’s transformation... The Strategy describes key goals to achieving net-centric data management… <ul><li>The Strategy (signed May 9, 2003) provides the foundation for managing the Department’s data in a net-centric environment, including: </li></ul><ul><ul><li>Ensuring data are visible, accessible, and understandable when needed and where needed to accelerate decision making </li></ul></ul><ul><ul><li>“ Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery by known and unanticipated users in the Enterprise </li></ul></ul><ul><ul><li>Posting of all data to shared spaces for users to access except when limited by security, policy, or regulations </li></ul></ul><ul><ul><li>Organizing around Communities of Interest (COIs) that are supported by Warfighting, Business, Enterprise Information Environment, and Intelligence Mission Areas and their respective Domains . </li></ul></ul>
    22. 22. COIs are a key ‘implementer’ of data strategy goals… <ul><li>Tag data assets with COI-defined metadata that enables it to be searched (visible) </li></ul><ul><li>Organize data assets using taxonomies developed by experts within the COI </li></ul><ul><li>Define the structure and business rules for operating with data and information (e.g. define data models, schema, interfaces) </li></ul><ul><li>Identify, define, specify, model, and expose data assets to be reused by the Enterprise as services </li></ul>Key COI Actions: Enable Data to be Trusted Enable Data Interoperability Make Data Accessible Enable Data to be Understandable Make Data Visible Key Goals
    23. 23. Blue Force Tracking (BFT) COI Example Implementation of the Data Strategy…

    ×