Resources

What is an intelligent P&ID?

What the term means for an engineer, and how to get one.

Comparisons of this kind usually run on adjectives. These are five questions you can put to a drawing you already have, this afternoon.

Five questions, answered by a CAD drawing and by an intelligent P&ID
Put this to the drawingA CAD drawingAn intelligent P&ID
How many DN100 gate valves are on this sheet?Count them by eye, or trust the last count.A query over the elements and their attributes.
What feeds this tank?Follow the line across the sheet yourself.Connections are directed, so upstream is a traversal.
Swap a pump for a bigger one.Erase, redraw, then find every other sheet it is on.Change the element; the sheets are views of it.
Where did this bill-of-materials line come from?Someone typed it. The link is in their head.The line carries the id and tag of its element.
What do you own at the end?A file, and whoever can open it.A structure the drawing is one view of.

The short answer

A P&ID records two things: what a plant is made of, and how it is connected. The vessels, pumps, valves and instruments; the lines between them; and the tag that names each one.

On a CAD drawing that record lives in the eye of the reader. The file holds lines, arcs and text. A pump is a group of strokes a person recognises as a pump, and the tag beside it is text that happens to sit nearby. Nothing in the file knows the two belong together, or where the line leaving the pump arrives.

On an intelligent P&ID each of those is an object. The pump is an element with its own identity, a tag and a set of attributes. The line is a connection with a direction, a source and a target. The sheet you look at is a view of that structure rather than a picture kept alongside it.

That is the whole distinction. Everything sold on top of it — quantities that count themselves, registers that cannot disagree with the drawing — follows from it.

What makes an element “intelligent”

Four properties. None of them is a feature anyone sells; they are the shape of the data, and everything else is downstream of them.

It has an identity, and a tag that is not just textAn element carries its own id, the symbol definition it was placed from, and an equipment tag held as a field on the element — not as a label that happens to be drawn next to it. Move the symbol and the tag is still its tag.
It carries attributesEach instance holds its own property map — size, material, duty, whatever the discipline needs. Two valves placed from one symbol are two different objects with two different sets of values.
It is connected, and the connection knows which way it runsA connection is a directed link from a port on one element to a port on another, carrying its own line type and line tag. Held together they are a graph, which is why "what is upstream of this" becomes a question the model can answer instead of something you trace with a finger.
What is generated from it can point back at what it came fromBecause every element has an identity, anything derived from the model can record which element it came from. A bill-of-materials line carries the id and tag of the element that produced it; a generated datasheet records the simulation run its process figures came from.
A Component Library screen reading 2,159 total symbols, 67 categories and 466 enabled symbols, above a table in which every symbol definition carries a name, a subcategory, an enabled or disabled status, a property count, a port count, a size in grid units, the library it belongs to and a shape id.
An element that carries attributes

Every symbol definition in the catalogue carries a property count, a port count and a size in grid units. Place one twice and you have two objects with two sets of values — not two copies of a picture.

A Revision Comparison dialog comparing Rev B with Rev C. It reports "+2 added, -0 removed, ~0 modified, 0 moved" and carries tabs for Components, Properties, Interface Points and Metadata; the Components tab lists two rows, each a Node, named elem-pump-005 and elem-valve-006 and marked "added".
A drawing that knows what changed

Comparing two revisions returns elements, not pixels: two nodes added, named by their own ids, with separate tabs for properties and interface points. A drawing made of lines can only tell you that the picture is different.

The phrase you will hear, and what it is worth

Vendors call this a digital source of truth, and the phrase has one honest meaning: the drawing is not a document kept alongside a database and reconciled with it, it is a view of that database.

What it never says is how much of the plant is in there. That is the question worth putting to anyone who uses it, ours included — which elements carry attributes, which deliverables are derived from them, and which are still typed by a person. Ask for the second list.

What you get for the extra discipline

Structuring a drawing costs more up front than drawing it. These are the four things the structure pays for, each narrowed to what the software actually does today.

Quantities that are derived rather than typedA bill of materials is generated from the elements on the drawing, and re-generated when the drawing is saved — about half a minute behind the last edit, not instantly. Nothing is re-keyed, so the drawing and the bill cannot quietly diverge.Bill of materials
A tag register you export rather than maintainBecause the tags are fields and not text, the register is a read over the model. It exports as RFC-4180 CSV with the spreadsheet-formula guard applied.P&ID editor
Studies worked against the model, not against a printoutHAZOP, LOPA, SIL, FMEA and DSEAR run in the same place as the drawing, and an action can be linked to the model component it applies to. Setting up the node list is still engineering work — nothing extracts nodes from the drawing for you.Safety studies
A flowsheet compiled from the drawingFor wastewater processes the drawing compiles into a simulation model: process areas become units and connections become streams, with a record of which drawing the model came from.Simulation

Two ways to end up with one

Draw itPlace from a symbol library filed by standard — 2,660 symbols, bucketed as BS 1553, ISA-5.1, ISO 10628, PIP and IEC — then tag and connect. What you place is the object; there is no second step that converts a drawing into a model.
Import what you already haveErgoPlanner accepts PDF, PNG, JPG, TIFF, BMP, DXF and DWG. CAD files are mapped deterministically; recognition of scans and PDFs is a preview that proposes elements, and an engineer accepts, adjusts or rejects each proposal before anything is placed. Detection is a proposal, not a result, and the review step is not a formality.
raw geometryproposals??your reviewmodelP-101rejected: not placed
  1. Upload
  2. The pipeline proposes
  3. You accept or reject
  4. Placed in the model

One thing to know before you plan a round tripDWG comes in and does not go out. Sheets export as PDF, SVG or PNG, and as DXF for one sheet or a whole set. There is no DWG writer.

Where to go from here

The fast way to settle whether any of this is real is to look at the editor. The slower way is to read what each part of it does, and what it does not.