Manufacturing Process Development and Approval —— Comprehensive Lifecycle Management from Process Design to Mass Production Release

1. Introduction: Why Process Development and Approval Are the Core Battlegrounds of Quality Management

In the quality management system (QMS) of manufacturing, product design quality and manufacturing process quality are considered the two pillars that determine the final product quality. Product design determines the inherent quality level of the product—what it can potentially be; while the manufacturing process determines the extent to which the product quality is realized—what it actually becomes. Extensive corporate practices have shown that a significant proportion of batch quality issues do not stem from design flaws but from insufficient process development, superficial process validation, and formalistic process approval.

A typical scenario: After a new project is initiated, the process department hastily produces drawings without adequate process design. Procurement purchases equipment based on the drawings, and production arranges tooling according to the equipment capabilities. The quality department only gets involved for process validation after the production line is built. The result is—high defect rates after the production line is launched, inadequate process capability, and frequent engineering changes and rework becoming the norm. This "go live first, rectify later" model is essentially the consequence of missing or ineffective process development and approval stages.

Process development and approval refer to the systematic control process from the design of process schemes, through process risk analysis, control measure design, and process capability validation, to the final mass production release. It serves as a bridge from "what can be designed" to "what can be manufactured well," acting as a critical hub connecting product development and mass production.

This article will systematically discuss the comprehensive lifecycle management methods for manufacturing process development and approval from four dimensions: stage division of process development, core toolchain, process validation methods, and approval release mechanisms, helping quality and process professionals build a complete process development control system.

2. Four Key Stages of Process Development

Manufacturing process development is not a one-time task but a process that needs to follow four progressive stages: concept design, detailed design, validation and confirmation, and mass production approval.

Stage One: Process Concept Design

Process concept design is initiated during the project initiation phase. Its inputs are the product design outputs and project goals, and its outputs are the process flow diagram (Process Flow Diagram) and a preliminary process scheme. The core tasks of this stage are to answer three questions: What processes are needed to complete product manufacturing? How are the material and information flows arranged between processes? Which processes are key processes that require focused control?

The quality of the process flow diagram directly determines the foundation for all subsequent work. A high-quality process flow diagram should include: process names and numbers, the sequence of processes, the flow of materials and information, key process markings, special characteristic associations, and inspection and testing nodes.

A common misconception in process concept design is to simplify the flow diagram to a "list of processes"—listing only the step names without marking key control points and inspection nodes. This simplified flow diagram often leads to "control omissions" in later PFMEA and control plan development—some processes that should be closely monitored are unintentionally skipped.

Stage Two: Process Detailed Design

The process detailed design stage involves expanding each process in the process flow diagram into specific work schemes. This includes: determining the process parameters (temperature, pressure, speed, time, etc.), selecting equipment and tooling, designing work methods, establishing inspection standards, and determining personnel skill requirements.

The most critical input at this stage is the PFMEA (Process Failure Modes and Effects Analysis). PFMEA is not just a standalone "form-filling" task but the methodological core of process detailed design—by systematically analyzing potential failure modes for each process, it identifies the process characteristics that need focused control, thereby providing design basis for the control plan and work instructions.

The process detailed design should output the following document package:

• Work instructions (SOP) and standardized operation cards
• Equipment parameter tables and equipment operation specifications
• Inspection specifications and measurement system plans
• Tooling and fixture design plans
• Personnel training plans and skill matrices

In actual practice, the most common issue in process detailed design is the disconnect between "design" and "reality"—the process department draws diagrams and compiles documents in the office, while production line operators and team leaders are not involved in discussions. The result is that the designed process does not match the actual operating conditions, either because the parameters are set too idealistically and cannot be achieved, or because the control requirements do not align with the inspection capabilities.

Stage Three: Process Validation and Confirmation

Process validation and confirmation are the stages most likely to be compressed in process development—under project schedule pressure, "produce first, validate later" almost becomes the norm for many companies. However, a process that has not been fully validated is like a ship that sets sail without a trial run—highly risky.

Process validation includes two levels:

• Process Design Validation: Confirm whether the process design meets the expected functional and performance requirements. This is typically done during the pilot production phase by producing a certain batch of products according to the designed process parameters and control plan, and then testing whether the products meet the specification requirements and whether the process is stable and controlled.
• Process Capability Confirmation: Confirm whether the process has the ability to consistently and stably produce conforming products. This is achieved through process capability studies (Ppk/Cpk) to quantitatively assess the actual capability level of the process. For key characteristics and special characteristics, a Cpk of ≥1.33 (corresponding to a process nonconformance rate of about 63 PPM) is usually required; for safety-related characteristics, the requirement is often higher (Cpk ≥1.67).

A critical node in process validation is the Initial Process Capability Study. This is not done after mass production stabilizes but should be conducted during the pilot production phase. The initial process capability study typically focuses on three aspects: process stability (judged using control charts), process capability index (quantitatively assessed using Cpk/Ppk), and the reliability of the measurement system (ensured through MSA to guarantee data credibility).

