Tag Archive for: Functional safety

FirmwareApplication Notes

Verification, Validation and TDD in Critical Firmware

Engineering Insight · Software V&V

Verification, Validation and TDD for Critical Converter Firmware

Why the firmware of a power converter is a critical reliability component — and how Premium SA treats it as such

1981
Year Boehm formulated the V&V distinction
V-Model
EN 50128 methodological framework for railway firmware
MC/DC
Minimum coverage required at SSIL 4
143
MISRA C:2012 rules (16 mandatory)

Executive Summary

A modern power electronics converter is, today, as much software as hardware. The controller firmware executes regulation loops, protections, digital calibration, active thermal management, telemetry and, in an increasing number of cases, functional safety functions certified to railway SSIL or automotive ASIL. Any defect in that firmware is indistinguishable — from the end operator’s perspective — from a hardware defect: the equipment does not work, does not fulfil its mission, triggers contractual penalties. The difference is that firmware does not physically age, but it does degrade in terms of confidence if it is not subjected to a disciplined process of verification and validation.

This article reviews the fundamentals of software quality assurance applied to embedded power electronics firmware: Boehm’s critical distinction between verification and validation, the Test-Driven Development discipline, the V-Model of EN 50128, the MiL → SiL → PiL → HiL → SYSiL testing pyramid, black-box and white-box techniques, and the “terminological swamp” that persists in the industry. The thesis is direct: critical firmware is designed with the same discipline with which we design a power module — mission profile, derating, FMEA, V&V — because it shares the same customer and the same contractual commitments.

1. Firmware as a Critical Component — Why Discipline Matters

A typical Premium SA converter from fifteen years ago carried minimal firmware: an elementary state machine, a few PI loops implemented in fixed-point arithmetic, hardware protections reinforced with a couple of software checks. The complexity of the embedded code fitted in a few kilobytes and could be reviewed line by line by an expert in an afternoon. That era is over.

The modern converter — integrating digital calibration, active thermal management, predictive DC bus ripple control, CAN/Ethernet/Modbus communication with the operator’s supervisor, PHM telemetry with RUL estimation, OTA firmware update with cryptographic signature, and possibly active safety functions certified to railway SSIL — carries tens of thousands of lines of C code, organised in modular architectures with HAL, RTOS, priority tasks and communications libraries. The probability that such code is perfectly correct on its first writing is, simply, zero.

Firmware as a component with a manageable failure rate. From the RAMS reliability standpoint, firmware is a component like any other in the system. It has its own failure rate, dominated — unlike physical components — by systematic defects (programming or specification errors) rather than random defects. The good news is that those systematic defects can be attacked with methodology: a disciplined verification and validation process reduces them in a quantifiable way. The bad news is symmetric: without discipline, those defects remain latent in the code and emerge — always — at the most costly moment. A firmware failure detected in the fleet has exactly the same economic structure as a hardware failure: penalty, withdrawal, FRACAS, propagation of the correction to the installed population. For this reason, at Premium SA, firmware is treated with the same methodological seriousness as the power module: D2W → D2F → D4R → D4Co applied to software.

2. Verification and Validation — Boehm’s Distinction

The most clarifying distinction in software quality assurance was formulated by Barry Boehm in 1981 through two apparently similar but methodologically distinct questions:

Boehm’s two questions. Verification: “Are we building the product right?” Validation: “Are we building the right product?” The first question looks inward: does the code respect the technical specification? Does each development phase fulfil the conditions set at the start of that phase? The second looks outward: does the final system do what the customer actually needs in their operating environment? Both are necessary. Neither is sufficient on its own.

2.1 The practical differences

Dimension Verification Validation
Question Are we building the product right? Are we building the right product?
Orientation To the internal technical process To the customer and real use
Reference Technical specification User needs
Timing Continuous, phase by phase At the end of development or integration
Dominant techniques Static analysis, reviews, unit testing, MISRA, MC/DC System tests, acceptance tests, full HIL
Granularity “Small-scale” tests “Large-scale” tests
Who decides The technical team The customer / end user
Automatable Mostly yes Partially — the final word is human
Type of error detected Implementation errors vs. the spec Spec errors vs. the real world

2.2 Why both are necessary

Impeccable verification without validation produces technically correct code that satisfies a specification that was itself defective — the team meets its obligations and the customer receives a product that does not solve their problem. Vigorous validation without verification produces code that “works in demo” but hides structural defects that emerge under operating conditions not contemplated in the acceptance test. The two disciplines are complementary and attack different classes of error, and no serious software engineering strategy can do without either of them.

