Archive for March, 2007

Data is NOT Information

Friday, March 30th, 2007

Several years ago the trend to make all the vibration data available to all parties within the coporation took over. This was a reflection (according to some) of the will expressed everywhere, and this was mroe or less doomed to failure. Why?

Trained analysts vary in proficiency: some are starting out, others have progressed considerably. The degree of confidence and credibility of analysts grows with training and experience, but some problems can be one-time events within the plant’s or the machine asset’s life.

Interpreting the data and churning out usable diagnosis or prognosis information from that data requires pertinent knowledge and experience.

Assessing the probability of failure from the data is a delicate operation.

The end result was thus predictable: if people trained to draw conclusions from this type of complex data can sometimes be wrong, it was unlikely that just anyone would be able to make much of it.

A time waveform, an FFT spectrum, an amplitude or a trend thereof are NOT information. A time-to-failure probability and financial consequences, or a remaining L10 estimate, or an assessment of bearing or motor damage IS information.

If properly written, it can even be comprehensible and would thus become usable information.

© 2007 by François Gagnon

Reliability: Culture Change & Change Management

Wednesday, March 28th, 2007

In 1967, Sweden had an abrupt change of a very simple aspect of everyday life: driving went from left (a la British) to right (a la “rest of Europe”). The event was well prepared, well publicized, and slated to take effect at midnight upon the arrival of the 3rd of September, a Sunday (well, you do need to make the changeover beforehand for signs and intersections, and midweek would surely not do). Memory seems to bring back a little awe at only one reported accident linked to switching sides, a credit to the Swedes.

There were reports of relatively mild confusion and hesitation: entering a brand new area calls upon a certain skillset, but an upheaval of the familiar is far more disturbing.  Old reflexes seek to take over, but can no longer be trusted to provide the needed or adequate response when confronted with even the simplest situation. Former trajectories must be reassessed. The car’s internal arrangement may also feel awkward in virtue of the new rules applicable to the task of driving. 

Adopting a culture of reliability also creates a little upheaval. Even today, in many plants where predictive maintenance has surveyed machine assets for the past quarter-century, the culture can sometimes feel more reactive than proactive. The predictive approach implementation was attempted and partly adopted, too often with a lack of cohesion or completeness in training. 

Certain tools may even feel awkward (whether it be the CMMS or the EAM, or new technology implementation in other areas). Much like the car…

Understanding what is needed, comprehending the underlying causes of that need, giving it a little time and making the conscious awakened effort to meet the challenge… Much like switching roadsides in Sweden…

© 2007 by François Gagnon

90% of Predictive Programs Need Substantial Improvements

Monday, March 26th, 2007

That’s right! Our in-house statistics reveal that only 10% of programs (admitedly slightly rounded up) we have surveyed only require tweaking, suggestions, minor improvements. If we were to compare PdM programs to a house, a small number only require interior decoration adjustments.

Much worse, about 50% of programs require foundation work: horrors have been perpetrated in the name of implementation or program launch speed, often relying on less than ideal templates and requiring so much reworking that we have even at times wondered if the data was worth saving. In some cases, interpolation (applying a mathematical algorithm to better detail FFT resolution) can help make old data more relevant.

Few programs have their information extracted from the mess of data collected over years of weekly or monthly intervals. Hint: a spectrum is data, a diagnosis or prognosis is information. So is a correlation between data and an actual picture of reality such as a damaged component!

Do yourself a favor: don’t let the people who initially made a mess attempt to audit themselves and don’t let them play around in your program.

In closing, a little anecdote: some years back (in 2000, I guess), during a training session in Caracas, one company had two participants, manager and engineer. The latter offered the information that they were using an IRD 818 as a data collector. While this antiquity might provide a better safety net than nothing, it was…ancient, inefficient, very, very passé. In its day an excellent workhorse, we had seen three generations of instruments go by since that instrument had appeared on the market. After making a comparison with the (then) current capacity of colelctor and software platforms, I commented that I still owned one of those, but used it as a doorstop for my furnace room.

