Dirk Dusharme/Adobe
With the publication of the new VDA AIAG SPC Manual in July 2026, one of the most significant changes to statistical process control (SPC) in decades has been introduced. While much attention has been given to the new process capability indices, an equally important change is the introduction of a new approach for calculating control limits.
|
ADVERTISEMENT |
For nearly a century, Walter Shewhart’s three-sigma control limits have formed the foundation of SPC. They have proven to be remarkably effective and are still widely used in manufacturing industries today. So why does the new manual introduce an alternative approach?
The manual recommends allowing organizations to select different confidence levels when calculating control limits. Although the manual explains how these limits can be calculated, it provides relatively little guidance on why this flexibility has been introduced or how it should be applied in practice.
Based on our experience of implementing SPC systems in manufacturing environments around the world, we believe the motivation is closely related to the dramatic increase in automated data collection. Modern factories generate far more data than Shewhart could ever have imagined in 1931, creating practical challenges that traditional SPC was never designed to address.
This article explains the statistical concepts introduced by the new manual, and discusses the practical considerations for implementing them in large-scale SPC systems.
The origins of three-sigma control limits
Statistical process control was introduced by Walter A. Shewhart in his landmark 1931 publication Economic Control of Quality of Manufactured Product (latest edition from Barakaldo Books, 2022). His work established the principles that still form the basis of modern control charts.
Shewhart’s choice of three standard deviations (3σ) for the control limits represented a practical compromise between detecting genuine process changes quickly while avoiding excessive false alarms.
As Donald Wheeler has demonstrated in numerous publications, three-sigma control limits are remarkably robust and effective for stable manufacturing processes.
Manufacturing has changed
When Shewhart developed SPC, measurements were collected manually and relatively few process characteristics were monitored. Today, modern production systems continuously collect data from PLCs, vision systems, CMMs, automated gauging equipment, and IoT devices. In many industries, SPC has evolved from monitoring a handful of characteristics to continuously analyzing millions of measurements every day.
The challenge of false alarms
Traditional three-sigma control charts have a confidence level of approximately 99.73%, meaning about 0.27% of stable subgroups are expected to exceed the control limits purely due to random variation. With thousands of charts, this results in a significant number of statistical signals every day, creating alarm fatigue and making it difficult for operators to identify genuinely important process changes.
Although the manual doesn’t explicitly identify alarm overload as the motivation for introducing configurable confidence levels, it does emphasize that additional control-chart rules should only be applied when they serve a specific purpose.
What has changed
The new manual allows organizations to select different confidence levels when calculating control limits. This changes the constants used for control charts (e.g., A2, D3, and D4), allowing organizations to balance sensitivity against false alarms.
This provides considerably more flexibility. For example:
• Lower confidence levels produce narrower control limits.
• Narrower limits detect smaller process shifts more quickly.
• However, they also generate more false alarms.
Conversely:
• Higher confidence levels produce wider control limits.
• False alarms are reduced.
• Detection of genuine process changes becomes slower.
Neither approach is inherently better, but each represents a different balance between sensitivity and stability.
To understand these trade-offs, we first examine three statistical concepts: the false alarm rate, the operating characteristic (OC) curve, and the average run length (ARL).
Confidence level, OC curve, and ARL: Understanding the trade-off
Selecting a confidence level affects three important performance characteristics of every control chart.
False alarm rate
The most obvious consequence is the false alarm rate. With traditional three-sigma limits, approximately 0.27% of stable subgroups are expected to exceed the control limits. Reducing the confidence level increases this percentage, while increasing the confidence level reduces it. From an operational perspective, this directly influences the workload placed on operators and engineers.
Operating characteristic curve
A less familiar—but equally important—concept is the operating characteristic (OC) curve.
The OC curve shows the probability that a particular process shift will be detected by the control chart. Reducing the confidence level increases the likelihood of detecting small process shifts, but this improved sensitivity comes at the expense of more frequent false alarms.
Conversely, increasing the confidence level reduces unnecessary alerts but delays detection of genuine process changes.
It should be noted that these OC curves consider only violations of the control limits. Additional Western Electric or Nelson rules will further influence the actual detection performance.
Average run length
Another useful measure is the average run length (ARL).
ARL represents the average number of subgroups that will be collected before a process shift is detected. Lower confidence levels generally reduce the ARL because shifts are detected sooner. Higher confidence levels increase the ARL because larger shifts are required before the control chart signals.
For organizations producing large volumes of product, this difference can have a significant effect on the amount of nonconforming material produced before corrective action is taken.
Comparing different confidence levels
To illustrate these trade-offs, Figure 1 compares three commonly discussed confidence levels for an XR chart with a subgroup size of five.

