Operations
Infrastructure must be operated, not merely installed.
Availability is not a property of hardware. It is the result of readiness checks, rebalancing, cleaning, maintenance and fast response — run to a defined standard, every day.
01The operating day
From readiness to the maintenance window.
Step through an example operating day. Times and tasks illustrate the operating model; real schedules are designed per destination.
12:30
First peak
Releases climb at entrances while returns gather in the atrium and food court. Exceptions are queued, not hidden.
Led by
Operations
02The service model
What keeps the network available.
Fleet readiness
Daily inspection, cleaning and charge checks before units enter service.
Rebalancing
Units moved between docks ahead of demand, guided by network state.
Maintenance
Planned servicing and parts replacement, recorded against every unit.
Incident response
Faults withdraw units automatically; staff see the exception and its location.
Remote support
Platform-side diagnosis before anyone walks the floor.
Service records
A history per unit and per dock, for operators and for audits.
Responsibilities between Knull and the destination operator, and any service levels, are defined in each deployment agreement. No generic service levels are published.
Next step
Design the operating model with us.
Operations are scoped during site assessment: staffing, service windows and responsibilities on both sides.