Cameras now map the workspace.
No CAD files needed.
Real-time scene detection replaces manual calibration. Xolver reads the environment directly — parts, fixtures, zones, surfaces — and aligns coordinate frames automatically, cutting setup time from hours to minutes.
Where scene context comes from
Live capture
Environment cameras
When a cell publishes fresh environment state, Xolver reads the scene directly — part positions, fixture locations, zone boundaries — without manual CAD entry.
Declared metadata
Reference geometry
For cells without live scene publishing, structured workcell metadata and reference geometry serve as a fallback — letting commissioning start earlier while keeping assumptions explicit.
Historical records
Replayed commissioning
Replayed scene records let teams inspect how a proposal was produced, what assumptions were active, and why the system allowed, blocked, or escalated a path.
What the system does with a live scene
When a cell publishes fresh environment state, Xolver uses that context across preview, planning, and constraint surfaces — keeping proposals grounded in where things actually are, not where they were programmed to be.
- Locating known parts and surfaces
- Checking workspace and reachability bounds
- Previewing target movement before execution
- Reasoning about fixture and conveyor context
- Aligning proposals to current cell state
Public safety boundary
Scene context helps Xolver preview and constrain behavior. It does not replace safety validation, operator approval, or hardware-specific signoff.
If scene information is missing, stale, or insufficient, the system blocks, refuses, or requests review — it does not improvise unsafe motion.
FAQ
Does scene context replace safety validation?
No. Scene context grounds previews and proposals, but it does not replace runtime contracts, safety validation, hardware-specific checks, or operator approval.
What happens if live scene information is stale?
The system marks the context as stale, falls back to declared reference geometry where appropriate, or blocks and requests review when the information is insufficient for safe evaluation.
Can Xolver work without live scene context on day one?
Yes. Bench and pilot workflows can start from structured metadata and reference geometry, as long as the system stays explicit about the limits of that context.
Why is replayed scene context useful?
Replayed records help teams inspect how a proposal was produced, what assumptions were active, and why the system allowed, blocked, or escalated a given path.