Sample Template Community of Interest COI Steering Committee Kickoff

1
Sample TemplateCommunity of Interest
(COI)Steering Committee Kick-off
Date POC
2
Purpose of the COI

• Describe what information sharing problem this
  community will address (preferably in a single
  sentence)

Community of Interest 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. -
DoD Directive 8320.2
3
COI Membership

• Describe key members / stakeholders
• Should be Joint
• Across relevant Military Services, Agencies and
  Combatant Commands)
• Could include non-DoD government agencies,
  coalition partners, and commercial partners
• Should include
• Operators and Users
• Resource Managers Program Managers
• Engineers
• Subject Matter Experts

Membership All producers and consumers of
information relative to this COI are welcome and
encouraged to participate.
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

• Ensure appropriate participation
• Act as primary COI POC
• Track milestones success criteria

Steering Committee Forum (Chair or Co-Chair)
Pilot Demonstration Working Group (Appropriate
Lead/Co-Lead)
Joint Implementation Working Group (Appropriate
Lead/Co-Lead)
Data Management Working Group (Appropriate
Lead/Co-Lead)

• 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

• 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

5
Pilot Purpose
One sentence that describes the increment of COI
information sharing to be addressed by the pilot
in 9-12 months.
6
Pilot Scope

• What programs of record or other sources will
  advertise data as a web-service IAW the agreed
  COI vocabulary?
• Will value-added services will be demonstrated?
  If so, which ones?
• What network(s) will be used to demonstrate
  net-centric capabilities?
• What joint exercise(s) or venue will be used to
  demonstrate net-centric capabilities?
• What organizations are participating?
• Operational representatives from data consumer
  organizations
• Engineers and acquisition representatives from
  data producer organizations
• Etc.

7
Scope of the Data Management Working Group Task
to Support the Pilot
The Data Management WG will develop the community
vocabulary that is necessary to support the COI
pilot.
8
COI Pilot POAM
High-level Graphic with dependencies, decision
points, and final demonstrated illustrated.
Kickoff COI
Interim Pilot Capability
4th SC Meeting
Select Pilot
Vocab Defined
2nd Steering Committee Meeting
1st COI Anniversary
3rd SC Meeting
SAMPLE
Stand up WGs
Capabilities Plan
Services Inventory
Potential Agency Budget Inputs
Integrate Pilot into Ops
OM Plan
9
Discovery Use Case
Infrastructure
NCES SOA Foundation
COI
MDA DS COI Data Producers
Content Discovery
DHS Consumers
Navy Afloat
NAIS
DOD Consumers
AMRS
Volpe
NCES Federated Search
NCES Security Service
DOD
DHS
Defense Online Portal
HSIN Portal
HSIN Identity Store (Portal Authentication)
NCES Service Discovery
Data Sharing
SOA Foundation
10
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 program. Identify
resource shortfalls, impacts, and risk mitigation
efforts.
11
COI Pilot Metrics

• Metrics to assess pilot return on investment
  (ROI)
• Resources as well as net-centric capabilities and
  agility
• Consider what is convincing to seniors
• Some ideas
• 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 NCES
  pilot services
• 5 Level of effort to agree on initial COI
  vocabulary

12
Reference Links

• The DoD Net-Centric Data Strategy
• http//www.defenselink.mil/cio-nii/docs/Net-Centri
  c-Data-Strategy-2003-05-092.pdf
• Data Sharing in a Net-Centric DoD, DODD 8320.2
• http//www.dtic.mil/whs/directives/corres/html
  /832002.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) and
  DDMS Schema
• http//metadata.dod.mil/mdr/irs/DDMS/
• COI Resources
• http//www.dod.mil/nii/coi/