V5 Ultimate
Module · Maintenance & OEE

MaintenancePMs run on the kiosk, OEE rolls up by itself.

Assets are first-class. PMs schedule themselves, technicians close them on the kiosk, downtime gets a reason at the moment it happens, and OEE rolls up without a spreadsheet.

Start free — no card
PMs aren't a calendar · they're a heartbeat

Every asset has vital signs.

MIXER-3 on Line B is live below. Temperature, vibration and runtime stream from the floor; when a threshold trips, V5 opens the work order and reserves the parts before a human notices.

MIXER-3 · Line B · Suite 2
live · 1 Hz
Motor temp
68.0°C
55 – 72 °C
Vibration
2.40 mm/s
≤ 2.7 mm/s
Runtime
4,192 h
next PM at 4,300 h
vibration · last 60s
0stolerance band ± 2.7 mm/snow
next PM (vibration-based)120 h to threshold
queued
WO-PM-0922 · MIXER-3 · bearing inspection
trigger: runtime ≥ 4,300 h
assignedJ. Patel · MFG eng
SLAnext planned downtime
parts reservedBRG-624 · O-RING-118 · GREASE-MS2
downtime impactscheduled · no impact
SOPSOP-MAINT-051 · rev 4 · approved
✓ MIXER-3 cleared · last PM signed · vibration baseline 1.8 mm/s
Condition-based PM · OEE-first

Assets ask for the wrench before they fail.

Calendar-only PM either over-services or surprises you. V5 watches runtime, throughput, vibration and temperature on every asset — and opens the right PM work order when the asset's behaviour says so.

The pulse · live

Four signals. One verdict.

MX-19
Mixer · Line B
Runtime to PM
1842h / 2000h
Vibration mm/s
22
PK-04
Packer · Line A
Runtime to PM
1180h / 1500h
Vibration mm/s
14
FL-08
Filler · Line B
Runtime to PM
1985h / 2000h
Vibration mm/s
38
CV-12
Conveyor · main
Runtime to PM
4204h / 5000h
Vibration mm/s
9
The PM writes itself

FL-08 hit 1,985 runtime hours. V5 opens the work order.

The PM template is already linked to the asset class. Parts are checked against inventory and a pick list issued. The technician gets the right SOP rev on the right device, on the right shift, with the right lock-out tags pre-printed.

WO-PM-2025-0918 · auto-generated
Asset: FL-08 · Filler · Line B
Trigger: runtime 1,985h ≥ 95% of 2,000h target
Template: PM-FILLER-Q · 8 tasks · 2.5h est
Parts: gasket kit FK-19 (in stock · BIN-D-04)
Scheduled: Thursday 06:00 (line idle window)
Technician: J. Patel · SOP MFG-204 rev 9
LOTO tags: pre-printed · TAG-2241..2245
OEE · honest math

Availability × Performance × Quality. No fudge factors.

Availability 88%

Planned run time minus unplanned stops. Planned downtime excluded — visible separately.

Performance 92%

Actual speed vs nameplate. Micro-stops and minor speed losses captured per cycle.

Quality 96.9%

Good units / total units. Quality scrap traced to root cause.

OEE = 0.88 × 0.92 × 0.969 = 78.4% · Line B · last 7 days

A floor that warns you. Then fixes itself.

V5

Curious how maintenance actually behaves on the floor?

What it talks to

One asset register. Every signal. No spreadsheet.

The asset is the centre of gravity. Sensors, parts, calibration, the schedule, the kiosk and finance are wired in — not bolted on.

Asset register
Centre of gravity
  • Sensors & PLCs
    Live

    OPC UA / Modbus TCP for runtime, temperature, vibration. No external historian needed for basic OEE.

  • Spare parts · WMS
    Pre-pick

    PMs pre-reserve the parts kit; missing parts surface before the technician walks to the asset.

  • Calibration partners
    Cert-aware

    External cal certificates upload via the supplier portal and attach to the asset record automatically.

  • Scheduling
    Constraint

    PM windows are constraints in the production plan — known maintenance is never a surprise.

  • MES · kiosk
    Two-way

    Technicians close PMs at the same kiosk operators run. Faults raise from the live step.

  • ERP · cost
    Roll-up

    Parts, labour and downtime hours post to the asset and roll up to maintenance cost in finance.

V5

Wondering how V5 maintenance plugs into your stack?

When the asset misbehaves

The edge cases buyers always ask about.

PMs slip, lines move, things just break. Watch V5 absorb the three hits maintenance dread — without losing a record or a part.

PM overdue · mid-batch
Asset MX-204 · runtime hours
0hPM @ 1000h
BMR-9120 · runningfinish allowed
BMR-9121 · nextblocked · PM due
no override path

Soft-warn now, hard-block next

The running batch completes — no silent override. The next batch on that asset is blocked until the PM is closed and signed at the kiosk.

Asset · moved Line 1 → Line 3
Line 1
MX-204
Line 3
moves
history travels with it
PM · 1000h
Cal · 14 Mar
Bearing swap

History travels with the asset

Every PM, every breakdown, every part used follows the asset to its new home. The line-change is an e-signed event in the trail.

Unplanned · breakdown
MX-204 · downunplanned
pick reason · 2 taps
Mechanical
Material
Operator
Other
schedule re-cut · QA notified for BMR-9118

Two taps, reason captured, plan re-cuts

Operator scans the asset, picks a reason. Unplanned downtime opens, the schedule recomputes downstream impact, and QA is paged if a batch is at risk.

Each scenario is a live policy in V5 — not a slide.Same engine on every line, every shift.
V5

Got a maintenance 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 maintenance & oee — pms, downtime, condemn, requisitions | 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.