Robotic cleaning fleet
Sizing the number of cleaning robots a plant needs, and deciding gap by gap where a supported bridge will be installed.
π€ Robotic Module Cleaning sizes the cleaning fleet: how many robots the plant needs to cover every module. It works from the layout you have placed, so the answer reflects the real geometry β where the control rooms landed, where the arresters sit, where obstructions broke the rows β rather than a rule of thumb applied to a capacity figure.
The output is a count you can procure and price against, and it reaches the bill of materials.
Where it is
The button is the second of five in the Studies card on the Tools tab, between π Simulation with AC Capacity and Robot count from DXFβ¦. Like every study except Robot count from DXFβ¦ it is greyed out until a layout exists, because the count is measured off the placed layout.
To size a fleet from a plant drawing instead β a layout you did not generate here β use Robot count from DXFβ¦. It runs the same count on any plant layout DXF and adds nothing to the project; see Robot count from DXF.
Before you size the fleet
More than generating the layout: settle the equipment that breaks the rows before you start ticking gaps, because that equipment is what creates most of them.
| Decide first | Why it matters here |
|---|---|
| Lightning arresters | An arrester clears the tables under its pile and shadow, which produces a gap blocked by equipment. Placing them later changes the gap list |
| Control rooms and unit substations | Every building footprint clears tables around it and interrupts the lines that ran through it |
| Obstructions you draw by hand | Each one breaks the rows it crosses, so each one can add segments |
| Half tables and Maximize placement | Both change how rows are packed, and a staggered plant has a different set of gaps from a gridded one |
The gap list is a measurement of one particular layout, not a property of the site. If any of those change afterwards, open the window again and read it.
How a robot moves
A robot drives along the module frames of one cleaning line. The frames are its track: it travels the continuous run of structure, cleaning the modules it passes, and it can only go where that run continues.
That is why the direction of a cleaning line is not a setting but a consequence of the mounting type. The window's strip states it for the design you are in.
The strip reads robots travel westβeast along each table row. Rows of MMS tables run east to west, so the continuous run of frames along a row is the eastβwest direction, and a line follows one row of tables across the plant.
In both cases the rule is the same β the line follows the frames β and the two answers differ only because the frames run differently. A robot cannot cross from one line to the next; each line is its own track.
The window
Robotic module cleaning opens as one window, and it can be maximised for a long gap list. Across the top a strip reports n cleaning lines, the direction of travel, and a chip with the table count. The inputs and the result sit on the left; the gaps on the right; the action in the footer.

