22.2 Configuration Management, Interface Control, and Verification & Validation

FE Industrial and Systems Study Guide Exam

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Exam Overview, CBT Strategy & Handbook Navigation

1.1 FE Industrial Exam Structure, CBT Logistics, and Pacing 1.2 Using the NCEES FE Reference Handbook and Approved Calculators

2 Chapter 2: Mathematics for Industrial Engineers

2.1 Analytic Geometry, Coordinate Systems, and Trigonometry 2.2 Calculus: Differential, Integral, and Series Approximations 2.3 Linear Algebra: Matrix Operations, Systems of Equations, and Vectors

3 Chapter 3: Engineering Sciences Core

3.1 Thermodynamics Fundamentals and Fluid Flow Principles 3.2 Statics, Dynamics, and Mechanics of Materials Core 3.3 Electrical Circuits, DC/AC Analysis, and Power in Industrial Systems

4 Chapter 4: Ethics and Professional Practice

4.1 NCEES Model Rules of Professional Conduct and Technical Society Ethics 4.2 Engineering Licensure, Public Welfare, and Professional Liability 4.3 Engineering Contracts, Intellectual Property, and Conflicts of Interest

5 Chapter 5: Engineering Economics

5.1 Time Value of Money, Discount Factors, and Equivalence 5.2 Evaluating Alternatives: Present Worth, Equivalent Annual Cost, and IRR 5.3 Incremental Rate of Return, Replacement Analysis, and Break-Even 5.4 Depreciation Methods, MACRS, Income Taxes, and Inflation

6 Chapter 6: Probability Foundations & Distributions

6.1 Basic Probability Concepts, Conditional Probability, and Bayes' Theorem 6.2 Discrete Probability Distributions 6.3 Continuous Probability Distributions

7 Chapter 7: Statistical Inference, Regression & Design of Experiments

7.1 Sampling Distributions, Central Limit Theorem, and Confidence Intervals 7.2 Hypothesis Testing: Means, Proportions, and Variances 7.3 Linear Regression, Correlation Analysis, and Design of Experiments (ANOVA)

8 Chapter 8: Data, Logic, Modeling & Linear Programming

8.1 Optimization Modeling: Decision Variables, Objectives, and Constraints 8.2 Linear Programming: Graphical Solutions and Simplex Fundamentals 8.3 Duality, Sensitivity Analysis, and Integer Linear Programming 8.4 Data, Logic Development, and Analytics

9 Chapter 9: Stochastic Models & Simulation

9.1 Queuing Theory: Little's Law, M/M/1, and Multi-Server Systems 9.2 Discrete-Time Markov Chains: Transition Matrices and Steady-State Probabilities 9.3 Discrete-Event Simulation Principles and Monte Carlo Modeling

10 Chapter 10: Engineering Management, Project Planning & Performance Measurement

10.1 Organizational Structure, Leadership, and Worker Motivation Theories 10.2 Project Management: WBS, Critical Path Method (CPM), PERT, and Crashing 10.3 Earned Value Management (EVM), Decision Trees, and Risk Preference 10.4 Performance Measurement: Productivity, KPIs, Wage Systems, and the Balanced Scorecard

11 Chapter 11: Manufacturing & Production Systems

11.1 Manufacturing Processes, Material Processing, and Tolerancing 11.2 Assembly Line Balancing, Takt Time, Cycle Time, and Throughput 11.3 Sustainable Manufacturing, Waste Minimization, and Life-Cycle Assessment

12 Chapter 12: Production Planning, Inventory Control & Sequencing

12.1 Demand Forecasting Methods and Forecast Error Tracking 12.2 Aggregate Planning, Master Production Scheduling (MPS), and MRP 12.3 Deterministic Inventory Models: EOQ, EPQ, and Safety Stock 12.4 Job Sequencing, Dispatching Rules, and Flow Shop Scheduling

13 Chapter 13: Lean Systems & Theory of Constraints

13.1 Lean Foundations: Value Stream Mapping, Seven Wastes, and 5S 13.2 Pull Systems, Kanban, Just-In-Time (JIT), and SMED Setup Reduction 13.3 Theory of Constraints: Bottleneck Identification and Drum-Buffer-Rope

