Implementing Battle Management Language: A Case Study Using the Command and Control Information Exch - PowerPoint PPT Presentation

1 / 21
About This Presentation
Title:

Implementing Battle Management Language: A Case Study Using the Command and Control Information Exch

Description:

Defends. 1 ID (M) To secure. The key passes. 302130JAN98. Seizes. 1 ID (M) To defeat ... On order, defends in sector from PL ELM to PL MAHOGANY to complete the ... – PowerPoint PPT presentation

Number of Views:56
Avg rating:3.0/5.0
Slides: 22
Provided by: vdo5
Category:

less

Transcript and Presenter's Notes

Title: Implementing Battle Management Language: A Case Study Using the Command and Control Information Exch


1
Implementing Battle Management Language A Case
StudyUsing the Command and Control Information
Exchange Data Model and C4I-MS Reference Object
Model05S-SIW-068
  • Liam DeMasi
  • Verlynda S. Dobbs, Ph. D.
  • Adam Ritchie
  • William P. Sudnikovich
  • Atlantic Consulting Services, Inc.
  • 167 Avenue at the Common
  • Shrewsbury, NJ 07702
  • (732) 460-9416
  • ldemasi_at_acsinc-nj.com, vdobbs_at_acsinc-nj.com,
  • aritchie_at_acsinc-nj.com, wsudnikovich_at_acsinc-nj.com

2
Focus of Paper
  • Battle Management Language (BML)
  • SIMCI, DMSO and JNTC-sponsored initiative
  • Proof of Principle demonstrated in early 2003
  • Legacy-based database
  • Application of two standards-based
    interoperability models to continued BML test bed
    development
  • C2IEDM Command and Control Information Exchange
    Data Model
  • C-ROM C4I-MS Reference Object Model

3
Model Descriptions
  • C2IEDM
  • Maintenance and CM by Multilateral
    Interoperability Program (MIP)
  • 2 decades of multi-national development
  • Well documented and publicly available
  • www.mip-site.org
  • C-ROM
  • Aligned with C2IEDM from inception
  • Uses standard approaches (UML)
  • SIMCI sponsored
  • S03-SIW-073, F03-SIW-030, S04-SIW-076

4
Application of Two Interoperability Models
  • Demonstrated at I/ITSEC, December 2004
  • Data Representation
  • Used International, Joint standards
  • C2IEDM IDEF1X
  • Application Development
  • Develop Web services
  • Standards based - OO
  • C-ROM - UML

5
BML to C2IEDM/C-ROM Three Level Mapping
  • Conceptual level
  • Describe BML concepts as 5Ws
  • Compose OPORD from 5Ws
  • Identify C2IEDM/CROM concepts for 5Ws
  • Logical
  • Identify C2IEDM/C-ROM entities for 5Ws
  • Physical
  • Map enumerated data elements

6
BML Concepts As 5Ws
  • Who Unit to accomplish task
  • What Task to be accomplished
  • When Timing of task
  • Where Location for accomplishing task
  • Why Reason for accomplishing task

7
OPORD 1 ID (M) Mission Paragraph As 5Ws
1 ID (M) attacks 302130JAN98 in zone to secure PL
SPRUCE and seizes OBJs HOOK and JAB to defeat
lead elements of 10 MRD and 11 MRD, and secure
the key passes between the GRANITE/TIEFORT and
TIEFORT/FURLONG mountains. On order, defends in
sector from PL ELM to PL MAHOGANY to complete the
destruction of the 10 MRD and 11 MRD.
8
5WsC2IEDM Concepts
9
Logical Level Mapping
  • BML to C2IEDM
  • Tables
  • Columns of tables
  • Relationships
  • BML to C-ROM
  • Classes
  • Attributes
  • Relationships
  • C-ROM classes/attributes/relationships
  • align with
  • C2IEDM table rows/columns/relationships

10
BML ActivityC2IEDM and C-ROM
WHAT
CONTEXT
WHAT
CONTEXT
WHO
WHERE
WHY
WHO
WHERE
WHY
11
WHOC2IEDM and C-ROM
12
WHATC2IEDM and C-ROM
13
WHENC2IEDM and C-ROM
14
WHEREC2IEDM and C-ROM
15
WHYC2IEDM and C-ROM
16
Physical Mapping Step
  • Examine Enumeration Codes
  • Map Element mapped to appropriate enumeration
    element of C2IEDM
  • Add Element added to existing enumerated data
    set
  • New Element included in a new enumerated data
    set

17
Priority of Additions
  • Add enumerated values to existing C2IEDM
    enumeration data sets
  • Add enumeration data sets
  • Add attributes to existing logical tables
  • Add logical tables and attributes

18
Logical and PhysicalAdditions
19
Lessons Learned C2IEDM for BML data
representation
  • BML is Instantiated in C2IEDM
  • Added two relationship tables of static
    information
  • who-what and what-why tables
  • Key in representing the context which removes
    ambiguity
  • Added two additional tables
  • Subclasses of REFERENCE
  • DOCUMENT and MAP
  • Overload Action Entity top level of OPORD, each
    paragraph, each subsection, all activities

20
Future Work
  • BML
  • Complete OPORD paragraphs
  • Extend to additional Services
  • C2IEDM
  • Examine extensions required for BML
  • Identify extensions to be submitted for inclusion
  • C-ROM
  • Increase degree of alignment with C2IEDM

21
CROM Baseline Version 2.1
  • Remaining C2IEDM entities (tables attributes
    codes) added
  • C-ROM naming closely aligned with C2IEDM
  • Functional area specific information removed
  • C-ROM to C2IEDM mapping created
  • All products of baseline posted on SIMCI Website
  • http//simci.army.mil
  • (Library -gt Projects -gt C-ROM Baseline Version
    2.1)
Write a Comment
User Comments (0)
About PowerShow.com