The M

1
The MS COI Focus Groups

• Frank Carr, MITRE Corporation
• MS Community of Interest (COI)
• Technical Advisor
• carr_at_mitre.org
• 6 April 2005

2
What are Communities of Interest?
The Object Management Group is an open
membership, not-for-profit consortium that
produces and maintains computer industry
specifications for interoperable enterprise
applications.
The Open Group is an international vendor and
technology neutral consortium that is committed
to delivering greater business efficiency by
bringing together buyers and suppliers of
information technology to lower the time, cost,
and risk associated with integrating new
technology across the enterprise.
The Dublin Core Metadata Initiative is an open
forum engaged in the development of interoperable
online metadata standards that support a broad
range of purposes and business models.
The Web Standards Project fights for standards
that reduce the cost and complexity of
development while increasing the accessibility
and long term viability of any site published on
the web.
Collaborative groups of users who must exchange
information in pursuit of their shared goals,
interests, missions, or business processes and
who therefore must have a shared vocabulary for
the information they exchange.
3
What are GIG COIs supposed to do?

• Address the organization and maintenance of data
• data implies all data assets such as system
  files, databases, documents, official electronic
  records, images, audio files, web sites, and data
  access services.
• Develop metadata to describe data assets and the
  use of registries, catalogs, and shared spaces,
  which are mechanisms to store data and
  information about data.
• Identify and provide GIG Enterprise Services that
  enable data tagging, sharing, searching, and
  retrieving

4
GIG Communities of Interest

• METOC (Meteorology Oceanography)
• Joint Electronic Warfare Data Standardization
• Joint Targeting Intelligence
• MASINT Community of Interest
• Space COI
• Undersea Warfare XML

• Force Projection
• Information Operations
• Time Sensitive Targeting
• Health/MHS
• Computer Network Defense
• Distribution
• Global Force Management

5
GIG MS COI

• Organized around MS Technology
• Spectrum of Domain
• Training
• Systems Test and Evaluation
• Analysis
• Decision Support
• Others??
• Depth of experience in working collaboratively
• Professional Groups (e.g. SISO, SCS)
• Federation Building
• Others ???

6
An Exemplar

• Mission and Scope
• Developing Metadata Stds
• Define frameworks for interoperability of
  metadata sets
• Facilitate dev of community or discipline
  specific metadata sets
• Activities
• Standards Dev and Maintenance
• Working groups and workshops
• Dev Tools, Services, and Infrastructure
• Educational outreach
• Other Community Liaison
• Mailing Lists

For more information www.dublincore.org
7
Other COIs Example Working Groups

• 20 Active, 18 Deactivated.
• Chartered for special interests, fixed tasks,
  analysis of alternatives
• Administrative Metadata WG
• Datamodel WG
• Registry WG
• Standards WG
• Format WG
• Schema WG
• Registry WG
• Tools WG
• Business Special Interest Group
• Moving Pictures SIG

• 9 Forums
• Architecture
• Strategy Standardization
• Messaging
• Secure Messaging
• Identity Management
• Directory Interoperability
• Directory Certification
• Mobile Directory Challenge
• Quality of Service
• Enterprise QoS Service Level Agreements
• Real-Time QoS
• Application Manageability QoS

8
Other COIs Example Projects

• 70 Projects listed including
• AHDS Arts Humanities Data Service
• Build an integrated system capable of providing
  electronic resources on archaeology, history,
  textual studies
• Australian Geodynamics Cooperative Research
  Centre
• Providing delivery system for research results.
• CEN/ISS Dublin Core Workshop
• Encourage cross-industry acceptance of Dublin
  Core Metadata Element Set
• WWW full-text and bibliographic resources for
  libraries
• Provide verified information sources primarily
  for specialists in librarianship, information
  sciences, humanities, social sciences
• Univ Arizona Resources for SiteSearch
  Implementation
• Provide a variety of Internet accessible
  databasses that include images, video, sound, and
  documents

• 17 Projects Including
• Secure Mobile Architecture
• Extending current activities from reqts spec to
  architecture model for secure mobility
• Access Control
• Identify potential work items that members would
  be interested in taking up as work projects
• Mobile Directory Challenge
• A direct consequence of the business scenario
  The executive on the move which is intended to
  explore technology potential and business
  benefits
• Data Center Resource Mapping to Applications
• Goal Identify within the Data Center a
  top-down approach to mapping sub-elements to
  operational critical applications. Define a QoS
  architecture NOT technology specific

9
Initial Focus Group Definitions

• Data Mediation
• Focus group to examine issues of Data Mediation
  for MS on the GIG. Will assess use of existing
  standards (e.g. C2IEDM), deficiencies of each,
  and their potential for cross-COI coordination.
  This includes an assessment phase, a
  specification phase and may include a pilot
  phase.
• Maillist https//lists.dmso.mil/mailman/listinfo/
  coi-fg-mediation
