V5 Ultimate
Module · Scheduling

Schedulingvisual, finite, and constraint-aware.

A schedule the floor will actually follow because it respects the constraints the floor actually has.

Start free — no card
No whiteboard · no Excel · no daily firefight

A schedule that re-plans itself when reality changes.

Tap a "what if" — an operator out, a material slipping, a cal due. The Gantt re-flows around every constraint: skill, instrument cal, BOM, shift, eBMR readiness.

06:00
07:00
08:00
09:00
10:00
11:00
12:00
13:00
14:00
15:00
16:00
17:00
Line A
WO-918 · 500 mg
WO-919 · 250 mg
WO-920 · 1 g
Line B
WO-870 · syrup
WO-871 · cream
WO-872 · gel
Line C
WO-655 · tab A
WO-656 · tab B
WO-657 · tab C
Pack
WO-PK-203 pack
WO-PK-204 pack
all clear
All constraints satisfied · plan locked
OEE plan
82%
WOs
11
on-time
100%
Not a queue. A negotiator.

The plan you're looking atwas negotiated 80 milliseconds ago.

Every constraint — equipment availability, operator skills, shift calendars, material readiness, changeover penalties, customer promise dates, regulatory hold windows — is a chip on the table. When a chip moves, V5 re-bargains the entire plan against the same constraints and shows you the new feasible schedule before you can refresh.

7 axes
constraint dimensions
~80ms
re-plan latency
0 manual
drag-and-drop required
1 source
of plan truth
Breakdown · live re-plan

Line B goes down at 09:18. The plan rewrites itself.

Watch the timeline cycle: before the breakdown, the alert moment, and the re-negotiated plan. WO-919 hops to Line C because its skill profile matches. WO-922 slides into Line A's open slot because its changeover cost from Lot B is lowest there.

gantt · T-0 baseline plan
LINE-A
WO-918 · Lot A
WO-921 · Lot B
LINE-B
WO-919 · Lot C
WO-922 · Lot D
LINE-C
WO-920 · Lot E
WO-923 · Lot F
↩ pulled forward into open slot
↪ moved to skill-matched line
— halted, ticket auto-opened
What the negotiator is bargaining with

Seven axes, one feasible answer.

01
equipment
valid · in-cal · clean · unbooked
02
operator
trained on current SOP rev · on-shift · not idle-locked
03
material
released · in-spec · FEFO-eligible · LPN at staging
04
changeover
minimize allergen/color crossover cost matrix
05
promise
customer due-date and tolerance per SKU
06
regulatory
post-cure hold, stability window, segregation rules
07
energy
peak-demand windows, oven preheat overlap
Changeover · choreography

The changeover starts before the last unit drops.

V5 doesn't wait for "line ends." It pre-stages the next lot, pages the cleaning crew, and books the QA pre-release window while the current run is still flowing. The lines you optimize are the ones that don't sit cooling.

LINE-A · changeover · Lot B → Lot D
  1. 08:54
    Last unit of Lot B falls off
  2. 08:55
    Auto-CIP cycle starts (cleaning crew paged)
  3. 09:08
    Lot D staged at LINE-A by FEFO-aware picker
  4. 09:14
    QA pre-release check signs the clean line
  5. 09:18
    First unit of Lot D — zero idle time
24 minutes saved vs. linear changeover — banked into next WO's promise date.
Promise · the customer-facing edge

Every plan change updates a promise date in real time.

ATP / CTP, automatic

Available-to-promise is computed from the live plan, not a nightly snapshot. Sales sees the same truth as the planner.

Customer portal sync

If a re-plan pushes a ship date by 2 days, the customer portal updates the same minute and a notification fires.

What-if without commit

Simulate "what if WO-925 jumps the queue?" — see the cascading promise impact before clicking commit.

A plan that's always feasible is a plan you can actually run.

V5

Curious how the planner actually behaves?

What it talks to

One scheduler. Every constraint. No glue code.

The planner is the centre of gravity. ERP, MES, maintenance, people, materials and customer promises are wired in — not bolted on.

Scheduler
Centre of gravity
  • ERP demand
    Two-way

    Sales orders, forecast and safety-stock pulled two-way; firm-up posts confirmed dates back.

  • Labour & shifts
    Skills-aware

    Crew rosters, skills and shift calendars constrain the plan — no batch lands without qualified people on hand.

  • Calendar feeds
    .ics

    iCal/.ics per crew, per asset, per shift — drops straight into Outlook / Google Calendar.

  • MES · kiosk
    Live

    Schedule is the authority for what kiosks show. No un-scheduled batch starts without an override.

  • Maintenance & OEE
    Constraint

    PM windows, calibration due dates and downtime are first-class constraints — not a side spreadsheet.

  • Customer portal
    Auto-push

    Promise dates and shipment ETAs flow to customers automatically — fewer 'where's my order' calls.

V5

Not sure if V5 talks to your stack?

When the day goes sideways

The edge cases buyers always ask about.

Real schedules break the moment reality shows up. Watch V5 absorb the three hits planners dread — without anyone re-keying a thing.

Hot order · 3:07pm
0810121416
+2h OT · 1 slip · 0 allergen

What-if before you commit

Drop the rush in. V5 instantly shows which orders slip, by how much, the overtime cost, and any allergen conflicts that open up. Commit only when the trade-off is acceptable.

Material ETA · slipped
PO-9921 ETA+1 day
WO-4821
WO-4822
WO-4830
WO-4841
WO-4855
portal · promise dates → 14 customers

Amber cascades, customers warned

Affected WOs auto-flag amber. The customer portal updates promise dates. CSRs get a digest of who needs a call — before customers email in.

Operator · called in sick
Mix
Fill
Seal
Pack
A. Reyes
·
·
M. Khan
·
·
L. Park
·
·
S. Vidal
·
·
⚠ 2 steps blocked · reassign

Skills matrix re-checks coverage

Every scheduled step re-validated against the skills matrix. Steps that need a specific competency surface as blocked until reassigned — nothing runs uncovered.

Each scenario is a live policy in V5 — not a slide.Same engine runs every shift, quietly, in the background.
V5

Got an edge case the team's worried about?

Engineered on
21 CFR Part 11 e-signatures
Immutable audit trail
Multi-tenant RLS isolation
GS1-128 license plates
Two-way ERP adapters
Instead of an FAQ

Just ask V5 — it knows the product cold.

Pick a question or type your own. V5 answers grounded in how production scheduling — drag-drop work orders & finite capacity | v5 ultimate actually behaves on the floor.

Got questions, or want to see it on your shop floor?

Ask V5 — our code-aware assistant — or spin up a workspace. Both are free.