Solutions · Security installers & low-voltage
Cameras, doors, and the cable between them
A PPF calculator hands you a number; your customer stands in the aisle at midnight and asks why the face is not identifiable. SiteOps Command computes each camera’s actual point of view from the manufacturer’s datasheet — then models the doors it covers and the cable that feeds both.
What you run today
A number, a markup, a spreadsheet, and a flashlight
Three trades, four instruments, and none of them knows what the others placed. The gaps between them are where handoff disputes are born.
IPVM Calculator
pixel-density math on a straight line
The seam
no 3D point of view, no fisheye model, no IR simulation
CAD / PDF markups
where the cameras go
The seam
not what they see — occlusion is discovered from the lift
The door schedule
an architect’s spreadsheet, in your inbox
The seam
retyped into the BOM by hand, and stale by the site visit
The night walk-test
proving IR coverage after install
The seam
the first time anyone sees night performance is after the sale
What each camera sees
The point of view, not a cone
Every camera renders a three-dimensional point of view computed from its lens geometry: focal length, sensor, mounting height, tilt. Walls, glass, and warehouse racking cast real shadows in it — so the view you sell is the view the customer gets.
- Shadow-casting field of view: walls, glass, and racking block what they should
- Per-camera POV rendered in 3D from the datasheet lens geometry
- Warehouse aisles covered honestly: racking runs and areas occlude views the way steel does on site
Occlusion, respected
- Walls
- height-aware; solid walls block views
- Glass
- windows see-through; glass walls block
- Racking
- in-rack and cross-rack shadowed
- Result
- the actual point of view
IEC 62676-4
DORI on every target, fisheye included
Pixels-on-target is computed per zone against DORI — detect, observe, recognize, identify. Fisheye and panoramic lenses get real projection models, not a straight-line PPF formula stretched past where it holds.
- DORI (IEC 62676-4) pixel-density targets evaluated per zone
- Multiple lens projection models, including fisheye and panoramic
- Coverage heatmaps that account for structural occlusion across the whole floor
DORI tiers
- Detect
- presence in the scene
- Observe
- activity and behavior
- Recognize
- a known individual
- Identify
- an unknown individual
IR from the datasheet
Night is not a guess
IR night-vision range is read from each camera’s datasheet and applied to the coverage math — so the doorway that identifies a face at noon and loses it at midnight is caught at design time, not on the punch list.
- IR range from the manufacturer datasheet, per camera
- Night-mode coverage evaluation alongside the daytime view
- Per-camera POV reports a customer can verify standing on site
After dark
- IR range
- from the datasheet
- Night mode
- coverage with IR applied
- Report
- per-camera POV, printable
- Handoff
- verifiable on site
Access control
The doors, with their hardware on them
A door is not a dot on a plan. It carries handing, fire rating, ADA state and a hardware set — and the reader, controller, REX and lock that go on it. Hand over the architect’s door schedule and it is normalized and matched rather than retyped, then published back out on the plan set.
- Eleven device types with OSDP, Wiegand or IP configuration, fail-safe or fail-secure, supervised end-of-line
- Door schedules ingested from XLSX or CSV, normalized and fuzzy-matched, then published back out
- Controller capacity read from the product library under a no-invented-numbers rule — an unknown port count stays unknown
- Fire, ADA and egress compliance checked, with a life-safety flag when a fail mode contradicts egress
- Cameras paired to doors, so the view covering an opening is tied to the opening
Every door, specified
- Doors
- handing, fire rating, ADA state
- Devices
- 11 types · OSDP / Wiegand / IP
- Schedules
- imported, normalized, published
- Power
- PSUs sized from summed load
Structured cabling
Every device is a drop, and every drop is a run
Cameras and readers do not float. Each one is a cable run with a real length, a real pathway and a label — validated against ANSI/TIA-568 distance limits, calculated with service loops included, and scheduled per closet so the installer knows what to pull before the truck is loaded.
- Copper and fiber validated against ANSI/TIA-568 distance limits
- Cable routing with calculated lengths including service loops, and capstan pull-tension physics on the optimizer
- TIA-606-D labeling, with per-closet cable and drop schedules
- PoE budgets to IEEE 802.3af/at/bt carrying 20% power and 25% port headroom
- Access-control protocol cable limits and the BICSI run model, with ADA 48" reader height
Pulled by the numbers
- Distances
- ANSI/TIA-568 validated
- Lengths
- routed, service loops included
- Labels
- TIA-606-D
- Power
- PoE · 20% / 25% headroom
Grounded in the standard, not the brochure
Capability facts and named standards — no invented accuracy claims.
- DORI
- IEC 62676-4 pixels-on-target
- detect · observe · recognize · identify
- 3D POV
- per-camera point of view
- walls, glass, and racking occlude it
- 11 types
- access-control devices
- OSDP, Wiegand, IP — fail-safe or secure
- +25%
- power-supply headroom
- over summed lock and reader current
Security installer questions
Does it do access control, or only cameras?
Both, on the same model. Eleven access-control device types are modeled with OSDP, Wiegand or IP configuration, fail-safe or fail-secure behaviour and supervised end-of-line. Doors carry handing, fire rating, ADA state and a hardware set; fire, ADA and egress compliance are checked, with a life-safety flag raised when a fail mode contradicts egress. Lock and reader power supplies are sized from the summed load. Battery standby time is not calculated yet, and the access report says so. Cameras can be paired to the doors they cover. There is a dedicated Access Control Requirements deliverable.
We get the door schedule as a spreadsheet. Do we retype it?
No. Door schedules are ingested from XLSX or CSV, normalized and fuzzy-matched against the doors in the model, and then published back out on the plan set and in the requirements deliverable. Controller capacity is read from the product library under a no-invented-numbers rule — where a port count is not known, it stays blank rather than being guessed.
Can it produce the cable schedule?
Yes. Every placed device is a cable run: copper and fiber are validated against ANSI/TIA-568 distance limits, lengths are calculated from the routed pathway with service loops included, labeling follows TIA-606-D, and schedules are produced per closet. PoE budgets are computed to IEEE 802.3af/at/bt carrying 20% power and 25% port headroom, so the switch is sized before the order goes in.
How is this different from the IPVM Calculator?
A PPF calculator projects pixel density along a straight line. SiteOps Command computes each camera’s three-dimensional point of view — with walls, glass, and warehouse racking casting real shadows — models fisheye and panoramic lenses, applies DORI (IEC 62676-4) targets per zone, and reads IR night-vision range from the datasheet.
Can it show coverage at night?
Yes. IR range comes from each camera’s datasheet, and coverage can be evaluated in night mode — so a camera that covers the aisle at noon and loses it at midnight is caught at design time, not at handoff.
What do we hand the customer at sign-off?
Per-camera point-of-view reports, coverage heatmaps that account for structural occlusion, an Access Control Requirements deliverable, per-closet cable schedules, and print-ready multi-floor site plan sets — all generated from the same model the design was built in, so the deliverable matches what was sold.
Does it handle warehouse racking?
Yes — racking is a first-class obstacle. Runs and areas block camera views the way steel and pallets do on site: aisles are covered, in-rack and cross-rack views are shadowed, and the heatmap reflects it.
Prove the coverage before you pull cable
Camera POV, DORI zones, door hardware and per-closet cable schedules — all from one model your customer can verify at handoff.