• Metadata
• Focus group to develop a standard use case for
  MS Metadata in the GIG a business case for MS
  Metadata assessment of current programs using
  extensions to DoD Discovery Metadata
  Specification (DDMS) and exploration of the need
  to provide MS COI specific fields to the DDMS.
• Maillist https//lists.dmso.mil/mailman/listinfo/
  coi-fg-metadata

10
How will future Focus Groups occur?

• Solicit Community for Ideas/Proposals
• Identify relevant/interested contributors
  stakeholders
• Present to MSWG (COI Exec) for approval
• Evaluation against COI charter, vision, goals
• Facilitate start-up, on-going activities

11
Focus Group Data Mediation

• NCES Definition
• Mediation Services translate, aggregate,
  integrate, correlate, fuse, broker, publish, or
  perform other transforming processes to
  data/metadata.
• Examples of Questions
• How might/will Data Mediation apply to MS based
  applications on the GIG?
• How might/will it be implemented?
• Are existing standards (e.g. C2IEDM) sufficient?
• What additional standards are required?
• Example Goal/Objective
• Build a community understanding, consensus,
  proposed approach to Data Mediation

For example ONLY TBD
12
Focus Group Metadata

• DoD Discovery Metadata Specification (DDMS)
• The DDMS defines a core set of elements that must
  be used to describe data assets made visible to
  the Enterprise
• Examples of questions
• What data assets will MS Services
  publish/subscribe to?
• What metadata elements are suggested or required
  to support access?
• How will metadata be generated?
• Example Goals/Objectives
• Develop consensus based use cases for example MS
  services
• Define proposed metadata spec (by category/use?)
  for MS data assets
• Facilitate required changes to metadata for
  non-MS data assets to support MS use

For example ONLY TBD
13
Near-Term Activity Plan

• Focus Groups (2) Formation Announcement
• 22 Mar 05 at MSWG/COI Meeting
• Email soliciting MSWG participants registration
• Sent out by 25 Mar 05
• Discussion sessions at SISO SIW
• Coordinating Telecon(s)
• Week of April 11
• COI Focus Groups Definition Meeting
• 19 Apr 05, 0800 1200
• Location DMSO Offices

YOU ARE HERE
14
MS Services Focus Group

• Description
• Planning support services, training support
  services. To try to find what the shared concerns
  and vocabulary of the COI. How would I organize
  MS services on the GIG?
• Questions
• 1) what are the broad categories of MS services
  needed on the gig?
• 1.5) How MS services fit into the GIG?
• 2) What services do we need from the GIG?
• Deliverables
• MS Strategy for GIG Implementation (KM Outline)
• Reccmndtns of impacts to other documents
• HPT/LHF and others to work on

15
Focus Group Definition Mtg

• 19 April 2005
• DMSO Offices, Alexandria, VA
• 0800-1200 Eastern
• Working Agenda
• 1 hr Introduction Overview
• 2 hr Break-out Sessions
• Focus Groups meet separately
• 1 hr Out-Brief Preparation
• Definition Meeting Deliverables
• Mini-Terms of Reference (1 page)
• Description
• Participants
• Group End-state Deliverables
• Group Delivery Schedule
• COI Concurrence Out-Brief (2 slides max)
• COI Concurrence Out-Brief at afternoon COI session

16
Help by getting these people involved

• Operational Users
• Service MS Offices
• DoD Material Developers
• Research Dev Organizations
• Professional Standards Organizations
• Commercial Product Developers
• GIG Architecture Infrastructure Developers

17

• Discussion

18
Example Group Standards Metadata

• Objectives
• Administer MS Namespace Configuration Control
  Board
• Establish Liaison Relationship with Standards
  Metadata Groups
• Dublin Core Metadata Initiative, Simulation
  Interoperability Standards Organization, IEEE
• Report on Liaison Group activities, topics of
  interest to MS
• Initial Deliverables
• Process Group detailed ConOps, governance
  document
• MS Namespace Configuration Management and
  Version Control process
• Duration/Scope
• Indefinite
• Participants
• Responsible to MS Namespace Mgr, COI Board
• Agency membership nominated for fixed term
• Approved by COI Board

19
Example Group MS Use Cases

• Objectives
• Explore emerging GIG/NCES Architecture and
  Implementation(s) and the impact on
  Non-Operational MS Applications (e.g. Training,
  Exercise, Acquisition, Operational Service Test
  Evaluation)
• Define Conceptual (Reference) Use Cases, proposed
  community based Architecture, requirements,
  implementation approach, projected cost,
  schedule, implementation strategy
• Report out to COI membership groups with relevant
  interest
• Initial Deliverables
• Proposed MS Use Case(s)
• Use Case and related
• documentation standards
• Analytical approach/plan
• Duration/Scope
• 6-9 Months
• Participants
• Responsible to Technical Advisor,
• COI Board
• Member Groups nominate or
• appoint representative