We had a good laugh with that one, but then I detailed the portrait: old houses were built with quasi explosion-proof coffers around furnaces, and the very concept of an oil-furnace for heating can sound bizarre when one soaks in the heat in Caracas. At any rate, the door is in fact balanced for self-closing. The truth of the matter is that to this very day, the IRD 818 hangs from the doorlatch where I can quickly let it slide to the ground with the strap and provide an efficient stop…

© 2007 by François Gagnon

Bemoaning Analytical Costs

Thursday, March 22nd, 2007

We sat in with a (then) prospective customer having problems with a very special machine: one of a kind, a prototype really, made in Europe, highly-complex variable speed multistage planetary gearbox, with inverted simultaneous movements: a fun challenge for an analyst, but one that could rapidly turn to nightmare if sound methods were not followed in orderly or procedural fashion.

While we took a look at drawings, and commented, the meeting went on with the people in charge. “We’re losing $100,000 a day on reduced production!” Indeed, the vibration would get so bad as to limit speed, \commensurately reducing output.

Now for vibration analysis purposes, we need to do a speed-sweep recording of multiple channels of information to then compare reactions, and perhaps even build an animation. The problem obviously needs to be quantified before we can affirm anything, and the measurements taken by the customer proved fairly basic: lending a nebulous idea, but no great help in establishing the scope or nature of the problem.

We conferred, and stated a package price of $20,000 all-inclusive: measurements, analysis, report in both brief and full versions, presentation of report, engineered solution.

That’s when the roof caved in on us with the plant manager almost calling us names (along the lines of price gouger, and a few other terms punctuated with choice epithets). Pause… Shall we say it was clear the price was not to their liking? Yet, in the meantime, over a 90 minute meeting, they had allegedly lost $6,000.

Was the proposed price justified? Absolutely! We had a 12 hours 16-channel collection speed-sweep and variable-load sequence, data review (Simultaneous data from sixteen channels under controlled variation of recorded factors conditions requires ample time) and analysis, a possible (and rather likely) machine design review, a whole day of presentation possibly involving two persons. As a matter of fact, we were trying to deliver a fully-packaged, functional and feasible solution to an unknown problem at a reasonable price.

To the uninitiated, multi-channel work may seem a mere matter of unconnected information, but correlations need to be established: imagine recording 16 TV channels and then finding out if commercials are synchronized (or not), if there is an underlying contents programming emulation where all networks decide to show similar programs at the same time. Then, imagine that your need to cut up one channel’s contents in tiny pieces, or process it differently to isolate “dialogue”, or modify the contents of one channel in relation to another’s.

Within the context of this contract, synchronous time-averaging and order-tracking had to be completed in post-processing, high-resolution FFT cascades had to be extracted, and in this case, high-resolution means much more than 3200 or 12800 lines. Jitter and jerk even were assessed. A little structural work was done to complete the picture. Our Finite Element specialist associate also handled the case.

All this takes time. And the relationships and workings are not automated. A guiding intelligence must determine how best to extract what seems relevant to the mission.

Once the initial storm blew over, and the solutions implemented, all parties were content, but THAT is another story!

Additionally, one may read herein the key point of the nuance between detection and analysis: “detection” was here summarily conducted by intolerable vibration levels making the machine dysfunctional at its design speed, a status that was readily assessed using portable instruments, whereas analysis called for much more depth.

© 2007 by François Gagnon

L10 Life? L1? Lzero? Bearing Life Vagaries

Thursday, March 22nd, 2007

L10 rating is largely… inadequate… even when just considering the fatigue question. Forget not the effect of contaminants, and lubrication, etc, etc.

In the paper I presented at the CMVA last year (Canadian equivalent to VI), the early portion deals with fatigue. See the ugly red thumbnail in the last segment (first by date) of Articles & Papers

To make a long story short: bearing fatigue life has more to do with contaminant inclusions within the steel than load and cycling. That is the principal reason why so many bearings which should fail from fatigue keep going well beyond the life estimate: low contaminant contents in the load zone.

