Engineering knowledge graph

Every entity the project holds and what joins them, with the reason for each edge.

Demonstration project - no figure here describes a real facilityChanges are not saved

Why

Node and edge counts are computed from the project's own records. No edge here was inferred from drawing geometry.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

Documents

Assets

Hierarchy nodes

Requirements

Deliverables

Edges, by what they rest on

Only an edge from a reading is fixable by reprocessing.

Edges by provenance
Edge	Count	Rests on	Fixable by
Document to asset	131	a reading, with a parser and a confidence	reprocessing the document
Asset to hierarchy node	100	a placement somebody recorded	a person changing the placement
Deliverable to requirement	12	a requirement analysis somebody accepted	a person revising the analysis
Deliverable to source document	20	an input checklist somebody satisfied	a person adding or removing an input

One neighbourhood at a time, with the reason for each edge.

Neighbourhood of M-1201A
Edge	To	Why
read from	ZRF-PID-1201	P&ID - Condensate Export Pumps and Discharge carries this tag
read from	ZRF-SLD-6001	Single Line Diagram - Utilities MCC carries this tag
read from	ZRF-DS-P-1201A	Equipment Datasheet - Condensate Export Pump P-1201A carries this tag
sits in	U-12	physical placement
commissioned in	SYS-12-01	commissioning breakdown
driven by	P-1201A	the driver named in P-1201A's own attributes
on line	C-60101	the "to" field of C-60101 in the cable schedule

Condensate export pump A motor

Each value as the register holds it.

P-1201AStated
A driver named in the item's own attributes: the driver named in P-1201A's own attributes
C-60101Stated
Both appear on the same line in a register: the "to" field of C-60101 in the cable schedule

Only what a document states, or two documents imply.

No requirement the project holds names this tag.

Requirements that name this tag.

Machine-read, not verified

Asset

Counts and a neighbourhood, not a cloud

Every asset in the graph is named by a document the project holds.

Connectivity inferred from lines meeting on a drawing. A crossing is not a connection.
Edges between assets that merely appear on the same sheet. Drawing two items together says little.
A confidence on a human decision. A recorded placement is not a reading.