P&ID sheets in.
Checked lists out.

For a process-plant team, we built software that reads drawings on their own machines and builds the line, valve and equipment lists, with every row traced back to its place on the sheet. The instrument index is a target, not yet extracted.

skarowP&ID list automation[PROJECT NUMBER] / Drawings / [DWG-0000-001]Issue list[INITIALS]
Line list[PROJECT NUMBER]-LL-[SEQ] · REV [B]verified ·flagged ·conflict
PITI[V-201][P-101][E-301][T-401][P-102][V-202]2"-P-1001-A1A2"-CW-1003-B2CTO [HDR-01]6"-P-1006-A1A3"-P-1002-A1AB4"-P-1004-A1A
Sample line list, illustrative values only
#Line no.FromToSizeSpecStatusNote
0012"-P-1001-A1A[V-201][P-101]2"A1Averified
0023"-P-1002-A1A[P-101][E-301]3"A1AflaggedSize change at reducer, confirm
0032"-CW-1003-B2C[E-301][HDR-01]2"B2Cverified
0044"-P-1004-A1A[E-301][T-401]4"A1AconflictSpec break A1A / B2C not shown
0056"-P-1006-A1A[T-401][P-102]6"A1Averified
0062"-P-1007-A1A[P-102][V-202]2"A1Averified
0073"-CW-1008-B2C[HDR-01][E-302]3"B2Cverified
0081"-D-1009-A1A[V-202][DRN-01]1"A1AflaggedDrain size below spec minimum
0092"-P-1010-A1A[E-302][T-402]2"A1Averified
0104"-P-1011-A1A[T-402][P-103]4"A1Averified
0112"-N-1012-A1A[P-103][V-203]2"A1Averified
0123"-P-1013-A1A[V-203][E-303]3"A1Averified
0132"-CW-1014-B2C[E-303][HDR-02]2"B2Cverified
0144"-P-1015-A1A[E-303][T-403]4"A1Averified
0151"-V-1016-A1A[T-403][ATM]1"A1Averified
0162"-P-1017-A1A[T-403][P-104]2"A1Averified
Project
[PROJECT NUMBER]
Client
[DEMO CLIENT]
Drawing
[DWG-0000-001]
Drawn
[INITIALS]
Sheet
[01] OF [04]
Issue
[ISSUE PURPOSE]
Rev
[B]
Demo data: a synthetic drawing beside its line list, with verified, flagged and conflict rows and the drawing title block.
Work
01
Deploys
On-prem
Input
P&ID PDF · text layer · vector
Output
Lists · reports · DEXPI-style (target)
Rev
[A]

The problem

Line, valve and equipment lists are typed up by hand from the drawings, and every revision means checking them again.

What we built
Software that reads P&ID PDFs on the client’s own machines and builds line, valve and equipment lists, with every row traced back to its place on the sheet.
For
a process-plant team
Delivered
On-prem software

How it works

  1. 01

    Input

    P&ID PDFs with a text layer or vector text, plus the client’s line-spec table and tag format.

  2. 02

    Extraction

    Symbols, text and tags, read from the PDF text layer and linework.

  3. 03

    Connectivity

    Lines traced and junctions resolved into a graph of equipment, valves and instruments.

  4. 04

    Validation

    Written rules check each row against the spec. Anything they can’t resolve is flagged for an engineer, not guessed.

  5. 05

    Outputs

    Lists, a connectivity report and a validation report. DEXPI-style export is a target. Same input, same output on every run.

Deliverables

Issued as “P&ID Extracted Lists”: one workbook per drawing set, on the client’s title block, with a cover sheet, contents, revision history and approval block.

Document numberTitleFormat
[PROJECT NUMBER]-LNL-[SEQ]Line List.xlsx · .pdf
[PROJECT NUMBER]-VLV-[SEQ]Manual Valve List.xlsx · .pdf
[PROJECT NUMBER]-EQL-[SEQ]Mechanical Equipment List.xlsx · .pdf
[PROJECT NUMBER]-[LIST CODE]-[SEQ]Instrument IndexTarget.xlsx · .pdf
[PROJECT NUMBER]-[LIST CODE]-[SEQ]Validation Report.xlsx · .pdf

Rev [X]Numbering shown is a sample; client numbering is carried separately as [CLIENT DOCUMENT NUMBER]. [TBC]

TargetInstrument index: a template today, not a list extracted from the drawings.

[DEMO CLIENT] · [PLANT / UNIT]

P&ID Extracted Lists

[PROJECT NAME] — [AREA]

Revision [X] · [ISSUE PURPOSE]

Demo data

Contents

Document numberTitleTabRevision
[PROJECT NUMBER]-LNL-[SEQ]Line ListLine List[X]
[PROJECT NUMBER]-VLV-[SEQ]Manual Valve ListValve List[X]
[PROJECT NUMBER]-EQL-[SEQ]Mechanical Equipment ListEquipment List[X]

Revision history

RevDateDescriptionPreparedCheckedApproved
[C][YYYY-MM-DD][Issued for construction][INITIALS][INITIALS][INITIALS]
[B][YYYY-MM-DD][Issued for review][INITIALS][INITIALS][INITIALS]
[A][YYYY-MM-DD][Issued for internal check][INITIALS][INITIALS][INITIALS]

Approval

RoleNameSignatureDateOrganization
Prepared[NAME][YYYY-MM-DD][ORGANIZATION]
Checked[NAME][YYYY-MM-DD][ORGANIZATION]
Approved[NAME][YYYY-MM-DD][ORGANIZATION]
Document number[PROJECT NUMBER]-IDX-[SEQ]
Client document number[CLIENT DOCUMENT NUMBER]
Prepared for
[DEMO CLIENT]
Client[DEMO CLIENT]
Project name[PROJECT NAME]
Project number[PROJECT NUMBER]
Revision[X]
Document titleP&ID Extracted Lists
Issue purpose[ISSUE PURPOSE]
Date[YYYY-MM-DD]

Replace every bracketed field before issue.

Fig. B · Cover sheet · demo data

On-prem and security

Built for drawing sets that cannot leave the building.

Deployment
Runs on the client’s own servers as a signed Docker image. No cloud account needed. [TBC]
Offline
Works on air-gapped networks. [TBC]
Drawings
Drawings and outputs stay on the client’s network. Nothing is sent to Skarow. [TBC]
Access and audit
Per-project access. Every row change in review is logged with the reviewer’s initials. [TBC]

Status

Built[TBC]The lists are built; the instrument index and DEXPI-style export are targets.

Line list
Built
Manual valve list
Built
Mechanical equipment list
Built
Connectivity and validation reports
Built
Instrument index
Target
DEXPI-style export
Target

Start a project

Have drawings or documents that people re-type into lists by hand? Tell us about them.

or [[email protected]]