3. The Terminological Swamp — Error, Defect, Failure, Incident

Any serious discussion about software quality carries the historical vocabulary problem. Multiple key terms — verification, validation, test, error, defect, fault, failure — are overloaded with conflicting meanings in the literature. A team that uses these terms interchangeably commits, unwittingly, reasoning errors that translate into process errors. It is worth anchoring the vocabulary to the IEEE standard.

Term Precise definition Example in a power converter
Error Incorrect human action. Mistake in specification, design or coding An engineer assumes the current sensor is bipolar when it is unipolar
Defect / Fault / Bug Internal manifestation of the error. Incorrect state embedded in the code A branch of the OCP protection calculation that never executes because the condition is impossible
Failure Observable inability of the system to fulfil its function — the visible symptom The converter does not trigger OCP protection when current exceeds the threshold
Incident Anomalous event during execution that merits recording and analysis The operator reports an unexpected stop that does not match any known cause
Why the causal chain matters. A human commits an error → the error introduces a defect in the code → the defect may or may not manifest as a failure when executed. A defect can live in code for years without ever causing a failure, simply because the specific conditions that activate it have not yet arisen. This subtlety explains why exhaustive testing is impossible and why deliberate test case design matters. The strategy is not to test everything (impossible) but to test correctly: the conditions most likely to activate latent defects.

4. The V-Model — Verification at Every Level

The methodological framework that articulates verification throughout the software lifecycle is the V-Model. Its proposal is structural: to each level of specification corresponds a symmetric level of verification. The left branch descends from requirements to code; the right branch ascends from unit verification to final acceptance. The V-Model is the backbone of EN 50128 (railway), IEC 61508 (generic), ISO 26262 (automotive) and DO-178C (avionics).

4.1 The V correspondences

Specification level (left branch) Verification level (right branch) Question answered
System requirements (SyRS) Acceptance / system validation tests Does the system meet user needs?
Software requirements (SRS) System tests on firmware Does the firmware satisfy its functional specification?
Architecture design Integration tests between modules Do the modules collaborate as designed?
Module design Unit tests per module Does each module do what its contract says?
Source code Static analysis + inspection Is the code free of dangerous patterns?

4.2 SSIL — Software Safety Integrity Levels

EN 50128 defines five software integrity levels: Basic Integrity and SSIL 1 to SSIL 4. Each level imposes mandatory V&V techniques, scaled in rigour according to function criticality. Premium SA maps its applications to these levels according to the responsibility of each firmware block:

SSIL level Typical application in Premium SA converters Mandatory EN 50128 techniques
Basic Integrity Non-safety-related functions — telemetry, log, UI Code review, functional tests
SSIL 1-2 Cabin auxiliaries, standard OVP/OCP/OTP protections MISRA C static analysis, unit tests with I/O coverage
SSIL 3 Non-brake-critical traction converters, EV BMS MISRA + decision coverage + response time analysis
SSIL 4 Active safety functions (regenerative brake inhibition) MC/DC + formal models + diverse redundancy

5. Test-Driven Development — Tests as a Design Decision

Test-Driven Development (TDD) emerged in the early 2000s as one of the pillars of Extreme Programming and represents a radical inversion of the traditional workflow. In the classic order, the programmer writes functionality first and then — if there is time — adds tests to verify it. In TDD, the order is inverted: the test is written first, before the functionality exists.

5.1 The Red-Green-Refactor cycle

Phase Developer action Code state
Red Write a unit test for functionality that does not yet exist Test fails — confirms the test measures something real
Green Write the minimum code to make the test pass Test passes — the minimum behaviour is implemented
Refactor Restructure the code to eliminate duplication and improve design, without altering behaviour Tests still pass — behaviour is preserved

The cycle repeats in small increments — minutes, not hours. After a TDD session, the developer has produced both the production code and its test battery, and each line of the former is backed by at least one of the latter. The deepest methodological consequence is not having tests, but the inverted order: thinking the test before the implementation forces the developer to understand exactly what success or failure of the functionality means. That is, ultimately, an act of design.

5.2 TDD as a partial substitute for traditional design

