The Operations Manager at the operations console reading the live fleet map, with the four jobs of the view around it: what is running and what is at risk, whether the fleet is being used well, driver safety and compliance, and the state of every EV charger.
The Operations Manager view exists to catch fleet problems before they ever reach a guest. Breakdowns, delays, and idle vehicles rarely announce themselves; left unwatched, they surface later as complaints, missed transfers, and rising cost. This view is built to give early sight of the fleet, so each of those problems can be acted on while it is still small.
It watches four things at once: what is running and what is at risk, whether the fleet is being used well, driver safety and compliance, and the state of every EV charger. The aim across all four is the same, to move from finding out something is wrong too late to always knowing what is running, what is under strain, and what needs attention before it turns into a cost or a service problem.
The wide view of the destination. The bottom strip is the operations read: fleet and maintenance, utilization, driver safety, and EV charging.
What you see
At the wide view, the bottom strip is the operations read for the whole destination, grouped into fleet availability, utilization and efficiency, driver safety, and EV infrastructure. A map legend in the corner counts the open items by severity and confirms the operational sensor feed is live.
| Group | Field | Reads | What it tells you |
|---|---|---|---|
| Fleet availability | On service vs maintenance | bar | Share of the fleet in service against those in maintenance |
| Fleet availability | Repair and return | 4.2 h | Average time to fix a vehicle and return it to service |
| Utilization and efficiency | Top used vehicle types | Buggy 1,240, shuttle bus 980, EV sedan 610 | The most used classes, by trip count |
| Utilization and efficiency | Fuel and battery hub | 72% avg | Average charge across the fleet |
| Utilization and efficiency | Hub idle time | 22% avg | Time vehicles sit unused |
| Utilization and efficiency | Hub peak | 17:00 to 18:00, 34 vehicles, 318 guests | Busiest hour and its load |
| Utilization and efficiency | Under and over use | bar | Balance of over-used against under-used assets |
| Utilization and efficiency | Inspection and inspection compliance | 96.6%, Compliant | Share of the fleet meeting inspection requirements |
| Driver safety | Violation, fatigue, accidents | 0, 0, 0 | Driver behaviour, fatigue, and incident counts today |
| EV infrastructure | Active vs inactive charging | bar | Charging stations working against those down |
| EV infrastructure | Total energy charged | 63% capacity | Energy delivered against capacity |
The map legend reads the open items by severity: 0 critical, 1 high, 2 medium, and 8 low or info, fed by the operational sensor feed running live.
Reading the fleet across the destination
The read works at two levels. At the wide view the strip covers the whole destination. Drop into a hub, here Turtle Bay, and the same read rescopes to that hub, which is what shows whether a problem is local to one hub or shared across the whole fleet.
| Aspect | Detail |
|---|---|
| Problem | Breakdowns, delays, and idle vehicles rarely announce themselves, and surface later as complaints, missed transfers, and rising cost. |
| Goal | Keep early sight of the fleet across the destination and within a hub, so a problem can be caught while it is still small. |
| Precondition | The operations feed is live: fleet and maintenance, utilization, driver safety, and EV charging are reporting. |
| Steps | 1. Open the Operations Manager from the persona bar. 2. Read the destination operations strip: fleet and maintenance, utilization, driver safety, and EV charging. 3. Select a hub to rescope the same read to one hub. 4. Read the hub figure against the destination figure to tell a local problem from a fleet-wide one. |
| Postcondition | A problem is located to a hub or recognised as fleet-wide, early enough to rebalance. |
Zoomed to the Turtle Bay hub. The strip rescopes to that hub, carrying the same grouped read as the destination: repair and return 4.2 hours, fuel and battery 72%, hub idle 22%, inspection compliance 96.6%, and total energy charged 63%, with the asset pins placed across the hub.
The close-up: four things to stay ahead of
At the closest level the view drills into a site, here Turtle Bay, and brings the four areas together in one panel before raising a recommended action for each. Each card frames the same shift, from reacting after the fact to acting on an early signal.
The Operations Manager close-up at Turtle Bay, with the consolidated site panel on the left and camera and charger pins across the campus.
| Field | Reads | What it tells you |
|---|---|---|
| Repair and return | 4.2 h | Average time to fix a vehicle and return it to service |
| Inspection compliance | 96.6% | Share of the site fleet meeting inspection requirements |
| Idle time | 22%, 3.1 h average | How long vehicles sit unused |
| Fuel and battery | 72% | Average charge across the site fleet |
| Top used vehicle types | Buggy, shuttle bus, EV sedan | The most used classes, in order |
Fleet availability
What is running, at risk, and out of service is legible early, so capacity can be rebalanced before it bites.
| Aspect | Detail |
|---|---|
| Problem | You found out something was wrong too late to prevent it. |
| Goal | Always know what is running, what is at risk, and what is out of service, so capacity can be rebalanced before it bites. |
| Precondition | Fleet and maintenance figures are reporting for the site. |
| Steps | 1. The card surfaces: 18 of 24 buggies running at only 2 of 6 seats. 2. Pool reception trips to fill buggies, freeing about 6 vehicles, or defer with Remind me later. |
| Postcondition | Capacity is rebalanced before it bites, with about 6 vehicles freed. |
Close-up of Turtle Bay, fleet availability. The card suggests pooling reception trips to fill buggies, because 18 of 24 buggies are running at only 2 of 6 seats, so pooling frees about 6 vehicles.
Utilization and efficiency
Overworked and idle assets show up early, so a vehicle sitting empty in one place can be moved to where demand is building.
| Aspect | Detail |
|---|---|
| Problem | There was no clear sense of whether the fleet was being used well. |
| Goal | Surface overworked and idle assets early, so an empty vehicle can be moved to where demand is building. |
| Precondition | Utilization and idle figures are reporting for the site. |
| Steps | 1. The card surfaces: an idle pod sitting empty while 4 single-rider sedans queue and 5 assets are under-used. 2. Move the idle pod to where demand is, or defer with Remind me later. |
| Postcondition | The idle asset is repositioned to where demand is building. |
Close-up of Turtle Bay, utilization. The card suggests moving an idle pod to where demand is, because it is sitting empty while 4 single-rider sedans queue and 5 assets are under-used.
Safety and compliance
Driver behaviour and compliance gaps show up before they escalate, so a marshal can be sent while the situation is still recoverable.
| Aspect | Detail |
|---|---|
| Problem | Violations and incidents were reported after they had happened. |
| Goal | Surface driver behaviour and compliance gaps before they escalate, so a marshal can be sent while it is still recoverable. |
| Precondition | Driver safety and compliance flags are reporting for the site. |
| Steps | 1. The card surfaces: a buggy over capacity at 7 of 6, with helmet and tailgating flags rising on the bridge. 2. Send a safety marshal to the causeway queue, or defer with Remind me later. |
| Postcondition | A marshal is sent while the situation is still recoverable. |
Close-up of Turtle Bay, safety. The card suggests sending a safety marshal to the causeway queue, because a buggy is over capacity at 7 of 6 and helmet and tailgating flags are rising on the bridge.
EV charging
A live map of what is working, what is not, and how much energy is left lets vehicles be routed to the chargers that can actually serve them.
| Aspect | Detail |
|---|---|
| Problem | You learned a charger was down only when someone told you. |
| Goal | Hold a live map of what is working, what is not, and how much energy is left, so vehicles route to chargers that can serve them. |
| Precondition | The EV charging network is reporting, each charger over OCPP. |
| Steps | 1. The card surfaces: 2 EVs under 65% and the Turtle Bay charger 84% free. 2. Route the 2 EVs to the Turtle Bay charger after drop-off, or defer with Remind me later. |
| Postcondition | The EVs are routed to a charger that can actually serve them. |
Close-up of Turtle Bay, EV charging. The card suggests routing 2 EVs to the Turtle Bay charger after drop-off, because both are under 65% and the charger is 84% free.
The building model
At this level the site also opens into its building model. The roofs lift off and the interior is read floor by floor on the L1 and L2 selector. The tracked cameras stay pinned in place, and layers over the floor plate show where people are gathering, the temperature each zone is holding, and the airflow being delivered to it.
The Intelligence Operation Centre buildings opened with the roofs removed, camera pins placed across the floor plates, and the L1 and L2 selector on the right.
A floor with the human occupancy heatmap on. Warm zones mark where people are gathering across the floor plate, with the figures at their desks beneath.
The same floor plate with the temperature layer on. Each zone is tagged with the air temperature it is holding, reading 22.3 C across the plate.
Temperature and airflow read together. Each tag pairs the zone temperature, 22.3 C, with the airflow being delivered to it, 927 CFM.
Evacuation and bottleneck severity
The building model also runs a live fire-evacuation simulation. A Pathfinder run plays the alarm forward through the occupied floors, reading clearance time against the safe limit, the egress rate and which routes are carrying it, and the bottlenecks forming across the plates. The left panel holds the run: percent evacuated, estimated clearance against the ASET margin, the egress routes with their per-minute throughput, and the bottlenecks building with their waiting counts.
Bottlenecks surface as cards, and they carry a severity tier so an operator triages worst-first rather than reading every point equally. The three tiers use the same act-now grammar as the recommended-action cards: a state badge, the location, the density against its threshold, the projected impact, and a single recommendation. Read in order of what to take care of first.
Alert. Egress has stalled at a chokepoint and the queue is backing up behind it, the point where a delay becomes a crush. This is the tier to clear first, because flow at the node is already near zero and every second adds to the upstream pressure.
The most urgent tier: egress has stalled at a single doorway and the queue is backing up behind it, the point where a delay turns into a crush.
Critical. A hard limit is close but not yet breached, here a stairwell approaching its descent capacity as two floors' flow merge into it. Flow is still moving, so the window is to relieve the merge before it stalls into an Alert.
A stairwell approaching its descent limit as two floors' flow merges, the squeeze to relieve before it stalls.
Warning. The earliest signal, density climbing in a space while flow still moves freely. There is the most headroom here, so it is caught and watched rather than acted on immediately, before it trends toward Critical.
The earliest signal: density climbing in a corridor while flow still moves, caught with room to act.
| Tier | Trigger | What is happening | Recommended action |
|---|---|---|---|
| Alert | Density past the crush band (5.4 against 4.0 pax/m2) | Egress near zero at the chokepoint, the queue backing into the corridor | Inspect this node |
| Critical | Approaching a hard limit (82 against 85%) | Descent flow nearing stair capacity, a merge conflict projected next interval | Isolate the merge point |
| Warning | Density above the comfortable line (2.8 against 2.5 pax/m2) | Flow still moving, density elevated and trending toward Critical | Check flow detail |
Virtual tour (preview)
The site is also navigable as a CCTV virtual tour, a set of fixed ground-level viewpoints you can move between, with info popups on the assets you pass. This is in preview. The frames below are samples.
Ground level at the site, the arrival view onto the operations campus, with a buggy at the entrance canopy and the live map legend in the corner.
A charger at the Central Transport Hub, an EV connected at the bay beside the parking, before the status card is opened.
The same charger selected. The status card reads RCTH-AC022-127 at the Central Transport Hub, Shura, connected, a Type 2 connector at 22 kW with a single connector. It logs 38 sessions in March, 247 kWh delivered, an average session of 19 minutes and 4.2 kWh, a last session of 12 Mar 08:24, and a last charge from 35% to 70%, reported over OCPP 1.6.
Simulations this view runs
The Operations Manager runs the simulations that read the site as a system under load: how crowds and clearances stack against capacity, how the fleet and microgrid hold up, and where a hazard forces a response. The simulation object is Humans and Vehicles. Each read is summarised below and documented in full in the Simulation chapters.
| Category | Simulation | What it reads | What it drives | Read in full |
|---|---|---|---|---|
| People | Crowd | Gate capacity and staffing against footfall | Position staff and open lanes before an entrance gridlocks | Crowd |
| People | Evacuation | Clearance time and the binding exit | Act on the exit or route that drives the number | Evacuation |
| Traffic | Mobility | The day's load against fleet and charging | Rebalance before the peak, naming the binding constraint | Mobility |
| Traffic | Energy | Clean share against the backup trigger and reserve | Shape dispatch and reserve before the gap compounds | Energy |
| Traffic | Shuttle network | Utilization and the legs running hot | Add or rebalance service before a leg saturates | Shuttle network |
| Traffic | Drop-off forecourt | Throughput through kerb, bays, and staff | Position staff and manage the kerb ahead of the rush | Drop-off forecourt |
| Transport | Safety conflicts | Which crossings flare up under load | Focus staffing and control where risk concentrates | Safety conflicts |
| Transport | Flood and storm surge | Surge reach and depth at critical facilities | Secure and clear before the surge lands | Flood and storm surge |
People
Crowd. Make sure the gates and the people working them keep up, so a busy period never becomes a backed-up entrance. The twin plays footfall forward against gate capacity and staffing, showing which entrances tip first and how much resourcing the peak demands, so staff are positioned and lanes opened ahead of the surge. Read in full
Crowd, Operations read.
Evacuation. A clearance that comes in inside the margin the site is meant to hold, with visibility of where flow stalls. The twin plays the clearance forward across the structure, reporting where flow concentrates and naming the binding constraint, so the team acts on the specific exit that drives the number. Read in full
Evacuation, Operations read.
Traffic
Mobility. Meet the day's demand with the assets on hand, keeping enough vehicles and charging that the system never runs out of slack at the peak. The twin plays the load forward against the fleet and charging network, naming the binding constraint before the peak, so the shortfall is solved on paper. Read in full
Mobility, Operations read.
Energy. Keep the island on its own clean supply, never drifting to where diesel backup is called. The twin plays demand and supply forward against the renewable balance, showing when the clean share drifts toward the backup trigger and how much reserve sits behind it, so dispatch and reserve are shaped before the gap compounds. Read in full
Energy, Operations read.
Shuttle network. Fleet health, keeping utilization balanced so no leg carries more than it was sized for. The twin plays the network forward from the asset's side, showing the routes running hot and the capacity stretched, so service is added or rebalanced before a leg saturates. Read in full
Shuttle network, Operations read.
Drop-off forecourt. Throughput, clearing vehicles fast enough through kerb, bays, and staff that the approach never backs up. The twin plays the arrival pattern forward against forecourt capacity, surfacing where staging falls behind, so staff are positioned and the kerb managed ahead of the rush. Read in full
Drop-off forecourt, Operations read.
Transport
Safety conflicts. Know which crossings flare up under load and warrant staffing or control, and which can be left alone. The twin surfaces the conflict locations and grades them, so attention goes where the risk concentrates rather than across every junction. Read in full
Safety conflicts, Operations read.
Flood and storm surge. Protect critical facilities and assets, where the whole game is lead time. The twin plays a storm, tide, and rainfall scenario forward, showing how far the surge reaches, how deep it gets at the facilities that matter, and how evacuation timing stacks up, so the response is staged before the water is at the door. Read in full
Flood and storm surge, Operations read.
Working in this view
- Open the Operations Manager from the persona bar.
- Read the destination operations strip at the wide view.
- Select a hub to rescope the fleet, utilization, safety, and EV figures.
- Open a site to read its recommended action and dispatch a response.
- Open the site close-up for the consolidated panel, the building model, and the CCTV virtual tour preview.
Alert states and the full incident lifecycle are documented in the Interface Guide.