Chapter 01 of 04
The brief
A walkthrough scan of an office floor should do more than render a 3D model.
It should say where every fire extinguisher, smoke detector and exit sign is, as a register somebody can check. The work was getting from a cloud of imagery to a list of real objects with trustworthy positions, and then deciding which of those objects were dependable enough to hand over.
A walkthrough scan already carries the information. Every fire extinguisher, smoke detector and exit sign on the floor is sitting there in the captured imagery and geometry, and nothing about how the building is scanned needs to change. What is missing is the step that turns all of that into a list of real objects with positions, which is the difference between a 3D model somebody looks at and a register somebody can act on.
The tempting shortcut is to find each asset in an image and estimate how far away it looks. That puts assets near where they are, and near is not useful when the output is a safety document. Positioning each one against the building's own captured geometry costs more work and is the only version worth shipping.
Chapter 02 of 04
The problem
Read a fire-safety asset register off a handheld building scan, accurately enough that an operator can check it rather than redo it.
Chapter 03 of 04
The build
- Research
- Rebuilt the register from scratch rather than patching the existing one, so the new result could be compared against the old. The two diverged, and that divergence was recorded as a finding instead of being reconciled away.
- 3D & Spatial
- Positioned each asset against the building's own captured geometry rather than estimating its distance from a single image, which is the difference between roughly where a thing is and where it actually is. For a safety register, roughly is not useful.
- AI & Machine Learning
- Open-vocabulary detection across the scanner's several camera streams, so new asset types could be asked for in plain language instead of requiring a labelled training set per class, with a second pass triaging candidates before an operator sees them.
- Data Pipelines
- Consolidated repeated sightings into one entity per real object: the same extinguisher appears in many frames, so each detection is a vote on a position rather than a separate asset. How strict that consolidation is turned out to be the accuracy dial.
Build notes. How it came together.
Chapter 04 of 04
What it did
Four asset classes came out dependable enough to put in front of an operator, each entry positioned against the building's own geometry and paired with a crop so it can be checked by eye.
A fifth was tested and cut, which turned out to be the more useful result.
Four classes are dependable enough to hand to an operator, each paired with a crop so an entry can be checked by eye rather than trusted, and by the end the office-wide pipeline covered a much wider set of asset types. Emergency lights stay out. The honest version is that these detectors cannot separate an emergency light from an ordinary ceiling light because the two look the same, and no amount of rephrasing the request fixes a problem the pixels do not contain. Getting past it needs a human in the loop teaching the difference, not a cleverer prompt, and knowing which of those two you are facing is most of the value.
- 4
- Classes trustedoperator-checkable
- 1
- Class tested and cuton evidence, not instinct
- 27
- Classes, office-widethe wider register pipeline this pilot fed into, not this pilot's own count
Research origin.
[ Spatial asset intelligence ]
Turning one handheld building scan into a per-object, queryable asset registry.