TDD is more design than testing. Academic sources and industrial experience converge on a counterintuitive observation: TDD is not primarily a testing technique, it is a design technique. The effort of thinking the test before the code forces the developer to clarify the contract of each function: what inputs it accepts, what outputs it produces, what side effects it has, what error conditions it contemplates. Much of the work traditionally done in “analysis and design” is absorbed within the Red-Green-Refactor cycle. The documented benefits are consistent: better designed and cleaner code, greater scalability, lower defect rate, drastic reduction of regression time thanks to automated tests. The price is a significant learning curve: TDD requires higher-order thinking capacity to apply under pressure, and pedagogical studies suggest its mastery is only internalised with an 80 % practice / 20 % theory balance.

5.3 TDD, BDD and ATDD — the evolution towards behaviour

Pure TDD is effective but has a limit: it is purely technical. A team using only TDD can produce code that passes all unit tests and yet turns out to be inconsistent with the real needs of stakeholders. Two variants have emerged to close this gap. BDD (Behavior-Driven Development) extends TDD by focusing on the expected behaviour of the system, expressed in a ubiquitous language (Given-When-Then) that both developers and customers can understand — the specification is not translated into tests, the specification is the test. ATDD (Acceptance Test-Driven Development) combines requirement specification with automated acceptance tests written before the code. The three practices are complementary: TDD ensures each function is well designed technically; ATDD ensures the complete system fulfils its business purpose; BDD provides the linguistic bridge between the two.

6. Testing Fundamentals — What We Test and How

As Edsger Dijkstra famously noted, testing can be very effective at demonstrating the presence of errors, but is hopelessly inadequate for demonstrating their absence. This limitation is structural: the input domain of any non-trivial program is so large that exhaustively testing all combinations is, in practice, impossible. The discipline of testing therefore consists in selecting a finite, representative subset of the domain that effectively exercises the critical characteristics of the system.

6.1 The test case and the oracle

The basic unit of testing is the test case: a defined set of conditions, input data and an expected result under which the software is executed to determine in a measurable way whether it meets a requirement. Each test case presupposes, implicitly or explicitly, an oracle: the arbiter that decides whether the result obtained is correct. In simple systems, the oracle is the specification itself. In complex systems where no closed specification exists, the oracle is a human expert — the tester who decides whether the observed behaviour matches the expected behaviour.

6.2 Black-box, white-box, and the critical distinction

Aspect Black-box (functional testing) White-box (structural testing)
Knowledge of code None — only the specification is known Total — includes internal implementation
Case design From expected inputs/outputs From control flow paths
Coverage metrics Requirements / equivalence class coverage Statement, branch, MC/DC, path coverage
Detects Discrepancies vs. functional specification Structural defects, dead code, untested branches
Example in Premium SA firmware Converter regulates output voltage with < 2 % error under standard load profiles Each branch of the ADC interrupt handler executes at least once
Limitation Does not detect defects in unspecified code Does not detect missing requirements
The mindset shift that costs most. The foundational principle of modern testing — and the one hardest for a young team to internalise — is that the test is not a demonstration that the program works, but a deliberately destructive process designed to find its errors. A truly successful test cycle is one that manages to make the system fail and brings latent defects to light. A cycle where everything passes at the first attempt is not good: it is suspicious. This inversion of attitude changes even who does the testing. In critical projects, tests are designed — whenever possible — by someone different from the code author, because the author’s confirmation bias is one of the greatest enemies of good testing. At Premium SA, SSIL ≥ 2 tests are reviewed by a Validator independent from the Designer.

7. The MiL → SiL → PiL → HiL → SYSiL Pyramid

For embedded firmware — where code runs on a microcontroller coupled to a real physical system — testing discipline adds a layer of complexity that does not exist in classical application software. Tests cannot be limited to digital inputs and outputs; they must close the loop with the physical behaviour of the converter. The X-in-the-Loop methodology structures this challenge in five progressive levels:

Level What is tested Test platform
MiL — Model-in-the-Loop System model (Simulink, Stateflow) Pure simulation on PC; no C code yet
SiL — Software-in-the-Loop C code compiled for PC Execution on host; I/O are simulated
PiL — Processor-in-the-Loop Binary code in an emulator of the target processor Verifies object code correctness without physical hardware
HiL — Hardware-in-the-Loop Binary code on the real microcontroller Firmware runs on target HW; plant simulated in real time
SYSiL — System-in-the-Loop Complete physical embedded system Final validation on bench with real hardware and real plant

Each level resolves a class of defects before adding an additional layer of complexity. MiL captures modelling and control algorithm errors. SiL captures model-to-code translation errors. PiL captures target-compiler-specific errors, aggressive optimisations and finite arithmetic problems. HiL captures firmware-hardware integration defects: timing, interrupts, races, peripherals. SYSiL is the final validation with the real plant.

