Evidence SVG
One SVG per drawing with observed geometry, provenance and generation metadata, and embedded semantic data. Traceable drawing evidence — not a screenshot.
Product
Turn P&IDs and engineering records into trustworthy process context.
PIDEX reads a SmartPlant P&ID project read-only and emits engineering artifacts that engineers and AI agents can inspect, review, and publish from the same evidence.
Currently in Alpha evaluation.
Problem
Drawings, tags, and lists can exist apart from shared identity, connectivity, and provenance. Filling gaps with filenames or on-screen proximity creates topology without authority.
What it does
PIDEX collects Oracle schemas and drawing geometry from Smart P&ID read-only, then emits observed drawing evidence, DEXPI-based semantic artifacts, Engineering Identity / Rich Tag Graph, and lists into a result folder. Missing values stay missing; they are never guessed.
I/O flow
Authoritative sources create facts; evidence artifacts carry them; Workspace only gathers work context. Final publication authority stays with Engineering Publication.
SmartPlant P&ID
Read-only ingestion
Evidence SVG · DEXPI 2.0 XML
Drawing and semantic evidence
Engineering Identity / Rich Tag Graph
Topology authority
Lists · Result Explorer
Inspect outputs
Workspace · CRS
Task and comment context
Engineering Publication
Project PDF/A-4f
Capabilities
One SVG per drawing with observed geometry, provenance and generation metadata, and embedded semantic data. Traceable drawing evidence — not a screenshot.
Project and per-drawing DEXPI 2.0 XML with DEXPI-aligned vocabulary for semantic/process evidence. Normalization and exchange only — not DEXPI certified or compliant claims.
Exact engineering identities and source-backed relations. Topology authority lives here. TAG strings, SVG proximity, and viewer heuristics do not create topology.
Browse list outputs and the result folder’s drawings, records, data, and review tools. Engineering Graph visualization is a derived view of the Rich Tag Graph.
Workspace is drawing- and object-centred work context. CRS binds comments, annotations, and identity links to a generation. It has no approval, e-signature, or publication authority.
The sole final publication authority for project PDF/A-4f with associated files. Workspace and CRS do not emit per-drawing or per-comment final PDFs.
Relation to Engineering Context
Engineering Identity and the Process Rich Tag Graph from PIDEX supply the process-side authority Tag Resolver uses with 3D model context. Spatial meaning belongs to S3DX’s Spatial Graph; PIDEX does not redefine it.
Workflow
Configure the Smart P&ID Oracle connection in setup (read-only).
Select drawings, run generation/publication, and produce a result folder.
Inspect Evidence SVG, DEXPI, Graph, lists, and verification/history in Result Explorer.
Gather drawing/object context in Workspace; use CRS for comments and annotations when needed.
Publish the project PDF/A-4f through Engineering Publication.
Boundaries and authority
PIDEX never edits the source Smart P&ID project. Topology authority is the Rich Tag Graph; semantic/process evidence is DEXPI XML; final publication is Engineering Publication only.
| Layer | Role |
|---|---|
| Rich Tag Graph / Engineering Identity | Topology and engineering-identity authority |
| DEXPI 2.0 XML | Semantic/process evidence (normalize/exchange). No certified/compliant claim |
| Evidence SVG / Drawing Evidence | Observed drawing and geometry evidence |
| Engineering Graph visualization | Derived view only — not authority |
| Workspace | Task/context only — not engineering authority |
| CRS | Review/comment/annotation workflow — no approval or e-signature |
| Engineering Publication | Sole final publication authority (PDF/A-4f) |
| Engineering Record | Provenance, integrity, generation, currentness — not approval |