Stage Four: Process Approval and Mass Production Release

Process approval is the endpoint of process development and the starting point of mass production. It is not a simple signing action but a systematic review and release process—by comprehensively reviewing the outputs of the previous three stages, it confirms whether the process has reached the conditions for mass production.

Typical mass production release standards include:

• The process flow diagram is complete and has been signed off by relevant departments
• The PFMEA has been updated and high-risk items have improvement measures in place
• The control plan has been developed and aligns with the PFMEA
• The work instructions have been published and operators have been trained
• The initial process capability meets the target value (usually Cpk ≥1.33)
• The measurement system analysis (MSA) has been passed
• The pilot production report is completed and the results are satisfactory
• The quality issue list is closed or has a clear rectification plan

This process approval is typically conducted in the form of a "mass production approval meeting," convened by the project quality leader, with participation from process, production, equipment, and procurement departments. The approval decision can result in three outcomes: mass production approval, conditional approval (rectification required within a specified period), or disapproval (not meeting mass production conditions).

3. Core Toolchain and Synergistic Relationships in Process Development

Process development is not a solo effort of a single tool but a collaborative operation of a toolchain. Understanding the logical relationships between tools is more important than mastering a single tool.

Four Core Tools of the Toolchain

Process Flow Diagram is the foundational skeleton of the entire toolchain. It defines the boundaries of the process, the hierarchy and sequence of processes, and serves as the input source for all subsequent tools. The quality of the process flow diagram directly limits the depth of PFMEA analysis.

PFMEA is the risk analysis engine of the toolchain. It identifies potential failure modes, failure effects, and failure causes for each process, and determines priorities based on severity (S), occurrence (O), and detection (D) scores. The output of PFMEA—prevention and detection measures for high-risk failure modes—is the direct input for control plan design.

Control Plan is the execution guideline of the toolchain. It converts the risk control measures identified in the PFMEA into executable control plans, specifying what needs to be controlled in each process, the methods used, the control frequency, and who is responsible. The control plan transforms the "verbal measures" in the PFMEA into "written requirements."

Work Instructions and Standardized Operations are the implementation carriers of the toolchain. They further convert the control requirements in the control plan into specific operational steps and inspection standards that frontline operators can execute.

Common Disconnection Issues Between Tools

In actual application, disconnection in the toolchain is the most common systemic issue, primarily manifested as:

• Mismatch Between PFMEA and Control Plan: High-risk failure modes identified in the PFMEA do not have corresponding control measures in the control plan, or some control requirements in the control plan lack risk analysis basis in the PFMEA.
• Inconsistency Between Control Plan and SOP: The control plan requires "XX dimension to be inspected every 2 hours," but the SOP states "3 pieces inspected per shift"; the control plan requires "first article must be confirmed by the inspector," but the SOP states "operator self-inspection is sufficient."
• Untimely Updates to Process Flow Diagram: When process changes occur, the flow diagram is not updated synchronously, leading to subsequent PFMEA and control plan analyses based on outdated process designs, resulting in systemic discrepancies between documentation and reality.

The fundamental solution to these disconnection issues is not to strengthen "audits" and "inspections" but to establish a data linkage mechanism between tools—when a control measure in the PFMEA changes, the system or process should automatically trigger an update to the control plan. In highly digitized companies, this can be achieved through PLM (Product Lifecycle Management) or QMS (Quality Management System) to integrate toolchain management.

4. Practical Methods for Process Capability Validation

Process capability validation is the core basis for process approval. Without sufficient process capability data, process approval becomes a "gut feeling" decision.

Implementation Steps for Initial Process Capability Study

Step One: Data Collection Planning. During the pilot production phase, determine the process characteristics to be studied, the sampling plan, sample size, and data collection period. A sample size of at least 25 subgroups (each group containing 3-5 pieces) is typically recommended to ensure that the data represents the normal variation range of the process.

Step Two: Process Stability Analysis. Use control charts (typically Xbar-R or Xbar-S charts) to determine whether the process is in a statistically controlled state. If the control chart shows abnormal points (beyond control limits) or non-random patterns (continuous rising/falling trends, periodic fluctuations, etc.), the cause must be identified and the abnormality eliminated, followed by re-collection of data.

Step Three: Process Capability Calculation. After confirming process stability, calculate the Cpk (process capability index) and Ppk (process performance index). Cpk measures the inherent capability of the process, while Ppk measures the actual performance. The difference between the two reflects whether the process is in a controlled state—when there is a significant difference between Ppk and Cpk, it indicates the presence of unstable factors in the process.

Step Four: Capability Judgment and Improvement. Compare the calculated capability indices with the target values. If they are below the target, the causes need to be analyzed and improvement measures implemented. Common reasons for insufficient capability include: inadequate equipment accuracy, improper process parameter settings, excessive operator variability, and incoming material fluctuations.