Why HIL is the most powerful tool in embedded firmware. HIL closes the firmware verification loop with operational power that is difficult to overstate. The real microcontroller executes the compiled and linked firmware exactly as it will enter production. Input signals (voltage, current, temperature sensors) are synthesised in real time from a simulator that emulates the behaviour of the DC bus, transformer, motor or load. The firmware does not know the signals are synthetic: for it, the system is real. This allows executing thousands of scenarios — including sensor failures, mains transients, short-circuits, overvoltages — without physical risk to the equipment or the test bench. A well-designed HIL programme discovers hardware/software integration defects that no unit test could capture: ADC sample losses in high-frequency interrupts, races between RTOS tasks, protection conditions that trigger incorrectly by a few microseconds. At Premium SA, no critical firmware reaches SYSiL without first passing an exhaustive HIL programme.

8. Premium SA’s D4Co-SW Process

Premium SA applies to firmware the same methodological framework as to hardware: the sequential gates D2W → D2F → D4R → D4Co, adapted to the specific techniques and artefacts of software.

Gate Meaning for firmware Exit criteria
D2W — Design to Work Firmware executes nominal functions SRS signed, modular architecture defined, MiL/SiL prototype running
D2F — Design to Function Firmware meets full functional specification Unit tests ≥ 90 % branch coverage, HIL integration passed
D4R — Design for Reliability Firmware maintains behaviour under adverse conditions Fault injection passed, timing analysis, RTOS stress testing
D4Co — Design for Compliance Firmware meets regulations and is maintainable for 30 years EN 50128 SSIL dossier, MISRA C clean, FRACAS active

8.1 Non-negotiable techniques — MISRA, MC/DC, HIL

  • MISRA C:2012 — static analysis with Polyspace, Coverity or PC-lint on all C code. The 16 mandatory rules and 111 required rules are exit conditions of the D2F gate.
  • MC/DC for SSIL ≥ 3 — every Boolean decision is tested with n+1 cases where each individual condition changes the result while the others remain fixed; for SSIL 4 it is complemented with formal analysis.
  • HIL as exit criterion — no firmware with responsibility over active safety closes the D4Co gate without a complete HIL programme covering the mission profile space.
  • Fault injection for SSIL ≥ 2 — sensor failures, analogue signal noise, communication loss and memory corruption are simulated. The system must always enter a safe state: PWM off, output high impedance, alarm active.

8.2 FRACAS applied to software

The FRACAS methodology — Failure Reporting, Analysis and Corrective Action System — that Premium SA applies to hardware extends to firmware. Any defect detected in the fleet is analysed at the appropriate level (function, module, shared library), the root cause is documented, and the correction is propagated: to all platforms sharing the code, via cryptographically signed OTA update, and to the development process, via a new review rule or new test case that prevents reintroduction of the defect. Fleet firmware improves over time, just as hardware improves through field returns.

9. Synthesis — Firmware as an Engineering Product

Critical firmware in a Premium SA converter is designed with the same discipline as a power module. The pillars are six and are chained:

Pillar Question answered Premium SA practice
Precise vocabulary Are we talking about the same problem? IEEE glossary — error / defect / failure / incident differentiated
V&V per Boehm Are we building the product right and are we building the right product? Continuous phase-by-phase verification + final validation with customer
V-Model + EN 50128 Is each level verified symmetrically? Mapping SRS ↔ SyRS, module ↔ unit test, architecture ↔ integration
TDD / BDD / ATDD Does the test precede the code? TDD on critical modules; ATDD for system requirements
Black-box + white-box Is the spec met and is all code exercised? Branch coverage for SSIL 1-2, MC/DC for SSIL 3-4
MiL → SiL → PiL → HiL → SYSiL Does the firmware work on real hardware with a real plant? Exhaustive HIL before SYSiL; nothing reaches the fleet without passing HIL
The technical closing. Modern firmware is as much a component as the power module. It fails by different mechanisms — systematic defects rather than physical degradation — but produces the same symptom from the operator’s perspective: the equipment does not fulfil its mission. Treating software with the same methodological discipline as hardware is not optional for the railway or critical infrastructure engineer: it is the condition of compliance with the 30-year RAMS commitment. At Premium SA, the D4Co-SW methodology articulates this discipline in gates with quantitative criteria. The result is firmware that enters the fleet with systematic defect rates several orders of magnitude lower than a “test and fix” process, and that improves over time thanks to a FRACAS that closes the loop between real operation and development. Software engineering for critical systems does not consist of avoiding all errors — that is impossible. It consists of building a process that detects them early, documents them with precision, and propagates corrections across the entire system before the next defects reach the customer.

