Large-model publishing
Build rmodel from very large Smart3D plants and deliver 3D Tiles for the web — with attributes, hierarchy, and pick metadata, not mesh-only conversion.
Product
S3DX
Publish large models together with spatial context.
S3DX builds an inspectable intermediate (rmodel) from Smart3D databases and publishes 3D Tiles, NWC/NWD, and Spatial Graph so web, Navisworks, and review workspaces share object identity.
The current shipped flow follows the user guide: Connect → Extract → Publish → Inspect. v2 (SAT/B-Rep path) is a development line and is not part of 1.x distributions.
Problem
Huge models open — without the spatial meaning review needs.
Geometry alone leaves object identity, hierarchy, spatial topology, and metadata out of review and AI. Full republish-only workflows cannot keep pace with frequent model change.
What it does
Publishes the model and the spatial context together.
S3DX reads Smart3D (MDB/RDB/CDB_SCHEMA and related stores), materializes rmodel, and publishes 3D Tiles and NWC/NWD with the geometry store. Spatial Graph carries objects, hierarchy, links, and spatial relations for resolvers and review surfaces.
- Input: Smart3D project databases (read)
- Intermediate: rmodel · geometry store (inspectable, verified)
- Output: 3D Tiles, NWC/NWD, Spatial Graph, engineering metadata
I/O flow
From Smart3D to tiles, NWC, and graph
Publish only after extract and verification. Invariant failure is not fail-forward.
- 01
Smart3D DB
Connect and plant selection
- 02
Extract
rmodel · geometry (incremental)
- 03
Verify
Invariant checks
- 04
Publish
3D Tiles · NWC/NWD
- 05
Spatial Graph
Hierarchy, relations, topology
- 06
L3D Vue / Navisworks
Review and delivery surfaces
Capabilities
What the shipped pipeline covers
Incremental extract and publish
Re-extract changed objects, continue rmodel from prior results, and rewrite changed tiles. Full reset rebuild is available when needed.
NWC / NWD
Alongside 3D Tiles, publish Navisworks NWC/NWD from the same extract — with selection publish, exclusion rules, and attribute settings.
Spatial Graph
Build the spatial relations and topology review and resolvers need — a spatial context layer separate from geometry delivery.
Inspectability
Stage outputs are SQL-openable; invariants gate publish. rmodel is not authority and is rebuilt when upstream changes.
Relation to Engineering Context
The primary Spatial Context infrastructure.
Spatial Graph from S3DX is what Spatial Resolver uses to select review neighborhoods. Process identity stays with PIDEX; S3DX owns spatial objects, relations, and delivery.
Workflow
User-guide order
- 01
Activate license, then connect the plant folder and SQL Server.
- 02
Run incremental extract or full reset rebuild.
- 03
Publish 3D Tiles or NWC/NWD.
- 04
Inspect objects, attributes, and hierarchy; continue with Spatial Graph.
- 05
Review the same identities in L3D Vue or Navisworks.
Boundaries and authority
What we claim — and what we do not
S3DX is read-only extract-and-publish infrastructure. It does not write back to Smart3D and holds no process meaning or approval authority.
| Layer | Role |
|---|---|
| Smart3D source | Design authority — S3DX reads only |
| rmodel / geometry store | Inspectable intermediate — not authority |
| 3D Tiles · NWC/NWD | Delivery and review artifacts |
| Spatial Graph | Product output for spatial relations and topology |
| v2 (dev) | Next SAT/B-Rep path — not a shipped distribution |
- No unlimited model size, all-CAD, or unverified performance claims.
- No GA / production-ready assertion.
- Smart3D MCP is not advertised as a public product capability.
- v2 features are not described as part of the current shipped pipeline.