14 Chapter 14: Facilities Planning & Material Handling

14.1 Facility Location Analysis: Qualitative Factor Rating and Centroid Method 14.2 Facility Layout Design and Flow Analysis 14.3 Material Handling Equipment, Warehousing, and AS/RS

15 Chapter 15: Supply Chain Design & Logistics

15.1 Supply Chain Network Architecture and Transportation Modes 15.2 Distribution Strategies, Cross-Docking, and Vehicle Routing 15.3 The Bullwhip Effect, Risk Pooling, and Supply Chain Coordination

16 Chapter 16: Human Factors & Cognitive Ergonomics

16.1 Cognitive Engineering, Human-Machine Interface, Displays, and Controls 16.2 Anthropometric Principles, Percentile Design, and Biomechanical Posture 16.3 Environmental Ergonomics: Industrial Noise, Lighting, and Heat Stress

17 Chapter 17: Physical Ergonomics & Workplace Safety

17.1 Physical Ergonomics: The NIOSH Manual Lifting Equation 17.2 Cumulative Trauma Disorders and Postural Assessment 17.3 Workplace Safety: OSHA Standards, Hazard Analysis, and Control Hierarchy

18 Chapter 18: Work Design & Measurement

18.1 Methods Engineering, Process Charting, and Principles of Motion Economy 18.2 Direct Stopwatch Time Study: Observed Time, Performance Rating, and Allowances 18.3 Predetermined Time Systems, Work Sampling, and Learning Curves

19 Chapter 19: Quality Management, Six Sigma & Analytical Tools

19.1 Quality Philosophies, Total Quality Management, and Cost of Quality 19.2 Six Sigma DMAIC Methodology and Quality Function Deployment 19.3 The Seven Basic Quality Tools, Root Cause Analysis, and Taguchi Loss Function

20 Chapter 20: Statistical Process Control

20.1 Statistical Process Control Principles, Variation, and Run Rules 20.2 Variable Control Charts: X-bar & R, X-bar & S, and Individual-Moving Range 20.3 Attribute Control Charts: Defectives (p, np) and Defects (c, u)

21 Chapter 21: Process Capability & Acceptance Sampling

21.1 Process Capability Indices and Defect Levels 21.2 Acceptance Sampling Concepts and Operating Characteristic Curves 21.3 Sampling Risks, AQL, LTPD, and Standard Sampling Plans

22 Chapter 22: Systems Engineering & Life-Cycle Management

22.1 The Systems Engineering V-Model, Stakeholder Requirements, and Functional Architecture 22.2 Configuration Management, Interface Control, and Verification & Validation 22.3 Life-Cycle Costing, Maintainability, and System Availability

23 Chapter 23: Reliability Engineering & Risk Analysis

23.1 Reliability Mathematics, Hazard Rates, and the Bathtub Curve 23.2 System Reliability Configurations: Series, Parallel, and k-out-of-n Systems 23.3 Failure Modes and Effects Analysis and Fault Tree Analysis

22.2 Configuration Management, Interface Control, and Verification & Validation

Key Takeaways Explain This Topic AI

Configuration Management (CM) maintains technical baseline integrity across four essential pillars: Configuration Identification, Configuration Change Management, Configuration Status Accounting (CSA), and Configuration Audits.

Formal engineering baselines govern lifecycle maturation: the Functional Baseline (FBL) at SRR establishes top-level system specs, the Allocated Baseline (ABL) at PDR freezes subsystem requirements, and the Product Baseline (PBL) at CDR freezes build-to drawings and code.

Class I Engineering Change Proposals (ECPs) alter form, fit, function, interfaces, or baseline specifications and mandate formal Configuration Control Board (CCB) authorization, whereas Class II ECPs address minor editorial corrections.

Verification proves whether the system conforms to technical specifications ('Did we build the system right?') via Inspection, Analysis, Demonstration, or Test; Validation proves whether the system satisfies operational needs in the field ('Did we build the right system?').

Technical Performance Measures (TPMs) track critical engineering parameters against planned tolerance profiles over time to detect margin erosion and technical risk early in development.

Last updated: September 2026

22.2 Configuration Management, Interface Control, and Verification & Validation