About Premium PSU — With over 40 years of experience, Premium SA designs and manufactures custom power converters in Barcelona for railway, energy, industrial, data center and defence applications. Firmware development is integrated with hardware design from the conceptual phase of each project, following EN 50128, IEC 61508 and ISO 26262 practices.

Developing a converter with safety-related firmware? Talk to our engineering team.

protosApplication Notes

The First Prototype Admits No Second Chance

Engineering Insight · Simulation & Test

The First Prototype Admits No Second Chance

Why we simulate before soldering: the integrated simulation, quantitative reliability and accelerated test chain behind custom power electronics delivered on time.

Premium SA
Born in Barcelona, Powering the World

In power electronics for critical sectors — railway, defence, energy, digital infrastructure — the custom project does not allow the iterative cycle of the catalogue product. Production runs are short. Deadlines are contractually binding. The first prototype delivered to the customer is validated against the entire contract, not against a simplified preliminary version.

The consequence is structural: success at the first prototype is not a desirable goal, it is the condition that makes the business model work. When a railway customer needs a converter operating at −40 °C, or an AI application requires dissipating more than 700 W/cm² locally, the design cannot be closed “by eye”. Whether a project delivers at the first prototype or iterates three times is decided before the first PCB is manufactured.

The constraint that defines the sector

Typical production runs in custom railway or defence projects sit between 50 and 500 units. The product learning curve runs out before the cost of a partial redesign is covered, so the catalogue business model — amortising iteration over thousands of subsequent units — does not apply. Every deviation detected when validating the first prototype has three possible outcomes, all costly: redesign with replanning, acceptance of contractual penalties, or batch rejection with replacement.

The metric Premium SA uses internally to evaluate design-flow maturity is the first-pass approval rate of DVT (Design Verification Testing). When stages are shortened due to schedule pressure, the indicator drops rapidly and drags timelines and margins with it.

Four fault vectors, four models

Pre-hardware verification is structured in four layers covering the dominant fault vectors in power electronics.

Electrical modelling: SPICE, PLECS and Simulink

SPICE for detailed switching analysis, and PLECS or Simulink for full-system simulation, allow verification — before manufacturing the first PCB — that the closed loop is stable, that waveforms do not exceed semiconductor margins, and that losses are consistent with the available dissipation. For SiC or GaN topologies, accurately capturing packaging parasitic inductance is decisive: a use case of the European ALL2GaN research project has documented how TOLL versus PG-DSO-20 packaging conditions snubber sizing in 3 kW/48 V totem-pole rectifiers achieving 97.5% efficiency and 40 W/in³ density.

Thermal CFD simulation

From chip to system. Real density does not come from table coefficients. For local heat fluxes above 700 W/cm² in AI applications and current-generation OCP servers, integrated liquid microchannels with dielectric coolant, in fraction-of-a-millimetre channel geometries, are already production-ready technology.

EMC pre-compliance simulation

The chamber costs thousands of euros and calendar days; discovering a radiated-emissions failure with the product already wired is one of the most damaging scenarios in a custom project. Modern solvers allow prediction of compliance with CISPR 32, EN 50121-3-2 (railway) or MIL-STD-461 (defence) before manufacturing. The Premium SA criterion: a design margin of at least 6 dB with respect to the applicable limits.

MATLAB / Simulink for digital control

Verification of control-loop stability and automatic C code generation. For SIL2/SIL3 under EN 50128 or ASIL-B/C under ISO 26262, traceability between safety requirement, model and generated code is a normative requirement.

Beyond simulation: reliability by design and physical testing

Reliability is not only verified on the bench; it is designed. Quantitative reliability analysis — the D4R block in Premium SA’s D2x methodology — makes it possible to commit to contractual MTBF figures backed by model and evidence. Tools: Telcordia SR-332, MIL-HDBK-217F, Siemens SN29500 and FIDES, depending on the customer and sector; FMEA with quantitative RPN thresholds; FTA with PFH calculation for SIL3. We explain this approach in more depth in our white paper on reliability in critical power electronics.

