The unified spatial computation engine
One model of the building. Every number computed from it.
Walls, glass, racking, ceilings — modeled once on your real floor plans. Every physics engine reads that same geometry: walk the design in 3D, read the numbers where you stand, and let SOC survey the building before a truck rolls.
One model, many engines
The obstacle model
walls & materials · glass · doors · ceilings · racking · furniture
-
Wi-Fi RF
ITU-R P.2040 · P.526 · P.1238
-
Camera optics
DORI · IEC 62676-4
-
Conference A/V
AVIXA DISCAS · IEC 60268-16
-
Paging
STI · NFPA 72
-
DAS
Coverage on the same model
-
Electrical
NEC · IEEE 1584
Change the model once — every affected engine recomputes.
Why point tools can't follow
Three things a stitched-together stack can't do
Each one exists because every discipline computes from the same spatial model. Remove that, and none of them work.
01
Unified spatial computation engine
One obstacle model, many physics engines. Change a wall and every affected discipline re-flows.
Read the proof
02
GPS-anchored 3D walkthrough
Stand anywhere and read Wi-Fi, camera, audio, and display numbers — computed from real datasheets.
Read the proof
03
Autonomous virtual site survey
SOC walks the building, checks every discipline against your targets, and flags the fixes. No truck roll.
Read the proof
Proof 01 · Unified spatial computation engine
Change a wall. Watch every discipline re-flow.
The obstacle model is the single source of truth for the building — so an edit to the geometry is an edit to every discipline's inputs at once. What six point tools each approximate separately, the platform computes from one model.
- Walls with real materials, glass, doors, ceilings, warehouse racking, and furniture — modeled once, on your actual floor plans, in 2D and full 3D.
- Each discipline — Wi-Fi RF, camera optics, conference A/V, paging, DAS, electrical — runs its own standards-grounded engine against that same geometry.
- Change a wall material and Wi-Fi coverage, camera shadows, audio, and cable runs re-flow from the same edit. No re-keying across six tools.
One edit
Wall W-14 · interior
Drywall to Glass
Everything downstream
- Camera shadows re-cast through the new material
- Wi-Fi coverage re-propagated through the wall
- Speech intelligibility re-scored where it changed
- Cable runs re-flowed around the geometry
No exports. No re-keying. One geometry.
Proof 02 · GPS-anchored 3D walkthrough
Stand anywhere. Read every number.
The model is anchored to the building's real coordinates: where you stand in the walkthrough is where you'd stand on site. Walk it in first person and read what every discipline delivers at that exact position — the site walk you wish you could do before the site exists.
- Live readouts, every discipline at once: Wi-Fi signal strength, camera pixels-on-target, speech intelligibility, display sizing.
- Computed from real manufacturer datasheets — datasheet-derived antenna patterns, lens and sensor specs, IR range, speaker output. Not guesses.
- The proof travels: coverage heatmaps, per-camera POV reports, and print-ready site plan sets come from the same model.
Position readout — anywhere you stand
- Wi-Fi signal
- dBm at your position · ITU-R propagation
- Camera coverage
- pixels-on-target vs DORI · IEC 62676-4
- Speech
- intelligibility (STI) · IEC 60268-16
- Displays
- sized to the viewer · AVIXA DISCAS
Every figure starts from a manufacturer datasheet — antenna patterns, lenses, IR beams, speaker output.
Proof 03 · Autonomous virtual site survey
SOC walks the building, so you don't have to.
Point SOC at the model and it walks the building like a surveyor — floor by floor, discipline by discipline — checking what each position gets against your targets and flagging what falls short, with the fix it suggests. Design validation without booking a flight or renting a survey kit.
- Evaluates coverage against your targets across every floor of the model.
- Returns a punch list: what falls short, where, and the suggested fix — you review and apply.
- Re-run after every design change — validation is a re-run, not a return visit.
A virtual survey run
- 01 Traverses every floor of the model, discipline by discipline
- 02 Checks what each position gets against your coverage targets
- 03 Flags the gaps, with the fix it suggests
- 04 You review, apply, and re-run
No survey kit. No truck roll.
What the fragmented stack costs you
Tool figures below are what buyers pay for the point tools today — your current spend, never our price.
- One model
- Entered once, read by every engine
- No exports, no re-imports, no version drift between tools
- $4–12K/yr
- What an Ekahau seat costs today
- Plus the $3K Sidekick kit the virtual survey replaces
- $5–15K
- What AFMG EASE costs today
- Conference and paging assessment run on the same model here
- 6 → 1
- Point tools consolidated
- Ekahau · IPVM · EASE · System Surveyor · ConnectWise · DocuSign
The trust architecture
SOC never invents the numbers.
Not a policy — an architecture. The deterministic physics and cost engines own every figure on every deliverable; SOC researches, suggests, and explains. The boundary is structural: physics figures come only from the engines, and SOC explains them — it cannot author them.
What SOC does
- Reads your documents, orders, and datasheets into structured product and project data — with provenance.
- Researches products and enriches your library from cited sources.
- Walks the model, flags coverage gaps, and suggests the fix.
- Explains what was computed and from which standards, datasheets, and assumptions.
What SOC never does
- Never generates a physics figure — signal strength, pixels-on-target, intelligibility, and sizing come only from the deterministic engines.
- Never papers over a missing spec — unknowns stay visible as unknowns, not guesses.
- Never silently applies a change — SOC suggests; you review and approve.
The universal comparison
One platform vs. the six-tool stack
Capability for capability — the closest equivalent to the platform is six subscriptions stitched together.
| What you need | SiteOps Command | The six-tool stack |
|---|---|---|
| Wi-Fi RF design & survey | ✓ | Ekahau + Sidekick |
| Camera coverage & pixels-on-target | ✓ | IPVM Calculator |
| Conference audio & display assessment | ✓ | AFMG EASE |
| Survey documentation & site plans | ✓ | System Surveyor |
| Renewals, orders & AR | ✓ | ConnectWise |
| Design sign-off | ✓ | DocuSign |
| One shared building model across every discipline | ✓ | — |
| GPS-anchored 3D walkthrough with live readouts | ✓ | — |
| Autonomous virtual site survey | ✓ | — |
Even with all six on the shelf, the parts that matter most have no equivalent: the unified physics model, the GPS-anchored walkthrough, and the autonomous survey exist because every discipline computes from one geometry — and that is precisely what six separate tools can never share.
See the full six-tools comparisonBeyond design
The same model carries the whole job
The engine leads; the lifecycle follows. Design data flows into scope, install, and the commercial records without re-keying — the as-built you close with is the design you sold.
Built for the way you deploy
Start from your own workflow — each solutions page leads with the pain, the tools it displaces, and how the platform runs your job end to end.
Frequently asked questions
Does SOC generate the coverage numbers?
No. The deterministic physics and cost engines own every figure — Wi-Fi propagation, camera pixels-on-target, speech intelligibility, display sizing, and pricing are computed from your building model and manufacturer datasheets. SOC researches, suggests, and explains; it never invents a number.
Which standards does the physics follow?
Wi-Fi RF propagation follows ITU-R P.2040, P.526, and P.1238. Camera coverage is scored as pixels-on-target against DORI (IEC 62676-4). Speech intelligibility uses STI (IEC 60268-16), with NFPA 72 in view for paging. Display sizing follows AVIXA DISCAS, and electrical work references NEC and IEEE 1584.
Is this a simulation of the finished building?
It is design-stage estimation, and the platform labels it that way. Coverage is computed from your obstacle model and real manufacturer datasheets — strong enough to catch problems before install, honest enough not to claim it replaces an as-built field measurement. Field verification workflows are built in for install time.
Do the disciplines really share one model?
Yes — that is the architecture. Walls and their materials, glass, ceilings, racking, and furniture are modeled once; each discipline then runs its own engine against that same geometry. Change the geometry and the affected engines recompute. There is no export, re-import, or re-keying between tools.
Is SiteOps Command a CRM?
The platform carries the commercial side — renewals, orders, invoices, and receivables — so the model that wins the job also runs it. The lead is the engine: unified physics, the 3D walkthrough, and the autonomous survey. If you are comparing CRMs, see the ConnectWise comparison.
How do I evaluate it on my own building?
Book a demo and bring your own floor plans — we will design a floor, walk it in 3D, and run the virtual survey on it live. Prefer to explore alone? A sample project is available in the app the moment you sign up.
Walk your next site before it exists
Bring your own floor plans — design a floor, walk it in 3D, and run the virtual survey on it. Talk to us about what your team needs.