As a rule, the design target is 50,000 or 100,000 hours for many machines. It can be higher for electric motors since the bearing size tends to be relative to shaft dimensions, and that last size will be based on force couple and torque issues rather than the very light rotor loads.

It doesn’t mean that you would not encounter cases representative of more extensive lives: they abound.

© 2007 by François Gagnon

Frequency Mismatch

Wednesday, March 21st, 2007

Something that got on the radar again in the past few days: formula to calculate frequencies from various mechanisms, and mismatches occurring when confronted to reality.

Several items come to mind, not the least of which are the “supposedly” accurate bearing frequency formula. Why deride the end result? For one, the formulae used presume metal-to-metal contact, or attempt to compensate the presence of lubrication through consideration of the pitch diameter or value of the diameter measured between the central position (middle points) between races (inner and outer).

Does the center of the load-bearing elements correspond exactly with that Pitch diameter? It does not. Does the thickness of the lubricant film amount to something? We may neglect it, but it sometimes can play a role. Oil is thinner than grease, and where grease is concerned, the soap-base plays an important role in film thickness (as demonstrated by SNR conducted research; send email for paper). Of course, the effect of any sliding will outweigh considerations of film-thickness: overly light loading or dynamically contributing factors occasionally resolved as light loading (hence, a temporary light-load condition) will cause elements to slide and frequency values will either shift (considerably) or fluctuate (between a minimum and maximum value threshold). Installed bearings may not always conform to our asset list.

Pitch diameter is again used when dealing with sheaves or pulleys: “diameter of a sheave or drum measured from the center line of the cable wrapped around it”. Is that an accurate measurement or a useful estimate of values needed to determine belt speed, belt length, driven rotor RPM? We like to say estimate. Sheves wear down. So do belts (or they deform). V-belts will slip, often continuously. Review the definition of Pitch Diameter given in this case, and you will realize that even this “reference” varies over time. On chain drives, where the equations become an issue of links and sprocket (acting as a gear).

Line frequency may vary. North America and parts of Europe are well served in that respect, but it still has “end of the line” locations (the last plant downstream may get slightly altered power), local generation issues (small in-plant generation or limited network more susceptible to variations), and other areas may experience wider fluctuations. Since all induction motor speeds will vary accordingly (unless a VFD acts as compensator), most machines will also experience RPM and commensurate linked frequency shifts.

© 2007 by François Gagnon

Maintenance & Misalignment: Vibration or Not?

Monday, March 19th, 2007

Misalignment is a functional condition: it is not just a matter of completing a perfect cold alignment, as we all know. Offsets need to be factored in to accommodate thermal growth or rather, thermal growth differential between two machine train components. If that last factor affects alignment precision, there are others.

Dynamic reaction, often neglected, can play an important role: a machine “sits” differently when it delivers (motor) a 500 HP (for example) couple or receives it (driven rotor). Working stresses change the equation: a contracting or expanding pipe will push/pull on one component, or twist it out of shape. And finally, a significant unbalance will create a dynamic, temporary, acting misalignment: the center of a shaft moving by 4 Mils p-p can hardly line up with its counterpart. Obviously, any condition resulting in driver or driven overreaction (in terms of vibration) also resolves itself into misalignment.

The short catalog of causes (which we will likely explain at length in future articles) often explain why the millwright staring at alignment correction with work order in hand may feel a sudden wrath when thinking about his colleague the analyst: with the best of intentions and the machine still warm, no alignment fault seems present, so our poor millwright feels like someone is not performing properly. This can lead to credibility issues within maintenance.

Another item tied to misalignment: the case of the misalignment-induced energy-loss. One paper reported there were no such mechanical losses from misalignment. We will protect the innocent, and prove them wrong: whenever an asynchronous AC electric-motor vibrates, two things occur, in varying degrees: the RPM DROPS slightly, and the amperage draw rises slightly. This is common knowledge, but not necessarily common to just anyone as extensive experience with balancing and other field procedures should likely be common trait of those who know this for a fact.

