|
Scope:
The Strike COI is an initiative to standardize data for the strike community. The COI will be responsible for identifying organizations that provide and use strike data and information, facilitating resolution of inconsistencies, coordinating data deconfliction within the DoD Registry, and providing implementation guidance to program offices as required.
Goals and Objectives: The goals and objectives of the COI are to assist/accomplish the following:
- Compile and address information sharing requirements for organizations, platforms and systems operating within the strike environment.
- Define/implement a repeatable work process that maximizes the COI's productivity, establishes accountability, accurately measures effectiveness and promotes community-wide data management and access.
- Synchronize COI products with the DoD Decision Support Systems (i.e., Defense Acquisition System; Planning Programming Budgeting & Execution; and Joint Capabilities Integration Development System).
- Develop a shared vocabulary in accordance with DoD Net-Centric Data Strategy.
- Influence appropriate information sources to adopt Net-Centric data sharing and Service Oriented Architecture.
It will do this by providing an inter-service coordination of community standards on how information will be exchanged within the COI. It will develop a data vocabulary or taxonomy and register the data standards in the DoD Metadata Registries.
Introduction:
The Strike Community of Interest (COI) Data Management Working Group (DMWG) was established in June 2006 to define a taxonomy and identify a schema that the Strike COI will use to enable all authorized users to discover, access, and collaborate on the data necessary to conduct time sensitive strike missions. The initial tasking of the DMWG was to develop a Strike COI Spiral 1 core vocabulary, data model and schemas with focus placed on defining and developing key data objects to support only the Spiral 1 requirements.
The Strike COI DMWG was established concurrently with the Strike COI Pilot and Strike COI Implementation Working Groups. Chairmanship of these three groups was divided between the services with the leadership of the Strike COI DMWG assigned to the Army, and designated COL Stuart Whitehead as the chairperson. As is the case with all these Working groups, representatives from all the services, Strategic Command (STRATCOM), Joint Forces Command (JFCOM), and Defense Information Systems Agency (DISA) were invited to participate in these DMWG efforts. The complete COI Strike Governance organization is shown in Figure 1.
The Strike COI Steering Committee defined the scope of Spiral 1 on 21 SEP to be the following:
"Publish a discoverable Strike User-Defined Operating Picture (UDOP) as a standards compliant portlet that displays the location, identification, and mission of blue forces within a designated vicinity of a planned Strike mission from current timeframe to 12 hours in the future."
The Strike COI Data Model is an evolving standard and this initial release only includes data elements pertinent to support of the Spiral 1 requirements set. The model selected in this process was developed with the intention to extend the initial baseline of Blue Force objects to later include enemy targets and other command and control data types and sources.
Three key models were built in the development of the Spiral 1 deliverables:
- A High Level Conceptual Model
- A Unified Modeling Language (UML) Class-relationship diagram
- A Strike Conceptual Implementation Model
A top-down approach was taken to develop the core vocabulary set and associated Extensible Markup Language (XML) data elements and XML Schema Definitions (XSDs) with the goal that this approach would support extensibility for subsequent Strike COI spirals. A handful of high-level objects were defined to help identify the relationship of blue objects and their assigned tasks and missions.
The vocabulary and data schemas provide a foundation that the Strike community can leverage for their development efforts. Users of these products must recognized they are an initial release that supports a limited scope but uses a flexible design that will allow future growth and the inclusion of additional data sources.
General:
Spiral 1:
Spiral 2:
|
