A field monitoring process to ensure SOTIF in operation is defined before release and executed afterwards. Expectations depend on the automation level, complexity and criticality of hazards: market observation may suffice at lower levels, while higher levels may need data storage or event recorders and on-board monitoring specified during development. Topics include incidents where the function caused or could have caused harm or exceeded values that might lead to harm (accident reports, driver reports, misuse reports, on-board signals such as violated minimum distance or near-triggered reactions), the body of knowledge from public incidents and similar systems, and context evolution such as changes in road and traffic, regulation, infrastructure, new usage and misuse and road user characteristics.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.