Presentation on theme: "COI Pilot Capability Development and Deployment Overview"— Presentation transcript:
1COI Pilot Capability Development and Deployment Overview DoD Net-Centric Data Strategy (DS) andCommunity of Interest (COI) TrainingCOI Pilot Capability Development and Deployment Overview2-Day TrainingVersion 08.4For further information OSD at:
2Purpose / OutlinePurpose: Explain the purpose of a COI pilot and describe a recommended process to develop and deploy a successful COI pilotOutlineWhy is a Pilot Valuable?Sample COI Governance StructureRecommended COI Pilot ProcessSummary
3Why is a pilot valuable? Pilots are intended to Perform risk reduction on Programs of RecordInfluence CONOPS, planning and requirements analysisIdentify and resolve issuesProvide state of the art experimentationDevelop and test approachesObtain user feedbackProvide joint capabilities rapidlyImplementing net-centric information sharing requires change in:Mindset: From “Need to Know” to “Responsibility to Share”Governance: Shared capabilities that are jointly managed and fundedPolicies and Procedures:Accreditation processes that are more flexible and have an enterprise perspectiveSecurity policies that accommodate unanticipated usersTechnologies: Services, Service-Oriented Architectures, etc.Scoping a small pilot project will help pave a path toward larger projects when the pilot transitions into Programs of Record
4Sample COI Governance Structure Mission Area & Domain Portfolio ManagersExecutive Board(FO/GO) Chair or Co-ChairPromote & review COI activitiesResolve cross-COI discrepancies2 or 3 star levelMay be collapsed1 star level Chair with 0-6/GS-15 membershipSteering Committee Forum (Chair or Co-Chair)Ensure appropriate participationAct as primary COI POCTrack milestones & success criteriaBriefingFocusJoint ImplementationWorking Group(AppropriateLead/Co-Lead)Data ManagementWorking Group(AppropriateLead/Co-Lead)Pilot Demonstration Working Group(AppropriateLead/Co-Lead)WGsAdditional Working Groupsas neededDefine & implement high level COI capability roadmap and schedule milestonesStand up Pilot WG as neededSynchronize COI products with existing processes (e.g., JCIDS, Acquisition, PPBE)Develop shared vocabulary for a given problem area in accordance with the DoD Net-Centric Data StrategyDevelop repeatable process to demonstrate COI products (e.g, COI vocabulary)Leverage core enterprise servicesExecute as risk reduction for next Pgm of Record (PoR) spiral
5Recommended COI Pilot Process Denotes MajorProcess Milestone1. Determine Scope and Objectives2. Develop Design &Implementation Plan3. Approve Planand FundingJoint Implementation and Pilot Work GroupsPilot Work GroupSteering Committee & Executive BoardIdentify Pilot WorkingGroup LeadDevelop Use Cases and High Level ArchitectureObtain COILeadership ApprovalDefine Pilot Problem Statement(s)Define Plan, Budget, and MilestonesDefine Pilot Objectives and SpiralsIdentify Success Criteria/Metrics4. Develop Data Management PlanCollaborate with Existing Data ProducersPrepare for Next Pilot SpiralCollect MetricsSelect Next PilotData Management Work Group7. Transition Pilot6. Evaluate PilotDefine and Validate Data VocabularyJoint Implementation and Pilot Work GroupsJoint Implementation and Pilot Work GroupsMention may also iterate within a pilot spiral (i.e., within steps 2-5)DocumentUser FeedbackIntegrate withProgram(s) of RecordTest and Demonstrate PilotDesign Service Interfaces and InteractionsGather LessonsLearnedIntegrate with CoreEnterprise ServicesImplement Data ServicesExecute Transition PlanEvaluate Success Criteria/Metrics5. Implement Pilot & DemonstrationPilot Work GroupApprox months
61. Determine Scope and Objectives Select an appropriate Working Group leadIdeally one with a linkage to the targeted Program of Record (PoR)Define an information sharing problem statement (Samples on next chart)Limit pilot scope to 9-12 month effortDefine additional pilot objectives, e.g., use NCES Security & Discovery services, deliver capabilities in 9 monthsDefine pilot spiralsSequence several spirals to implement pilot objectivesConfirm that PoRs intend to incorporate successful pilot capabilitiesIdentify success criteria/metrics, e.g.,Quantify pilot influence and risk reduction to PoRs involvedCompare costs of developing net-centric information sharing vs. traditional point-to-point interfacesAssess if pilot provided capabilities and information are useful to targeted and unanticipated usersAssess lifecycle cost/effort reduction from the use of core enterprise servicesKEY POINT!
7Sample Pilot Problem Statements To reduce the latency of updates to Defense Satellite Communications System (DSCS) Link Status data from 12 hours to 15 minutes, and to provide these updates to the Single Integrated Space Picture (SISP) system as well as to other authenticated consumers via a service interface.To publish vessel position reports from Automatic Identification System (AIS) Aggregation Centers (i.e., US Coast Guard (USCG), Office of Naval Intelligence (ONI), Navy, and Department of Transportation) to authorized subscribers and graphically display that data on several visualization tools (e.g., Google Earth, Google Maps).To provide Time Sensitive Targeting information from the Army’s Advanced Field Artillery Tactical Data System (AFATDS) and Command and Control Personal Computer (C2PC) to authorized users that only have web browser capability.
82. Develop Design and Implementation Plan Develop use cases and scenarios based on pilot problem statementDevelop a high level architecture that includes:Data sourcesVocabulary needsServices to implementCore Enterprise Services usageService interactions to include the tentatively planned information exchange model, e.g.,Request / ResponsePublish / SubscribeAdvertise in combination with Request / ResponseData consumers to be demonstratedSecurity model
92. Develop Design and Implementation Plan (concluded) Conduct meetings up front with appropriate data “owners” to obtain approval to access and share dataWhere needed, raise issues to senior stakeholdersAn MOU may be needed to gain concurrenceDefine pilot plan, budget and milestonesScope is key!Consider sequencing the use cases and scenarios into several iterations to implement and extend the solutionEstablish target milestones to include synchronization with joint exercises, programs of record incremental delivery cycles, and requirements, acquisition and budgeting cyclesIdentify funding requirements for personnel, hardware, software, and other resourcesInclude pilot transition plan
103. Approve Plan and Funding Obtain COI Steering Committee and Executive Board approvalApprove implementation plan includingData access approachData that will be made availableAgreement that planned data access controls sufficeWho has decision authorityCertification and Accreditation (C&A) approachSchedule and milestonesTargeted transition planApprove budget and secure fundingCommit resourcesSteering Committee and Executive Board must include Component Resource SponsorsProgram Manager must agree pilot is a risk mitigation for the next program incrementKEY POINT!KEY POINT!
114. Develop Data Management Plan Collaborate with authoritative data sources to develop vocabularyInvolve all key stakeholders in the Data Management Working GroupCreate information modelsFollow a systematic approach by beginning with modeling the use cases and scenarios, developing a logical data model to support those scenarios, and deriving physical schemas and data definitions from the logical modelReuse existing data models and schemas, where appropriateLeverage DoD & IC Universal core vocabulary where appropriateLeverage other terminology already defined in the DoD metadata registryDetermine how the data asset should be tagged using the DoD Discovery Metadata Specification (DDMS)Extend the DDMS with COI-specific extensions as necessaryRecognize that vocabulary development and maintenance is an iterative processKEY POINT!
125. Implement Pilot & Demonstration Design Service Interfaces and InteractionsDecompose high level architecture into detailed designSpecify service interface incorporating COI approved XML schemaDetermine how to integrate with authoritative data sources to include security models and mechanismsDevelop Information Assurance (IA) approachInvolve Designated Approving Authority (DAA) early to approve requirements and approachDevelop Systems Security Authorization Agreement (SSAA) for pilot environmentImplement Data ServicesLeverage industry standards and design patternsMake services discoverable – register with enterprise service registryIntegrate with Core Enterprise Services (as applicable)Test and Demonstrate PilotDevelop test plan (e.g., unit, performance, user tests)Deploy software to test/demonstration environmentDemonstrate the pilot – coincide with Joint exercise where possible
136. Evaluate Pilot Document user feedback and lessons learned Document pilot experience and lessons learnedInclude user feedback from user testing and demonstrationsCapture and share for each pilot spiralSummarize at pilot conclusionEvaluate pilot successSummarize success criteria / metrics resultsShare with COI Steering Committee and Executive BoardPresent pilot results at next COI Forum
147. Transition PilotIntegrate pilot results with targeted Programs of Record as defined in the pilot transition plan (if appropriate)Identify and prioritize remaining gaps to be fulfilled before pilot can be rolled into productionIncorporate as requirements into Capability Development Documents (CDDs) of relevant Programs of RecordDetermine resource and funding requirementsInform your Portfolio ManagerEnsure COI services are registered in a Service Registry and made available for service discoverySelect a new risk reduction pilotPortfolio Manager fills gaps and detects overlaps and could help ensure that the transition is funded
15Next StepsCustomize the pilot process to meet the needs and structure of your COIA common approach is to have the vocabulary definition run parallel to the early steps of the pilotGain concurrence on the pilot process with the COI Steering CommitteeExecute!
16SummaryPilots can be pathfinders for programs as they implement net-centric information sharingExercise COI approved vocabularyIncrease familiarity with Service Oriented ArchitecturesGain experience with the use of NCES Core Enterprise ServicesObtain user feedback on needed capabilitiesPilots result in risk reduction and inform future program spiralsPost Milestone B (System Development and Demonstration Phase) programs can (and should) spend current year funds on pilot demonstrations to define their next incrementStrong Leaders help Pilots succeed