Start with a place, not an alert.
A building has people, equipment, cameras and routes. A request must refer to the same objects across all of them.
Facility · mobile inspector · connected systemsOne operating layer for the physical world.
The agent interprets a request. The world model supplies context and memory. Orchestration sends a permitted task to a robot, system or person—and records the result.
Give the agent something reliable to reason from.
The world model combines spatial relationships, current observations and history. The agent can ask what changed, what it affects and which evidence is still missing.
Observation → entity → state → memoryCoordinate the response. Keep the evidence.
Mission orchestration turns the plan into a task for a robot, infrastructure controller or person. The local executor can refuse; returned evidence closes the loop.
Plan → permission → executor → verified resultLoading spatial model…
Scroll to reveal context · drag to orbitIllustrative 3D geometry
PHYSICAL CONTEXTOne estate. Shared context. Different executors.
A spatial model connects the building, its equipment and the inspection route.
REASONING AGENT
A request is not yet a command.
Resolve the target, query current and historical evidence, ask for missing information and propose a bounded plan. Permissions belong to the mission service.
- READS
- Goal, spatial context, evidence freshness and capability limits.
- RETURNS
- A plan with cited evidence, assumptions and required approval.
- DOES NOT OWN
- Authoritative sensor facts, operator authority or motor control.
THE OPERATING LOOP
Put the three roles to work.
Example: cooling has failed in a production area. The agent investigates, the world model retains the evidence, and orchestration requests a scoped recovery.
FACTORY EXAMPLE · P-204 DUTY CIRCUIT / SB-02 BACKUP
INTERACTIVE SCENARIO · SIMULATEDrev 0
Monitoring cooling
Flow / FT-0218.0L/min
Pressure / PT-049.4bar
Source-labelled observations arrive continuously.
PRODUCT DECISIONS
Build the part that gets reused.
The value is not another camera alert or robot demonstration. It is a workflow an operator can trust and a deployment the team can repeat.
Make the model replaceable.
Evaluate a general VLM for semantic understanding. Retain small specialist models where measured quality, latency, offline operation or total cost is better.
Own the operating contract.
Stable identity, evidence freshness, scoped authority, mission lifecycle and outcome acceptance should survive a change of camera, model or robot.
Make site two easier.
Separate reusable skills and policies from site maps, asset bindings and OEM adapters. Measure the work required for the next deployment.