Resistance to Change (2)

October 2nd, 2009

Legitimate Concerns
Either some adjustments are needed to make the proposed changes function properly, or there are hurdles or barriers that have not been considered. Perhaps the product / change / project / system does not meet the objecter’s expectations of quality (or other, such as technical level), or there are known issues that the salesperson would not reveal.

Feedback from other parties (different location or facility within the corporation, friends, colleagues, or other) may point out severe problems.

Very often, some person voicing a legitimate concern may not be capable of fully expressing the reasons behind their reticence (oddly enough). The objecting party “feels” the proposed solution to be wrong for their environment.

If consensus must be achieved, develop a checklist and discuss the proposed goals with the vendor / service provider, and never forget to get the agreement in writing, detailing the issues, what the solution will address, and how it will achieve this.

© 2009 by François Gagnon

Resistance to Change (1)

September 10th, 2009

The infamous “resistance” to any proposed change takes many forms.

There are legitimate concerns, there’s contrariness, there’s fear of change, there’s protectionism, there’s a confrontation with a history of failed or abandoned initiatives, and finally, refusal to execute the work involved in the implementation of change, which unfortunately amounts to plain laziness.

Arriving at a consensus within a group of people may well face every previously stated type of objection, making compliance and adoption of almost any novelty / improvement / project difficult or even impossible at the best of times, no matter the value of the proposed initiative or change.

Over the course of the next few days (we hope), the author will endeavor to write out a few thoughts on each of the above.

Contrariness
The contrarian takes two forms: he can be a naysayer to anything he does not himself initiate, and thus, becomes a negative influence and rarely a helping hand in any of the activities of the group, corporate or otherwise, or he can be a conscientious critic of unlikely, unpalatable, unreasonable, inefficient or ineffective practices, methods or proposed “advances”, seeking to ensure quality and thoughtful of achieving specific goals. Of course, whether or not the contrarian can deliver his message in palatable form remains a challenge, and the (often different or opposed) views tendered by said contrarian can clash with the majority or the view adopted by leadership. Both require considerable maturity to accept the opposing current and trigger intelligent discussions based on analyzing what that impopular person is saying to obtain the value or pointed correctives that his views may contain.

In the above, “unlikely, unpalatable, unreasonable, inefficient or ineffective practices, methods or proposed “advances”…” could merely signify that there may be room for better adjustments or they may be downright necessary: the person deemed a contrarian may merely seek a slightly better approach, or more bang for the (same) buck…

As examples… 
One anecdote I often use (and may even be found in another posting on this site) is the advent of the first Windows-based or Windows-compatible (the Microsoft registered brand used without permission, not the household-type) vibration condition-monitoring software. Given the current preponderance of that operational system or platform, the reader will understand a few years have gone by since the anecdotal incident.

That software’s main qualities were:
1) it was going to be first to market under the increasingly dominant Windows (see previous disclaimer),
2) it actually worked without crashing,
3) it simplified report printing and layouts, but only for what was now extremely basic (or entry-level) reporting.

The same software principal defects were:
1) It offered little except basic functions, made readily accessible not through any ingenious design, but merely through the Graphic-User Interface’s benefits,
2) the software did away with many of the useful application functions that were readily available under DOS (but of course, that was going to be rectified in the future, meaning probably never),
3) it cost a frightening amount of money

My attempts at making suggestions to achieve expansion from the foundation we previously had, as opposed to devolution in terms of application, were met with allusions to “resistance to change”, when in fact, the nature of my objections was “Nice eye-candy, where’s the meat?” or where was the substance to assist analysts in better doing their jobs.

Another valid example, when faced with various problems during a reliability audit done under another company’s auditing process (or lack thereof), was to ask whether the process had been the subject of an FMEA (Failure Modes & Effects Analysis). After all, if you sell the science, the execution and the mindset, you should be interested in applying all of the previous to your own product, whether physical or service oriented.

