1. COI Pilot Capability Development and Deployment Overview
DoD Net-Centric Data Strategy (DS) and
Community of Interest (COI) Training
COI Pilot Capability Development and Deployment Overview
2-Day Training
Version 08.4
For further information OSD at:

2. Purpose / Outline
Purpose: Explain the purpose of a COI pilot and describe a recommended process to develop and deploy a successful COI pilot
Outline
Why is a Pilot Valuable?
Sample COI Governance Structure
Recommended COI Pilot Process
Summary

3. Why is a pilot valuable? Pilots are intended to
Perform risk reduction on Programs of Record
Influence CONOPS, planning and requirements analysis
Identify and resolve issues
Provide state of the art experimentation
Develop and test approaches
Obtain user feedback
Provide joint capabilities rapidly
Implementing net-centric information sharing requires change in:
Mindset: From “Need to Know” to “Responsibility to Share”
Governance: Shared capabilities that are jointly managed and funded
Policies and Procedures:
Accreditation processes that are more flexible and have an enterprise perspective
Security policies that accommodate unanticipated users
Technologies: 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

4. Sample COI Governance Structure
Mission Area & Domain Portfolio Managers
Executive Board
(FO/GO) Chair or Co-Chair
Promote & review COI activities
Resolve cross-COI discrepancies
2 or 3 star level
May be collapsed
1 star level Chair with 0-6/GS-15 membership
Steering Committee Forum (Chair or Co-Chair)
Ensure appropriate participation
Act as primary COI POC
Track milestones & success criteria
Briefing
Focus
Joint Implementation
Working Group
(Appropriate
Lead/Co-Lead)
Data Management
Working Group
(Appropriate
Lead/Co-Lead)
Pilot Demonstration Working Group
(Appropriate
Lead/Co-Lead)
WGs
Additional Working Groups
as needed
Define & implement high level COI capability roadmap and schedule milestones
Stand up Pilot WG as needed
Synchronize 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 Strategy
Develop repeatable process to demonstrate COI products (e.g, COI vocabulary)
Leverage core enterprise services
Execute as risk reduction for next Pgm of Record (PoR) spiral

5. Recommended COI Pilot Process
Denotes Major
Process Milestone
1. Determine Scope and Objectives
2. Develop Design &
Implementation Plan
3. Approve Plan
and Funding
Joint Implementation and Pilot Work Groups
Pilot Work Group
Steering Committee & Executive Board
Identify Pilot Working
Group Lead
Develop Use Cases and High Level Architecture
Obtain COI
Leadership Approval
Define Pilot Problem Statement(s)
Define Plan, Budget, and Milestones
Define Pilot Objectives and Spirals
Identify Success Criteria/Metrics
4. Develop Data Management Plan
Collaborate with Existing Data Producers
Prepare for Next Pilot Spiral
Collect Metrics
Select Next Pilot
Data Management Work Group
7. Transition Pilot
6. Evaluate Pilot
Define and Validate Data Vocabulary
Joint Implementation and Pilot Work Groups
Joint Implementation and Pilot Work Groups
Mention may also iterate within a pilot spiral (i.e., within steps 2-5)
Document
User Feedback
Integrate with
Program(s) of Record
Test and Demonstrate Pilot
Design Service Interfaces and Interactions
Gather Lessons
Learned
Integrate with Core
Enterprise Services
Implement Data Services
Execute Transition Plan
Evaluate Success Criteria/Metrics
5. Implement Pilot & Demonstration
Pilot Work Group
Approx months

6. 1. Determine Scope and Objectives
Select an appropriate Working Group lead
Ideally 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 effort
Define additional pilot objectives, e.g., use NCES Security & Discovery services, deliver capabilities in 9 months
Define pilot spirals
Sequence several spirals to implement pilot objectives
Confirm that PoRs intend to incorporate successful pilot capabilities
Identify success criteria/metrics, e.g.,
Quantify pilot influence and risk reduction to PoRs involved
Compare costs of developing net-centric information sharing vs. traditional point-to-point interfaces
Assess if pilot provided capabilities and information are useful to targeted and unanticipated users
Assess lifecycle cost/effort reduction from the use of core enterprise services
KEY POINT !

7. Sample 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.

