Operations
Scheduling
Put work orders on a timeline. Drag them onto lines. Release the plan.
Scheduling holds the work orders and the week's plan. The planner drags a job onto a line on a Gantt, a timeline with one row per line. Everybody reads the same plan instead of the last spreadsheet that came round by email.
The planner places the work. The system does not invent a sequence of its own. A job can only land on a line that can actually run that product, and any other drop is refused. Release is a deliberate step, so the floor only sees work that has been released. Work orders can also be imported from the plant's ERP, the back-office system for finance and purchasing. They land in the unscheduled pool and the planner still places them.
Production reports back against this plan. As the line declares output, the made quantity moves on the bar. Capacity Planning can publish the near weeks into the same unscheduled pool.
Who uses it
| Person | What they do here |
|---|---|
| Planner | Creates work orders, sequences them on the Gantt and releases the plan. |
| Supervisor | Reads what is released and what is running. |
| ERP | Pushes a list of work orders in. The planner still places them. |
Today vs Phasis
What you get
- One timeline for the plant, with a row per line.
- The planner places the work. The system does not invent a sequence.
- A job can only land on a line that can actually run that product.
- Release is a deliberate step, and the floor only sees released work.
- Progress on the bar comes from what Production declared.
- Capacity Planning can fill the pool. This module places it.
See it on your own plant.
Thirty minutes with an engineer. We walk the modules you care about against your own lines and shifts.