20
MS COI Organization Possibility?
All Service Joint DHS Inteligence
Tech Advisors Admin
Staff
COI Manager
Manage
Charters
Process
Process
Process
Populate
Populate
Namespace Manager
Config Version Control Board
Project
Special Interest Group
Project
Special Interest Group
Requests
Project
Special Interest Group

• Sample Projects
• Prototype Services
• Analysis of Standards
• Intra-Community Tools

21
MS on the GIG

• To be operationally relevant, MS must live in
  the same information environment as operational
  applications and data.
• The information environment for military
  operations, the GIG, is being evolved through
  development of Communities of Interest (COI)
• A significantly different interoperability
  paradigm
• Web-ifying todays practices we lose the GIG
  advantage
• Establishment of coherent, integrated MS
  capabilities on the GIG requires establishment of
  an MS COI
• Content development and management is being done
  by communities

22
Building a Vocabulary

• Criteria
• Capable of conveying semantic understanding of
  critical terms in MS
• Data (resolution, certification)
• MS Capability and suitability
• Critical assumptions
• Consistency with associated operational
  vocabularies
• Enable rapid exchange of MS and operational data
• Ability to access MS as an operational
  capability
• Example operational vocabularies
• JMBL, C2IEDM (others to be explored)
• SISO and NATO(NMSG) to convene a BML working
  group to explore candidate vocabularies and
  extensions needed to enable MS and operational
  systems to exchange data seamlessly

23
Existing COI?

• Are there any existing COIs?
• What can we learn from them?
• Process lessons
• Product lessons
• Which Existing COIs are relevant to MS?
• C2 COI example Multilateral Interoperability
  Programme (MIP)
• JMBL
• Others . . .

24
MIP Terms of Reference

• Multilateral Interoperability Programme
  www.mip-site.org
• Aim Achieve international interoperability of
  Command and Control Information Systems (C2IS) at
  all levels
• corps to battalion, or lowest appropriate level
• support multinational, combined and joint
  operations
• advance digitization in the international arena
  including NATO
• Scope
• War Ops, Crisis Response Ops, Defence Against
  Terrorism
• Joint, Interagency, Multinational,
  Non-governmental Organizations
• Tactical to Operational and Strategic levels
• An international venue for consensus and
  standards development and coordination
• Not cooperative development program

Bottom Line MIP is a functioning successful C2
Community of Interest
25
MIP Members / C2IS Systems

• FULL MEMBERS
• CA LFC2IS
• DA DACCIS
• FR SICF, SIR
• GE HEROS-2/1
• IT SIACCON
• NL ISIS
• NO NORTaC/NORCCIS
• SP SIMACET
• UK ATacCS/ComBAT
• US MCS (L)
• TU TKKBS

ASSOCIATE MEMBERS AS JCCS, BCSS AU PHOENIX BE SICB
EL CZ GF-TCCS FI TBD GR HARCCIS HU HAVIR LH TBD P
L SZAFRAN PO SICCE
RO TBD SI TBD SW IS MARK SLB AFNORTH ACT BiSC
AIS
TBD To be determined
26
MIPWorking Groups
MIP Steering Group (MSG)
Programme Management Group (PMG)
Operational Working Group (OWG)
Systems Engineering Architecture Working
Group (SEAWG)
Configuration Control Working Group (CCWG)
27
C2 Core C2IEDM

• GH ? LC2IEDM ? C2IEDM ? JC3IEDM
• Operational exchange standards use a common
  vocabulary consisting of 176 information
  categories that include over 1500 content
  elements.
• Core C2 Information and Metadata Exchange Data
  Model
• Serves as a hub on which to build
  mission/functional unique extensions
• XML Namespace XSD autogenerated
• 1000 pages of great documentation

28
www.mip-site.org
29
Questions?
30
How can GIG MS COI accomplish this?

• Through Processes
• Govern COI Processes With Sustained Leadership
• Establishment sustainment of Focus Groups
• Nomination Approval of Standards
  Specifications
• Config Mgmnt Version Control of Metadata
  Registry
• User Feedback Response
• Through Collaboration (using Focus Groups)
• Develop Metadata for Data Structure and
  Definition
• Develop and/or Associate Security, Content,
  Format, other COI specific Related Metadata
• Register Metadata
• Associate Data Pedigree and Security
• Define COI-Specific Ontologies
• Ensure Compliance with GIG/NCES relevant
  Standards
• Through Projects
• Identify and provide GIG Enterprise Services
• MS Technology Use Cases in a GIG Architecture

31
MS COI Focus Groups

• Objective
• Administer MS COI based activities
• Define/Refine a specific need of the MS COI
• Respond to requests of others
• Facilitate bringing together best brightest
  of Community members
• General Requirements
• Focused, well defined efforts
• Measurable, Deliverable efforts
• Responsible to, Appointment by COI Board
• Oversite by Technical Advisors
• Scope of efforts
• COI Process based
• Chartered to Define/Administer COI Processes
• On-Going, with fixed term participation
• COI Project based
• Fixed term, focused area
• Non-renewable