Physical testing closes the loop: DVT on three units (all must pass without rework), HALT to identify operational and destructive margins, and HASS as a production filter for each manufactured unit. The HALT+HASS combination does not replace DVT; it complements it — DVT verifies the design, HALT identifies the margins and HASS ensures that each unit stays within them.

The first prototype as the threshold of the business model

The chain described — four layers of simulation, three quantitative reliability tools, two levels of accelerated testing, all structured by the D2x methodology with V-Model and quantitative stage-gates (D2W, D2F, D2C, D4R, D4Co) — is Premium SA’s operational answer to a structural constraint: the first prototype must work. The investment has a measurable return: every hour of correct modelling is an hour not spent — multiplied — on physical bring-up, production redesign or warranty.

For the customer engineer evaluating suppliers, the relevant question is not whether the supplier knows how to design; it is whether the supplier knows how to verify. In custom power electronics for critical sectors, this is not an efficiency improvement: it is the condition that sustains the project.

Normative references

Standard Scope
Telcordia SR-332 · MIL-HDBK-217F · SN29500 · FIDES 2022 MTBF / reliability prediction methods
IEC 61508 · EN 50128 Functional safety; PFH <10⁻⁷/h for SIL3
ISO 26262 Automotive functional safety (ASIL)
CISPR 32 · EN 50121-3-2 · MIL-STD-461 EMC: multimedia equipment, railway rolling stock, defence

Talk to our engineering team

Planning a custom converter for railway, defence, energy or digital infrastructure? Talk to our engineers about how the simulation and test chain is applied to your project from the first design gate.

Contact Premium SA

About Premium SA

Premium SA (Premium PSU) is a Barcelona-based designer and manufacturer of custom power supplies and power converters for railway, energy, industrial, data centre and defence applications, with over 40 years of experience since its foundation in 1981. Born in Barcelona, Powering the World.

© 2026 Premium SA · Barcelona, Spain · Born in Barcelona, Powering the World
simulatingApplication Notes, Whitepapers

Simulation and Test Tools That Ensure Success from the First Delivery

Engineering Insight · Technical Article

Simulation and Test Tools That Ensure Success from the First Delivery

How Premium SA builds custom power supplies and conversion systems that work at the first prototype

Premium SA
Born in Barcelona, Powering the World
4
Simulation layers
≥6 dB
EMC design margin
3 units
DVT, zero rework
RPN > 100
FMEA verification trigger

Executive summary

The custom power electronics project for critical sectors — railway, defence, energy, infrastructure — does not allow the iterative cycle of the catalogue product. Production runs are short, deadlines are contractually binding, and the first prototype delivered to the customer must operate within specification. Massive hardware iteration is not an economically or temporally viable option.

Premium SA has developed an integrated simulation and test chain that systematically reduces the risk of the first prototype. The philosophy is direct: each hour of well-formulated simulation saves between five and ten hours of physical bring-up, and every fault detected in the modelling phase prevents costs that multiply exponentially when they appear in production or in the field.

The D2x methodology: five phases, one chain. The chain is built upon Premium SA’s proprietary D2x methodology — D2W (Design to Win), D2F (Design to Fabrication), D2C (Design to Cost), D4R (Design for Reliability) and D4Co (Design for Compliance / Component) — with quantitative stage-gates between phases and a V-Model that links each requirement with its verification evidence.

1. The custom project challenge: no second chance

Custom equipment is born from a tender specification: 15 kV DC in a railway substation, passive cooling in a deployable defence converter at −40 °C, a form factor for a traction cabin that does not allow a single additional millimetre. Each of these requirements eliminates entire families of catalogue solutions and forces design from the topology level upwards.

The operational consequence is severe: the first prototype delivered to the customer — typically between week four and week six of the project — is validated against the entire contract, not against a simplified version. Any deviation appearing in that validation has three possible outcomes, all costly: partial redesign with timeline replanning, acceptance of contractual penalties, or batch rejection with replacement.

Production runs are short — 50 to 500 units is a typical range in railway and defence — and the product learning curve runs out before it covers the cost of iteration. Success at the first prototype is not a desirable goal; it is the minimum threshold of economic viability.

The key metric: first-pass DVT approval rate. In projects where stages are shortened due to schedule pressure, this indicator drops rapidly and drags timelines and margins with it. Applying the simulation chain in full is what protects it.

2. The pre-prototype simulation chain

Pre-hardware verification is structured in four layers covering the four dominant fault vectors in power electronics: electrical behaviour in transients, thermal dissipation, electromagnetic compatibility and digital control. The four layers run in parallel and intersect at quantitative validation points.

