Every warehouse manager who has watched a robot fleet grind to a halt at peak dispatch knows the real cost of deferred maintenance — and it is never just the repair bill. A structured AMR and AGV preventive maintenance program is what separates operations that run at 95% fleet availability from those constantly firefighting fault codes, battery failures, and navigation drift. With over 62,000 AMR and AGV units deployed globally in 2024 and maintenance costs rising 19% year-over-year, the gap between planned and reactive maintenance has never been more expensive to ignore. This complete checklist covers every critical inspection point — battery health, LiDAR sensors, drive systems, safety interlocks, and fleet software — giving your team the framework to protect uptime, extend asset life, and keep your robots moving with confidence.
Fleet Maintenance & Inspection Guide
AMR & AGV Preventive Maintenance Checklist
Battery Health · LiDAR Calibration · Drive System · Safety Interlocks · Fleet Software
62K+
AMR/AGV units deployed globally in 2024
19%
Rise in fleet maintenance costs year-over-year
30–50%
Battery life lost from deep discharge below 15% SoC
21%
Reduction in plant downtime with automated material transfer
Why Most Robot Fleets Underperform
AMRs and AGVs are treated as self-sufficient machines right up until they aren't. The truth is that each robot is an assembly of interdependent systems — power, navigation, mechanical drive, and safety — and each system degrades on its own timeline. Missing one inspection interval in any of these four areas creates a compounding failure chain that shows up as unexpected downtime weeks later. Here is what is actually failing in most fleets and why.
01
Battery Degradation
Deep discharge cycles below 15% state-of-charge reduce lithium cell pack life by 30–50%. Most fleets have no visibility into individual cell health until the pack fails completely.
Fix: Opportunity charging above 20% SoC + monthly capacity trending
02
Sensor Drift
LiDAR optics accumulate dust that degrades point cloud accuracy, causing route deviation, docking errors, and false obstacle detection — often weeks before a fault code appears.
Fix: Weekly LiDAR cleaning + recalibration after any physical contact event
03
Drive Wheel Wear
Worn tyre tread causes odometry drift that compounds navigation errors across the entire fleet — one robot's position error infects fleet path validation for every unit sharing the same map.
Fix: Monthly tread depth measurement + odometry accuracy spot-checks
04
Safety Interlock Failure
Bumper sensors, emergency stops, and zone interlocks degrade silently. A safety system that tests fine during commissioning may fail to trigger under real operating load months later.
Fix: Monthly functional safety verification under load conditions
Automate Your Robot Fleet PM Schedules
OxMaint tracks each AMR and AGV unit individually by serial number, auto-schedules maintenance by operating hours or battery cycle count, and delivers digital checklists to technician devices — so nothing falls through the cracks.
AMR & AGV Maintenance Checklist
Robot fleet maintenance runs across four time horizons — daily operator checks, weekly technician tasks, monthly mechanical and electrical inspections, and quarterly deep-system verification. Each interval catches failure modes the others cannot. Skipping any level creates a blind spot that eventually becomes an unplanned stoppage.
Daily
Operator Walk-Around
10–15 minutes per unit · Before first shift deployment
Visual & Physical
Inspect robot exterior for physical damage, cracks, or impact marks from the previous shift — any new damage requires logging before the unit re-enters service
Check drive wheels and caster wheels for visible wear, flat spots, debris lodged in treads, or unusual contact with the floor surface
Verify all sensor windows — LiDAR, camera lenses, and ultrasonic transducers — are clean and free from dust, smear, or obstruction
Confirm bumper sensors engage properly with a manual press test — bumper must trigger an immediate motion stop response
Test emergency stop button — press and verify full motion halt; release and confirm normal restart sequence completes without residual faults
Power & System
Check battery state-of-charge before deployment — unit must not enter service below 20% SoC; deep discharge accelerates cell degradation significantly
Verify charging contacts on robot and docking station are clean and making full surface contact — corroded contacts cause incomplete charging cycles
Confirm fleet management software shows the unit online and in communication — no orphaned or offline robots should be deployed without first clearing connection status
Review overnight fault log from the onboard system — document and escalate any unresolved error codes before clearing them for the day shift
Verify the navigation map version on the unit matches the current approved facility map — version mismatch causes route deviations and unexpected stops
Weekly
Technician Inspection
30–45 minutes per unit · Instruments required
Battery & Charging
Record battery voltage at rest and under load — compare against baseline to identify cells losing capacity faster than the pack average
Inspect battery pack casing for swelling, electrolyte leakage, or heat discoloration around terminals — any deformation is a removal-from-service trigger
Verify charging station output voltage and current match OEM specification — undercharging reduces operational range per cycle progressively
Clean charging contacts on both robot and docking station with dry cloth — do not use solvents that leave residue on contact surfaces
Navigation & Sensors
Clean LiDAR optics with manufacturer-approved lens cloth — compressed air alone is insufficient and can embed fine particles into the lens coating
Run automated sensor self-test from onboard diagnostics and confirm all sensor zones report within specification tolerance
Verify camera lens cleanliness on vision-guided units — lens contamination causes pick/place position errors and false collision detections
Check Wi-Fi and fleet communication signal strength across all operational zones — dead spots cause navigation hold events that cascade into throughput losses
Mechanical & Safety
Inspect drive wheel tread depth against minimum specification — worn treads cause odometry error that compounds navigation inaccuracy across the fleet
Check all external fasteners and panel covers for security — vibration from operation gradually loosens fasteners on high-cycle units
Test all safety zone responses — slow zone, stop zone, and emergency zone — by walking an object through each detection boundary during a controlled test run
Review and clear fault history log after documentation — recurring fault codes that reappear weekly indicate an underlying issue requiring investigation, not just repeated clearing
Monthly
Full Mechanical & Electrical Inspection
60–90 minutes per unit · Calibrated tools required
Drive System & Mechanics
Measure drive wheel diameter at four points — acceptable variation less than 2mm; asymmetric wear indicates bearing or alignment issue requiring immediate investigation
Re-torque all drive wheel hub mounting bolts to OEM specification using calibrated torque wrench — follow cross-pattern tightening sequence to ensure even seating
Inspect caster wheel bearings for smooth rotation and lateral play — binding or roughness requires bearing replacement before the unit returns to service
Lubricate articulating joints, lift mechanisms, and guided path tracks with manufacturer-specified lubricant type and quantity — never substitute grease types
Verify brake hold test — apply brake, push against robot manually with rated load on board, and confirm no movement; brake release must be smooth without judder
Inspect payload platform, forks, or conveyor deck depending on unit type — check for deformation, loose fasteners, or material buildup that affects load sensing accuracy
Electrical & Navigation Calibration
Inspect all internal cable harnesses and connectors for chafing, kinking, or connector corrosion — high-cycle robots develop wiring fatigue at articulation points first
Verify sensor-to-chassis alignment by running a position accuracy test against known reference points — deviation above tolerance requires full sensor calibration procedure
Check grounding continuity between chassis, drive motors, and battery system — poor grounding causes electromagnetic interference that degrades sensor accuracy
Perform overload relay and thermal protection test — confirm motor thermal limits trigger protective shutdown before reaching damaging temperatures under sustained load
Record and trend battery capacity against baseline capacity at commissioning — a pack delivering less than 80% of original capacity should be flagged for replacement planning
Back up current parameter set, navigation map, and fleet configuration to external storage — verify backup integrity before closing the maintenance record
Quarterly
Deep System Verification
2–4 hours per unit · Diagnostic software + safety test equipment
Battery & Power Deep Check
Perform full battery capacity test — discharge to minimum safe SoC under controlled load and measure actual versus rated capacity; document trend against previous quarter
Inspect battery management system (BMS) logs for cell-level voltage imbalance — individual cells diverging more than 50mV from pack average indicate early degradation
Test thermal management performance — confirm battery cooling fans or thermal pads are functioning and battery temperature remains within OEM operating range under full charge rate
Navigation & Fleet Software
Perform full facility map re-validation — drive each route segment and confirm robot position accuracy at every node, intersection, and docking station
Review and apply fleet software updates after staging in a test environment — never apply firmware updates directly to the live production fleet without verified rollback capability
Audit fleet path efficiency data — compare actual cycle times against baseline and identify routes where robot performance has degraded, indicating navigation drift or physical obstruction
Safety System Certification
Conduct full safety function verification per ANSI/RIA R15.08 or ISO 3691-4 as applicable — document test results for compliance records and insurance requirements
Test emergency stop chain at system level — verify that a single E-stop event on any unit triggers the correct fleet-wide response without leaving adjacent units in undefined states
Review and update risk assessment documentation if any facility layout, payload type, or operational zone has changed since the previous quarter — safety zones must reflect current operating conditions
AMR vs AGV: Different Robots, Different Maintenance Priorities
Using the same maintenance checklist for AMRs and AGVs is one of the most common reasons robot PM programs fail. These two platforms share a power system and drive mechanics, but their navigation architectures create entirely different failure modes that require different inspection focus areas.
Maintenance Area
AMR Focus
AGV Focus
Navigation System
LiDAR calibration, SLAM map validation, camera lens cleaning — sensors define the entire navigation capability
Magnetic tape condition, wire guide integrity, floor marker visibility — physical path infrastructure must be maintained
Maintenance Frequency
Higher sensor maintenance frequency — weekly LiDAR cleaning; recalibration after any physical contact event
Higher infrastructure maintenance frequency — monthly tape/wire inspection; re-marking when reflectivity drops
Battery Demands
Higher compute load means faster discharge — opportunity charging strategy is critical; LiFePO4 preferred for cycle life
More predictable energy consumption on fixed routes — lead-acid viable where long charge windows exist and capex is constrained
Critical Failure Mode
Sensor drift causing position error — affects route accuracy, docking precision, and obstacle detection simultaneously
Path infrastructure damage — damaged tape or guide wire causes immediate loss of navigation on all units sharing that route
Software Dependency
Fleet management software and map versions must match across all units — version mismatch causes unpredictable routing behavior
Route programming updates require physical infrastructure change validation — software update alone may not resolve a navigation fault
Maintenance Interval Reference
| Maintenance Task | Daily | Weekly | Monthly | Quarterly | Annual / Hours-Based |
|---|---|---|---|---|---|
| Battery SoC check & charging contact inspection | Required | Log trend | — | — | — |
| Battery pack capacity trending | — | — | Measure & record | Full discharge test | Replace at <80% capacity |
| LiDAR / camera sensor cleaning | — | Clean optics | — | Full calibration | — |
| Drive wheel tread depth & odometry check | — | Visual check | Measure & record | — | Replace worn treads |
| Bumper sensor & E-stop functional test | Manual press test | Zone boundary test | — | Full safety audit | — |
| Navigation map validation | Version check | — | — | Full re-validation | — |
| Charging station output verification | — | Voltage & current | — | Full electrical check | — |
| Cable harness & connector inspection | — | — | Visual & pull-test | — | Replace fatigued harnesses |
| Fleet software & firmware update | — | — | — | Staged update review | — |
| Safety function certification (ANSI / ISO) | — | — | — | Full certification | — |
| Parameter & map backup to external storage | — | — | Verify & save | Full backup | — |
From Paper Checklists to Digital Fleet Intelligence
OxMaint captures every battery cycle count, sensor calibration result, and safety test record in a searchable digital history — giving your reliability engineers the trend data needed to predict failures weeks before they happen.
Battery Health: The Number One Fleet Availability Factor
Battery failure is the single most common cause of unplanned AMR and AGV downtime. Yet most fleets manage battery health reactively — replacing packs only after a unit fails to complete a shift. A proactive battery monitoring approach based on state-of-charge protocols and capacity trending can extend pack life significantly and predict replacement needs 4–6 weeks in advance.
Above 80% SoC
Operational
Unit is fit for full shift deployment. Continue standard opportunity charging protocol and log daily SoC at deployment start.
20–80% SoC
Charge Window
Opportunity charging zone. Return unit to dock during breaks or idle periods. Avoid depleting below 20% to preserve cycle life.
15–20% SoC
Charge Now
Unit should be removed from active operation immediately for charging. Operating below 15% accelerates cell degradation and shortens pack lifespan.
Below 15% SoC
Do Not Deploy
Deep discharge risk. Remove from service and charge immediately. Repeated deep discharges reduce pack capacity by 30–50% over time.
Pack Capacity Degradation — When to Replace
90–100%
Excellent — Continue regular PM
80–90%
Good — Monitor quarterly
70–80%
Flag — Plan replacement
Below 70%
Replace — Operational liability
Measure actual capacity quarterly using a controlled discharge test. A pack delivering less than 80% of original rated capacity should be in the replacement planning queue. Waiting for complete failure costs 3–5x more in emergency replacement and lost production time than a planned swap.
Frequently Asked Questions
How often should LiDAR sensors be calibrated on AMRs?
LiDAR optics should be cleaned every week as part of routine technician inspection — dust accumulation on the optic degrades point cloud accuracy before any fault code appears. Full sensor-to-chassis calibration should be performed after any physical contact event, any facility layout change that affects mapped areas, and at minimum every quarter as part of your scheduled preventive maintenance program. Navigation accuracy depends entirely on the alignment between what the LiDAR sees and what the map expects to see, so even minor drift causes compounding route deviation errors that affect the entire fleet sharing that map.
What is the correct battery charging protocol to maximize AGV and AMR pack life?
The most effective protocol for lithium-based packs is opportunity charging — returning units to dock during natural idle periods to keep state-of-charge above 20% at all times. Deep discharge cycles below 15% SoC are the single biggest driver of premature cell degradation, reducing pack life by 30–50% over time. For lead-acid packs used in some AGV deployments, full charge cycles are more beneficial and the battery should not be repeatedly interrupted mid-charge. Always charge at the rate specified by the battery management system — overcharging generates heat that shortens cell life regardless of chemistry. Tracking battery cycle counts in a CMMS allows you to plan pack replacements proactively rather than reacting to mid-shift failures.
How do I know when to replace drive wheels on an AMR or AGV?
Measure drive wheel diameter at four points monthly — acceptable diameter variation is less than 2mm across measurement points. Asymmetric wear indicates a bearing or alignment issue requiring investigation beyond just wheel replacement. Worn treads cause odometry drift that compounds navigation errors across every unit sharing the same fleet map, so wheel condition affects the whole fleet, not just the individual robot. Beyond measurement, watch for floor contact noise, vibration during operation, or any unit consistently deviating from its expected route. Logging wheel condition data by serial number in OxMaint builds the operating hours trend you need to replace wheels proactively before degradation impacts navigation accuracy.
What safety standards apply to AMR and AGV maintenance programs?
The primary standards in the United States are ANSI/RIA R15.08 Parts 1 and 2 for industrial mobile robots, and ANSI/ITSDF B56.5-2019 for driverless automated guided industrial vehicles. In Europe, EN ISO 3691-4:2023 covers safety requirements for driverless industrial trucks. OSHA 29 CFR 1910.147 Lockout/Tagout procedures must be followed before any maintenance activity involving physical interaction with the robot or its battery system. These standards are not legally mandatory in all jurisdictions but are widely adopted as the industry benchmark, and compliance is typically required by insurance carriers and facility safety audits. Your maintenance management platform should capture safety function test results as compliance evidence.
Should fleet software updates be applied immediately when released by the manufacturer?
No — fleet software and firmware updates should always be validated in a staging environment on a single test unit before applying to the production fleet. Even manufacturer-released updates can contain changes to navigation algorithms, safety thresholds, or parameter handling that produce unexpected behavior in your specific facility layout. Maintain a verified rollback capability before any update, and schedule updates during planned maintenance windows rather than during operational hours. Parameter backups must be confirmed complete and restorable before any firmware change. Document every software version change in your CMMS maintenance record so that any performance change after an update can be correlated to the software version with confidence.
Ready to Protect Your Robot Fleet Investment?
OxMaint's robotics maintenance tracking module manages AMR and AGV PM schedules by operating hours, battery cycle counts, or calendar intervals — with digital checklists, technician accountability, and full maintenance history for every unit in your fleet.
