From the first opportunity to the work on site. Bring the organisations, approvals and operating records behind robot services into one place.
Host acceptance and Vendor mobilisation converge here.
From the organisation commissioning the work to the team running the robots, everyone can see what they own and what happens next.
Site teams decide what the service needs to achieve, where it can operate and what must be ready before launch.
Fleet operators mobilise the people and equipment that deliver the work and stay responsible for day-to-day operations.
A shared operating record carries decisions and evidence from the first opportunity through to delivery.
Select each chapter to see what the airport governs, what the Vendor operates and how BellBots keeps both organisations coordinated without collapsing their responsibilities.
Reduce passenger connection friction across four terminals while protecting airside security, accessibility and service continuity.
Sets outcomes, budget, terminal restrictions and acceptance measures.
Reviews the operating context and confirms relevant capability.
Approved outcome brief · AUD 18.4M program envelope
BellCore identifies 14 qualified Vendors with airport operating evidence.
Approved organisations define outcomes and invite qualified autonomous service providers to respond through one governed operating record.
This is not a cosmetic role choice. BellBots configures the correct authority, workflows, operating views and onboarding path for your organisation.
The Host controls where, when and under what conditions robots may operate. The Vendor remains responsible for operating and maintaining them.
Every recommendation discloses its evidence, confidence, freshness, authority and expected impact.
The current policy expires before commissioning. Continuing without renewal would breach the executed contract and leave AUD 4.8M outside the required coverage window.
Vendor: select Quote Q-284 and submit final evidence. Host: hold Site 04 readiness acceptance until coverage is verified.
Explore the exampleReadiness approval blocked
Commissioning window at risk
Contractual continuity breached
Delay exposure increases
Tell us about the site, the service and the people who will run it.
Talk to BellBots