Skip to content
Product data & engineeringPumps & ValvesWater & EnvironmentMachinery & Plant EngineeringWaste & Recycling+3

Check P&IDs against equipment lists and piping classes

demi reads tags, lines and valves from every P&ID, scans included, and reports each conflict with the lists and piping classes.

Today

The P&ID, the equipment list, the instrument list, the valve list and the piping classes are maintained by different people in different files. For existing plants the P&ID often exists only as a scan or as a PDF with hand-written changes. Conflicts such as a wrong nominal size, a valve with too low a pressure rating or a missing instrument show only when the wrong parts arrive on site.

An example

Orvelon is extending the mixing plant for its alkaline cleaner AR 240. The P&IDs of the existing plant exist only as scans from the nineties and as PDFs with later changes. The agent reads 9 sheets with 41 lines, 96 instruments and 133 valves and reports 12 conflicts, among them: the line from caustic pump P-203 to mixing vessel B-201 is DN 50 on the P&ID and DN 65 in the line list. Two ball valves are listed at PN 10 while the piping class requires PN 16, and four instruments are missing from the instrument list. Process engineering settles everything before any valves are ordered.
Fictional company, typical workflow.

Your data, wherever it lives

Today P&IDs sit in the CAD system, for older plants only as PDFs or scans, equipment, instrument and valve lists as spreadsheets on the network drive, piping classes in the DMS and purchase orders in the ERP. demi reads and understands these documents, scans included, and links every tag to its row in every list, with your access rights. The AI then checks a sheet in minutes instead of hours, and your process engineers decide on every correction.

Where the data lives today

  • CAD & drawings
  • PDFs
  • Scans & paper
  • Office files
  • Folders & drives
  • DMS & archive
  • ERP
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    Data sources in this case: CAD, P&IDs as PDFs and scans, lists as spreadsheets, the DMS and the ERP with the purchase orders. demi replaces nothing and turns each P&ID into a list of every tag, line and valve, linked to its row in the equipment, instrument, valve and line lists and to the piping class that applies to the line.

  2. 2 · PermitPermission Layer

    P&IDs and lists are visible to process engineering, piping, instrumentation and project management. The responsible process engineer decides which side of a conflict is right; demi changes neither drawing nor list on its own, and every decision is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads symbols, tags, nominal sizes and piping classes from the P&ID, scans included, and compares them line by line with the lists. A fixed rule set checks each line against its piping class, such as material, pressure rating and size range. Whatever it cannot read for certain on a scan, it marks for review instead of guessing.

How it runs

  1. 1

    The P&IDs come from CAD, as PDFs or as scans, together with the lists and piping classes.

  2. 2

    The agent reads every sheet and builds a list of all equipment, lines, instruments and valves.

  3. 3

    It matches them with the equipment, instrument, valve and line lists and checks every line against its piping class.

  4. 4

    Each conflict comes with sheet, position and the two entries that disagree.

  5. 5

    Process engineering decides for each conflict which side is right and corrects the P&ID or the list.

What changes

  • Conflicts found at the desk, not on site

  • The right parts on the first order

  • Old P&IDs become searchable and usable

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+108 hfreed per year

Assumptions and calculation

demi reads every P&ID and matches it with lists and piping classes; you decide on each conflict.

2 h → 1.4 h per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

15 P&ID sheets × 2 h × 30% × 1.0 (manual) × 12 months = 108 h

Value per year, before demi costs

Freed per year+108 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$7,020

gained per year

108 h ÷ 1,760 h per role = 0.1 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Can demi read scanned P&IDs?

Yes. The agent recognizes symbols to ISO 10628, tags, nominal sizes and line numbers on scans and on PDFs without data behind them. It marks uncertain spots, and you confirm or correct them once. From then on the old P&ID is as searchable as a new one.

Which lists does the agent compare with?

With all the ones you connect: equipment list, instrument list, valve list, line list and piping classes, and the purchase orders in the ERP if you wish. That way it also shows when an ordered valve does not fit the piping class of its line.

Does demi change P&IDs or lists?

Not on its own. The agent shows each conflict with both entries; the responsible person decides which one is right and corrects it in CAD or in the list. If you wish, demi carries the correction into the list after release. Every decision is recorded.

Does this help with changes to existing plants?

Especially there. In older plants the P&ID and the lists have often drifted apart over the years. demi shows before the revamp where the documents do not match, so the site walk can check those points instead of surveying everything again.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases