Permian Basin, West Texas. Wide area operations where expert drive times are measured in hours.
Every operations manager in oil and gas knows their labour rate. What fewer have calculated is how much of that labour produces zero value — not because the technician isn't working, but because they're driving. The $150 problem is simple: when a field expert drives two hours to help a struggling colleague, that's $300 in labour cost with no wrench turned, no task completed, no client value delivered.
The Visible Cost vs. the Real Cost
Operations managers track the obvious costs: parts, overtime, equipment rental. Expert travel rarely appears as a line item because it's absorbed into the general labour budget. The technician is "working" — they're just not producing anything while they drive.
In a wide-area operation like the Permian Basin, where a single service territory might span hundreds of square miles with dozens of sites, the accumulated cost of expert travel is substantial. Consider a team where experienced techs are called to assist junior colleagues two or three times a week:
Example calculation: 3 expert assist trips per week × 3 hours average travel per trip × $150/hr = $1,350 per week in non-productive labour. Over a year, that's $70,200 — per experienced technician — before accounting for vehicle costs, fuel, or the compounding effect of delayed jobs.
Why This Problem Is Getting Worse
The oil and gas service industry is facing a structural skills shortage. Experienced technicians are retiring faster than they can be replaced. The knowledge gap between a 20-year veteran and a 2-year tech is wide — and closing it currently means the veteran physically going to wherever the junior tech is stuck.
Distributed Operations, Concentrated Expertise
The most experienced people in your operation are also the most valuable. Every hour they spend in a truck is an hour they're not supervising, training, troubleshooting, or producing. In a Permian Basin operation where activity is spread across hundreds of miles of road — roads that themselves carry significant near-miss and accident risk — sending your best people to drive is a safety issue as well as a cost issue.
The Near-Miss Nobody Counts
There is a safety cost to expert travel that rarely appears in incident reports. Leash roads and basin highways in West Texas carry dense two-way traffic from service vehicles. Rear-view mirror accidents are common. Every expert assist trip that requires a two-hour drive is also an additional two hours of road exposure for one of your most experienced people.
"If I got a guy who is turning wrenches he's giving us value for the $150, but the guy driving up the road to help someone else is not benefiting the company."
The Remote Assistance Calculation
Remote assistance changes the unit economics of field support. Instead of the expert driving to the problem, the problem comes to the expert — via live video, audio, and screen annotation. The expert guides the fix from wherever they are. The time cost of a support call drops from three hours to twenty minutes.
- Expert assist time: 3 hours travel + 1 hour on-site → 20-minute remote session
- Road risk: eliminated for the expert, junior tech stays on-site and safe
- Documentation: automatically generated by the platform — no manual reporting
- Knowledge transfer: the junior tech learns by doing, with expert guidance, on the actual equipment
- Scalability: one expert can support multiple techs simultaneously, across multiple sites
How to Build the ROI Case Internally
If you're presenting remote assistance to a VP, safety director, or board, the most compelling argument is not the technology — it's the cost model. Here's the framework:
Step 1: Count Your Expert Assist Trips
Pull your dispatch records for the last 90 days. Count every instance where an experienced technician was sent to another site to assist a junior colleague. Include travel time in both directions.
Step 2: Apply Your Fully-Loaded Labour Rate
Multiply total travel hours by your fully-loaded hourly cost — salary, benefits, vehicle, and overhead. This is your current baseline cost for field support.
Step 3: Model the Remote Alternative
Estimate what percentage of those trips could be resolved remotely. Industry experience suggests 60–80% of equipment faults can be diagnosed and guided to resolution via live video without physical presence. Apply a 20-minute average session time. Calculate the savings.
Step 4: Compare Against Subscription Cost
Remote assistance platforms are typically priced as monthly subscriptions. The break-even point — when the labour savings exceed the subscription cost — is usually reached within the first two to four weeks of deployment for a team of ten or more field technicians.
The right question isn't "can we afford this?" It's "how much are we currently spending on the problem it solves — and how quickly does it pay back?"
The Training Multiplier
The ROI calculation above addresses only the direct cost of expert travel. There is a second, larger value driver: accelerated skills development in junior technicians.
When a junior tech is guided through a complex repair via remote assistance rather than waiting for an expert to arrive and take over, they learn by doing. The next time the same fault occurs, they may resolve it independently. This compounding effect — faster ramp speed for less experienced field staff — is often more valuable than the direct travel cost savings over a 12–24 month horizon.
The most important question to answer for a junior tech is not "what is broken" but "how do I fix it, correctly, safely, right now." Remote assistance answers that question in real time, on the actual equipment, with the actual context. No classroom can replicate it.
What to Look for in a Remote Assistance Platform
Not all remote assistance tools are created equal for field service environments. The standard video conferencing tools that work in an office fail in the field for predictable reasons:
- Cell connectivity: remote oil and gas sites frequently have limited or intermittent signal. The platform must degrade gracefully and sync data when connectivity returns.
- Offline capability: JSAs and safety checks must be completable without an active connection — paper JSAs exist because digital ones have failed at the wrong moment.
- Evidence capture: every session must automatically generate a timestamped log. Manual reporting is a burden that techs will resist and managers will chase.
- Annotation tools: the expert must be able to draw on the live video feed. Text instructions for a complex mechanical task are insufficient.
- Audit trail: every session must be attributable, timestamped, and retrievable — for near-miss reporting, client reporting, and regulatory compliance.