The Balanced M&S/C2 Technical Evolution of Joint Fires Support

1. The Balanced M&S/C2 Technical Evolution of Joint Fires Support Nacer Abdellaoui NMSG-087 Symposium Enhance or Replace: Finding the Right Live vs. Synthetic Balance October 13, 2011 Bern, Switzerland

2. Outline • Introduction • Joint Fires Support (JFS) Vision • JFS Components • M&S • C2 • Human Element • JFS Experiments • Capability Development (IJFiC series) • Human Factor Experiments (HF series) • Project Achievements • Joint Battle Lab Exploitation • Conclusion & Recommendations

3. Introduction • There is still a tendency in each separate unit . . . to be a one handed puncher. By that I mean that the rifleman wants to shoot, the tanker to charge, the artilleryman to fire. . . . That is not the way to win battles. If the band played a piece first with the piccolo, then with the brass horn, then with the clarinet, and then with the trumpet, there would be a hell of a lot of noise but no music. To get the harmony in music, each instrument must support the others. To get harmony in battle, each weapon must support the other. Team play wins. You musicians of Mars must not wait for the band leader to signal you. . . . You must each of your own volition see to it that you come into this concert at the proper place and at the proper time.* Gen George S. Patton Jr., 8 July 1941 * Joint Fires Concept of Operations document, April 2006

