One flow, from the floor plan to the job site. No loose spreadsheets, no guesswork.
Draw the building, the interior walls and the project boundary point by point on the plan. Each camera cone is now clipped by what stands in front of it — it no longer passes through walls, and never leaves the perimeter. The project summary also groups cameras by building.
Draw the target zone in Konva; width and distance come from the geometry, not hand-typed numbers.
For each position: minimum resolution, minimum HFOV, and the DORI/OODPCVS level it meets — in both standards side by side.
Evidence forces Validate (500 px/m) in the 2025 standard. Above 4000 px it proposes two positions, never a camera that does not exist.
Mounting height, target height, vertical tilt and ground slope, with a side view of the camera that follows what you draw on the plan.
Routes on the plan, cable type and pathway; length = route × quantity; infrastructure counts once.
Draw per camera, sum per switch, recommended headroom, and automatic switch upgrade when connected ports exceed capacity.
TB per period given resolution, fps, codec, retention and recording mode.
Generates the logical schematic from the real connections, with equipment icons.
Try alternative positions on the same plan and compare the coverage achieved, to reach the camera count that meets the requirement.
Hours and costs per line — cabling, installation, configuration, training — with quantities taken from the drawing. Hourly cost per resource and fixed or per-kilometre travel.
Tasks, durations and resources from the estimated services, shown as a Gantt chart and exported with the technical dossier.
Exports a requirements envelope any supplier can answer — not a list of models.