S1 Fleet is intended for properties where coverage, scheduling and service visibility must be managed across multiple units. It is not simply a larger robot; it is a deployment model built around route sequencing, dock access, network coverage and an assigned operations owner.
The planning mistake to avoid is multiplying the number of robots without changing the operating process. More units can shorten coverage time, but they also create more docks, consumables, fault events and route dependencies. A fleet is useful when the property has enough work and enough management capacity to keep those units productive.
S1 Fleet at a glance
- Body: 450 x 450 x 125 mm commercial platform.
- Suction: 16,000 Pa maximum for high-traffic office floors.
- Battery: 12,000 mAh with up to 3,000 sqm daily coverage in suitable conditions.
- Dock: 10 L high-capacity auto-empty configuration.
- Management: fleet dashboard with task status and consumable visibility.
When one S1 Office is not enough
Start with the simpler S1 Office plan when the cleanable area, operating window and route are straightforward. Move to S1 Fleet when the property has multiple floors, several independent zones, demanding cleaning frequency or a need to coordinate several units from one operating view.
A practical threshold is when one unit can no longer complete the required daily route inside the available window, even after route optimization and dock planning. At that point, compare a second S1 Office with a coordinated S1 Fleet plan, including the service workload created by each additional machine.
Multi-floor logistics
Each floor usually needs its own dock, network assumptions and route owner unless a documented process exists for moving the robot safely. Stair transport should not be improvised. Elevator use requires a controlled procedure, staff awareness and a route that can recover if the robot is interrupted between floors.
For a multi-floor building, document where each unit starts, which zones it owns and where it returns. If a fleet dashboard reports a robot on the wrong floor or outside the expected route, the operations team needs a clear recovery procedure. This is as much a workflow design task as a robotics task.
Route sequencing and operating windows
Plan the highest-visibility areas first, but leave enough time for dock cycles and recovery. A fleet can clean in parallel, yet shared corridors and elevator access create dependencies. Record which unit covers which zone and how a blocked route affects the rest of the schedule.
Use realistic route times for the pilot instead of the maximum coverage claim. Furniture density, door access, security checks and staff movement all reduce effective capacity. A route that looks efficient on a floor plan may need more turns, more recovery or a different start order in real operation.
Network and service ownership
Verify Wi-Fi coverage across every route. Assign a named operator for daily checks, consumable replacement and first-line fault response. The fleet dashboard is useful only when the property has a process for acting on the information.
Keep a small service inventory appropriate to the fleet: filters, brushes, bags and any site-specific wear parts. Record which unit received which consumable and when. Over several months, this makes it easier to compare actual operating hours with service demand and to plan replacements before failures affect the cleaning window.
A useful fleet pilot
Measure coverage, interventions, route time and dock availability across a full operating cycle. Include at least one non-standard week. Compare the fleet result with the existing manual process and define the conditions for adding another floor or unit.
Useful pilot evidence includes percentage of intended route completed, number of staff interventions, average dock cycle, fault frequency and the time needed to recover a blocked route. A pilot that only shows a successful clean demonstrates the robot, not the operating model.
Is S1 Fleet the right starting point?
If the property is a single open office with a long cleaning window, S1 Office planning may be enough. If the building needs multiple robots, central visibility and a repeatable deployment plan, S1 Fleet is the stronger platform. Our deployment services team can review the floor plan and service model.
S1 Fleet is most defensible when the purchase decision includes dock locations, network coverage, a route owner, a pilot scorecard and a spare-parts plan. Those details are also what turn a robotics demonstration into a reliable facility service.