Maintworld Magazine 3/2021
- maintenance & asset management
- maintenance & asset management
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
RELIABILITY<br />
the leak, then understand why the leak is<br />
happening, then fix the leak, then we can<br />
begin to mop up the water. To provide a<br />
more maintenance-specific example you<br />
don’t need to implement operator care or<br />
autonomous maintenance to free up maintenance<br />
resources for firefighting or emergency<br />
reactive repairs. If that is the world<br />
you are living in, then in essence you are<br />
mopping the floor while the water floods in.<br />
Not only that, but you also look silly asking<br />
operations to be proactive when you and<br />
your maintenance organization are still<br />
fully in the reactive maintenance world.<br />
There is an order in which you need to<br />
implement the elements of reliability and<br />
maintenance improvement. It is not the<br />
same for everyone or every site. You need<br />
to understand your specific issues and reasons<br />
for the change in your organization.<br />
Then, understand the vision for the future<br />
support it. Pick a pilot area. An area where<br />
you can, without a doubt, be successful. If<br />
you are not successful in the pilot area, then<br />
your chances of being able to implement in<br />
other areas diminishes rapidly.<br />
The second big mistake I see here is that<br />
the area that is selected is too risky. The<br />
high-risk selections come from leadership<br />
teams that are trying to solve an issue in a<br />
problem area that might be your problem<br />
area for another reason. For example, “Let’s<br />
improve maintenance in area X because we<br />
need more volume or throughput.” However,<br />
had they really looked to ensure success<br />
and understand the issues, they would have<br />
noticed that this area is running a product<br />
that the equipment was not designed to run<br />
and has a high operational turnover so the<br />
equipment is being told to do things that<br />
it just physically cannot do by unskilled<br />
operators, or maybe they would find that<br />
WITHOUT MAINTENANCE PLANNING, YOUR RELIABILITY<br />
IMPROVEMENT IS DOOMED.<br />
vision and mission and developing the<br />
plan to get to the new level of performance.<br />
Many sites over the years have not taken<br />
the time to really figure out what needs to<br />
happen in order to get to their vision or future<br />
state on time. What do they do? Without<br />
understanding where they truly are,<br />
they just do things. They decide to tackle<br />
random improvement strategies. They get<br />
a list from a book or corporate that is not<br />
tied to the issues at the site or the goals and<br />
vision. I would compare this to trying to<br />
mop the floor dry when we have not identified<br />
where the leak is coming from. You<br />
can mop for days but the water just keeps<br />
coming. You need an order of execution or<br />
a master plan if you will. It should make it<br />
clear that first, we must find the source of<br />
state and let that help you select both the<br />
order and the elements that become part of<br />
your plan.<br />
Creating success<br />
The next area that trips many organizations<br />
up is that they spread themselves too<br />
thinly from an implementation resources<br />
perspective. They try to do everything<br />
everywhere in the organization. In most,<br />
if not all organizations we have limited<br />
people and financial resources and we have<br />
to build our implementation strategy with<br />
that in mind. You should not plan to paint<br />
an entire building with one three-inch<br />
brush and two painters painting a brick<br />
here and a brick there. You could, but most<br />
organizations do not have the patience to<br />
wait on the painted bricks to join up and<br />
generate the results they expect. If I have<br />
one brush and two painters then I am going<br />
to train those painters to be as effective<br />
as possible and then have them tackle one<br />
small section at a time, maybe a wall of 600<br />
bricks, so that the organization can see the<br />
change in that area and imagine what the<br />
change will look like once we paint more.<br />
To put this into maintenance terms, you<br />
don’t want to try and do every facet of reliability<br />
improvement in every area of the<br />
plant all at once. It will not connect, the<br />
vision gets lost, and you likely just cannot<br />
the leadership in that area is disengaged or<br />
unskilled. It would be hard to be successful<br />
with a maintenance improvement strategy<br />
if that is your pilot area.<br />
So, to increase your chances of success,<br />
pick an area that you have the resources to<br />
manage and can guarantee success because<br />
you have the unwavering support of the<br />
area leadership, as an example. Think not<br />
about your bottlenecks or trouble spots<br />
alone, because that is how the trap is set<br />
and then we fall and fail.<br />
Driving a problem-solving<br />
culture<br />
The next area that trips up many is based<br />
on the thinking that problem-solving and<br />
root cause analysis is something you should<br />
start employing after you have data in your<br />
enterprise asset management system, and<br />
you have many of the tenets of reliability<br />
started. This could not be further from the<br />
truth. You have to understand what is at<br />
the root of your past failures during other<br />
implementations or simply why you never<br />
implement at all. You need to know what<br />
has held you back. I also do not mean just<br />
a simple five whys or fishbone either. You<br />
need to understand what we call the systemic<br />
and latent roots. Some refer to these<br />
as organizational roots. What culturally has<br />
distracted or derailed us in the past or what<br />
3/<strong>2021</strong> maintworld 33