Infor LX Tips, Infor LN Tips, BPCS Tips, Baan Tips, Infor M3 Tips & Infor ERP News, Crossroads Connection

I have been working with ERP in various roles for over 30 years, directly involved in over a hundred implementations, while my company has been involved with over 400 more. Of course, in many ways the systems we use today are completely different from what we used in the ‘80s – back then it was green screens, simple transaction entry forms, and cumbersome updates (at best) to link what one department did with all the other areas that needed access to that information. Then there were those planning programs that took all the information along with various parameters the users needed to set and told us what to do.

The More Things Change, the More They Stay the Same

When fixing a downtime issue, make one change at a time.

Often, multiple changes are made at the same time, without individually checking their impact on the equipment. This makes it much harder to diagnose problems and evaluate the effectiveness of solutions.

When fixing a downtime issue, make one change at a time.

Often, multiple changes are made at the same time, without individually checking their impact on the equipment. This makes it much harder to diagnose problems and evaluate the effectiveness of solutions.

It is essential to capture a reason and duration for each downtime incident to enable the team to effectively prioritize and focus.

Start simple, and make sure every reason is clear (when compared with other reasons) and describes symptoms (as opposed to attempting to diagnose root causes). Remove reasons that aren’t regularly used and add reasons.

It is essential to capture a reason and duration for each downtime incident to enable the team to effectively prioritize and focus.

Start simple, and make sure every reason is clear (when compared with other reasons) and describes symptoms (as opposed to attempting to diagnose root causes). Remove reasons that aren’t regularly used and add reasons.