Digital twin
A topology-first model connects power, cooling, network, compute, storage, and environmental systems.
VANTREXIS Labs concept
ORBIT
Industrial Digital Twin & Mission Control
A digital twin for understanding how critical infrastructure behaves—and how it fails. ORBIT models power, cooling, compute, and network systems as one connected operational environment, allowing operators to inspect telemetry, understand dependencies, and simulate component failures to see how risk propagates across the system.
- Digital Twin
- Real-time
- IoT
- Simulation
Simulate a failure Interactive concept · Synthetic data
- Type
- VANTREXIS Labs concept
- Domain
- Industrial Digital Twin & Mission Control
- Format
- Interactive system model
- Interaction
- Failure simulation
What the concept explores
Telemetry becomes more useful when operators can see what depends on it.
Complex infrastructure becomes difficult to operate when telemetry is separated from the relationships between systems. ORBIT explores an interface where operators can see system state and dependency impact in one operational model.
Failure propagation
A deterministic rules engine resolves direct dependencies, secondary impact, redundant capacity, and operational risk.
Contextual telemetry
Each asset exposes metrics that match its role instead of repeating generic charts across the system.
System model
The interaction follows the system, not a generic dashboard pattern.
The demo runs entirely in the browser with typed, deterministic mock data. Each state transition is derived from relationships in the product model.
- 01
Inspect system topology
- 02
Select a physical asset
- 03
Simulate its failure
- 04
Observe dependency impact
- 05
Review response and risk
Engineering challenges
Complexity placed where it improves understanding.
The concept focuses on relationship modelling, consequential interaction, and operational clarity—not fabricated business outcomes.
- Typed infrastructure and dependency modelling
- Deterministic cascade and failover calculation
- Readable topology across responsive breakpoints
- Accessible non-colour status communication
- Timer cleanup and reduced-motion support
- Contextual telemetry by component type
Engineering focus
Modeling how infrastructure behaves when dependencies fail.
ORBIT explores the engineering behind dependency-aware operational systems: representing connected infrastructure, propagating state changes through the model, correlating telemetry with system risk and making failure scenarios understandable to operators.
- 01
Dependency graph modeling
Represent power, cooling, compute, network and storage assets as one connected operational model with explicit upstream, downstream and redundant relationships.
System topology · Dependency relationships · Redundancy
- 02
Deterministic failure simulation
Run reproducible failure scenarios against the system model so the same initial condition produces an explainable sequence of operational state changes.
Scenario modeling · Reproducible state · Controlled simulation
- 03
Cascading state propagation
Propagate a component failure through dependent systems while distinguishing the primary causal path, secondary impact and unaffected infrastructure.
Causal paths · Downstream impact · State propagation
- 04
Telemetry & state correlation
Keep operational metrics synchronized with asset state so load, temperature, capacity and risk evolve consistently with the simulated incident.
Telemetry state · Operational context · Risk signals
- 05
Resilience & failover logic
Model redundancy, load redistribution and compensating actions to show how infrastructure responds when normal operating capacity is reduced.
Redundancy · Failover · Load redistribution
- 06
Operational visualization
Turn a complex system model into an interface where operators can identify the failure, understand its consequences and inspect the response without decoding the graph manually.
Mission-control UX · Incident focus · Explainable system state
Simulation model
From component failure to operational response.
- 01
System model
- Assets
- Dependencies
- Redundancy
- 02
Failure event
- Selected component
- State transition
- Scenario context
- 03
Impact propagation
- Primary cascade
- Secondary effects
- Affected assets
- 04
Telemetry & risk
- Load changes
- Capacity changes
- Operational risk
- 05
System response
- Failover
- Load redistribution
- Operator context
Interactive product concept
See how a cooling failure propagates across the system.
Replay a controlled infrastructure failure and follow how dependencies, telemetry, operational risk, and system response evolve as the incident propagates.
Simulate a failureHave a similar challenge?