ROBOT
Four fields. On a tracker plant the unit reads "trackers" instead of "tables".
| Field | Default | Range | What it does |
|---|---|---|---|
| Travel per charge (m) | 0, shown as no limit | 0β100,000 | How far a robot travels on one charge |
| Standard bridge span (m) | the gap already configured | 0β50 | The widest gap a standard bridge spans |
| Skip lines up to (tables or trackers) | 0 | 0β1,000, in steps of 0.5 | A segment carrying this many units or fewer gets no robot |
| Out and back β must return on the same charge | ticked | β | Doubles the distance a robot has to cover, because it travels its segment twice |
Travel per charge ships at 0, so out of the box there is no battery constraint at all and every cleaning segment gets one robot. Enter a real range and it becomes a second reason for the fleet to grow, on top of broken lines.
Out and back ships ticked, and it halves the effective reach, because the robot travels the segment twice. Untick it if the robot need not return on the same charge.
Standard bridge span starts from your own geometry rather than a constant, so it is consistent with the layout on first open. It is taken from the Gap between MMS-Tables on a fixed-tilt plant, which ships at 1.0 m β see Table configuration β or from the NβS service gap between units on a tracker plant, which ships at 2.0 m; see Tracker configuration. Where that gap is zero the span starts at 2.0 m. Any gap at or under the span β plus 0.25 m of placement tolerance β is crossed as a matter of course; anything wider is a decision, which is the next section.
Skip lines up to ships at 0, so nothing is discarded until you raise it. It steps in halves because a half unit counts as 0.5 β the section on short segments below covers what raising it does and does not do.
RESULT
A verdict banner gives the answer, the same verdict as Robot count from DXF:
| When | Headline | Detail |
|---|---|---|
| Nothing split, no robots added for range, nothing skipped | n robots β one per row (column on trackers), with a tick | "r rows, no wide gap left unbridged." or "r rows, k wide gaps bridged." |
| Otherwise, with gaps ticked | n robots with k bridges, with an exclamation mark | What the count is made of: "+a for split rows", "+b for battery range", "βc for skipped segments", each only when it is not zero |
| Otherwise, nothing ticked | n robots at most, with an exclamation mark | The same parts |
Any crossing gaps ticked for checking add "n crossing bridge(s) is/are preview only." to the end. On a plant with nothing placed the banner reads No tables placed β "Generate a layout first, then size the cleaning fleet." β and the primary button reads Add to BOM, greyed out, with the reason "No tables to clean".
Four tiles sit under the banner, each with a line under its figure:
| Tile | What it reports | The line under it |
|---|---|---|
| Standard bridges | The bridges of the standard span the lines need | "gaps up to x m", or "+ n supported" once supported bridges are ticked |
| Longest segment | The longest stretch one robot serves | "no range limit", "within range", or "+n robot(s) for range" |
| Cleaning segments | How many segments the lines are broken into | "no broken lines", "n unbridged gap(s)", or "k skipped Β· βn robot(s)" |
| One full pass | One complete cleaning pass over the plant | "out and back" or "one way" |
Lengths are in whole metres, however long.
A wide gap is a decision, not an assumption
This is the part of the window that does the real work, and the reason the tool exists rather than a formula.
The right-hand side lists every gap in the plant wider than a standard bridge, individually, with its measured span and where it is. Its heading reads GAPS TOO WIDE FOR A STANDARD BRIDGE Β· n when some of the gaps are at equipment, and GAPS IN OPEN GROUND Β· n when none are; n counts every wide gap.
A filter above the list splits it three ways, each segment with its count: Inside the boundary, Crossing it, and At equipment β the last only when such gaps exist. Bridge all n and None tick or clear the rows the filter shows, not the whole list; on Crossing it the first reads Preview all n.
| Column | What it holds |
|---|---|
| Bridge | The tick box β your commitment to install a supported bridge there |
| Table row (Tracker column on a tracker plant) | Which cleaning line the gap is on β "Row n" or "Column n" |
| Gap | Its measured span |
| Saves | What bridging it is worth: "1 robot"; "up to 1 robot" once a range or a skip threshold is set; or "none Β· leaves the site" |
| Blocked by | What sits in the gap β an arrester, a building, an obstruction β and whether the bridge would cross the boundary. Shown only under At equipment |
A note under the list says what the filtered gaps are. Under Inside the boundary: "These gaps are open plant area, not equipment. Bridge one only if the tables there will really be connected." Under Crossing it: "A straight bridge here would leave the plant boundary. Tick one to draw it on the plot in red and check the crossing; it does not reduce the fleet." With no wide gaps at all it reads "No wide gaps β every cleaning line is continuous at the x m bridge span."
Each tick box is a commitment:
- Ticked means you will install a supported bridge across that gap. The robot drives over it, the line stays continuous, and the fleet count drops by the figure in Saves.
- Left unticked means the line is broken there. The stretch on the far side becomes its own segment, and that segment keeps its own robot.
Nothing is bridged unless you tick it. The application will not assume a bridge anywhere, at any span, for any reason. A wide gap is a civil and structural commitment with a cost and a design behind it, and assuming it away would produce a fleet count that quietly depends on structures nobody has agreed to build.
As you tick, the bridges are drawn on the plot behind the window, so you can see where each one lands: bridged gaps in pink, crossing gaps in red, skipped segments in amber. A bridge that would leave the site is a preview only β it is drawn for checking and never lowers the count.
The Blocked by column is there because the two kinds of gap are not the same kind of decision. A gap in open ground needs a longer span of the same idea β usually straightforward. A gap blocked by equipment needs a bridge that gets a robot over or around something solid, which may be expensive, may be impossible, and may be a reason to move the equipment instead while the layout is still editable. The At equipment filter shows you only those.
Every tick is a structure someone has to design, buy and install. Tick the gaps you have decided to bridge, not the gaps that would give you a convenient fleet count. Bridge all is there for the case where you genuinely will.
How the fleet is counted
Sizing starts from the simplest possible answer and grows it for two reasons.
One robot per line to start. Each cleaning line gets one robot. On a plant of unbroken rows with no range limit, which is what the shipped Travel per charge of 0 gives you, that is the whole answer, and the verdict says n robots β one per row.
Broken lines add robots. Every unticked wide gap splits a line into segments, and each segment needs its own robot, because no robot can cross the gap to reach the rest of the line. A line broken in two places carries three robots where an unbroken one carried a single robot. The verdict's "+a for split rows" counts how many robots exist only for this reason.
Travel per charge adds robots. With a range entered, a robot that cannot finish its segment on one charge needs company β the segment is shared between more than one robot. With Out and back ticked, the distance to be covered is the segment travelled twice, so range binds sooner.
The two causes compound: a long line broken into segments may still exceed the range within each segment. That combination is what makes an eyeballed estimate unreliable on a real plant, and it is why the count is worth deriving.
Segments too short to be worth a robot
A segment can be a stub β two tables cut off in a corner by an obstruction. A dedicated robot for it is not a sensible procurement, so Skip lines up to sets a threshold:
A segment β a whole line, or a stretch between unticked gaps β whose weighted unit count is at or below the threshold gets no robot.
- The count is weighted: a half unit counts as 0.5, so two half tables count the same as one full table. That is why the field steps in halves.
- The field ships at 0, which counts every line however short. Raising it discards more short stubs and lowers the fleet count.
- Whatever the threshold discards still has modules on it. Those tables are not covered by the fleet the count describes, so decide how they will be cleaned β by hand, or by a robot moved there β rather than letting the threshold hide them.
Live recalculation, and where the result goes
Everything in the window recalculates live. Tick a gap and the verdict moves immediately; change Travel per charge or the bridge span and it moves again. Work the list top to bottom, watching the Saves column, and you can see directly which bridges pay for themselves in robots saved.
Start with everything unticked
Because nothing is bridged unless you tick it, the first count on a new fleet is the honest baseline, n robots at most: the fleet required if you build no additional bridges at all. Note it before you change anything β it is the upper bound, and the figure every bridge is measured against.
Set the robot inputs before touching the gap list
Standard bridge span decides which gaps are listed at all; Travel per charge and Out and back decide how long a segment one robot can serve. Settling them first stops you re-deciding the same gaps twice.
Work the open-ground gaps
Filter to Inside the boundary: every gap there is open ground. Tick the ones you will genuinely install and watch the count fall.
Work the equipment gaps last, and sceptically
Filter to At equipment. Each of these needs a bridge that gets a robot past something solid. Some are straightforward, some are not worth building, and some are a reason to move the equipment while the layout is still editable.
Add the fleet to the bill of materials
The primary button in the footer names what it will add: Add n robots + m bridges to BOM, where m counts the standard-span bridges and the supported bridges you ticked. Click it, and the count and the bridges become materials lines; the status line reads "Robotic cleaning: n robots for m cleaning lines β added to the BOM." Close leaves without adding anything and puts the bridges drawn on the plot back as they were before the window opened.
The result then reaches three places:
- The Summary view. A Cleaning robots row appears in the Site group of the Plant sheet. See Summary view.
- The bill of materials. The fleet becomes Cleaning robot and Cleaning robot bridge lines, the bridges split into standard and supported, so the ticked gaps are carried as a scope item and not only as a lower robot count.
- The design report, which says whether robotic cleaning was sized. See Design report.
What happens when the layout changes
The fleet you added is saved with the project, with your answers and ticks. The window reopens with them, in the session and after opening the project. Only Add keeps them: Close without adding keeps nothing.
When the layout is generated again, the fleet is re-sized for the new layout with the answers you gave. Each ticked gap carries to the same gap in the new layout, and those that no longer exist are said once on the status line: " | Robotic cleaning: 1 ticked gap no longer exists and was dropped".
A new site drops the fleet, with "Robotic cleaning: the fleet was sized for the previous site and was dropped. Size it again under Tools."
The bill of materials never carries a fleet you did not ask for. Those lines appear only after you have run this study and clicked the add button, so a materials list from a plant where you never opened this window contains no cleaning fleet at all β not a zero, not an estimate. If a bill of materials has to include the cleaning system, run this first. See Bill of materials.
The soiling loss in the performance ratio is a separate input that you set, and it is not derived from the fleet. See Loss breakdown. The two belong together in a report, though: a soiling assumption presumes a cleaning regime, and this is where the regime gets counted.
Where to go next
Bill of materials
Where the fleet and its bridges appear as materials lines, and when
Table configuration
The inter-table gap that sets the default bridge span
Sizing from an AC capacity
The first study in the same card, run from a placed layout
Robot count from DXF
The same count run on any plant layout drawing, without a layout
Sizing from an AC capacity
Work backwards from a contracted AC capacity and a target DC/AC ratio to a layout capped at the capacity you are allowed to build.
Robot count from DXF
Size a cleaning-robot fleet from any plant layout drawing, without generating a layout and without changing the open project.