Solutions · MSPs & network teams
Every system on the site, one model
A customer site is rarely one discipline. It is access points, cameras, door controllers, and the switching, cabling and power that carry all three. SiteOps Command designs them on a single model of the building — then analyses how they interfere with one another.
What the job looks like today
Four systems. How many tools?
One site, four disciplines, and a different instrument for each — none of which knows what the others placed. The Wi-Fi figure is what buyers pay for the incumbent tool today, not SiteOps Command pricing.
Wi-Fi
a predictive RF tool, licensed per seat
$4–12K/yr
The seam
and the validation trip is still yours
Cameras
a lens-and-field-of-view calculator, per vendor
per vendor
The seam
the racking and the glass are not in it
Access control
the architect’s door schedule, in a spreadsheet
manual
The seam
retyped into the BOM, by hand, twice
Network & cabling
a drawing tool, and the port count in your head
manual
The seam
the PoE budget gets checked after the order goes in
Network, cabling and power
The network that carries all of it
Access points, cameras and door controllers all land on a switch port and all draw power. Place them and the topology is derived from the design itself — five tiers from WAN to access — with the closets modeled, the racks elevated in BICSI order, and the power budgeted before the order goes in.
- Five-tier topology derived from the placed design, with MDF/IDF closets and 2D/3D rack elevations
- Switch-port and patch-panel planning, with VLAN groupings suggested
- PoE budgets to IEEE 802.3af/at/bt, carrying 20% power and 25% port headroom
- Copper and fiber validated against ANSI/TIA-568 distances, TIA-606-D labeling, per-closet cable schedules
Computed, not counted
- Topology
- WAN → access, five tiers
- Closets
- MDF/IDF + rack elevations
- Power
- PoE, 20% / 25% headroom
- Cabling
- TIA-568 distances, TIA-606-D labels
Cameras and access control
Cameras and doors on the same floor plan
Camera coverage is computed rather than drawn: each camera carries its real lens and sensor, pixels-on-target are measured against the IEC 62676-4 DORI bands per zone, and walls, glass and warehouse racking cast real shadows. Doors carry their hardware, handing, fire rating and ADA state.
- DORI pixels-on-target per zone (IEC 62676-4), with four projection models including fisheye and panoramic
- Height-aware occlusion from walls, glass and racking — plus a per-camera 3D point of view
- Eleven access-control device types: OSDP, Wiegand and IP, fail-safe or fail-secure, supervised EOL
- Door schedules ingested from the architect’s spreadsheet, normalized, and published back out
Both disciplines, one model
- DORI
- IEC 62676-4, per zone
- Optics
- 4 projection models
- Doors
- 11 device types, full spec
- AC power
- PSUs sized from summed load
Standards-grounded propagation
Wi-Fi that respects your walls
Coverage is computed from the building, not sketched over it. Every wall carries a material with published attenuation, propagation follows ITU-R indoor models with diffraction, and each antenna is modelled from the gain and beamwidth in its product record, equal in every direction where no beamwidth is on file.
- ITU-R P.1238 indoor propagation, P.2040 building materials, P.526 diffraction
- Wall-by-wall obstacle physics fused with calibrated indoor statistical models
- Transmit power, antenna gain and beamwidth from the product record
- Multi-floor buildings with per-floor design and inter-floor propagation
Every input, sourced
- Materials
- published attenuation values
- Propagation
- ITU-R P.1238 · P.2040 · P.526
- Antennas
- gain + beamwidth from the product record
- Radios
- datasheet transmit power
Autonomous virtual site survey
The survey that walks itself
SOC walks the building model the way a technician with a meter would — systematically, floor by floor — probing coverage at each step, flagging the gaps, and proposing deterministic fixes. No Sidekick, no ladder, no flight.
- Systematic coverage pass across the whole floor plate
- Gaps flagged with deterministic, explainable remediation suggestions
- The physics engines own every number — SOC researches, suggests, and explains
The autonomous pass
- Walk
- systematic path through the model
- Probe
- coverage at every step
- Flag
- gaps and weak spots
- Fix
- deterministic remediation
Cross-domain interference
The conflicts a one-discipline tool cannot see
Two systems can each satisfy their own design rules and still defeat one another. This is not collision detection — none of the systems involved need to touch. It is the capability that exists only because every discipline computes on one shared model, and it is invisible to any tool that models them one at a time.
- Wi-Fi against DAS — co-channel, adjacent-channel and intermodulation (ITU-R SM.1541, 3GPP TS 36.104)
- Voice alarm against sound masking, whose objectives are opposites (IEC 60268-16)
- Electrical into RF and into audio — drive harmonics, conducted EMI, ground loops (IEEE C62.45)
- Spatial conflict — low-voltage separation from power, conduit congestion (NEC 300.3, NEC 800.133, TIA-568)
How it runs
- Classes
- five, each citing its standard
- Second pass
- real positions, not zone averages
- Severity
- counts against the design
- Output
- feeds the remediation list
From design to sign-off
Prove it to the customer in 3D
Walk the customer through their own building and read the signal live at any point you stand — then hand over the heatmaps, the plan set and a bill of materials generated from the same model that produced the design.
- GPS-anchored 3D walkthrough with a live Wi-Fi readout at any position
- Coverage heatmaps — Wi-Fi and camera — that change when the building changes
- Multi-floor print-ready plan sets with per-trade schedules
- A BOM built from the placed devices, and the SOW from the same survey
The handoff
- Walkthrough
- live signal, any position
- Heatmaps
- wall-aware coverage
- Plan set
- multi-floor, print-ready
- BOM & SOW
- from the design itself
The numbers that matter
The displaced-tool figure is the buyer's current spend. The rest are the standards the engines implement.
- $4–12K/yr
- Ekahau licensing
- one discipline, one tool
- IEC 62676-4
- DORI pixels-on-target
- per-zone camera targets
- 5 classes
- cross-domain interference
- analysed on every pass
- One model
- network · Wi-Fi · cameras · doors
- one BOM, one plan set
MSP questions
Does it cover cameras and access control, or only Wi-Fi?
All of it, on the same model. Cameras carry their real lens and sensor with pixels-on-target measured against the IEC 62676-4 DORI bands per zone, and walls, glass and racking cast real shadows. Access control models eleven device types with OSDP, Wiegand or IP configuration, fail-safe or fail-secure behaviour and supervised end-of-line — with door schedules ingested from the architect’s spreadsheet and published back out. Both produce their own requirements deliverable.
Can it design the switching and cabling too?
Yes — and that is the point of placing everything on one model. The five-tier topology is derived from the devices you placed, the MDF and IDF closets are modeled with rack elevations in BICSI order, switch ports and patch-panel chains are planned, and PoE budgets are computed to IEEE 802.3af/at/bt with 20% power and 25% port headroom. Copper and fiber are validated against ANSI/TIA-568 distances with TIA-606-D labeling and per-closet cable schedules.
What does “cross-domain interference” actually mean?
Two systems can each satisfy their own design rules and still defeat one another, without ever touching. Five classes are analysed — Wi-Fi against DAS, voice alarm against sound masking, electrical into RF, electrical into audio, and spatial conflict — each against the standard it cites. Conflicts are found on every analysis, carry a severity that counts against the design, and feed the remediation list. It exists because the disciplines share one model; a tool that designs them separately has nothing to compare.
Does this replace our Ekahau seats?
SiteOps Command covers the predictive-design and virtual-validation work: coverage computed from wall materials and manufacturer datasheets using published indoor models (ITU-R P.1238, P.2040, P.526), plus an autonomous virtual survey that flags gaps without hardware. If a contract requires on-site measured validation, you can still run that pass — the design no longer waits on it.
Does it scale past one site?
Designs are per-project with multi-floor buildings, and the survey and remediation pass runs on the model rather than on-site hardware — so a fifty-branch rollout is fifty models, not fifty truck rolls.
Design the whole site in one place
Network, Wi-Fi, cameras and door access on one model — with the conflicts between them found before anyone is on a lift.