1. Military Open Simulator Enterprise Strategy
Virtual World Technology Strategic Applications

2. Overview
What is MOSES?
Why was MOSES created?
What value does MOSES bring to military training applications?
What are the down sides?
What does the MOSES architecture look like?

3. What is MOSES
The Military Open Simulator Enterprise Strategy is an exploratory effort designed to evaluate the ability of the Open Simulator to provide independent and secured access to a virtual world.
Year One Goals:
Provide a completely independent virtual world capability. Runs in an enclaved network, capable of multiple levels of secured processing.
Provide a stable in-kind Second Life®-like environment.
Provide guidance to other organizations wishing to replicate the MOSES results.
Link with other organization in a hyper-grid manner to demonstrate external growth and scalability.
Next Steps:
Secured/Encrypted Communications
User Authentication with certificates and CAC
Larger Scale User Support
Integration/Conformance with the DoD Virtual World Framework

4. Why Was MOSES Created? SLE: 20 Feb 2011 8 Concurrent Sims VOIP
Replacement to the Second Life® Enterprise Project
Effort to preserve significant investment in the SLE platform.
Continue research started in the SLE platform.
SLE: 20 Feb 2011
8 Concurrent Sims
VOIP
MOSES: 26 Mar 2012
182 Concurrent Sims
VOIP
MESH, Media on a Prim
30+ Gb Assets

5. What value does MOSES bring to military training applications?
Breaks the traditional paradigm of modeling and simulation.
Art Pipeline
Computationally Steerable
The scripting language can enact changes to objects without restarting simulation.
Out of the Box External Communications Mechanisms
Everything in the environment is an interactive object, capable of being driven by external behavior models.
Every Object can connect to an external data source.
Flexible Terrain
Real world terrain sources can be used.
Terrain is deformable while simulation is running; May be restored via scripting
Persistent Virtual Environment
Capable of High Availability and Uptimes
Multiple Communications Options
Point to point chat, point to many chat
Point to point VOIP, point to many VOIP – can replicate military radio behavior

6. What are the down sides?
Insecure communications between client and server.
Phase II of the MOSES project will look at 100% encryption of all data transmitted/received.
Content is produced to the client “on demand”.
Susceptible to network lag.
Physics engine needs work.
Phase II of the MOSES project will experiment with alternate physics engines.

7. What does the MOSES architecture look like?
Host Hardware:
4x12 Core
512 Gb Ram
Typical VM Guest:
8 Core
64 Gb Ram
Hypervisor VM Manager
OpenSim Server 1-20
OpenSim Server 21-40
OpenSim Server 41-60
OpenSim Server n …
Robust / Monit
Mumble Server
MySQL Server
SRAS Server
Firewall not part
of MOSES system
but part of location
infrastructure
STTC Network
Firewall / NAT Translation
Unknown Network
(Internet)
MOSES Client 1
MOSES Client 2
MOSES Client 3
MOSES Client m …

8. Lessons Learned Created preconfigured client.
Subject matter experts may not be technical.
Network is most precious resource.
Community is critical for sustainment.
Regular office hours
Assistance with management
Adopt flexible culture
Plan ahead for growth, network/computing hardware
Listen to open source developers to help make informed decisions

9. MOSES Website: http://fvwc.army.mil/moses/ MOSES Account Page:
Project Information
MOSES Website:
MOSES Account Page:
MOSES Wiki: