ISR Modeling Categories

In preparing a recent presentation for the IO-ISR Forum at the Simulation Interoperability Workshop, I listed a dozen simulations of Intelligence, Surveillance, and Reconnaissance; ordered them by time; and attempted to identify categories to characterize the evolution of ISR modeling over the last few decades. The categories that I arrived at are:

• Role Player. Initially intelligence was created through the actions of role players who injected information into the training event in the form of voice phone reports, textual reports, and map overlays.
  
• Sensor Models. The first step in modeling ISR was to create sensor models for the native combat objects in the game. These usually posted enemy ID, location, and status information to a global blackboard in the system that made it accessible to all units and players. Examples: JESS/CBS, ADSIMS/AWSIM, ENWGS/RESA.
  
• Intel Side-car Models. The next step was to create side-car ISR models that operated unique units in a model that was separate from the combat model. This allowed separation for classification issues, independent development of ISR sims, and adoption of existing sims that were used in the testing world. But it also created dual environments that were not always well synchronized. Examples: TACSIM, NWARS, JOISIM, JECEWSI, FIRESTORM, IEWTPT.
  
• Extensions. A few ISR simulations have been developed as extensions of the combat model. These use the same infrastructure, data, and models where possible; but add classified data and models as necessary. Examples: BICM, WIM.
  
• Integrated. I was not able to identify any ISR simulations that are truly integrated with their combat sim parent. In all cases, the ISR simulation is developed separately and evolves its own unique features that are not common with the combat simulations. Examples: None. Though I believe ENWGS had an integrated ISR model at one point, but it was removed.