TRADOC Program Integration Office for Information Age Metrics Working Group The Multilateral Interoperability Programme “The Nature of Things” (Part 1) COL Stuart A. Whitehead Director TRADOC Program Integration Office for Battle Command

Agenda Background COL Whitehead MIP Program Mr. Ulrich JC3IEDM Mr. Simaitis Configuration Management Mr. Simaitis Leveraging MIP COL Whitehead Battle Command Vision Ms. Wortman

Sun Tzu: The Art of War No Army briefing would be complete without a famous “dead guy” quote. This one I am sure is familiar to you all, but it speaks to both the historic and current need for commanders to have situational awareness. As our recent experience shows and especially when it comes to coalition operations, knowing the location of ourselves, our allies and the enemy is essential to both force protection and operational effectiveness. Achieving this capability lies at the hart of coalition information sharing and the Multi-Lateral Interoperability Program. “If you know the enemy and know yourself, you need not fear the result of a hundred battles.”

The Commander Washington's first successes at Boston. Lithograph by Turgis.

General Meade and His Staff

The Modern Division Staff FM 6-0 AUG 2003

Army Battle Command System Overview GCCS - A GCCS-A (Global Command and Control System - Army) GCCS GCCS - - A A AMDPCS (Air and Missile Defense Planning and Control System AMDWS ASAS ASAS (All Source Analysis System) AMDPCS AMDWS AMDWS ASAS ASAS CSSCS CSSCS (Combat Service Support Control System) CSSCS CSSCS AFATDS AFATDS (Advanced Field Artillery Tactical Data System) AFATDS AFATDS DTSS DTSS (Digital Topographic Support System) MCS MCS DTSS DTSS IMETS This is an example of the Army Battle Command family of systems or ABCS. Like many of our legacy systems, each one was developed generally in isolation, or I should say within the community that the particular system serviced. Over time we realized that in order to execute Battle Command, these systems should share pertinent elements of information. This need prompted the development of the Maneuver Control System (MCS) a separate system for Command and Control which was intended to serve as the integrator of each of the systems shown. While MCS has been partially successful in achieving integration, it is endemic of the challenges faced by anyone who must integrate existing systems. Just by way of example let me offer a few insights to these challenges: MCS had to integrate with all the other systems. That meant accommodating 7+ different data models, exchange mechanisms and as many architectures. Each time that data was transmitted from one system to the other it required translation, which opened the way for induced errors. In short, we created about as complicated a system for command and control as possible. This is an example of how not to achieve system interoperability. TAIS IMETS IMETS TAIS TAIS TAIS (Tactical Airspace Integration System) IMETS (Integrated Meteorological System) MCS (Maneuver Control System) FBCB2 FBCB2 FBCB2 (Force XXI Battle Command BDE & Below)

Linearity in Theory Proportionality Additivity Y X Input Output

Non-Linearity “You think because you understand one you must understand two, because one and one makes two. But you must also understand and.” Ancient Sufi text.

The Human Dimension of “AND”

The Linear Battlefield XXX V US XX 1 US AR 2 GE IN X

The Non-Linear Battlefield 2 X 1 X 3 X

Expeditionary Capability Full Spectrum: JIM Environment XXX JTF XXX XX CORPS X DIV BCT X X BCT UA MEU Plug and Play Units with C4I This slide reflects the CSAs vision of the modular force. Asset Visibility Through Alerts and Deployments Simultaneous deployment from several bases Planning and Distributive Training Modular Organization

Laying the Foundation for Effective Future Systems Leader-centric network-enabled Battle Command Warfighter involvement from concept to employment New thinking – holistic context Governance/consensus in a JIM environment Interoperability

Operational View “Aggregation” X Corps View I I I I I I Division View I I I I I I I I I Brigade View “Look two down, order one down.”

Simultaneous Multi-Echelon Operations X PLAN PREPARE EXECUTE ASSESS PLAN PREPARE EXECUTE ASSESS I I PLAN PREPARE EXECUTE ASSESS I

Information Interoperability Organizations (Military) (Friendly, Enemy, Neutral, Unknown ) Unit Location Unit Holdings Unit Status Establishment Info (TOE) Action/Activity Action Task Action Event Plan/Orders Header Commander’s Intent Rules of Engagement Task Organization Messages: Alerts (e.g.,NBC msgs) Plans/Orders Control Features (all types) Control Feat Location Control Feat Status Geometry Point, Line, Area and Volume Meteorology Features Facilities (Bridge, Minefield, Obstacle, Airfield) Facility Location Facility Status Communications Network Materiel Equipment Consumables Personnel (type only) What’s Authorized Commander’s Assessment

INITIAL TYPEFILL TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE TYPE CBT CSS Leopard2 A 5 TYPE TYPE TYPE TYPE TYPE TYPE

ORGANISATION ESTABLISHMENT REPORT X 42 GE 421 423 O I L 422 424 OF-2 OR-5 OR-4 OR-1 425 011000Zmar01

PERSONEL MATERIEL HOLDING REPORT 422 011000Zmar01

ORDER OF BATTLE ORDER REPORT 011000Zmar01 X (-) attachment detachment directive to cooperate REPORT 234 attachment detachment directive to cooperate 421 422 423 424 5 4 231 (-) 3 011000Zmar01 X 42 425

ORGANISATION LOCATION REPORT STATUS X 42 24AHE7980056400 = 0 50 100 Status 011000Zmar01

ACTIVITY REPORT REPORT X ? 42 24UHU2350078400 011000Zmar01

CONTROL FEATURE REPORT SL FLOT 421 422 422 425 011000Zmar01

AD WEAPON CONTROL-FEATURE ORDER REPORT HOLD FIRE NOT KNOWN 234 WEAPONSFREE WEAPONSTIGHT 011000Zmar01

FACILITY REPORT REPORT 011000Zmar01 ASSEMBL AREA ASSEMBL AREA

MATERIEL LOCATION REPORT 011000Zmar01 STATUS Status X 42 24AHE7980056400 24AHE7650053400 0 50 100 Status 011000Zmar01

COMMUNICATION STATUS REPORT 011000Zmar01 Online 3 42 Offline 1 42 3 42 Offline 1 42 32UTN3240076500 32UTM2250045000 2 42 32UTN3040056500 011000Zmar01

METEOROLOGICAL REPORT 011000Zmar01

COMMANDERS ASSESSMENT REPORT ASSESSMENT /EXER/......../.........// /OPER/......../.........// /MESSID/....../.......// /CONTXT/....../.....// /CONTOIA/...../.....// /CONTASES/..../...// COMMANDER 011000Zmar01

OPERATIONAL ORDER HEADING TASKING RULES OF ENGAGEMENT X ? 42 140530Zapr01 24UHU2350078400 ROE 011000Zmar01

DOCUMENT REFERENCE ORDER DOCREF /EXER/......../.........// /OPER/......../.... ...// /MSGID/......../......// /RFFNC/......../......// 011000Zmar01

OPERATIONS ORDER ORDER ORDER /EXER/......../.......// /MSGID/......../.......// /ORDPLAN/...../....// /MSGREF/....../......// /UNITORG/....../....// COMMANDER 011000Zmar01

ACKNOWLEDGEMENT ORDER ACK /EXER/......../.........// /OPER/......../.........// /MSGID/....../........// /MSGREF/....../.....// /DTG/........./..........// /UNITORG/..../.....// OFFICER 011000Zmar01

Data Strategy Options Data Model Convergence Data Model Mapping Battle Command Simulations Geospatial Terrain …and others!

Information Exchange Standard Multi-National NATO JOINT C2IEDM JC3IEDM JBCIEDM Mission Capability Package Extensions

TRADOC Program Integration Office for Questions? COL Stuart A. Whitehead Director TRADOC Program Integration Office for Battle Command