New failure mode log, BOM rules validation and many more​

We launched BOM rules validation, and teams are generating FMEDAs faster than we can keep up with.

Creating and checking BOM rules is now faster than ever. You can import the BOM list of your choice and basically iterate over and over again until you get the required parts properly matched to respective references.

Failure mode injection and abstraction log​

The new failure mode log gives you full visibility into how failure modes evolve over time. Track changes, review updates, and understand who modified what—all in one place.

This makes collaboration easier and audits more transparent, ensuring that every decision in your FMEDA process is traceable and well-documented.

Learn more in the manual →

BOM rules validation​

BOM rules validation is designed to drastically speed up how you prepare your FMEDA. Import your BOM, define your rules, and iterate quickly until all components are correctly matched.

With real-time feedback and clear validation results, you can resolve mismatches faster and generate accurate FMEDAs without the usual back-and-forth.

See how it works →

Import effects and safety mechanisms from medini​

You can now import effects and safety mechanisms directly from medini, reducing the need for manual rework. This helps maintain consistency between your safety analysis and formalize section.

By reusing existing data, teams save time and ensure alignment across tools, making the overall safety workflow more efficient and reliable.

Read the import guide →

Other notable changes​

• Domain notes.
• Safety note for effect type in formalize menu.
• Support for using SPICE measurement (.MEAS[URE]) statements for LTspice output variables.
• Application setting for changing the default no effect name.
• Notes in formalization panel for domains and values.
• Improved variable name suggestions for SPICE circuit parameters.
• Logging enabled by default.
• Execution log no longer shows reusing model results as a warning during failure injection/abstraction.
• Improved parsing of failure DS when Excel formula is corrupted.
• Can set the no effect name in the reports.

Check our changelog for exhaustive list of changes.

BOM rules editor, safety mechanisms (ISO26262) manager and many more​

Streamline your BOM workflow—import or create a set of rules, format and fine-tune rules until everything clicks.

You can now take control of safety mechanisms—configure once, and let the system handle detection, coverage, and FMEDA population.

BOM rules edtior​

BOMs are messy by nature — different formats, naming conventions, and structures every time — but the BOM Rules Editor brings order to the chaos. Start by defining parsing rules that tell the system how to read your file, from separators and field names to handling multiple parts, ranges, and edge cases like comments or empty values. Once configured, the parser intelligently interprets your BOM, turning inconsistent raw data into a structured, reliable foundation for FMEDA. It’s flexible enough to adapt to virtually any BOM you throw at it, while still enforcing the consistency your analysis depends on.

From there, you can build powerful matching rules that map components to the right parameters and categories with precision. Field-based conditions, pattern matching, and numeric filters let you automate what used to be tedious manual work, while built-in validation ensures your rules actually apply to the imported BOM. You can even pull field names directly from a file to avoid errors and speed up setup, then reuse or duplicate rules to iterate quickly. The result is a faster, smarter workflow where BOMs go from raw input to fully mapped data in just a few iterations.

Explore the editor →

Safety mechanisms manager​

Safety mechanisms are at the core of ISO 26262 analysis, ensuring systems can detect, control, or prevent faults and safely respond when things go wrong. In Paitron, they’re defined similarly to effects but with a sharper focus—capturing diagnostic coverage for both single-point faults (SPF) and latent multi-point faults (MPF,L). Once specified, safety mechanisms are automatically detected and applied, populating the relevant FMEDA columns without manual effort. This means your analysis stays aligned with safety requirements while reducing repetitive work.

The system also keeps things smart and transparent behind the scenes. Only safety mechanisms with defined diagnostic coverage are considered, and when multiple are detected, the one with the highest coverage is selected by default. If something is missing or incomplete, you’ll get clear warnings down to the condition level, so nothing slips through unnoticed. The result is a more reliable, audit-ready FMEDA process with built-in guidance every step of the way.

Learn how to manage safety mechanisms →

Other notable changes​

• Option to change the selected FM of existing FMEA rows.
• Operational lifetime information for ISO 26262 reports (default value - 20000h).
• Support for FM mappings based on pin roles.
• Pin-to-pin FM mappings for the built-in failure data sources.
• Option to specify environment factor for MIL-HDBK-217F on a report level.
• Updated PMHF calculation to use the estimate from ISO 26262-5:2018, Annex F.
• Throwing an error when the quantitive behavior information cannot be mapped to a qualitative value.
• Requiring output variables domains to be complete.
• Improved parsing of PSpice .MODEL and .SUBCKT statements from the output files.
• Updated failure model mappings for some Birolini failure modes.

Check our changelog for exhaustive list of changes.