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.
| 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 |
What touches 12-CD-1202-150-A1A
One neighbourhood at a time, with the reason for each edge.
| Edge | To | Why |
|---|---|---|
| read from | ZRF-PID-1201 | P&ID - Condensate Export Pumps and Discharge carries this tag |
| read from | ZRF-PID-1202 | P&ID - Condensate Export Metering carries this tag |
| read from | ZRF-REG-LL-001 | Piping Line List carries this tag |
| sits in | U-12 | physical placement |
| commissioned in | SYS-12-02 | commissioning breakdown |
| tested in | ZRF-TP-001 | test pack membership |
| same test pack (implied) | P-1201A | both are in ZRF-TP-001 |
| same test pack (implied) | P-1201B | both are in ZRF-TP-001 |
| same test pack (implied) | V-1210 | both are in ZRF-TP-001 |
| same test pack (implied) | HV-1201 | both are in ZRF-TP-001 |
| same test pack (implied) | HV-1202 | both are in ZRF-TP-001 |
| same test pack (implied) | 12-CD-1201-150-A1A | both are in ZRF-TP-001 |
| same test pack (implied) | 12-CD-1203-100-A1A | both are in ZRF-TP-001 |
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.