BRAWLER simulates air-to-air combat between multiple flights of aircraft in both the visual and beyond-visualrange (BVR) arenas. This simulation of flight-versus-flight air combat is considered to render realistic behaviors by Air Force pilots. BRAWLER incorporates value-driven and information-oriented principles in its structure to provide a Monte Carlo, event-driven simulation of air combat between multiple flights of aircraft with real-world stochastic features. The user decides the pilot’s decision process including:

• Missions and tactical doctrines

Brawler can be used in a confederation with another model EADSIM (Extended Air Defense Simulation). Integration of the next generation of the Confederation is intended to have EADSIM model the larger air defense engagement, with BRAWLER modeling air-to-air engagements in greater details as they occur. BRAWLER now has the capability of dynamic ghosting, the ability to receive vectoring commands from EADSIM controllers, enhanced transfer of control mechanisms, and modeling EADSIM digital terrain. While operating in the confederation mode, the two simulations rendezvous at regular intervals and exchange information about aircraft they are controlling. Engagement status, weapon firing, and kill/no kill messages are also sent from BRAWLER to EADSIM.

Input
BRAWLER inputs consist of system capabilities which include aircraft performance, weapons performance, and sensor systems performance. The simulated scenario consists of number an types of aircraft, their disposition and bases, and electronic countermeasure (ECM) effects included. BRAWLER accepts inputs for GCI’s (Ground Controlled Intercept), AWACS (Airborne Warning and Control System), Surface-to-Air Missile Simulations (SAMS), Surface-to-Surface Missiles (SSM) and stand-off jammers. Also the set of rules that the simulation pilots will use to make their flight decisions must be specified. BRAWLER’s current configuration is capable of handling a total of 20 different aircraft in as many as 10 independent flights with up to 8 aircraft per flight. To create an input file takes considerable time for realistic combat to be simulated.

Output
BRAWLER output consists of five files. The first is a log of the scenario that includes major events such as detections, weapons firings, and kills viewed at the terminal. The second file is a printed output file that reflects the input data read and provides more detailed information about the activities that took place. User-controlled switches are used to control the detail and kind of information and includes the capability to provide specific information during specified time windows. The third file is a disk history file which is processed by BRAWLER support programs to provide event summaries and graphics output. Another file provides BRAWLER with a checkpoint/restart capability which can be used to salvage catastrophic failures in order to fine tune a flight as well as to assist in debugging. The final file is used by the Measures of Performance (MOP) database system for statistical calculations in the analysis of multiple runs.