In the previous statement, my “or lack thereof” was unfair, and of the naysayer contrariness type: in all fairness, they did have a process, but the process should have been accompanied by clear directives and guidelines as to “do’s and dont’s”. The process should have benefitted from strong warnings against allowing corporate tag-alongs during execution. My suggestion that an FMEA would clearly have established problems with such a practice came from obvious hurdles such as the reluctance of audit interview participants to formulate their answers in the presence of a corporate representative.

Opposing views leads to (minor) confrontation, and people are increasingly uncomfortable with disagreement or argumentation. Yet, out of the clashes of ideas are born the better or even best solutions. HBR (Harvard Business Review) and other management article sources state that the increasing disappearance of differing opinion hurts business.

For the well-meaning contrarian, perhaps the road to Hell is paved with good intentions.

© 2009 by François Gagnon

Reliability & Condition Monitoring Traps (1) (Tips)

April 15th, 2009

The year is already getting older… As 2009 progresses, have you set PRECISE and achievable goals relating to…

- Execution (of various tasks)

- Results (metrics, or KPI)

- Accomplishments / ambitious achievements to aim for over the next 12 months

Even the efficiency and effectiveness of PdM must be assessed and measured to set the bar a little higher until the calendar year takes us over into 2010.

Where is the trap? Failure to measure and failure to set goals for improvement leave you far away from the ever elusive continuous improvement nirvana…

© 2009 by François Gagnon

Best Practices (2)

March 31st, 2009

The first hurdle in establishing anything remotely superior in terms of practices, or correction of established methods in any plant, remains the too often shoddy quality of information derived from inaccurate, biased, incomplete or even lost data.

In a recent discussion regarding the age-old approach of first dealing with high maintenance cost assets, the sad realization that these could only be identified through subjective impressions of personnel left us perplexed: the problems of old are still alive and well.

Simply put, you can not manage what you do not measure, and measuring (metrics or performance indicators) can fall short of the target if the proper controls were never established from the start (or some time in the past).

© 2009 by François Gagnon

“Best” Practices

March 30th, 2009

The benefit of wielding several languages can sometimes be found in the details of how another culture considers an expression or statement that pervades our culture to the extent where we no longer question it! Take “Best Practices”, for instance…

The French language instantly applies a caveat to that now sacred cow of a buzzword: it becomes Exemplary Practices. We immediately get a different sense of importance as that critical nuance gets introduced, since Best and Exemplary ring altogether different bells.

The problem with Best can be readily summed up: “Best” for the people who use it, in their business, industry, context, environment, management style, CMMS or EAM, may well be far from the bull’s eye for YOUR plant. Sadly, “Best” may be a lie! 

“Exemplary”, on the other hand, avoids the pushy arrogance of stating “this is the way you should also manage, work, implement, or execute”. Instead, it gently introduces itself as an example of methods that work for certain people in their very specific circumstances.

Thus, the reader may concur that “exemplary” may well be much better than “best”! An odd conundrum, to say the least!

© 2009 by François Gagnon

Unraveled Reliability

June 17th, 2008

Humans are creatures of habit. They perform along certain established “known” lines of action, and reject the unknown quantities as potential failures or as unnecessary supplementary effort quite likely to yield identical (and sometimes worse) results. Due consideration for said results may at times ignore the fact that the additional benefits are seen elsewhere by people with a different skillset (for instance, the habit of entering ALL pertinent data in a CMMS merely seems overly long and tedious, whereas the manager wishes to mine the data to yield significant indicators that may or may not be understood at the keyboard entry level).

Changing any one “train of thought” is possible, but even that requires patience and dexterity in managing the change and shifting attitudes towards new goals. Attempting to change several known parameters towards newfangled ways of doing things can thus be readily demonstrated as both dangerous and most likely ineffective in the long run. A change can be achieved in the short run whilst a constant push is maintained to hold up the massive “old ways” but the second we remove the sustaining presence of that force, the old ways will seek to return back into familiar patterns.

