Net-Centric Data Strategy


Published on

In 2003, the DoD CIO published the "Net-Centric Data Strategy". This briefing was a collection of the many slides that we used between 2003-2006 to articulate the concepts of the strategy and the value of information sharing. It addresses the essentials of Net-Centricity, the goals and approaches of the Data Strategy, Communities of Interest, Common Operational Picture COP) vs. User-Defined Operational Picture (UDOP).

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Net-Centric Data Strategy

  1. 1. 1Transforming the Way the DoD Manages DataOffice of the DoD CIOInformation Policy DirectorateCollected SlidesCompiled by:Daniel.Risacher@osd.milDoD CIO(IM), OASD/NIIUpdated 27 Jul 2006The slides in this briefing aredeclared works of the US Governmentand are not subject to copyrightprotection in the United States.
  2. 2. 2Contents 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. 3. We cant solve problems byusing the same kind ofthinking we used when wecreated them.3Albert Einstein
  4. 4. 4National Defense Strategy March 2005, National Defense Strategy:– Identifies a critical needed capability to“conduct network-centric operations.“– Explicitly recognizes the need forfundamental change toprocesses, policy, and culture.
  5. 5. 5Net-Centricity Objectives Deliver capabilities-based service infrastructure for ubiquitousaccess to timely, secure, decision-quality information by edgeusers Enable information providers to post and share any informationthey hold Enable edge users to:– rapidly and precisely discover and pull informationresources– dynamically form collaborative groups for problem solving Provide security for, and coordinated management of, nettedinformation resources Supports transition towards Service-Oriented Architectures(SOAs) which, in turn, supports the shift towards „datainteroperability‟ versus „application interoperability‟Better information for better decisions
  6. 6. 6Net-Centric Attributes IPv6 – IP, not point-to-point Security – IA enabled and encryptedcommunications Dynamic allocation of access – trustedaccess to net resources Only handle information once – data postedby authoritative sources and visible Post in parallel – data posted as it is created Smart pull – applications encourage datadiscovery Data centric – data separate from applications Application diversity – applications posted foruse Quality of service – datatimeliness, accuracy, completeness, ease ofuse
  7. 7. Global Information Grid: IP BasedThe convergence layer!ServicesandInformation TypesInternetwork LayerTransport MediaInternet Protocol (IP)MultimediaServicesDataTerrestrial&AirborneWirelessFiberCableCopperCableSpaceTelecomm ...TelephonyServicesVideo World-wideacceptance and use Packet-switchedInternet transport Provides common-user, integratedservices framework Providesstandardizedinterface betweenApplication andTransport Services Used over manynetwork-levelprotocols (Ethernet,ATM, WAP…)
  8. 8. Net-Centric Enterprise Services(NCES)GIGApplicationsand DataNet-CentricEnterpriseServicesTransformational 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 - Collaboration9 Core Enterprise Services + APIsGIG IP-basedTransportPart of the Global Information GridNet-Centric Enterprise Services (NCES) provide a common set ofinformation capabilities for timely, secure, ubiquitous edge useraccess to decision-quality information within the GIG.IA/SecurityEnterpriseServiceManagement
  9. 9. The Department’s StrategyTo move from privately owned and stored data in disparate networks andwithin legacy systems/applications to an enterprise informationenvironment where authorized known and authorized unanticipated userscan 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 unplannedconsumers• Shared meaning of the data enablesunderstandingEnabling Net-Centricity  Data StrategyUbiquitous Global NetworkMetadataCatalogsEnterprise &CommunityServicesApplicationServices(e.g., Web)SharedData SpaceMetadataRegistriesSecurity Services(e.g., PKI, SAML)ProducerDeveloperFrom Producer-centric:• Multiple calls to find data• Private data – only supports plannedconsumers• Data translation needed for understandingwhen pulled from multiple sourcesConsumerProducerandDeveloperSystem 1 DataSystem 2 DataSystem N DataConsumer...
  10. 10.  DoDD 8320.2 (signed Dec 2, 2004) directs implementation of theNet-Centric Data Strategy The Net-Centric Data Strategy (signed May 9, 2003) is a key enabler ofthe Department‟s transformation The Strategy provides the foundation for managing the Department‟sdata in a net-centric environment, including:– Ensuring data are visible, accessible, and understandable whenneeded and where needed to accelerate decision making– “Tagging” of all data (intelligence, non-intelligence, raw, andprocessed) with metadata to enable discovery by known andunanticipated users in the Enterprise– Posting of all data to shared spaces for users to access exceptwhen limited by security, policy, or regulations– Organizing around Communities of Interest (COIs) that aresupported by Warfighting, Business, Enterprise InformationEnvironment, and Intelligence Mission Areas and their respectiveDomains.10Data Sharing in a Net-Centric DoD
  11. 11. 11In a Net-Centric EnvironmentData is separate from Applications, andData, Value-Added Services, and Applications are:– Visible – must be discoverable by a person (ormachine) who is searching for it– Accessible – available to someone (or machine)for use– Understandable – so that it can be acted uponSupport Unanticipated UserPost Data AssetsData TaggingSmart Pull
  12. 12. 12Barriers to Identifying, Accessing and Understanding DataDefiningThe Data ProblemEnd-User Consumer End-User ProducerB 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 iswhat I need?”“How can I tell someonewhat data I need?”“How do I share my datawith others?”“How do I describe mydata so others canunderstand it?”Organization “A” Organization “B” Organization “C”User isunaware thisdata existsUser knows this data existsbut cannot access itbecause oforganizationaland/ortechnical barriers?User knows data exists and canaccess it but may notknow how to makeuse of it due tolack of under-standing ofwhat data representsData Strategy Approach:DiscoveryMetadataData Strategy Approach:Web Enabling,Web-service EnablingData Strategy Approach:Communities of Interest,Metadata Registry
  13. 13. DDMS: Leverages Industry Standard 13Make Data VisibleDDMS AttributesSecurityTitleIdentifierCreatorPublisherContributorDateRightsLanguageTypeSourceSubjectGeospatialCoverageTemporal CoverageVirtual CoverageDescriptionFormatTag with DoD Discovery Metadata Specification(DDMS) to aid Enterprise searchDDMS endorsed byExecutive Order 13388“Further Strengthening TheSharing Of TerrorismInformation To ProtectAmericans”Data Catalog(historical)******* mandatoryotherCOI DatacreatorIdentifierUNCLASSIFIED
  14. 14. 14Make Data Accessible Documents– Use common formats– Store in shared spacesaccessible via URL Databases– Expose data to applicationsvia web services (applicationinterface for the web)– Expose data to authorizedusers via browser or thin-client application
  15. 15. 15Enable 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 smallteam, neutralize occupants, fortify and hold at all costs untilproperly relieved. SEMPER FI!”and…– Air Force: “Take out a three-year lease with option to buy.”One reason Government Agencies and Military Services havetrouble operating jointly is that they speak different languages.Register Terms, Definitions, & Relationships
  16. 16. DoD Metadata Registry (MDR) andClearinghouse “One Stop” Publish, Subscribe and Manage capabilitiesfor reusable structural metadata components to aidunderstanding 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
  17. 17. 17DoDDiscoveryCatalogsDoD Metadata RegistryDoD ServiceRegistryData ProducerData Consumer“Shared Space”Publishing and Subscribing of Data & ServicesSupporting Both Known and Unanticipated Authorized UsersUnanticipated Authorized Userof System A DataSystem XPublishStructural and SemanticMetadataPublishDiscoveryMetadata System BData exchanged acrossengineered, well-definedinterfacesKnown Userof System A DataSystem AAll Data Assets areTagged with DoDDiscovery MetadataSpecification (DDMSMetadataLeveragesService Oriented Architecture
  18. 18. 23 April 2013 18Blue Force Tracking (BFT) COI ServiceAn Implementation of the DoD Net-Centric Data StrategyBFT Content ProvidersBFT ServiceConsumersFBCB2/EPLRSTacticalInternet FBCB2JVMFIP/MCGBFTSVCXMLSOAPAir FeedADSITADIL-JL-16BFTSVCXMLSOAPFBCB2/MTS/L-BandGroundStationJVMFMTSBFTSVCRM FBCB2XMLSOAPMMCGroundStationBFTSVCRM MMCXMLSOAPMDACT/USMCEPLRS/CNR IOWVDXIPBFTSVCXMLSOAPBFT ServicePICIBFT ServicePICIBFT ServicePICIBFT ServicePICIWeb Services Info GridBFT ServicePICIBFT Service( ConsolidationNCESServiceDiscoverySecurity Messaging ESMJointWebCOPC2PCFalconViewUser InterfaceF-15 WSOMCS
  19. 19. 19DoD Discovery Metadata Specification (DDMS)Core Layer Category Set Primary Category ObligationThe Security elements enable the descriptionof security classification and related fieldsSecurity MandatoryResource elements enable the description ofmaintenance and administration informationTitle MandatoryIdentifier MandatoryCreator MandatoryPublisher OptionalContributor OptionalDate OptionalRights OptionalLanguage OptionalType OptionalSource OptionalThe Summary Content elements enable thedescription of concepts and topicsSubject MandatoryGeospatial CoverageMandatory unlessnot ApplicableTemporal CoverageMandatory unlessnot ApplicableVirtual Coverage OptionalDescription OptionalThe Format elements enable the descriptionof physical attributes of the assetFormat OptionalThe COI Extensible Layer elements enableCommunities to define additional discoverymetadataCOI defined Optional
  20. 20. 23 April 2013 20BFT C2 COI – Content ProviderAdvertisement (DDMS)BFT Content Provider Advertisements“ Army 3rd Infantry DivisionUnclassifiedSearch and RescueinAOI1 …”WhatWhenWhereUNCLASSIFIED
  21. 21. 21BusinessMission AreaWarfightingMission AreaFinancialManagementCoreBusinessMissionRealPropertyandInstallationsManagementNationalIntelligenceMission AreaIn workEnterprise Information EnvironmentMission Area(Cross-Cutting & Inter-Dependent Domains)Communications ComputingInfrastructureCoreEnterpriseServicesInformation AssuranceBattlespaceAwarenessForceApplicationProtectionFocusedLogisticsBattlespaceCommsDoD and Related National Intelligence Information Portfolios29-Aug-05HumanResourcesManagementWeaponsSystemsLifecycleManagement&MaterialSupply/Services
  22. 22. Data Sharing Responsibilities• Develop and maintainvocabularies, taxonomies fordata exchange• Register these agreements inDoD metadata Registry• Maintain DoD Metadata Registry• Develop and maintain federatedmetadata registry for semanticand structural metadataMake dataunderstandable• Implement access services• Maintain repository ofacceptable commercial standardsfor web-based services• Develop and maintain Enterprisefederated service registryMake dataaccessible• Tag data holdings withdiscovery metadata (DDMS)• Extend for COI specificsearch criteria• Register access services inEnterprise service registry• Maintain DoD DiscoveryMetadata Specification (DDMS) tofacilitate DoD-wide search• Develop and maintain Enterprisesearch capabilityMake data visibleWhat is the Role ofthe COI?What is the Role of theEnterprise?Key Goal of DoDD8320.2
  23. 23. 23What is a COI? A community formed to solve a data-sharingproblem (per DoD Net-Centric Data Strategy)– “What is the information sharing problem we want tosolve?” What does a COI do?– Work together to resolve the issues that affect theircommunity– Establish community standards on how information willbe 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, orCPDsHowever, members of COIs do!
  24. 24. 24Steps to Implement Information Sharing1. Describe in one sentence the community‟s information sharingproblem2. Identify information assets that must be accessed to solve thatinformation sharing problem3. Tag information sharing assets with DDMS compliant discoverymetadata (DISA has an automated tool)4. Register discovery metadata with Enterprise search service5. Implement a service to make the information accessible toauthorized users6. Register metadata about the information asset in the DoDMetadata Registry7. Develop a standards-based User Defined Operating Picture(UDOP) to view the information assets.
  25. 25. 25Technology 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 andamong COIs– Taxonomies to improve precision discovery Register semantic and structural metadata to the DoDMetadata Registry (– XML Gallery for XML schemas, stylesheets, domainsets, samples– Taxonomy Gallery for discovery taxonomies (OWL syntax)
  26. 26. 26ObjectivesPurpose of the COI: One sentence that describes the information sharingproblem 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 mustexchange information in pursuit of its shared goals, interests, missions, orbusiness processes and therefore must have shared vocabulary for theinformation it exchanges.Purpose of the COI Pilot: One sentence that describes the net-centriccapabilities the COI pilot will demonstrate that begin to solve theinformation sharing problem, and designates the lead component for thepilot.• Registered Community-based Vocabulary, Schema and Data Services• Repeatable Process – Risk Reduction Pilots for Programs of Record• Adoption/Enforcement Memo to Requirements, Acquisition, andBudgeting Process Owners for Programs of Record
  27. 27. 27Sample COI Governance ChartData ManagementWorking Group(AppropriateLead/Co-Lead)WGsFOR DISCUSSION PURPOSES ONLYAdditionalWorking Groupsas neededExecutive Board(FO/GO) Chair or Co-ChairPilot DemonstrationWorking Group(AppropriateLead/Co-Lead)• Develop sharedvocabulary for agiven problemarea inaccordance withDoD Net-CentricData Strategydraft2 or 3 star level1 star level Chairwith 0-6/GS-15membership• Develop repeatableprocess/capabilityto demonstrate COIproducts, e.g datavocabulary, DoDEnterpriseservice, etc• LeverageNCES services• Execute as riskreduction fornext POR spiraldevelopmentSteering Committee Forum(Chair or Co-Chair)Joint ImplementationWorking Group(AppropriateLead/Co-Lead)• Define/implement high levelCOI Capability Roadmap(prioritize data & services to bemade available, id program ofrecord (POR), fund spiral ifneeded, stand up Pilot WG asneeded)• Synchronize COI products withJCIDS, Acquisition, PPBE andMission Areas, (e.g. Business,Warfighting, Intel and EIE)
  28. 28. 28COI Pilot Plan of Action & MilestonesHigh-level Graphic with dependencies, decisionpoints, and final demonstrated illustrated.Scope - Metrics - ResourcesKickoffCOIStand upWGsSelectPilotCapabilitiesPlanMetadataVocabInterimPilotCapability 1st COIAnniversaryServicesInventory2nd Exec BDMeeting 3rd Exec BdMeeting4th Exec BDMeetingO&MPlanIntegratePilotinto OpsPotentialAgencyBudgetInputs
  29. 29. Maritime Domain Awareness COIHigh-Level Pilot ArchitectureOtherCOIsDoD/DHS Partnership ! – Unclassified AIS InformationMDA DS CoIUSCG R&DCenterNAISAMRSONIPEO C4I &SpaceFed SearchWebPartHSINIdentity Store(Portal Authentication)DefenseOnLineDoD PortalNCESDiscoveryServiceNCES SecurityService Discovery,SubscriptionNavyAfloatTBDDHS DODFed SearchWebPartServiceRegistrationNCESDoD Net-CentricityEnterprise ArchitectureHSINNon-DoD PortalSecurityRegistration,PublicationUNCLASSIFIEDInfrastructure:NCES SOA FoundationDHS ConsumersInterfaces:FSFederated SearchWeb ServiceDOD ConsumersContent DiscoveryMPMessagingPublisherMSMessagingSubscriberMMessagingService
  30. 30. Sample Data Management WG ProcessDevelop UML Use-CaseClass-Relationship DiagramGenerate XSD - XMLData Vocabulary and Schema
  31. 31. Maritime Domain Awareness COIPilot Pub-Sub ArchitectureNCES -EarlyCapabilityBaselineMessagingServiceCommon SchemaONIAMRSCoastGuardAISNavyOrganicAISGoogleEarthHSINFalconView= WrapperAcronymsAIS := Automated Identification SystemAMRS := Automated Maritime Reporting SystemNCES := Net-Centric Enterprise ServicesHSIN := Homeland Security Information NetworkCommon SchemaCommon SchemaCommon SchemaPublish Subscribe UDOPProviderCommon SchemaCommon Schema
  32. 32. 32COP vs UDOP COP = Common Operational Picture UDOP = User-Defined Operational Picture A COP is a visual representation of a common databaseshared by some community– The information available is limited to pre-arrangeddata sources A UDOP is a visual representation of data sourceswhich are available in common to the community– The information available is not pre-determined
  34. 34. Web Browser Interfacesa services arestandardThe data formatsare standardThe information contentand its publication aretotally dynamicDNSRegistryCOP vs UDOP (2/4)
  35. 35. UDOP InterfacesServiceRegistryWebCOP-NGSISPOther UDOP AppArmy Data ProviderNavy Data ProviderUSAF Data ProviderUSMC Data ProviderNRO Data Provider............Data You NeededLast WeekThe servicesand dataformatsneed to bedefined andagreed uponCOP vs UDOP (3/4)
  36. 36. UDOP Interface AgreementsUserDefinedOperationalPictureTracksOverlaysImagerySys XSys XSys XSys XSys XSys XSys XSys XSys X Sys XSys X Sys XSys XSys XSys XSys X Sys X Sys X Sys XSys XSys XSys XSys XSys X Sys XSys XSys XSys XAlertsData providers publish to the GIG in standard formatsUsers select what they want on their UDOPAir Force Army Navy/MarineJoint ServicesCOP vs UDOP (4/4)
  37. 37. Google Earth and the Keyhole Markup Languageprovide an example of what a UDOP might be likeKatrina Damage Assessment 14Sep-10am KMZ file
  38. 38. <?xml version="1.0" encoding="UTF-8"?><kml xmlns=""><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) at1000, damage assessments as of September 9th (Friday) at 1000, and road/rail/bridge outages as ofSeptember 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>...38Keyhole Markup Language (KML)as an example interchange agreement for a UDOP•KML is a de-facto standard forexchange of geospatial datasuited for display•Developed by Keyhole, Inc.(now Google Earth)•Documented at
  39. 39. 39HSIN implementation of the MDA UDOPOnlyforHSINConsumers….
  40. 40. 40C2 SSA COI Pilot User Defined OperatingPicture (UDOP)BannerWelcome showsafter loginChanges to Logoutafter login (ifneeded)Main Menu. Selectportlet andpersonalizationoptions.General UDOPInformation onBenefits andFeaturesDSCS Portlet(simple chart ofIRON summary fornew users. Savequery and alertsdisabled for newusers)NavAcc Portlet(default display fornew users)
  41. 41. 23 April 2013 41C2 SSA COI DSCS Link Status Service UDOP (as of 1 Dec 2005)ConsumersProducers/DevelopersDDMSDiscoveryMetadata Schemaw/ C2 SSA extensions(XML)Web Services Info GridAdvertisePostInfo RequestInfo DeliveryWS AdWS PWS IRWS IDDSCS Link StatusAuthoritative SourceWeb ServiceS DNCESContentDiscoveryS DWSIRDoDMetadataRegistryNCESServicesACCESSIBLEVISIBLEServiceAdapterS DC2 SSADSCS LinkStatus DisplayDOL Portal /ContentDiscovery UIMetadataRegistry UIC2 SSAData ModelSchema(XML)C2 SSA PilotHomeDevelopersUNDERSTANDABLESD= data flow usesC2 SSA data modelschema= data flow usesDDMS Discoverymetadata schema= uses NCESSecurity forauthorization andPKI= uses NCESService Discoveryfor web serviceregistryNCESMessagingDSService RegistryRegister & DiscoverC2 SSA COI Service = C2 SSA Data Model + NCES Security/Discovery/Adapter + NCES Messaging + DoD Metadata Registry12 36ServiceAdapterS DSISP UI(LegacyProgramEnhancement)ServiceAdapterS DUSSTRATCOMLegacy UI(Cognos)DSCS Link StatusSubscriptionPage= register duringdevelopmentor at initialization554 6
  42. 42. 23 April 2013 42C2 SSA COI NavAcc Prediction Alert Service UDOP (as of 1 Dec 2005)ConsumersProducers/DevelopersDDMSDiscoveryMetadata Schemaw/ C2 SSA extensions(XML)Web Services Info GridAdvertisePostInfo RequestInfo DeliveryWS AdWS PWS IRWS IDNCESContentDiscoveryS DServiceAdapterS DDoDMetadataRegistryNCESServicesACCESSIBLEVISIBLEMetadataRegistry UIC2 SSAData ModelSchema(XML)C2 SSA PilotHomeDevelopersUNDERSTANDABLESD= data flow usesC2 SSA data modelschema= data flow usesDDMS Discoverymetadata schema= uses NCESSecurity forauthorization andPKI= uses NCESService Discoveryfor web serviceregistryService Registry= done duringdevelopment or atinitializationC2 SSANavAccPredictionAlert UI User EmailInboxGPS NavAccPrediction AlertAlertProfilesWeb ServiceS DNavAccPredictsGPS StatusChange ServiceServiceAdapterS DNCESMessagingDSRegister&Discover12 346797C2 SSANavAccPredictionProducts UIExisting SISPNavigationalAccuracyApplicationWeb Service5810DOL Portal /ContentDiscovery UI
  43. 43. DoDI 5000.2 requires pilots! … requirements are refinedthrough demonstration and riskmanagement …requirementsfor future increments depend onfeedback from users …3.6.5. … Multiple technologydevelopment demonstrationsmay be necessary …3.6.6. … identification anddevelopment of thetechnologies necessary forfollow-on increments continuesin parallel with the acquisition ofpreceding increments…Post MS-B programs can (and should) spend current-year fundson pilot demonstrations to define the next increment!
  44. 44. Pilots define the CDD, not the reverse3.3.2.1. … requirements are refinedthrough demonstration and riskmanagement …requirementsfor future increments depend onfeedback from users …3.6.7. The project shall exitTechnology Development when… the technology for thatincrement has beendemonstrated … DuringTechnology Development, theuser shall prepare theCapability DevelopmentDocument (CDD) …Tech demos for the next increment happen before the CDD is written.Don’t let JCIDS bog you down!
  45. 45. 45Reference LinksThe DoD Net-Centric Data Strategy Sharing in a Net-Centric DoD, DODD 8320.2 for Implementing Net-Centric Data Sharing, DOD8320.2-G Discovery Metadata Specification (DDMS) Schema information Resources
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.