4. Three Block War Non-Combatant Evacuation STF/SOG Amphibious Operations What does the CF need? A capability to support coordinated joint effects for … `

5. Joint Fires Support Vision • Assemble a net enabled decision support system that allows a Joint Fires Coordination Center to integrate time sensitive target requests and immediate calls for fire into an ongoing fires plan. This system of systems would: • Leverage available situational awareness; • Display weapons and unit status and capability; • Interpret commander’s intent; • Follow the rules of engagement; and • Determine if a call for fire can be acted upon.

6. JFS Components • Command & Control (C2) • C2 is fundamentally the task of a military commander • Today's C2 systems/tools built in a stovepipe constraint/approach • Tools/Systems must survive interoperability in a joint environment and vertiginous pace • Modeling & Simulation • Key Goals: • Test the entire JFS ‘system’ along with the JFCC command structure in a synthetic environment • Validate the entire JFS C2 system including its command structure in a realistic warfare exercise • M&S must provide: • Simulation of forces (Red, Blue, Others) • Realistic communication for C2 between players and controllers • Simulation of warfare equipment (weapons, platforms, damage, communications, sensors, EW, etc.) • Human element is behind the decisions/interpretations • commander’s intent, • digesting various sources’ inputs, • creating a situational awareness (SA), and • passing this SA to the subordinates for execution. Disruptive innovations, various exigencies, and high operational tempo → Another look at C2 functionalities (update understanding of C2 purposes, circumstances, approaches, processes, and procedures)

7. JFS Experiments • Experimentations went through phases: • Capability Development Development of operational architectures used for preparation of a CONOPS. As-is architecture served as an important reference for developing the mid-term capability. To-be looked at future systems. Validate the ability of the test-bed to stimulate the JFS coordination process • Integrated Joint Fires Coordination series (I, II, III) • Human Factor Integration HF experiments run to simulate the operations of a C2 HQ determining the technology requirements for a future battle command centre. HF experiments tried to shed more light on the human element and scientifically analyze its relevance • Human Factor series (One, Two, Three, …)

8. Integrated Joint Fires Coordination Experimentation One (IJFiC I) • Validate the test-bed infrastructure in preparation for follow-on collaborative experimentation to explore evolving tools and techniques for JFS. • Assess JADOCS as a potential solution to integrate the information required for Joint Fires Coordination. • Ensure that track information generated by the three environmental command and control systems can effectively populate COP which was displayed using JADOCS. • Introduced MUSIC Service Framework

9. Integrated Joint Fires Coordination Experimentation Two (IJFiC II) • Used a technical scenario outlining the exact requirements in terms of entities and interactions. • Improvements to the CGFs to allow: • Track filtering to TBMCS and GCCS-M (JSAF); • Adequate and valid data through OTHGMD gateway (LCSS); • Investigated the usage of one CGF (JCATS) for pushing air and maritime tracks to GCCS; and • Representing Blue Force SAS feed (2015 timeframe) on JCATS. • Used the MUSIC Test Bed (MTB) to correlate the Joint COP from all three environmental C2 systems • In depth JADOCS assessment • Overlay information (LCSS-JADOCS) • Mil Std 2525 symbology

10. Integrated Joint Fires Coordination Experimentation Three (IJFiC III) • Build on the lessons learned from previous experiments to validate the test-bed infrastructure against future collaborative experimentation • Focus on trouble shooting, tracking information flow, and the ability to populate a JCOP • Trouble shooting the MUSIC Service Framework • Provide an effective environment to allow JFC to occur effectively in a simulated headquarters.

11. Human Factor One (HF1) • Sponsored by the Chief of Force Development (CFD) • Contributed to evolving Canadian C4I and associated Joint Warfare tactics • Baselined the entire architecture within CFWC, providing a solid foundation to move forward with Joint Fires experimentation and adding more complex pieces to the baseline in Joint Warfare

12. HF1 Experiment • Mission Statement • Successful use of in service systems to incorporate issued plans and execute operations (simple and complex joint fire support requirements) • Using JFS Prototype (based on JADOCS) to plan and execute an operation involving both simple and complex joint fire support requirements with a Joint COP • Verification of Track completeness/user confidence • Passing: fire orders/requests, target data, and targeting info • Fires Support Coordination/De-confliction with multiple inputs • Hypothesis • Using JFS prototype, Operators will make effective fire support decisions, faster and have better SA with near real time updates of joint blue positional data and understood joint OpFor picture than when using the in service environmental C2 Systems • Outcomes • Effectiveness of fire support decision making, timeliness, better SA, usability measures, utility ratings, measure passage of fire orders/requests, target data, targeting info • Helped identifying/correcting deficiencies with the JADOCS application that will benefit the Joint and Coalition warfighter • MUSIC application has been removed from the architecture

13. Human Factor Two (HF2) • Sponsored by the Chief of Force Development (CFD) • Review and validate JFS decision making processes: • Targets Assessment/Prioritization, Synchronization of Effects, Effectors to Target (Weapon-Targets Pairing), Time Sensitive Targeting • Identify potential gaps • Assess existing decision aids and C2 applications (from HF perspective) • Validate decision aids requirements to improve C2 applications

14. HF2 Experiment • Mission Statement • The successful integration of as many tools as possible. These include: • C2 related: LCSS, TBMCS, GCCS-M, ADSI, MIDB, CSD, … • Simulation: JSAF, JCATS, and VBS 2 • Operator tools: JADOC, JTT, CSD client, TAIS, SimSpeak, … • Delivery of a successful JFS TDP and potential Joint Battle Lab to CF/DND senior leadership. • Hypothesis • HF2 aimed at establishing a set of baseline data that assesses the agility and effectiveness of JFS operators in decision-making related tasks (e.g., coordination, de-confliction, targeting, weapon-target pairing) • Outcomes Better understanding of: • Target folder preparation • Collateral damage escalation process • Judge Advocate General officer (JAG) interaction and requirements • All-Source Intelligence Cell (ASIC) interaction and requirements • Special Operation Forces (SOF) interaction and requirements

15. Human Factor 3 (HF3)/Coalition Attack Guidance Experiment (CAGE) • Experiment sponsored by TTCP Aerospace Systems Group (AER) Technical Panel 1 (TP1) • Large Canadian operational stakeholder community • Focused on Afghanistan • Secret x 4 eyes • Actively supported by: • US Army Battle Command, • US Joint Force Command (JFCOM)

16. HF3/CAGE experiment • Mission Statement • Analyze Battlespace Management and integration technologies and processes to increase SA throughout the chain of command → freedom of maneuver & effectiveness of Fires (i.e. shorten the targeting cycle, and reduce the potential for fratricide, collateral damage and civilian casualties) in a JIIM/JIMP operational context. • Integrate selected US Army Battle Command systems including the TAIS/DACT, AFATDS and CPoF, and the NATO ICC system to analyse the evolving coalition C2 configuration intended for ISAF. • Hypothesis • SA from integration of many digital interfaces and C3I platforms provides enhanced decision/action cycle in a congested battlespace • Outcomes • Assessment of TAIS/DACT Concept of Employment (COE) and TTPs • Assessment of evolving ISAF collapsed Centrix/ISAF network for coalition C2 and the potential impact on operations, personnel, training • Support to JFS ESC in identifying coalition joint fire issues (focused on the integration of ISR and UAVs into Fires) • Improved understanding of JFS battlespace management in a coalition environment • Advancement of the JFS test-bed to emulate coalition operations

17. Employment Perspective of JFS test-bed From “JFS HF-2 VIP Day Presentation” Dec 2009

18. Project’s Achievements • Erection of the Joint Battle Lab (JBL) • BGen Matte was behind the transition of the JFS test-bed into the JBL • Seen as the centrepiece and a pillar of the new warfare center • CFD will invest ~$10M in JBL transition • VCDS directs new JHQ(R) to leverage the JBL • JBL is the cornerstone for developing the new JHQ(R) • Long term underpinning of the JHQ(R) capability supporting technology injection, pre-deployment preparation, training, and as back-up capability • Future experiments will support JHQ(R)

19. JBL Exploitation • CEFCOM Planning to field JADOCS as a technical solution. • Requested JFS support in transition of technology • Taking active roles in coming experiments • Joint Information and Intelligence Fusion Capability Detachment launched a supporting options analysis for the JIIFC IOC using JBL • LCSS interested in leveraging JBL to facilitate the design of the future versions for the army • DPDOIS (Air) saw in JBL a means to test systems in ways they do not have at their disposal

20. Conclusion & Recommendations • JFS is a threefold (process, people, and equipment) complex project • Incremental process for edifying the test-bed • Valid test-bed (right systems, tools, processes) • Because of the adopted architecture, the test-bed could be tailored and adapted in various flexible manners • Incrementally complex experiments • More challenging scenarios • More systems • More consideration for HF element • Spiral Approach helps focus on tasks and progress towards JFS requirements • JBL & ITB Spinoff • M&S can be used to support the Operational Planning Process or the Military Decision Making Process (MDMP) in real-time

21. Questions “Any intelligent fool can make things bigger, more complex ... It takes a touch of genius and a lot of courage to move in the opposite direction.”