WellOPS · Equipment Maintenance · Permits, Lone-Worker, MOC, Incidents
The easiest equipment maintenance module to configure. And the most meaningful.
For Maintenance Managers · Field Superintendents · VP Ops
Part of WellOPSYou buy WellOPS from WorkSync. Field Work Management is the work management capability of WellOPS, the operating platform for production operations, and it ships with the platform.
Configuration
The easiest equipment maintenance module to configure.
Configuration is three objects. Equipment classes describe the kinds of things you own: rod pumps, ESPs, plunger lift, compressors, separators, tanks, meters, valves. Maintenance plans hang off those classes and carry an interval, a task list, a parts list and a qualification. Triggers say when a plan fires: a calendar date, a runtime or cycle count, a regulatory clock, or a condition read off SCADA. Set those three and the module runs.
The reason a traditional CMMS takes a year is that it wants a complete, correct equipment hierarchy before anything works, and building one across thousands of wellsites is a project in its own right. This module is designed the other way around: it starts from the well and the site, and equipment attaches as it is found. If a field team member knows the equipment is there, they can log against it from the app, in the field, and the record fills in from the work rather than from a spreadsheet exercise that has to finish first.
Everything is configured, not built. When your maintenance strategy changes, you change the class, the plan or the trigger, and the change lands on the next sync. There is no development cycle between you and a different cadence.
Equipment classes
A short list you write once, in your own vocabulary. Classes carry the attributes that matter for scheduling, not a full engineering taxonomy.
Maintenance plans
Interval, task list, parts, expected duration and the qualification required. Plans attach to a class, so adding an asset inherits the whole schedule.
Triggers
Calendar, runtime, cycle count, regulatory clock, or a condition read off SCADA. A trigger firing creates the item; the ranking decides when it gets worked.
Why it is meaningful
The work that never reaches the CMMS is the work that matters.
Upstream carries an enormous number of assets at wildly variable value, and the maintenance that keeps them producing is small, frequent and mostly undocumented: plunger changes, stuffing box greasing, chemical checks, meter calibrations, belt and packing replacement. In most operations that work is scheduled by habit, tracked in a text message, and invisible to the system that is supposed to own maintenance.
This module puts that work in the same ranked queue as production response, so it is scheduled against value rather than against a calendar. A greasing job on a high cash-flow producer outranks the identical job on a low-rate well, and both are visible with a dollar figure and a due date instead of a color.
Two rules keep it honest. Regulatory deadlines are absolute where the regulator sets them, so a compliance PM never gets ranked out of existence by a production job. And the unit of optimization is the site stop rather than the task, so the grease gun rides along with a visit that was already worth making instead of generating a dedicated truck roll.
What it does
7 capabilities that turn your existing stack into action.
- 01
Configured from three objects, not from a completed hierarchy
Equipment classes, the maintenance plans that hang off them, and the triggers that fire those plans. Assets attach to the well and the site as the field finds them, so the record fills in from the work rather than from a hierarchy project that has to finish before anything is usable. - 02
Work generated from SCADA conditions and PM triggers
Runtime thresholds, cycle counts, sensor drift, pressure conditions and calendar or regulatory clocks each raise the item automatically, pre-filled with the asset, the plan, the parts, the qualification and the expected duration. - 03
Every item priced against the value of the site it sits on
The same task on two wells ranks differently because the wells are worth different amounts, read from current production and your price deck rather than from a static criticality field. Maintenance backlog and production response share one ranked list. - 04
The site stop is the unit of optimization
Items pending at a site are bundled into the visit, so a crew already going there for a higher-value reason picks up the greasing, the meter calibration and the visual inspection in the same stop. Nobody is dispatched for a grease gun alone. - 05
Built for gloves in a truck cab
One-tap completion, voice-to-text notes, photo capture and offline-first caching for cellular-dead zones. Most field team members are productive on the mobile app within two hours. - 06
Full lifecycle with the cost and the cause attached
Create, assign, execute, verify, close, every step in-platform. Parts and labor are captured at close-out against your well and equipment hierarchy, every failure carries its cause code, and the accrual is booked with the work, not at month-end. - 07
Compliance evidence that rolls up on its own
Regulatory PMs (valve inspections, tank integrity, cathodic protection) tracked with dates, evidence and signatures, with API RP 75 and OSHA PSM workflow templates included. Auditor packets generate on demand.
How a job gets scheduled
Deadline and site value, weighed together.
A maintenance item does not sit in a maintenance queue waiting for a maintenance planner. It enters the same ranking as everything else and earns its place in a crew’s day.
- 01
The trigger creates a priced item
A PM comes due, a runtime threshold trips, or a condition flag fires. The item is created pre-filled with the asset, the plan, the parts and the qualification, and it carries a dollar figure from the moment it exists.
- 02
The deadline sets the hard bound
Where a regulator or a permit sets the date, that date is absolute and the item escalates on its own approach to it. Everywhere else the due date is a soft bound that raises the score as it nears.
- 03
Site value sets the position
The same task on two wells ranks differently because the wells are worth different amounts. Value is read from current production, your price deck and your interests, not from a static asset criticality field somebody set in 2019.
- 04
The site stop is the unit
Items pending at a site are bundled into one visit, so a crew already going there for a higher-value reason picks up the grease job, the meter calibration and the visual inspection in the same stop.
- 05
The close-out carries the cost and the cause
Parts and labor are captured at close-out against your well and equipment hierarchy, and every failure carries its cause code. The accrual is booked with the work, not at month-end.
- 06
The history sharpens the interval
Failure and close-out history per equipment class and per failure mode feeds back, so intervals move toward what your assets actually need instead of the manufacturer default nobody revisited.
The ranking itself comes from the Work Engine, and the day it lands in is solved by the Route Optimizer.
What it replaces
Retires the workarounds your team has been stacking for years.
How it works
Three steps from your existing data to field action.
- 1 · Configure
Three objects, days not quarters
Equipment classes, maintenance plans and triggers. Assets attach from the field as they are found, so nothing waits on a completed hierarchy. Changes to strategy land on the next sync. - 2 · Generate and rank
The item arrives priced
A trigger fires and the item is created pre-filled, then priced against the value of the site and bounded by any regulatory deadline. It enters the same queue as production response. - 3 · Bundle, work, and close
One stop, cost and cause attached
Pending items bundle into the site stop the crew is already making. Parts, labor and cause code are captured at close-out, the accrual books with the work, and the history sharpens the next interval.
Works with your existing stack
Reads the systems you already run.
- IBM Maximo
- eMaint
- MaintainX
- Fiix
- Enertia
- Quorum
- Oildex
- Ignition
- AVEVA PI
- Cygnet
- iOS
- Android
- Signature capture
- Photo upload
Pricing · WellOPS
Scoped to your operation.
Impact Guarantee · license fees only when the metrics move
You buy WellOPS from WorkSync; the tracks beside this are rollout scopes of that one purchase.
Scoped to your well count and systems with our implementation team when you plan your pilot. The pilot runs four weeks on one field, and DataHub is included.
- GOOD
- Field Work Management standalone
- BETTER
- adds DataHub + Field Data Capture
- BEST
- adds Work Engine + Operations Dashboard
Proof
Field Work Management ties the permit clock, the lone-worker check-in and the maintenance item to the same ranked plan the field team member is already running, so a permit approaching expiry and a missed check-in each reach the right person in minutes, on the same screen as the work.
Capability statement · permit and lone-worker workflow
Before you ask
Common questions
How long does configuration actually take?
Do I have to replace my existing enterprise CMMS deployment?
How is this different from a horizontal CMMS?
How does maintenance get ranked against production response?
Can field crews learn it without a week of training?
What does it cost?
What about compliance reporting (PSM, OSHA, API)?
See the maintenance module configured on your equipment.
Bring one field and your equipment list. We configure the classes, the plans and the triggers with you, and show you the maintenance backlog ranked against your production work with the dollars attached.