| RFQX-1001379436-P10-000-01-0009 | Method and scope shall be proposed to and approved by the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0010 | Documentation on the method and results shall be provided to the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0011 | Note: The vehicle manufacturer and supplier shall collaboratively define the context of the system or function to enable the supplier performing the risk assessment. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0014 | For each risk identified in the cybersecurity risk analyses, a risk treatment decision shall be made to avoid, reduce, share, or retain the risk. | Needs Customer Clarification | Low | Cybersecurity requirement handling | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0016 | It shall be possible to verify which cybersecurity controls were derived from which requirements. | Needs Customer Clarification | Low | Cybersecurity requirement handling | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0026 | Methods shall be proposed to and approved by the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0028 | Selection of cryptographic methods and their use shall be agreed upon between the vehicle manufacturer and the supplier. | Accept with Assumption | High | None | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0033 | Methods shall be proposed and approved by the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0035 | The details shall be agreed upon between the vehicle manufacturer and the supplier. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0036 | Only hardware interfaces and protocols specified by the vehicle manufacturer shall be available in series production. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-1001379436-P10-000-01-0041 | It shall be possible for the vehicle manufacturer to securely inject key material and other data used for cybersecurity controls into the ECU according to the specification of the vehicle manufacturer. | Partially Accept | High | Key management | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-1001379436-P10-000-01-0042 | Secrets, public keys and other data used for cybersecurity controls in production vehicle systems shall be different from those used in pre-production phases. | Accept with Assumption | High | Key management | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0045 | It shall be possible to update the software of the ECU. | Accept with Assumption | High | Cybersecurity requirement handling | Validate assumption with customer; complete mapping; implement. |
| RFQX-1001379436-P10-000-01-0052 | The report shall include information needed to identify the affected vehicles/products. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0053 | Methods including the stipulation of a reasonable notification time shall be proposed to and approved by the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0054 | Following each identified and reported vulnerability, the supplier and vehicle manufacturer shall agree on an initial response to the vulnerability. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-1001379436-P10-000-01-0056 | The information shall contain • the version(s) of affected hardware or software components, • nature of the vulnerability, • description of the affected cybersecurity goal, • technical conditions to exploit the vulnerability, • impact of the exploitation and • possibilities to remove the vulnerability. | Needs Customer Clarification | Low | Vulnerability management | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0057 | Methods including the stipulation of a reasonable reporting time shall be proposed to and approved by the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0063 | All secrets specified by the vehicle manufacturer shall be protected throughout the lifecycle of the ECU. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-1001379436-P10-000-01-0064 | End-of-life and decommissioning shall be specifically considered. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0065 | Notes: a) It shall not be possible for a third party to reuse an ECU without system support from the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-1001379436-P10-000-01-0066 | b) Decommissioning of an ECU shall not have the potential of causing unacceptable risk to the road user or the vehicle manufacturer. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0001 | The gearbox itself shall be used in all drivetrains and the ECA shall be common and must be complaint to be put on any driveline setup. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0008 | The variant type shall be based on delivery agreement and Brand involved. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0009 | Common marking requirements that must be fulfilled for each marking variant are: Marking method: MA1 Marking height: 3 mm Date format: YYMMDD A unique serial number A DMC according to Scania STD 4562 (Ref 14.18) that contains the part number and serial number information. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0010 | The marking shall not be visible when the ECA is mounted on a gearbox. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0011 | The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0015 | 4.16) shall be marked according to the requirements in Scania STD19 (Ref 14.17) Tentik, wordmark variant W Part number (9 digits, two spaces in format 12 345 6789) Marking method: CAS Marking height: 2-6 mm. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0016 | Details to be agreed with Traton 2.9 Traton shall be invited to participate in electrical and mechanical design reviews. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0017 | 2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0018 | 2.12 Traton requires: - Documentation of the product, i.e. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0024 | When the ECA is assembled, it shall not be possible to insert an object larger than Ø0,2 mm (A wire could be used as test object) between the ECA and gearbox flange, so that the object enters the space behind the ECA. The rubber grommet at the lower part of the flange can have the same interface as the surrounding aluminum flange. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0028 | The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0033 | It shall be possible to pull the pushrod 50 times with a force of 300 N without risk for it to come loose from the ECA. Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0036 | The ECA shall provide a support for a clutch snap in tool on the marked surface in Figure 4 ISO view of 3D envelope. The maximum force is 1kN. Surface indents are allowed as long as it does not affect other requirements or the structural integrity of the ECA. | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0037 | The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0038 | Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. | Needs Customer Clarification | Low | None | Confirm with customer whether this is a binding requirement and assign a customer ID. |
| RFQX-3299216-1-0039 | The hole shall be equipped with a cover possible to assemble and disassemble at least 50 times without tools. If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature. It shall still remain intac t and keep tightness after vibration testing (See req.10.5) | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0040 | When the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mm into the gearbox housing between the cover and ECA. A wire could be used as test object. Figure 6 - Snap in tool space | Partially Accept | Medium | None | Agree responsibility split (DIA) for the non-ECU portion. |
| RFQX-3299216-1-0041 | The ECA shall have a loop or similar feature where the cable can be fixated with a cable tie Optionally an M8 screw thread and rotation stop for a sheet metal bracket indicated in Figure 4 - ISO view of 3D envelope, can be provided. The loop or Scania assembled bracket shall be located close to the centre ( ± 20 mm) of the cable section between the connector and last cable fixation point on the gearbox | Partially Accept | Low | None | Agree responsibility split (DIA) for the non-ECU portion. |