Verification Strategies for Small Batch Processes

In production modes such as aerospace and large equipment, where small batch and multi-variety production is common, traditional large-sample process capability study methods are not applicable. In such cases, the following alternative methods can be used:

• Pre-Control Method: Set pre-control lines at the 1/4 and 3/4 positions of the specification limits, and judge whether the process is suitable for continued production based on the qualification of five consecutive pieces. This method does not require a large sample size and is suitable for small batch scenarios.
• Zero-Failure Testing: Verify process capability by continuously producing a certain number of conforming products. Based on statistical principles, the absence of failures in N consecutive pieces can prove that the process nonconformance rate is below a certain level. For example, 59 consecutive pieces without failure can confirm that the process nonconformance rate is below 5% (with 95% confidence).
• Analogous Analysis Method: Refer to historical capability data of similar processes, combined with an analysis of the differences between the current process and the new process, to evaluate the process capability level. The prerequisite for this method is the establishment of a comprehensive process capability database.

5. Decision Mechanism for Process Approval

Process approval, as the "last mile" of process development, requires a clear and transparent decision mechanism to support it.

Three-Level Approval Structure

Level One: Process-Level Approval. After each process completes debugging and initial validation, the process engineer and quality engineer jointly review and confirm that the process meets the predetermined capability requirements, then sign off on the process release form. Process-level approval is a prerequisite for subsequent line integration and debugging.

Level Two: Line-Level Approval. After all processes complete debugging and process-level approval, a full line trial production is conducted. The line-level approval review content includes: results of line integration and debugging, summary of process capabilities for each process, production rhythm verification, material flow verification, and the status of the quality issue list.

Level Three: Mass Production Approval. After line-level approval is completed, the project management committee or quality committee conducts the final mass production release review. The decision basis for mass production approval is the completeness and quality of the outputs from each stage of process development, with core check items including the completeness and consistency of the four major documents (flow diagram, PFMEA, control plan, SOP), the achievement of process capability targets, the quality results of the validation batches, and the acceptability of residual risks.

Control of Conditional Approval

In project practice, it is not common for all release conditions to be fully met before mass production—especially when project schedule pressure is high, "conditional approval" becomes a compromise solution. However, conditional approval is also the mechanism most prone to abuse, and without proper control, it can become "unconditional indulgence."

Effective control of conditional approval requires the following principles:

• Conditions Must Be Clear and Quantifiable: Not "continuous process improvement," but "improve the Cpk of X process from 1.2 to 1.33 or above within 30 days of mass production."
• Clear Responsibility and Completion Deadlines: Each condition must have a clearly designated responsible person and a deadline.
• Escalation Mechanism: If the conditions are not met by the deadline, they should automatically escalate to management for decision-making—whether to extend the deadline or pause mass production.
• Tracking Ledger System: All conditionally approved items should be included in a tracking ledger and regularly reviewed until closure.

6. Change Management and Process Re-Approval

Process approval is not a one-time event but a continuous activity throughout the product lifecycle. When the process changes, the changed parts need to be re-validated and re-approved.

Types of Changes Triggering Re-Approval

Typical changes requiring process re-approval include:

• Major changes in process parameters (beyond the original PFMEA boundary)
• Equipment replacement (especially with non-identical equipment)
• Changes in tooling/molds
• Changes in materials (including auxiliary materials)
• Transfer of production site
• Addition, reduction, or adjustment of process sequence

Tiered Change Control

Based on the impact of changes on product quality, changes can be classified into three levels:

• Level I Changes: Changes affecting product safety or regulatory compliance. A complete "redevelopment → validation → approval" process must be executed, and no simplification is allowed.
• Level II Changes: Changes affecting key characteristics or functional performance of the product. At a minimum, PFMEA updates, control plan updates, and process capability re-validation are required.
• Level III Changes: Changes with limited impact on product quality (such as optimization of work sequence within a process). A simplified process can be used, requiring only the signature and confirmation of the process department and the quality department.

7. Conclusion: A Quality Culture Perspective on Process Development and Approval

The completeness of the process development and approval system fundamentally reflects the maturity of an organization's quality culture. When a company is willing to invest sufficient time and resources in process development, validation, and approval before mass production, rather than "learning on the job" after mass production, it indicates that the company's quality culture has shifted from "post-event remediation" to "pre-event prevention."

Building process development and approval capabilities is not a one-time "project." It is a process that requires continuous investment, continuous optimization, and continuous evolution—just like quality management itself.

Process development and approval are not stumbling blocks before mass production but the cornerstones of quality assurance—when the process is stable, the product can be stable.

Knowledge code: 8.3.3

Version: v20260730

Author: Quality Think Tank Quality Think Tank is dedicated to providing systematic professional knowledge, methodologies, and practical tools for quality management practitioners, helping companies continuously improve their quality capabilities.