Three steps from deliverable
to traceable finding register.
Owner’s-engineer AI reviews for oil & gas deliverables — traceable findings, comment registers and human-supervised escalation in hours. Here is exactly what happens inside the black box.
Drop it in. Get findings back.
You drop the deliverable.
Upload your P&ID, isometric drawing, equipment datasheet, HAZOP register, or spec section. PDF for drawings and multi-page deliverables (plotted from DWG or native), XLS for registers and structured exports. Redacted documents work fine — engineers upload what they'd send to a client.
SpecSense runs codified CEng checks.
The discipline classifier identifies the document type and routes it to the correct check sequence. Each check runs in order — the same sequence an Owner's Engineer would follow, encoded into logic.
You get traceable findings with human sign-off.
A Chartered Engineer triages severity, discards false positives, and signs the comment register. You receive a PDF/CSV register with code citations, drawing locations, and recommended actions. Hours, not weeks.
The review pipeline, stage by stage.
Every deliverable passes through the same codified sequence. No stages are skipped. No stages run without the prior stage’s output as input.
OCR / parse
The document is extracted into structured text, tables, and drawing geometry. Page layout, tag callouts, and table structure are preserved. Handwritten annotations and stamp overlays are flagged so nothing gets missed.
Discipline classifier
The document is classified: P&ID, isometric, equipment datasheet, HAZOP register, line list, spec section, or other. The classifier selects the appropriate check library and cross-reference set.
Check sequence
The discipline-specific check sequence runs. Checks are ordered: prerequisite data checks first, then primary engineering checks, then cross-document consistency checks. The order is codified, not arbitrary.
Code citation
Every flagged item is matched to a code clause. ASME B31.3, ASME B16.5, API 520, API 521, IEC 61511, ASME BPVC VIII-1, NACE MR0175 — the relevant edition and clause number. No generic references.
Severity scoring
Candidate findings are scored Major, Minor, or Info based on safety consequence, code compliance status, and rework cost. Scoring is discipline-calibrated, not generic.
CEng review
A Chartered Engineer reviews every candidate finding. False positives are discarded. Major findings are annotated with escalation recommendations. The engineer signs the register.
Export
You receive a PDF finding register, a CSV comment register in your template format, and an audit trail log. Every finding links back to the pipeline stage that generated it.
Every finding cross-referenced against YOUR standards, not just public codes.
SpecSense ships with a baseline of public codes — ASME B31.3, API 610, IEC 61511 and their discipline equivalents. But real projects run on client-specific overrides: a Shell DEP that supersedes ASME, an Aramco SAES that tightens API, an ADNOC AGES that mandates a specific valve type. Upload them once and every finding from that point forward cites your document, not a generic clause.
On the marketplace (pay-per-review), attach up to five reference documents at upload time — no account needed. In the B2B portal, your document library lives under the project and is available to every reviewer assigned to it. Either way, the reviewer sees your standards indexed and searchable before the first check runs.
Files are retained for 30 days, then hard-deleted from our servers. The audit trail (document type, count, upload date) is kept for the project record. Your IP does not persist beyond the review window.
📚 Every finding cross-referenced against YOUR standards, not just public codes.
Shell DEP, Aramco SAES, ADNOC AGES, BP GIS, project PMS, HAZOP register — upload the documents that govern your project and every finding traces back to the exact clause in the document you supplied.
Supported document types
- 1Company standard— Shell DEP, Aramco SAES, ADNOC AGES, BP GIS, etc.
- 2Project specification— PMS, line list, tag philosophy
- 3Basis of Design— Design envelope, governing constraints, project philosophy
- 4Owner procedure— Operating procedures, maintenance practices, commissioning requirements
- 5Standards override matrix— Project-specific deviations from base codes
- 6Related drawing— HAZOP register, C&E matrix, SIL determination report
Codified checks per input type.
Different deliverable types get different check sequences. A P&ID review is not the same workflow as a HAZOP register review.
P&ID
Piping & Instrumentation Diagrams
- Line class consistency vs. line list
- Spec breaks — correct class transitions at battery limits
- Valve types against service fluid and pressure class
- Relief valve presence and discharge routing
- Instrument tagging format against ISA 5.1
- Utilities cross-connections flagged
- Shutdown logic consistency against cause-and-effect matrix
Isometric
Piping Isometrics
- Flange class vs. design pressure at service temperature
- Wall thickness vs. design pressure + corrosion allowance
- Thermal expansion provisions — loops, offsets, guides
- Support spacing against allowable span tables
- Material call-out against line class specification
- Weld joint factor applied to seamless vs. ERW pipe
- PWHT requirements triggered by material and thickness
Datasheet
Equipment Datasheets
- Design pressure and temperature vs. vessel code margin
- Material selection for service fluid, H₂S content, and temperature
- NACE MR0175 compliance for sour service
- Nozzle schedules — size, rating, and position completeness
- Nameplate data consistency vs. process datasheet
- Inspection category and test pressure derivation
HAZOP
HAZOP Registers
- Action closeout status — open actions with no assigned owner
- Recommendations with no cause-and-effect matrix reference
- SIL targets recorded but not referenced in SIL calculation
- Consequence descriptions without mitigation safeguard
- Deviations missing credible initiating cause
- Independent Protection Layers (IPLs) credited without validation
What a finding looks like.
Every finding is traceable — code clause, drawing location, severity, and recommended action. No vague commentary. No ambiguity about what needs to change.
Flange class vs. design pressure — derated for service temperature
Where the code clauses come from.
Buyers always ask this in the first ten minutes. Here is exactly what SpecSense checks against — no fudging, no marketing gloss.
Your project spec is the source of truth.
At project onboarding you upload the client spec bundle — ADNOC ES, Saudi Aramco SAES, Shell DEP, TotalEnergies GS, Equinor TR, or your company standard. SpecSense builds a per-project RAG index against that revision. Every finding cites the exact clause, edition and paragraph from the document you supplied.
- Client-supplied specs override base code where they conflict
- Revision pinned per project — no silent updates mid-review
- Full evidence chain: finding → clause → page → uploaded PDF
Base codes: current AI baseline today, licensed library Q4 2026.
For public codes referenced by your spec — ASME B31.3, API 610, ASTM A106, ISO 15156 / NACE MR0175, DNV-OS-F101, IEC 61511, EEMUA 159 and similar — v1 uses the model’s baseline knowledge to draft findings. Full licensed digital libraries with per-clause traceability are on the enterprise roadmap for Q4 2026, priced into that tier because the annual publisher licences are material.
What this means in practice: any base-code citation in a draft finding is flagged for CEng review before release. The CEng validates against the current edition before the comment register is signed off. No unverified base-code claim leaves the portal.
CEng sign-off is the last line, not the AI.
Every Severity-3+ finding routes to a chartered engineer before it appears in the register you receive. The AI drafts; the CEng defends. That’s the layer that lets a Principal Engineer put a SpecSense register in front of a client audit and have it hold.
- Named CEng on every deliverable
- Findings you can defend clause-by-clause in review
- Indemnity structure documented in the enterprise MSA
A note for the technical buyer: we are deliberately not claiming a live subscription to every publisher at launch. Buying ASME, API, ASTM, ISO and DNV digital libraries at enterprise seat count costs six figures a year, and we’d rather carry that cost into the enterprise tier once we’re certain of the volume. In the interim, your uploaded project spec is authoritative and every base-code citation is CEng-checked. If your procurement team needs a written statement of standards handling for a pilot, ask on the intro call — we send it as a one-pager.
See the pipeline run on your deliverable.
48-hour supervised pilot. Chartered-engineer sign-off. Full comment register.