top of page

The success of Reliability Assessments depends on the quality of the facilitation.
The success of Reliability Assessments depends on the quality of the facilitation.

Assessing critical infrastructure and facilities is essential for maintaining performance as systems age. Mid-level engineers are frequently tasked with leading a reliability assessment with limited training. The good news is that you don't need to be a subject matter expert to be successful. But you do need a structured collaboration approach and a mental model to help you through the tough spots. Success rises and falls based on the quality of the facilitation.

Reliability Assessment Defined

A reliability assessment is a decision-making tool that assists in making trade-off decisions related to system performance and financial investments. The major benefit is a comprehensive understanding of the interrelated physical parts, human aspects, and interfaces.


In the least case, reliability assessments will indicate a system's single points of failure and generate mitigation actions that make success more probable. In the greatest case, a reliability assessment will quantify the probabilities of success and failure.

Seven Components of a Reliability Assessment

This is my standard seven-step process for reliability assessments:

  1. Establish the problem/function statement.

  2. Verify and calculate future stresses (loads/demands/flows).

  3. Establish the system condition and asset performance history.

  4. Perform system reliability analysis.

  5. Evaluate the ability to predict unreliability and accept the associated risk.

  6. Determine mitigation and improvement alternatives (decision analysis).

  7. Document and communicate (communication)


Human factors or human interfaces are aspects of most physical systems. Human factors have tools and approaches that are not common to other fields of practice and are often overlooked by many physical systems professionals.

Facilitation Defined

Facilitation is defined as a structured session(s) in which the meeting leader (the facilitator) guides the participants through a series of predefined steps to arrive at a result that is created, understood, and accepted by all participants.

Group Collaboration Requires Interactive Communication

Two forms of communication are applicable when groups collaborate. The first is linear communication, which involves moving information from a source to a receiver.

 These "sender-message-receiver" models are common when information is shared directly from one person to another with less subject-specific knowledge.

Two-way or interactive communication occurs when message senders and receivers share information. The basic processes and components of a linear communication model are required - after all, each party must be able to transfer a clear message to the other. However, similar knowledge and multiple feedback loops are necessary for interactive communication.

Facilitators spend a lot of effort making sure participants have mutual understanding and multiple feedback channels so that collaboration occurs.

What is CATER?

The mental model CATER will help you recall the five ways to move any facilitated applications from good to great. FINESSE is the backbone of effective communication while CATERing to participants creates comparable knowledge and opens feedback channels for successful collaboration.

Five Ways CATER Makes a Difference

CATER makes a big difference when facilitating reliability assessments. I cover more than these five ways in training sessions. These represent one example from each letter of CATER.

Communicating in Pre-session Exchanges

Many participants will have different definitions and understandings of the key concepts. Pre-session exchanges allow a facilitator to learn the organization's reliability language and find out whether everyone shares the same understanding.

CATER provides a mental model that helps when reliability assessments get tough.
CATER provides a mental model that helps when reliability assessments get tough.

 Reliability, availability, and risk are three of my favorites that you encounter wide variations wherever you go. Costly (or expensive) is also a common word with very different definitions depending on who you talk to within an organization.

My favorite case example is from a multi-site mining company and its uncommon definition of Overall Equipment Effectiveness (OEE). After three pre-session exchanges, I discovered that OEE had become a type of sport within the organization for over a decade. Different managers changed this key performance indicator to justify whatever they wanted. It became clear that the reliability assessment should not be anchored to this definition.

Ask Powerful Questions

The most powerful questions when facilitating reliability assessments relate to understanding how things work. However, facilitators and subject matter experts (SMEs) tend to blow through the basic functions that are the backbone of reliability assessments.

One great example I use comes from a pharmaceutical company. The assessment began as a root cause analysis and eventually led to a full reliability assessment to resolve all single points of failure. The most interesting part is that the sterilization system used a common autoclave (similar to a large pressure cooker) and was not complicated. The maintenance manager exclaimed at one point, "You are going to ask the most basic questions about every autoclave system we have ever seen!" He was right. And it made all the difference.

Anticipate Trouble

Many subject matter experts either want to be a designer or think they can do someone else's job better. Focus on a common understanding of the system; avoid direct conflict with subject matter experts in the live sessions over terminology or theory.

The example that most often comes to mind is from a reliability assessment I led for a wastewater utility near Charleston, SC. The CEO and COO believed that one pump station was more critical than the others due to its volume and proximity to a major waterway. Both had been at the utility for nearly 30 years and had built the system from the ground up. The trouble was that the staff had reconfigured the overflow. Everyone knew it but me (the facilitator) and the top two executives. But it was not the time to argue about it in the group session.

Engaging Exercises

Block diagrams and business process maps should be developed live with the participants (preferably on a whiteboard or projected on a screen in Excel) to enhance participation, create consensus, and minimize individual biases. However, few things are more boring. Facilitators should develop the block diagrams and business processes in advance to identify obvious gaps and to help the group sessions move efficiently.


Assessing reliability for a large water system is not trivial.
Assessing reliability for a large water system is not trivial.

