Solutions · Camera OEMs & distributors
The coverage design tool behind your deployments
Your cameras are only as good as the design that places them. When the channel proves coverage — per zone, day and night, from your real datasheet specs — your hardware wins the spec. When it guesses, the RMA and the lost renewal are yours too.
The honest frame
This platform was not built for OEMs — that is the point
SiteOps Command is the design platform integrators run whole jobs on. This page is not a special OEM product; it is the straightforward observation that the tool your channel designs with decides how your cameras get specified.
We will not invent an OEM-shaped pitch: there is no separate OEM edition, and you are not the license the platform was designed around. What exists is more useful — a design environment where your cameras are modeled from their own datasheets, placed into real buildings, and proven against IEC 62676-4 DORI zones with occlusion and IR night reach. Your sales engineers can design in it directly, and your channel can run entire deployments in it.
What the channel designs with today
A free calculator, a single-brand widget, and SE hours
None of these carries a deployment. Each seam is a deal that stalls while somebody re-draws the layout.
IPVM Calculator
free PPF math on a flat map
The seam
no 3D point of view, no fisheye model, no IR, no occlusion — a number, not a proof
Single-brand lens tools
one camera at a time, one brand at a time
The seam
they cannot model the whole site, the mixed-brand reality, or the racking in the way
SE hours
your sales engineers hand-building layouts to support the channel
The seam
design support becomes the bottleneck on every deal that needs proof
Your line, as physics
Cameras modeled from their datasheets
The product library holds thousands of camera models with real manufacturer specs — and product enrichment pulls the numbers straight from datasheets. Lens focal length and sensor resolution become pixels-on-target; the IR beam specification becomes night reach; fisheye and panoramic models use their own projection math.
- Lens, sensor, and IR specs drive the computation — not generic archetypes
- Fisheye and panoramic projection modeled per design, not approximated as a cone
- Loading your line is product enrichment, not data entry — the specs come from your own datasheets
From the datasheet
- Lens
- focal length → field of view
- Sensor
- resolution → pixels-on-target
- IR
- beam spec → night reach
- Fisheye
- panoramic projection models
The spec conversation
Deals close on proof, not on promises
When an integrator places your camera in a design, the model computes what it will actually do there: DORI pixels-on-target per zone under IEC 62676-4, a 3D point of view per camera, and shadows cast by walls, glass, and warehouse racking. The deliverables carry your hardware to the end customer as evidence.
- Per-camera point-of-view reports — what this exact model sees from this exact mount
- Occlusion-aware coverage heatmaps across the whole floor, day and night
- Customer-facing design proposals and print-ready site plan sets with your SKUs on the BOM
Computed per design
- DORI
- IEC 62676-4, scored per zone
- POV
- 3D — what each camera sees
- Night
- IR reach in the design
- Occlusion
- walls, glass, racking
Team & channel
One tool your SEs and your partners share
Your sales engineers design deployments in the same platform your channel runs jobs in. Projects have shareable views and sign-off flows for people outside your org, and a camera-focused workspace preset keeps the surface scoped to survey and coverage work.
- SE-built designs hand off to the integrator as a live model, not a PDF
- Shareable project views and sign-off flows for stakeholders outside your org
- A Camera OEM workspace preset — survey and coverage surfaces without the modules your team does not need
Working together
- Design
- SE team, on the real floor plan
- Share
- live views outside your org
- Sign-off
- stakeholder flows built in
- Preset
- camera-scoped workspace
Neutral ground, measured honestly
Structural facts about how cameras are modeled — no invented benchmarks, no brand deals.
- Thousands
- of camera models in the library
- real manufacturer specs, enrichment-fed
- IEC 62676-4
- DORI pixels-on-target
- scored per zone, per design
- Spec-driven
- no brand weighting in the physics
- the engines compute whatever camera is placed
- Datasheets
- every figure computed from real products
- SOC never invents the numbers
OEM & distributor questions
We make cameras — why is a design platform our tool?
Because the spec decision happens inside design tools. SiteOps Command is where integrators prove coverage to end customers, and where your own sales engineers can build that proof for the channel. Cameras win deployments when the design shows — per zone, day and night — that they do the job.
Are our cameras already in the library?
The library covers thousands of camera models with manufacturer specs, and product enrichment pulls real numbers from datasheets — so loading or extending your line is enrichment work, not manual data entry. Bring a handful of SKUs and see how they model.
Does the physics favor any brand?
No. Every figure is computed deterministically from the placed camera’s datasheet specs — lens, sensor, IR beam — against the building geometry. There is no scoring layer to tune and no brand weighting to buy. SOC never invents the numbers; the optics engine owns them.
Can our distributors and integrator partners work from our designs?
Yes. Projects support shareable views and sign-off flows for people outside your org, so an SE-built deployment design reaches the partner as a live model rather than a static export.
Put your line in the design conversation
Bring two or three SKUs and a real floor plan. See your cameras modeled from their own datasheets — and the coverage proof your channel could be selling with.