When complex engineering systems progress from conceptual design to manufacturing and field deployment, thousands of technical artifacts—CAD models, software source code, circuit schematics, wiring harnesses, and operating manuals—must remain strictly synchronized. A failure to control drawing baselines, manage interface boundaries, or verify physical hardware against design requirements inevitably results in catastrophic assembly mismatches, cost overruns, and catastrophic field failures. This section covers Configuration Management (CM), Interface Control Documents (ICDs), the four formal methods of Verification, operational Validation, and Technical Performance Measures (TPMs).

1. The Four Pillars of Configuration Management (CM)

Configuration Management (CM) is a systems engineering management discipline that establishes and maintains consistency of a product's performance, functional, and physical attributes with its requirements, design, and operational information throughout its lifecycle. CM is structured upon four mandatory operational pillars: The Four Pillars of Configuration Management

┌────────────────────────┬────────────────────────┬────────────────────────┬────────────────────────┐
│ Configuration │ Configuration Change │ Configuration Status │ Configuration │
│ Identification │ Management │ Accounting │ Audits │
├────────────────────────┼────────────────────────┼────────────────────────┼────────────────────────┤
│ • Configuration Items │ • Class I vs Class II │ • Traceability Records │ • Functional (FCA) │
│ • Functional Baseline │ • Engineering Change │ • Baseline Versioning │ • Physical (PCA) │
│ • Allocated Baseline │ Proposals (ECP) │ • Pending ECP Tracking │ • Compliance Reports │
│ • Product Baseline │ • CCB Governance │ • Implementation Logs │ • As-Built Verification│
└────────────────────────┴────────────────────────┴────────────────────────┴────────────────────────┘
Pillar 1: Configuration Identification

Configuration identification selects the specific system entities to be managed and establishes the technical baselines that govern development.

Configuration Items (CIs) : An aggregation of hardware, software, or firmware that satisfies an end-use function and is designated for separate configuration management. Examples include an automated guided vehicle drive motor controller, an industrial robot wrist assembly, or an embedded PLC safety program.

Technical Baselines : A baseline is a formally approved technical description of a product at a specific point in time, serving as the legal and engineering foundation for subsequent activities. Baselines can only be modified through formal change control procedures. The three standard lifecycle baselines are:

Functional Baseline (FBL) : Established at the System Requirements Review (SRR) or System Functional Review (SFR) . It consists of the approved System Specification, defining top-level functional performance, mission requirements, operational interfaces, and overall system constraints. Core question: What must the system do functionally?

Allocated Baseline (ABL) : Established at the Preliminary Design Review (PDR) . It consists of the development and subsystem specifications, allocating system-level functional and performance requirements down to individual CIs. It freezes subsystem interface requirements and internal design constraints. Core question: How are functions distributed across subsystems?

Product Baseline (PBL) : Established at the Critical Design Review (CDR) and finalized during the Physical Configuration Audit (PCA) . It consists of the detailed "build-to," "code-to," and "procure-to" technical documentation: complete engineering drawings with GD&T tolerances, circuit schematics, software source code listings, bills of materials (BOM), material specifications, and manufacturing process instructions. Core question: Exactly how is the physical system manufactured and assembled?

Pillar 2: Configuration Change Management

Once a baseline is formally approved, it is frozen. Uncontrolled, informal design modifications ("creeping scope" or "drawing board adjustments") are prohibited. All modifications are executed via formal Engineering Change Proposals (ECPs) .

Class I vs. Class II Engineering Change Proposals

On the FE exam, candidates must distinguish between the two legal classes of ECPs:

Class I ECP (Major Change) : A change that impacts:

The operational performance, reliability, maintainability, or safety of the system.

Form, fit, or function.

External or internal physical/functional interfaces specified in Interface Control Documents (ICDs).

Contractual cost, milestone delivery schedule, or customer-approved baselines (FBL, ABL, PBL).

Approval Authority : Requires formal technical evaluation and authorized sign-off by the Configuration Control Board (CCB) and contractual approval from the acquiring customer.

Class II ECP (Minor Change) : A change that does not impact form, fit, function, interfaces, baselines, cost, or schedule. Examples include fixing drawing drafting errors, correcting typographic part numbers, or adopting alternative non-critical manufacturing tooling.

