How it works

A worked example: the hydrotest procedure.

A package of scanned P&IDs, a line list, scope appendices, design specifications, a Primavera schedule and vendor data. The deliverable is a hydrotest procedure for one system. This is what EDS does with it.

Step 1

Ingest and catalogue.

  1. 1

    Upload

    The package is stored unchanged. Each file is fingerprinted, paginated and typed, and duplicates or superseded revisions are flagged rather than resolved silently.

  2. 2

    Classify

    Each document is classified: P&ID, line list, instrument index, specification, contract appendix, schedule. Confidence is recorded with the class.

  3. 3

    Queue

    Processing is queued work, resumable per page, so a 400-page scanned package can be processed incrementally and partially retried.

Step 2

Interpret the drawings.

DWG-1201 Rev C3 - Condensate Stabilisation Unit 1242 recognised6 to review2 conflicts
PTLTFTV-1210E-1215P-1201AP-1201BD-1208E-1216

What is recognised

  • Equipment and instrument tags
  • Line numbers, sizes and classes
  • Valves and inline items
  • Title block and revision block fields
  • Connectivity between items

Uncertainty is kept

Low-confidence objects enter the verification queue. Nothing is promoted to a register because it looked probable.

Step 3

Assemble the deliverable from verified records.

Required inputs

The checklist is derived from the deliverable type, discipline, contract and what the project holds: system boundary, line schedule, test pressure basis, hold points.

Grounded content

Each generated statement carries its citations.

LST-0045 Rev B p.12

Gaps that block

With no approved pressure basis, the procedure can still be drafted - but formal approval is blocked until an authorised reviewer resolves it.

Approval blocked

Step 4

Review, approve, issue.

  1. 1

    Check and review

    Internal check, then interdisciplinary review, then client review where the contract requires it. Comments attach to sections and to individual assertions.

  2. 2

    Approve

    Attested approval by a named approver who holds that capability. Approval rights are never a side effect of being a project administrator.

  3. 3

    Issue

    An editable DOCX and a controlled PDF, with revision history, transmittal record and a complete audit trail.

Run it against your own package.

The fastest way to judge EDS is to give it a real unit package and look at what it cites.