Operator wallet and basin coverage for oilfield services companies

An oilfield services company is usually strong in one basin and blind in the next. Its own job tickets say which operators it serves and on which rigs. The rig activity file it already pays for says which operators are active and on how many. Joined, the two answer the question the regional sales director asks every quarter and nobody can answer: where are we absent from active operators. This guide sets out the join and the roll-up.

The measures

Per basin:

Basin coverage = rigs served ÷ rigs active Operator coverage = operators served ÷ operators active

Per operator and service line:

Wallet share = billed revenue on the line ÷ operator's estimated spend on the line

Per rep, the operators covered against operators assigned, and the gaps ranked by estimated value.

The rows you need

• Invoices and job tickets: one row per ticket with operator, well or rig, basin, service line, date, revenue and rep. From the field ticketing system and the billing system.
• Rig activity: one row per rig with operator, basin and status, by month. From Enverus, Baker Hughes or a public count.
• Coverage list: which rep or region owns which operator.
• Spend estimates: optional, per operator and line, with the basis recorded.

Operator identifiers only. On an enterprise deployment the whole roll-up runs in a separate tenant.

The join

Operators appear under different names in the ticketing system and the rig file. The join needs a mapping table from every operator name in every source to one identifier, maintained once and reused. The report counts rigs in the activity file whose operator did not map, because those are the operators nobody is looking at.

The roll-up

1. Operator by service line by basin: revenue, tickets, rigs served.
2. Operator by basin: lines sold, lines bought where estimated, rigs served against rigs active.
3. Basin: operators served against active, rigs served against active.
4. Rep and region: assert that tickets by operator sum to the rep's revenue, reps to the region, regions to billed revenue.

billed revenue = Σ regions = Σ reps = Σ operators = Σ service lines

The by-service-line equality catches a line renamed between the ticketing and billing systems. The by-rep equality catches an operator covered by two reps after a basin realignment.

A worked example

One basin, one quarter.

Basin coverage: 19 of 33 rigs, 58 percent. Operator coverage: three of four. Operator C is the finding, six active rigs and no tickets, and Operator B is the second: three rigs served of nine, one service line of four. The regional director's list for the quarter is two names with the estimated spend beside each.

Where it goes wrong

Operator names that do not map. Subsidiaries, joint ventures and abbreviations make one operator into five. The mapping table is the work, and the unmapped-rig count on the report is how you know it is incomplete.

Rig counts at the wrong grain. Monthly rig activity against quarterly revenue makes rigs served look small. Align periods before computing coverage.

Tickets without a basin. Tickets coded to a district office rather than a basin cannot join the activity file. The report counts them; the ticketing system needs the basin on every ticket.

Spend estimates treated as facts. An estimated wallet with no recorded basis becomes a number in a slide. Keep the basis on the row, and report coverage, which needs no estimate, alongside share, which does.

Every quarter, per basin

Mapped once, the ticket export and the monthly activity file produce the basin view every quarter, reconciled to billed revenue, with each rep's operators and gaps ranked. Covirage builds this from the exports as they are, operator identifiers only, inside the company's tenant on an enterprise deployment. The oil and gas services page describes the setup.