1D / 2D / 3D integrated review
Move across data grids, P&IDs, and 3D models inside one project to find the same object. Not a 3D-only product.
Product
L3D Vue
An Engineering Context Workspace across 1D, 2D, and 3D — with shared identity.
L3D Vue joins graphs, lists, P&IDs, and large 3D models in one workspace. It is not a fast 3D viewer; it is the work surface where humans and AI continue design review on the same object identities and relationships.
Problem
Review jumps across drawings, models, and data — and identity breaks each time.
3D alone misses process meaning; P&ID alone misses space. When the same tag looks like a different object in each tool, review evidence cannot stay in one place.
What it does
Gathers Engineering Context into one browser work surface.
L3D Vue binds a 1D data tool, 2D P&ID view, and CesiumJS-based 3D view into one project context. Selection, highlight, and context sync keep the same object across dimensions, and review interactions can flow into Evidence and CRS support.
- 1D: engineering metadata, lists, relationship navigation
- 2D: P&ID / drawing view with object highlight
- 3D: large engineering models (3D Tiles) explore and select
- Sync: shared identity and selection context across dimensions
I/O flow
How context arrives in the workspace
L3D Vue does not redefine sources of truth. It consumes context and deliverables from PIDEX, S3DX, and Emit.
- 01
PIDEX Process Context
Identity, P&ID, graph
- 02
S3DX Spatial Context
Tiles, Spatial Graph
- 03
Emit deliverables
Drawings / Evidence when needed
- 04
L3D Vue Workspace
1D · 2D · 3D synced review
- 05
Review / Evidence
Findings · viewpoints
- 06
CRS support
Comment disposition — not approval
Capabilities
What the workspace actually connects
Identity sync
Align selection and highlight across dimensions so a target chosen on a drawing continues as the same object in the model — by project identifiers, not filename guesses.
Relationship graph navigation
Follow 1D relations and graph views to widen review scope. The graph is a navigation surface; it does not replace source topology authority.
Human + AI review context
Aim for a work surface where people and agents share objects, revisions, and relationships. Agents may query and analyze context to assist review; authorized engineers make final decisions.
Evidence · CRS workflow support
Carry findings, annotations, and viewpoints into Evidence flows and CRS comment disposition. CRS is not approval or e-signature.
Relation to Engineering Context
A review surface that consumes context.
PIDEX owns Process Context; S3DX owns Spatial Context. L3D Vue opens that context across 1D·2D·3D and hosts Evidence Snapshot and CRS support.
Workflow
A typical multi-discipline review path
- 01
Open project context (1D·2D·3D data) in the workspace.
- 02
Find targets by tag, object, or drawing and align selection across dimensions.
- 03
Follow relations and spatial neighborhoods to set review scope.
- 04
Capture findings and viewpoints as Evidence; hand off to CRS when needed.
- 05
Authorized engineers dispose comments and make follow-on design decisions.
Boundaries and authority
A work surface — not a redefinition of truth
L3D Vue does not redefine Process or Spatial sources. Internal codebase names are not the public brand.
| Layer | Role |
|---|---|
| PIDEX / S3DX | Process and Spatial Context sources |
| L3D Vue | Human + AI Engineering Context Workspace |
| Evidence Snapshot | Review evidence package — not approval substitute |
| CRS | Comment disposition support — no approval or e-signature |
| AI / Agent | Query, analyze, assist review — no final decision authority |
- Not positioned as a “fast 3D viewer” alone.
- Internal repository or binary names are not public branding.
- WebMCP is not a headline capability.
- No CRS approval authority or sole ownership of Evidence.