In the test for misalignment, the professor(s) who controlled the experiment did not propose to simultaneously monitor the vibration to the amount of misalignment. No one ever suggested that misalignment was the loss by itself: if misalignment fails to produce mechanical energy losses through vibration, the misalignment is resolved as an applied force without any movement. Instead, they merely monitored the output through a dynamometer, without measuring the input.

Whosoever says “force applied without any movement” quickly realizes that no mechanical work (our old friend W = F d) is being performed (since d = 0, or close enough) and thus, no great energy losses occur. Simple! But when will we have a misalignment incapable of producing vibration? Given a relatively stiff structure for a small test bench, the dynamic stiffness could be important enough (low mobility, or very small responses per force unit) as to prevent any such vibration and losses. As a note, yes, the author is aware of rotational equations. Just consider Work along the horizontal axis for the sake of simplicity.

It should thus become clear that as a protocol to confirm or invalidate any misalignment-borne losses, the chosen approach lacked scientific rigor. The previous did not consider the possible pernicious losses within the electro-magnetic system should any air-gap variation effect come into play. In fact, for a very small motor, the probability of such losses becomes negligible, and their cumulative effect would be trifling should they be manifest.

© 2007 by François Gagnon

Off the “Maintenance Forum”, “ElectricPete” had a question: “I have never heard this before and at first glance I’m skeptical, but always interested to learn. Do you have any additional information on this? (For example: Any example of how much change you have seen? Any reference to discuss this? Any possible explanation for the physical mechanism?)”

FG replies:
The observation is purely empirical, over the balancing of hundreds of rotors, and really ties in best with the reverse of my statement…

Let me explain: while balancing, the slight RPM variation is typically known in high-precision work as a source of error. Not a huge one by any account, but still present. If using a balancer with a photocell or lasertach, the increase in RPM can be notable as one alleviates the 1X vibration amplitude. In lighter cases, it may only be beyond the decimal point. Worst case I’ve ever noted: abnormally vibrating (0.7 ips pk or more)light rotor (boiler fan) mounted directly on 2-pole motor shaft, 45 RPM variation from start to finish. Usual variation will usually be between 2 and 10 RPM (4-5 is a good target).

Obviously, VFDs will obliterate signs of this if the control is sophisticated and the RPM fixed to a preset: you’ll go right back to “nominal” RPM = last setting (within control precision).

The mechanical energy wasted by unwanted motion must come from somewhere… For the motor, there are only two possible variations to consume energy away from the main task and dedicate it to “shaking”: RPM and power consumption.

For RPM, the “hit” is also power consumption. For purposes of this example, I’ll use “neverland” RPMs (reality never has 1800 RPM unless synchro or VFD, and this neglects losses): take a 200HP, 4-pole motor at 1800 RPM, reduced (gears) to 900 RPM. What is the power output? 400HP. A drop of 9 RPM on that motor considered in a different application would account for (close to) 10 HP, if the relationship were linear… (9 for 1800, or 5% of speed applied to 200HP). Loose terms. This is not a thesis… The previous merely demonstrates the link between total power and RPM x HP. And we’re still constructing the example.

Consider the total power delivered by the motor, and the total amount of slip: if the motor delivers 200 HP while slipping by 20 RPM (1780 RPM rotor in relation to 1800 RPM magnetic field), the amount of slip can serve as a quasi linear power scale: 2 RPM of slip corresponds (in this case, for this motor) to 20 HP. Thus, for this motor, an extra 9 RPM of slip would represent a considerable amount or 45% of total motor power: the motor running at 1771 RPM would obviously be under overloaded strain as it would be delivering 290 HP. No need to mention the presumption of all other factors being constant and adequate (stable 60Hz line, normal voltage fed to motor at lugs, no insanely inappropriate environment temperature, etc). In this case, unbalance responsible for a 2 RPM drop means that 20 HP are used up in shaking the structure.

Do take note that my observation predates the wide adoption of high-efficiency motors. Namely because no one has wanted to pay our fees to cover balancing tasks in quite some time :D Thus, I can not positively affirm same behavior, but one could suppose same principles apply.

