1 / 18

Transforming the Way the DoD Manages Data

Government Executive Panel NDIA Net-Centric Operations Conference March 13-16, 2006. Transforming the Way the DoD Manages Data. An Army Officer recently observed, “The Global Information Grid (GIG) exists to connect people with information”. Mike Krieger Director, Information Management

johnk
Download Presentation

Transforming the Way the DoD Manages Data

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. Government Executive Panel NDIA Net-Centric Operations Conference March 13-16, 2006 Transforming the Way the DoD Manages Data An Army Officer recently observed, “The Global Information Grid (GIG) exists to connect people with information” Mike Krieger Director, Information Management OASD(NII)/DoD CIO michael.krieger@osd.mil March 14, 2006

  2. We can't solve problems by using the same kind of thinking we used when we created them. Albert Einstein

  3. National Defense Strategy • March 2005, National Defense Strategy: • Identifies a critical needed capability to “conduct network-centric operations.“ • Explicitly recognizes the need for fundamental change processes, policy, and culture.

  4. B A R R I E RB A R R I E R B A R R I E R B A R R I E R Barriers to Identifying, Accessing and Understanding DataDefining The Data Problem End-User Producer End-User Consumer “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?” 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 User knows this data existsbut cannot access itbecause of organizational and/or technical barriers ? User needs it but is unaware this data exists Organization “A” Organization “B” Organization “C” Data Strategy Approach: Discovery Metadata Data Strategy Approach: Web Enabling, Web-service Enabling Data Strategy Approach: COIs, Metadata Registry

  5. Data Sharing in a Net-Centric DoD • DoDD 8320.2 (signed Dec 2, 2004) directs implementation of the Net­Centric Data Strategy • The Net-Centric Data Strategy (signed May 9, 2003) is a key enabler of the Department’s transformation • The Strategy provides the foundation for managing the Department’s data in a net-centric environment, including: • Ensuring data are visible, accessible, and understandable when needed and where needed to accelerate decision making • “Tagging” of all data (intelligence, non-intelligence, raw, and processed) with metadata to enable discovery by known and unanticipated users in the Enterprise • Posting of all data to shared spaces for users to access except when limited by security, policy, or regulations • Organizing around Communities of Interest (COIs) that are supported by Warfighting, Business, Enterprise Information Environment, and Intelligence Mission Areasand their respective Domains.

  6. Net-Centric Data Strategy Enables Unanticipated Users FBCB2-EPLRS OTH-G SMTP Tactical Internet JVMF IP/MCG FBCB2 DCE API MCS JCDB API MCS-L GCCS-A UNITs CST FBCB2/EPLRS Post data Provide Discovery metadata Tactical Internet XML SOAP JVMF IP/MCG FBCB2 BFT SVC Register structural metadata Shared Space Data Content Focus of Net-Centric Data Strategy System X is an Unanticipated User of System A Data Metadata Catalog DoD Metadata Registry DDMS Compliant “Metacards” Structural Metadata “Pull” data Data Producer Data Consumer Query catalog System X Apply “pulled’ data based on registered metadata structure Focus of Existing Data Administration Policy is Pre-defined Point-to-Point Interfaces Data exchanged across engineered, well-defined interfaces System A System B

  7. What is a COI? • COIs are described in the DoD Net-Centric Data Strategy • A COI is … • a Community • Of people • who are all Interested in something • and need to share information • What does a COI do? • Work together to resolve the issues that affect their community • Establish community standards on how information will be exchanged within the COI • What can’t a COI do? • COIs do not operate systems or provide services • COIs do not submit POMs • COIs do not direct changes to ICDs, ORDs, CDDs, or CPDs However, members of COIs do!

  8. SAMPLECommunity of Interest (COI)Steering Committee Template Date: POC: Version 1.2.5

  9. Purpose of the COI • One sentence that describes the information sharing problem this community is tackling. • Definition of a COI from DOD Directive 8320.2 – • Community of Interest (COI). 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.

  10. Sample COI Organization Chart Executive Board (FO/GO) Chair or Co-Chair 2 or 3 star level 1 star level Chair with 0-6/GS-15 membership Steering Committee Forum (Chair or Co-Chair) WGs Additional Working Groups as needed Data Management Working Group (Appropriate Lead/Co-Lead) Pilot Demonstration Working Group (Appropriate Lead/Co-Lead) Joint Implementation Working Group (Appropriate Lead/Co-Lead) • Develop shared vocabulary for a given problem area in accordance with DoD Net-Centric Data Strategy • Develop repeatable process/capability to demonstrate COI products, e.g data vocabulary, DoD Enterprise service, etc • Leverage NCES services • Execute as risk reduction for next POR spiral development • Define/implement high level COI Capability Roadmap (prioritize data & services to be made available, id program of record (POR), fund spiral if needed, stand up Pilot WG as needed) • Synchronize COI products with JCIDS, Acquisition, PPBE and Mission Areas, (e.g. Business, Warfighting, Intel and EIE) FOR DISCUSSION PURPOSES ONLY

  11. Pilot Purpose Purpose: One sentence that describes the net-centric capabilities the COI pilot will demonstrate, and designates the lead component for the pilot.

  12. Pilot Scope • Scope: • What programs of records or other sources will advertise data as a web-service IAW the agreed COI vocabulary? • What value-added services will be demonstrated? • What network(s) will be used to demonstrate net-centric capabilities? • What joint exercise(s) will be used to demonstrate net-centric capabilities? • What organizations are participating?

  13. Scope of the Data Management Working Group Task to Support the Pilot Describe the initial community vocabulary that is necessary to support the COI pilot.

  14. COI Pilot POA&M High-level Graphic with dependencies, decision points, and final demonstrated illustrated. Metadata Vocab Interim Pilot Capability 4th Exec BD Meeting Kickoff COI Select Pilot 2nd Exec BD Meeting 1st COI Anniversary 3rd Exec Bd Meeting SAMPLE Stand up WGs Capabilities Plan Services Inventory Potential Agency Budget Inputs Integrate Pilot into Ops O&M Plan

  15. GS COI Blue Force Current + 18 Hours Service UDOP (DRAFT) Developers Consumers GS Blue Force Current + 18 Hours UDOP Legacy ISPAN UDOP DOL Portal / Content Discovery UI Metadata Registry UI Service Adapter Service Adapter D D S S WS WS WS ID WS WS ID ID WS ID ID WS IR WS IR IR WS IR IR WS Discover Discover Web Services Info Grid Info Request Info Delivery VISIBLE DoDMetadataRegistry Service Registry = data flow uses TST data model schema Register & Discover NCES Services NCESContentDiscovery D S = data flow uses DDMS Discovery metadata schema Register & Discover = uses NCES Security for authorization and PKI S = uses NCES Service Discovery for web service registry D Web Service D S ACCESSIBLE UNDERSTANDABLE Web Service S D = register during development or at initialization Web Service S D GS Data Model Schema (XML) DDMS w/ GS extensions (XML) Web Service S D C2PC Blue Force Data Authoritative Source AFATDS Producers/ Developers SBMCS TBMCS COI Pilot Systems Architecture SAMPLE

  16. COI Pilot Metrics Metrics to assess the return on investment (ROI) (resources as well as net-centric capabilities and agility) of the pilot. Start-point: #1 - Changes and impact to Programs of Record (POR) involved in the COI Pilot #2 - Initial and incremental costs of web service interfaces to advertise Program of Record (POR) data #3 - User assessment of demonstrated net-centric capabilities #4 – Feedback on ease of use and adoption of CES pilot services #5 – Level of effort to agree on initial COI vocabulary

  17. COI Resources Identify resources required to conduct the pilot. Identify resources broken out by program of record that provides the resources (as a technical risk mitigation effort), and DoD or non-DoD Component that owns the programs. Identify resource shortfalls, impacts, and risk mitigation efforts.

  18. Reference Links The DoD Net-Centric Data Strategy http://www.defenselink.mil/nii/org/cio/doc/Net-Centric-Data-Strategy-2003-05-092.pdf Data Sharing in a Net-Centric DoD, DODD 8320.2 http://www.dtic.mil/whs/directives/corres/html/83202.htm DoD Discovery Metadata Specification (DDMS) http://metadata.DoD.mil/ DDMS Schema information http://diides.ncr.disa.mil/mdreg/user/DDMS.cfm COI Directory https://gesportal.dod.mil/sites/coidirectory

More Related