Process Maps and FMEA Help Prepare Utility for Disaster

The Six Sigma methodology contains many tools that can be used successfully throughout an organization to improve processes and prevent failures, regardless of whether the full DMAIC (Define, Measure, Analyze, Improve, Control) roadmap is used. Demonstrating the efficacy of these tools for preventing or solving real business problems is a powerful way to market Six Sigma. Two of these tools, process maps and the failure mode and effects analysis (FMEA), were applied in the following case study. A team at a wastewater utility used them to prepare for possible issues in the wake of retiring staff, and in the process helped ready the facility to face a powerful natural disaster.

Case Study: Virginia Wastewater Utility

A northwestern Virginia wastewater utility with a relatively small workforce was concerned about the potential impact of pending retirements of experienced operators. Industry statistics demonstrate why utility management was concerned:

  • Average age of wastewater utility employees – 47 years
  • Average age of lead operators – 52 years
  • Average retirement age – 56 years
  • Average years of service – 24 years

Experienced operators who were approaching retirement age were very knowledgeable, but much of their knowledge about operations was the result of years of experience and was not always well documented. This fact was particularly true of knowledge about infrequent but potentially high-risk events such as floods at the treatment plant.

To address this concern, the utility’s engineering consultant designed and facilitated a workshop to document critical knowledge about utility operations. A by-product of the workshop was an assessment of plant flooding risk, which helped the utility identify and implement preventive measures. Coincidentally, a major hurricane and subsequent flooding hit the area a few weeks after the workshop. The measures put in place through the workshop enabled the wastewater utility to operate continuously during the disaster.

Handpicked Content :   Using Taguchi's Loss Function to Estimate Project Benefits

Workshop Objectives

The primary objectives of the workshop were to map critical utility operating knowledge, identify the flow of work that directly addressed critical operating parameters, and prepare the groundwork for future knowledge capture and dissemination efforts.

The first task was to identify target processes and define basic process parameters, including the following:

  • Outputs
  • Customer(s) for outputs
  • Process owners
  • Inputs
  • Suppliers of inputs
  • Process boundaries
  • Quality characteristics of the process outputs

Workshop Process

Before the workshop, the consultants worked with utility management to identify teams and several processes. These included wastewater collection, water distribution, wastewater treatment and water treatment. In the workshop, the team mapped several critical subprocesses within each process. For example, for the wastewater treatment process, they mapped the subprocess for responding to a flood event. Figure 1 captures a SIPOC (suppliers, inputs, process, outputs, customers) summary of this process. Figure 2 is a more detailed process map.

Figure 1: SIPOC for Wastewater Treatment Plant Flood Response

Figure 1: SIPOC for Wastewater Treatment Plant Flood Response

Figure 2: Process Map for Flood Response

Figure 2: Process Map for Flood Response

Identifying Risks with FMEA

After the team mapped the flood response process, they compiled an FMEA to identify process failure risks. The FMEA is used to evaluate the nature and impact of a failure event, including the severity of the failure effect, the expected frequency of occurrence, and the likelihood that the current process will prevent or detect the failure. The team rated each attribute on a 1-to-10 scale (Table 1).

Handpicked Content :   Leverage ITIL and Six Sigma Together to Maximize Outcome
Table 1: FMEA Rating Scale


Frequency of Occurrence

(Likelihood of Prevention)

1Be unnoticed and not affect the performance1Once every 7+ years1Certain that potential failure will be prevented before it impacts productivity or schedule
2Be unnoticed; minor affect on performance2Once every 3-6 years2Almost certain potential failure will be prevented before it impacts productivity or schedule
3Cause a minor nuisance; can be overcome with no loss3Once every 1-3 years3Low likelihood potential failure will be prevented before it impacts productivity or schedule
4Cause minor performance loss4Once per year4Controls may prevent the potential failure from impacting productivity or schedule
5Cause a loss of performance; likely to result in a complaint5Once every 6 months5Moderate likelihood potential failure will impact productivity or schedule if undetected
6Result in partial malfunction6Once every 3 months6Controls are unlikely to prevent the potential failure from impacting productivity or schedule
7Cause customer dissatisfaction7Once per month7Poor likelihood potential failure will be prevented before impacting productivity or schedule
8Render the product or service unfit for use8Once per week8Very poor likelihood potential failure will be prevented before impacting productivity or schedule
9Be illegal9Once every 3-4 days9Current controls will probably not even detect the failure
10Injure a customer or employee10More than once per day10Absolute certainty that current controls will not detect the failure
Handpicked Content :   Improved IT Project Forecasting Through Six Sigma

