Spotlight: Cesium, and a snap back to the source BIM
Cesium’s second design-model preview versions BIM uploads, flags element changes, and snaps to original geometry instead of the streamed tile.
Yesterday’s unused story was a measurable 3D record from a phone walk. The leftover from the same conference week is a viewer change: Cesium’s second design-model preview, posted 16 September.
That is not a new authoring tool. Firms already drop a Revit, IFC or iModel into a web globe and watch it turn into 3D Tiles. The usual waste is what happens next. The stream is a decimated copy. A later issue of the model gets a new asset ID. Nobody can say which pipe moved, and a click on a beam lands on the simplified mesh, not the edge the fabricator used. Cesium’s claim is that the ion copy can now keep versions, report element changes, and snap back to the source geometry.
What actually changed
June’s preview was the intake: tile common design formats in Cesium ion and query metadata through the Asset Elements API. The 16 September note is about the model after it is in the globe.
Versioning is the file-handling change. A re-upload does not overwrite the tiled asset. Ion creates a new 3D Tiles asset and hangs it on the same BIM/CAD Database. The database ID stays put. Older revisions remain available. That is how you stop hard-coding a tileset ID that dies on the next issue.
Change detection compares two related tilesets and classifies each element as inserted, updated or deleted. The September post says developers can isolate or zoom to those elements, including items that are internal or hidden. Cesium’s own sample paints inserts lime, updates orange and deletes red. That is a visual delta of two tiled issues, not a coordinated clash report.
Snapping is the sentence that matters for review. Runtime tiles are simplified so they stream. Cesium is explicit that this is a poor basis for measurement, clash or exact placement. The new snap service queries the original source geometry and snaps to edges, vertices and midpoints. Cesium calls that millimeter-level. Treat the figure as a viewer claim until you close it on project control. Measurement widgets that use the same snap are listed as later in 2026, not in this drop.
Around that sit smaller pipeline fixes. A CRS Search API lets an app pick a valid coordinate system when an asset is created. GPU clipping now handles polygons with holes and can skip fully clipped tiles. Ingestion filters can drop meshes, lines or text you do not need in the stream. New tilesets include the July EXT_mesh_primitive_edge_visibility extension so CAD-style edges show without z-fighting.
Cesium says the work is built on Bentley technology, including the iTwin Platform and iModels. Docs also accept models added from Bentley Infrastructure Cloud. Early users named in the post are engineering teams reviewing options in geospatial context and state departments of transportation stitching systems onto one canvas. That is a digital-twin review seat, not a replacement for the authoring model.
Still later this year, Cesium lists automated footprints, a georeferencing wizard, richer element queries, hierarchy filters and the measurement widgets. Do not write those into a live method yet.
What a BIM or VDC lead should do
Do not move coordination into a globe because the tile can now snap. Keep issue ownership where it already closes. Use this where the pain is real: a city-scale or corridor review that must sit on terrain, and a weekly model drop that used to mean a new URL and a manual overlay.
If the firm already publishes design models to Cesium ion, pick one non-sensitive pair of issues. Upload the later file as a revision on the same BIM/CAD Database. Then ask four questions: does the database ID stay stable; does change detection list the elements you already know moved; does a snap land on the source edge, not the decimated mesh; and does the model sit on the CRS you already issue.
If the answers are yes, the twin canvas can stop being a screenshot of last month’s export. If a hidden duct does not appear in the delta, keep the coordination model as the record.
Start with Cesium’s 16 September note and the versioning and change-detection docs.
Frequently asked questions
What did Cesium announce?
A second technology preview, posted 16 September 2026, for design models already tiled in Cesium ion. It adds revision uploads, a Change Detection API, snapping to source geometry, GPU clipping, a CRS Search API, ingestion filters and CAD-style edges on new tilesets.
Does this replace Navisworks or a CDE clash set?
No. Cesium is a geospatial viewer and ion pipeline. The preview helps keep a digital-twin canvas current and show what changed between two tiled revisions. Coordination, issue ownership and a written tolerance still live in the tools you already run.
What models can I put through it?
Cesium’s docs describe models tiled with the BIM/CAD Tiler with Database, or models added from Bentley Infrastructure Cloud. The September note says the pipeline is built on Bentley technology, including the iTwin Platform and iModels.
Can I measure off the snap today?
Not as a finished tool. Cesium says the snap is the foundation for measurement widgets later in 2026. What shipped in this preview is the snap to edges, vertices and midpoints against source geometry.