Datasets & scenarios

The Live dataset

Your default dataset is called Live. It mirrors Odoo every sync. Live is read-only — you cannot run the scheduler against it or edit ops directly. Treat Live as the canonical reference state.

To plan, you create a scenario (an editable working copy of Live). All scheduling and edits happen inside scenarios.

What is a scenario

A scenario is a named, editable copy of a dataset. Create one when you want to:

• Try a different scheduling strategy without disturbing the floor
• Test a what-if (“what if priority for order X were raised?”)
• Simulate a disruption (machine breakdown, material delay)
• Show options to a colleague before committing

Scenarios are completely isolated. Editing a scenario does not touch Live or Odoo until you explicitly publish.

Create a scenario

1. Click New Scenario in the top bar (or Save Scenario when already inside a scenario).
2. Give it a name (e.g. “Q3 ramp-up”) and an optional description.
3. Click Save.

APS clones the currently-active dataset — usually Live — into a new scenario, copying every MO, WO, BOM line, locked state and priority. You're switched into the new scenario automatically.

Switching datasets

Use the dataset switcher in the top bar to move between Live and your scenarios. Every page — Schedule, Orders, Materials — updates to show the active dataset's data.

Edit a scenario

Inside a scenario you can:

• Run any number of scheduler runs with different settings
• Change MO priorities or due dates
• Lock or unlock individual operations
• Drag-and-drop on the Gantt

Comparing one plan with another

The Datasets page used to put a card per scenario side by side with four averages on each and no difference between them, which answered a question nobody was asking. It is gone. Capacity asks the question it was reaching for: what would it take, and which orders would that move — by name, with the date before and after.

Publish back to Odoo

When you're happy with a scenario, click Publish in the top bar. APS writes the scenario's schedule (start dates, resource assignments) onto the matching MOs in Odoo. Only fields APS owns are touched — quantities, customers, products, etc. remain untouched.

Update material reservations is on by default. After the dates are written, APS releases the reservations it is allowed to touch and hands the stock back out in the order the plan says — rush orders first, then highest priority, then earlier deadline. Work that has already started keeps its material.

Publishing moves the dates of sub-assembly orders too. That is Odoo's own behaviour: a component's need date follows the order that consumes it, the same way Odoo's own Plan button works. The delivery date of the finished order, which comes from the sales order, is not touched.

Unplan what this plan leaves out is the second switch, and it is off unless you turn it on. With it, an order the run deliberately left out of the plan — because nothing covers its components — also has its dates cleared in Odoo, so the shop floor is not left looking at a date APS no longer stands behind.

Cleaning up

Old scenarios cost nothing but clutter the switcher. Delete from the Datasets page when no longer relevant. Live cannot be deleted.