Quality assurance is the planned system of processes, standards and documentation that gives confidence a product or service will meet requirements. Quality control is the set of activities that actually inspects, tests and measures outputs to detect nonconformance. In practice, assurance designs the rules, such as work instructions, calibration schedules and training requirements, while control checks whether those rules were followed and whether the product passed. Assurance is preventive and systemic, focusing on how work is done, whereas control is detective, focusing on what was produced. A mature organization needs both, because inspection alone cannot create quality that the process did not build in from the start.
A test plan defines what will be tested, why, how, and against which acceptance criteria. It typically identifies the product or batch scope, the requirements or specifications under evaluation, the test methods and equipment, sample sizes and sampling rationale, environmental conditions, roles and responsibilities, and the procedure for recording and dispositioning results. Clear pass and fail limits are essential so that technicians are not left to interpret outcomes. For example, a plan for a molded housing might specify dimensional tolerances measured with calibrated gauges on a set number of parts per shift. Documenting the plan in advance reduces disputes, supports traceability and makes the results repeatable by another qualified team.
Throughput is the rate at which completed, acceptable units leave a process over a period of time. A bottleneck is the step with the lowest effective capacity relative to demand, and it governs the output of the entire line. Analysts measure cycle time at each station, track work-in-process inventory queued before each step, and compare utilization figures. The station with the longest queue and highest utilization is usually the constraint. For instance, if a functional tester takes four minutes per unit while upstream stations take two minutes, adding capacity elsewhere produces no gain. Improvement efforts should therefore focus on the constraint first, such as adding a parallel tester or reducing setup time, before optimizing other areas.
A control chart plots a measured characteristic over time against a center line representing the process average and upper and lower control limits typically set at three standard deviations. Points falling outside the limits, or systematic patterns such as runs of consecutive points on one side of the center line, signal special cause variation that needs investigation. Common cause variation, the inherent random noise of a stable process, falls within the limits. The distinction matters because reacting to common cause variation by adjusting the process often increases variation. Teams use control charts to decide whether to intervene, to verify that a corrective action worked, and to demonstrate process capability to customers in a documented, evidence-based way.
Failure mode and effects analysis is a structured method for identifying potential ways a design or process could fail, estimating the severity of each effect, the likelihood of occurrence and the ability to detect the failure before it reaches the customer. Teams multiply these ratings to prioritize risks and then define actions that reduce severity, occurrence or detection risk. The method is most valuable early, when changes are inexpensive. For example, a team reviewing a soldering process might find that a weak solder joint has a high severity and low detection rate, prompting a change to automated optical inspection. The analysis becomes a living document that is updated as the process matures and field data arrives.
Correcting only the visible symptom, such as reworking or scrapping a defective part, restores output in the short term but leaves the underlying condition free to recur. Root cause analysis seeks the systemic reason the defect was able to occur, which may involve equipment wear, an unclear work instruction, inadequate training, a supplier material change or a missing control. Common tools include the five whys, fishbone diagrams and fault tree analysis. Effective investigations verify the cause with data rather than assumption, then implement a corrective action and confirm its effectiveness over time. This disciplined approach converts isolated problems into lasting process improvement and reduces the total cost of quality.
Acceptance sampling inspects a statistically selected subset of a lot and uses the results to decide whether to accept or reject the entire lot against an agreed acceptable quality level. It is appropriate when testing is destructive, costly or time-consuming, when the volume makes full inspection impractical, or when the process has a proven record of stability. Sampling plans specify sample size, acceptance number and the risk each party accepts, including producer risk and consumer risk. Full inspection remains necessary for safety-critical characteristics where even a single defect is unacceptable. The choice should be documented and justified, since sampling introduces a known probability of accepting a bad lot.
A measurement system includes the gauge, the operator, the method and the environment, and any of these can introduce error that masquerades as product variation. Measurement system analysis, often performed with gauge repeatability and reproducibility studies, quantifies how much observed variation comes from the measuring process rather than the parts being measured. A common guideline treats a system as acceptable when measurement error is a small fraction of the total tolerance, although thresholds depend on the application and governing standards. For example, if a caliper gives inconsistent readings between two inspectors, good parts may be rejected and bad parts accepted. Validating measurements therefore protects both the producer and the customer from decisions based on noise.
Calibration compares an instrument against a reference of known, higher accuracy and documents any deviation, adjusting or qualifying the instrument as needed. Traceability means this chain of comparisons can be followed back to national or international standards, which gives measurement results a common, defensible basis. Calibration intervals are set based on the instrument's stability, usage intensity, the criticality of its measurements and historical drift data. Equipment found out of tolerance may require an assessment of previously tested products to determine whether any were affected. Without documented calibration and traceability, a test result cannot demonstrate that a product truly meets its specification, which is a core requirement in regulated and contractual testing.
Nondestructive testing evaluates a material or component using physical principles that do not impair its future serviceability. Common methods include ultrasonic testing, which sends high-frequency sound waves through a part and interprets reflections from internal flaws; radiographic testing, which uses penetrating radiation to reveal internal voids; magnetic particle inspection for surface and near-surface cracks in ferromagnetic materials; and dye penetrant testing for surface-breaking discontinuities. Each method has limits on the defect types and materials it can reliably detect, so selection depends on the expected failure modes and the part geometry. For example, a welded pressure vessel might undergo ultrasonic and radiographic inspection to confirm weld integrity. Qualified personnel and written procedures are essential to obtain meaningful results.
Reliability testing estimates how long a product will perform its intended function under specified conditions, which matters for warranty costs, safety and customer satisfaction. Because products may operate for years, engineers often use accelerated life testing, subjecting units to elevated stress such as temperature, humidity, vibration or electrical load to induce failures in a shorter time. Analysts then apply physics-based or statistical models to extrapolate results to normal use conditions. The extrapolation depends on assumptions about how the stress acts on failure mechanisms, so acceleration factors must be justified rather than assumed. Results are estimates with uncertainty, and teams should confirm predictions against field returns as data accumulates.
Environmental stress screening subjects manufactured units to controlled stresses such as thermal cycling, vibration or power cycling to precipitate latent defects, which are flaws that may not cause immediate failure in the factory but will appear early in service. Burn-in is a related practice that operates units under electrical and thermal load for a defined period to remove infant mortality failures. Screening is a production activity rather than a design verification, so its stress levels are chosen to be severe enough to expose defects without damaging good units. Over-stressing can consume product life, while under-stressing misses weak parts. Teams therefore balance screen effectiveness against cost and yield, using failure data to tune the profile.
Unit testing verifies the smallest testable pieces of code, such as a single function or module, in isolation. Integration testing checks that these components interact correctly, including interfaces, data exchanges and timing. System testing evaluates the complete integrated product against its requirements, often including performance, usability and fault-handling behavior. Each level catches a different class of error, and defects are generally cheaper to find and fix at lower levels. For example, a controller might pass its unit tests for signal processing, yet fail integration when the communication timing drifts under load. A layered strategy, supported by automated regression suites, gives teams confidence that changes do not silently break existing functionality.
Automation is most valuable for tests that run frequently, are stable, are tedious for people to perform, or require precise repetition, such as regression suites and performance benchmarks. Manual testing remains important for exploratory work, usability evaluation and situations where human judgment about appearance, behavior or unexpected results is required. Automation carries upfront development cost and ongoing maintenance, particularly when the product interface changes often, so teams should estimate the return over the expected life of the product. A balanced portfolio typically automates the repetitive core and reserves skilled manual effort for risk-based exploration. Good automation strategy also records what is covered, so that gaps are visible rather than assumed.
Regulated industries such as medical devices, aerospace, food and pharmaceuticals must demonstrate to authorities and auditors that products were designed, tested and released under controlled conditions. Complete documentation links requirements to test cases, records actual results, identifies who performed each activity, and shows how deviations were investigated and resolved. Traceability allows regulators or the organization itself to reconstruct the history of any unit or batch if a problem emerges. Governing requirements vary by sector and jurisdiction, and organizations must follow the specific guidance and quality system standards that apply to them, ideally with input from qualified regulatory and quality professionals. This educational overview cannot substitute for that professional judgment.
Test environments can expose personnel to electrical energy, high pressure, elevated temperatures, moving equipment, hazardous chemicals, ionizing radiation and high noise levels, depending on the test type. Management typically follows a hierarchy of controls: eliminating or substituting hazards where practical, applying engineering controls such as interlocks, guarding and ventilation, using administrative measures like written procedures, training and lockout tagout, and providing personal protective equipment as a last line of defense. Risk assessment should be performed before a new test method is introduced. Workers conducting hazardous tests need appropriate training and competence verification. Specific obligations depend on local occupational safety regulations, so organizations should consult current requirements and qualified safety professionals.
Preventive maintenance performs scheduled inspection, cleaning, lubrication, adjustment and component replacement before failures occur, based on time, usage or condition indicators. For test equipment, neglected maintenance can cause drift, false failures that waste time, or false passes that let defective products ship, so its effect reaches the quality record as well as the production schedule. Maintenance planning uses equipment history, manufacturer recommendations and failure analysis to set intervals. Condition-based approaches, such as monitoring vibration or temperature trends, can refine timing further. A test station that is maintained predictably is easier to schedule, validate and trust, which supports both throughput targets and defensible results.
Overall equipment effectiveness is a composite measure computed as availability multiplied by performance efficiency multiplied by quality rate. Availability captures time lost to stops and breakdowns, performance captures speed losses relative to the ideal cycle time, and quality captures units that fail or require rework. A value of one hundred percent would mean only good parts were produced at the ideal rate with no interruptions, which is rarely achieved. The metric helps teams see which loss category dominates. For example, a tester with excellent quality but poor availability may need better fault recovery or preventive maintenance rather than process changes. Its interpretation depends on consistent data collection and clear definitions of each loss.
19
Cost of quality
What is the cost of quality, and why do organizations separate prevention, appraisal and failure costs?
The cost of quality is the total expense associated with ensuring and falling short of quality requirements. It is commonly grouped into prevention costs, such as training, process design and supplier audits; appraisal costs, such as inspection, testing and calibration; and failure costs, which are split into internal failure costs like scrap and rework and external failure costs like warranty claims and recalls. Separating these categories reveals whether spending is shifted toward prevention. Organizations often find that modest investment in prevention reduces the larger internal and external failure costs. The analysis is only as accurate as the cost capture, so teams must agree on what is counted and how it is allocated across accounts.
A material specification defines the properties, tolerances, test methods and acceptance criteria that incoming materials must satisfy. A supplier quality program uses qualification, audits, certificates of conformance, incoming inspection and corrective action requests to ensure suppliers consistently meet these requirements. Clear specifications matter because ambiguous requirements leave room for suppliers and buyers to interpret acceptance differently, creating disputes and escapes. Risk-based approaches concentrate verification on critical characteristics and suppliers with weak histories. When a supplier changes a process or raw material without notice, the effect may appear weeks later as a test failure, which is why change notification clauses are a standard element of supplier agreements.