Sample Template Community of Interest (COI) Steering Committee Kick-off

1
Sample TemplateCommunity of Interest
(COI)Steering Committee Kick-off
V08.4
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.02
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 net-centric
information sharing capability solution to the
9-12 month increment of the information sharing
problem the COI pilot will demonstrate
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 be demonstrated? If
  so, which ones?
• What network(s) will be used to demonstrate
  net-centric information sharing capabilities?
• What joint exercise(s) or venue will be used to
  demonstrate net-centric information sharing
  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 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
POAM Plan of Action and Milestones
9
Sample Use Case
Infrastructure
NCES SOA Foundation
COI Data Producers
COI
Content Discovery
DOD Consumers
Other Consumers
NCES Federated Search
NCES Security Service
DOD
Other
Defense Online Portal
Portal
Identity Store (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 information
  sharing 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
  information sharing 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/

13
Example of Populated TemplateMaritime Domain
Awareness Data Sharing Community of Interest (MDA
DS COI)Kick-off
Date Oct 2007 POC Brian Freeman
14
Purpose of the COI

• To improve global maritime situational awareness
  by sharing information related to vessels, cargo,
  and people amongst MDA stakeholders.

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
15
Spiral 1 COI Membership

• Executive Board
• US Coast Guard (co-lead)
• NORAD-USNORTHCOM (co-lead)
• Steering Committee
• US Coast Guard (co-lead)
• NORAD-USNORTHCOM (co-lead)
• Data Management Working Group
• Office of Naval Intelligence (co-lead)
• US Coast Guard (co-lead)
• Naval Research Laboratory
• NORAD-USNORTHCOM
• Office of the Director of National Intelligence
• Pilot Working Group
• PEO C4I (lead)
• Department of Transportation (i.e. VOLPE Center)
• Office of Naval Intelligence
• US Coast Guard
• Navy
• Joint Implementation Working Group

Membership All producers and consumers of
information relative to Maritime Domain Awareness
are welcome and encouraged to participate.
16
MDA DS COI Spiral 1 Governance Structure
MDA DS COI Executive Board
FO/GO Co-leads DoD NORAD-USNORTHCOM DHS US
Coast Guard
MDA DS COI Steering Committee
O-6/GS-15 Co-leads DoD NORAD-USNORTHCOM DHS US
Coast Guard
Joint Implementation Working Group (DoD DHS
Co-Leads)
Data Management Working Group (DoD DHS
Co-Leads)
Pilot Demonstration Working Group (DoD DHS
Co-Leads)
PEO C4I lead
Co-leads DoD NORAD-USNORTHCOM DHS US Coast
Guard
Co-leads DoD Office of Naval Intelligence DHS
US Coast Guard
17
Spiral 1 Pilot Purpose
Problem Users are unable to discover and
subscribe to Automatic Identification System
(AIS) information in a common format Purpose To
 publish vessel position reports from AIS
Aggregation Centers  to authorized subscribers
and graphically display that data on several
visualization tools.
18
Spiral 1 Pilot Scope

• Relevant Programs
• US Coast Guard Nationwide AIS (NAIS)
• Department of Transportation (Volpe) Maritime
  Security and Safety Information System
• Navy Navy Organic AIS
• Demonstrable service
• AIS Vessel Position Service
• Available via NIPRNET and Internet
• Targeted Exercises
• Coalition Warfare Interoperability Demonstration
  (CWID) 07
• Trident Warrior 07
• Participating Organizations
• US Coast Guard
• Navy
• NORAD-USNORTHCOM
• PEO-C4I
• Office of Naval Intelligence

19
Scope of the Data Management Working Group Task
to Support the Pilot
Developing and register a common vocabulary
supporting the MDA DS COI, beginning with the
schematic representation of Automatic
Identification System (AIS) data as it pertains
to the MDA Pilot objectives.
20
Spiral 1 COI Pilot POAM
17 Oct
Kickoff MDA COI 21-22 Feb 06
Pilot Selected Mar 06
Pilot Demo Oct 06
2nd MDA Meeting mid Jul 06
Pilot UDOP Selection Aug 06
1st Anniversary 22 Feb 07
OTE
Pilot 3-way NCES Discovery Aug 06
Pilot 3-way NCES Messaging Sep 06
Define Future Spirals
WGs Stood up Early Mar 06
Common Vocabulary Delivered May 06
21
Spiral 1 Discovery Architecture
Infrastructure
NCES SOA Foundation
COI
MDA DS COI Data Producers
Content Discovery
DHS Consumers
Navy Afloat
NAIS
DOD Consumers
Other
Volpe
NCES Federated Search
NCES Security Service
DOD
DHS
HSIN Portal
Defense Online Portal
HSIN Identity Store (Portal Authentication)
NCES Service Discovery
Data Sharing
SOA Foundation
22
Spiral 1 Messaging Architecture
Pilot Channels A NE USA B SE USA C MED
West D MED East E West USA F All G Other
MDA DS COI
USCG NAIS
Other
Navy Organic
Volpe
C
D
E
F
G
B
NCES Messaging Service
Messages Received (in COI Vocab)
Subscription Request
UDOP
23
Spiral 1 COI Resources
Potential Funding Sources USCG, USNORTHCOM, N6,
ONI, DOD CIO Program of Record costs to
implement and sustain services Pilot costs
Pilot Working Group 3 FTE Data Management
Working Group 2-3 FTE DISA costs NCES
Training and Support Other Stakeholders costs
associated with participating in working group
meetings
24
COI Spiral 1 Pilot Metrics

• Number of participating organizations
• Number of subscriptions
• Level of effort required for each program to
  interface with NCES
• Level of effort required to service-enable a new
  data provider
• Level of effort required to stand up a new
  consumer
• Operational impact of service outages
• Number of messages published per unit of time
• Level of effort required to train data producers
  and consumers on schemas and NCES
• Level of effort to develop and sustain schemas
• Size of schemas relative to cost and number of
  participants
• Number of programs extending schemas
• Level of effort required to register schemas
• Time required to search, discover, and filter
  published information