The software is only useful if the geometry survives contact with the real site.
Teams searching for CCTV planning software are usually trying to solve one of two problems: proving a camera layout is credible, and producing outputs that other people can actually review. SighThor is built around both.
What buyers usually need answered
- Can it model real terrain and line-of-sight blockage?
- Can it produce DORI zones from actual sensor and lens inputs?
- Can consultants share the output without forcing a desktop install on everyone else?
- Can it export a schedule, map, and report pack without manual reconstruction?
Selection Criteria
What modern camera planning software should actually deliver
The product category is full of tools that draw coverage nicely but leave the hard questions unresolved. These are the capabilities worth paying attention to.
Terrain sources, not hidden flat assumptions
Outdoor camera planning breaks when embankments, ridgelines, and level changes are ignored. The software needs to model those effects directly.
Reference-threshold DORI reasoning
The output should compare nominal camera performance with IEC 62676-4 DORI / PPM reference thresholds rather than hand-waved distance claims.
Web-native collaboration
Teams increasingly need Mac, Windows, Linux, and tablet access without being trapped in a single desktop install path.
Draft review evidence
A planning workflow is incomplete if the schedule, map, and report still need to be rebuilt in other tools before the client can review them.
Why SighThor
A terrain-aware alternative to flat-plan camera workflows
SighThor is designed for consultants and planning teams who want the DORI math, the map geometry, and the export pack to tell the same story.
Practical positioning
Web-native where it helps, explicit about assumptions throughout.
SighThor keeps the workflow browser-based while exposing the selected terrain source, configured camera geometry, and draft deliverables. Nominal results still require field and competent-person review.
Next useful step
Use the product page for the active workflow and the DORI guide for the technical detail.
FAQ
Questions that usually come up during evaluation
These are the discussions teams tend to have when they are comparing camera-planning workflows.
Turn a site brief into an inspectable planning draft.
Start with terrain-aware geometry, then review every source, limitation and field check.