Four Approaches to Simulation as an IT Service

Previously I have described an idea to deliver simulations as an IT service in the same way that people are able to use the Web, email, and other online services. Further investigation and discussions with companies pursuing similar projects suggest that there are four methods of achieving this. Each has their own advantages and drawbacks.

• Basic HTML. If a simulation can be delivered as basic HTML, then the infrastructure and desktop software is already in place to deliver this. Currently, Google Maps is an example of how far this can be taken with user interactivity.
• Plug-in. We could develop a browser plug-in so that the main interface to simulation tools and content is still through the browser, but it would allow us to create more advanced content. The most popular plug-in of this type is Flash. Garage Games has developed a plug-in that uses DirectX and the power of the graphics card on the machine. This service is currently in Beta test at InstantAction.com.
• Simulation Framework or Driver. A framework driver is a program that is approved to reside on a standard Army desktop and contains generalized rendering, AI, a GUI, and other tools that can be installed to support specific simulation content modules. The specific content (flight ops, team tactics, etc.) would be downloaded by the driver according to the needs of the soldier that was using a specific machine. The content modules would not be installed as unique programs but would be libraries to an already installed and approved driver.
• Full Simulation. Finally, each computer user would have to download and install a full application that is specific to their needs. This is the most problematic in terms of server support, bandwidth, and user permissions.