3299216_1

Product Requirement · System Function · Core ECA system behavior

Executive Takeaway

Confirmed by requirements: this product requirement contributes 216 Markdown-derived RFQ requirements with the strongest evidence in core eca system behavior. Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping core eca system behavior; system architecture design; system.

Confirmed by requirements: supplier positioning is 125 accept; 70 accept with assumption; 5 partially accept; 1 needs customer clarification; 5 needs internal review (showing 5 of 6). The generated traceability links this document to 20 supplier system requirement records. Inferred from mapped features, capabilities, and interfaces: the main design/security impact is core eca system behavior; system architecture design; system. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.

Requires customer confirmation: 2 document-linked open point(s) remain, mainly: Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. Do not convert these items into agreed baseline scope until the customer confirms the decision. Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.

Requirements216from this PDF

Critical6ranked

Open Points2linked

Derived SSRs20linked

Concept Impactyesdocument-specific

Estimation Impactyesdocument-specific

Document Abstract

Document Purpose

Confirmed by requirements: this product requirement contributes 216 Markdown-derived RFQ requirements with the strongest evidence in core eca system behavior.

Engineering Interpretation

Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping core eca system behavior; system architecture design; system.

Main Requirement Themes

Core ECA system behavior; System architecture design; System; System core; Responsibility and customer approval model (showing 5 of 8)

System / Security Impact

Inferred from mapped features, capabilities, and interfaces: the main design/security impact is core eca system behavior; system architecture design; system. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.

Supplier Proposal Impact

Customer Clarification Impact

Confidence and Limits

Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.

Main Requirement Themes

Theme	Engineering Meaning	Requirement Count	Representative Requirements
Core ECA system behavior	Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope.	210	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00065
System architecture design	Groups related document requirements into a single engineering theme.	189	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00065
System	Groups related document requirements into a single engineering theme.	149	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067
System core	Groups related document requirements into a single engineering theme.	142	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067
Responsibility and customer approval model	Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk.	54	REQ-AUTO-00072; REQ-AUTO-00074; REQ-AUTO-00076
Cybersecurity concept and evidence	Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations.	32	REQ-AUTO-00076; REQ-AUTO-00081; REQ-AUTO-00090
Interface	Groups related document requirements into a single engineering theme.	22	REQ-AUTO-00066; REQ-AUTO-00078; REQ-AUTO-00138
Constraint	Groups related document requirements into a single engineering theme.	21	REQ-AUTO-00069; REQ-AUTO-00072; REQ-AUTO-00080

Document Content Structure

Section	Requirements	Critical	Open Points	SSR Links
1 Document overview	1	0	0	1
2 General	13	0	0	3
3 Position definition	1	0	0	0
4 Mechanical interface	29	2	1	9
5 Clutch engage and disengage	24	1	0	6
6 SW functionality	50	2	1	10
7 Electrical	42	0	0	6
8 Reliability	8	0	0	4
9 Environmental impact	6	0	0	2
10 Environmental and electrical testing	14	1	0	5
11 Functional safety	5	0	0	2
12 Quality conformance verification	11	0	0	3
13 Sample maturity definition	5	0	0	1
14 References	7	0	0	3

What This PDF Is About

Field	Value
Source PDF	customer-input/pdf/3299216_1.pdf
Converted Markdown	converted/markdown/3299216_1.md
Document Type	Product Requirement
Domain	System Function
Scope Summary	216 extracted requirements; 20 linked SSRs; 2 linked open points.
Main Themes	Core ECA system behavior; System architecture design; System; System core; Responsibility and customer approval model (showing 5 of 8)
Does Not Confirm	Customer-owned responsibility, final customer decisions, and unresolved open points remain unconfirmed.
Confidence	High
Evidence Basis	Markdown-derived requirements and generated RFQX registers; no downstream PDF analysis.

Key Conclusions From This PDF

Confirmed by requirements: this product requirement contributes 216 Markdown-derived RFQ requirements with the strongest evidence in core eca system behavior.
Confirmed by requirements: supplier positioning is 125 accept; 70 accept with assumption; 5 partially accept; 1 needs customer clarification; 5 needs internal review (showing 5 of 6). The generated traceability links this document to 20 supplier system requirement records.
Requires customer confirmation: 2 document-linked open point(s) remain, mainly: Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. Do not convert these items into agreed baseline scope until the customer confirms the decision.

Critical Requirements

This table is horizontally scrollable. Use the bottom scrollbar to view all columns.

ID	Score	Category	Requirement / Reason	Supplier Position
REQ-AUTO-00146	95	High risk due to unclear OEM/supplier responsibility	Message contents to be agreed with Traton 6.9 ECA identification number: The ECA shall report a unique ECA individual identification number 6.10 Supplier code: The ECA shall report supplier code 5 via CAN.security relevant; architecture relevant; Needs Customer Clarification; linked open point; Unknown estimation impact; blocks SSR derivation	Needs Customer Clarification
REQ-AUTO-00078	77	High risk due to unclear OEM/supplier responsibility	P 1 Page 4 Mechanical interface 4.1 The maximum release stroke is 22,4 mm from FCCP 4.2 The total stroke of the actuator shall be 85 mm.security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact	Partially Accept
REQ-AUTO-00091	48	High risk due to unclear OEM/supplier responsibility	Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand.security relevant; architecture relevant; Partially Accept	Partially Accept
req-5.10	48	High risk due to unclear OEM/supplier responsibility	P 1 Page 5 Clutch engage and disengage 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to req 5.10,and max speed set to 125mm/s (see req 6.4) Time is measured according to Figure 7 – Max disengage time, where the dashed line is the position request as it becomes available on the CAN bus, and the full line is the actual PP.security relevant; architecture relevant; Partially Accept	Partially Accept
REQ-AUTO-00140	48	High risk due to unclear OEM/supplier responsibility	If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit.security relevant; architecture relevant; Partially Accept	Partially Accept
REQ-AUTO-00247	48	High risk due to unclear OEM/supplier responsibility	P 1 Page 10.5.11 CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y 10.5.12 CVS40 §5.6 TC-06 Thermal shock Y 10.5.13 CVS40 §5.7 TC-07 Splash water test Y 10.5.14 CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y 10.5.15 CVS40 §5.9 TC-09 Leakage search test Y 10.5.16 CVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors.security relevant; architecture relevant; Partially Accept	Partially Accept
REQ-AUTO-00116	44	General project impact	The FCCP after a clutch engage shall be updated to 90% of the step within 0,2 s per mm that the FCCP have changed during the stroke.security relevant; architecture relevant; High estimation impact	Accept with Assumption
req-6.20	44	High impact on diagnostic security	6.13 Error State Diagnostic - ESD and Error State Action - ESA The ECA shall send a bit field via CAN containing errors present Additionally, see req 6.20, req 6.22 ,req.security relevant; architecture relevant; High estimation impact	Accept with Assumption
REQ-AUTO-00164	44	General project impact	The filter time shall equal the update frequency .security relevant; architecture relevant; High estimation impact	Accept with Assumption
REQ-AUTO-00169	44	High impact on cybersecurity concept/work products	6.21 Cyber Security: Cybersecurity shall be considered through a separate process with the latest Traton workflow in mind.security relevant; architecture relevant; High estimation impact	Accept with Assumption
REQ-AUTO-00203	44	High impact on secure software update	7.36 Termination resistance: - 2 x 60 - Ω 1% resistors shall be used 7.37 Baud rate: 250 500 1000 kbit/s Flashing in production shall be possible with 1000kbit/s.security relevant; architecture relevant; High estimation impact	Accept with Assumption
REQ-AUTO-00204	44	General project impact	ID Requirements 7.39 Note: The layout shall always be present on the PCB and the supplier must be flexible in changing/removing the CAN related components in this section.security relevant; architecture relevant; High estimation impact	Accept with Assumption

Customer Clarifications / Open Points

Total Open Points2document-linked

P10priority

P20priority

Blocking Conceptyesyes/no

Blocking Estimationyesyes/no

Blocking SSRyesyes/no

This table is horizontally scrollable. Use the bottom scrollbar to view all columns.

Open Point	Priority	Question / Impact	Required Customer Decision	Recommended Supplier Position	Owner	Status
OP-004		Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.Update-control scope and evidence ownership stay open; risk of an unprotected update path.	Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.	Implement authenticated, integrity-protected ECU programming with controlled boot/app state; require OEM update-chain definition.	Shared (OEM backend / Supplier ECU)	Open
OP-011		Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.Supplier position, estimation, and affected design allocation remain conditional for the listed requirements.	Decide whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context.	Carry the items as customer-confirmation dependencies and review them in the next clarification workshop.	OEM / Customer	Open

Requirements From This PDF

Content / SectionSupplier PositionReview StatusSecurity CapabilityEstimation ImpactOpen Point

This table is horizontally scrollable. Use the bottom scrollbar to view all columns.

