MPP-Order
Submit an explicit scheduling request to the MPP Scheduler for computation. Orders create a clear execution boundary and make results reproducible.
Purpose
An order represents a clear execution boundary between project definition and algorithm execution. It ensures reproducibility by running the scheduler against a fully specified scenario (activities, resources, and parameters) at a point in time.
When to use
Use this module once activities, resources, and parameters are fully defined. If you change any of those inputs, submit a new order to generate a comparable result.
Good practices
- Verify activity data, resource calendars, and parameter values before submitting.
- Use meaningful order names (scenario, date, parameter set) to make comparisons easy.
- Avoid submitting multiple identical orders unless you intentionally need repeated runs for comparison.
Common mistakes
- Submitting orders with incomplete data (missing resources, invalid precedence links, or unset parameters).
- Assuming results update automatically after changes—orders are snapshots; changes require a new order.
Next module
View, compare, and interpret generated schedules.