Approval Authority : Can be approved internally by the lead design engineer or project engineering manager without full CCB review.

The Configuration Control Board (CCB)

The Configuration Control Board (CCB) is a formally chartered, cross-functional governing authority composed of representatives from Systems Engineering, Project Management, Quality Assurance, Manufacturing Operations, Procurement, Safety, and Product Support. The CCB is responsible for:

Evaluating the technical feasibility, cost impact, and schedule risk of proposed Class I ECPs.

Approving, rejecting, or deferring changes.

Authorizing baseline updates and issuing formal Engineering Change Orders (ECOs).

Pillar 3: Configuration Status Accounting (CSA)

Configuration Status Accounting is the administrative record-keeping system that tracks and reports the configuration of CIs throughout the lifecycle. CSA maintains records of:

The approved baseline configuration documentation and version history.

The current status of proposed Class I and Class II ECPs (submitted, under review, approved, rejected).

The precise implementation status of authorized ECOs across serial numbers (e.g., verifying which specific warehouse robots on the factory floor have had the new drive-shaft retrofit installed).

Pillar 4: Configuration Audits (FCA vs. PCA)

Configuration audits provide independent, formal verification that the physical product matches its technical baselines before entering volume production:

Audit Type Governing Baseline What Is Audited? Core Verification Question

Functional Configuration Audit (FCA) Functional Baseline (FBL) & Allocated Baseline (ABL) Formal test reports, analytical models, inspection records, and demonstration data "Did the test data objectively prove that the system achieved all functional and performance requirements specified in the baselines?"

Physical Configuration Audit (PCA) Product Baseline (PBL) The physical "as-built" hardware, assembly tooling, software code, and engineering drawings "Does the actual physical hardware and compiled code exactly match the released build-to engineering drawings and BOM?"

2. Interface Management & Interface Control Documents (ICDs)

In complex multidisciplinary engineering systems, over 60 % 60\% 60% of all technical redesigns and schedule delays stem from interface failures —situations where two individually compliant subsystems fail to operate cooperatively when joined together. An interface is the shared boundary between two functional or physical entities across which data, power, structural loads, fluids, or human interactions flow.

Interface Types

Mechanical / Physical : Spatial envelopes, bolt patterns, mounting brackets, center of gravity limits, structural load transfers, thermal expansion clearances, and vibration damping.

Electrical / Power : Voltage levels, alternating vs. direct current, transient suppression, power consumption limits, pin assignments, connector keying, and grounding topology.

Data / Software : Communication bus protocols (CAN bus, Ethernet/IP, RS-485, Modbus), baud rates, packet frame definitions, message schemas, API contracts, and memory-mapped address registers.

Thermal / Fluid : Fluid flow rates, inlet/outlet pressures, operating viscosity, heat rejection rates, and fluid chemical compatibility.

Interface Control Document (ICD)

An Interface Control Document (ICD) is a formal, contractually binding technical agreement between interacting design teams, internal departments, or external subcontractors. The ICD establishes:

The precise physical, electrical, and data characteristics of the boundary.

Exact geometric dimensions, pinouts, and signal tolerances.

The designated owner responsible for each side of the interface.

Change control rules (any modification to an ICD boundary automatically constitutes a Class I ECP requiring bilateral CCB concurrence).

3. Verification vs. Validation (V&V)

One of the most frequently tested concepts on the NCEES FE exam is the fundamental distinction between Verification and Validation : Verification ⟹ "Did we build the system right?" (Conformance to Specifications) Validation ⟹ "Did we build the right system?" (Satisfaction of Operational Needs) \begin{aligned}

\textbf{Verification} &\implies \text{"Did we build the system right?"} \quad \text{(Conformance to Specifications)} \\[6pt]

\textbf{Validation} &\implies \text{"Did we build the right system?"} \quad \text{(Satisfaction of Operational Needs)}

\end{aligned} Verification Validation ⟹ "Did we build the system right?" (Conformance to Specifications) ⟹ "Did we build the right system?" (Satisfaction of Operational Needs) Verification vs. Validation Comparison