Figure 1: Results for different confidence levels based on an XR chart with n = 5
Several observations can immediately be made.
A confidence level of 99% substantially increases the probability of detecting small process shifts. However, this comes with a corresponding increase in false alarms.
At the opposite extreme, a confidence level of 99.99% dramatically reduces false alarms but significantly decreases the chart’s ability to detect meaningful process changes in a timely manner.
The traditional 99.73% confidence level remains a well-balanced compromise between these two extremes.
Interestingly, the examples provided in the new VDA AIAG SPC Manual focus primarily on confidence levels of 99% and 99.73%, suggesting that the authors expect users to consider somewhat tighter limits where appropriate rather than universally widening control limits.
Changing the confidence level is not a way to improve process capability. It only changes how sensitive the control chart is to process variation. A wider control limit reduces false alarms but also delays the detection of genuine process changes. Manufacturers should therefore select confidence levels based on operational requirements rather than expecting improved process performance.
Practical implementation considerations
In the past, we’ve explained the statistical background behind the new VDA AIAG SPC Manual and discussed why it introduces the option of selecting different confidence levels for calculating control limits. Although understanding the statistical concepts is important, implementing these recommendations in a production environment presents a very different challenge.
Selecting a confidence level for a single control chart is relatively straightforward. Applying the same approach consistently across hundreds—or even thousands—of control charts is considerably more complex.
Based on our experience implementing SPC systems in manufacturing facilities worldwide, we believe the biggest challenge isn’t calculating new control limits. The real challenge is ensuring that SPC remains an effective tool for operators and engineers without overwhelming them with unnecessary alerts.
Here we discuss the practical considerations for implementing the new recommendations and provide our advice for organizations looking to adopt the new VDA AIAG approach.
Flexibility comes at a cost
One of the strengths of the new manual is that it no longer assumes a single confidence level is appropriate for every situation.
From a statistical perspective, this makes perfect sense. Different processes have different objectives and different levels of risk.
From an implementation perspective, however, this flexibility introduces additional complexity. Consider a company with 5,000 control charts. If every characteristic can have its own confidence level, someone must decide:
• Which confidence level should be used?
• Who is responsible for making that decision?
• How will these decisions be documented?
• How will consistency be maintained throughout production lines and plants?
• What happens when customer requirements change?
Although selecting a confidence level for a single chart is easy, maintaining different settings for thousands of characteristics can quickly become a significant engineering and administrative effort.
For this reason alone, we expect that many manufacturers will continue to use a common default confidence level for most of their control charts.
Dynamic vs. fixed control limits
The new confidence-level approach can be used with either dynamically calculated control limits or fixed control limits established during an initial process capability study.
Both approaches have advantages.
Dynamic limits automatically adapt as the process changes. They require little maintenance and always reflect the current process variation.
However, there is also an important disadvantage.
When a process slowly drifts over time, dynamically calculated limits may gradually move with the process. As a result, a genuine deterioration in process performance might not immediately produce an out-of-control signal because the limits themselves are changing.
For critical characteristics, this is often undesirable.
In our experience, safety characteristics, regulatory characteristics, and customer-critical dimensions are usually better monitored using fixed control limits established from a stable process. These limits provide a consistent reference against which future performance can be evaluated.
Dynamic limits remain valuable during process development or when establishing an initial baseline, but they should not automatically be considered the best choice for every application.
Does every characteristic need its own confidence level?
The new manual makes different confidence levels possible. It doesn’t necessarily mean they should be used everywhere.
Some characteristics clearly justify greater sensitivity. Examples include safety-related dimensions, characteristics with a history of instability, or processes where very small shifts have significant consequences. Other characteristics may be less critical and could tolerate wider control limits without increasing business risk.
Although this approach is statistically sound, implementing it consistently requires detailed engineering knowledge for every monitored characteristic. In organizations managing thousands of SPC charts, this quickly becomes difficult to maintain.
Consequently, we expect many manufacturers to adopt a practical compromise:
• Use a common default confidence level throughout the organization.
• Apply alternative confidence levels only where there is a clear engineering or customer requirement.
This approach captures most of the benefits while avoiding unnecessary complexity.
The real challenge: Alarm fatigue
In our opinion, the biggest challenge facing modern SPC systems is not the calculation of control limits. It is alarm management.
Today’s manufacturing systems generate far more data than traditional SPC was designed to handle. Even when control limits are calculated correctly, operators may still receive far more alerts than they can reasonably investigate.
Eventually two things happen.
First, operators become accustomed to frequent alarms and begin to ignore them.
Second, truly important process changes become hidden among numerous routine statistical signals.
Neither outcome improves quality.
For SPC to remain effective, operators must have confidence that when an alarm occurs, it deserves their attention.
A different way to reduce unnecessary alerts
One obvious way to reduce alarms is to increase the confidence level, thereby widening the control limits. While this reduces false alarms, it also delays the detection of genuine process changes.
In our experience, there’s often a better solution. Instead of asking simply whether a point falls outside the control limits, we should also ask whether the process itself is capable.
A process with a Ppk value of 12 is operating far inside its specification limits. Although an individual subgroup might occasionally fall outside the statistical control limits, the risk of producing nonconforming products remains extremely small. In contrast, exactly the same statistical signal on a process with a Ppk value close to 1.33 deserves immediate investigation.
Although both charts generate identical SPC signals, the operational response should not necessarily be the same.
This illustrates an important principle.
Not every statistical signal requires the same operational response.
Intelligent alert management
Within Datalyzer Qualis we have addressed this challenge by allowing alerts to be prioritized based on process capability.
For example, alerts requiring operator action can be suppressed automatically when the Ppk value exceeds a configurable threshold.
This doesn’t ignore the statistical information. The control chart still records every point and every rule violation. The difference is that operators are interrupted only when the signal represents a meaningful operational risk. Engineering personnel remain able to review all SPC information, while production operators can focus their attention on where it creates the greatest value.
In our experience, this approach produces a much larger reduction in unnecessary operator interventions than simply changing confidence levels.
Our recommendations
Based on our implementation experience, we recommend the following approach when adopting the new VDA AIAG SPC Manual.
1. Unless there is a clear engineering reason to do otherwise, use the traditional 99.73% confidence level as the organizational default. It remains an excellent compromise between sensitivity and false alarms, and avoids unnecessary configuration complexity.
2. Only use alternative confidence levels where there is a clear engineering justification. Examples include safety-critical characteristics, customer-specific requirements, or specialized process monitoring.
3. Consider fixed control limits for critical characteristics. Fixed limits provide a stable reference and make gradual process deterioration easier to detect.
4. Focus on alarm management rather than simply changing control limits. Reducing unnecessary operator interventions often delivers greater benefits than modifying the statistical calculations themselves.
5. Prioritize alerts according to process capability. A capable process and a marginal process should not necessarily generate the same operational response, even when they produce identical SPC signals.
Conclusions
The new VDA AIAG SPC Manual introduces valuable flexibility by allowing manufacturers to select different confidence levels for calculating control limits. From a statistical perspective, this is an important evolution.
However, successful implementation requires more than selecting a different confidence level. Organizations must also consider the practical realities of operating modern SPC systems that monitor thousands of process characteristics simultaneously.
The greatest improvements come not from changing the mathematics behind the control limits, but from ensuring that operators receive meaningful, actionable information.
A well-designed SPC system should help operators focus on the few process changes that truly matter—not overwhelm them with statistical signals that add little operational value.
Ultimately, the objective of SPC hasn’t changed since Shewhart introduced it almost a century ago: to detect meaningful process variation early enough to take effective corrective action. The new VDA AIAG recommendations provide additional flexibility to achieve that objective, but they should always be implemented within a broader strategy for effective process monitoring and intelligent alarm management.
Nearly 100 years after Shewhart introduced SPC, the mathematics may have evolved, but the objective remains exactly the same: Provide the right information to the right people at the right time so that meaningful process variation can be eliminated before it affects product quality.
This article reflects the author’s interpretation and implementation experience with the AIAG VDA SPC Manual. It’s intended as practical guidance and does not replace the official manual.

