• Orders sequenced214 of 214

Production plan

Turn open orders into a plan for the whole site

Feed it your open orders. It builds the steps for each one from the process definition and ranks every candidate before anything lands on the schedule. You get a plan for the whole site, not a sequence for one line.

  • Every open order turned into sequenced steps
  • Steps derived from the process definition on the product
  • Candidates evaluated and ranked before anything is scheduled
  • Lowest changeover: WO-118363 Machining Cell B 40 min Picked

Routing and changeover

Check changeover cost before you set the order

It picks the asset your routing allows, then reads the changeover cost from your changeover matrix. Your sequencing rules and priorities decide what runs first.

  • Asset selection follows the routing on the product
  • Changeover cost read from the changeover matrix
  • Sequencing rules and priorities decide what runs first
  • One schedule Batch: 6 jobs Continuous: 2 lines MRO: pump rebuild

Run schedule

Plan batch, continuous and maintenance work together

One schedule covers batches, continuous lines, and maintenance and repair work. Batches run with their own quantities and steps, continuous flow runs as a rate over a window, and maintenance competes for the same assets as production.

  • Batch jobs sequenced with their own quantities and steps
  • Continuous flow scheduled as a rate over a window
  • Maintenance work planned on the same schedule as production
  • Line 2 went down 09:14
  • PRP-0318Proposal, 3 of 7 moves +40 min
  • Proposal PRP-0318 Commit plan Discard

Planning issues

Review a proposed plan before you commit it

A proposal is a draft, and nothing on your floor moves until you commit it. A replan never touches work that’s already started, and anything that can’t be scheduled shows you why.

  • Plan proposal and plan commit are two separate steps
  • A replan never moves work that has already started
  • Planning issues surface with the reason they could not schedule
  • Rush order, cost to the week +6 h
  • Compared to committed v41.2

Schedule simulation

Test a rush order or a down machine first

Run the scenario before you commit to it. A simulation shows what a rush order or a down asset costs your week, using the same constraints as the real plan, so you can compare it to the committed plan and decide.

  • What-if scenarios run against the same constraints as the plan
  • Compare a scenario to the committed plan, then commit or discard
  • Recommendations attach to the production order they affect
  • Fri18 Planned downtime, 06:00 to 10:00

Shift calendar

Set shifts and downtime once

Enter your shift patterns, planned downtime and changeover matrix one time, and every plan after that is built against them. See the week on the calendar or the shift on the run schedule, with tool utilization next to the plan that uses it.

  • Shift patterns and planned downtime set per site
  • Calendar view for the week, run schedule for the shift
  • Tool utilization shown next to the plan that consumes it
  • Machining Cell A, load todayFull
  • Bottleneck: Machining Cell A

Bottlenecks

See which machine is holding up the day

The bottleneck view names the resource capping your day, so the constraint isn’t a guess. The Scheduling Engine sequences the work. You still make the call on what happens next.

  • Bottlenecks ranked, so the constraint is not a guess
  • Command center shows the plan against what is happening
  • The Scheduling Engine sequences. A planner still makes the call.

FAQ

Bring the schedule that keeps breaking.

See how the Scheduling Engine replans when the floor changes. 30 minutes, no demo script.