Being aware of the clauses of industrial power supply contracts (expected levels, penalties for spikes above steady consumption, and the like) and given our care to often seek better documentation of exact costs, not to mention the sensitive units, we had monitored many motors during balancing procedures.

Observations often placed Amp draw difference at fractional to 5 A, depending on motor. One of these days, on a large synchro motor, I’d like to get the exact power consumption before and after a balance job, but it’ll likely be as an observer busy on other items.

© 2007 by François Gagnon

Sleeve Bearing Cardinal Sin

Friday, March 16th, 2007

Strange, but there are some places where people still believe that a sleeve bearing will only work properly if the millwright carefully gouges channels for the oil, a practice no doubt derived from seeing bushings inner surfaces for which the practice is common.

Reality check: a brass bushing does not perform the same task as a sleeve bearing. Whatever a bushing sustains usually falls short of rotor dynamic concerns. “What do you mean?” The ritualistic slaying of the sleeve bearing’s damping… pardon… the gouging of oil channels REMOVES most viscous damping capacity from the sleeve bearing.

Obviously, such a comment never applies to the more sophisticated designs (tilting-pad, etc). By not apply, we mean “no one gouges those, right?”

© 2007 by François Gagnon

Report Disclaimers

Friday, March 16th, 2007

Someone on the maintenance forum asked about the intelligence or validity of including a disclaimer in a report. While I replied, and I believe I may have covered most concerns, I felt the matter was important enough to replicate the brief response.

Generally speaking, unless covered under local law (professional engineering status and commensurate insurance) and / or contract stipulation, it is best to have such disclaimers.

Report writing is an art. Including caveats in the proper location is key. Let me explain: some “consultants” operate as service industries, and others as full consultancy businesses. The status differs considerably. A contract may or may not be signed, but if a proposal or contract is issued, it will often bear much needed disclaimers or warnings.

Why? Because my client will WANT an opinion off the $1200 job in spite of the fact he will not retain the much needed and highly recommended continuation into a $20K mandate (yes, there are such mandates in vibration, and there are $250K mandates as well).

In the previous example, do you want the responsibility of any work undertaken when the full job was never contracted? Obviously not! And even LESS so in the USA. Your customer wants a “guesstimate”? Why should we be prevented from issuing one?

Disclaimers may stipulate that the expertise for the given case EXCLUDES any status reporting on bearings (for instance, you do structural work on the supports w/o analyzing the machine because it may be stopped, or you analyzed the dynamics of the rotor six months ago, not the current condition of this machine asset).

There are other ways of doing it. Presume the issuance of a “non-verified” or unsigned DRAFT report. Allows for exploration w/o committing to final professional opinion.

One colleague limits the price of any claim (linked to recommendations, as opposed to non-consultation linked, such as wping out with your car and caving in a corporate wall) to the price of the consultation.

So, instead of falling under untrustworthy or a credibility issue, it is likely far more a question of sound business practice, and getting everyone on the same page with respect to responsibility attribution.

Bearing Damage Detection: Research Issues & Culture Clash

Friday, March 16th, 2007

While recently attending a seminar, the horrors of an ever-widening “truth” of defective bearing detection methods came home to roost.

There are, in any given year, dozens of papers published on that topic. Bearings may be submitted to torture tests, or damaged purposely with seeded faults, or any other mechanism, but some specific factors emerge as a growing annoyance: the novelty aspect sought to get retained for publishing fails to promote good science and good engineering inasmuch as a complete picture is concerned.

The writer / researcher may well demonstrate that this or that measurement or signal processing technique works in his fault-finding effort, but the measurements are rarely compared to “older” standards of bearing-defect detection, and the most crucial question seems to never get an answer: when is the proposed approach better than the odler approaches? The various papers will demonstrate at length that his proposal works out, but more often than not, the accompanying data jumps out at us with alarm bells for the Crest Factor or the PeakVue or Spike Energy or acceleration levels are so blatantly abnormal that even the plant receptionist (now retired, and visiting old colleagues for receptionists mostly represent a long-gone position) would have spotted the problem. If I see a corpse lying in the middle of the street, I too can tell you that person is not in good health.

