Use Case #6:
Once the ADAS system moves to SOP and beyond the validation process doesn’t end- there may be just a brief pause. That’s because OEM customers and/or dealers are likely to submit trouble tickets describing issues with system functionality, including cases where the system activated unnecessarily under certain conditions, or failed to activate when it should have. When there appears to be a pattern in the failures that are reported, the ticket generally gets escalated to Engineering, who then try to reproduce the problem and see if a software update may be required. The first place to look for data that could help reproduce the issue is in the archived data that was used for validation. Let’s say the issue was lane guidance failures at night on curvy roads. It would be very difficult for most engineering teams to find and extract the relevant test cases from a sea of data across thousands of drive trials.
If Ottometric was used to validate the ADAS function prior to SOP, the Engineering team can benefit from the prior analysis to easily identify and extract drive segments that are similar to the reported failure conditions. All the drive data would have already been classified and meta-tagged for environmental conditions- making it easily searchable. In addition, the Scenario Prioritization Ranking (SPR) technology can be used to “fingerprint” the failure condition and identify other drive segments with a similar fingerprint. These drive segments can then be used to reproduce the problem on a HiL system and/or test any fixes to make sure that the problem is truly resolved without creating any other regressions.
• Creates a compact regression test suite to reproduce failures and test software updates
• Shortens the trouble ticket resolution time by weeks