For upstream oil & gas

Auto-generated P&IDs from operator intent.

PadSpec is a layered rule engine that turns separation rates, basin context, regulatory framing, and your firm's engineering practice into a complete, auditable P&ID — equipment list, connection topology, sizing, and a rule-trace audit on every line item.

Generated P&IDHoffmeyer 12-1H Pad · Permian
Auto-generated P&ID for a single-well oil pad in the Permian Basin — 14 equipment items with full connection topology, produced deterministically by the rule engine.

Real engine output. Not a mockup.

What changes

What took a team of engineers months now takes one engineer in hours.

The work that used to consume a facilities engineering team for a full project cycle — wizard interviews, equipment sizing, P&ID drafting, rule-by-rule justification, estimate-to-final reconciliation — collapses into a single engineer's afternoon.

BeforeWith PadSpec
  • Months of engineering timeHours, not months
  • A team of engineers per specOne engineer, end-to-end
  • Hand-drafted P&ID in CADAuto-generated, rule-cited P&ID
  • Pre-sell estimate ≠ final designOne spine from estimate to deliverable

How it works

Three steps. Same flow, every facility.

  1. 01

    Capture operator intent

    An 8-step wizard collects separation rates, basin, regulatory context, and equipment preferences.

  2. 02

    Run the rule engine

    Layered rules — core, firm, project — fire deterministically. Equipment sized, topology resolved, every decision cited.

  3. 03

    Ship the P&ID

    Auditable diagram plus JSON / PDF exports. Native Visio (.vsdx) on the roadmap for the operator's editing tools.

See it work · one worked example

From operator inputs to an auditable facility spec.

The engine handles single-well pads, multi-well central tank batteries, gas pads, and water-handling facilities across the Permian, Bakken, Eagle Ford, Marcellus, and Haynesville. The inputs change, the rules that fire change, the equipment sizing changes — the auditable output shape stays constant.

Below is one worked example: Hoffmeyer 12-1H Pad, a single-well oil-weighted pad in Reeves County, TX · Permian Basin.

Generated P&IDHoffmeyer 12-1H Pad
Generated facility diagram for Hoffmeyer 12-1H Pad — 14 equipment items with connection topology, produced deterministically by the rule engine.
Inputs
Oil
1,500 bbl/d
Gas
1,800 mcf/d
Water
808 bbl/d
GOR
1,200 scf/bbl
H₂S
8 ppm
Future water cut
55%
Engine output
14
equipment items sized & catalogued
8
design rules fired, each cited in the trace
2
engineering warnings surfaced for review
Rule trace · cited inline on every line item
  • R003Free-water knockout added — high water rate justifies upstream separation.
  • R020Two oil tanks specified for 5-day storage with redundancy buffer.
  • R040TEG dehydrator required to meet sales-gas water-content spec.
  • R060Vapor recovery unit required under NSPS OOOOa for storage tank emissions.
  • R080LACT unit required because oil sales destination is pipeline.

Three more rules fired on this pad. Every rule citation is immutably tied to the spec version that fired it — a regulator or operator can trace any decision back to its source.

Why teams use it

P&IDs, generated from rules.

PadSpec turns operator intent into a complete P&ID — equipment, connection topology, sizing, rule citations — deterministically, in minutes. No CAD drafting from scratch, no parallel spreadsheets, no drift between the pre-sell estimate and the engineered deliverable.

Auditable by construction

Every spec carries a full rule trace and an immutable snapshot of the rule library that produced it. A regulator, operator, or your own QA can answer 'why this equipment, why this size' on any line item without picking up the phone.

Your firm's practice, encoded once

Senior engineers author overlay rules at the firm level — sizing margins, vendor preferences, the judgment calls that distinguish your shop — and every project inherits them. No more re-arguing the same decisions on every pad.

Pre-sell and final share one spine

A project carries a pre-sell phase and a final phase, both backed by the same engine and the same rule library. The estimate you used to win the work is the seed of the engineered deliverable — no re-keying, no parallel spreadsheets.

Deterministic, repeatable, comparable

Same inputs, same rules, same output — every time. Re-run an old project against today's rule library and see exactly what changed and why. Versioning, diffs, and overrides are first-class.

Design partner

PadSpec is being built in partnership with Pursuit Services, a facilities engineering and project delivery firm for upstream oil & gas operators.