After applying the rating scale, the team was able to assign risk priority numbers (RPN), which are calculated as the product of the severity, frequency of occurrence and detectability scores. The team set an RPN of 60 as an initial threshold value to determine if drilling down on any step of the process was necessary to further define the response to a failure. In Table 2, for example, the RPN scoring for the risks deemed worthy of further mitigation (either by the RPN scores or the process knowledge of the experienced operators) are highlighted in yellow or red. After the workshop, the plant manager and his experienced operators used the results of the FMEA to clarify the response procedure and guide communications to the plant staff.

Table 2: Excerpt of FMEA Worksheet on the Flood Response Process
Potential Failure
Potential Failure
Monitor weather and flowsFlows exceed filter capacityBackup clogs filters6Not paying attention to weather reports4Filter alarm; SOP checklist if high flows; operator knowledge372
  Backwash water will overflow clarifiers7Not paying attention to weather reports4Filter alarm; SOP checklist if high flows; operator knowledge384
  Permit violation9Not paying attention to weather reports4Filter alarm; SOP checklist if high flows; operator knowledge3108
Decision to prepare plant for floodFlow surge basins not activatedFlood damage, backups8Poor judgment; lack of experience1Filter alarm; SOP checklist if high flows; tacit knowledge216
  Permit violation9Poor judgment; lack of experience1Operator knowledge218
Secure plant for high flowsFlow surge basins not activatedBackups7Poor judgment; lack of experience4Filter alarm; SOP checklist if high flows; tacit knowledge384
  Permit violations9Poor judgment; lack of experience4Operator knowledge272
Shut power to rotorsPower stays on, rotors keep turning, shut off wrong rotorRuin gear reducers; rotor bearings; solids blowout8Operator inattention, inexperience, lack of training3Training; operator tacit knowledge; SOP on rotor shut-off6144
Kill power to preliminary treatment buildingOperator does not kill powerTrip breaker when water covers motor, other power failures, electrocution9Operator inattention, inexperience, lack of training2EOP on flood conditions6108
Decision – preliminary treatment building 1st floor flooded?Building is floodedMotor failure, loss of paddle, grit machine, manual bar screen, safety issues10Happens overnight; pump station failure; pressure transducer failure; redundant float system failure2Safety SOPs; training; tacit knowledge; high water wet well alarm6120
Monitor dry well water levelDry well failureDry well floods, lose pump station8Operator inattention, inexperience, lack of training2Operator tacit knowledge;696
Handpicked Content :   Use a Modified FMEA to Mitigate Project Risks

Post-workshop Implementation

Process mapping and FMEA analysis provided a structured approach to identifying and mitigating risk for the flood response process. Utility supervisors recognized the value of the exercise by requesting (without any prodding) the process documentation produced during the workshop. The utility staff then refined their emergency response plans to address the risks highlighted by the FMEA. This updated response plan proved invaluable when, three weeks after the workshop, Hurricane Isabel ravaged the eastern seaboard.

The hurricane was at the time the costliest natural disaster in the history of Virginia. Strong winds affected 99 counties and cities, downing thousands of trees and leaving about 1.8 million people without power. Interior Virginia bore the brunt of the heavy rains and flooding, with a maximum rainfall total of 20 inches in the Shenandoah Valley, not far from the site of the treatment plant. The director of the utility credited the preparation inspired by the workshop and the FMEA exercise with ensuring that the treatment plant experienced only minor flooding and no interruption of operations.

Handpicked Content :   US Fuels Improves Invoicing Accuracy Using Work-out

You Might Also Like

Leave a Reply