Comments
VDA Manual
Who are the people that have asked for the computation of limits to be altered to apparently alter the confidence for the detection of a signal? I wonder if they've ever used process behaviour charts to actually improve processes?
A triumph of computation over common sense.
This is defined by the…
This is defined by the comittee. Maybe people from the committee can explain where this comes from. In case you want to minimize the risk to produce products out of spec and you are not doing 100% control it might make sense to use tighter limits than 3 sigma and the OC curve gives you an idea of the risk in relation to the Ppk but you are right for normal process improvement and an acceptable Ppk of 2 or higher it would not make much sense.
Focusing on the wrong things
False alarms are of concern only when a process is operated predictably. When a process is operated unpredictably false alarms are of no concern since the signals of change will be much more abundant than the false alarms.
Likewise, the objective is to detect changes that are large enough to be of economic consequence rather than detecting any and every small shift. The speed with which we detect a shift is not so important as how we react to the shift. If you think process behavior charts are there to tell you when to adjust the process you will not get the full benefit of the charts. If you look for the assignable cause of the process change, then you will gain new insight that will allow you to operate with greater capability, less inspection, and higher quality.
The purpose of a process behavior chart is to characterize the process behavior as being either predictable or unpredictable. This classification has nothing to do with conformance of the product, although the AIAG VDA manual is clearly focused on using their version of SPC as an alternative to inspection (Process monitoring rather than process improvement). This classification into these two broad categories is relatively easy to do. Ultra precise limits are not needed.
So while the comments about the trade-offs for the different width limits are technically correct, they are irrelevant for those who wish to simply operate their processes up to their full potential and thereby increase quality, increase productivity, and increase their market share.
Process behavior charts as created by Shewhart are a simple, statistical axe. They get the job done. An axe works by brute force. A process behavior chart simply separates the probable noise from the potential signals. It does not do to try to put too fine an edge on an axe. Yet the AIAG VDA manual is all about trying to shave with an axe.
I totally agree..
I totally agree. The problem with high amounts of data nowadays is that we easily have 60000 control charts in place at the shop floor. With a semiconductor customer 60000 characteristics are monitored with control chart continuously, so we need to make sure when we address an OOC, operator and engineering time is spent as effective as possible. And almost all 60000 charts are in control. In aerospace we have products where with one CMM measurement 7000 characteristics are measured...Real time SPC is required in more and more industries and with new technology we follow more product and process characteristics with a higher frequency.
I have seen too many installations where all data is collected, charted and given to the operators to apply SPC. That will always fail so therefore I think it is mandatory to provide solutions to use the techniques in the appropriate way and not get lost in thousands of signals (Correct or false alarms)
You can argue that this is not where behavior charts are intended for and I agree but it is the most powerful tool I know to identify if all processes are (still) in control and which process should get our attention but we need to assist the operator how to prioritize and not drop an impossible task on his plate. But like always thanks for your valid comments
It's not a problem with high…
It's not a problem with high amounts of data, it's a problem of thinking about what, in the opinion of a knowledgable person, are the key characteristics that need to be demonstrated to enable the process to be efficient.
Just because you provide intelligence to enable this to happen with 1000's of points doesn't mean that it's adding value to controlling and minimising the variability of the part or assembly.
There will never be a substitute for knowledge, this is increasingly getting lost over time.
AIAG always does a good job, and this is easy to implement
I see AIAG as the best place to go for authoritative, well thought out references for quality. The AIAG/VDA FMEA manual, for example, does away with a lot of the problems (risk priority numbers--Don Wheeler's article on RPNs is worth reading--and probability-based occurrence ratings that cannot be calculated in practice) that make people not want to do FMEAs. IATF 16949:2016 offers a lot of material that is not in ISO 9001:2015, and most is relevant to all manufacturing and not just automotive.
It's always been possible, and relatively easy, to set probability-based control limits, including for non-normal distributions. The previous AIAG SPC manual showed how to do this. You just calculate the 99.73 and 0.27 percentiles of the actual distribution, and StatGraphics will do this. There are Excel functions that will do it as well. While it is true that traditional 3 sigma limits work for sample averages due to the central limit theorem, you have to fit the non-normal distribution anyway to get the Ppk. If you use the normal distribution, the estimate of the nonconforming fraction can be off by orders of magnitude.
The chi square distribution (available in Excel) can set probability based limits for the s chart. I meanwhile created a Visual Basic integration routine to set them for the R chart, and I think this can even be used for non-normal distributions.
If your Ppk is really good, and you don't want to respond to every out of control signal that comes along, you can set a center band rather than a center line that shows where the process mean is allowed, i.e. small shifts don't require action. The control limits are 3 standard deviations from the upper and lower parts of the band.
Add new comment