ID	Requirement / Proposal	Supplier Position	Review	Security Capability	Feature / Interface	SSR	Open Point	Source
REQ-AUTO-00146	Message contents to be agreed with Traton 6.9 ECA identification number: The ECA shall report a unique ECA individual identification number 6.10 Supplier code: The ECA shall report supplier code 5 via CAN.Proposal: Needs customer clarification. The requirement implies customer-owned infrastructure, approval, or a responsibility split that is not yet available.	Needs Customer Clarification	Reviewed Internally	None	External interfaces External Interfaces; OEM/Customer Review Interface	None	OP-011	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00078	P 1 Page 4 Mechanical interface 4.1 The maximum release stroke is 22,4 mm from FCCP 4.2 The total stroke of the actuator shall be 85 mm.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation.	Partially Accept	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	OP-004	4 Mechanical interface page 8 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 8
REQ-AUTO-00091	Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation.	Partially Accept	Proposal Ready	None	Backend and IT integration None	SSR-COM-003	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
req-5.10	P 1 Page 5 Clutch engage and disengage 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to req 5.10,and max speed set to 125mm/s (see req 6.4) Time is measured according to Figure 7 – Max disengage time, where the dashed line is the position request as it becomes available on the CAN bus, and the full line is the actual PP.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation.	Partially Accept	Proposal Ready	None	Backend and IT integration None	SSR-COM-003	-	5 Clutch engage and disengage page 13 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 13
REQ-AUTO-00140	If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation.	Partially Accept	Proposal Ready	None	Backend and IT integration None	SSR-COM-003	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00247	P 1 Page 10.5.11 CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y 10.5.12 CVS40 §5.6 TC-06 Thermal shock Y 10.5.13 CVS40 §5.7 TC-07 Splash water test Y 10.5.14 CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y 10.5.15 CVS40 §5.9 TC-09 Leakage search test Y 10.5.16 CVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors.Proposal: Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation.	Partially Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	10 Environmental and electrical testing page 43 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 43
REQ-AUTO-00116	The FCCP after a clutch engage shall be updated to 90% of the step within 0,2 s per mm that the FCCP have changed during the stroke.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
req-6.20	6.13 Error State Diagnostic - ESD and Error State Action - ESA The ECA shall send a bit field via CAN containing errors present Additionally, see req 6.20, req 6.22 ,req.Proposal: Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies.	Accept with Assumption	Proposal Ready	Diagnostic security	Diagnostic security None	SSR-RBAC-001	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00164	The filter time shall equal the update frequency .Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00169	6.21 Cyber Security: Cybersecurity shall be considered through a separate process with the latest Traton workflow in mind.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	Cybersecurity requirement handling	Cybersecurity requirement handling None	SSR-CON-001	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00203	7.36 Termination resistance: - 2 x 60 - Ω 1% resistors shall be used 7.37 Baud rate: 250 500 1000 kbit/s Flashing in production shall be possible with 1000kbit/s.Proposal: Accept with assumption. Implement ECU-side secure update/bootloader behavior, including controlled programming state, authenticity/integrity checks, and verification evidence, subject to customer-confirmed SUV2 applicability and update-chain ownership.	Accept with Assumption	Proposal Ready	None	System behavior; Secure software update and flash readiness None	SSR-UPD-001	-	7 Electrical page 34 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 34
REQ-AUTO-00204	ID Requirements 7.39 Note: The layout shall always be present on the PCB and the supplier must be flexible in changing/removing the CAN related components in this section.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces; OEM/Customer Review Interface	SSR-COM-002	-	7 Electrical page 35 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 35
REQ-AUTO-00212	The layout of the PCB, including component placement, shall take the applying of conformal coating into consideration so that the aforementioned requirement can be met.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00253	The supplier shall analyse risks of individua l HW and SW components, mechanics, and any other technologies, independently of the scope of ISO 26262.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-009	-	11 Functional safety page 49 Source details Document section 11 Functional safety Section path 11 Functional safety Page reference page 49
REQ-AUTO-00249	P 1 Page 10.7.14 CVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y 10.7.15 CVS46 §4.7 Test VCB CTE N 10.7.16 CVS46 §4.8 Test VCB AN and VCB CP N 10.7.17 CVS46 §4.9 Test C-VCB-VCA N 10.7.18 CVS46 §4.10 Test TSUP VCB A N 10.7.19 CVS46 §4.11 Test TSUP VCB B N 10.7.20 CVS46 §4.12 Test VCB Surge N 10.7.21 CVS46 §4.13 Test VCB Burst N 10.7.22 CVS46 §4.14 Test VCB Charging mode N 10.7.23 CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y 10.7.24 CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y 10.7.25 CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y 10.7.26 CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y 10.7.27 CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	10 Environmental and electrical testing page 47 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 47
REQ-AUTO-00077	Should the PP be fully calculated from the AP-sensor, then this offset should not exist.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline.	Needs Internal Review	Reviewed Internally	None	Hardware platform support None	None	-	3 Position definition page 7 Source details Document section 3 Position definition Section path 3 Position definition Page reference page 7
REQ-AUTO-00122	100ms after reaching 2 mm from target, the maximum position error should be ±0.1mm.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline.	Needs Internal Review	Reviewed Internally	None	System behavior None	None	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
req-5.1	The full strokes should be performed within 180 ms, as specified in req 5.1 and 5.2.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline.	Needs Internal Review	Reviewed Internally	None	System behavior None	SSR-SYS-009	-	14 References page 57 Source details Document section 14 References Section path 14 References Page reference page 57
REQ-AUTO-00275	Between the two movements the actuator should remain in the fully disengaged position.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline.	Needs Internal Review	Reviewed Internally	None	System behavior None	None	-	14 References page 57 Source details Document section 14 References Section path 14 References Page reference page 57
REQ-AUTO-00276	After the complete engagement the actuator should remain in this position until the next disengagement is requested.Proposal: Needs internal review. Confirm whether this should-level requirement is in the committed baseline.	Needs Internal Review	Reviewed Internally	None	System behavior None	None	-	14 References page 57 Source details Document section 14 References Section path 14 References Page reference page 57
REQ-AUTO-00066	2.4 The actuator will be controlled by a position and speed demand by CAN-bus 2.5 The actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connection 2.6 The ECA units shall be manufactured with marking variants according to the requirements in Scania STD19 (Ref 14.17).Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00068	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.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00070	The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00071	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.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00072	Alternative design: CXM or equivalent combination of date dial and date field The rubber cover marking shall not be visible when the ECA is mounted on a gearbox 2.8 The ECA shall be designed with Remanufacturing and/or Refurbishment in mind with possibility of swapping out larger electronic assemblies/components.Proposal: Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00074	2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00076	2.12 Traton requires: - Documentation of the product, i.e.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior; Security evidence and traceability OEM/Customer Review Interface	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00084	4.8 The ECA shall be adapted for 6 pcs M8 flange screws described by Scania STD4435Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 9 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 9
REQ-AUTO-00089	Surface indents in the contacts are allowed as long as the structural integrity is unaffected 4.12 The pushrod end that makes contact with the clutch lever shall be a Ø15,93±0,07 mm steel sphere.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-DAI-002	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00092	4.14 The ECA shall allow space for external tools according to the cylinders in the 3D envelope attached.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00093	4.15 The ECA shall have a window where the volume shown in Figure 6 – Snap in tool space, could pass through(See req.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Engineering tooling None	SSR-TOOL-004	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00094	4.16 The ECA shall provide a support for a clutch snap in tool on the marked surface in Figure 4 - ISO view of 3D envelope.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Engineering tooling None	SSR-TOOL-004	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00095	P 1 Page 4.17 The hole shall be equipped with a cover possible to assemble and disassemble at least 50 times without tools.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00098	Figure 6 - Snap in tool space 4.19 The ECA shall have a loop or similar feature where the cable can be fixated with a cable tie.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Engineering tooling None	SSR-COM-004	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00099	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 4.20 The connector for communication and power shall be positioned as indicated in Figure 4 - ISO view of 3D envelope, when connected.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Hardware platform support None	SSR-COM-005	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00138	ECA behavior and additional requirements for this mode can be found in (Ref 14.16) Control mode Test mode 0x04 6.3.5 When this Control Mode is sent the actuator shall behave as if the power supply was cut with aspect to control of the actuator.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00139	CAN communication shall still be active.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00141	6.5 Self-adjustment The self-adjustment signal defines the restrictions of how the FCCP shall be identified.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00143	The value of the FCCP shall be reported via CAN(Ref 14.14) Req.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00145	6.6.1 When low accuracy mode is requested, the maximum push rod position(PP) error can be ±0.5mm Accuracy mode Low accuracy 0x0 6.6.2 Accuracy according to 5.10 shall be fulfilled.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00150	ESA definition( Ref 14.16) The supplier shall provide documentation for the ESD bits and related faults .Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior; Security evidence and traceability OEM/Customer Review Interface	SSR-SYS-002	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00152	6.14.1 Boot Mode If the actuator is in boot mode, 0x00 shall be reported as active state.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00159	0xB 6.14.8 Debug / Test This value shall be sent when the actuator is in debug or test control state.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00168	6.20 Diagnosis: CVS120 shall be applied (Ref 14.12).Proposal: Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00172	P 1 Page 6.23 Validation and Invalidation: The reported ESD must be able to be validated and invalidated.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior; Security evidence and traceability OEM/Customer Review Interface	SSR-VV-001	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00173	6.24 Diagnosis tracking: The gearbox control unit(TCU) shall be responsible for setting DTCs based on received notifications from ECA via ESD, including time-stamps, occurrence counters etc.Proposal: Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-DIAG-001	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00174	If higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-003	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00175	Internally stored parameters may be accessible only using supplier defined tools .Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	System behavior OEM/Customer Review Interface	None	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00176	6.25 Data logging: Any data logged or stored shall be agreed upon together with Traton.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00177	6.26 Data storage: When storing data in the device, the supplier shall take measures to prevent corruption of data which can occur for example when suffering power loss during read or write cycles.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces; OEM/Customer Review Interface	SSR-COM-002	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00178	The supplier shall also ensure that systems are in place that ensure that data corruption is handled without loss of data, or loss of function.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Application software behavior OEM/Customer Review Interface	SSR-SYS-007	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00180	6.28 Reset: It shall be possible to reset the ECA application with a power off/on cycle after all functional safety events.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Application software behavior None	SSR-SYS-007	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00183	7.3 A safe boot sequence must be set to prevent unwanted or undefined behavior during or after loss of power, or corruption of stored data.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00193	The Wake-up signal shall also be connected to a digital input on the µP.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00194	Special precautions shall be taken to prevent direct connection between Wake-up and 30 in case of a single failure.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00195	After the wake-up line goes to high state: The ECA shall communicate on the CAN line within 250ms in case of a normal start -up The ECA shall be ready to open the clutch within 350ms in case of a normal start -up The ECA shall be ready to open the clutch as soon as possible after necessary movements in case of an abnormal start-up.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00196	After movement and reset, the ECA shall communicate on the CAN line within 250ms After movement and reset, the ECA shall be ready to open the clutch within 400ms In the case if the wake-up goes "high" at the same time as U30 signal the ECA should be ready to open the clutch within 3 seconds.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00199	If a signal for disengaging the clutch is received the ECA shall actuate the request regardless of CAN-request.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 33 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 33
REQ-AUTO-00200	Any watchdog circuit shall have no influence on the CAN bus.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 34 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 34
REQ-AUTO-00201	The CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 34 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 34
REQ-AUTO-00202	7.35 The controller and transceiver shall be CAN FD ready.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 34 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 34
REQ-AUTO-00206	The CAN front end shall be designed to comply with TB1905.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	7 Electrical page 35 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 35
REQ-AUTO-00209	The melting point of the soldering material and the composition of the soldering material shall be declared by supplier.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00218	The following requirements shall be fulfilled: The unit shall withstand the salt-spray environment, according to CVS40 §6.1.6, without clogging of the membrane.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00220	The design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00224	8.4 Six consecutive units shall run past 6.5M actuations at the supplier, and continue to end of life.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-LIFE-002	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00225	Three consecutive units shall run past 6.5M actuations at Scania, and continue to end of life.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-LIFE-002	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00232	Out of a recycling and environmental perspective the following standards shall be taken under consideration in addition to CVS55(Ref 14.32): STD4158, Chemical substances which shall not be used – Scania Black list.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-003	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
REQ-AUTO-00239	CAN communication shall not be affected.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	10 Environmental and electrical testing page 40 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 40
REQ-AUTO-00241	Accepted behaviour in this case shall be agreed upon between Traton and Supplier.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	10 Environmental and electrical testing page 40 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 40
REQ-AUTO-00256	ID Verification methods 12.1 Conformance to Requirement Specification A1 The supplier must do conformance test of all external and internal I/O.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior; Security evidence and traceability OEM/Customer Review Interface	SSR-VV-001	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00257	This test must verify that all internal and external I/O fulfils the requirements in this specification.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior None	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00258	A2 The supplier must perform full DV (Design Verification at B-sample level) and full PV (Product Validation at C-sample level) environmental test programs according to CVS40 and CVS41 (incl.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior; Security evidence and traceability OEM/Customer Review Interface	SSR-VV-001	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00260	Additional tests initiated and performed by the supplier must be discussed with Traton.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00261	A3 The supplier must test the connectors according to TB1787.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00262	A4 The supplier must do EMC tests with the unit alone.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00263	The supplier must certify the ECA according to UN ECE R10 (EMC), according to the latest revision with all amendments.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00264	A5 The supplier must check that both prototypes and serial units fulfil the dimension requirement according to any relevant Traton supplied drawings.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00266	12.3 Testability The supplier of the unit must write software to enable his own testing of the unit during development, production and on any claimed unit.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	Application software behavior OEM/Customer Review Interface	SSR-SYS-007	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00267	However, dividing sample phases into several generations must be agreed upon between Traton and the supplier.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	13 Sample maturity definition page 51 Source details Document section 13 Sample maturity definition Section path 13 Sample maturity definition Page reference page 51
REQ-AUTO-00271	The supplier must use the sample denominations requested by Traton.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	13 Sample maturity definition page 51 Source details Document section 13 Sample maturity definition Section path 13 Sample maturity definition Page reference page 51
REQ-AUTO-00273	P 1 Page Appendix B – Life length test The life time testing of the ECA shall consist of 6500000 repetitions of the test cycle described in ”I – Test cycle” Two different test profiles/setups can be used.Proposal: Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method.	Accept with Assumption	Proposal Ready	None	External interfaces External Interfaces	SSR-COM-002	-	14 References page 57 Source details Document section 14 References Section path 14 References Page reference page 57
REQ-AUTO-00277	• A function test rig shall be used for function tests between intervals • At 6.25M cycles a function test at -40C as well as the release frequency test is performed, before the rigs are put into run-to-failure mode • Run-to-failure mode implies cycling at intermediate load and RT/80C until failure • @Temp durability will start with 15/min frequency to verify if 30/min is feasible • One rig at RT shall run at 15/min as a reference unit for cycle acceleration.Proposal: Accept. Provide the cybersecurity concept as a supplier work product covering scope, assumptions, risk-treatment traceability, cybersecurity goals/requirements, mitigation strategy, V&V approach, and open responsibility dependencies.	Accept with Assumption	Proposal Ready	None	Application software behavior None	SSR-SYS-007	-	14 References page 59 Source details Document section 14 References Section path 14 References Page reference page 59
REQ-AUTO-00186	If internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00227	8.6 Failure rate for ECU and electronics shall be less than: 0ppm @ “0” km 200ppm/year during year 1-5 400ppm/year during year 6-10 1000ppm/year during year 11-15 8.7 External vulnerable components might need to be replaceable.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00236	For type approval, the vehicle and its components shall comply with ECE Regulation No.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
req-6.3	The signal is valid during Control Modes RPC and TC(see req 6.3).Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00171	P 1 Page 6.22.4 Positions sensor short circuit / open load (if used) 6.22.5 Watchdog error 6.22.6 Low voltage 30 6.22.7 CAN-timeout (stored and sent when possible) 6.22.8 High temperature/current consumption (system needs to indicate abnormal usage that can damage the device), indicate a self-protective mode (if applicable) 6.22.9 Error on temperature sensor 6.22.10 High friction in mechanical system 6.22.11 Other electrical HW errorProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	6 SW functionality page 26 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 26
REQ-AUTO-00250	Y 10.7.28 CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y 10.7.29 CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y 10.7.30 CVS46 §5.2.2 Vehicle test RE: Self- interference Y 10.7.31 CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N 10.7.32 CVS46 §5.3.1 Vehicle test: AC charging: Vehicle in AC charging mode N 10.7.33 CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N 10.7.34 CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y 10.7.35 CVS46 §5.4.1 Vehicle test RI: External interference sources YProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	10 Environmental and electrical testing page 47 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 47
REQ-AUTO-00063	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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	1 Document overview page 3 Source details Document section 1 Document overview Section path 1 Document overview Page reference page 3
REQ-AUTO-00064	P 1 Page 2 General 2.1 The clutch actuator shall be electrically driven.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00065	2.2 The actuator is placed outside of the gearbox 2.3 The ECA (Electric Clutch Actuator) must have its own internal ECU for manoeuvring and error handling.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00067	The variant type shall be based on delivery agreement and Brand involved.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00069	The marking shall not be visible when the ECA is mounted on a gearbox.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 4 Source details Document section 2 General Section path 2 General Page reference page 4
REQ-AUTO-00073	Details to be agreed with Traton 2.9 Traton shall be invited to participate in electrical and mechanical design reviews.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00075	2.11 The mechanics shall also be tested and verified, in an overall durability test as stated in Appendix B etc.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	2 General page 5 Source details Document section 2 General Section path 2 General Page reference page 5
REQ-AUTO-00079	4.3 The clutch actuator shall be able to reach the extreme positions A and B in with the center of the pushrod end.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 8 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 8
REQ-AUTO-00080	P 1 Page 4.4 ECA shall not interfere with any geometry in the 3D envelope 53612101-1 1_RFQ2030.stp except where interference fits or other types of functional contacts are required.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 9 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 9
REQ-AUTO-00081	4.6 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	4 Mechanical interface page 9 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 9
REQ-AUTO-00082	4.7 When the ECA is assembled, a gap of 3,5 mm towards surface B with a profile tolerance of ±1 mm to the nominal dimensions shall be provided.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 9 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 9
REQ-AUTO-00083	The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 9 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 9
REQ-AUTO-00085	P 1 Page 4.9 The ECA shall be adapted for 2 pcs 10 mm guide pins.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00086	Figure 5 - Gearbox flange 4.10 The guide pin holes in the ECA shall be Ø 10,1±0.05 mm and at least 12 mm deep.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00087	The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00088	4.11 The ECA shall be able to be held by the guide pins only while being exposed to the max clutch load, (req.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00090	4.13 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	4 Mechanical interface page 10 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 10
REQ-AUTO-00096	If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
req.10.5	It shall still remain intac t and keep tightness after vibration testing (See req.10.5) 4.18 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.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00100	Details regarding actual length and positioning tolerances shall be agreed in design phase.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00101	4.21 If the ECA is powered up with the PP in the utmost forward position (for example when not connected to the clutch lever) it shall move AP to its utmost reversed position.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	4 Mechanical interface page 11 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 11
REQ-AUTO-00102	4.23 The actuator shall apply a preload force for the release bearing.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 12 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 12
REQ-AUTO-00103	The preload force measured on the push rod shall be 150N to 250N independent of the clutch position 4.24 The pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 12 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 12
REQ-AUTO-00104	4.25 It must be possible to assemble the actuator independent of the lever position without any power connection.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	4 Mechanical interface page 12 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 12
REQ-AUTO-00105	This means that the push rod shall be possible to move by hand.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 12 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 12
REQ-AUTO-00106	4.26 When the clutch is fully engaged, the active control mode is position or torque control mode and there is no active request to extract the pushrod (clutch opening motion), the ECA shall not apply a force outside of limits in preload force defined in req.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	4 Mechanical interface page 12 Source details Document section 4 Mechanical interface Section path 4 Mechanical interface Page reference page 12
REQ-AUTO-00108	This shall be measured against the maximum disengage force (See Appendix A) Figure 7 – Maximum disengage timeProposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 13 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 13
req-6.4	P 1 Page 5.2 It shall be possible to engage the clutch in 180ms (=Ts) with accuracy according to re q.5.10, and the max speed set to 125mm/s (see req 6.4).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	5 Clutch engage and disengage page 14 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 14
REQ-AUTO-00110	This shall be measured against the minimum engage force (See Appendix A) Figure 8 - Maximum engage timeProposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 14 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 14
REQ-AUTO-00111	P 1 Page 5.3 The clutch actuator shall report the absolute position of the current actuator stroke (AP) (Ref 14.14).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00112	5.4 It shall also report the position that corresponds to a fully closed clutch position (FCCP), expressed in absolute position of the actuator stroke and relative to the absolute zero position (See req.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00113	5.5 The clutch actuator shall be equipped with a displacement sensor measuring the movement of the push rod, (Ref 14.14) 5.6 The actuator must be able to determine the pushrod position according to the following: Accuracy (maximum difference between measured pushrod position and actual pushrod position): +/- 1.6mm.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00114	Range: 85mm (AP) 5.7 For each stroke that the actuator performs it shall adjust to the current wear of the clutch.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00115	This means that is shall be possible to request a relative stroke from the fully closed clutch position and achieve the step accuracy as defined in req.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00117	5.9 The maximum stationary position error relative to real FCCP (i e self-adjustment error + step response error) shall be ±0.15mm.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 15 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 15
REQ-AUTO-00118	P 1 Page 5.10 The actuator shall move the pushrod according to the following points: Actuator maximum speed: The maximum achievable speed of the pushrod shall be at least 125 mm/s.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
REQ-AUTO-00119	The actuator shall move the pushrod at the highest possible speed, limited only by its maximum achievable speed and the maximum speed request.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
REQ-AUTO-00120	6.4) Dynamics start of movement: The requested speed (or 125mm/s, if requested speed > 125mm/s) shall be achieved within 50ms from when a new value for requested position is sent.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
REQ-AUTO-00121	Dynamics end of movement: The requested speed shall be kept until 2 mm from the target position.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
req-5.1	The full strokes should be performed within 180 ms, as specified in req 5.1 and 5.2.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-009	-	5 Clutch engage and disengage page 16 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 16
REQ-AUTO-00124	5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 17 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 17
REQ-AUTO-00125	P 1 Page 5.12 The ECA shall be able to run the 4 second test cycle in Figure 11 - Release frequency test continuously for 5 hours without any degradation or failure.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 18 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 18
req-8.1	The test shall be done with the highest operating temperature (see req 8.1) and maximum clutch force (See Appendix A) Figure 11 - Release frequency testProposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 18 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 18
REQ-AUTO-00127	Between 16V and loss of power the ECA shall hold its current position or move towards requested position without any time requirement.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 19 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 19
REQ-AUTO-00128	The strategy shall be disc ussed and approved with Traton.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 19 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 19
REQ-AUTO-00129	5.1 and 5.2) Figure 12 - Class B exceptions 5.14 It shall be possible to keep the clutch disengaged continuously without risk of loss of function for 120 min.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Application software behavior None	SSR-SYS-007	-	5 Clutch engage and disengage page 19 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 19
REQ-AUTO-00130	This shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	5 Clutch engage and disengage page 19 Source details Document section 5 Clutch engage and disengage Section path 5 Clutch engage and disengage Page reference page 19
REQ-AUTO-00131	P 1 Page 6 SW functionality 6.1 TB4684 shall be applied.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 20 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 20
REQ-AUTO-00132	It shall be followed to its full extent.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	6 SW functionality page 20 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 20
REQ-AUTO-00133	When requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 21 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 21
REQ-AUTO-00134	Specific cases shall be approved with Traton.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 21 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 21
REQ-AUTO-00135	Control mode Absolute position 0x01 6.3.2 When requesting Relative Position Control (RPC) the actuator shall move to an offset that corresponds to the Requested Position from the Fully Closed Clutch Position (FCCP).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 21 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 21
REQ-AUTO-00136	Control mode Relative position 0x02 6.3.3 When requesting Torque Control (TC) the actuator shall actuate the requested motor torque.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 21 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 21
REQ-AUTO-00137	6.3.4 When requesting Test Mode, the actuator shall perform tests to detect latent faults.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00144	The value shall be frozen at the last identified position and used for RPC.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 22 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 22
REQ-AUTO-00147	6.11 SW number: The ECA shall report a complete SW version number.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00148	6.12 HW number: The ECA shall report a complete HW version number.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00151	6.14 System state The ECA shall report its current System State.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 23 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 23
REQ-AUTO-00153	0x0 6.14.2 Absolute Position Control This value shall be sent when the ECA is actuating Absolute Position Control.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00154	0x1 6.14.3 Relative Position Control This value shall be sent when the ECA is actuating Relative Position Control.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00155	0x2 6.14.4 Torque Control This value shall be sent when the ECA is actuating Torque Control.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00156	0x4 6.14.5 Self-Adjustment This value shall be sent when the ECA is performing a Self-Adjustment procedure that is not part of a RPC or TC request (i.e.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00157	0x5 6.14.6 Initializing This value shall be sent when the ECA is performing its initiation routine and is not yet available for control.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-002	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00158	0xA 6.14.7 Shut down This value shall be sent when the ECA is performing its shut down routing and is not available for control.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00160	0xC 6.14.9 Motor Brake Simulation This value shall be sent when the actuator is performing a motor brake simulation.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 24 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 24
REQ-AUTO-00161	P 1 Page 6.15 System Temperature The ECA shall report the current system temperature.(Ref 14.14) 6.16 Torque Feedback The ECA shall calculate and report the actuator motor torque.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00162	(Ref 14.14) 6.17 Current feedback The ECA shall report the current for each phase of the actuator.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00163	These values shall be calculated using a moving mean filter.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00165	(Ref 14.14) 6.18 Supply Voltage Feedback The ECA shall report the current system voltage.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
Req.ID-Description-6.19.1	(input voltage) (Ref 14.14) 6.19 Operational data The following operational data deemed important to store (req.6.16.1, req 6.16.2) (Ref 14.14) Req.ID Description 6.19.1 Operational hours: The ECA shall store and report its accumulated operational hours.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00167	6.19.2 Total travelled length: The ECA shall report its accumulated lifetime travel length.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00179	6.27 Calibration: There shall only be one calibration set of the ECA that is delivered to Traton, i.e, the calibration shall not be dependent of installation variants.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	6 SW functionality page 27 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 27
REQ-AUTO-00181	ID General electrical requirements 7.1 The electrical design must ensure that an internal short circuit through one of H -bridges (“shoot- through”) is avoided.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00182	7.2 Short circuit protection shall be implemented by hardware.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00184	7.4 A safe memory read/write sequence must also be implemented during actuator movement, in order to ensure safe and predictable behavior during operation, or in case of power lo ss.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
Req.ID-Connector-Requirements-7.5	Req.ID Connector Requirements 7.5 All external electrical connectors shall be geometrically coded.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00187	7.8 ECU tab headers shall comply with TB1787.(Ref 14.6) 7.9 ECU tab headers shall be made of self-extinguishing materials (i.e.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	7 Electrical page 28 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 28
REQ-AUTO-00188	All power used by the ECA shall be taken from this battery connection.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 29 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 29
REQ-AUTO-00189	The ground shall not be DC connected to the ECA housing.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 29 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 29
REQ-AUTO-00191	7.23 Quiescent current: According to CVS41 (Ref 14.2), must be met independent of input and output conditions.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 30 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 30
REQ-AUTO-00192	It shall be used to control the power up sequence to the µP.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00197	Definition ready to open clutch: The actuator position shall be between FCCP and FCCP -3mm and the ECA is capable to move to disengaged clutch directly when requeste d.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00198	Redundancies due improper shutdown shall be aligned with Traton.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 31 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 31
REQ-AUTO-00205	The components shall not be populated by default.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 35 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 35
REQ-AUTO-00207	The quality of the wire bonding and position shall be properly analyzed.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00208	The material shall be lead free and of ”high temperatures solder type”.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00210	The PCB must be supported and must not bent in any direction during the process.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-009	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00211	Conformal coating or lacquer shall cover the entire PCB and all solder joints.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00213	shall be specified in the initial offer.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00214	The conformal coating process and materials shall apply to the latest versions of IPC/EIA J-STD-001 (with applicable standards as e.g.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-009	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00215	HDBK-001, IPC-CC-830 and HDBK-830) and the visual appearance of the final coating shall be consistent with the latest version of IPC-A-610.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00216	Water based and silicone lacquers shall not be used.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00217	7.45 Ventilation: The air inside the electronics enclosure shall be ventilated with the use of a membrane.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00219	The membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00221	7.46 Forbidden components: BGA capsule in any form must not be used.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00222	Tantalum capacitors must not be used Serial resistors on power supply circuits must not be used.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	7 Electrical page 36 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 36
REQ-AUTO-00223	8.3 The clutch actuator shall withstand 6 500 000 actuations with the test cycle described in Appendix B.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00226	8.5 The ECA must be maintenance free over the whole life time.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00228	Spare parts or repair kits shall be defined together in agreement.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-LIFE-002	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00229	4.17) shall be provided as a spare part.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-LIFE-002	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00230	8.9 In a situation where the ECA has jammed, and is holding the clutch open, it shall be possible to remove the clutch force by following an instruction documented on the ECA drawing.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Backend and IT integration None	SSR-TOOL-001	-	8 Reliability page 38 Source details Document section 8 Reliability Section path 8 Reliability Page reference page 38
REQ-AUTO-00231	ID Recycling and environmental impact 9.1 The ECA shall fulfil the requirements stated in STD3868.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-003	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
REQ-AUTO-00233	The different parts of the housing shall be marked according to material content.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
REQ-AUTO-00234	The ECA shall be lead free.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
REQ-AUTO-00235	ID ADR Requirements 9.2 All included parts shall fulfil applicable sections of Part 9 in Annex B to the latest ADR ,as applicable at the time of type approval.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior OEM/Customer Review Interface	SSR-SYS-004	-	9 Environmental impact page 39 Source details Document section 9 Environmental impact Section path 9 Environmental impact Page reference page 39
REQ-AUTO-00237	P 1 Page 10 Environmental and electrical testing 10.1 The ECA must fulfil the general requirements for Electronic Control Units (ECUs), which are stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	10 Environmental and electrical testing page 40 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 40
REQ-AUTO-00238	10.2 The ECA must not be dependent on software for protection against requirements stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2).Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Application software behavior None	SSR-SYS-007	-	10 Environmental and electrical testing page 40 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 40
REQ-AUTO-00240	Memory functions shall remain Class A.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Hardware platform support None	SSR-HW-001	-	10 Environmental and electrical testing page 40 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 40
REQ-AUTO-00242	P 1 Page 10.4 For this unit, the following definitions of test procedure I and test procedure II shall be used: Test procedure I A comprehensive test where all functional requirements are verified.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	10 Environmental and electrical testing page 41 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 41
REQ-AUTO-00243	This test shall be performed before and after exposure.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	10 Environmental and electrical testing page 41 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 41
REQ-AUTO-00244	Test procedure I (See Figure 17 - Test procedure I) shall at least contain: - Full stroke to evaluate speed - Staircase to evaluate accuracy - Power loss to evaluate safety Figure 17 - Test procedure I Test procedure II A reduced function test where the fundamental requirements are verified.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	Application software behavior None	SSR-SYS-007	-	10 Environmental and electrical testing page 41 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 41
REQ-AUTO-00245	This test shall be possible to perform during exposure.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	10 Environmental and electrical testing page 41 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 41
REQ-AUTO-00248	tab headers) shall be made of self- extinguishing materials (i.e.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	10 Environmental and electrical testing page 44 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 44
REQ-AUTO-00251	P 1 Page 11 Functional safety The ECA is a part of a safety critical system and shall be handled as such.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	11 Functional safety page 49 Source details Document section 11 Functional safety Section path 11 Functional safety Page reference page 49
REQ-AUTO-00252	The ECA shall therefore be developed and implemented in accordance with the objectives and requirements of ISO 26262 "Road vehicles - Functional Safety".Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-009	-	11 Functional safety page 49 Source details Document section 11 Functional safety Section path 11 Functional safety Page reference page 49
REQ-AUTO-00254	For this purpose possible causes must be systematically identified.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	11 Functional safety page 49 Source details Document section 11 Functional safety Section path 11 Functional safety Page reference page 49
REQ-AUTO-00255	For these analyses at least the methods in ISO 26262 shall be applied.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-009	-	11 Functional safety page 49 Source details Document section 11 Functional safety Section path 11 Functional safety Page reference page 49
REQ-AUTO-00259	the suppler must carry out two full test rounds according to the Traton test requirements.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00265	A6 All prototypes and serial ECA’s shall fulfil requirements according to TB1822, IPC/EIA J-STD-001 class 3 and IPC-A-610 class 3.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	12 Quality conformance verification page 50 Source details Document section 12 Quality conformance verification Section path 12 Quality conformance verification Page reference page 50
REQ-AUTO-00268	All samples shall be functionally tested before sent to Traton.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	13 Sample maturity definition page 51 Source details Document section 13 Sample maturity definition Section path 13 Sample maturity definition Page reference page 51
REQ-AUTO-00269	Deviations shall be reported as a part of the sample delivery.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	13 Sample maturity definition page 51 Source details Document section 13 Sample maturity definition Section path 13 Sample maturity definition Page reference page 51
REQ-AUTO-00270	Dimensional checks shall be performed for B and C-samples prior to delivery to Traton.Proposal: Accept. Implement the ECA ECU behavior against the mapped feature/interface and verify through supplier test evidence, subject to customer-confirmed responsibility and acceptance criteria.	Accept	Proposal Ready	None	System behavior None	SSR-SYS-004	-	13 Sample maturity definition page 51 Source details Document section 13 Sample maturity definition Section path 13 Sample maturity definition Page reference page 51
Req.ID-Description-6.22.1	Req.ID Description 6.22.1 Wrong rotation direction 6.22.2 Short circuit / open load on the phases 6.22.3 Motor rotation feedback, short circuit / open loadProposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	6 SW functionality page 25 Source details Document section 6 SW functionality Section path 6 SW functionality Page reference page 25
REQ-AUTO-00190	7.17 Umax: - - 32/36/48 A Specific test relations TBD 7.18 Umin: 16 - - V CVS41 limits may go below this value.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	7 Electrical page 29 Source details Document section 7 Electrical Section path 7 Electrical Page reference page 29
REQ-AUTO-00246	Reduced versions of test procedure II may be agreed and used during various tests.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	10 Environmental and electrical testing page 41 Source details Document section 10 Environmental and electrical testing Section path 10 Environmental and electrical testing Page reference page 41
REQ-AUTO-00272	Unless otherwise stated, valid version is the latest available as of 1st May 2026.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	14 References page 52 Source details Document section 14 References Section path 14 References Page reference page 52
REQ-AUTO-00278	This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.Proposal: Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability.	Informational Only	Proposal Ready	None	None None	None	-	14 References page 61 Source details Document section 14 References Section path 14 References Page reference page 61

Derived Supplier System Requirements

This table is horizontally scrollable. Use the bottom scrollbar to view all columns.

SSR	Statement / Trace	Feature	Security Capability	Interface	Responsibility	Status	Verification
SSR-COM-002	External Interfaces — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for External Interfaces, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.From this PDF: REQ-AUTO-00066; REQ-AUTO-00078; REQ-AUTO-00138; REQ-AUTO-00139; REQ-AUTO-00141; REQ-AUTO-00143; REQ-AUTO-00145; REQ-AUTO-00177; REQ-AUTO-00193; REQ-AUTO-00195; REQ-AUTO-00196; REQ-AUTO-00199; REQ-AUTO-00200; REQ-AUTO-00201; REQ-AUTO-00202; REQ-AUTO-00204; REQ-AUTO-00206; REQ-AUTO-00212; REQ-AUTO-00239; REQ-AUTO-00273. This SSR is also supported by requirements from other PDFs.	External Interfaces	None	External Interfaces	Shared	Blocked by Customer Clarification	Review + Test
SSR-COM-003	Backend and IT integration — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Backend and IT integration, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.From this PDF: REQ-AUTO-00091; REQ-AUTO-00140; req-5.10. This SSR is also supported by requirements from other PDFs.	Backend and IT integration	None	None	Shared	Blocked by Customer Clarification	Review + Test
SSR-COM-004	Engineering tooling — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Engineering tooling, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.From this PDF: REQ-AUTO-00098.	Engineering tooling	None	None	Supplier-Owned	Candidate	Review + Test
SSR-COM-005	Hardware platform support — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Hardware platform support, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.From this PDF: REQ-AUTO-00099. This SSR is also supported by requirements from other PDFs.	Hardware platform support	None	None	Supplier-Owned	Candidate	Review + Test
SSR-CON-001	Cybersecurity requirement handling — Cybersecurity Concept and EvidenceThe supplier shall produce and maintain the cybersecurity concept and verification evidence covering Cybersecurity requirement handling.From this PDF: REQ-AUTO-00169. This SSR is also supported by requirements from other PDFs.	Cybersecurity requirement handling	Cybersecurity requirement handling	OEM/Customer Review Interface	Supplier-Owned	Candidate	Review + Test
SSR-DAI-002	System behavior — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of System behavior data and reject manipulated or unauthenticated data.From this PDF: REQ-AUTO-00089. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Review + Test
SSR-DIAG-001	System behavior — Diagnostic ServicesThe ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.From this PDF: REQ-AUTO-00173. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Shared	Blocked by Customer Clarification	Test
SSR-HW-001	Hardware platform support — Hardware / HSM / Secure StorageThe ECU hardware shall provide the platform and secure-storage capabilities required for Hardware platform support.From this PDF: REQ-AUTO-00065; REQ-AUTO-00113; REQ-AUTO-00182; REQ-AUTO-00184; REQ-AUTO-00187; REQ-AUTO-00227; REQ-AUTO-00240; Req.ID-Connector-Requirements-7.5. This SSR is also supported by requirements from other PDFs.	Hardware platform support	None	OEM/Customer Review Interface	Shared	Ready for Customer Alignment	Review + Test
SSR-LIFE-002	System behavior — Lifecycle / Field Return / DecommissioningThe ECU and supplier process shall handle lifecycle, field return and decommissioning for System behavior, including secure data and key handling.From this PDF: REQ-AUTO-00224; REQ-AUTO-00225; REQ-AUTO-00228; REQ-AUTO-00229. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Review + Test
SSR-RBAC-001	Diagnostic security — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Diagnostic security, restricting security-relevant diagnostic services per the OEM-agreed role model.From this PDF: req-6.20. This SSR is also supported by requirements from other PDFs.	Diagnostic security	Diagnostic security	OEM/Customer Review Interface	Shared	Blocked by Customer Clarification	Review + Test
SSR-SYS-001	System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067; REQ-AUTO-00068; REQ-AUTO-00069; REQ-AUTO-00070; REQ-AUTO-00071; REQ-AUTO-00072; REQ-AUTO-00073; REQ-AUTO-00074; REQ-AUTO-00075; REQ-AUTO-00076; REQ-AUTO-00079; REQ-AUTO-00080; REQ-AUTO-00082; REQ-AUTO-00083; REQ-AUTO-00084; REQ-AUTO-00085; REQ-AUTO-00086; REQ-AUTO-00087; REQ-AUTO-00088; REQ-AUTO-00092. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Test
SSR-SYS-002	System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00095; REQ-AUTO-00096; REQ-AUTO-00100; REQ-AUTO-00102; REQ-AUTO-00103; REQ-AUTO-00105; REQ-AUTO-00106; REQ-AUTO-00108; REQ-AUTO-00110; REQ-AUTO-00111; REQ-AUTO-00115; REQ-AUTO-00116; REQ-AUTO-00117; REQ-AUTO-00118; REQ-AUTO-00119; REQ-AUTO-00120; REQ-AUTO-00121; REQ-AUTO-00124; REQ-AUTO-00125; REQ-AUTO-00127; REQ-AUTO-00128; REQ-AUTO-00130; REQ-AUTO-00131; REQ-AUTO-00133; REQ-AUTO-00134; REQ-AUTO-00135; REQ-AUTO-00136; REQ-AUTO-00137; REQ-AUTO-00144; REQ-AUTO-00147; REQ-AUTO-00148; REQ-AUTO-00150; REQ-AUTO-00151; REQ-AUTO-00152; REQ-AUTO-00153; REQ-AUTO-00154; REQ-AUTO-00155; REQ-AUTO-00156; REQ-AUTO-00157; req-8.1.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Test
SSR-SYS-003	System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00158; REQ-AUTO-00159; REQ-AUTO-00160; REQ-AUTO-00161; REQ-AUTO-00162; REQ-AUTO-00163; REQ-AUTO-00164; REQ-AUTO-00165; REQ-AUTO-00167; REQ-AUTO-00168; REQ-AUTO-00174; REQ-AUTO-00176; REQ-AUTO-00179; REQ-AUTO-00181; REQ-AUTO-00183; REQ-AUTO-00186; REQ-AUTO-00188; REQ-AUTO-00189; REQ-AUTO-00191; REQ-AUTO-00194; REQ-AUTO-00197; REQ-AUTO-00198; REQ-AUTO-00205; REQ-AUTO-00207; REQ-AUTO-00208; REQ-AUTO-00209; REQ-AUTO-00211; REQ-AUTO-00213; REQ-AUTO-00215; REQ-AUTO-00216; REQ-AUTO-00217; REQ-AUTO-00218; REQ-AUTO-00220; REQ-AUTO-00221; REQ-AUTO-00222; REQ-AUTO-00223; REQ-AUTO-00226; REQ-AUTO-00231; REQ-AUTO-00232; Req.ID-Description-6.19.1.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Test
SSR-SYS-004	System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00233; REQ-AUTO-00234; REQ-AUTO-00235; REQ-AUTO-00236; REQ-AUTO-00237; REQ-AUTO-00241; REQ-AUTO-00242; REQ-AUTO-00243; REQ-AUTO-00245; REQ-AUTO-00248; REQ-AUTO-00251; REQ-AUTO-00254; REQ-AUTO-00257; REQ-AUTO-00259; REQ-AUTO-00260; REQ-AUTO-00261; REQ-AUTO-00262; REQ-AUTO-00263; REQ-AUTO-00264; REQ-AUTO-00265; REQ-AUTO-00267; REQ-AUTO-00268; REQ-AUTO-00269; REQ-AUTO-00270; REQ-AUTO-00271. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Test
SSR-SYS-007	Application software behavior — System FunctionThe ECU shall implement the Application software behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00129; REQ-AUTO-00178; REQ-AUTO-00180; REQ-AUTO-00238; REQ-AUTO-00244; REQ-AUTO-00266; REQ-AUTO-00277. This SSR is also supported by requirements from other PDFs.	Application software behavior	None	OEM/Customer Review Interface	Shared	Ready for Customer Alignment	Test
SSR-SYS-009	System behavior — System FunctionThe ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.From this PDF: REQ-AUTO-00210; REQ-AUTO-00214; REQ-AUTO-00252; REQ-AUTO-00253; REQ-AUTO-00255; req-5.1; req-5.1. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Supplier-Owned	Candidate	Test
SSR-TOOL-001	Backend and IT integration — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Backend and IT integration.From this PDF: REQ-AUTO-00081; REQ-AUTO-00090; REQ-AUTO-00101; REQ-AUTO-00104; REQ-AUTO-00112; REQ-AUTO-00114; REQ-AUTO-00132; REQ-AUTO-00192; REQ-AUTO-00219; REQ-AUTO-00230; REQ-AUTO-00247; req-6.4; req.10.5. This SSR is also supported by requirements from other PDFs.	Backend and IT integration	None	None	Shared	Ready for Customer Alignment	Review + Test
SSR-TOOL-004	Engineering tooling — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Engineering tooling.From this PDF: REQ-AUTO-00093; REQ-AUTO-00094.	Engineering tooling	None	None	Supplier-Owned	Candidate	Review + Test
SSR-UPD-001	System behavior — Software Update / FlashingThe ECU shall support secure software update/flashing for System behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence.From this PDF: REQ-AUTO-00203. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Shared	Blocked by Customer Clarification	Review + Test
SSR-VV-001	System behavior — Verification and ValidationThe supplier shall verify and validate System behavior per the agreed cybersecurity verification and validation plan.From this PDF: REQ-AUTO-00172; REQ-AUTO-00256; REQ-AUTO-00258. This SSR is also supported by requirements from other PDFs.	System behavior	None	OEM/Customer Review Interface	Shared	Blocked by Customer Clarification	Review + Test

System / Security Design Impact

Impact Area	Evidence From This PDF
Impacted system features	Application software behavior; Backend and IT integration; Cybersecurity requirement handling; Diagnostic security; Engineering tooling; External interfaces; Hardware platform support; System behavior; System behavior; Secure software update and flash readiness; System behavior; Security evidence and traceability
Impacted interfaces	External Interfaces; External Interfaces; OEM/Customer Review Interface; OEM/Customer Review Interface
Impacted security capabilities	Cybersecurity requirement handling; Diagnostic security
Impacted architecture elements	Application Software; Application Software; OEM/Customer Review Interface; Backend and IT Systems; Compliance Process; Compliance Process; OEM/Customer Review Interface; Compliance Process; System Core; Engineering Toolchain; External Interfaces; External Interfaces; OEM/Customer Review Interface; Hardware Platform; Security Services; System Core (showing 12 of 13)
Impacted work products	Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design
Tools / IT / hardware / test	Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/Medium; Medium/Low/Low; Medium/Low/Medium
Design assumptions introduced	Security-relevant requirement the ECU can own once responsibility/method is confirmed.
Design decisions required	Agree responsibility split (DIA) for the non-ECU portion.; Send linked open point to the customer for decision.

Estimation / Resource / Tooling Impact

Impact	Status
Estimation impact	yes
Resource/tool/IT/HW/test impact	Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/Medium; Medium/Low/Low; Medium/Low/Medium

Document Impact Diagram

Document Impact

Generated from document-specific requirement, traceability, SSR, and open-point evidence.

flowchart LR doc["3299216_1.pdf"] d0["Cybersecurity requirement handling"] doc --> d0 d1["Diagnostic security"] doc --> d1 f0["Feature: Application software behavior"] doc --> f0 f1["Feature: Backend and IT integration"] doc --> f1 f2["Feature: Cybersecurity requirement handling"] doc --> f2 i0["Interface: External Interfaces"] doc --> i0 i1["Interface: External Interfaces; OEM/Customer Review Interface"] doc --> i1 i2["Interface: OEM/Customer Review Interface"] doc --> i2 s0["SSR: SSR-COM-002"] doc --> s0 s1["SSR: SSR-COM-003"] doc --> s1 s2["SSR: SSR-COM-004"] doc --> s2 o0["Open point: OP-004"] doc --> o0 o1["Open point: OP-011"] doc --> o1

Mermaid source

flowchart LR
  doc["3299216_1.pdf"]
  d0["Cybersecurity requirement handling"]
  doc --> d0
  d1["Diagnostic security"]
  doc --> d1
  f0["Feature: Application software behavior"]
  doc --> f0
  f1["Feature: Backend and IT integration"]
  doc --> f1
  f2["Feature: Cybersecurity requirement handling"]
  doc --> f2
  i0["Interface: External Interfaces"]
  doc --> i0
  i1["Interface: External Interfaces; OEM/Customer Review Interface"]
  doc --> i1
  i2["Interface: OEM/Customer Review Interface"]
  doc --> i2
  s0["SSR: SSR-COM-002"]
  doc --> s0
  s1["SSR: SSR-COM-003"]
  doc --> s1
  s2["SSR: SSR-COM-004"]
  doc --> s2
  o0["Open point: OP-004"]
  doc --> o0
  o1["Open point: OP-011"]
  doc --> o1

Traceability

This table is horizontally scrollable. Use the bottom scrollbar to view all columns.

Customer Requirement	SSR	Disposition	Confidence	Reason
REQ-AUTO-00063	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00064	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00065	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00066	SSR-COM-002	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00067	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00068	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00069	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00070	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00071	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00072	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00073	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00074	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00075	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00076	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00077	None	Needs Internal Review	n/a	Low confidence / human review before derivation.
REQ-AUTO-00078	SSR-COM-002	Shared Responsibility / CIA Needed	Medium	Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC.
REQ-AUTO-00079	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00080	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00081	SSR-TOOL-001	Derive Supplier System Requirement	High	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00082	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00083	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00084	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00085	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00086	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00087	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00088	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00089	SSR-DAI-002	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00090	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00091	SSR-COM-003	Shared Responsibility / CIA Needed	Low	Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC.
REQ-AUTO-00092	SSR-SYS-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00093	SSR-TOOL-004	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00094	SSR-TOOL-004	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00095	SSR-SYS-002	Derive Supplier System Requirement	High	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00096	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
req.10.5	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00098	SSR-COM-004	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00099	SSR-COM-005	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00100	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00101	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00102	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00103	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00104	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00105	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00106	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
req-5.10	SSR-COM-003	Shared Responsibility / CIA Needed	Low	Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC.
REQ-AUTO-00108	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
req-6.4	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00110	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00111	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00112	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00113	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00114	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00115	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00116	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00117	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00118	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00119	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00120	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00121	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00122	None	Needs Internal Review	n/a	Low confidence / human review before derivation.
req-5.1	SSR-SYS-009	Derive Supplier System Requirement	High	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00124	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00125	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
req-8.1	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00127	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00128	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00129	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00130	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00131	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00132	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00133	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00134	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00135	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00136	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00137	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00138	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00139	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00140	SSR-COM-003	Shared Responsibility / CIA Needed	Low	Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC.
REQ-AUTO-00141	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
req-6.3	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00143	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00144	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00145	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00146	None	Blocked by Customer Clarification	n/a	Needs customer clarification before derivation.
REQ-AUTO-00147	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00148	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
req-6.20	SSR-RBAC-001	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00150	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00151	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00152	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00153	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00154	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00155	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00156	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00157	SSR-SYS-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00158	SSR-SYS-003	Derive Supplier System Requirement	High	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00159	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00160	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00161	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00162	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00163	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00164	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00165	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
Req.ID-Description-6.19.1	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00167	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00168	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00169	SSR-CON-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
Req.ID-Description-6.22.1	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00171	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00172	SSR-VV-001	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00173	SSR-DIAG-001	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00174	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00175	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00176	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00177	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00178	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00179	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00180	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00181	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00182	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00183	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00184	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
Req.ID-Connector-Requirements-7.5	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00186	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00187	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00188	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00189	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00190	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00191	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00192	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00193	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00194	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00195	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00196	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00197	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00198	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00199	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00200	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00201	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00202	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00203	SSR-UPD-001	Derive Supplier System Requirement	Medium	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00204	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00205	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00206	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00207	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00208	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00209	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00210	SSR-SYS-009	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00211	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00212	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00213	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00214	SSR-SYS-009	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00215	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00216	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00217	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00218	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00219	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00220	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00221	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00222	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00223	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00224	SSR-LIFE-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00225	SSR-LIFE-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00226	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00227	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00228	SSR-LIFE-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00229	SSR-LIFE-002	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00230	SSR-TOOL-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00231	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00232	SSR-SYS-003	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00233	SSR-SYS-004	Derive Supplier System Requirement	High	Accepted requirement; seed of its SSR cluster.
REQ-AUTO-00234	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00235	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00236	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00237	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00238	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00239	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00240	SSR-HW-001	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00241	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00242	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00243	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00244	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00245	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00246	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00247	SSR-TOOL-001	Shared Responsibility / CIA Needed	High	Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC.
REQ-AUTO-00248	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00249	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00250	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00251	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00252	SSR-SYS-009	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00253	SSR-SYS-009	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00254	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00255	SSR-SYS-009	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00256	SSR-VV-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00257	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00258	SSR-VV-001	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00259	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00260	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00261	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00262	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00263	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00264	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00265	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00266	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00267	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00268	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00269	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00270	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00271	SSR-SYS-004	Covered by Existing Supplier System Requirement	High	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00272	None	Informational Only	n/a	Non-binding; not derived.
REQ-AUTO-00273	SSR-COM-002	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
req-5.1	SSR-SYS-009	Duplicate / Merged	High	Duplicate of another requirement.
REQ-AUTO-00275	None	Needs Internal Review	n/a	Low confidence / human review before derivation.
REQ-AUTO-00276	None	Needs Internal Review	n/a	Low confidence / human review before derivation.
REQ-AUTO-00277	SSR-SYS-007	Covered by Existing Supplier System Requirement	Medium	Accepted requirement; covered by a clustered SSR.
REQ-AUTO-00278	None	Informational Only	n/a	Non-binding; not derived.

Detailed Evidence

Document intelligence markdown

3299216_1

Source PDF: customer-input/pdf/3299216_1.pdf
Converted Markdown: converted/markdown/3299216_1.md
Document type: Product Requirement
Domain: System Function
Confidence: High
Evidence basis: Markdown-derived requirements and generated RFQX registers; no downstream PDF analysis.

Executive Summary

Document Abstract

Field	Interpretation
Document Purpose	Confirmed by requirements: this product requirement contributes 216 Markdown-derived RFQ requirements with the strongest evidence in core eca system behavior.
Engineering Interpretation	Inferred from requirement pattern: for RFQX it affects the Electric Clutch Actuator ECU on the TRATON GW AMT platform by shaping core eca system behavior; system architecture design; system.
Supplier Proposal Impact	Confirmed by requirements: supplier positioning is 125 accept; 70 accept with assumption; 5 partially accept; 1 needs customer clarification; 5 needs internal review (showing 5 of 6). The generated traceability links this document to 20 supplier system requirement records.
System / Security Impact	Inferred from mapped features, capabilities, and interfaces: the main design/security impact is core eca system behavior; system architecture design; system. These themes should drive concept updates, verification evidence, and supplier proposal assumptions only where the linked requirements support them.
Customer Clarification Impact	Requires customer confirmation: 2 document-linked open point(s) remain, mainly: Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. Do not convert these items into agreed baseline scope until the customer confirms the decision.
Confidence and Limits	Confidence and limits: High confidence. Evidence is limited to Markdown-derived requirements, registers, open points, and SSR links; no downstream PDF analysis or AI-generated conclusion is claimed.

Main Requirement Themes

Theme	Summary	Requirement Count	Representative Requirements
Core ECA system behavior	Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope.	210	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00065
System architecture design	Groups related document requirements into a single engineering theme.	189	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00065
System	Groups related document requirements into a single engineering theme.	149	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067
System core	Groups related document requirements into a single engineering theme.	142	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067
Responsibility and customer approval model	Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk.	54	REQ-AUTO-00072; REQ-AUTO-00074; REQ-AUTO-00076
Cybersecurity concept and evidence	Drives cybersecurity concept, risk treatment, verification evidence, and traceability obligations.	32	REQ-AUTO-00076; REQ-AUTO-00081; REQ-AUTO-00090
Interface	Groups related document requirements into a single engineering theme.	22	REQ-AUTO-00066; REQ-AUTO-00078; REQ-AUTO-00138
Constraint	Groups related document requirements into a single engineering theme.	21	REQ-AUTO-00069; REQ-AUTO-00072; REQ-AUTO-00080

Document Content Structure

Section	Requirements	Critical	Open Points	SSR Links
1 Document overview	1	0	0	1
2 General	13	0	0	3
3 Position definition	1	0	0	0
4 Mechanical interface	29	2	1	9
5 Clutch engage and disengage	24	1	0	6
6 SW functionality	50	2	1	10
7 Electrical	42	0	0	6
8 Reliability	8	0	0	4
9 Environmental impact	6	0	0	2
10 Environmental and electrical testing	14	1	0	5
11 Functional safety	5	0	0	2
12 Quality conformance verification	11	0	0	3
13 Sample maturity definition	5	0	0	1
14 References	7	0	0	3

What this document does not confirm

Customer-owned responsibility, final customer decisions, and unresolved open points remain unconfirmed.

Critical Requirements

ID	Score	Category	Reason	Statement
REQ-AUTO-00146	95	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Needs Customer Clarification; linked open point; Unknown estimation impact; blocks SSR derivation	Message contents to be agreed with Traton 6.9 ECA identification number: The ECA shall report a unique ECA individual identification number 6.10 Supplier code: The ECA shall report supplier code 5 via CAN.
REQ-AUTO-00078	77	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Partially Accept; linked open point; High estimation impact	P 1 Page 4 Mechanical interface 4.1 The maximum release stroke is 22,4 mm from FCCP 4.2 The total stroke of the actuator shall be 85 mm.
REQ-AUTO-00091	48	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Partially Accept	Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand.
req-5.10	48	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Partially Accept	P 1 Page 5 Clutch engage and disengage 5.1 It shall be possible to disengage the clutch in 180ms (= Ts) with accuracy according to req 5.10,and max speed set to 125mm/s (see req 6.4) Time is measured according to Figure 7 – Max disengage time, where the dashed line is the position request as it becomes available on the CAN bus, and the full line is the actual PP.
REQ-AUTO-00140	48	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Partially Accept	If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit.
REQ-AUTO-00247	48	High risk due to unclear OEM/supplier responsibility	security relevant; architecture relevant; Partially Accept	P 1 Page 10.5.11 CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y 10.5.12 CVS40 §5.6 TC-06 Thermal shock Y 10.5.13 CVS40 §5.7 TC-07 Splash water test Y 10.5.14 CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y 10.5.15 CVS40 §5.9 TC-09 Leakage search test Y 10.5.16 CVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors.
REQ-AUTO-00116	44	General project impact	security relevant; architecture relevant; High estimation impact	The FCCP after a clutch engage shall be updated to 90% of the step within 0,2 s per mm that the FCCP have changed during the stroke.
req-6.20	44	High impact on diagnostic security	security relevant; architecture relevant; High estimation impact	6.13 Error State Diagnostic - ESD and Error State Action - ESA The ECA shall send a bit field via CAN containing errors present Additionally, see req 6.20, req 6.22 ,req.
REQ-AUTO-00164	44	General project impact	security relevant; architecture relevant; High estimation impact	The filter time shall equal the update frequency .
REQ-AUTO-00169	44	High impact on cybersecurity concept/work products	security relevant; architecture relevant; High estimation impact	6.21 Cyber Security: Cybersecurity shall be considered through a separate process with the latest Traton workflow in mind.

Open Points

Open Point	Priority	Question	Impact	Status
OP-004		Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.	Update-control scope and evidence ownership stay open; risk of an unprotected update path.	Open
OP-011		Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.	Supplier position, estimation, and affected design allocation remain conditional for the listed requirements.	Open

Supplier System Requirements

SSR	Title	Statement	Reqs From This PDF	Other PDFs	Status
SSR-COM-002	External Interfaces — Secure Communication and Boundary Control	The ECU shall restrict and protect communication for External Interfaces, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.	REQ-AUTO-00066; REQ-AUTO-00078; REQ-AUTO-00138; REQ-AUTO-00139; REQ-AUTO-00141; REQ-AUTO-00143; REQ-AUTO-00145; REQ-AUTO-00177; REQ-AUTO-00193; REQ-AUTO-00195; REQ-AUTO-00196; REQ-AUTO-00199; REQ-AUTO-00200; REQ-AUTO-00201; REQ-AUTO-00202; REQ-AUTO-00204; REQ-AUTO-00206; REQ-AUTO-00212; REQ-AUTO-00239; REQ-AUTO-00273	yes	Blocked by Customer Clarification
SSR-COM-003	Backend and IT integration — Secure Communication and Boundary Control	The ECU shall restrict and protect communication for Backend and IT integration, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.	REQ-AUTO-00091; REQ-AUTO-00140; req-5.10	yes	Blocked by Customer Clarification
SSR-COM-004	Engineering tooling — Secure Communication and Boundary Control	The ECU shall restrict and protect communication for Engineering tooling, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.	REQ-AUTO-00098	no	Candidate
SSR-COM-005	Hardware platform support — Secure Communication and Boundary Control	The ECU shall restrict and protect communication for Hardware platform support, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals.	REQ-AUTO-00099	yes	Candidate
SSR-CON-001	Cybersecurity requirement handling — Cybersecurity Concept and Evidence	The supplier shall produce and maintain the cybersecurity concept and verification evidence covering Cybersecurity requirement handling.	REQ-AUTO-00169	yes	Candidate
SSR-DAI-002	System behavior — Data Authenticity and Integrity Verification	The ECU shall verify the authenticity and integrity of System behavior data and reject manipulated or unauthenticated data.	REQ-AUTO-00089	yes	Candidate
SSR-DIAG-001	System behavior — Diagnostic Services	The ECU shall provide the diagnostic services for System behavior required by the allocated customer requirements, including the specified services, sessions and data identifiers.	REQ-AUTO-00173	yes	Blocked by Customer Clarification
SSR-HW-001	Hardware platform support — Hardware / HSM / Secure Storage	The ECU hardware shall provide the platform and secure-storage capabilities required for Hardware platform support.	REQ-AUTO-00065; REQ-AUTO-00113; REQ-AUTO-00182; REQ-AUTO-00184; REQ-AUTO-00187; REQ-AUTO-00227; REQ-AUTO-00240; Req.ID-Connector-Requirements-7.5	yes	Ready for Customer Alignment
SSR-LIFE-002	System behavior — Lifecycle / Field Return / Decommissioning	The ECU and supplier process shall handle lifecycle, field return and decommissioning for System behavior, including secure data and key handling.	REQ-AUTO-00224; REQ-AUTO-00225; REQ-AUTO-00228; REQ-AUTO-00229	yes	Candidate
SSR-RBAC-001	Diagnostic security — Secure Diagnostics / RBAC	The ECU shall enforce authenticated, role-authorised access for Diagnostic security, restricting security-relevant diagnostic services per the OEM-agreed role model.	req-6.20	yes	Blocked by Customer Clarification
SSR-SYS-001	System behavior — System Function	The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00063; REQ-AUTO-00064; REQ-AUTO-00067; REQ-AUTO-00068; REQ-AUTO-00069; REQ-AUTO-00070; REQ-AUTO-00071; REQ-AUTO-00072; REQ-AUTO-00073; REQ-AUTO-00074; REQ-AUTO-00075; REQ-AUTO-00076; REQ-AUTO-00079; REQ-AUTO-00080; REQ-AUTO-00082; REQ-AUTO-00083; REQ-AUTO-00084; REQ-AUTO-00085; REQ-AUTO-00086; REQ-AUTO-00087; REQ-AUTO-00088; REQ-AUTO-00092	yes	Candidate
SSR-SYS-002	System behavior — System Function	The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00095; REQ-AUTO-00096; REQ-AUTO-00100; REQ-AUTO-00102; REQ-AUTO-00103; REQ-AUTO-00105; REQ-AUTO-00106; REQ-AUTO-00108; REQ-AUTO-00110; REQ-AUTO-00111; REQ-AUTO-00115; REQ-AUTO-00116; REQ-AUTO-00117; REQ-AUTO-00118; REQ-AUTO-00119; REQ-AUTO-00120; REQ-AUTO-00121; REQ-AUTO-00124; REQ-AUTO-00125; REQ-AUTO-00127; REQ-AUTO-00128; REQ-AUTO-00130; REQ-AUTO-00131; REQ-AUTO-00133; REQ-AUTO-00134; REQ-AUTO-00135; REQ-AUTO-00136; REQ-AUTO-00137; REQ-AUTO-00144; REQ-AUTO-00147; REQ-AUTO-00148; REQ-AUTO-00150; REQ-AUTO-00151; REQ-AUTO-00152; REQ-AUTO-00153; REQ-AUTO-00154; REQ-AUTO-00155; REQ-AUTO-00156; REQ-AUTO-00157; req-8.1	no	Candidate
SSR-SYS-003	System behavior — System Function	The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00158; REQ-AUTO-00159; REQ-AUTO-00160; REQ-AUTO-00161; REQ-AUTO-00162; REQ-AUTO-00163; REQ-AUTO-00164; REQ-AUTO-00165; REQ-AUTO-00167; REQ-AUTO-00168; REQ-AUTO-00174; REQ-AUTO-00176; REQ-AUTO-00179; REQ-AUTO-00181; REQ-AUTO-00183; REQ-AUTO-00186; REQ-AUTO-00188; REQ-AUTO-00189; REQ-AUTO-00191; REQ-AUTO-00194; REQ-AUTO-00197; REQ-AUTO-00198; REQ-AUTO-00205; REQ-AUTO-00207; REQ-AUTO-00208; REQ-AUTO-00209; REQ-AUTO-00211; REQ-AUTO-00213; REQ-AUTO-00215; REQ-AUTO-00216; REQ-AUTO-00217; REQ-AUTO-00218; REQ-AUTO-00220; REQ-AUTO-00221; REQ-AUTO-00222; REQ-AUTO-00223; REQ-AUTO-00226; REQ-AUTO-00231; REQ-AUTO-00232; Req.ID-Description-6.19.1	no	Candidate
SSR-SYS-004	System behavior — System Function	The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00233; REQ-AUTO-00234; REQ-AUTO-00235; REQ-AUTO-00236; REQ-AUTO-00237; REQ-AUTO-00241; REQ-AUTO-00242; REQ-AUTO-00243; REQ-AUTO-00245; REQ-AUTO-00248; REQ-AUTO-00251; REQ-AUTO-00254; REQ-AUTO-00257; REQ-AUTO-00259; REQ-AUTO-00260; REQ-AUTO-00261; REQ-AUTO-00262; REQ-AUTO-00263; REQ-AUTO-00264; REQ-AUTO-00265; REQ-AUTO-00267; REQ-AUTO-00268; REQ-AUTO-00269; REQ-AUTO-00270; REQ-AUTO-00271	yes	Candidate
SSR-SYS-007	Application software behavior — System Function	The ECU shall implement the Application software behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00129; REQ-AUTO-00178; REQ-AUTO-00180; REQ-AUTO-00238; REQ-AUTO-00244; REQ-AUTO-00266; REQ-AUTO-00277	yes	Ready for Customer Alignment
SSR-SYS-009	System behavior — System Function	The ECU shall implement the System behavior behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing.	REQ-AUTO-00210; REQ-AUTO-00214; REQ-AUTO-00252; REQ-AUTO-00253; REQ-AUTO-00255; req-5.1; req-5.1	yes	Candidate
SSR-TOOL-001	Backend and IT integration — Tooling / IT / Evidence Storage	The supplier shall provide the tooling, IT infrastructure and evidence storage required for Backend and IT integration.	REQ-AUTO-00081; REQ-AUTO-00090; REQ-AUTO-00101; REQ-AUTO-00104; REQ-AUTO-00112; REQ-AUTO-00114; REQ-AUTO-00132; REQ-AUTO-00192; REQ-AUTO-00219; REQ-AUTO-00230; REQ-AUTO-00247; req-6.4; req.10.5	yes	Ready for Customer Alignment
SSR-TOOL-004	Engineering tooling — Tooling / IT / Evidence Storage	The supplier shall provide the tooling, IT infrastructure and evidence storage required for Engineering tooling.	REQ-AUTO-00093; REQ-AUTO-00094	no	Candidate
SSR-UPD-001	System behavior — Software Update / Flashing	The ECU shall support secure software update/flashing for System behavior, accepting only authenticated, integrity-verified software through the agreed programming sequence.	REQ-AUTO-00203	yes	Blocked by Customer Clarification
SSR-VV-001	System behavior — Verification and Validation	The supplier shall verify and validate System behavior per the agreed cybersecurity verification and validation plan.	REQ-AUTO-00172; REQ-AUTO-00256; REQ-AUTO-00258	yes	Blocked by Customer Clarification

Design Impact

Impacted System Features: Application software behavior; Backend and IT integration; Cybersecurity requirement handling; Diagnostic security; Engineering tooling; External interfaces; Hardware platform support; System behavior (showing 8 of 10)
Impacted Interfaces: External Interfaces; External Interfaces; OEM/Customer Review Interface; OEM/Customer Review Interface
Impacted Security Capabilities: Cybersecurity requirement handling; Diagnostic security
Impacted Architecture Elements: Application Software; Application Software; OEM/Customer Review Interface; Backend and IT Systems; Compliance Process; Compliance Process; OEM/Customer Review Interface; Compliance Process; System Core; Engineering Toolchain; External Interfaces (showing 8 of 13)
Impacted Work Products: Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design
Impacted Tools It Hardware Test: Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/Medium; Medium/Low/Low; Medium/Low/Medium
Impacted Supplier System Requirements: SSR-COM-002; SSR-COM-003; SSR-COM-004; SSR-COM-005; SSR-CON-001; SSR-DAI-002; SSR-DIAG-001; SSR-HW-001 (showing 8 of 20)
Design Assumptions Introduced: Security-relevant requirement the ECU can own once responsibility/method is confirmed.
Design Decisions Required: Agree responsibility split (DIA) for the non-ECU portion.; Send linked open point to the customer for decision.