How does this affect reliability efforts? Another author (and I seemingly can not readily find the reference at present) calls it the “6 months rule”. People will (albeit often grudgingly) go along with new methods for a period of six months and then, if no obvious results or benefits can be identified from their point of view, these same people will stop believing (if they ever did) that potential rewards will soon appear.

Six months is an exceedingly short time when projects are handled in parallel to regular tasks. The vaunted “trial period” may be shorter than many implementations when execution is handled internally, and contracting out requires adequate budgets and an ever expanding relationship with the contractor to achieve the desired ends within a short time period.

Bottom line: if implementation must succeed, sustained efforts (and money) must be provided to deliver quickly!~

© 2008 by François Gagnon

 

Capital Investment Versus Maintenance Cost

June 17th, 2008

We can likely never reach a conclusion befitting the complexity of the following question: should we buy new equipment, replacing the “old”, or should we repair what is currently installed and already paid?

Problems from an operating cost quickly arise when from a matter of policy, no “new” expenditure can take place to pay for asset replacement: maintenance falls into a rut, incapable of effectively managing reliability, and the plant becomes overly expensive for such simple matters as aging (and obsolete or “too often repaired”) assets.

The case of the electric motor comes to mind. How often should a motor be repaired or rewound, excluding purely mechanical components such as a bearing replacement? Three repair cycles is generally recognized as the upper limit (some may disagree). What is the principal cost tied to the electric motor? Its purchase price? In fact, the cost of power consumption (and waste if inefficiencies accumulate) far exceeds the purchase price, or the difference in price between a high-efficiency electric motor and a relatively inefficient one.

Failure to evaluate (or reassess in cases where the original evaluation was made years in the past) the true costs of operation tied to electric motors lead to unreliable operation and stupendously superior energy expenditures. The breakpoint of “buy new” versus “operate the inefficient” is reached much sooner than most people intuitively assess. Therefore, the payback period of such a project as buying a new motor must be set at a time-period enabling plant cost viability. Is 3 months too long a payback? Is the plant not going to stay in operation for years to come? Worse is the cumulative effect of spreading the “disease” to a large population of motors and eventually facing huge cost overruns that can then only be addressed by massive injections of capital instead of dealing with this issue progressively and constantly during the plant’s life.

“In this business climate, we know not how long we will continue production!” seems to be a common concern, but since usable assets would likely be shipped to a more viable site, the expense still holds as a reasonable approach.

© 2008 by François Gagnon

Reliability Challenges & Fundamentals

March 16th, 2008

Numerous experts report the undeniable absolute necessity of management conviction and dedication for reliability efforts to result in a proper and sustained “field” (that would be the plant floor) implementation. No argument could possibly otherwise convince us or our readers. We agree on something.

Why then do we see a generalized backtracking to antiquated methods or unwitting feeble returns from reliability approaches? Where is this management commitment when reports from the field indicate reliable methods get implemented and then seem to vanish into thin air or quickly get set aside? Why is apparent regression almost inevitable?

What some may fail to mention is the capital importance of fundamentals. And these essentials may escape most of the “business model improvement” proponents due to a simple and quite ugly fact: the “business” people rarely speak with the technical personnel who get the maintenance train on track and keep it there. And when they do, as they are often used to speaking very different languages, these parties may have limited exchanges or communications due to the different focus or interests they manifest.

The communication gap may be further aggravated by a largely false perception in head offices that the technical people remain uneducated. Nowadays, their credentials and pertinent experience may even at times exceed those of decision makers. This is not to criticize anyone: the preceding merely attempts to state occasionally occurring (and previously encountered) circumstances.

The predictive maintenance and condition-based approach to maintenance and reliability are vital to success. Yet, these facets of maintenance and engineering have been in place for some time, with often poor to moderate results (the author is being kind; so many PdM or CBM programs are hobbled structurally and technically that their returns can only be qualified as hobbled). The promise of fabulous returns can not be met when the program is not “fed” properly: investment, education (training at ALL levels) and sensible recognition of efforts, to name but a few factors too often missing from the final recipe…

