Net-Centric Data Strategy
Download as PPTX, PDF3 likes3,694 views
The COI will establish standards and processes to enable the sharing of geospatial intelligence information among the National Geospatial- Intelligence Agency, the Defense Intelligence Agency, and the National Reconnaissance Office to improve situational awareness and support to military operations.
Net-Centric Data Strategy
- 1. 1 Transforming the Way the DoD Manages Data Office of the DoD CIO Information Policy Directorate Collected Slides Compiled by: Daniel.Risacher@osd.mil DoD CIO(IM), OASD/NII Updated 27 Jul 2006 The slides in this briefing are declared works of the US Government and are not subject to copyright protection in the United States.
- 2. 2 Contents Intro Slides – Einstein Quote – National Defense Strategy Net-centricity – Net-Centricity Objectives – Net-Centric Attributes – GIG IP Convergence – NCES and the GIG Net-Centric Data Strategy – Producer to consumer-centric – Data Strategy documents – Separating Data from Apps – Three Barriers – Visibility – Accessibility – Understandability – The DoD Metadata Registry – A-B-X – Blue Force Tracking Demo DoD Discovery Metadata Specification (DDMS) – DDMS Contents – DDMS Example (BFT) Governance and Portfolios – Mission Areas and Domains – Enterprise vs. COI roles Communities of Interest (COIs) – What is a COI? – Implementing Info Sharing – COI activities (Geeky version) – Sample COI Objectives – Sample COI Organization Chart – Sample COI Pilot POA&M – MDA COI example – Sample Data Management process – MDA Sample Pub-Sub Architecture User-Defined Operational Picture (UDOP) – COP vs UDOP – COP Interfaces (point to point) – WWW Interfaces – UDOP Interfaces – Google Earth as a UDOP – KML as a Community standard – MDA COI UDOP example – C2 SSA UDOP example Pilots – C2 SSA Pilot Architecture (1&2) – DoDI 5000.2 requires Pilots (1&2) Reference Links
- 3. We can't solve problems by using the same kind of thinking we used when we created them. 3 Albert Einstein
- 4. 4 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 to processes, policy, and culture.
- 5. 5 Net-Centricity Objectives Deliver capabilities-based service infrastructure for ubiquitous access to timely, secure, decision-quality information by edge users Enable information providers to post and share any information they hold Enable edge users to: – rapidly and precisely discover and pull information resources – dynamically form collaborative groups for problem solving Provide security for, and coordinated management of, netted information resources Supports transition towards Service-Oriented Architectures (SOAs) which, in turn, supports the shift towards „data interoperability‟ versus „application interoperability‟ Better information for better decisions
- 6. 6 Net-Centric Attributes IPv6 – IP, not point-to-point Security – IA enabled and encrypted communications Dynamic allocation of access – trusted access to net resources Only handle information once – data posted by authoritative sources and visible Post in parallel – data posted as it is created Smart pull – applications encourage data discovery Data centric – data separate from applications Application diversity – applications posted for use Quality of service – data timeliness, accuracy, completeness, ease of use
- 7. Global Information Grid: IP Based The convergence layer! Services and Information Types Internetwork Layer Transport Media Internet Protocol (IP)Multimedia Services Data Terrestrial &Airborne Wireless Fiber Cable Copper Cable Space Telecomm ... Telephony Services Video World-wide acceptance and use Packet-switched Internet transport Provides common- user, integrated services framework Provides standardized interface between Application and Transport Services Used over many network-level protocols (Ethernet, ATM, WAP…)
- 8. Net-Centric Enterprise Services (NCES) GIG Applications and Data Net-Centric Enterprise Services Transformational Communications System (TCS) Joint Tactical Radio System (JTRS) Global Information Grid –Bandwidth Expansion (GIG-BE) - Enterprise Systems Management - Messaging - Discovery - Mediation - User Assist - IA/Security - Storage Services - Application - Collaboration 9 Core Enterprise Services + APIs GIG IP-based Transport Part of the Global Information Grid Net-Centric Enterprise Services (NCES) provide a common set of information capabilities for timely, secure, ubiquitous edge user access to decision-quality information within the GIG. IA/Security EnterpriseServiceManagement
- 9. The Department’s Strategy To move from privately owned and stored data in disparate networks and within legacy systems/applications to an enterprise information environment where authorized known and authorized unanticipated users can access any information and can post their contributions for enterprise- wide access. To Consumer-centric: • Data is visible, accessible and understandable • Shared data – supports planned and unplanned consumers • Shared meaning of the data enables understanding Enabling Net-Centricity Data Strategy Ubiquitous Global Network Metadata Catalogs Enterprise & Community Services Application Services (e.g., Web) Shared Data Space Metadata Registries Security Services (e.g., PKI, SAML) Producer Developer From Producer-centric: • Multiple calls to find data • Private data – only supports planned consumers • Data translation needed for understanding when pulled from multiple sources Consumer Producer and Developer System 1 Data System 2 Data System N Data Consumer ...
- 10. 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 Areas and their respective Domains. 10 Data Sharing in a Net-Centric DoD
- 11. 11 In a Net-Centric Environment Data is separate from Applications, and Data, Value-Added Services, and Applications are: – Visible – must be discoverable by a person (or machine) who is searching for it – Accessible – available to someone (or machine) for use – Understandable – so that it can be acted upon Support Unanticipated User Post Data Assets Data Tagging Smart Pull
- 12. 12 Barriers to Identifying, Accessing and Understanding Data DefiningThe Data Problem End-User Consumer End-User Producer 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 Data Strategy Approach: Discovery Metadata Data Strategy Approach: Web Enabling, Web-service Enabling Data Strategy Approach: Communities of Interest, Metadata Registry
- 13. DDMS: Leverages Industry Standard 13 Make Data Visible DDMS Attributes Security Title Identifier Creator Publisher Contributor Date Rights Language Type Source Subject Geospatial Coverage Temporal Coverage Virtual Coverage Description Format Tag with DoD Discovery Metadata Specification (DDMS) to aid Enterprise search DDMS endorsed by Executive Order 13388 “Further Strengthening The Sharing Of Terrorism Information To Protect Americans” Data Catalog (historical) * * * * * * * mandatory other COI Data creato r Identifier UNCLASSIFIED
- 14. 14 Make Data Accessible Documents – Use common formats – Store in shared spaces accessible via URL Databases – Expose data to applications via web services (application interface for the web) – Expose data to authorized users via browser or thin- client application
- 15. 15 Enable Data To Be Understandable “Secure the Building!” What does it mean? – Navy: “Turn off the lights and lock the doors.” – Army: “Surround the building, occupy, and control entry.” – Marines: “Call in close air support, assault with small team, neutralize occupants, fortify and hold at all costs until properly relieved. SEMPER FI!” and… – Air Force: “Take out a three-year lease with option to buy.” One reason Government Agencies and Military Services have trouble operating jointly is that they speak different languages. Register Terms, Definitions, & Relationships
- 16. DoD Metadata Registry (MDR) and Clearinghouse “One Stop” Publish, Subscribe and Manage capabilities for reusable structural metadata components to aid understanding and translations among applications – Currently 118K XML items (schema, stylesheet etc) registered – 7175 Registered Users from DoD, IC, DHS, NASA and more – Unclassified, Secret and Top Secret instances operating Run Time support available User feedback driven Online user-to-developer DoD Metadata Working Group http://metadata.dod.mil
- 17. 17 DoD Discovery Catalogs DoD Metadata Registry DoD Service Registry Data Producer Data Consumer “Shared Space” Publishing and Subscribing of Data & Services Supporting Both Known and Unanticipated Authorized Users Unanticipated Authorized User of System A Data System X Publish Structural and Semantic Metadata PublishDiscoveryMetadata System B Data exchanged across engineered, well-defined interfaces Known User of System A Data System A All Data Assets are Tagged with DoD Discovery Metadata Specification (DDMS Metadata Leverages Service Oriented Architecture
- 18. 23 April 2013 18 Blue Force Tracking (BFT) COI Service An Implementation of the DoD Net-Centric Data Strategy BFT Content Providers BFT Service Consumers FBCB2/EPLRS Tactical Internet FBCB2 JVMF IP/MCG BFT SVC XML SOAP Air Feed ADSI TADIL-J L-16 BFT SVC XML SOAP FBCB2/MTS/L-Band Ground Station JVMF MTS BFT SVC RM FBCB2 XML SOAP MMC Ground Station BFT SVC RM MMC XML SOAP MDACT/USMC EPLRS/ CNR IOW VDX IP BFT SVC XML SOAP BFT Service PI CI BFT Service PI CI BFT Service PI CI BFT Service PI CI Web Services Info Grid BFT Service PI CI BFT Service (www.bft.smil.mil) Ad/Sub Propagation Query Info Delivery Filtering QoS Consolidation NCES Service Discovery Security Messaging ESM Joint WebCOP C2PC FalconView User Interface F-15 WSO MCS
- 19. 19 DoD Discovery Metadata Specification (DDMS) Core Layer Category Set Primary Category Obligation The Security elements enable the description of security classification and related fields Security Mandatory Resource elements enable the description of maintenance and administration information Title Mandatory Identifier Mandatory Creator Mandatory Publisher Optional Contributor Optional Date Optional Rights Optional Language Optional Type Optional Source Optional The Summary Content elements enable the description of concepts and topics Subject Mandatory Geospatial Coverage Mandatory unless not Applicable Temporal Coverage Mandatory unless not Applicable Virtual Coverage Optional Description Optional The Format elements enable the description of physical attributes of the asset Format Optional The COI Extensible Layer elements enable Communities to define additional discovery metadata COI defined Optional
- 20. 23 April 2013 20 BFT C2 COI – Content Provider Advertisement (DDMS) BFT Content Provider Advertisements “ Army 3rd Infantry Division Unclassified Search and Rescue in AOI1 …” What When Where UNCLASSIFIED
- 21. 21 Business Mission Area Warfighting Mission Area Financial ManagementCore BusinessMission RealPropertyand Installations Management National Intelligence Mission Area In work Enterprise Information Environment Mission Area (Cross-Cutting & Inter-Dependent Domains) Communications Computing Infrastructure Core Enterprise Services Information Assurance BattlespaceAwareness ForceApplication Protection FocusedLogistics BattlespaceComms DoD and Related National Intelligence Information Portfolios 29-Aug-05 HumanResources Management WeaponsSystems LifecycleManagement &Material Supply/Services
- 22. Data Sharing Responsibilities • Develop and maintain vocabularies, taxonomies for data exchange • Register these agreements in DoD metadata Registry • Maintain DoD Metadata Registry • Develop and maintain federated metadata registry for semantic and structural metadata Make data understandable • Implement access services• Maintain repository of acceptable commercial standards for web-based services • Develop and maintain Enterprise federated service registry Make data accessible • Tag data holdings with discovery metadata (DDMS) • Extend for COI specific search criteria • Register access services in Enterprise service registry • Maintain DoD Discovery Metadata Specification (DDMS) to facilitate DoD-wide search • Develop and maintain Enterprise search capability Make data visible What is the Role of the COI? What is the Role of the Enterprise? Key Goal of DoDD 8320.2
- 23. 23 What is a COI? A community formed to solve a data-sharing problem (per DoD Net-Centric Data Strategy) – “What is the information sharing problem we want to solve?” 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!
- 24. 24 Steps to Implement Information Sharing 1. Describe in one sentence the community‟s information sharing problem 2. Identify information assets that must be accessed to solve that information sharing problem 3. Tag information sharing assets with DDMS compliant discovery metadata (DISA has an automated tool) 4. Register discovery metadata with Enterprise search service 5. Implement a service to make the information accessible to authorized users 6. Register metadata about the information asset in the DoD Metadata Registry 7. Develop a standards-based User Defined Operating Picture (UDOP) to view the information assets.
- 25. 25 Technology view of what does a COI does Make their data assets visible and accessible – Visible via service registry (WSDL), metadata registry (XSD), and data catalogs (DDMS) – Accessible via web services and common mime types Define COI-specific vocabularies and taxonomies – Vocabularies to improve data exchange within COI and among COIs – Taxonomies to improve precision discovery Register semantic and structural metadata to the DoD Metadata Registry (http://metadata.dod.mil) – XML Gallery for XML schemas, stylesheets, domain sets, samples – Taxonomy Gallery for discovery taxonomies (OWL syntax) http://www.defenselink.mil/nii/org/cio/doc/COI_FAQ.doc
- 26. 26 Objectives Purpose of the COI: One sentence that describes the information sharing problem that this community wants to solve. 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. Purpose of the COI Pilot: One sentence that describes the net-centric capabilities the COI pilot will demonstrate that begin to solve the information sharing problem, and designates the lead component for the pilot. • Registered Community-based Vocabulary, Schema and Data Services • Repeatable Process – Risk Reduction Pilots for Programs of Record • Adoption/Enforcement Memo to Requirements, Acquisition, and Budgeting Process Owners for Programs of Record
- 27. 27 Sample COI Governance Chart Data Management Working Group (Appropriate Lead/Co-Lead) WGs FOR DISCUSSION PURPOSES ONLY Additional Working Groups as needed Executive Board (FO/GO) Chair or Co-Chair Pilot Demonstration Working Group (Appropriate Lead/Co-Lead) • Develop shared vocabulary for a given problem area in accordance with DoD Net-Centric Data Strategy draft 2 or 3 star level 1 star level Chair with 0-6/GS-15 membership • 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 Steering Committee Forum (Chair or Co-Chair) Joint Implementation Working Group (Appropriate Lead/Co-Lead) • 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)
- 28. 28 COI Pilot Plan of Action & Milestones High-level Graphic with dependencies, decision points, and final demonstrated illustrated. Scope - Metrics - Resources Kickoff COI Stand up WGs Select Pilot Capabilities Plan Metadata Vocab Interim Pilot Capability 1st COI Anniversary Services Inventory 2nd Exec BD Meeting 3rd Exec Bd Meeting 4th Exec BD Meeting O&M Plan Integrate Pilot into Ops Potential Agency Budget Inputs
- 29. Maritime Domain Awareness COI High-Level Pilot Architecture Other COIs DoD/DHS Partnership ! – Unclassified AIS Information MDA DS CoI USCG R&D Center NAIS AMRS ONI PEO C4I & Space Fed Search WebPart HSIN Identity Store (Portal Authentication) Defense OnLine DoD Portal NCES Discovery Service NCES Security Service Discovery, Subscription Navy Afloat TBD DHS DOD Fed Search WebPart Service Registration NCES DoD Net-Centricity Enterprise Architecture HSIN Non-DoD Portal Security Registration, Publication UNCLASSIFIED Infrastructure: NCES SOA Foundation DHS Consumers Interfaces: FS Federated Search Web Service DOD Consumers Content Discovery MP Messaging Publisher MS Messaging Subscriber M Messaging Service
- 30. Sample Data Management WG Process Develop UML Use-Case Class-Relationship Diagram Generate XSD - XML Data Vocabulary and Schema
- 31. Maritime Domain Awareness COI Pilot Pub-Sub Architecture NCES - Early Capability Baseline Messaging Service Common Schema ONI AMRS Coast Guard AIS Navy Organic AIS Google Earth HSIN Falcon View = Wrapper Acronyms AIS := Automated Identification System AMRS := Automated Maritime Reporting System NCES := Net-Centric Enterprise Services HSIN := Homeland Security Information Network Common Schema Common Schema Common Schema Publish Subscribe UDOPProvider Common Schema Common Schema
- 32. 32 COP vs UDOP COP = Common Operational Picture UDOP = User-Defined Operational Picture A COP is a visual representation of a common database shared by some community – The information available is limited to pre-arranged data sources A UDOP is a visual representation of data sources which are available in common to the community – The information available is not pre-determined
- 33. COP External Interfaces EVERY ARROW HAS BEEN PRE-ARRANGED AND ENGINEERED COP vs UDOP (1/4)
- 34. Web Browser Interfaces a counter-example HTTP HTTPS www.defenselink.mil www.google.com www.yahoo.com www.whitehouse.gov www.wikipedia.org www.mit.edu www.something.com www.something-else.net www.nato.int . . . . . . . . www.end-of-the.net The services are standard The data formats are standard The information content and its publication are totally dynamic DNS Registry COP vs UDOP (2/4)
- 35. UDOP Interfaces Service Registry WebCOP-NG SISP Other UDOP App Army Data Provider Navy Data Provider USAF Data Provider USMC Data Provider NRO Data Provider . . . . . . . . . . . . Data You Needed Last Week The services and data formats need to be defined and agreed upon COP vs UDOP (3/4)
- 36. UDOP Interface Agreements User Defined Operational Picture Tracks Overlays Imagery Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys XSys X Sys X Sys X Sys X Sys XSys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Sys X Alerts Data providers publish to the GIG in standard formats Users select what they want on their UDOP Air Force Army Navy/Marine Joint Services COP vs UDOP (4/4)
- 37. Google Earth and the Keyhole Markup Language provide an example of what a UDOP might be like Katrina Damage Assessment 14Sep-10am KMZ file
- 38. <?xml version="1.0" encoding="UTF-8"?> <kml xmlns="http://earth.google.com/kml/2.0"> <Document id="khDocument137739"> <name>Katrina-damage-outages-14Sep-1000</name> <open>1</open> <description>This file contains flooding assessments provided by NGA as of September 14th (Wednesday) at 1000, damage assessments as of September 9th (Friday) at 1000, and road/rail/bridge outages as of September 8th (Thursday) at 1800.</description> ... <ScreenOverlay id="khScreenOverlay137741"> <name>Damage Legend</name> <Icon> <href>images/Legend_050909_1000.JPG</href> </Icon> <overlayXY x="0" y="1" xunits="fraction" yunits="fraction"/> <screenXY x="0" y="1" xunits="fraction" yunits="fraction"/> <rotationXY x="0.5" y="0.5" xunits="fraction" yunits="fraction"/> <size x="0" y="0" xunits="fraction" yunits="fraction"/> </ScreenOverlay> ... <Folder id="khFolder137743"> <name>Damage Assessment</name> <Folder id="layer 0"> <name>Flooded - 14Sep - 1000</name> <S_katrina_receded_flood_all_14sep05_1000_SSSDDDDDD> <name>0</name> ... 38 Keyhole Markup Language (KML) as an example interchange agreement for a UDOP •KML is a de-facto standard for exchange of geospatial data suited for display •Developed by Keyhole, Inc. (now Google Earth) •Documented at http://www.keyhole.com/kml/kml_doc.html
- 39. 39 HSIN implementation of the MDA UDOP OnlyforHSINConsumers….
- 40. 40 C2 SSA COI Pilot User Defined Operating Picture (UDOP) Banner Welcome shows after login Changes to Logout after login (if needed) Main Menu. Select portlet and personalization options. General UDOP Information on Benefits and Features DSCS Portlet (simple chart of IRON summary for new users. Save query and alerts disabled for new users) NavAcc Portlet (default display for new users)
- 41. 23 April 2013 41 C2 SSA COI DSCS Link Status Service UDOP (as of 1 Dec 2005) Consumers Producers/ Developers DDMS Discovery Metadata Schema w/ C2 SSA extensions (XML) Web Services Info Grid Advertise Post Info Request Info Delivery WS Ad WS P WS IR WS ID DSCS Link Status Authoritative Source Web ServiceS D NCES Content Discovery S D WSIR DoD Metadata Registry NCESServices ACCESSIBLE VISIBLE Service AdapterS D C2 SSA DSCS Link Status Display DOL Portal / Content Discovery UI Metadata Registry UI C2 SSA Data Model Schema (XML) C2 SSA Pilot Home Developers UNDERSTANDABLE S D = data flow uses C2 SSA data model schema = data flow uses DDMS Discovery metadata schema = uses NCES Security for authorization and PKI = uses NCES Service Discovery for web service registry NCES Messaging DS Service Registry Register & Discover C2 SSA COI Service = C2 SSA Data Model + NCES Security/Discovery/Adapter + NCES Messaging + DoD Metadata Registry 1 2 3 6 Service AdapterS D SISP UI (Legacy Program Enhancement) Service AdapterS D USSTRATCOM Legacy UI (Cognos)DSCS Link Status Subscription Page = register during development or at initialization 5 5 4 6
- 42. 23 April 2013 42 C2 SSA COI NavAcc Prediction Alert Service UDOP (as of 1 Dec 2005) Consumers Producers/Developers DDMS Discovery Metadata Schema w/ C2 SSA extensions (XML) Web Services Info Grid Advertise Post Info Request Info Delivery WS Ad WS P WS IR WS IDNCES Content Discovery S D Service AdapterS D DoD Metadata Registry NCESServices ACCESSIBLE VISIBLE Metadata Registry UI C2 SSA Data Model Schema (XML) C2 SSA Pilot Home Developers UNDERSTANDABLE S D = data flow uses C2 SSA data model schema = data flow uses DDMS Discovery metadata schema = uses NCES Security for authorization and PKI = uses NCES Service Discovery for web service registry Service Registry = done during development or at initialization C2 SSA NavAcc Prediction Alert UI User Email Inbox GPS NavAcc Prediction Alert Alert Profiles Web ServiceS D NavAcc Predicts GPS Status Change Service Service Adapter S D NCES Messaging DS Register&Discover 1 2 3 4 6 7 9 7 C2 SSA NavAcc Prediction Products UI Existing SISP Navigational Accuracy Application Web Service 5 8 10DOL Portal / Content Discovery UI
- 43. DoDI 5000.2 requires pilots! 3.3.2.1. … requirements are refined through demonstration and risk management …requirements for future increments depend on feedback from users … 3.6.5. … Multiple technology development demonstrations may be necessary … 3.6.6. … identification and development of the technologies necessary for follow-on increments continues in parallel with the acquisition of preceding increments… Post MS-B programs can (and should) spend current-year funds on pilot demonstrations to define the next increment!
- 44. Pilots define the CDD, not the reverse 3.3.2.1. … requirements are refined through demonstration and risk management …requirements for future increments depend on feedback from users … 3.6.7. The project shall exit Technology Development when … the technology for that increment has been demonstrated … During Technology Development, the user shall prepare the Capability Development Document (CDD) … Tech demos for the next increment happen before the CDD is written. Don’t let JCIDS bog you down!
- 45. 45 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 Guidance for Implementing Net-Centric Data Sharing, DOD 8320.2-G http://www.dtic.mil/whs/directives/corres/html/832002g.htm DoD Discovery Metadata Specification (DDMS) http://metadata.DoD.mil/ DDMS Schema information http://metadata.dod.mil/mdr/irs/DDMS/ COI Resources http://www.dod.mil/nii/coi/