The libraries

Your firm's engineering practice, encoded once and cited on every deliverable.

PadSpec ships a core library of design rules, drawing conventions, and costs with research provenance on every entry. Your senior engineers author an overlay on top of it. Every project at the firm inherits both, and every drawing and estimate names the exact library state that produced it.

The core seed is a starting point, not an answer. Entries tagged practice carry a design-partner validation flag until confirmed; cost entries are labelled seed-only until a firm's reconciled projects calibrate them. The product shows those labels wherever the entry is used.

One rule, as the engineer sees it
R060_vru_required_nsps[verified]core

Storage-vessel vapor control applies and the gas has a sales path, so a vapor recovery unit is the default control device: recovered vapor is salable. The 95 percent standard is technology-neutral; with no sales path the vapors route to the combustion terminus instead.

When
gas sales destination is a gathering pipeline or gas plant, and either the NSPS OOOOb determination applies or the jurisdiction is Colorado or New Mexico
Then
ensure a VRU on the tank vapor header with 95 percent capture efficiency
Sources
40 CFR 60.5365b(e), 60.5395b, 60.5412b; 5 CCR 1001-9 Reg. 7 Part D; 20.2.50.123 NMAC
Firm overlay
a firm may shadow this rule by code, for instance to prefer a combustor below a vapor-rate threshold; the default device is marked operator-tunable

Three layers

Core, firm, project. The firm layer is the one that matters.

The core seed

Equipment catalog, topology templates, design rules, P&ID rules and conventions, cost modules, curves, rate tables, factors, tax rules, and indices, maintained by PadSpec. Every entry carries its sources and a verified or practice tag, and the practice entries say which design partner still needs to confirm them.

Your firm's overlay

A firm entry with a core entry's code replaces it; a firm curve can replace one size band of a core module while the module stays core. Sizing margins, vendor preferences, basin practice, tag classes and pipe classes, crew rates and cost curves: authored once by your senior engineers, inherited by every project.

The project's overrides

An engineer who disagrees with a line on one project overrides it there, with a written justification that becomes part of the record. Resolution order for any value: the project, then the firm, then the core. Every output records which layer supplied each decision.

Authoring discipline

Built so a library owner can trust what the firm runs on.

Draft, preview, activate

Firm content is written as drafts: a shadow of a core entry, a new entry, a spreadsheet import, or a calibration proposal accepted from closed projects. A draft prices and draws nothing until it is previewed against the firm's open work and activated.

A second reviewer when you want one

With the setting on, the author of a draft cannot activate it; another admin must. The same rule covers design rules, drawing conventions, and cost entries.

Immutable snapshots

Activation freezes a snapshot. Every spec version names the rule snapshot that drew it; every estimate version names the cost snapshot that priced it. Issued deliverables never move when the library changes; the next generation picks up the change and the history shows the delta.

Your content stays yours

Export the firm's library in the import layouts, with every estimate version, at any time. The core seed is revised by PadSpec and never overwritten by a firm; a firm's overlay is never read by another tenant.

Spec, draw, and price your next pad in an afternoon.

Bring a facility from your basin. We will run it end to end: the sized equipment list, the P&ID set issued for review, and the Class 4 estimate with its basis, with your firm's practice as the overlay. Create an account or book a walkthrough.