Menu

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

25

Assets

50

Hierarchy nodes

20

Requirements

9

Deliverables

8

Edges, by what they rest on

Only an edge from a reading is fixable by reprocessing.

Edges by provenance
EdgeCountRests onFixable by
Document to asset131a reading, with a parser and a confidencereprocessing the document
Asset to hierarchy node100a placement somebody recordeda person changing the placement
Deliverable to requirement12a requirement analysis somebody accepteda person revising the analysis
Deliverable to source document20an input checklist somebody satisfieda person adding or removing an input

What touches C-60102

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

Neighbourhood of C-60102
EdgeToWhy
read fromZRF-SLD-6001Single Line Diagram - Utilities MCC carries this tag
read fromZRF-REG-CS-001Cable Schedule carries this tag
sits inU-12physical placement
commissioned inSYS-12-01commissioning breakdown
on lineMCC-6001the "from" field of C-60102 in the cable schedule
on lineM-1201Bthe "to" field of C-60102 in the cable schedule

Pick an entity

Counts and a neighbourhood, not a cloud

Nodes with nothing behind them

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

What is deliberately absent

  • 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.