What makes you think that doing the same thing in the same way will now yield a better result? What will now be done to properly adjust the targeting? The liabilities (or problems) and personnel are the same. Or personnel keeps changing in turnstile-mode.

Of course, critics might glumly reply “Have you not been part of the system that created the ineffectiveness we must now endure?”, a pertinent albeit biased question. We propose a viable working platform or product to our clients. We might express it as “we sell a car”. The client then plays pick and choose, dismantling the platform to purchase (allegorically) the two left-side wheels, one rear bumper, and parts of the engine, instead of buying the whole functional vehicle. The reasons are many and they feel justified in this purchasing approach: they already have two right-side wheels (of a different size), one bumper and engine parts (likely mixing centimeters and inches), so they feel they can reassemble a working whole. The truth seems to point to “wishful thinking”.

An example? Some years back as I instructed a Vibration Analysis 1 course for one of the main vendors in our field of endeavor, two technicians showed up from an automotive parts manufacturing plant. They expressed their concerns relative to the course, having discussed with their supervisor what they felt was their need for training (they would have been more comfortable with an introductory course instead of the one they were now to attend). I assured them of my availability over lunch and after regular hours should they face serious hurdles, and also told them I ran a very open classroom where questions were welcome at any time. This can be helpful, but if fear of ridicule and timidity become the governing concern of the puzzled, our best efforts to remain available yield little in the way of improved comprehension. At any rate, they never availed themselves of the repeatedly tendered “extra” support or semi-private sessions.

Most Level 1 courses clearly state a need for 6 months prior experience and/or having attended an introductory class. These two participants were lacking in both respects. Net result: come evaluation time, these two felt that the vendor offering this training was only interested in revenue and they never should have been “allowed” to attend that course.

Everybody is entitled to an opinion. Ours would differ slightly: in the hopes of saving some training dollars, their supervisor sent these participants to a course that was above their current reach. In so doing, he wasted more training dollars than he saved. He also exposed his technicians to a little discouragement, and lower motivation due to perceived difficulties.

Could the problem have been resolved right then and there by using a different approach? Course contents did not lend itself to a quick readjustment: other participants quite liked that course and got what they came for, but then, they had the necessary bases to absorb the curriculum.

To the previous example, we should also add the unpopularity of introductory courses in certain areas of the world. The “client” (purchasing or management) feel them to be a reach for more $$$, when in fact, the participant get swamped with too much material when attending the “chosen” (not by them) higher-level course.

Worse yet, in those same areas, when a certification exam is faced at the end of a week’s training, some participants have at times been warned that failure would equate dismissal. Sitting (or writing) an exam that is meant to cull the untrained may dauntingly challenge the neophyte.

Another sad hurdle to reliability excellence remains the discrepancy in pay rate and benefits afforded those who practice it adequately. Sooner or later, if competent technical personnel find they may be given better opportunities elsewhere, they will jump ship and seek out better climes. There are management or HR theories about pay scales and bonuses (this writer will purposely stay away from them as readers might be offended by psychological aspects of remuneration), but an occasional carrot, such as two checks waiting in the wings (gold and silver medals, if you wish) might yield surprising competitive benefits. Or setting PdM program goals and tying a bonus to meeting those targets.

Proactive engineering steps used hand in hand with precision maintenance yield better reliability. The latter is undeniable. Yet, without a strong predictive program, above and beyond any scheduled preventive replacements (likely arising from an RCM study) and inspections, production and asset reliability will remain out of reach.

PdM / CBM or Condition-Monitoring ARE the technical foundation that can be encouraged, but not managed at any level other than that of maintenance and engineering. In other words, if reliability is a fortification against trouble and decay and a guarantee of productivity, the walls or battlements depend on solid groundwork called predictive maintenance.

Simply put, Asset Reliability (and maintenance) can not be driven by failure-detection if predictive efforts remain incapable of perceiving faults.

