WellOPS · Equipment Maintenance · Permits, Lone-Worker, MOC, Incidents

The easiest equipment maintenance module to configure. And the most meaningful.

See Your Wells RankedView a Sample 6 AM Plan

For Maintenance Managers · Field Superintendents · VP Ops

Gate valves, a pressure gauge and a flexible connector on a manifold of steel lines above a gravel pad

Part of WellOPS

Configured in days from three objects.

Live in four weeks.

You buy WellOPS by WorkSync. Field Work Management is the work management capability of WellOPS, the operating platform for production operations, and it ships with the platform.

  • 3
    Objects to configure
  • 5,000+
    Wells under coverage, deployment fact
  • 4 wks
    Kickoff to live
  • 1
    Record for permits, MOC, and lone worker

In plain terms

What is field work management in oil and gas?

Field work management in oil and gas is the practice of planning, dispatching and recording the work done at wellsites and facilities: inspections, preventive maintenance, repairs, and the follow-up that a failure creates.

How it works, and what sets it apart

It works by holding one queue of open work against each asset, assigning each item to a crew and a day that can physically reach it, and closing it with the labor, the parts and the readings captured at the location, so the asset history stays complete.

The constraint that separates it from maintenance management inside a plant is distance: the crew spends a large share of the day driving between sites.

Oilfield work management 

Configuration

The easiest equipment maintenance module to configure.

Configuration is three objects. Set those three and the module runs.
Equipment classes

Equipment classes describe the kinds of things you own: rod pumps, ESPs, plunger lift, compressors, separators, tanks, meters, valves.

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

Maintenance plans hang off those classes and carry an interval, a task list, a parts list and a qualification.

Interval, task list, parts, expected duration and the qualification required. Plans attach to a class, so adding an asset inherits the whole schedule.

Triggers

Triggers say when a plan fires: a calendar date, a runtime or cycle count, a regulatory clock, or a condition read off SCADA.

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 a traditional CMMS takes a year

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.

Configured, not built

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.

Why it is meaningful

The work that never reaches the CMMS is the work that matters.

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.
Small, frequent and mostly undocumented

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.

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.

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.

WellOPS on a phone: today’s route with the first stop open, why the crew is there, and the do-this-now task with its one-tap outcomes (synthetic demo data)
Demo screen, synthetic data

What it does

7 capabilities that turn your existing stack into action.

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.
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.
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.
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.
Built for gloves in a truck cab
One-tap completion, voice-to-text notes, photo capture and offline-first caching for cellular-dead zones. Crews pick it up on the job rather than in a classroom.
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.
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.

Pricing · WellOPS

Scoped to your operation.

You buy WellOPS by WorkSync; the tracks beside this are rollout scopes of that one purchase.

  1. GOOD

    Field Work Management standalone

  2. BETTER

    adds DataHub + Field Data Capture

  3. BEST

    adds Work Engine + Operations Dashboard

Impact Guarantee · license fees only when the metrics move

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.

See How Pricing Works
See Your Wells Ranked

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

Read the full 3-basin case study 

Before you ask

Common questions

What is field work management in oil and gas?
Field work management is the planning, dispatch and recording of the work done at wellsites and facilities: inspections, preventive maintenance, repairs, and the follow-up a failure creates. One queue of open work hangs off each asset, each item is assigned to a crew and a day that can physically reach it, and it closes with the labor, the parts and the readings captured at the location, so the asset history stays complete. What separates it from maintenance management inside a plant is distance: a crew spends a large share of the day driving between sites, so the sequence of the work is as much of the problem as the work itself.
How long does configuration actually take?
Days, because there are three objects to set: equipment classes, the maintenance plans that hang off them, and the triggers that fire those plans. It does not require a completed equipment hierarchy first, which is the requirement that turns a traditional CMMS configuration into a year-long project. Assets attach to the well and the site from the field as they are found, and the record fills in from the work.
Do I have to replace my existing enterprise CMMS deployment?
No. Field Work Management co-exists with it: run this for field crews and mobile workflows and keep the CMMS as the enterprise system of record for high-value assets. Many customers start with co-existence and migrate specific asset classes over time.
How is this different from a horizontal CMMS?
Horizontal tools serve construction, manufacturing and facilities, and they have no concept of a well, a lift type, deferred production or a price deck. Field Work Management is oil-and-gas-native: work generated from SCADA conditions, every item priced against the value of the site it sits on, the site stop as the unit of optimization, and direct integration into production accounting.
How does maintenance get ranked against production response?
On the same economic ruler. Each maintenance item carries a dollar figure derived from the value of the site and the consequence of deferring it, so a greasing job on a high cash-flow producer outranks the identical job on a low-rate well. Regulatory deadlines are absolute where the regulator sets them and never get ranked out of existence. Items pending at a site bundle into one visit, so small tasks ride along with a stop that was already worth making.
Can field crews learn it without a week of training?
Yes. Most field team members pick it up on the job rather than in a classroom. One-tap completion, voice-to-text, photo capture, offline sync. The design bar is a truck cab at 6 AM in gloves.
What does it cost?
You buy WellOPS by WorkSync; Field Work Management is its work management capability, and the tracks are rollout scopes of that one purchase. GOOD (standalone start), BETTER (adds DataHub + Field Data Capture), BEST (adds Work Engine + Operations Dashboard). Scoped to your well count and systems with our implementation team when you plan your pilot, and deployed in four weeks.
What about compliance reporting (PSM, OSHA, API)?
Built in. PM schedules for API RP 75 / OSHA PSM / state-specific regs with templates, and audit packets generated on demand. Every task is linked to the regulation it satisfies, so the evidence chain assembles itself.

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.

See Your Wells RankedView a Sample 6 AM Plan