nextmv Docs

Design Goals

Design Goals

Nextmv is a decision modeling and simulation framework built for developers. It helps you automate and evaluate decisions like routing, scheduling, and assignment.

Hop helps you optimize and automate decisions as well as iterate quickly when requirements change. Dash provides a simulation environment that helps you pressure test your models to ensure you're taking the best approach, no matter what conditions come your way. Both Hop and Dash are modular packages that easily integrate with the modern, cloud-based development environment, which minimizes time spent on infrastructure and maximizes modeler impact.

Hop and Dash are unique in that they encourage users to follow decision engineering best practices.

At Nextmv, decision models and simulations mirror the same principles:

  • Repeatable
  • Testable
  • Interpretable

Repeatable models and simulations are easy to create and deploy to different environments. They are configured the same way in research and development, testing, and deployment. They can share business logic so you don't violate the DRY principle (don't repeat yourself).

Testable models are easy to validate and configure in CI/CD. Recoding decision logic into an unfamiliar language (e.g. linear inequality systems) or coding an entire discrete event-based simulator from scratch introduces layers of potential errors and maintenance. Hop models and Dash actors are built from state. This makes testing models or sims like testing other software.

Interpretable models and simulations have outputs that don't require complex data transformation. Hop decisions and Dash measures can be stored and queried directly just like any other data. They can be picked up and re-created from their inputs for debugging. The modeler owns the model and the actor definitions. It's not a black box behind a REST API.