Most Planned Maintenance schedules focus on the obvious tasks: lubrication, bearings, belts, guarding and general electrical checks. These matter, but ageing PacDrive assets carry risk across a broader set of areas.
A PacDrive maintenance schedule is only useful if it reflects how the machine can actually fail
Controllers, drives, motors, feedback systems, communications, cable assemblies, stored programmes and obsolete spares can all create risks in ageing PacDrive M and PacDrive 3 systems. A schedule that covers only the mechanical layer leaves these areas unexamined between breakdowns. The engineer may sign off the sheet, but the underlying risk does not change.
Start by mapping the installed PacDrive system
Before setting any intervals you need to know exactly what is installed. This means the controller type, which MC-4 drives are fitted and to which axes, the motor series in use (e.g. whether iSH, SM or SH), the power supply and distribution arrangement, communications infrastructure and critical cable runs.
Once the hardware picture is clear, each asset should be allocated to a specific machine function and a production criticality rating. A MC-4 drive on a primary forming axis carries different consequences if it fails than one managing a lower-speed auxiliary function. The map needs to come before the maintenance plan, not after it.
Build maintenance around criticality, not one universal interval
The popular approach is to apply the same inspection schedule across the whole machine: check everything every six months, tick the boxes and move on. However, this risks producing an incomplete result because not every part needs the same level of attention.
High-impact assets, such as obsolete controllers (MAx-4’s and now PacDrive 3 LMC600’s) and drives where replacement availability is already under pressure, require a higher degree of attention than low-level components. PacDrive M obsolescence is a genuine pressure point for many companies and a blanket schedule plan does not reflect that reality.
Instead, the inspection priority and frequency schedule should be based on criticality, the operating environment, function, failure history and availability of replacements. An ageing controller on a critical primary line and a lower-risk component elsewhere on the machine should not receive identical attention just because they are on the same schedule routine.
What should a PacDrive PM inspection actually cover?
The checklist below covers the main areas a structured PacDrive inspection should address. A generic maintenance schedule will cover some of these, but risks missing the rest.
| Area | What to check |
| Physical condition | Enclosure integrity, contamination, corrosion on controller and MC-4 drive housings |
| Cooling and contamination | Fan operation, airflow paths, heat stress indicators on drive units |
| Connections and cabling | Motor cables, encoder and feedback cables, communications wiring, connector condition |
| Feedback and communications | Encoder integrity, fieldbus stability, communication error trends |
| Diagnostic history | Fault log entries since the last check, acknowledged alarms not yet investigated |
| Abnormal and repeating errors | Events that clear on reset, intermittent warnings not yet linked to a cause |
| Motor and mechanical loading | Following-error trends on SM and SH motors, axis load changes, brake condition where fitted |
| Backups and configuration | EPAS-4 programme backup, firmware version, verified parameter settings |
| Spare readiness | Critical spares confirmed tested, firmware-compatible and available on-site |
Each row represents a failure category that a standard mechanical check may not cover.
Use history and trends, not just visual inspection
A Planned Maintenance review which relies only on what the engineer can see and hear during an inspection will almost certainly miss what the machine was doing between checks.
Recurring errors, following-error behaviour on individual axes, load changes on MC-4 drives and intermittent events between service visits provide evidence of condition. However, they may not necessaily be evident during a scheduled inspection window, but they will exist in the diagnostic record if this has been kept.
This is where Machine Analyser® adds a practical layer during scheduled maintenance reviews. As a read-only condition monitoring tool, it surfaces patterns in the event log a walk-round inspection may not capture. This provides engineers with something specific to investigate rather than relying purely on what is visible on the day.
Document what was found and what changed
A Planned Maintenance schedule needs records. A record that only confirms a visit happened has limited value to the next engineer.
For each asset inspected, the record should capture the asset reference and type, what was found, any measurements or observations, diagnostic changes since the last visit, actions taken, outstanding risk, spares required and the date for the next review.
With that structure in place, the next engineer can compare rather than start again. They can see whether logged events have increased, whether a flagged cable condition has worsened and whether a recommended spare has been sourced. A trend only becomes visible when there is a record history to refer to.
Connect maintenance to the wider lifecycle plan
Maintenance findings should drive decisions. After each inspection cycle, the output should map each asset to a clear next action: continue monitoring, arrange repair, stock a tested spare, begin a partial upgrade or initiate a migration plan.
Planned maintenance and obsolescence management are not separate processes. For ageing PacDrive M equipment in particular – but also PacDrive 3 – the evidence gathered through regular inspections provides the basis for decisions that might otherwise be deferred until a breakdown forces them.
Conclusion
The objective is a documented system that tells the Plant Manager which PacDrive risks are changing and what action should happen before they become breakdowns. Generating more maintenance activity for its own sake will risk it being unproductive and may well miss a indications of a future failure.
A PacDrive maintenance schedule that proves maintenance took place is not the same as a schedule that shows whether the machine’s risk profile has changed.