Robots and cobots don't announce when they're about to fail — they degrade gradually through joint wear, sensor drift, software decay, and safety system erosion until a cell stops, a product is damaged, or a person is hurt. OxMaint's Robotics & Cobot Maintenance Tracking automates every PM task across your robotic systems — joint inspections, sensor calibration, software checks, and safety system verification scheduled and logged so reliability never silently degrades. Book a free demo to see automated robot PM in action.
Checklist · Robotics & Automation · Preventive Maintenance · 2026
Robotic and Cobot System Preventive Maintenance Checklist
A complete zone-by-zone PM checklist for cobots, robotic arms, and AMRs. Joints, sensors, grippers, software, and safety systems — organised by daily, weekly, and monthly schedules so every failure mode is caught before it stops production.
4
maintenance zones every robotic system requires on a structured PM schedule
55%
of unplanned robot downtime is caused by deferred joint and sensor PM
100%
task traceability — every PM result timestamped, technician-signed, and audit-ready
Zero
missed PM intervals when OxMaint auto-schedules every robot task per shift and cell
Schedule:
Daily Pre-shift check every production day
Weekly Once per maintenance week
Monthly Full overhaul and calibration
Zone 1: Joints & Mechanical
→
Zone 2: Sensors & Grippers
→
Zone 3: Software & Calibration
→
Zone 4: Safety Systems
PM Coverage Across the 4 Robotic System Zones
Every zone on a robotic or cobot system generates maintenance data — torque readings, sensor logs, software version records, and safety test results. Without structured PM, performance degrades silently until a cell stops or a safety incident occurs. OxMaint captures every task at completion — traceable per robot, per shift, and per cell, instantly available for OEM, insurance, and compliance audit review.
Zone 1
Joints & Mechanical
DailyJoint movement and abnormal noise check
WeeklyLubrication and cable inspection
MonthlyFull joint torque and wear assessment
Zone 2
Sensors & Grippers
DailyForce/torque sensor and gripper check
WeeklyVision system and proximity sensor clean
MonthlyFull sensor calibration and gripper audit
Zone 3
Software & Calibration
DailyError log and path accuracy review
WeeklyBackup verification and patch status
MonthlyFull TCP calibration and program audit
Zone 4
Safety Systems
DailyE-stop and safety scanner test
WeeklyCollaborative speed and force limit check
MonthlyFull ISO 10218 / TS 15066 safety audit
Before You Start: Configure Your Robot PM Schedule
Effective robot PM starts before the first shift. Teams must register every robot, cobot, and AMR with asset IDs, configure PM intervals per system type and duty cycle, assign maintenance responsibilities, and record baseline performance readings — so every scheduled task is meaningful and every deviation from baseline is immediately actionable. OxMaint's setup wizard configures your full robot PM schedule in under a day.
Pre-Checklist: Robot PM Platform Setup
All robots, cobots, and AMRs registered with asset IDs
Every robotic system registered with make, model, serial number, firmware version, cell assignment, and install date before PM scheduling begins.
Baseline joint torque, TCP accuracy, and cycle counts recorded
Joint torque readings, TCP positional accuracy, error rates, and cumulative cycle counts recorded per robot as performance baselines before PM intervals begin.
OEM PM intervals and lubrication specs configured per robot model
PM frequencies set per OEM recommendation and adjusted for duty cycle. Food-grade or clean-room lubricant grades linked to the relevant joint tasks where applicable.
Safety validation records and risk assessment documents linked
Current ISO 10218 / ISO/TS 15066 risk assessment, safety function validation records, and E-stop test procedures linked to each robot asset record before safety PM tasks are scheduled.
ZONE 1
Joints & Mechanical Systems — PM Checklist
Joint wear is the leading cause of positional drift and unplanned robot downtime. It develops gradually through cumulative cycle counts, contamination ingress, and deferred lubrication — and it doesn't announce itself until repeatability failures start showing up in product quality or the robot throws a position error. Check joints at every shift start and never defer lubrication beyond the OEM interval.
| # | Task | Schedule | Acceptance Criteria | Sign-Off | |
|---|---|---|---|---|---|
| 1.1 | Joints moved through full range at shift start. Any grinding, clicking, or squealing noted and escalated before production. | Daily | Smooth, quiet motion through full range. Any abnormal noise triggers maintenance hold before production. Result logged. | ________ | |
| 1.2 | Arm and base structure inspected for cracks, chips, or dents that could affect structural integrity or create a contamination risk. | Daily | No cracks, chips, or structural damage. Any damage triggers immediate cell stop and engineering assessment. | ________ | |
| 1.3 | Tool changer or wrist flange checked for secure locking, correct seating, and absence of play or rocking that could indicate wear in the coupling mechanism. | Daily | No play, rocking, or incomplete locking detected. Any loose or suspect coupling triggers cell stop before production begins. | ________ | |
| 1.4 | All joint lubrication points serviced per OEM specification and cycle-count trigger. Type, grade, quantity, and technician ID logged. | Weekly | All lube points confirmed serviced with correct OEM-specified grade. Quantity within spec. Logged with cycle count. | ________ | |
| 1.5 | Power and signal cables inspected for chafing, kinking, or connector fretting. Cable clips and drag chain condition checked. | Weekly | No chafing, kinking, or visible wear on any cable. Drag chain intact and moving freely. Defective cables scheduled for replacement. | ________ | |
| 1.6 | Robot base mounting bolts checked for torque to specification. Vibration from the cell floor can loosen base fasteners over time, causing positional drift that is misdiagnosed as software or calibration issues. | Weekly | All base mounting fasteners at specified torque. Any loose bolt triggers TCP recalibration after re-torquing. Results logged per bolt position. | ________ | |
| 1.7 | Joint torque and backlash measured against OEM spec and baseline. Trended over time to catch progressive wear before positional errors occur. | Monthly | Torque and backlash within OEM limits. Trend increase above threshold triggers joint service before next production campaign. | ________ |
PM records: joint motion check, structural inspection, lubrication log, cable condition, torque and backlash trend — timestamped, technician-signed, OEM warranty-ready
OxMaint Robotics Maintenance Tracking
Joint PM tasks triggered automatically at OEM cycle-count intervals — lubrication, torque checks, and cable inspections assigned to the right technician and logged against the robot asset record. No spreadsheets, no missed intervals. See how OxMaint tracks robot joint PM.
ZONE 2
Sensors & End-Effectors — PM Checklist
Force/torque sensor drift and gripper wear are the most common causes of product damage and missed picks in robotic pick-and-place applications. A 5% drift in force feedback is invisible to the operator but produces measurable product damage or drop rates. Calibrate sensors at every defined interval — never assume they hold between calibrations in a high-cycle environment.
| # | Task | Schedule | Acceptance Criteria | Sign-Off | |
|---|---|---|---|---|---|
| 2.1 | Force/torque sensor zero-point checked at shift start via controller zeroing routine. Offset above threshold triggers recalibration before production. | Daily | Zero-point offset within ±2% of rated capacity. Offset above threshold triggers recalibration before production. Logged. | ________ | |
| 2.2 | End-effector inspected for wear, contamination, cracks, or missing components. Jaw alignment and closing force checked against specification. | Daily | Gripper components intact and clean. Jaw alignment and closing force within specification. Any worn component replaced before run. | ________ | |
| 2.3 | Gripper finger wear measured and compared against the replacement threshold defined in the application spec. Worn fingers cause pick failures and product damage before they are visually obvious. | Daily | Finger wear within replacement threshold. Fingers approaching limit flagged for scheduled replacement before the next shift. Measurement logged. | ________ | |
| 2.4 | Vision cameras and proximity sensors cleaned with approved materials. Checked for damage, loose mounts, or lens contamination. | Weekly | Lenses optically clear. Mounts secure. No physical damage. Detection verified against reference object after cleaning. | ________ | |
| 2.5 | Suction cup components — cups, valves, tubing, filters — inspected for cracking or blockage. Vacuum level measured against specification. | Weekly | Cups pliable with no cracking. Vacuum level within ±5% of specification. Filters clean. Blocked or hardened components replaced. | ________ | |
| 2.6 | Tool changer electrical and pneumatic connections tested for signal integrity and leak-free operation. Repeatability of tool change cycle verified with timed run of 5 consecutive exchanges. | Weekly | All signals confirmed. No pneumatic leaks. 5/5 tool change cycles completed without error or positional deviation. Results logged. | ________ | |
| 2.7 | Full calibration suite: force/torque against certified reference, vision system positional accuracy, and proximity sensors against known reference distances. Results archived. | Monthly | All sensors within OEM accuracy specification. Calibration results archived per sensor asset ID. Out-of-spec sensors replaced or returned to OEM for recalibration. | ________ |
PM records: sensor zero-point, gripper condition, vision system clean, vacuum check, full calibration suite — timestamped, technician-signed, OEM and quality audit-ready
55% of Robot Downtime Is Preventable
Most unplanned robot stops trace back to deferred sensor and gripper PM — not software faults. OxMaint schedules every sensor check and gripper inspection automatically, raising work orders when readings drift before a cell stop occurs. See the sensor PM workflow live.
ZONE 3
Software & Calibration — PM Checklist
Software and calibration issues account for the majority of product quality failures in robotic systems that are otherwise mechanically sound. TCP drift of as little as 0.5mm in a precision welding or dispensing application produces rejects. Back up every program before every maintenance window and verify TCP calibration whenever any mechanical work has been done on the robot.
| # | Task | Schedule | Acceptance Criteria | Sign-Off | |
|---|---|---|---|---|---|
| 3.1 | Controller error log reviewed for fault codes, current anomalies, or position errors from the previous shift. Recurring faults flagged even if production was unaffected. | Daily | No unreviewed fault codes from previous shift. Recurring faults trigger a work order even if production was unaffected. Log exported and archived. | ________ | |
| 3.2 | Path accuracy spot-checked with a test cycle. TCP position compared against programmed points. Deviation outside tolerance triggers recalibration before production. | Daily | TCP positional accuracy within ±defined tolerance for the application. Deviation above threshold triggers TCP recalibration before production continues. | ________ | |
| 3.3 | All programs backed up to designated location. File integrity verified and timestamp confirmed current. Previous version retained per change control. | Weekly | Current backup confirmed on designated server. File integrity verified. Previous version retained. Backup location and filename logged against robot asset record. | ________ | |
| 3.4 | Firmware and safety software patch status reviewed against OEM release notes. Pending patches assessed and scheduled for planned downtime installation. | Weekly | No unapplied safety patches outstanding beyond 30 days. Patch assessment documented. Installation schedule confirmed for pending updates. | ________ | |
| 3.5 | Joint mastering / zero-point calibration verified by running the robot to its mechanical zero position and confirming encoder values match the stored reference. Drift from reference indicates mechanical or encoder wear. | Weekly | Encoder values at mechanical zero match stored reference within OEM tolerance. Drift above threshold triggers full re-mastering before production. | ________ | |
| 3.6 | Cycle time trend reviewed against the baseline production cycle time. Increasing cycle time on a nominally healthy robot indicates joint friction, communication latency, or path execution issues before they surface as faults. | Weekly | Cycle time within ±3% of baseline. Consistent increase above threshold triggers a joint and software diagnostic before next planned maintenance window. | ________ | |
| 3.7 | Full TCP calibration using OEM method. World and user frame verified. All waypoints confirmed against physical reference points. Results archived in CMMS. | Monthly | TCP calibration within OEM positional accuracy specification. All waypoints confirmed. Calibration result and date archived per robot asset ID. | ________ |
PM records: error log, path accuracy check, program backup, patch status, TCP calibration — timestamped, engineer-signed, change-controlled and OEM-compliant
100% Software Change Traceability
Every program backup, firmware patch, and TCP calibration logged against the robot asset record with engineer ID and timestamp in OxMaint. Full change control audit trail generated automatically — no manual spreadsheet updates. Book a demo to see robot software PM in OxMaint.
ZONE 4
Safety Systems — PM Checklist
For collaborative robots operating under ISO/TS 15066, safety system integrity is not a compliance exercise — it is the engineering basis for human-robot coexistence. A safety scanner with contaminated optics, an E-stop with a worn contact, or a force limit that has drifted above its validated threshold can allow a dangerous situation to occur without triggering a protective stop. Test every safety function at every defined interval without exception.
| # | Task | Schedule | Acceptance Criteria | Sign-Off | |
|---|---|---|---|---|---|
| 4.1 | All E-stop buttons — robot, pendant, and cell perimeter — activated and confirmed to stop motion within required stop time. Reset procedure verified functional. | Daily | All E-stops trigger immediate motion stop. Reset confirmed requiring deliberate operator action. Any E-stop failure triggers immediate cell lockout. Result: Pass / Fail | ________ | |
| 4.2 | Safety scanners, light curtains, and area sensors tested by interrupting each detection zone. Robot confirms stop or speed reduction within validated response time. | Daily | All safety zones trigger correct protective response. Stop or speed reduction within validated response time. Failure triggers immediate cell lockout. Result: Pass / Fail | ________ | |
| 4.3 | Cobot speed and force limits verified against validated risk assessment values via controller diagnostic mode. Any deviation is a safety-critical non-conformance. | Weekly | Speed and force limits match validated risk assessment values exactly. Any deviation is a safety-critical non-conformance — cell isolated until corrected and re-validated. | ________ | |
| 4.4 | Safety scanner optics and light curtain emitters/receivers inspected and cleaned. Zone boundaries re-verified after cleaning. Alignment drift corrected before production. | Weekly | Optics clean and undamaged. Zone boundaries confirmed after cleaning. Any alignment drift corrected and re-tested before production resumes. | ________ | |
| 4.5 | Physical guarding — interlocked gates, fixed guards, and anti-restart devices — inspected for structural integrity, correct function, and absence of bypass attempts or damage. | Weekly | All guards intact and correctly positioned. Interlocked gates confirmed functional — opening stops robot. No evidence of bypass. Any damage triggers immediate cell isolation. | ________ | |
| 4.6 | Safety PLC or safety controller diagnostics reviewed for any internal faults, redundancy channel errors, or self-test failures logged since the previous check. Safety system self-diagnostics must be reviewed, not just cleared. | Weekly | No unreviewed safety controller faults. Any redundancy channel error treated as a critical finding requiring immediate investigation before production resumes. | ________ | |
| 4.7 | Full safety audit per ISO 10218 / ISO/TS 15066: all safety functions tested to specification, results documented, and signed off by a competent person independent of daily operations. | Monthly | All safety functions pass full specification test. Audit report completed and signed by independent competent person. Findings documented and corrective actions scheduled. | ________ |
PM records: E-stop test, safety zone verification, speed and force limits, optics inspection, ISO 10218 / TS 15066 monthly audit — timestamped, safety-signed, independently verified
PM Sign-Off — Issued When All 4 Zones Are Confirmed
1
Joints & Mech.
PM Done ✓
PM Done ✓
2
Sensors &
Grippers ✓
Grippers ✓
3
Software &
Calibration ✓
Calibration ✓
4
Safety
Systems ✓
Systems ✓
✓
Robot PM
Sign-Off
Sign-Off
PM SIGN-OFF ISSUED — ROBOT CELL APPROVED FOR PRODUCTION
Any safety system failure — cell locked out immediately, no override without safety engineer sign-off
Open work orders hold the zone until corrective action is completed and re-checked
TCP calibration changes require engineer sign-off and program waypoint reverification
Every sign-off carries the full four-zone PM record for OEM, insurance, and ISO compliance review
Performance Metrics — Robotic System PM Programme
Cell Availability Rate
Percentage of scheduled production time the robot cell is available. AI tracking surfaces which cells show declining availability — correlating with overdue joint or sensor PM before a cell stop occurs.
TCP Positional Accuracy
Measured deviation from programmed TCP position during daily accuracy checks. Rising deviation is an early indicator of joint wear, cable fatigue, or base mounting shift before product quality is affected.
Safety Function Pass Rate
Percentage of safety function tests passing on first check. Any failure rate above zero requires an immediate investigation — safety function failures in robotic cells are never acceptable as routine events.
PM Completion Rate
Percentage of scheduled PM tasks completed on time across all four zones. Target 100% — missed PM tasks are the leading predictor of unplanned robot cell downtime and safety incidents.
55%
of unplanned robot stops are prevented by structured joint and sensor PM completed on schedule
100%
safety function traceability per cell — every E-stop and scanner test timestamped and independently signed
Zero
missed PM intervals when OxMaint auto-schedules every robot task per cycle count and shift
Deploy This Checklist Digitally
Cycle-Count PM Scheduling
Joint lubrication and sensor calibration triggered at OEM cycle-count intervals — not fixed calendar dates.
Safety Function Sign-Off
E-stop and scanner tests logged with independent sign-off — immutable safety audit trail per cell.
Drift & Fault Alerts
TCP drift and recurring fault codes raise work orders automatically before cell availability is affected.
OEM & ISO Audit Trail
Full PM record per robot — retrievable for OEM warranty, insurance, and ISO 10218 / TS 15066 audit at any time.
Replace Manual Robot PM Records with OxMaint
OxMaint gives robotics teams a fully automated, robot-specific PM programme — joint checks, sensor calibration, software backups, and safety audits scheduled automatically and logged in a compliance-ready digital record.
Trusted by automation teams across 40+ countries · ISO 10218 · ISO/TS 15066 compliant
Frequently Asked Questions
What robotic systems does this PM checklist cover?
This checklist covers four maintenance zones applicable to industrial robots, collaborative robots (cobots), and AMRs: Zone 1 (Joints and Mechanical — lubrication, cable inspection, torque trending), Zone 2 (Sensors and End-Effectors — force/torque sensors, grippers, vision systems), Zone 3 (Software and Calibration — error logs, TCP calibration, program backup, patch management), and Zone 4 (Safety Systems — E-stop, area scanners, speed and force limits, ISO audit). Each zone includes daily, weekly, and monthly tasks. Configure your robot PM schedule with OxMaint — free 14-day trial.
How does OxMaint schedule robot PM by cycle count rather than calendar date?
OxMaint integrates with robot controllers and SCADA systems to receive cycle count data in real time. PM tasks — lubrication, joint inspection, gripper replacement — are triggered when the asset reaches its OEM-defined cycle count threshold, not on a fixed date. This means high-utilisation robots get serviced more frequently than low-use systems, and no task is deferred because it isn't due on the calendar yet. Every trigger event is logged with the cycle count at time of completion. Book a demo to see cycle-count PM scheduling.
How does OxMaint handle cobot safety system PM requirements under ISO/TS 15066?
OxMaint schedules every ISO/TS 15066 safety verification task — daily E-stop and scanner tests, weekly speed and force limit checks, and monthly full safety audits — with mandatory independent sign-off by a competent person separate from day-to-day operations. All safety test results are stored in an immutable audit trail linked to the robot asset record, with the validated risk assessment and safety function specifications accessible in the same record for auditor review.
What happens when a robot safety test fails in OxMaint?
Any safety function failure — E-stop not responding within required stop time, scanner not triggering a protective stop, or force limit above validated value — raises a critical work order immediately, locks the zone in OxMaint to prevent sign-off, and notifies the safety engineer per your escalation rules. The cell cannot be cleared for production until the corrective action is completed, re-tested, and independently signed off. Every step is permanently recorded in the safety audit trail.
Can OxMaint manage PM schedules across multiple robot cells and facilities?
Yes. OxMaint runs all four zone PM programmes simultaneously across multiple robot cells, production lines, and facilities — applying the same task schedules, cycle-count triggers, and audit logging at every asset. Robotics and maintenance managers see PM completion rates, TCP accuracy trends, safety test pass rates, and open work orders across all cells in one dashboard, with complete OEM and ISO records per robot without manual assembly. Start your free trial and deploy robot PM management today.
