Fact Sheet: Risk Analysis and Assessment Modeling Language (RAAML)

PDF Download


Short description/
Transmitted information
  • Graphical descriptive modeling language
  • Language designed for usage with SysML 1.x and SysML 2.0
  • Suitable for mechatronic systems
  • Suitable for purely mechanical systems
Normative document
Version / Release state
  • Version 1.0
Release date
  • December 8, 2021
Application scope
  • Describe safety and reliability analyses and requirements
  • Describe system traceability to analyses
  • Traceability across multiple aspects/views ("from analyses to system model, requirements and test")
  • Cross-disciplinary communication and collaboration
  • Enabling model exchange internally and externally
Promoting bodies
  • prostep ivip Association
  • GfSE
  • OMG Standard (to be finalized in 4th Quarter, 2021)
IT Standard classification
  • Modeling Standard
Data format
  • Graphical modeling language
Additional available resources
  • Internal tool implementations
  • Literature (Books, Scientific Papers)
Relevant prostep ivip project groups
  • -

Positioning of RAAML in V-Model


  • Enables OEM-to-Tier and Tier-to-Tier model sharing for safety and reliability analysis information.
  • One Automotive Domain and cross industry Safety and Reliability profile/library to provide a common modeling approach for common tools used for safety and reliability analyses.
  • Provides a number of analysis tool frameworks to support FTA (Fault Tree Analysis), FMEA (Failure Mode and Effects Analysis), FMEDA (Failure Modes Effects and Diagnostic Analysis), STPA (Systems Theoretic Process Analysis), Risk Assessment, and GSN (Goal Structuring Notation).
  • Provides an automotive specific package which includes ISO 26262 usage of HAZOP (HAZard and OPerability), HARA (Hazard Analysis and Risk Assessment), and common safety requirement type definitions.
  • Provides a common language to enable tool interoperability for common analysis tools.
  • Was created with the collaboration of Automotive Industry, Nuclear Industry, Space Industry, Aerospace Industry, Robotic Industry, Tool Vendors, INCOSE, GfSE and Academia.
  • Provides a large efficiency gain potential and improved system to analysis traceability

Relevance and Benefit for MBSE

Model-Based Systems Engineering (MBSE) is gaining popularity in organizations creating complex systems where it is crucial to collaborate in a multi-disciplinary environment. SysML, being one of the key MBSE components, has a good foundation for capturing requirements, architecture, constraints, views and viewpoints. However, SysML does not provide the constructs to capture safety and reliability information in the system model. A group of industry experts at the OMG has been working since 2016 to define a new specification providing the necessary capabilities.

The need for a standardized UML profile/library for addressing safety and reliability aspects emerged long ago. Working group members have seen multiple commercial-grade model-based safety and reliability solution implementations being developed during the recent years and successfully used in practice. While the various safety and reliability implementations may fit the needs for a specific purpose, there are many instances where information needs to be traced and shared across multiple organizations. These inconsistent model-based solutions prohibit direct model sharing between organizations and across the various tools. One of the key goals for the working group is to reconcile these different approaches to alleviate the industry from repeatedly formulating safety and reliability constructs in their tools. The specification provides the modeling capabilities for tool vendors to build safety and reliability modeling tools that provide traditional representations (e.g. trees, tables, etc.) while using a modern model-based approach.

Risks and Impediments

What happens if we do nothing

  • Software vendor solutions that will lock AutoMOTIVE OEMs into proprietary products not based on standards.
  • Major and lower tier suppliers unable to support diverging OEM proprietary standards without adding significant time and cost which eventually gets shared with the OEMs.
  • Supplier requirements not considered → no collaboration possible