Providing Common Munition Models Via an Ordnance Server,

In Distributed Interactive Simulation DIS exercises, it is often required that simulated entities interact on an equal basis. When different simulators use different models for the same munitions, combat between the simulated entities may be skewed in favor of one simulation over another. Thereby, the validity of exercise data might be lessened and the worth of the exercise reduced. Using common munitions models eliminates this problem. One approach toward providing these models is to use an establish procedure or object class library where an entitys simulator would also simulate the ordnance it fires. However, since this library must be compiled and bound to the platform simulation, this approach may lead to integration and performance issues. This paper describes an alternative an ordnance server. the ordnance server acts as a common repository that interfaces directly with the network Once a munitions is fired, the server assumes control and simulates it apart from its launching platform. Given available information, the server employs the appropriate weapon model. The server simulates weapon flyout, status,trajectory, impact and other munitions attributes. Since the server may be located apart from simulation platforms, processing load may be better distributed. Also, by operating within the DIS protocol, the ordnance server provides no additional network load. Furthermore, it can be distributed to different sites about the network. Lastly, by using ordnance servers near target sites, latency between a weapon detonation and its effect on a target can be substantially lessened.