We can theorize that incipient (early) damage would have been spotted just as well, and the seeded fault’s size may be responsible for the obviously problematic levels, but more often than not, a little (perhaps a couple of hours) extra work would have documented the normal measurements’ trends and / or spectral contents to support the writer’s thesis. That is why we are in the process of completing a protocol to standardize at least a section of such papers or at least quickly extricate key indicators to comprehend the added value, if any, of the proposed approach, or its worthlessness to the practitioner in the field. A block of pertinent information would likely keep the matter much more pertinent to all invovled. Harsh, but KPIs are not just applicable to reliability and management…

Which brings us to another topic: the proper method to detect and quantify bearing damage detection has caused a LOT of ink to flow over the years. And many experts have argued the merits of one approach over another. Such experts make great claims, but often fail to fully qualify the nuances involved in their announcements.
vkc-logo-trans.gif

As a qualifier of the “failing bearing detection task”, see how the following sits with you, the reader (and feel free to comment at info@vibra-k.com or within the comment section).

1) detecting a failing bearing is not particularly difficult (the standard task sequence tedium must be completed without fail; collection, review, analysis)
2) positively identifying that it IS the bearing can be challenging in complex machines
3) knowing when to pull the bearing (remove it from service) requires a little savvy
4) knowing when to stop production to replace the bearing requires a lot of savvy
5) recognizing if and when (and how) a bearing can be “nursed” to the end of a production run demands experience

Further comments to qualify the previous (this will grow over time as preferred mode is to grow an article instead of adding multiple continuations):

For (1) Detection, there CAN be difficult circumstances or locations.

Acoustic measurement (instead of accelerometer) can help in measuring hard to reach bearing positions. Distance to source (remoteness) has always been an issue, as evidenced in some large reducers (for instance). Issues include the lack of transmissibility (or should I say propagation) of high(er) frequencies and the noise-pollution / signal contents density generated within the same spectral region by some reducer models.

The velocity / acceleration controversy, fed by one often maligned albeit well-intentioned author’s publishing of a pro-velocity article and the many disagreements it caused, is largely a NON issue: the intent was misinterpreted or article misread. As this writer remembers it, the article essentially stated that the proper method to assess bearing damage progression calls for an examination of velocity spectra, and not acceleration spectra. WAIT!

What was that author saying? He likely never meant that acceleration can not be used to DETECT bearing problems, he merely stated that from a pattern identification standpoint, the patterns obviously characterized in velocity by specific indicators (the bearing fatigue deterioration progression is well known, with the eventual appearance of bearing-defect frequencies peaks marked by flanking sidebands when modulation finally occurs; these become visible in the velocity spectrum whereas these traces were not previously to be seen) are not so characterized in acceleration. Why? In acceleration spectra, we will see the pattern much too early on, and this, even is using a linear scale. A logarithmic scale makes things appear much worse. We will see the pattern progress, mostly from amplitudes rising. The judgement call is made more difficult by relativistic concerns (must compare A to B), instead of appreciation of there / not there.

The same progression assessment CAN occur in velocity spectra when analyzing different bearing types: the split bearings (there are two main brands, so we can probably name them safely: FAG and Cooper). These useful components exhibit a pattern behavior DIFFERENT than that of other bearings. Why? If we speak of race “defects”, these are actually manufactured with a seam or joint where the raceway halves meet. Is this a problem? No! But in the usual mindset, we COULD (if not properly trained) MISinterpret the resulting spectral and overall activity (in acceleration and/or HF/Ultrasonic functions) as a “defect” of sorts. The patterns which are usually perceived as indicative of problems are here normal. Until they (eventually) progress, rising in amplitude due to abnormal conditions (damage from abrasion, contamination or fatigue).

If under normal circumstances, they appear abnormal in velocity, the acceleration signal will look much worse.

© 2007 by François Gagnon