An older HMI still works, but could you obtain a spare, find the project file and restore it if it failed tomorrow? Age is only one clue. The useful question is how dependable continued use and recovery really are.
Build one reviewable asset entry
- Record the precise model, software/firmware version and role in the line.
- Check manufacturer availability and support notices, keeping the source and date.
- Review a valid spare, project file, licensed tools and a tested recovery method.
- Record lead time, outage consequence, owner and next review date.
Old is not the same as unusable
An older device with proven recovery and a valid spare can present less risk than a newer device with no project file. Combine support status with the impact of failure. Explain the scoring rule and evidence rather than relying on a red colour.
Turn the list into prioritized work
- 01
Choose an important line and reconcile actual models with the inventory.
- 02
Collect supplier-status evidence and recovery checks for significant items.
- 03
Compare continued support, spares and migration options with their costs and limitations.
- 04
Assign actions and scheduled reviews for the highest-priority risks.
A replacement also needs verification
Similar part numbers do not prove interchangeability. Check communications, programming tools, licences and rollback tests. AutoNexit retains the related records and files; it does not automatically discover supplier status or certify compatibility.
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Does buying a spare remove the risk?
No. Its condition, storage, configuration and recovery method also need attention.
Is one laptop copy of the program sufficient?
Dependable access to the file, tools, licence and recovery evidence matters; dependence on one personal device is a risk.
How often should the register be reviewed?
Choose a risk-based interval and review sooner after a supplier notice, major fault or version change.
Should the oldest PLCs always be replaced first?
Prioritize failure consequences, recoverability and feasible options rather than age alone.