Multi-Machine Build (MMB) is the third generation of the MMB technology.

In this generation, MMB nodes now can take advantage of the multiple cores on a cpu and multiple cpus in a system, meaning even faster performance for your most demanding projects.

Unlike other distributed solutions, MMB scales beyond the CPUs and cores inside a single computer to take advantage of the computational resource on your entire network; and MMB is not limited to the production of visual databases in a single proprietary format. 

MMB can accelerate the production of 3-D databases in the following formats: OpenFlight, TerraPage, CTDB-GCS, STRIVE, SEDRIS 3.1 as well as the production of GeoPaint, DTED, vectors, and other correlated source materials. Other formats are currently under development for MMB processing.

MMB is extremely scalable with users able to choose from 4 to 200+ computational nodes on a single production project.

MMB is extremely flexible; it allows multiple users/projects to select the number of compute nodes needed based on demand. MMB can also re-allocate un-used compute nodes to running programs.

MMB is easy to use. To use the MMB technology, select the MMB panel to check for computational resources that are not in use, check them out, select “build-MMB,” and watch it build faster then you thought possible. Many customers have seen 30+ day projects build in less then a single day using this technology. Allowing for better projects and lower cost of production.

MMB licensing can be individual dongles per slave or a new network license. MMB nodes are locked per instance of the software running.

MMB is designed to address the concerns of our customers in several areas:

• Faster production to support time sensitive applications
• Faster and scalable production to lower personnel cost by making the current employees more productive. Allowing the same number of employees to work on more projects in the same amount of calendar time.
• Faster production on demand when needed to make up or limit schedule impacts on programs. Something you cannot do by adding more people to a program.
• Addition and removal of computational resources during the build process so you can use more compute resources during night time hours and reallocate them to other tasks during normal work hours.