imal input, and providing summarized output. Users must be able to "age" the simulation to accommodate a training scenario that describes actions in the midst of a campaign. The senior controller must be able to have the simulation start, stop/interrupt, rollback to any specified point in scenario, restart from a given point or the initial conditions and conduct concurrent replay. The seniorcontroller must have the capability to change any attributes of the simulated entities or the game characteristics at any time. (b) Conditions and Constraints. (i) Scenarios. The goal is for the simulation to portray events that could arise from scenarios based on any point in the operational continuum. At a minimum, requirements are for scenarios for war in Europe, Southwest Asia, Southeast Asia and Korea and for operations other than war in these locations as well as Central and South America and Africa. (ii) Fidelity. The simulation must allow commanders and battle staffs to do their tasks under the conditions and standards outlined in the Army Training and Evaluation Program Mission Training Plans (MTPs) for command groups and staff referenced in Appendix 1 to Annex A. (iii) Level of Detail. The simulation must be able to portray a level of detail that captures the effects of individual entities on the battle, e.g., single weapon platform, emitter, and sensor systems. Entities that operate near each other as cohesive units can be portrayed in aggregated units from team to battalion that represent the normal mode of employment. Individual, low-density, entities that operate in a geographically dispersed mode must be portrayed as they are employed, e.g., signal nodes, radars, jammers, missile and rocket systems, engineer obstacle systems, and individual surveillance and laser designation systems. All systems will be portrayed using performance data appropriate to the level of classificat...
