Fleet portal

Compliance at scale

Every AiR session becomes a compliance record: which vehicles are correct, which need attention, and which show repeat pressure loss.

Simulated real-world data being used for demonstration purposes

Verified Care compliance

Not enrolled

A verified four-channel check every 90 days is what keeps tyre warranty cover claimable across the fleet. Status below is derived from sessions completed in this platform.

Verified checks, last 12 months0 of 4
Next check dueFirst check required to enrol
Last verified checkNone recorded

What compliance recovers

Shoulder and inner-edge wearClaimable once inflation is excluded as a cause
Mileage guarantee shortfallEnforceable pro-rata against tread remaining
Cord or wire exposureReferable with a loss-pattern history behind it
Load-related wear on EVs and vansPriced against declared load, not a nominal case
Duty of careTimestamped per-wheel evidence per vehicle, per quarter
The tyre warranty standard

Fleet vehicles

1,284

Checked this month

1,031

Compliant

92%

Critical

14

71 need attention

VehicleTypeDepotDriverDuty cycleAvg correctionLast checkState
FL20 ABCVanManchesterJ. BennettUrban multidrop1.1 PSI0d critical
FL21 BCDEV vanPrestonS. OkaforTrunking1.5 PSI1d compliant
FL22 CDECarLeedsR. AhmedRegional1.9 PSI2d compliant
FL23 DEFEV carBirminghamL. NovakDepot shuttle2.3 PSI3d compliant
FL24 EFGMotorcycleBristolM. PriceUrban multidrop2.7 PSI4d attention
FL25 FGHVanManchesterK. ItoTrunking3.1 PSI5d compliant
FL26 GHIEV vanPrestonJ. BennettRegional3.5 PSI6d compliant
FL27 HIJCarLeedsS. OkaforDepot shuttle1.1 PSI7d compliant
FL28 IJKEV carBirminghamR. AhmedUrban multidrop1.5 PSI8d attention
FL20 JKLMotorcycleBristolL. NovakTrunking1.9 PSI9d critical
FL21 KLMVanManchesterM. PriceRegional2.3 PSI10d compliant
FL22 LMNEV vanPrestonK. ItoDepot shuttle2.7 PSI11d compliant
FL23 MNOCarLeedsJ. BennettUrban multidrop3.1 PSI12d attention
FL24 NOPEV carBirminghamS. OkaforTrunking3.5 PSI13d compliant
FL25 OPQMotorcycleBristolR. AhmedRegional1.1 PSI14d compliant
FL26 PQRVanManchesterL. NovakDepot shuttle1.5 PSI15d · overduecompliant
FL27 QRSEV vanPrestonM. PriceUrban multidrop1.9 PSI16d · overdueattention
FL28 RSTCarLeedsK. ItoTrunking2.3 PSI17d · overduecompliant
FL20 STCEV carBirminghamJ. BennettRegional2.7 PSI18d · overduecritical
FL21 TUDMotorcycleBristolS. OkaforDepot shuttle3.1 PSI19d · overduecompliant
FL22 UBEVanManchesterR. AhmedUrban multidrop3.5 PSI20d · overdueattention
FL23 VCFEV vanPrestonL. NovakTrunking1.1 PSI0d compliant
FL24 WDGCarLeedsM. PriceRegional1.5 PSI1d compliant
FL25 XEHEV carBirminghamK. ItoDepot shuttle1.9 PSI2d compliant

Evidence base

What the compliance and economics numbers rest on

Fleet value is the same physics applied to higher mileage: tread life, energy, downtime and duty of care.

Tread life scales with utilisation

Abrasion tracks the energy dissipated in the contact patch, so a fleet running high mileage on soft tyres pays the wear penalty faster than a private car.2008,1992

Energy is a line item

A 10% rolling-resistance change is worth roughly 1-2% of fuel, and inflation is the cheapest way to move it.2006,2017

Structural failure risk is operational risk

Sustained under-inflation drives casing fatigue and roadside failure, and crash data links large pressure errors to tyre-related crashes.2006,2012

Records are the compliance artefact

A dated, per-tyre record against an approved specification is what turns a maintenance intention into evidence.2025,2026

These are published third-party sources, not AiR simulation. The full bibliography - peer-reviewed papers, reference monographs, government reports, international standards and official statistics - lives in the science lab.

Open the research and full bibliography

Edge session, synchronised

Fleet-wide edge and federated-learning position

