For fire & security estimators

Device counts where every circle means something different

Fire alarm layouts are a family of near-identical circles: smoke, heat, multi-criteria, sounder bases. Getting the split right matters — devices are priced per type, and the difference is a tag letter or an inner stroke. StructCount reads both.

Optical & multi-criteria smoke detectorsHeat detectorsManual call pointsSounders & VADsBeam detectors & receiversInterfaces & I/O unitsCCTV & access control devices

Where counts go wrong

The hard parts of this trade — handled

The circle family

Smoke, heat and sounder symbols share the same outer circle. The engine separates them by the exact geometry inside the circle — and by the tag letters (SD, HD, S) drawn within, which become part of each symbol's identity rather than ignored text.

Tags drawn as outlines

CAD exports often turn device tags into vector outlines no text search can read. StructCount decodes the drawing's embedded fonts to recover them — so a detector tagged HD counts as heat, even when the PDF has no selectable text.

Addressable loops as noise

Loop wiring, zone boundaries and device address labels crowd every symbol. Geometry matching verifies the device's own strokes, so the loop passing through a detector doesn't change what it is.

Schedules that must reconcile

Every count is traceable to its locations, so reconciling your device schedule against the cause-and-effect matrix is a click-through, not a recount.

In practice

Upload the fire alarm layouts; the legend's device rows become your classes, tags included. The engine counts each type across the floors, look-alikes land in review with zoomed thumbnails, and the AI adjudicator can pre-sort them before you decide. Export the device schedule when the last sheet is finalized.

Try it on a live tender

Free while in early access — your drawings, your counts, minutes later.

Get started free