Stakeholder Needs & Operational Concept (OpsCon) ══════════════════════╗
│ ║ VALIDATION
▼ (Requirements Engineering) ║ ("Did we build the
System Requirements Specifications ───────────────┐ ║ right system?")
│ │ VERIFICATION ║
▼ (Design & Implementation) │ ("Did we build the ║
Completed Physical System ────────────────────────┘ system right?") ◄╝
The Four Formal Verification Methods

Every technical requirement in a system specification must specify one of the four standardized verification methods:

Inspection : Visual, dimensional, or physical examination of an item without dynamic operation. Used to verify physical features, paint coatings, labeling, wire color-coding, weld quality, and dimensional compliance using hand tools (calipers, micrometers, height gauges).

Analysis : Technical evaluation using mathematical calculations, computer simulations, finite element analysis (FEA), computational fluid dynamics (CFD), or statistical modeling. Analysis is selected when physical testing is destructive, cost-prohibitive, technically impossible, or hazardous (e.g., verifying structural margin under a 100-year seismic load or orbital radiation shielding).

Demonstration : Qualitative observation of functional performance without requiring highly calibrated precision instrumentation. Used to verify basic functional modes (e.g., demonstrating that an emergency stop pushbutton immediately drops main power, that access panels open to 90 ∘ 90^\circ 9 0 ∘ , or that an automated diagnostic routine boots successfully).

Test : Quantitative measurement of performance parameters under controlled operating conditions using calibrated instrumentation, followed by formal statistical or numerical comparison against pass/fail criteria. Examples include measuring hydraulic cylinder pressure under full load, measuring motor acoustic noise levels with a decibel meter, or conducting 3-axis vibration profile sweeps.

Verification Method Primary Characteristics Equipment Required Relative Cost
Inspection Static visual/dimensional check; no operation Basic measurement tools (calipers, gauges) Very Low

Analysis Mathematical modeling, FEA, CFD, extrapolation Simulation software, engineering equations Low to Moderate

Demonstration Qualitative "pass/fail" functional operation Operational environment, no precision instrumentation Moderate

Test Quantitative measurement against numerical specs Calibrated instrumentation, data loggers, test fixtures High to Very High

System Validation

While verification confirms that the engineered hardware and software meet the technical drawings and specifications, Validation evaluates the complete system in its intended operational environment with representative end-users. Validation answers whether the system actually resolves the customer's operational problem. A system can successfully pass all engineering verification tests (built 100% to spec) yet fail validation if the original specifications were flawed, missing critical environmental factors, or ergonomically unsuitable for human operators.

4. Technical Performance Measures (TPMs)

A Technical Performance Measure (TPM) is a critical engineering parameter tracked continuously throughout development to predict whether the system will satisfy its ultimate performance requirements. TPM tracking provides early warning of technical risks before major design reviews.

Core TPM Elements

Planned Value Profile : The time-phased technical target over the development lifecycle, accounting for design maturation.

Tolerance Band : The allowable upper and lower boundary limits around the planned value profile.

Current Estimate : The latest assessed value derived from engineering calculations, updated simulation models, or subsystem prototype test data.

Design Margin : The difference between the Current Estimate and the maximum allowable specification ceiling (or minimum floor): Margin = Specification Limit − Current Estimate \text{Margin} = \text{Specification Limit} - \text{Current Estimate} Margin = Specification Limit − Current Estimate % Margin = ( Specification Limit − Current Estimate Specification Limit ) × 100 % \% \text{ Margin} = \left( \frac{\text{Specification Limit} - \text{Current Estimate}}{\text{Specification Limit}} \right) \times 100\% % Margin = ( Specification Limit Specification Limit − Current Estimate ) × 100%

Typical TPM parameters include total vehicle mass, peak electrical power draw, software processing latency, hydraulic line pressure loss, and Mean Time Between Failures (MTBF). If the Current Estimate breaches the tolerance band months prior to CDR, systems engineers initiate immediate trade studies (e.g., a mass-reduction program) when design modifications are still inexpensive.

5. Step-by-Step Worked Engineering Calculations
Worked Example 22.2.1: TPM Tracking and Variance Analysis for an Autonomous Storage Crane

Problem : An industrial systems engineering team is developing an automated high-bay stacker crane. The top-level technical specification mandates that the total mass of the mast carriage assembly must not exceed M max ⁡ = 1 , 200 kg M_{\max} = 1,200\text{ kg} M m a x = 1 , 200 kg to ensure structural integrity and motor drive stability. The planned value profile and current engineering estimates across four project milestones are recorded in the table below:

Milestone Review Project Month Planned Value ( M plan M_{\text{plan}} M plan , kg) Allowable Upper Tolerance ( + 5 % +5\% + 5% ) Current Estimate ( M est M_{\text{est}} M est , kg)

System Requirements Review (SRR) Month 2 1 , 000 1,000 1 , 000 1 , 050 1,050 1 , 050 1 , 010 1,010 1 , 010

Preliminary Design Review (PDR) Month 6 1 , 050 1,050 1 , 050 1 , 102.5 1,102.5 1 , 102.5 1 , 080 1,080 1 , 080

Critical Design Review (CDR) Month 12 1 , 100 1,100 1 , 100 1 , 155 1,155 1 , 155 1 , 175 1,175 1 , 175
System Integration Test Month 16 1 , 150 1,150 1 , 150 1 , 200 1,200 1 , 200 1 , 220 1,220 1 , 220

Calculate the design mass margin (kg and percentage) remaining at PDR and CDR.

Calculate the percentage variance of the Current Estimate relative to the Planned Value at CDR.

Determine whether a technical breach occurred at CDR and what formal configuration management action is triggered.

Evaluate the status at System Integration Test. Does the physical assembly comply with the specification limit?

Solution :

Step 1: Calculate Remaining Mass Margin at PDR and CDR

At PDR (Month 6) : Margin PDR = M max ⁡ − M est, PDR = 1 , 200 − 1 , 080 = 120 kg \text{Margin}_{\text{PDR}} = M_{\max} - M_{\text{est, PDR}} = 1,200 - 1,080 = 120\text{ kg} Margin PDR = M m a x − M est, PDR = 1 , 200 − 1 , 080 = 120 kg % Margin PDR = ( 120 1 , 200 ) × 100 % = 10.0 % \% \text{ Margin}_{\text{PDR}} = \left( \frac{120}{1,200} \right) \times 100\% = 10.0\% % Margin PDR = ( 1 , 200 120 ) × 100% = 10.0%

At CDR (Month 12) : Margin CDR = M max ⁡ − M est, CDR = 1 , 200 − 1 , 175 = 25 kg \text{Margin}_{\text{CDR}} = M_{\max} - M_{\text{est, CDR}} = 1,200 - 1,175 = 25\text{ kg} Margin CDR = M m a x − M est, CDR = 1 , 200 − 1 , 175 = 25 kg % Margin CDR = ( 25 1 , 200 ) × 100 % = 2.083 % \% \text{ Margin}_{\text{CDR}} = \left( \frac{25}{1,200} \right) \times 100\% = 2.083\% % Margin CDR = ( 1 , 200 25 ) × 100% = 2.083%

Step 2: Compute Percentage Variance at CDR % Variance CDR = ( M est, CDR − M plan, CDR M plan, CDR ) × 100 % = ( 1 , 175 − 1 , 100 1 , 100 ) × 100 % = ( 75 1 , 100 ) × 100 % = + 6.82 % \% \text{ Variance}_{\text{CDR}} = \left( \frac{M_{\text{est, CDR}} - M_{\text{plan, CDR}}}{M_{\text{plan, CDR}}} \right) \times 100\% = \left( \frac{1,175 - 1,100}{1,100} \right) \times 100\% = \left( \frac{75}{1,100} \right) \times 100\% = +6.82\% % Variance CDR = ( M plan, CDR M est, CDR − M plan, CDR ) × 100% = ( 1 , 100 1 , 175 − 1 , 100 ) × 100% = ( 1 , 100 75 ) × 100% = + 6.82%

Step 3: CM Evaluation at CDR

The allowable upper tolerance at CDR was 1 , 155 kg 1,155\text{ kg} 1 , 155 kg ( + 5 % +5\% + 5% over planned value).

The current estimate of 1 , 175 kg 1,175\text{ kg} 1 , 175 kg exceeds the upper tolerance band by 20 kg 20\text{ kg} 20 kg ( + 6.82 % > + 5.0 % +6.82\% > +5.0\% + 6.82% > + 5.0% ).

Engineering Conclusion : A TPM tolerance band breach has occurred. The lead systems engineer cannot approve the Product Baseline (PBL) freeze at CDR without corrective action. The team must immediately convene the Configuration Control Board (CCB) and initiate a Class I ECP trade study (such as replacing structural steel gussets with high-strength aluminum or hollow-section weldments) to recover required mass margin.

Step 4: System Integration Test Status

At Month 16, the measured physical carriage mass is 1 , 220 kg 1,220\text{ kg} 1 , 220 kg .

Compare to specification ceiling: 1 , 220 kg > 1 , 200 kg 1,220\text{ kg} > 1,200\text{ kg} 1 , 220 kg > 1 , 200 kg .

Engineering Conclusion : The carriage fails Verification because it violates the binding requirement ( M ≤ 1 , 200 kg M \le 1,200\text{ kg} M ≤ 1 , 200 kg ). The carriage cannot be shipped without either redesigning structural members to eliminate 20 kg 20\text{ kg} 20 kg or submitting a formal Class I ECP to the customer requesting a specification waiver or motor upgrade.

Worked Example 22.2.2: Verification Method Selection Matrix

Problem : For an automated semiconductor wafer transfer robot, determine the most appropriate and cost-effective formal verification method (Inspection, Analysis, Demonstration, or Test) for each of the four engineering requirements below:

Req-01 : "The wafer transfer end-effector shall have a hard-anodized PTFE coating thickness of 25 ± 3 μ m 25 \pm 3\text{ }\mu\text{m} 25 ± 3 μ m across all contact surfaces."

Req-02 : "The robotic arm primary shoulder casting shall maintain a structural factor of safety ≥ 3.0 \ge 3.0 ≥ 3.0 under a 9.0-magnitude earthquake ground acceleration profile."

Req-03 : "The robot controller shall illuminate a flashing amber beacon and display 'ESTOP ENGAGED' within 500 ms 500\text{ ms} 500 ms of emergency stop actuation."

Req-04 : "The robot end-effector positioning repeatability shall be ≤ ± 15 μ m \le \pm 15\text{ }\mu\text{m} ≤ ± 15 μ m across 10 , 000 10,000 10 , 000 continuous transfer cycles under full payload."

Solution :

Req-01 → \to → Inspection : Coating thickness is a static physical property verified using a calibrated non-destructive eddy-current coating thickness gauge without dynamic robot operation.

Req-02 → \to → Analysis : Physical testing would require placing a multi-million-dollar wafer fab on an immense seismic shake table to destruction. Instead, a finite element analysis (FEA) structural dynamic model subjected to seismic response spectrums mathematically verifies the safety factor.

Req-03 → \to → Demonstration : Qualitative observation confirms that pressing the E-stop button triggers the amber light and updates the text display. It requires no complex laboratory measurement fixtures.

Req-04 → \to → Test : Repeatability of ± 15 μ m \pm 15\text{ }\mu\text{m} ± 15 μ m requires high-precision quantitative measurement using laser interferometers or high-speed optical coordinate measuring machines (CMM) tracking positional data over 10 , 000 10,000 10 , 000 cycles with rigorous statistical analysis ( C p k C_{pk} C p k ). Simple inspection or qualitative demonstration is incapable of verifying this requirement.

6. NCEES Reference Handbook Tips & Realistic Exam Traps

Verification vs. Validation Trap : Remember the strict definitions. If a question describes testing against "engineering specifications," "drawings," "tolerance standards," or "numerical requirements," the process is Verification . If it describes testing in the "operational environment," "with end-users," "in real warehouse missions," or "satisfying operational needs," the process is Validation .

FCA vs. PCA Confusion :

FCA (Functional Configuration Audit) reviews data, reports, and calculations to prove performance complies with functional baselines.

PCA (Physical Configuration Audit) examines the actual physical hardware, wiring, and code to prove the as-built product matches released drawings.

Class I ECP Criteria : Any change affecting form, fit, function, interfaces, safety, cost, or delivery schedule is Class I . Never select an answer claiming that changing a circuit board connector pinout is a "Class II minor change"—interface modifications are always Class I!