2.1 Electrical modelling: SPICE / PLECS / Simulink

The first layer is the power circuit model. Standard tools — SPICE for detailed switching analysis, PLECS or Simulink for averaged models and full-system simulation — allow verification, before manufacturing the first PCB, that the closed control loop is stable across the full operating range, that waveforms at critical nodes do not exceed semiconductor voltage margins, and that calculated losses are consistent with the available thermal dissipation.

For topologies using wide-bandgap semiconductors (SiC, GaN), accurate modelling of packaging parasitic effects is decisive. A use case of the European ALL2GaN research project has documented how the parasitic inductance of the power loop conditions snubber sizing in 3 kW/48 V totem-pole rectifiers achieving 97.5% efficiency and 40 W/in³ density: without an electrical model that captures the inductance of the TOLL package versus PG-DSO-20, the sizing falls outside the optimum.

2.2 Thermal CFD simulation: from chip to system

The second layer covers the thermal domain. CFD simulation enables characterisation at three levels of detail: chip-level dissipation and junction-to-case of the semiconductor; air or liquid circulation in the complete product; and heat transfer with the environment — cabin, cabinet, outdoor. We cover this domain in more detail in our article on thermal design in power electronics.

For demanding power densities — current OCP servers for AI workloads must dissipate hundreds of kilowatts per rack, with the most demanding variants approaching local heat fluxes above 700 W/cm² in active areas — integrated liquid microchannel solutions with dielectric coolant, in fraction-of-a-millimetre channel geometries, are already production-ready technology.

Cross-validation between the electrical model (which delivers the loss map per component) and the thermal model (which delivers the temperature map) closes the first cycle: an operating point with plausible losses but unacceptable temperature forces a topology revision, not an oversizing of the dissipation.

2.3 EMC pre-compliance simulation

The third layer is electromagnetic compatibility. A pre-compliance session in a semi-anechoic chamber typically costs several thousand euros and consumes calendar days; discovering a radiated-emissions failure at that stage, with the product already wired, is one of the most damaging scenarios for a custom project.

Modern EMC simulation tools — Method of Moments (MoM) solvers for radiated emissions, cable-bundle models for conducted emissions, PCB-specific simulators for ground-plane resonances — allow prediction of product behaviour against the applicable standards (CISPR 32, EN 50121-3-2 for railway, MIL-STD-461 for defence) before manufacturing. The Premium SA criterion sets a minimum design margin of 6 dB with respect to the applicable limits; any spectrum point that falls inside that margin in simulation triggers a design iteration before manufacturing.

2.4 MATLAB / Simulink: digital control validation

The fourth simulated layer covers the digital control loop. MATLAB and Simulink allow verification of the stability of voltage, current and temperature loops across the full load range, identification of operating points with insufficient phase margin, and sizing of compensators before implementing them in firmware. Automatic C code generation from the Simulink model reduces the risk of discrepancy between what is simulated and what is deployed.

This layer becomes particularly relevant when control must be certified at functional safety level — SIL2 or SIL3 according to EN 50128 for railway, ASIL-B or ASIL-C according to ISO 26262 for automotive. Traceability between the safety requirement, the Simulink model, the generated code and the associated test is both a normative requirement and a quality practice.

3. Quantitative reliability analysis: D4R

Reliability is not only verified on the bench; it is designed. Quantitative reliability analysis — embodied at Premium SA in the D4R methodological block — makes it possible to commit to MTBF figures backed by model and evidence. Our white paper on reliability in critical power electronics develops this approach further.

3.1 MTBF calculation

MTBF calculation at Premium SA follows the standards accepted by each sector: Telcordia SR-332 (formerly Bellcore) and MIL-HDBK-217F for the Anglo-Saxon and defence markets; Siemens SN29500 for European industrial customers; IEC 61709 when required by the customer; FIDES for sectors with particular environmental severity requirements.

For topologies using wide-bandgap semiconductors, derating factors are particularly relevant. SiC allows junction operation at 200 °C, and GaN between 175 °C and 200 °C; however, standard practice in custom projects is to work with a derating of 30 to 50% on datasheet limits. The difference between operating a SiC MOSFET at Tj = 150 °C versus Tj = 175 °C, all else being equal, roughly doubles the failure rate.

3.2 FMEA: systematic risk ranking

