Skip to main content
Avanti Robotics
Book a demo
AVM-WR-014Datasheet

Sector sheets

Five buildings, five drawings, and the one platform underneath all of them.

One dashboard for your whole fleet.

1Different jobs, one set of questions

A robot tidying a supermarket aisle and one doing a night round in a care home do unrelated work. The operational questions behind them are the same four: is it on, is it well, is it doing the right thing, and did the last change reach it safely.

That is how Avanti serves five sectors without becoming five products.

2The five sheets

RetailA robot estate, store by store

Shelf bay, elevation — a scanning passA shelf bay drawn in elevation with four shelves. A travel line runs the length of the bay at low level, marking the path a scanning robot takes past the face of the shelves. Two gaps in the stock on the upper shelves are marked as findings.12Shelf bay, elevationPASS
AVM-FIG-08Shelf bay, elevation — a scanning pass
Key
Shelf bay
Key
Scanning pass
Key
Stock, indicative

The bay is drawn in elevation — the face a robot sees as it passes. The travel line along the bottom is the pass itself, drawn in the standard line for the extreme position of a movable part, because the robot is not the subject of this drawing and is not measured anywhere on it.

HospitalityThe guest notices nothing

Corridor, plan — a scheduled roundA hotel corridor drawn in plan with rooms either side, a lift lobby at one end and a service door at the other. A travel line traces the round from the lobby to the far end and back. One point on the route is marked as an exception raised to the duty manager.1LobbyServiceDuty managerROUND
AVM-FIG-09Corridor, plan — a scheduled round
Key
Corridor and rooms
Key
Scheduled round
Key
Exception to the desk

The corridor is drawn in plan with the rooms it serves either side. The round runs from the lift lobby to the service door and returns, drawn in the standard line for the extreme position of a movable part.

Facilities managementThe same service, in every building you hold

Managed estate — one template, four buildingsA behaviour template at the top connects downward to four buildings drawn as separate blocks. Each building returns a line to a single record block at the foot of the drawing, showing one template deployed four times and one audit record collected back.Behaviour templateBuilding ABuilding BBuilding CBuilding DAudit record
AVM-FIG-10Managed estate — one template, four buildings
Key
Building
Key
Template deployed
Key
Record returned

The template is authored once, at the top. The four buildings beneath it hold nothing else in common — a different client under a different contract — and the drawing makes the point structurally by giving each one its own block instead of repeating a row.

CareProve a change on a few before it reaches everyone

Staged rollout — widen, or withdrawA horizontal bar divided into four stages of increasing width, showing a behaviour change reaching a growing proportion of an estate. A branch below the third stage shows the alternative path: if the error rate crosses the threshold, the change is withdrawn and the estate returns to the previous behaviour.1234Widening while the error rate stays flatChange withdrawnTHRESHOLD CROSSED
AVM-FIG-11Staged rollout — widen, or withdraw
Key
Estate carrying the change
Key
Estate on the previous behaviour
Key
Automatic withdrawal

The bar runs left to right as the change widens. Each stage is drawn wider than the last because the proportion of the estate carrying the change is the only quantity this drawing states. It is stated as a proportion. No robot count appears anywhere on it, because no such count exists.

Events & venuesStand it up, run it, stand it down

Event fleet — enrol, run, releaseA horizontal time bar divided into three phases: a short enrolment phase, a long running phase during which the fleet is monitored, and a short release phase. A bracket beneath the running phase marks the only period for which the fleet is billed.123EnrolRUNNINGReleaseBilled for this period onlySEQUENCE
AVM-FIG-12Event fleet — enrol, run, release
Key
Phase
Key
Fleet running and monitored
Key
Billed period

The bar states an order. It carries no hours and no days, because the length of an event belongs to the customer and this drawing has no business inventing one. What it does state is that enrolment, running and release all happen inside the platform, without a procurement cycle between them.

3What every sector gets

The common foundation — eight parts
PartWhat it does
Fleet healthEvery robot across every site on one screen, with its state and its last reading.
Multi-site groupingRobots organised by site, so one location is managed without touching another.
No-code behavioursWhat a robot does, composed from triggers and actions without writing code.
Staged rolloutA change proven on a small proportion of the fleet before it reaches the rest.
Role-scoped accessEach person sees the sites their job covers, and nothing beyond them.
Anomaly detectionA robot behaving unlike its cohort is surfaced rather than waiting to fail.
UK data residencyYour data is processed and stored on UK servers, under UK law — designed in from the start.
API and webhooksA versioned HTTP surface and signed webhook delivery for the systems you already run.