INTERNAL REVIEW DRAFT — not for publication. Screenshots are frames lifted from the two SiteView build recordings and two product-owner snips; most need re-shooting at full size before release. Blocks marked IMAGE NEEDED / BLOCKED / DEFERRED are captures that do not exist yet, and blocks marked FOR REVIEW are open questions. Every one of those blocks must be resolved and removed before this article leaves the Temporary section.
Introduction
Capture Intelligence is an AI analysis that runs against every 360-series capture. Gen6 SLAM works out where things are; Capture Intelligence works out what is there.
You do not turn it on and there is no panel to configure. It runs as part of processing, and what you meet in the product are its results.
Note: Capture Intelligence is the name of the engine, not a screen. In SiteView you meet it as a summary on a capture thumbnail and the overview it opens.
The Five Outputs
Five outputs, and they are not all produced at the same granularity. That difference matters when you go looking for a result.
| Output | Granularity | What it gives you |
|---|---|---|
| Summary | per video | A written account of what the capture shows. |
| WIP | per work area | Work in place — what has been built in that area. |
| Safety issues | per image | Safety conditions found in an individual frame. |
| Notable items | per image | Anything else worth a second look, per frame. |
| Custom object locator | per video | Finds and geo-locates the objects your team cares about. |
Custom object locator is the one that needs setting up. It finds and geo-locates custom 3D objects — scissor lifts and other equipment, for example — from 360 video. Training is few-shot: you register each target object with ten to twenty bounding boxes at the initial capture. On every subsequent capture, the objects it detects are created as Notes.
FOR REVIEW — The custom object locator's internal project codename must not appear in any external material. The user-facing term is "custom object locator".
What Capture Intelligence Does Not Produce
Surface-quality findings are not produced anywhere in CupixWorks 5.0. Corrosion, water damage, concrete defects, spills and surface cracks are not a Capture Intelligence output, and they are not available from SmartFilter either: SmartFilter labels what a thing is — floor, wall, duct, column — and carries no surface-quality family.
This is worth stating plainly, because a reader looking for defect detection will otherwise keep opening surfaces in search of it. Confirmed by the product owner, 2026-09-15.
Note: For what SmartFilter does label, refer to the SmartFilter article.
FOR REVIEW — Answered 2026-09-15 and the section is rewritten. Semantic Segmentation carries building-element labels only — twenty of them — and no surface-quality family, so the route this section used to describe does not exist and the launch-plan claim it rested on is the side to correct. Still with development: whether Capture Intelligence ships its own Quality Issues section at 5.0, since the specification gives it one and the build shows only Site Context and Overall Condition (re-asked as A11-1b).
Where You See It
Capture Intelligence has no home screen and, in SiteView, no panel. There is exactly one surface, and it is reached the way you would reach a photograph:
- A capture thumbnail in the ChronoNavigator strip carries a sparkle badge when the analysis found something, and shows its summary inline on the card.
- Show more opens the Capture Intelligence overview — a dated dialog holding the written summary, a block of context fields, and an Open button.
CI-02
CI-01
The field block under the summary is not constant. Site Context and Overall Condition appear on every capture seen so far. Beyond those, one capture shows Capturer, Devices, and Covered Work Areas; another shows Facility and Level.
Open is a navigation control, not just a read-out: it moves the viewer to that capture and a toast confirms the move.
CI-07
Two further places surface the same outputs, and both belong to other articles:
- The Captures page, outside the viewer, carries a per-capture read of its own. It shows the Summary, and excludes Safety issues, Quality issues, and Custom objects.
- Compass, indirectly. Compass can search Capture Intelligence outputs, so a question can return a Safety issue or a Summary without you opening anything.
Note: For the strip itself, refer to the ChronoNavigator article. For search, refer to the Compass article.
FOR REVIEW — The Captures-page surface has no confirmed name. The Capture Page spec calls it the "Site Track Node Panel"; that string appears in no other document, on no screen in either recording, and no reviewer recognised it. This section names the page and stops. Product needs to say what that surface is actually called — it is the cheapest open question in this batch.
Which Captures Get Analysed
360-series captures only, at 5.0 — and "360-series" means the two capture kinds that produce a 360 walk: 3D Map and videodrive.
| Capture type | Capture Intelligence at 5.0 |
|---|---|
| 3D Map (360) | Yes — all five outputs |
| videodrive (360) | Yes — all five outputs |
| Drone | No — not at 5.0 |
| Laser scan | No — not at 5.0 |
Note: Do not describe this limit as "360 video only". That reads as a file format and leaves a customer holding a laser scan guessing. Name the supported capture kinds and the unsupported ones.
There is one more limit worth knowing, because it is a page-level rather than an engine-level one: on the Captures page, Safety issues, Quality issues, and Custom objects are excluded — that page surfaces the Summary. The viewer is where the rest appears.
When Results Appear
Not at once, and the wait is worth setting out plainly.
Gen6 SLAM takes roughly half a day to process a capture. Capture Intelligence analysis completes within that run rather than instantly at capture, so its results arrive with the processed model. Progress tracking adds a couple more calendar days on top.
So: upload today, expect the model and its Capture Intelligence read within about half a day, and progress figures a couple of days after that.
FOR REVIEW — Two things a reviewer should decide before this is published. The §3 risk above — it rests on a launch-plan claim three captures have put in doubt. And whether this article stays standalone: its "where you see it" section is now one surface that the ChronoNavigator article already covers, so what remains is an engine explainer. Recommendation: keep it standalone, because it is the only place the engine is explained and both Compass and the Captures page surface its outputs.