Known condition
Review the last log entry and any open defect, service or inspection action. Confirm the machine is approved for the task and its configuration matches the planned work.
Upkeep / equipment and array
CARE FOR THE CLEANER, TOO
A planned cleaning pass depends on a machine that is fit for its next task and on a solar array left in a known, documented state. Maintenance links the two.
Make readiness an assigned task
The last minutes of a run are easy to overlook: the cleaner returns, the crew notes a small irregularity and the next shift assumes it is ready. A simple, assigned close-out avoids that gap. Identify who checks the equipment, what condition must be recorded, where it is stored and who can release it for use. Apply the manufacturer's maintenance instructions and the site's safety procedures; do not infer that a machine is ready merely because it completed a route.
Maintenance planning should also include the array. Cleaning components, transport and handling can introduce risks if teams do not inspect for unexpected debris, changes or contact marks. Work records should distinguish equipment maintenance from module or site findings, with clear routes for follow-up.
Before the shift
A consistent readiness checkContact components
Check brushes or other cleaning parts against the equipment instructions. Look for wear, damage, contamination or attachment concerns and replace or clean only as specified.
Travel and controls
Inspect wheels, tracks, sensors, guides, cables and control indications using the required procedure. Verify stop, isolation and communication arrangements before positioning.
Work setup
Confirm route, weather, access, crew roles, recovery path and required records. Resolve any difference between the plan and conditions before starting.
After the pass
At close-out, document whether the planned area was completed, which rows or sections were not reached, and any interruption or unusual behaviour. Follow the manual for cleaning and storing the machine; avoid improvised solvents, tools or disassembly. If the equipment shows damage, abnormal sound, unexpected movement or a fault indication, use the site's isolation and reporting process and keep it out of service where required.
Record condition in a way the next operator can understand. A useful note states the equipment identifier, date, work area, issue, immediate action and person responsible for the next step. Avoid vague entries such as “checked” when the actual concern or action needs follow-up.
Build the maintenance rhythm
Use the equipment supplier's instructions to establish inspection, cleaning, service and replacement intervals. The actual schedule may depend on use, environment and operating history, so preserve the source and revision of the instructions used. Do not invent an interval to make a calendar look complete. If site conditions differ from the conditions assumed in a manual, raise that question with the appropriate supplier or technical authority.
A maintenance record can separate routine checks, consumable changes, faults, repairs and release-to-service decisions. Assign an owner to review overdue items and repeated stoppages. Patterns may point to a route problem, handling issue, unsuitable environmental conditions or a machine that needs further evaluation. Those records help adjust the operating plan without claiming that every downtime event has the same cause.
Keep the array in the loop
Record exclusions
Map areas not cleaned and why they were excluded. This prevents an incomplete route from being mistaken for a complete site-wide task.
Log surface observations
Capture changes that need review, but distinguish a visual note from a diagnosis. Use the inspection process and appropriate expertise for assessment.
Protect work boundaries
Follow site procedures around electrical equipment, cables, access and isolation. A cleaning task does not grant permission to alter array components.
Close the handoff
Tell the relevant operations contact when work is complete, interrupted or awaiting follow-up, and preserve the record in the agreed site system.
Maintenance record at a glance
| Record item | Why it matters | Good handoff |
|---|---|---|
| Machine identity and configuration | Connects observations to a specific unit and setup. | Use the site's established equipment identifier. |
| Pre-use condition | Shows what was checked before deployment. | Note exceptions and release status. |
| Work result and route exceptions | Separates completed work from intended work. | Mark locations, pauses and exclusions. |
| Fault, action and owner | Prevents unresolved concerns disappearing between shifts. | Assign a named role and next review point. |
| Post-task storage and status | Clarifies readiness for later use. | Record where it is kept and whether it is available. |
Review what the routine tells you
Revisit the upkeep process when equipment changes, the site layout changes or recurring interruptions appear. Ask operators whether checks are feasible in the time and access available, whether fault reports reach the right person and whether the machine's status is clear to the next shift. If a maintenance burden makes a planned method impractical, that is useful evidence for reconsidering the method or its scope.
The goal is not to keep equipment moving at any cost. It is to make readiness, stop conditions and follow-up visible. A well-maintained fleet still needs a suitable task, a compatible array and a careful operating plan.
Review cleaner fit Connect inspection findings