8. 2. Develop Design and Implementation Plan
Develop use cases and scenarios based on pilot problem statement
Develop a high level architecture that includes:
Data sources
Vocabulary needs
Services to implement
Core Enterprise Services usage
Service interactions to include the tentatively planned information exchange model, e.g.,
Request / Response
Publish / Subscribe
Advertise in combination with Request / Response
Data consumers to be demonstrated
Security model

9. 2. Develop Design and Implementation Plan (concluded)
Conduct meetings up front with appropriate data “owners” to obtain approval to access and share data
Where needed, raise issues to senior stakeholders
An MOU may be needed to gain concurrence
Define pilot plan, budget and milestones
Scope is key!
Consider sequencing the use cases and scenarios into several iterations to implement and extend the solution
Establish target milestones to include synchronization with joint exercises, programs of record incremental delivery cycles, and requirements, acquisition and budgeting cycles
Identify funding requirements for personnel, hardware, software, and other resources
Include pilot transition plan

10. 3. Approve Plan and Funding
Obtain COI Steering Committee and Executive Board approval
Approve implementation plan including
Data access approach
Data that will be made available
Agreement that planned data access controls suffice
Who has decision authority
Certification and Accreditation (C&A) approach
Schedule and milestones
Targeted transition plan
Approve budget and secure funding
Commit resources
Steering Committee and Executive Board must include Component Resource Sponsors
Program Manager must agree pilot is a risk mitigation for the next program increment
KEY POINT !
KEY POINT !

11. 4. Develop Data Management Plan
Collaborate with authoritative data sources to develop vocabulary
Involve all key stakeholders in the Data Management Working Group
Create information models
Follow 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 model
Reuse existing data models and schemas, where appropriate
Leverage DoD & IC Universal core vocabulary where appropriate
Leverage other terminology already defined in the DoD metadata registry
Determine how the data asset should be tagged using the DoD Discovery Metadata Specification (DDMS)
Extend the DDMS with COI-specific extensions as necessary
Recognize that vocabulary development and maintenance is an iterative process
KEY POINT !

12. 5. Implement Pilot & Demonstration
Design Service Interfaces and Interactions
Decompose high level architecture into detailed design
Specify service interface incorporating COI approved XML schema
Determine how to integrate with authoritative data sources to include security models and mechanisms
Develop Information Assurance (IA) approach
Involve Designated Approving Authority (DAA) early to approve requirements and approach
Develop Systems Security Authorization Agreement (SSAA) for pilot environment
Implement Data Services
Leverage industry standards and design patterns
Make services discoverable – register with enterprise service registry
Integrate with Core Enterprise Services (as applicable)
Test and Demonstrate Pilot
Develop test plan (e.g., unit, performance, user tests)
Deploy software to test/demonstration environment
Demonstrate the pilot – coincide with Joint exercise where possible

13. 6. Evaluate Pilot Document user feedback and lessons learned
Document pilot experience and lessons learned
Include user feedback from user testing and demonstrations
Capture and share for each pilot spiral
Summarize at pilot conclusion
Evaluate pilot success
Summarize success criteria / metrics results
Share with COI Steering Committee and Executive Board
Present pilot results at next COI Forum

14. 7. Transition Pilot
Integrate 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 production
Incorporate as requirements into Capability Development Documents (CDDs) of relevant Programs of Record
Determine resource and funding requirements
Inform your Portfolio Manager
Ensure COI services are registered in a Service Registry and made available for service discovery
Select a new risk reduction pilot
Portfolio Manager fills gaps and detects overlaps and could help ensure that the transition is funded

15. Next Steps
Customize the pilot process to meet the needs and structure of your COI
A common approach is to have the vocabulary definition run parallel to the early steps of the pilot
Gain concurrence on the pilot process with the COI Steering Committee
Execute!

16. Summary
Pilots can be pathfinders for programs as they implement net-centric information sharing
Exercise COI approved vocabulary
Increase familiarity with Service Oriented Architectures
Gain experience with the use of NCES Core Enterprise Services
Obtain user feedback on needed capabilities
Pilots result in risk reduction and inform future program spirals
Post Milestone B (System Development and Demonstration Phase) programs can (and should) spend current year funds on pilot demonstrations to define their next increment
Strong Leaders help Pilots succeed