These figures are read from the same persisted edge-compute session used on the simulator page. Change the tier, connectivity or power state there and this view follows.

F1 · Jetson Orin NXFull cloud-connectedMains, nominal thermals1,000 nodes62% host share cap45% duty cycle

Available per node

157TOPS

157 TOPS peak, power derated

Safety reservation

43.9TOPS

Never pre-empted

Shared compute

97.3TOPS

62% of the node

Fleet useful capacity

141,200TOPS

0.0455% of the 100 MW reference

Scheduler allocation

Tyre-safety control looprunning18.9 TOPS
On-unit local intelligencerunning25 TOPS
Federated fine-tuningrunning40.8 TOPS
Scheduled tenant inferencerunning56.5 TOPS

Federated round in this session

Participating nodes947
Queued for later delivery53
Aggregate delta volume246.2 MB
Round duration6.1 min
Rounds per day59
Fleet compute draw36 kW
  • A host share above 60 percent should be contracted with an explicit thermal, power and privacy schedule.

Federated learning behaviour

Local trainingFine-tuning runs on data that never leaves the node or its regional trust boundary.
Update extractionOnly model updates or anonymised aggregates are transmitted, never raw vehicle or user records.
Secure aggregationRegional anchors aggregate updates so the control plane cannot attribute an update to one node.
Differential privacyNoise is added where a research use case justifies it, at the cost of some model fidelity.
National reconstructionThe central model is reconstructed from aggregates and redistributed as a signed package.
Tenant isolationExternal compute tenants run in separate namespaces with no route to vehicle, driver or safety data.

Data flow, stage by stage

  1. 01

    Sense · Node, L0

    Pressure, temperature, valve state and session context captured at the channel. Raw sensor data never leaves the enclosure in raw form.

  2. 02

    Decide locally · Node, L1

    The deterministic engine selects an approved profile, applies the thermal allowance and safety clamp, and drives the channels. No network dependency exists at this stage.

  3. 03

    Infer and redact · Node, L2

    Onboard inference runs anomaly, leak-pattern and integrity checks, then the redaction pipeline strips identifiers and derives features before anything is queued for transport.

  4. 04

    Sign and classify · Node, L2

    The session record is signed with the device key and each outbound message is tagged P0 to P4, which fixes its transport, priority and residency for the rest of its life.

  5. 05

    Transport by class · L3

    P0 and P1 take whichever path is available, LoRa included. P2 to P4 wait for IP. Bulk traffic is deferred to off-peak windows and never touches the resilience plane.

  6. 06

    Broker regionally · Anchor, L4

    Anchors cache models, broker compute work units, forward Reticulum traffic and hold store-and-forward queues for nodes that are currently unreachable.

  7. 07

    Reconcile centrally · Control plane, L5

    Signed sequence numbers and idempotent processing mean queued events replay safely when IP returns. Duplicate delivery over two planes is expected and harmless.

  8. 08

    Aggregate and serve · L6

    Personal records land in the UK sovereign service, anonymised trends in the analytics plane, tenant outputs in an isolated namespace. The three are never joined.

Adjust this session in the edge workload simulator

Compliance as a by-product

Every session writes an auditable record for the vehicle.

/Compliance/Exceptions/Duty cycles/Cost per mile/Downtime avoided/Audit trail/Compliance/Exceptions/Duty cycles/Cost per mile/Downtime avoided/Audit trail

Fleet economics

Tyres are a controllable line, not a fixed cost

Fleets already know their tyre spend. What they cannot see is which vehicles ran under-inflated, for how long, and what that did to replacement intervals - because nobody records a check that nobody performed.

Vehicles under management

0

Compliance rate

0.0%

Open exceptions

0

Repeat deviation, probable slow punctures, missed checks.

Modelled tread life gain

0%

From removing sustained under-inflation across the fleet.

Every session is an evidenced check with a timestamp, a location, a before value and an after value. That converts a policy statement into an audit trail suitable for an operator licence or an insurer conversation.

  • Per-vehicle check history with pass, correct or exception status
  • Automatic escalation when a vehicle deviates repeatedly
  • Driver-level and depot-level views without exposing personal data
  • Exportable records for compliance and insurance review

Questions

Straight answers

No. The measurement happens at the machine, so a mixed-age fleet is covered from day one without retrofitting anything.
Session records are designed to be pushed into an existing telematics or fleet management platform through the documented API rather than replacing it.