Fea Drm Akm 2005 03 28

570 views

Published on

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

  • Be the first to like this

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

No notes for slide
  • The DRM provides a common, consistent way of categorizing and describing data to facilitate data sharing and integration
  • Fea Drm Akm 2005 03 28

    1. 1. Federal Enterprise Architecture (FEA) Mandate OMB Reference Models, Data Reference Model (DRM) Initiatives, & AF iTRM Amit K. Maitra (MITRE) HQ AF CIO-A
    2. 2. . Business Reference Model (BRM) <ul><li>Lines of Business </li></ul><ul><li>Agencies, Customers, Partners </li></ul>Service Component Reference Model (SRM) Technical Reference Model (TRM) Business and Performance-Driven Approach Performance Reference Model (PRM) <ul><li>Inputs, Outputs, and Outcomes </li></ul><ul><li>Uniquely Tailored Performance Indicators </li></ul>Federal Enterprise Architecture (FEA) <ul><li>Service Domains, Service Types </li></ul><ul><li>Business and Service Components </li></ul><ul><li>Service Component Interfaces, Interoperability </li></ul><ul><li>Technologies, Recommendations </li></ul>Interoperability / Information Sharing (Business-Context Driven) The Federal Enterprise Architecture (FEA) is a business and performance-based framework to support cross-agency collaboration, transformation, and government-wide improvement Data and Information Reference Model (DRM) <ul><li>Subject Areas, Classifications, Data Elements, </li></ul><ul><li>Data Properties, Data Representations </li></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>
    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. 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
    7. 7. <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.
    8. 8. 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
    9. 9. Pilot Project <ul><li>Integrate DOJ and DHS data </li></ul><ul><li>Explore governance evolution </li></ul><ul><li>Explore framework evolution </li></ul><ul><li>Collaborative funding by DOJ and DHS </li></ul>
    10. 10. National Information Exchange Model (NIEM)
    11. 11. Institutionalizing Information Sharing <ul><li>Business Information Exchange Reference Model </li></ul><ul><ul><li>Incorporates XML Messaging, Federated Query, and Business Rule Execution to solve business problems </li></ul></ul>
    12. 12. Process <ul><li>Facilitate growth of data model through harmonization of new data components </li></ul><ul><li>Coordinate independent project teams within DOJ and DHS </li></ul><ul><li>Provide effective support and assistance for practitioners </li></ul><ul><li>Facilitate discovery of reusable data components </li></ul><ul><li>Facilitate assembly of exchange packages </li></ul>
    13. 13. CORE = Common
    14. 14. Core Data Type Example
    15. 15. Governance View Core U-Core User Organizations COIs UC Committee
    16. 16. Information Sharing Use Case (1) <ul><li>Markle Report—http://www.markle.org/ </li></ul><ul><ul><li>“ Creating a Trusted Network for Homeland Security” </li></ul></ul><ul><li>Vignette 3 </li></ul><ul><ul><li>Scenario—terrorists planning an attack using rail lines and chlorine gas </li></ul></ul>
    17. 17. Information Sharing Use Case (2) <ul><li>Agency X collects data </li></ul><ul><li>Using the DRM, Agency X creates metadata that describes this data in an unambiguous manner </li></ul>Rail Yard Terrorist Organization: + name: “Al Qaeda” Incident + when + where + what + who Zoo Person Chemical Plant Terrorist Terrorist Organization + name Chemical + name Chemical + name: “Chlorine”
    18. 18. Information Sharing Use Case (3) <ul><li>Agency Y needs data to perform analysis </li></ul><ul><li>Agency Y discovers Agency X has the data it needs </li></ul>Target Organization Indicators Vulnerability Capability Law Enforcement Intel Lethal Agent Facility LOB Infrastructure Protection
    19. 19. Information Sharing Use Case (4) <ul><li>Agency Y and Agency X assemble exchange packages </li></ul>Incident Report + who + what + when + where + activity HUMINT Report Threat Report Target Capability Police Incident Infrastructure Incident Critical Noncritical Chemical Plant Rail Yard Zoo
    20. 20. Information Sharing Use Case (5) <ul><li>Data is exchanged </li></ul>CIA Rail Yard Police Dept. Zoo Chemical Plant Infrastructure Protection Intel Law Enforcement Law Analysis Center Industry Analysis Center States Shared Space DHS Threat Report Incident Incident Incident Incident NCTC DHS DHS
    21. 21. Information Sharing Use Case (6) <ul><li>Data is associated in a shared space </li></ul>Shared Space Threat Report 1 Capability: Chlorine Gas Target: Rail Lines Incident 2: Police Incident 3: Chemical Incident 1: Zoo Incident 4: Rail Yard
    22. 22. OMB Inter-Agency DRM WG Position <ul><li>XML does not express rich semantics </li></ul><ul><li>Need stronger languages </li></ul><ul><ul><li>RDF </li></ul></ul><ul><ul><li>OWL </li></ul></ul><ul><ul><li>MOF </li></ul></ul><ul><li>These have XML representation </li></ul><ul><ul><li>Their particular types add a lot </li></ul></ul>
    23. 23. For Better Understanding of Our Data <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><li>If widely used, RDF will help make XML more interoperable </li></ul><ul><ul><li>Promotes the use of standardized vocabularies ... standardized types (classes) and standardized properties </li></ul></ul><ul><li>Provides a structured approach to designing XML documents </li></ul><ul><li>The RDF format is a regular, recurring pattern </li></ul><ul><ul><li>Quickly identifies weaknesses and inconsistencies of non-RDF-compliant XML designs </li></ul></ul><ul><li>Helps us better understand our data! </li></ul><ul><ul><li>Positions data for the Semantic Web! </li></ul></ul>
    24. 24. 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>
    25. 25. DRM Volume Strategies <ul><li>OMB Inter-Agency DRM position is being captured in: </li></ul><ul><ul><li>Volume I: DRM Overview </li></ul></ul><ul><ul><li>Volume II: DRM Management Strategy </li></ul></ul><ul><ul><li>Volume III: Data description </li></ul></ul><ul><ul><li>Volume IV: Data Sharing </li></ul></ul><ul><ul><li>Volume V: Data Context </li></ul></ul>
    26. 26. Infostructure-Technical Reference Model (i-TRM) <ul><li>Provides a common conceptual framework </li></ul><ul><li>Defines a common vocabulary </li></ul><ul><ul><li>Services, domains, sub-domains, interfaces, and their relationships </li></ul></ul>Diverse components within the Air Force can better integrate acquisition, development, and implementation activities in regards to the Air Force Inforstructure
    27. 27. Infostructure-Technical Reference Model (i-TRM) <ul><li>Provides an extensive set of service definitions and relationships </li></ul><ul><ul><li>Increase interoperability </li></ul></ul><ul><ul><li>Improve compatibility </li></ul></ul><ul><ul><li>Enhance warfighter capabilities </li></ul></ul><ul><ul><li>Resolve related issues. </li></ul></ul><ul><li>DOD C4ISR Architecture Framework compliant approach for modeling the technical information of the Enterprise and Infostructure Architectures. </li></ul><ul><li>Describes the main components of an information system, the applications, and the infostructure, itself, as a set of domains and services categorized by functional area. </li></ul><ul><li>These service areas can be implemented on a: </li></ul><ul><ul><li>Single component </li></ul></ul><ul><ul><li>Collection of homogeneous or heterogeneous systems that comprise the AF Infostructure. </li></ul></ul>

    ×