US Army CIO/G6 Battle Management Language (BML) Architecture Project ISSUE

Transcription

1 US Army CIO/G6 Battle Management Language (BML) Architecture Project Dr. Stanley H. Levine for the BML Conference 2/4/2009 ISSUE There are many Army, Joint, and Coalition BML efforts completed, ongoing, planned, or proposed. JBML, Training BML, FCS-BML, geobml, Integrated BML, NATO-MSG 048, CG JCTD, Coalition-BML, SIMCI Combined Project, Cyber BML, etc. However, there is no integrating overarching program to ensure that the Army receives maximum benefits from all of the ongoing and planned BML efforts. The US Army CIO/G6 funded a G3 sponsored FY09 BML Architecture effort to integrate and document a synchronized standard structure and set of products for BML developments. 2 1

2 Purpose of a BML Architecture To provide an engineered structure for technical and program analyses that will result in maximizing the benefits to the Army since there is no single overarching BML program for development and the ongoing diverse activities are becoming divergent. Army benefits will be: Significantly improved Army, Joint, Coalition interoperability among C2 Systems and between C2 and M&S systems Improved accuracy and reduced processing time during BC field operations Reduced time and cost to accomplish training Improved mission initialization 3 Use of the Architecture The architecture would be used by HQDA, users, developers, and managers to ensure: that derived requirements were best prioritized that developments were compatible that technologies were well integrated that compliance with the ANCDS was achieved That this cross-functional, cross-ma, crossdomain area was an integral part of the Army Enterprise Architecture that that the decisions on programs were aligned and in the best interest of the Army 4 2

3 Method Derived requirements, data exchanges, and capability structure information will be gathered from ongoing programs. The information will be analyzed and processed into one cohesive architecture including integrated views of data, capabilities, and system structures. Analyses will be performed to determine overlaps, gaps, disconnects. Results will be provided to program managers and HQDA so that they can improve implementations and usage within the Army. 5 Endstate/Deliverables Enterprise level information architecture unifying derived requirements for BML Technical Data specification of JC3IEDM based common data needed to unambiguously represent Geospatial Products, Orders, Plans, and Reports. Results of the architecture based analyses for BML employment Demonstration of operationally significant use of BML based on implementation of the architecture and the analyses results 6 3

4 BML Architecture - Efforts BML Reference Architecture Specification Technical Standards View (TV-1) Specification of Core BML JC3IEDM extensions, Operational View (OV-7) (Logical Data model) Systems and Services View (SV-11)(Physical Schema) OV-1, SV-1, OV-4, OV-6c / SV-10c under consideration IBML Control Board Participation Stakeholder BML Meeting Support 2009 G3 Army BML Conference Support Coordination plan for using results of on-going BML efforts NATO MSG-048 Demonstration Support Report JC3IEDM mappings to BML Schema BML Web Service Specification Specification of Engineered Knowledge for Stryker Brigade Reference script for the Scripted WS 7 IBML Projects Relationship geobml MSG-048 Knowledge Engineering JBML Geospatial Objects Grammar Joint and Coalition Aspects Contributions MSG-048+ Coalition Experimentation and Grammar feedback IBML Integrated Architecture Common Products Coordinated Participation geobml/cg JCTD Geospatial Objects Knowledge Engineering Other Efforts SIMCI JC3IEDM Transition M&S + BC Integration Script interpreter DB mapper SIMCI+ Transition BML into BC and M&S systems 8 4

5 Summary BML has been proven as a technology with the potential to provide cost savings and improve both training and operations. There are many Army, Joint, and Coalition efforts ongoing that cross Mission Areas and Domains. The BML Integrating Architecture effort should provide a basis for effectively and efficiently coordinating BML efforts/ products. 9 5