Platform

One engine. Four horizons. Every number traced.

How a Halō twin looks back, sees now, looks ahead and tests what-ifs, and how every answer traces to where it came from.

The four horizons One line through time. A solid past trace on the left, a live point at the present, a forecast with a widening confidence band for the future, and two scenario branches for what-if. A trace line runs underneath all four, with points dropped onto it from each horizon. 01 PAST What happened, and why 02 PRESENT What's happening now 03 FUTURE What's likely next 04 WHAT-IF What happens if you act TRACE EVERY NUMBER TO ITS SOURCE

From what happened to what if.

  1. Past: what happened and why.

    Every disruption carries a reason, so a missed target links back to the risk that caused it.

  2. Present: Detect.

    Rules flag what's happening now: a fault, a breached limit, a lapsed certificate.

  3. Future: Predict.

    Forecasts of what's likely next, each with its confidence and the drivers behind it.

  4. What-if: Explore.

    Scenarios play out a change across the operation, show the cascade before and after, and recommend what to do.

Every horizon also takes questions in your own words. Past, present, future and what-if are not limited to the screens we build: ask the twin anything about your operation in plain language, and every answer comes back with its sources.

Four horizons, one event at a time.

Each example follows a single event from what happened to what if.

  1. Past

    Last season, weather caused most small-craft delays, and labs waited on samples each time.

  2. Present

    Today's missions are running to plan, every asset inside its limits.

  3. Future

    A front is forecast to close the window for small craft and subsea launches in three days. Go-probability falls, with confidence and the drivers behind it.

  4. What-if

    The scenario shows missions slipping, labs waiting and crews idle. It recommends pulling work forward and moving research-vessel work into the bad days.

Scenario runner: weather window

In every tab, each figure and recommendation opens to the records behind it.

Real infrastructure, built in layers.

Four layers take the systems you already run to answers you can act on and defend. Security, governance and audit wrap every one.

The Halō stack, in depth An isometric stack of three plates. At the bottom, signals: tiles for the systems an operation already runs. In the middle, ingestion and resolution: a dot grid where entities are reconciled into one model. On top, the twin: assets, people and places connected on one orange-edged plate, whose two front edges carry the Performance and Risk dimension icons. Above float four cards for past, present, future and what-if, each linked down to the twin. An orange rule underneath reads security, governance and audit across every layer. PERFORMANCE RISK PAST PRESENT WHAT-IF FUTURE 04 INTERFACES AND EVIDENCE The four horizons, every figure traced 03 THE TWIN Measured on Performance and Risk 02 ENGINE Ingested, resolved into one model 01 SIGNALS The systems you already run SECURITY · GOVERNANCE · AUDIT ACROSS EVERY LAYER

  1. Signals.

    The systems you already run: tracking, telemetry, schedules, ticketing, maintenance, bookings, weather and records.

  2. Engine.

    Ingested, cleaned and resolved into one model: assets, people, places and events reconciled across every source.

  3. The twin.

    Assets, people and places connected, and measured on Performance and Risk.

  4. Interfaces and evidence.

    The four horizons, past, present, future and what-if, with every figure traced to its source.

Measured on what drives your operation.

Every operation is judged on different things. A port lives on throughput and dwell; a venue on experience and safe dispersal; a research fleet on reliability and weather windows. Halō's two frameworks are libraries of standard dimensions. Your twin lights the ones that drive your operation, and the rest are there when priorities change.

Framework dimensions, configured for All Two keypads of dimensions. Performance Unit: Throughput, Utilisation, Time, Reliability, Efficiency, Cost, Experience, Sustainability. Risk Unit: Operational, Technical, Environmental, Geopolitical, Financial, Behavioural, Compliance, plus an empty key for adding a dimension. Lit for this preset: Throughput, Utilisation, Time, Reliability, Efficiency, Cost, Experience, Sustainability, Operational, Technical, Environmental, Geopolitical, Financial, Behavioural, Compliance. CONFIGURED FOR ALL PORT RESEARCH FLEET VENUE Performance Unit 8 OF 8 LIT Throughput Utilisation Time Reliability Efficiency Cost Experience Sustainability Risk Unit 7 OF 7 LIT Operational Technical Environmental Geopolitical Financial Behavioural Compliance ADD A DIMENSION

The Performance Unit: how well is it running?

Throughput

How much moves through the operation

For exampleFreight units across a quay; passengers through a terminal; missions run per week

Lit for every operation

Choose a preset or any key to see what it measures.

  1. Dimension
  2. Measure or risk
  3. Signals from source
  4. Target and thresholds
  5. Status (green, amber, red)
  6. Source trail

Each measure and risk carries a target and green, amber and red thresholds agreed with you.

Both libraries grow, and every improvement we make reaches your twin.