The specification and design contain enough information to carry out SOTIF activities, covering where applicable: the intended functionality and supporting subsystems including the operational design domain, control authority over vehicle dynamics, vehicle-level SOTIF strategy, use cases and their active, inactive and transition states and the decision-making logic; the design of the system and elements; performance targets of sensors, controllers, actuators, maps and other inputs; dependencies on the driver, interface, remote operator, other road users, environment, infrastructure, data exchange and remote software updates; reasonably foreseeable direct and indirect misuse; potential performance insufficiencies, triggering conditions and countermeasures; architectures; the warning and degradation concept including fallback, minimal risk condition and driver monitoring; data collection procedures before release and in operation; and mechanisms supporting risk mitigation in operation.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.