A good example is from a major water supply system that supplies more than one million people. I conducted the reliability assessment in two phases because the owner believed the western part of the system was bulletproof due to its redundancy. It took us six months to get to the second phase. Then, it took me about six minutes with a rough block diagram to conclude there was no full redundancy. But the result in the ensuing team session was better as everyone came to their own conclusions as we worked through it on the whiteboard.

Manage the Rhythm

Having a structured approach is important to any type of facilitation. Participants need to know what they are doing, the sequence they are doing it, how they will know when it is time to stop, and what information will be developed or modified between sessions.

The seven-step process for reliability assessments is one that I developed over the years with several colleagues. We could not find a better one in a book. We sometimes struggled when we tried unique approaches to fit different situations.

Reliability assessments are thorough and rigorous, but that also means they can be boring and frustrating to participants. You need a structured approach to manage the rhythm and the flexibility to adjust when you encounter low points.

How Do You Guide Reliability Assessments

Reliability assessments are among the toughest things for most technically trained professionals to facilitate. Remember first that you don’t have to be the senior subject matter expert to lead the assessment. In fact, you’ll be a better guide (facilitator) if you are not. Next, use a structured approach. And finally, have a mental model like CATER to help guide you through the tough times.


Excerpts from this article are taken from Facilitating with FINESSE: A Guide to Successful Business Solutions. This article first appeared on Communicating with FINESSE.



 

Join us for the free April webinar on communicating reliability assessments.

Join CWF for April's free monthly webinar on communicating reliability assessments.


The systems thinking required to conduct a reliability assessment is not easily expressed. This free webinar will provide tips for addressing the three most important things that senior management wants to understand and a methodology for developing the report and presentation.


Two case examples will be used to demonstrate presentation structure and visuals that are recommended as good practice.



 

Communicating with FINESSE is the not-for-profit community of technical professionals dedicated to being highly effective communicators and facilitators. Learn more about our publications, webinars, and workshops. Join the community for free.


 

JD Solomon is a licensed professional engineer (PE), Certified Reliability Engineer (CRE), and Certified Reliability and Maintenance Professional (CRMP). is the author of Communicating Reliability, Risk & Resiliency to Decision Makers: How to Get Your Boss’s Boss to Understand and Facilitating with FINESSE: A Guide to Successful Business Solutions.


 

JD Solomon Inc. provides solutions for program development, asset management, and facilitation at the nexus of facilities, infrastructure, and the environment. Subscribe for monthly updates related to our firm.



Spend your time getting aligned with the boss on what they believe is the big decisions versus the small ones.  JD Solomon Inc. provides project development solutions.
Spend your time getting aligned with the boss on what they believe is the big decisions versus the small ones.

The story is a constant one. I saw it again just last week on a big program. In that case, one of the project managers saw an incident as something major and made it a big deal through a couple of emails and then as the primary subject of the meeting. Unfortunately, the program manager and the executive sponsors did not see it the same way. The project manager is now in purgatory, not the offending consultant and contractor. Project managers should know these three things about the big stuff and the small stuff.

 

#1 Most Decisions Are Tactical

Most decisions are similar to the hundreds we make every day to live our lives safely. Your boss, especially your boss's boss, wants their project managers to make these decisions without much fanfare.


If I walk outside and see a tiger, my simple response is to run. It is a simple rule of thumb that ensures my survival. It may not be an accurate or appropriate response – after all, the tiger may be a tame tiger, an old toothless tiger, or even a tiger chained to a tree. Nevertheless, I behave to avoid the hazard and ensure my survival.


Another type of tiger is Aubie, Auburn University's mascot. When I see Aubie, I yell 'War Eagle' and give him a high five. This may not be any more accurate or logical than running from a live tiger. After all, the person in the mascot suit may be a person intending to do me harm. As a rule of thumb, the odds of a negative outcome are remote, so I yell 'War Eagle' and give him a high five anyway.

 

#2 Big "Strategic" Decisions Take Time

Big decisions are relatively few. They take months or years to make and are categorized. Data analysis and statistical thinking are typically needed to make really good, big decisions. Big decisions require teams and layers of management because their resolution must be thoughtful and measured.

 

#3 Get on the Same Page

One of the greatest dangers for project managers is mistakenly considering a decision to be one type and the boss or boss’s boss considering it to be the other type.


In practice, I see the mistake as common in one direction as the other. In other words, I see many project managers blow through decisions they consider to be small ones when, in fact, their superiors saw the same decision as a game changer. On the other hand, I see many project managers allocate time, resources, and credibility to decisions that their bosses consider to be day-to-day, tactical decisions.

 

How to Separate the Big Stuff from the Small Stuff

The short answer is to get aligned with senior management. That is often easier said than done. These are a few ways:

  1. Charter (and re-charter) your projects regularly. Constantly update key success factors and key decisions.

  2. Establish weekly communication summaries.

  3. Provide the opportunity for senior management to participate in milestone reviews.

  4. Constantly segregate issues into tactical and strategic ones. Work the problem accordingly. Avoid drama.

  5. Effectively communicate. The most complex issues need to be communicated in less than three minutes (or about 300 words).

 

