2024 | 09 – Updates in reliability analysis framework

Anzen‘s mission is to streamline systems safety and reliability analysis with the use of digital technologies. The end goal is to provide a RAMS perspective next to each of the steps of the systems engineering process, in line with the level of detail about the system design required to perform the analysis.

While the image presents a systems engineering process based on the Arcadia methodology, and a safety and realibility workflow aligned with the standards applicable in the space sector (ECSS standards), the process described is very generic and with minor adaptations can be implemented in any other safety critical application.


Model Based Safety and Reliability Analysis Workflow
Model Based Safety and Reliability Analysis Workflow

ATICA framework implements a modular architecture, with the Model Based Safety Analysis (MBSA) as central module and multiple extensions covering parts of the Systems Safety and Reliability process.

  • ATICA MBSA is the base module, encapsulating the systems safety metamodel and the main safety processes (see Functional Hazard Analysis).
  • ATICA REQS is the extension that enables interoperability with requirement management tools, allowing to import / export requirements in standard format (ReqIF).
  • ATICA FTA is the Fault Tree Analysis extension, it encapsulates an editor and mathematical solvers to enable direct edition of trees and link with design and safety artifacts in the model.
  • ATICA RAF the Reliability Analysis Framework, an extension to model failure causes directly linked to the actual physical implementation of the system (lowest level of abstraction).

This month we have consolidated a new package of updates in the Reliability Analysis Framework, enabling traceability from high level design descriptions (systems and logical level) to the detailed implementation described in the End-Product Breakdown Structure layer.

About Capella End-Product Breakdown Structure

Capella’s End-Product Breakdown Structure (EPBS) layer allows to explictly define a Bill of Materials for the system of interest. Compared to the Physical Architecture, the EPBS is especially suited to describe the actual implementation of units and subsystems, declaring the Off-the-Shelf components that constitute it. While this is originally prepared to facilitate the coordination between design and supply operations teams; the perspective will prove very useful for realibility analysis.

More about EPBS could be found here.

Updates in the Reliability Analysis Framework

To implement reliability analysis we have extended the Configuration Item element with new features to declare its type (to be chosen among typical electronic and electromechanical components), intrinsic reliability (typically expressed as Mean Time Between Failures, MTBF); and the most usual failures corresponding to the component type.

Configuration Item dialog box (original)
Configuration Item dialog box (original)
Configuration Item dialog box (extended)
Configuration Item dialog box (extended)

The Bill of Materials dashboard allows to summarize in a table all the constituents of a unit / block.

Bill of materials - list of configuration items
Bill of materials – list of configuration items

Finally, the Piece-part FMEA presents the failures of each item, and its effects at unit level. This allows to link elementary failures such as short circuit of a capacitor with effects at unit level like instability of output current which will be declared at the Physical Architecture layer.

Piece Part FMEA
Piece Part FMEA

To find out more about these features, go to the dedicated page about ATICA Reliability Analysis Framework.


For more info, do not hesitate to reach out to us through the contact form