Figure 1 shows the supplier side of the use case.

Figure 1 - Supplier Side of the Exchange Models Use Case
The task of the supplier is to create a solution taking into account timing requirements of the OEM and additional functional control performance requirements. After attaching the OEM’s timing requirements to the created solution, he can extract the timing model that is communicated to the OEM for the purpose of timing validation of the overall system. The timing model contains the following artifacts:
1. Controller timing structure: executable entities (e.g. tasks and runnables) and their execution patterns.
2. Controller timing properties: execution times of the executable entities, etc.
Additionally, the supplier can derive Controller timing requirements from the chosen solution that are necessary to ensure the control performance of the functionality (e.g. minimum sampling periods, maximum delay, etc.). These requirements complement the OEMs timing requirements and must be fulfilled in the final solution, i.e. they must be validated by the OEM after system integration.
Obviously, before delivering the solution to the OEM, the supplier must check whether or not all timing requirements imposed by the OEM are met. For this purpose heanalyzes the timing model and compares the solution’s timing properties against the OEM’s timing requirements.
|