Three Things Project Managers Should Know

Remember that there are tactical decisions, strategic decisions, and differences of opinion on the big stuff and the small stuff. The perception of the boss, especially the boss's boss, matters most. Spend less time acting independently or convincing superiors to see it your way. Spend your valuable time as a project manager getting in alignment and staying there.


 

JD Solomon Inc. provides solutions for program development, asset management, and facilitation at the nexus of facilities, infrastructure, and the environment. Subscribe for monthly updates related to our firm.


 


Reliability, Availability, and Dependability all matter. In practice, dependability matters most. JD Solomon Inc provides practical solutions.
Reliability, availability, and dependability all matter. In practice, dependability matters most.

Reliability, dependability, and availability are key concepts in systems thinking and asset management. The distinctions around reliability and availability are usually most frequent within the reliability and maintainability community. However, improving reliability and availability are most suitable for the dark chambers of design. Most of what we do on the front lines relates to the lesser-used concept of dependability.

 

Boring (but important) Definitions and Measures

What is Reliability?

Reliability is the probability that an item will perform its intended function for a specified interval under stated conditions. Key aspects of the definition include probability, function, time, and conditions.

 

From a technical perspective, reliability addresses the period leading up to the first failure in repairable systems.

 

Reliability is often measured by uptime, failure rate, and mean time between failures (MTBF). In many sectors, downtime can result in significant financial losses or endanger lives. A system with a high MTBF is considered more reliable than one with a low MTBF.

 

What is Availability?

Availability makes for great techncial analysis but is lost in coversations with senior management.
Availability makes for great techncial analysis but is lost in coversations with senior management.

Availability is the ability of a product (item) to be in a state to perform its designated function under stated conditions at a given time. The definition of availability may include the time to repair (time on the wrenches), preventative and corrective maintenance time, and administrative time (including or not including waiting on parts).


For repairable systems, availability addresses the period following the first failure.

 

Availability is measured in three different ways.

 

What is Dependability?

Dependability is the probability that an item will meet its intended function during its mission. Dependability is often underused in R&M circles but is a powerful term usually synonymous with reliability when communicating with decision makers. It is similar to reliability because time and operating conditions are specifically limited to the mission.

 

Dependability is often measured by mean time to repair (MTTR), the average time a system takes to recover from a failure. A system with a low MTTR is considered more dependable than one with a high MTTR.

 

Factors that Impact Reliability and Dependability

Except for systems designers and analysts, most decision makers are unaware of the fine points of availability. We’ll discuss the finer aspects of reliability and dependability here.

 

Factors Impacting Reliability

Design Quality

The design determines a system's reliability. Maintenance can only restore a system to its original state. We must have the right tools for the job.

 

Environmental Conditions and Operational Stress

Both are part of the reliability definition. In most cases, systems in the filed are less than their intended reliability because their basis of design has changed.

 

Component Quality

High-quality components are one way to achieve fault avoidance, which is one of the key reliability measures.

 

Testing and Quality Control

Rigorous testing during development and roll-out is another form of fault avoidance.

 

Redundancy

Redundancy is a form of fault tolerance that provides switching to backup components. It reduces downtime, failure rates, and MTBF.

 

Factors Impacting Dependability

Safety Measures

Safety features and protocols contribute to a system's dependability so that it does not harm users or the external environment during mission execution.

 

Security Measures

Dependable systems incorporate robust physical and cyber security measures to protect against disruption.

 

Resilience

The ability to recover quickly from disruptions or failures is key to ensuring dependability. Remember dependability is usually measured in terms of mean time to repair (MTTR).

 

Adaptability

Many definitions of resilience include adapting over time rather than simply bouncing back when under distress. Adaptability is an important aspect of fulfilling an essential mission.

 

Training and Documentation

Adequate user training and documentation of business processes establish understanding and allow systems to recover quickly if trouble occurs during mission execution.

 

Feedback Mechanisms 

Establishing feedback loops is essential for effective communication. Effective communication is essential for reducing human errors.

 

Regulatory Compliance 

Violations of regulations and standards stop a mission in its tracks. This is especially true in critical industries.

 

Comparing Reliability and Dependability

The key distinction between reliability and dependability lies in the context of their usage.

 

Reliability is the more common term and appropriately incorporates system performance from conceptual design through decommissioning.

 

Dependability represents a deeper level of assurance. It implies that a system meets expectations consistently and is trustworthy in critical situations.

 

Moving Forward

Reliability, availability, and dependability are key concepts in systems thinking and asset management. Reliability and availability are more common among designers and analysts, but reliability and dependability are commonly used among decision makers and on the front lines. For my money, dependability is most important. After all, that is what we, as practitioners, do most on the front lines.


 

JD Solomon Inc. provides solutions for program development, asset management, and facilitation at the nexus of facilities, infrastructure, and the environment. Subscribe for monthly updates related to our firm.


 


Experts
bottom of page