FMEA is applied to both product design (Design FMEA) and the manufacturing process (Process FMEA). For each identified failure mode, three dimensions are assessed — severity, probable occurrence and detectability — giving a Risk Priority Number (RPN) as the product of the three. Premium SA practice sets two thresholds: no failure mode with severity 9 or 10 (out of 10) can leave the FMEA without documented corrective action, and any mode with an RPN above 100 enters the verification plan with a specific test.

3.3 FTA: top-down tree from the effect

Fault Tree Analysis works in the opposite direction to FMEA: it starts from a feared event — loss of power output, dangerous voltage emission to the load — and descends to identify the combinations of elementary failures that can produce it. The quantitative analysis, fed with component failure rates, allows calculation of the probability of the feared event and verification that it meets contractual or normative objectives — a PFH below 10−7 for SIL3, for example. FMEA and FTA are complementary: FMEA is exhaustive bottom-up; FTA is analytical top-down.

4. Physical testing: DVT, HALT and HASS

Simulation reduces uncertainty but does not eliminate it. The physical test plan closes the flow by verifying model predictions against reality and characterising the product against failure modes the model does not capture.

4.1 DVT: Design Verification Testing

DVT is the complete verification battery for the contractual product requirements: nominal and transient electrical behaviour, output regulation across the full load range, thermal behaviour under nominal and derating conditions, EMC margins with respect to the applicable standard, mechanical tests — vibration, shock, thermal cycling — and behaviour under simulated environmental faults. Standard practice runs DVT on three units; all three must pass all tests without rework.

4.2 HALT and HASS: accelerated filters

HALT (Highly Accelerated Life Testing) takes the product beyond operational conditions — temperature ramps between −80 °C and +120 °C with simultaneous six-axis vibration — to identify operational and destructive margins. The purpose is to dramatically accelerate the appearance of latent failures so they can be corrected before series production.

HASS (Highly Accelerated Stress Screening) applies the knowledge gained in HALT as a production filter: each manufactured unit is subjected to an accelerated profile (typically 50 to 80% of the operational margin identified in HALT) to discard units with latent defects before shipping. The HALT+HASS combination does not replace DVT; it complements it.

5. The D2x methodology as structural framework

The previous layers only add value if applied at the right time and with the right criterion. The D2x methodology structures this flow: each of the five phases has an assigned set of simulation and test activities, with quantitative stage-gates between phases that are crossed only when the criteria are met.

“The stage-gate turns the methodology into discipline, not intention. A phase does not close because the calendar has passed; it closes because the metric has been met.”

The V-Model that structures the methodology links each requirement in the descending branch with its corresponding verification phase in the ascending branch. For safety-critical software, the V-Model is a normative requirement: EN 50128 prescribes it for railway software classified SIL1 to SIL4; ISO 26262 for automotive ASIL-A to ASIL-D; and IEC 61508 is the umbrella standard for industrial functional safety.

6. Conclusion

“In custom projects, success at the first prototype is not a goal; it is the minimum threshold of viability. Premium SA has built the simulation and test chain that turns that threshold into reproducible practice.”

The chain described — four layers of simulation, three quantitative reliability tools, two levels of accelerated testing, all structured by the D2x methodology — is Premium SA’s operational answer to a structural constraint: the first prototype must work.

For the customer engineer evaluating providers of custom power electronics, the relevant question is not whether the supplier knows how to design; it is whether the supplier knows how to verify.

References

Standard / document Scope
Telcordia SR-332 (Issue 4) Reliability prediction — electronic equipment
MIL-HDBK-217F Notice 2 Reliability prediction — defence
Siemens SN29500 Failure rates — European industrial
FIDES Guide 2022 Reliability methodology — complex environments
IEC 61508 Functional safety — industrial
EN 50128:2011 Railway software — SIL1 to SIL4
ISO 26262 Automotive functional safety — ASIL-A to ASIL-D
CISPR 32 EMC — multimedia equipment
EN 50121-3-2 EMC — railway rolling stock
MIL-STD-461 EMC — defence equipment

Talk to our engineering team

Facing a demanding custom specification? Our engineering team can show you how the simulation, reliability and test chain is applied to your converter from the first design gate.

Contact Premium SA

About Premium SA

Premium SA (Premium PSU) is a Barcelona-based designer and manufacturer of custom power supplies and power converters for railway, energy, industrial, data centre and defence applications, with over 40 years of experience since its foundation in 1981. Born in Barcelona, Powering the World.

© 2026 Premium SA · Barcelona, Spain · Born in Barcelona, Powering the World