© 2008 by François Gagnon

Sources of Vibration

March 3rd, 2008

Where does vibration come from? What causes it? Any force changing in direction, changing in magnitude or any active component interaction generating a rub even as minimal as friction within rolling element bearings or moving fluids within pipes will cause vibration movement of some small to intolerable amplitude. Any combination of the previous would generate more complex vibration patterns. In practical terms, this means a long list of potential sources whenever an analyst tries to quantify and/or decompose machinery and structure behavior.

The (presumably, unless something escapes this writer) full list breaks down into:

Rotor related sources (rotor behavior and forces at play)

- unbalance

- static or force, couple, dynamic or combined

- misalignment, residual, growth-related or dynamic (reactionary)

- angular, parallel and combined

- bent shaft

- rubs

- macro rub

- rotor-casing

- rotor-product or moved fluid (when dense or solid)

- shaft-seal

- shaft-sleeve bearing

- gear coupling-jaws

- improperly lubricated gears

- micro rub

- belt-pulley

- sliding (instead of rolling) elements

- rolling elements themselves onto raceways (through lubricant film)

- pumping action or film-creation action within the bearing

- rolling elements and retaining cage

- fluid and casing or piping

- eccentricity

- whirl (of shaft or of the shaft within a fluid-film bearing) and whip

- gyroscopic effects (fairly common in inertia wheels)

- torsional vibration


Process related sources (what the machine does)

- hydraulic or aerodynamic forces

- blade / vane pass (BPF) or blade rate (BRF) vibration

- eccentricity relative to casing

- rotor mesh (lobes or screws)

- cavitation, recirculation, turbulence, stonewalling, surging, stalling

- compressed fluid wave or pulse (pipes, etc), turbulent flow

- reciprocating forces (can come close to shock)

- shock (presses, etc)

Drive related sources
Electromagnetic torque pulses from a motor and the interaction between armature and stator components a.k.a. rotor-bar and slot pass frequency
Pulses used to recreate Variable Frequency altered electrical line frequency
Pole or coil pass frequency

Magnetic centering
Coupling problems (lock-up, wear, etc)
Belt or chain drive w. eccentricity, belt problems, belt slip, cogs
Gear mesh and gear problem related vibration
Couple transmission discontinuities or variability from load transmission from one tooth to the next (simplified to picture the matter)
Hydraulic or aerodynamic forces from gas, steam or water turbines
BPF (Blade Pass Frequency) from turbines
BRF (Blade Rate) interaction between blades and stationary elements
Reciprocating forces from engines, unbalanced cam action

Other factors may cause the appearance or perception of an excessive vibration problem, but they are REACTIONS to one or more of the above sources as opposed to being themselves a source of vibration. The most easily recognized of these are looseness and resonance. Critical speeds of a rotor could be assigned to resonance for purposes of this listing. Oil whirl on sleeve bearings also fit into this category: it is an instability reaction due to lack of static load or dynamic loads overcoming static load. In this latter case, increased tolerances facilitate overcoming the static load. From the point of view of reactions, we can also add:

Reactive Problems

- dynamic misalignment (occurring from loads moving component positions)

- resonance

- looseness (really a change in response due to lessened stiffness)

- instability (rotor, hydraulic, oil film, other)

- base and retaining / supporting mechanism or structural problems

- distortion from pipe strain

- transmitted vibration (structure borne transmission from other nearby machines)

- acoustic excitation (airborne or structure borne noise exciting a plate, casing or other component; structure borne usually or closely falls under transmitted vibration)

 

© 2005, 2006, 2007, 2008 by François Gagnon

Just a Quote…

February 28th, 2008

“The society that scorns excellence in plumbing, because plumbing is a humble activity, and tolerates shoddiness in philosophy, because philosophy is an exalted activity, will have neither good plumbing nor good philosophy – neither its pipes nor its theories will hold water.”
John Gardner, former Secretary of HEW