M
"

Directory

SUNRISE Safety Assurance Framework

Input

Input Scenario Create Format Store Environment Query & Concretise Allocate Execute Safety Argument Coverage Test Evaluate Safety Case Decide Audit

The Input block provides data to be used in other SAF blocks such as ISMR and Safety Performance Assurance. As the figure shows, there are five arrows that input into SAF blocks originating from the Input block. The information covered by the Input block includes items like the description of the Operational Design Domain (ODD), external requirements, CCAM system specifications and pass/fail criteria. Hereafter, you can read why and how each of these Input items are used in other parts of the SAF.

 

The ODD description of the CCAM system is considered in various other blocks of the SAF. The ODD description includes ranges of relevant attributes, such as the maximum vehicle speed and rainfall intensity it is able to handle. The ODD description may adopt an inclusive approach (describing what is inside the ODD), an exclusive approach (describing what is outside the ODD), or a combination of both. The following overview explains where and how the ODD description is used in other blocks of the SAF:

  • The Create block can utilize the ODD description to create scenarios that are part of the described ODD.
  • The Query & Concretize block uses the ODD description to generate the test cases that are needed for the safety assurance of the CCAM system.
  • The Test Evaluate block uses the ODD description to determine whether the CCAM system operated safely within its ODD in a specific test.
  • The Coverage block uses the ODD description to check whether the ODD space is sufficiently covered.
  • The Decide block uses the ODD description to come to a final decision on whether the CCAM system is safe enough for approval and deployment (or not).
  • The ISMR block (in-service monitoring and reporting) employs the ODD description in order to verify whether the system is operating inside its ODD.

 

Various SAF blocks also need the external requirements applying to the CCAM system. These requirements might include behavioural competences, regulations, rules of the road, safety objectives, standards or best practices. The following list explains where and how the external requirements are used in other blocks of the SAF:

  • The external requirements can be a source for creating scenarios. For that reason, the Query & Concretize block should take these requirements into account during its search for relevant scenarios.
  • The external requirements can also establish a means to measure compliance of test case results. For that reason, the external requirements might also have to be communicated to the Test Evaluate block.
  • The In-Service Monitoring and Reporting (ISMR) block needs external requirements to check whether system-level requirements are satisfied during deployment of the CCAM system.

 

The CCAM system is the main subject of the test cases, thus the CCAM system specifications are important input for various blocks of the SAF. The following overview explains where and how the CCAM system specifications are used in other blocks of the SAF:

  • CCAM system specifications can inspire the creation of new scenarios, especially if these specifications are common or shared between various vehicle models.  For that reason, CCAM system specifications can be input for the Create block.
  • The CCAM system specifications need to be provided to the Query & Concretize block, since they can also be a source for extraction of scenarios from databases by means of queries.
  • In case specific system variables need to be measured during the test execution, this information can also be provided to the Test Evaluate block.

 

The pass/fail criteria originating from the Input block, are important input for the following other blocks of the SAF:

  • Analyzing the pass/fail criteria can influence the search for scenarios. For that reason, pass/fail criteria can be input for the Query & Concretize block.
  • Pass/fail criteria are also important input for the Test Evaluate block, where they are used to check if a test cases has been successfully executed. When a test case is executed outside of the pass/fail criteria for example, then its execution would have to be deemed unsuccessful.