NEXUS Work Control is work control and maintenance management in one governed flow — from anyone's work request, through planning and scheduling, to an authorization decision that checks what's actually isolated right now, not what a paper plan assumed.
The work order system and the isolation system are usually strangers — so "is it safe to release this job?" gets answered from memory, radio calls, and yesterday's printout.
NEXUS closes that loop. Designed to be the first to connect work orders, live isolation state, and drawing-derived connectivity in one governed authorization decision — and the boundary is principled: Work Control asks; the safety system decides.
One card, one job, one truth. A red band means an isolation rides with the work, today's release decision is checked against live isolation state — and the board knows when a day is overloaded for the crew you actually have, before the week starts.
The same calm grammar as the product — overdue wears red, today wears the watch color, the decision chip flips the moment the conflict clears — and Thursday is already telling you it's three hours short, while there's still time to move work or add hands.
The operator who heard the bearing can raise the request — planners triage it into real work with failure context preserved from the first report.
Boards and planning windows for routine weeks, outages, and campaigns — with resource load on the board: scheduled hours against the crew you have, so an overbooked day announces itself.
Release decisions check in-force isolations at the moment of authorization — four honest decision states, every decision attributed. LOTO-integrated work control.
JHA, permits, hold points, and step sign-offs ride the plan — and print as clean, branded field artifacts when the crew wants paper.
Preventive maintenance scheduling with deterministic PM generation and forecasting over a real asset registry — equipment, rotables, meters, weld identity.
Executor and approver are never the same person; failure and cause coding capture what was found; deferral-pressure analytics show where postponed work stacks risk.
Fetch-only connectors for SAP PM, IBM Maximo, and Procore plus CSV/JSON — external numbers stay references, never identity. And the read API and exports ride on every surface, never tier-gated.
Work Control consumes the isolation answer — it can never mutate it. The pushiest schedule in the plant still can't move a lock.
An inbound SAP or Maximo number is a reference, never the record's identity — outside systems inform the work, they don't own it.
Every surface exports; the read API is standard. Your data's exit door is part of the product, not an upsell.
Work control · Control of Work (CoW) · maintenance management · CMMS · work order software — whichever your team calls it, this page is for them. Built around 29 CFR 1910.147 and ANSI Z244.1 as design targets.
We'll walk one real job from request to authorized release — and show you the moment the isolation check would have caught something.