Document Purpose
Scope: this product requirement specifies system architecture design, covering 1 Document overview; 2 General; 4 Mechanical interface; 5 Clutch engage and disengage; 6 SW functionality; 7 Electrical.
3299216_1
3299216_1.pdf · Product Requirement · System Function
Search
Last updated: 2026-06-29 11:50
RTRFQX Review TeamWorkspace
3299216_1
3299216_1.pdf · Product Requirement · System Function
What this document contains
Confirmed Requirements98customer ID + normative
Needs Clarification114no customer ID
Information82descriptive
Reference3definitions, scope
Critical125ranked impact
Open Points5linked
Tables / Diagrams0 / 25extracted
Derived SSRs17linked
Executive Takeaway
Systems-engineering read of what this document defines for the system - scope, boundaries, interfaces, obligations, and what is still open.
System Boundary & Interfaces
System boundary and interfaces: the document constrains 2 interface(s) - OEM/Customer Review Interface; External Interfaces; OEM/Customer Review Interface; principal functions in scope are Security evidence and traceability; Secure software update and flash readiness.
Design / Security Impact
Design and security impact: affects Security evidence and traceability; Secure software update and flash readiness; security capabilities touched: Diagnostic security; 17 supplier system requirement(s) were derived from this document.
Open For Customer
Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). (sample: 3 of 5) - plus 114 unidentified requirement-like statement(s). Do not baseline these until the customer confirms.
Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used.
Main Requirement Themes
| Theme | Engineering Meaning | Requirement Count | Representative Requirements |
|---|---|---|---|
| System architecture design | Groups related document requirements into a single engineering theme. | 276 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| System | Groups related document requirements into a single engineering theme. | 218 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 166 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| System core | Groups related document requirements into a single engineering theme. | 145 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0007 |
| Needs clarification | Groups related document requirements into a single engineering theme. | 114 | RFQX-3299216-1-0001; RFQX-3299216-1-0008; RFQX-3299216-1-0009 |
| Requirement | Groups related document requirements into a single engineering theme. | 98 | RFQX-3299216-1-0002; RFQX-3299216-1-0004; RFQX-3299216-1-0007 |
| Information | Groups related document requirements into a single engineering theme. | 82 | RFQX-3299216-1-0003; RFQX-3299216-1-0005; RFQX-3299216-1-0006 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 62 | RFQX-3299216-1-0012; RFQX-3299216-1-0017; RFQX-3299216-1-0018 |
Document Content Structure
| Section | Requirements | Information | Unknown / Review Needed | Total Items | Critical | Open Points | SSR Links |
|---|---|---|---|---|---|---|---|
| 1 Document overview | 0 | 0 | 0 | 1 | 1 | 1 | 0 |
| 2 General | 6 | 3 | 0 | 17 | 8 | 3 | 2 |
| 3 Position definition | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 4 Mechanical interface | 21 | 4 | 0 | 32 | 13 | 2 | 7 |
| 5 Clutch engage and disengage | 13 | 1 | 0 | 27 | 13 | 1 | 6 |
| 6 SW functionality | 34 | 9 | 0 | 63 | 22 | 2 | 10 |
| 7 Electrical | 11 | 9 | 0 | 54 | 35 | 2 | 4 |
| 8 Reliability | 4 | 1 | 0 | 10 | 5 | 1 | 3 |
| 9 Environmental impact | 2 | 0 | 0 | 6 | 4 | 1 | 1 |
| 10 Environmental and electrical testing | 5 | 54 | 0 | 66 | 7 | 1 | 2 |
| 11 Functional safety | 0 | 0 | 0 | 5 | 5 | 1 | 0 |
| 12 Quality conformance verification | 1 | 1 | 0 | 12 | 10 | 1 | 1 |
| 13 Sample maturity definition | 0 | 0 | 0 | 5 | 5 | 1 | 0 |
| 14 References | 1 | 0 | 0 | 9 | 2 | 2 | 0 |
Tables and Diagrams
Tables are reconstructed column-correct from the document text layer (no OCR). Diagrams are linked from converted image assets.
Tables0column-correct
Diagrams25image-linked
Linked Artifacts13requirement-linked
Diagrams (25)
DiagramFigure 1 - Position definition
Diagram source context
DiagramFigure 2 - Position relations
Diagram source context
DiagramFigure 3 - Pushrod positions
Diagram source context
DiagramFigure 4 – ISO view of 3d envelope. (all parts not shown)
Diagram source context
DiagramFigure 5 - Gearbox flange
Diagram source context
DiagramFigure 6 - Snap in tool space
Diagram source context
DiagramFigure 7 – Maximum disengage time
State-machine or transition behavior
DiagramFigure 8 - Maximum engage time
State-machine or transition behavior
DiagramFigure 9 - Step response.
Diagram source context
DiagramFigure 9 - Step response
Diagram source context
DiagramFigure 10 - Step response test cycle
Diagram source context
DiagramFigure 11 - Release frequency test
Diagram source context
DiagramFigure 12 - Class B exceptions
State-machine or transition behavior
DiagramFigure 133 A 3. Up to 100 kHz
Diagram source context
DiagramFigure 13 - Max current
Diagram source context
DiagramFigure 13 - Wake up signal hysteresis
Diagram source context
DiagramFigure 14 – Dual function block diagram
Diagram source context
DiagramFigure 15 - Reference circuit
Software update or memory programming context
DiagramFigure 16 - Temperature histogram
Diagram source context
DiagramFigure 17 - Test procedure I
Diagram source context
DiagramFigure 18 - Disengage force
Diagram source context
DiagramFigure 19 - Engage force
Diagram source context
DiagramFigure 20 - Test cycle
Diagram source context
DiagramFigure 21 – Release Load vs Strokes
Diagram source context
DiagramFigure 22 – Release Load vs Strokes
Diagram source context
What This PDF Is About
| Field | Value |
|---|---|
| Source PDF | 3299216_1.pdf |
| Document Type | Product Requirement |
| Domain | System Function |
| Scope Summary | 98 confirmed requirements, 114 needing clarification, 82 information, 3 reference items; 17 linked SSRs; 5 linked open points. |
| Main Themes | System architecture design; System; Core ECA system behavior; System core; Needs clarification (sample: 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. |
Critical Requirements
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| ID | Score | Category | Requirement / Reason | Supplier Position |
|---|---|---|---|---|
| RFQX-3299216-1-0064 | 95 | High risk due to unclear OEM/supplier responsibility | 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; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0132 | 95 | High risk due to unclear OEM/supplier responsibility | The filter time shall equal the update frequency .security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0176 | 95 | High risk due to unclear OEM/supplier responsibility | 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; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0009 | 81 | High risk due to unclear OEM/supplier responsibility | 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.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0011 | 81 | High risk due to unclear OEM/supplier responsibility | The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0015 | 81 | High risk due to unclear OEM/supplier responsibility | 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.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0017 | 81 | High risk due to unclear OEM/supplier responsibility | 2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0018 | 81 | High risk due to unclear OEM/supplier responsibility | 2.12 Traton requires: - Documentation of the product, i.e.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0038 | 81 | 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; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0091 | 81 | High risk due to unclear OEM/supplier responsibility | 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.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0092 | 81 | High risk due to unclear OEM/supplier responsibility | CAN communication shall still be active.security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
| RFQX-3299216-1-0093 | 81 | 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; Needs Customer Clarification; linked open point; blocks SSR derivation | Needs Customer Clarification |
Customer Clarifications / Open Points
Total Open Points5document-linked
P10priority
P20priority
Blocking Conceptyesyes / no
Blocking Estimationyesyes / no
Blocking SSRyesyes / no
Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).
OpenOpen
Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.
OpenOpen
Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy).
OpenOpen
Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.
OpenOpen
Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline.
OpenOpen
Open full open-point table (all fields)
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-001 | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).TARA scope and effort stay open; downstream assets, goals and design may rework. | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). | Proceed on the working ECA-ECU interpretation; flag every TARA-scope statement as assumption until confirmed. | OEM / Customer | Open | |
| 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-008 | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy).Hardware fusing and EOL process design stay open; risk of an exposed debug/production interface. | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). | Apply debug lock and secured production access; request the customer-confirmed production-security and EOL requirements. | Shared (OEM process / Supplier ECU) | Open | |
| OP-009 | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed.Without an agreed DIA the supplier risks owning customer work products or leaving cybersecurity gaps in the case. | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. | Deliver supplier-owned work products per concept; require a signed DIA/RASIC before treating shared items as supplier scope. | OEM / Customer + Supplier (DIA) | 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 |
Confirmed requirements (98)
Items carrying a customer requirement ID and a normative (shall/must) statement.
The ECA shall have a loop or similar feature where the cable can be fixated with a cable tie Optionally an M8 screw thread and rotation stop for a sheet metal bracket indicated in Figure 4 - ISO view of 3D envelope, can be provided. The loop or Scania assembled bracket shall be located close to the centre ( ± 20 mm) of the cable section between the connector and last cable fixation point on the gearbox Details & reviewer feedbackSection 4 Mechanical interface Page page 11 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
When the ECA is assembled, it shall not be possible to insert an object larger than Ø0,2 mm (A wire could be used as test object) between the ECA and gearbox flange, so that the object enters the space behind the ECA. The rubber grommet at the lower part of the flange can have the same interface as the surrounding aluminum flange. Details & reviewer feedbackSection 4 Mechanical interface Page page 9 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
It shall be possible to pull the pushrod 50 times with a force of 300 N without risk for it to come loose from the ECA. Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
The ECA shall provide a support for a clutch snap in tool on the marked surface in Figure 4 ISO view of 3D envelope. The maximum force is 1kN. Surface indents are allowed as long as it does not affect other requirements or the structural integrity of the ECA. Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
The hole shall be equipped with a cover possible to assemble and disassemble at least 50 times without tools. If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature. It shall still remain intac t and keep tightness after vibration testing (See req.10.5) Details & reviewer feedbackSection 4 Mechanical interface Page page 11 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
When the cover is assembled it shall not be possible to insert an object larger than Ø0,2 mm into the gearbox housing between the cover and ECA. A wire could be used as test object. Figure 6 - Snap in tool space Details & reviewer feedbackSection 4 Mechanical interface Page page 11 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
The ECA will be controlled by messages on the CAN bus and by the PWM signal specified in req. 7.24-7.33. The CAN communication messages are specified in PD2497100 (Ref 14.14). It shall be followed to its full extent. If needed, some messages might be complemented with additional checksums and message counters Details & reviewer feedbackSection 6 SW functionality Page page 20 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
Maximum speed A maximum allowed speed of the actuator is sent as a separate signal on CAN. If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit. Details & reviewer feedbackSection 6 SW functionality Page page 22 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
Ventilation The air inside the electronics enclosure shall be ventilated with the use of a membrane. 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. The membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water. The design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane. Details & reviewer feedbackSection 7 Electrical Page page 36 Supplier proposal Partially accept. Supplier can implement the ECU-side behaviour, but OEM-owned backend/PKI/fleet responsibilities require customer confirmation. |
No update of the FCCP is allowed The value shall be frozen at the last identified position and used for RPC. Self-adjustment disabled 0x3 Details & reviewer feedbackSection 6 SW functionality Page page 22 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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 , Details & reviewer feedbackSection 6 SW functionality Page page 23 Security capability Diagnostic security Supplier 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. |
Current feedback The ECA shall report the current for each phase of the actuator. These values shall be calculated using a moving mean filter. The filter time shall equal the update frequency . (Ref 14.14) Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Cyber Security Cybersecurity shall be considered through a separate process with the latest Traton workflow in mind. The following apply: Mandatory: TRATON secure updates - CVS31,CVS32,CVS123-2,CVS154 TRATON secure diagnostics - CVS31,CVS32,CVS151 TRATON Specification on Unified diagnostic Services CVS124 Other applicable documents considered as supporting specifications: CVS30, CVS33, CVS34,CVS121,CVS122,SecureBoot,Vehicle Baseline Requirements, ECU Baseline Requirements Additional standards/documents will be made available, if applicable. Details & reviewer feedbackSection 6 SW functionality Page page 25 Security capability Diagnostic security Supplier 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. |
and 5.2. Details & reviewer feedbackSection The full strokes should be performed within 180 ms, as specified in Page page 57 Supplier proposal Needs internal review. Confirm whether this should-level requirement is in the committed baseline. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 2
|
The ECA units shall be manufactured with marking variants according to the requirements in Scania STD19 (Ref 14.17). The variant type shall be based on delivery agreement and Brand involved. Variant 1: For Scania units, wordmark variant C1 Part number (7 digits). Variant 2: For MAN units, wordmark variant Z1. Part number (13 digits). Variant 3: For International units, wordmark variant X1. Part number (8 digits) Variant 4 Tentik wordmark variant W. Part number (9 digits, two spaces in format: 12 345 6789). 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. The marking shall not be visible when the ECA is mounted on a gearbox. The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. Details & reviewer feedbackSection 2 General Page page 4 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The rubber cover (See req. 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. Date dial: CVM. 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 Details & reviewer feedbackSection 2 General Page page 5 Supplier 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. |
The ECA shall be adapted for 6 pcs M8 flange screws described by Scania STD4435 Details & reviewer feedbackSection 4 Mechanical interface Page page 9 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA shall be able to be held by the guide pins only while being exposed to the max clutch load, (req. 4.22) up to 50 times. The clutch load will be removed and the screw interface tightened between every load occasion. Surface indents in the contacts are allowed as long as the structural integrity is unaffected Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA shall allow space for external tools according to the cylinders in the 3D envelope attached. Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA shall have a window where the volume shown in Figure 6 – Snap in tool space, could pass through(See req. 4.4). Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The connector for communication and power shall be positioned as indicated in Figure 4 ISO view of 3D envelope, when connected. Details regarding actual length and positioning tolerances shall be agreed in design phase. Details & reviewer feedbackSection 4 Mechanical interface Page page 11 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
For each stroke that the actuator performs it shall adjust to the current wear of the clutch. 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. 5.10. The implementation can be either a pure mechanical solution or it can be implemented using a software based solution. Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Description Mode Name Enom When requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP). The RP can in this mode correspond to the full wear travel of the clutch (see req. 4.3) It is allowed to control movement to protect the ECA and clutch from hardware damage. Specific cases shall be approved with Traton. Control mode Absolute position 0x01 Details & reviewer feedbackSection 6 SW functionality Page page 21 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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). The RP can be up to a full Release Travel (22,4 mm) in this mode. How the FCCP can be identified is described in 6.5. When RP = 0 the actuator is allowed to have a position that is less than the FCCP but not more, since this would open the clutch. Control mode Relative position 0x02 Details & reviewer feedbackSection 6 SW functionality Page page 21 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Supplier code The ECA shall report supplier code 5 via CAN. Details & reviewer feedbackSection 6 SW functionality Page page 23 Feature / Interface None / External Interfaces; OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
SW number The ECA shall report a complete SW version number. The number is decided by the supplier and can be in the range 0-64255. Details & reviewer feedbackSection 6 SW functionality Page page 23 Feature / Interface None / External Interfaces; OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
HW number The ECA shall report a complete HW version number. The number is decided by the supplier and can be in the range 0-64255. Details & reviewer feedbackSection 6 SW functionality Page page 23 Feature / Interface None / External Interfaces; OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Debug / Test This value shall be sent when the actuator is in debug or test control state. 0xC Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Diagnosis CVS120 shall be applied (Ref 14.12). Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
Validation and Invalidation The reported ESD must be able to be validated and invalidated. Details & reviewer feedbackSection 6 SW functionality Page page 27 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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. One unique DTC will be set per bit in the ESD signal. If higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally. Internally stored parameters may be accessible only using supplier defined tools . Details & reviewer feedbackSection 6 SW functionality Page page 27 Feature / Interface None / External Interfaces; OEM/Customer Review Interface Supplier 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. |
Data logging Any data logged or stored shall be agreed upon together with Traton. Details & reviewer feedbackSection 6 SW functionality Page page 27 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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. 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. This could be designed with for example data mirroring. It is acceptable if purely statistical data (e.g. operation hours) from the active operation cycle is not stored in case of an abnormal shutdown. Details & reviewer feedbackSection 6 SW functionality Page page 27 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
Reset It shall be possible to reset the ECA application with a power off/on cycle after all functional safety events. Handling to be agreed with Traton. Details & reviewer feedbackSection 6 SW functionality Page page 27 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
A safe boot sequence must be set to prevent unwanted or undefined behavior during or after loss of power, or corruption of stored data. Details & reviewer feedbackSection 7 Electrical Page page 28 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA can be connected to the battery+ (30) permanently through the system fuse or through a master switch that physically cuts off power. All power used by the ECA shall be taken from this battery connection. Details & reviewer feedbackSection 7 Electrical Page page 29 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA has one CAN bus. Any watchdog circuit shall have no influence on the CAN bus The CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter. Details & reviewer feedbackSection 7 Electrical Page page 34 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The controller and transceiver shall be CAN FD ready Parameter Limit values Unit Remarks Min. Typ. Max. Details & reviewer feedbackSection 7 Electrical Page page 34 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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. Details & reviewer feedbackSection 7 Electrical Page page 35 Feature / Interface None / External Interfaces; OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
CAN_Shield CAN shield. Footprint prepared for internal connection to system ground 31_ECA via a resistor and a capacitor in series. The components shall not be populated by default. The CAN front end shall be designed to comply with TB1905. (Ref 14.3) Details & reviewer feedbackSection 7 Electrical Page page 35 Feature / Interface None / External Interfaces Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
The ECA shall fulfil the requirements stated in STD3868 STD3868 is a comprehensive document referring to several underlying standards. 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. STD4159, Chemical substances with limited use – Scania Grey list. CVS 83, Material declaration according to Scania IMDS reporting std. The different parts of the housing shall be marked according to material content. The ECA shall be lead free. Details & reviewer feedbackSection 9 Environmental impact Page page 39 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
CVS40 §5.10 TC-10 Ingress protection The ECA shall also fulfil IP54 without mounted connectors. IP classes to test: IP6K6K, IP6K7, and IP6K9K Y Details & reviewer feedbackSection 10 Environmental and electrical testing Page page 43 Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
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. Details & reviewer feedbackSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface Supplier proposal Accept. Implement as part of the cybersecurity concept and map to verification evidence, assuming the customer confirms responsibility allocation and method. |
) 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. Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 13 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 2
|
). Details & reviewer feedbackSection The signal is valid during Control Modes RPC and TC(see Page page 22 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
The clutch actuator shall be electrically driven Details & reviewer feedbackSection 2 General Page page 4 Supplier 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. |
The ECA (Electric Clutch Actuator) must have its own internal ECU for manoeuvring and error handling. Details & reviewer feedbackSection 2 General Page page 4 Supplier 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. |
The ECA shall be designed with Remanufacturing and/or Refurbishment in mind with possibility of swapping out larger electronic assemblies/components. Details to be agreed with Traton Details & reviewer feedbackSection 2 General Page page 5 Supplier 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. |
The mechanics shall also be tested and verified, in an overall durability test as stated in Appendix B etc. Details & reviewer feedbackSection 2 General Page page 5 Supplier 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. |
The total stroke of the actuator shall be 85 mm Details & reviewer feedbackSection 4 Mechanical interface Page page 8 Supplier 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. |
The clutch actuator shall be able to reach the extreme positions A and B in with the center of the pushrod end. Dimensions measured on the ECA. See Figure 3 - Pushrod positions. Figure 3 - Pushrod positions Details & reviewer feedbackSection 4 Mechanical interface Page page 8 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
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. The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm. Details & reviewer feedbackSection 4 Mechanical interface Page page 9 Supplier 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. |
P 1 Page 4.4 ECA shall not interfere with any geometry in the 3D envelope -1 1_RFQ2030.stp except where interference fits or other types of functional contacts are required. Details & reviewer feedbackSection 4 Mechanical interface Page page 9 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
The ECA shall be adapted for 2 pcs 10 mm guide pins Figure 5 - Gearbox flange Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
The guide pin holes in the ECA shall be Ø 10,1±0.05 mm and at least 12 mm deep. The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing. Both depths measured from the center of the oval hole in the Gearbox/ECA flange. Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier 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. |
The pushrod end that makes contact with the clutch lever shall be a Ø15,93±0,07 mm steel sphere. Details & reviewer feedbackSection 4 Mechanical interface Page page 10 Supplier 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. |
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. Details & reviewer feedbackSection 4 Mechanical interface Page page 11 Supplier 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. |
The actuator shall apply a preload force for the release bearing. The preload force measured on the push rod shall be 150N to 250N independent of the clutch position Details & reviewer feedbackSection 4 Mechanical interface Page page 12 Supplier 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. |
It must be possible to assemble the actuator independent of the lever position without any power connection. This means that the push rod shall be possible to move by hand. Maximum force allowed is 300N. Details & reviewer feedbackSection 4 Mechanical interface Page page 12 Supplier 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. |
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 ,and max speed set to 125mm/s (see Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 13 Supplier 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. |
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 ). Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 14 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 2
|
The clutch actuator shall report the absolute position of the current actuator stroke (AP) (Ref 14.14). Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier 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. |
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. 6.5). Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier 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. |
The clutch actuator shall be equipped with a displacement sensor measuring the movement of the push rod, (Ref 14.14) Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier 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. |
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. Resolution (smallest discernible unit of change along the X axis): 0.0125mm. Repeatability (maximum variation between measurements at the same position and in the same unit, with equal environmental conditions): +/- 0.1mm. Range: 85mm (AP) Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier 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. |
The maximum stationary position error relative to real FCCP (i e self-adjustment error + step response error) shall be ±0.15mm. Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 15 Supplier 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. |
Maximum overshoot is 0.2 mm When a new position is requested, but the stroke is too short to reach requested speed, the ECA shall complete the stroke in minimum time with dynamic in compliance with the , 5.2 and this section. Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 16 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 2
|
Req. 5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle. Step from FCCP to 0.5x fully open position Wait 2 seconds Step to fully open position Wait 2 seconds Step to 0.5x fully open position Wait 2 seconds Step to FCCP Figure 10 - Step response test cycle Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 17 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
The test shall be done with the highest operating temperature (see ) and maximum clutch force (See Appendix A) Figure 11 - Release frequency test Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 18 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
It shall be possible to keep the clutch disengaged continuously without risk of loss of function for 120 min. This shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req. 8.1). Details & reviewer feedbackSection 5 Clutch engage and disengage Page page 19 Supplier 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. |
ECA identification number The ECA shall report a unique ECA individual identification number Details & reviewer feedbackSection 6 SW functionality Page page 23 Supplier 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. |
System state The ECA shall report its current System State. Valid states are explained in requirements 6.14.1 - 6.14.9. Details & reviewer feedbackSection 6 SW functionality Page page 23 Supplier 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. |
Absolute Position Control This value shall be sent when the ECA is actuating Absolute Position Control. 0x1 Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
Relative Position Control This value shall be sent when the ECA is actuating Relative Position Control. 0x2 Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
Torque Control This value shall be sent when the ECA is actuating Torque Control. The torque being controlled is the torque of the motor. 0x4 Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
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. passing FCCP). 0x5 Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
Initializing This value shall be sent when the ECA is performing its initiation routine and is not yet available for control. 0xA Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
Motor Brake Simulation This value shall be sent when the actuator is performing a motor brake simulation. 0xD Details & reviewer feedbackSection 6 SW functionality Page page 24 Supplier 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. |
System Temperature The ECA shall report the current system temperature.(Ref 14.14) Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
Torque Feedback The ECA shall calculate and report the actuator motor torque. (Ref 14.14) Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
Supply Voltage Feedback The ECA shall report the current system voltage. (input voltage) (Ref 14.14) Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
Operational hours The ECA shall store and report its accumulated operational hours. Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
Total travelled length The ECA shall report its accumulated lifetime travel length. Details & reviewer feedbackSection 6 SW functionality Page page 25 Supplier 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. |
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. Details & reviewer feedbackSection 6 SW functionality Page page 27 Supplier 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. |
The electrical design must ensure that an internal short circuit through one of H -bridges (“shoot through”) is avoided. Details & reviewer feedbackSection 7 Electrical Page page 28 Supplier 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. |
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. Relates to Safety Goals set in PD3339794 (Ref 14.16). Details & reviewer feedbackSection 7 Electrical Page page 28 Supplier 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. |
All external electrical connectors shall be geometrically coded. If internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded. Details & reviewer feedbackSection 7 Electrical Page page 28 Supplier 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. |
The ECA is connected directly to the battery GND (31). This ground connection will act as system ground and reference for the entire ECA. The ground shall not be DC connected to the ECA housing. Requirements Power cable dimension: Operating parameters Remark Min Typ. Max. Unit Details & reviewer feedbackSection 7 Electrical Page page 29 Supplier 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. |
The clutch actuator shall withstand 6 500 000 actuations with the test cycle described in Appendix B. Details & reviewer feedbackSection 8 Reliability Page page 38 Supplier 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. |
The ECA must be maintenance free over the whole life time Details & reviewer feedbackSection 8 Reliability Page page 38 Supplier 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. |
The maintenance window cover (See req. 4.17) shall be provided as a spare part Details & reviewer feedbackSection 8 Reliability Page page 38 Supplier 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. |
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. It is allowed to destroy the ECA in the process. Details & reviewer feedbackSection 8 Reliability Page page 38 Supplier 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. |
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. For type approval, the vehicle and its components shall comply with ECE Regulation No. 105 and with European Directive 2008/68/EC, as amended. Details & reviewer feedbackSection 9 Environmental impact Page page 39 Feature / Interface None / OEM/Customer Review Interface Supplier 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. |
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). Details & reviewer feedbackSection 10 Environmental and electrical testing Page page 40 Supplier 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. |
The ECA must not be dependent on software for protection against requirements stated in CVS40 (Ref 14.1) and CVS41 (Ref 14.2). Details & reviewer feedbackSection 10 Environmental and electrical testing Page page 40 Supplier 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. |
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. This test shall be performed before and after exposure. 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. This test shall be possible to perform during exposure. Reduced versions of test procedure II may be agreed and used during various tests. Alternative 1: Test cycle according to Appendix B, frequency 10 to 30 strokes per minute. Alternative 2: Release frequency test according to req. 5.12. Details & reviewer feedbackSection 10 Environmental and electrical testing Page page 41 Supplier 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. Related source tables/diagrams are treated as interpretation context, not separate customer IDs. Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
CVS40 §8.1 TS-01 Flammability In order to fulfil flammability demands, any plastic materials (i.e. tab headers) shall be made of self- extinguishing materials (i.e. UL94). Y Details & reviewer feedbackSection 10 Environmental and electrical testing Page page 44 Supplier 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. |
,req. Details & reviewer feedbackSection 6 SW functionality Page page 23 Supplier proposal Informational only. Keep as context; do not treat as an implementation requirement unless the customer confirms applicability. |
Needs customer clarification (114)
Reads like a requirement but no customer requirement ID was identified in the source. Confirm with the customer before baselining — not counted as a confirmed requirement.
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 15 |
The filter time shall equal the update frequency . Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 25 |
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. Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied. DetailsSection 7 Electrical Page page 34 Feature / Interface Secure software update and flash readiness / None |
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. Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). DetailsSection 2 General Page page 4 |
The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). DetailsSection 2 General Page page 4 |
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. Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). DetailsSection 2 General Page page 5 |
2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 2 General Page page 5 Feature / Interface None / OEM/Customer Review Interface |
2.12 Traton requires: - Documentation of the product, i.e. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 2 General Page page 5 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface |
Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 10 |
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. Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). DetailsSection 6 SW functionality Page page 22 Feature / Interface None / External Interfaces |
CAN communication shall still be active. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 22 Feature / Interface None / External Interfaces |
If the actuator can move faster than this value it shall be controlled in a such way that it does not exceed this limit. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 22 |
6.5 Self-adjustment The self-adjustment signal defines the restrictions of how the FCCP shall be identified. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 22 Feature / Interface None / External Interfaces |
The value of the FCCP shall be reported via CAN(Ref 14.14) Req. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 22 Feature / Interface None / External Interfaces |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 23 Feature / Interface None / External Interfaces |
ESA definition( Ref 14.16) The supplier shall provide documentation for the ESD bits and related faults . Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 23 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface |
6.14.1 Boot Mode If the actuator is in boot mode, 0x00 shall be reported as active state. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 24 |
If higher resolution is required for the supplier to properly troubleshoot any individual occurrence, then the ECA is responsible for storing these parameters internally. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 27 Feature / Interface None / OEM/Customer Review Interface |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 27 Feature / Interface None / OEM/Customer Review Interface |
The Wake-up signal shall also be connected to a digital input on the µP. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 Feature / Interface None / External Interfaces |
Special precautions shall be taken to prevent direct connection between Wake-up and 30 in case of a single failure. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 Feature / Interface None / External Interfaces |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 Feature / Interface None / External Interfaces |
If a signal for disengaging the clutch is received the ECA shall actuate the request regardless of CAN-request. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 33 Feature / Interface None / External Interfaces |
Any watchdog circuit shall have no influence on the CAN bus. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 34 Feature / Interface None / External Interfaces |
The CAN front end shall be designed to comply with TB1905 (Ref 14.3), with the following additional information in this chapter. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 34 Feature / Interface None / External Interfaces |
The CAN front end shall be designed to comply with TB1905. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 35 Feature / Interface None / External Interfaces |
The melting point of the soldering material and the composition of the soldering material shall be declared by supplier. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 Feature / Interface None / OEM/Customer Review Interface |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 Feature / Interface None / External Interfaces |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
The design shall be made to prevent accumulation of water on top of the membrane, or in the cavity of the membrane. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
8.4 Six consecutive units shall run past 6.5M actuations at the supplier, and continue to end of life. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 8 Reliability Page page 38 Feature / Interface None / OEM/Customer Review Interface |
Three consecutive units shall run past 6.5M actuations at Scania, and continue to end of life. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 8 Reliability Page page 38 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 9 Environmental impact Page page 39 |
CAN communication shall not be affected. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 40 Feature / Interface None / External Interfaces |
Accepted behaviour in this case shall be agreed upon between Traton and Supplier. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 40 Feature / Interface None / OEM/Customer Review Interface |
The supplier shall analyse risks of individua l HW and SW components, mechanics, and any other technologies, independently of the scope of ISO 26262. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 11 Functional safety Page page 49 Feature / Interface None / OEM/Customer Review Interface |
ID Verification methods 12.1 Conformance to Requirement Specification A1 The supplier must do conformance test of all external and internal I/O. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface |
This test must verify that all internal and external I/O fulfils the requirements in this specification. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface Security evidence and traceability / OEM/Customer Review Interface |
Additional tests initiated and performed by the supplier must be discussed with Traton. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface |
A3 The supplier must test the connectors according to TB1787. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface |
A4 The supplier must do EMC tests with the unit alone. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface |
The supplier must certify the ECA according to UN ECE R10 (EMC), according to the latest revision with all amendments. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface |
A5 The supplier must check that both prototypes and serial units fulfil the dimension requirement according to any relevant Traton supplied drawings. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 Feature / Interface None / OEM/Customer Review Interface |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 1 Document overview Page page 3 |
The variant type shall be based on delivery agreement and Brand involved. Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). DetailsSection 2 General Page page 4 |
The marking shall not be visible when the ECA is mounted on a gearbox. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 2 General Page page 4 |
Details to be agreed with Traton 2.9 Traton shall be invited to participate in electrical and mechanical design reviews. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 2 General Page page 5 |
The surface roughness of the ECA opposite to surface B shall be equal or finer than Ra 3,2 µm. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 9 |
The holes shall also block the guide pin from protruding more than 14 mm from the gearbox housing. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 10 |
If an interference fit is chosen, the maximum force to assemble/disassemble shall be 50 N in room temperature. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 11 |
Details regarding actual length and positioning tolerances shall be agreed in design phase. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 11 |
This means that the push rod shall be possible to move by hand. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 12 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 4 Mechanical interface Page page 12 |
This shall be measured against the maximum disengage force (See Appendix A) Figure 7 – Maximum disengage time Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 13 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
This shall be measured against the minimum engage force (See Appendix A) Figure 8 - Maximum engage time Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 14 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 15 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 16 |
The actuator shall move the pushrod at the highest possible speed, limited only by its maximum achievable speed and the maximum speed request. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 16 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 16 |
Dynamics end of movement: The requested speed shall be kept until 2 mm from the target position. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 16 |
5.10 shall be tested with a step response test cycle, according to description and Figure 10 - Step response test cycle. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 17 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 18 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
Between 16V and loss of power the ECA shall hold its current position or move towards requested position without any time requirement. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 19 |
The strategy shall be disc ussed and approved with Traton. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 19 |
This shall be measured against the maximum disengage force (Appendix A) and an highest operating temperature (see req. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 5 Clutch engage and disengage Page page 19 |
P 1 Page 6 SW functionality 6.1 TB4684 shall be applied. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 20 |
It shall be followed to its full extent. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 20 |
When requesting Absolute Position Control the actuator shall move to the actuator position defined by the Requested Position (RP). Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 21 |
Specific cases shall be approved with Traton. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 21 |
Control mode Relative position 0x02 6.3.3 When requesting Torque Control (TC) the actuator shall actuate the requested motor torque. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 21 |
6.3.4 When requesting Test Mode, the actuator shall perform tests to detect latent faults. Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). DetailsSection 6 SW functionality Page page 22 |
The value shall be frozen at the last identified position and used for RPC. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 22 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 24 |
These values shall be calculated using a moving mean filter. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 6 SW functionality Page page 25 |
7.2 Short circuit protection shall be implemented by hardware. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 28 |
If internal components are included in repair kits, the internal electrical connectors shall also be geometrically coded. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 28 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 28 |
All power used by the ECA shall be taken from this battery connection. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 29 |
The ground shall not be DC connected to the ECA housing. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 29 |
7.23 Quiescent current: According to CVS41 (Ref 14.2), must be met independent of input and output conditions. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 30 |
It shall be used to control the power up sequence to the µP. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 |
Redundancies due improper shutdown shall be aligned with Traton. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 31 |
The components shall not be populated by default. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 35 |
The quality of the wire bonding and position shall be properly analyzed. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
The material shall be lead free and of ”high temperatures solder type”. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
The PCB must be supported and must not bent in any direction during the process. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
Conformal coating or lacquer shall cover the entire PCB and all solder joints. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
shall be specified in the initial offer. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
The conformal coating process and materials shall apply to the latest versions of IPC/EIA J-STD-001 (with applicable standards as e.g. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
Water based and silicone lacquers shall not be used. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
The membrane shall be placed so that it is protected against blunt force, falling dust and dripping salt-water. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
7.46 Forbidden components: BGA capsule in any form must not be used. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
Tantalum capacitors must not be used Serial resistors on power supply circuits must not be used. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 7 Electrical Page page 36 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 8 Reliability Page page 38 |
Spare parts or repair kits shall be defined together in agreement. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 8 Reliability Page page 38 |
4.17) shall be provided as a spare part. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 8 Reliability Page page 38 |
The different parts of the housing shall be marked according to material content. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 9 Environmental impact Page page 39 |
The ECA shall be lead free. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 9 Environmental impact Page page 39 |
For type approval, the vehicle and its components shall comply with ECE Regulation No. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 9 Environmental impact Page page 39 Feature / Interface None / OEM/Customer Review Interface |
Memory functions shall remain Class A. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 40 |
This test shall be performed before and after exposure. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 41 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 41 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
This test shall be possible to perform during exposure. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 41 |
tab headers) shall be made of self- extinguishing materials (i.e. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 10 Environmental and electrical testing Page page 44 |
P 1 Page 11 Functional safety The ECA is a part of a safety critical system and shall be handled as such. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 11 Functional safety Page page 49 |
The ECA shall therefore be developed and implemented in accordance with the objectives and requirements of ISO 26262 "Road vehicles - Functional Safety". Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 11 Functional safety Page page 49 |
For this purpose possible causes must be systematically identified. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 11 Functional safety Page page 49 |
For these analyses at least the methods in ISO 26262 shall be applied. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 11 Functional safety Page page 49 |
the suppler must carry out two full test rounds according to the Traton test requirements. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 |
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. Confirm whether each listed requirement is binding supplier scope, customer-owned scope, or evidence-only context for the ECA ECU baseline. DetailsSection 12 Quality conformance verification Page page 50 |
Information / descriptive (82)
Descriptive or contextual statements with a customer ID but no binding (shall/must) wording.
Minimum diagnostic feedback Minimum diagnostic feedback described in req. 6.22.1 - 6.22.11. DetailsSection 6 SW functionality Page page 25 |
100ms after reaching 2 mm from target, the maximum position error should be ±0.1mm. DetailsSection 5 Clutch engage and disengage Page page 16 |
The actuator will be controlled by a position and speed demand by CAN-bus DetailsSection 2 General Page page 4 |
The actuator will be controlled by a position and speed demand by a 1kHz PWM signal on wake up connection DetailsSection 2 General Page page 4 |
The gearbox flange designated to the ECA has three different surfaces, see Figure 5 Gearbox flange. Surface A, which is machined pressure die cast aluminium that can act both as a heat source and heat sink for the ECA Surface B which is a raw pressure die casted surface. Surface C which is a rubber grommet, that does not require any different interface compared to the surrounding surface A. DetailsSection 4 Mechanical interface Page page 9 |
Control mode Req. 6.3.1 to 6.3.5 describe the various control modes that can be requested via CAN (Ref 14.14) DetailsSection 6 SW functionality Page page 20 |
Feedback Feedback from the ECA will also be sent via CAN. Specific error reporting as per req. 6.13. Message contents to be agreed with Traton DetailsSection 6 SW functionality Page page 23 |
Internally stored parameters may be accessible only using supplier defined tools . DetailsSection 6 SW functionality Page page 27 |
ECA power and communication connector 2*6.3mm (MCP) 6*2.8mm (MCP) Code A TE part no.: 1-2299782-1 Pin list with: Pin distribution, Pin size (see req. 7.41) DetailsSection 7 Electrical Page page 28 |
Umin: 16 - - V CVS41 limits may go below this value. Valid only for ECU and communication function. For clutch actuation see req. 5.13 DetailsSection 7 Electrical Page page 29 |
Baud rate for CAN FD: 4000 - - kbit/s Figure 15 - Reference circuit DetailsSection 7 Electrical Page page 34 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
CVS41 §4.1 TE-00 Operating Voltage Class A for ECU and communication. Class B for clutch actuation Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component. Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y DetailsSection 10 Environmental and electrical testing Page page 47 |
The actuator is placed outside of the gearbox DetailsSection 2 General Page page 4 |
The maximum release stroke is 22,4 mm from FCCP DetailsSection 4 Mechanical interface Page page 8 |
The clutch force acting on the pushrod is defined in Appendix A DetailsSection 4 Mechanical interface Page page 12 |
The pushrod position when clutch is at rest and only preload force is applied, will vary randomly within 2 mm (± 1mm from FCCP). DetailsSection 4 Mechanical interface Page page 12 |
Accuracy mode DetailsSection 6 SW functionality Page page 23 |
Vehicle identification number(VIN Not applicable. DetailsSection 6 SW functionality Page page 23 |
Wrong rotation direction DetailsSection 6 SW functionality Page page 25 |
Short circuit / open load on the phases DetailsSection 6 SW functionality Page page 25 |
Motor rotation feedback, short circuit / open load DetailsSection 6 SW functionality Page page 25 |
6.3mm Tin, Sn ≥3 μm thick. ≥1 µm Ni DetailsSection 7 Electrical Page page 29 |
2.8mm Gold, Au ≥0,8 μm thick. ≥1 µm Ni DetailsSection 7 Electrical Page page 29 |
Power cable length: - - 2*6000 mm DetailsSection 7 Electrical Page page 29 |
System fuse: - 601|2 A 1. According to ISO 8820-5:2015 SF30 type fuse-links. 2. According to ISO 8820-5:2015 SF51 type fuse-links. DetailsSection 7 Electrical Page page 29 |
Umax: - - 32/36/48 A Specific test relations TBD DetailsSection 7 Electrical Page page 29 |
Peak current (Ipeak): - - See Figure 133 A 3. Up to 100 kHz DetailsSection 7 Electrical Page page 29 Related Tables / DiagramsLinked tables: 0 | Linked diagrams: 1
|
The life length requirement is minimum 3000 operating hours per year for 15 years DetailsSection 8 Reliability Page page 38 |
Reduced versions of test procedure II may be agreed and used during various tests. DetailsSection 10 Environmental and electrical testing Page page 41 |
CVS40 §5.5 TC-05 Temperature cycle test Tmax.tes= +120°C, Tmin.test=-40°C Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.6 TC-06 Thermal shock Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.7 TC-07 Splash water test Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.8 TC-08 Ice water / hot air shock test It is not allowed to use a snorkel to pass this test Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.9 TC-09 Leakage search test Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.11 TC-11 Corrosion in flowing mixed noxious gas N DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.12 TC-12 Salt spray test Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §5.13 TC-13 Dirt spray test TBD DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.2 TM-01 Resonance search Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.3 TM-02 Mechanical shock TBD DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.4 TM-03 Random vibration and thermal cycle P1 Test 2 Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.5 TM-04 Gravel bombardment and impact Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.6 TM-05 External forces Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §6.7 TM-06 Drop test – Free fall Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.1 TL-01 Life length As per Chapter 8 Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.2.1 TL-02 Power cycling test Y DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.2.2 TL-03 Extended thermal shock air TBD DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.2.3 TL-04 High temperature endurance test TBD DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.2.4 TL-05 Endurance test / actuation TBD DetailsSection 10 Environmental and electrical testing Page page 43 |
CVS40 §7.3 TL-06 Component specific test TBD DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS40 §7.4 TL-07 Ageing Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS40 §8.2 TS-02 UV resistance Datasheet sufficient Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS40 §8.3 TS-03 Chemical resistance Application method TBD Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS40 §8.4 TE-01 Isolation resistance and Dielectric strength tests N Exceptions and additional information to CVS41 [Y/N] DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4 Electrical loads Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4.2 TE-01 Operating Voltage (Long-term overvoltage) Umax: 15 min, functional status Class B Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4.3 TE-02 Transient Overvoltage Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4.4 TE-03 Transient Undervoltage Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4.5 TE-04 Jump start Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS41 §4.6 TE-05 Load dump, test pulse 5b Y DetailsSection 10 Environmental and electrical testing Page page 44 |
CVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.7 Test VCB CTE N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.8 Test VCB AN and VCB CP N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.9 Test C-VCB-VCA N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.10 Test TSUP VCB A N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.11 Test TSUP VCB B N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.12 Test VCB Surge N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.13 Test VCB Burst N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.14 Test VCB Charging mode N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.2.2 Vehicle test RE: Self interference Y DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.3.1 Vehicle test: AC charging Vehicle in AC charging mode N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N DetailsSection 10 Environmental and electrical testing Page page 47 |
CVS46 §5.4.1 Vehicle test RI: External interference sources Y DetailsSection 10 Environmental and electrical testing Page page 47 |
Field test Traton will perform field tests with the unit mounted in trucks DetailsSection 12 Quality conformance verification Page page 50 |
Reference / document information (3)
Definitions, abbreviations, document history, scope and other boilerplate. Not customer requirements.
Sample maturity definition However, dividing sample phases into several generations must be agreed upon between Traton and the supplier. The supplier must use the sample denominations requested by Traton. All samples shall be functionally tested before sent to Traton. Deviations shall be reported as a part of the sample delivery. Dimensional checks shall be performed for B and C-samples prior to delivery to Traton. DetailsSection 13 Sample maturity definition Page page 51 Feature / Interface None / OEM/Customer Review Interface |
References 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. • A function test rig shall be used for function tests between intervals • At 6.25M cycles a function test at -40C 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/80C 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. Between the two movements the actuator should remain in the fully disengaged position. After the complete engagement the actuator should remain in this position until the next disengagement is requested. Unless otherwise stated, valid version is the latest available as of 1st May 2026. , Normal operation, Class A This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed. DetailsSection 14 References Page page 57 Feature / Interface None / External Interfaces |
Position definition Should the PP be fully calculated from the AP-sensor, then this offset should not exist. DetailsSection 3 Position definition Page page 7 |
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-004 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems).From this PDF: RFQX-3299216-1-0024; RFQX-3299216-1-0033; RFQX-3299216-1-0088. | Secure Communication and Boundary Control | None | None | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-COM-005 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Hardware domain; allocated to Hardware Platform).From this PDF: RFQX-3299216-1-0041; RFQX-3299216-1-0042; RFQX-3299216-1-0083. | Secure Communication and Boundary Control | None | None | Shared | Blocked by Customer Clarification | Review + Test |
| SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software).From this PDF: RFQX-3299216-1-0061. | Secure Communication and Boundary Control | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-COM-007 | 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 (Interface domain; allocated to External Interfaces; interface: External Interfaces).From this PDF: RFQX-3299216-1-0084; RFQX-3299216-1-0102; RFQX-3299216-1-0103; RFQX-3299216-1-0104; RFQX-3299216-1-0153; RFQX-3299216-1-0171; RFQX-3299216-1-0172; RFQX-3299216-1-0177; RFQX-3299216-1-0178. | External Interfaces | None | External Interfaces | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
| SSR-COM-008 | OEM/Customer Review Interface — Secure Communication and Boundary ControlThe ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0137. | OEM/Customer Review Interface | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test |
| SSR-DAI-002 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Interface domain; allocated to External Interfaces; interface: External Interfaces).From this PDF: RFQX-3299216-1-0031. | Data Authenticity and Integrity Verification | None | External Interfaces | Supplier-Owned | Candidate | Review + Test |
| SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity VerificationThe ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems).From this PDF: RFQX-3299216-1-0036; RFQX-3299216-1-0079. | Data Authenticity and Integrity Verification | None | None | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-DIAG-001 | Diagnostic Services — Diagnostic ServicesThe ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Interface domain; allocated to External Interfaces; interface: External Interfaces).From this PDF: RFQX-3299216-1-0135. | Diagnostic Services | None | External Interfaces | Supplier-Owned | Candidate | Test |
| SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure StorageThe ECU hardware shall provide the platform and secure-storage capabilities required for Hardware / HSM / Secure Storage (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0004; RFQX-3299216-1-0059; RFQX-3299216-1-0145. | Hardware / HSM / Secure Storage | None | OEM/Customer Review Interface | Shared | Ready for Customer Alignment | Review + Test + table/diagram context review |
| SSR-LIFE-002 | Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / DecommissioningThe ECU and supplier process shall handle lifecycle, field return and decommissioning for Lifecycle / Field Return / Decommissioning, including secure data and key handling (System domain; allocated to System Core).From this PDF: RFQX-3299216-1-0200. | Lifecycle / Field Return / Decommissioning | None | None | Supplier-Owned | Ready for Internal Review | Review + Test |
| SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBACThe ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Diagnostic security; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0107; RFQX-3299216-1-0126. | Secure Diagnostics / RBAC | Diagnostic security | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-SYS-001 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0002; RFQX-3299216-1-0007; RFQX-3299216-1-0012; RFQX-3299216-1-0013; RFQX-3299216-1-0014; RFQX-3299216-1-0021; RFQX-3299216-1-0022; RFQX-3299216-1-0025; RFQX-3299216-1-0026; RFQX-3299216-1-0027; RFQX-3299216-1-0029; RFQX-3299216-1-0030; RFQX-3299216-1-0032; RFQX-3299216-1-0034; RFQX-3299216-1-0047; RFQX-3299216-1-0057; RFQX-3299216-1-0060; RFQX-3299216-1-0062; RFQX-3299216-1-0071; RFQX-3299216-1-0074; RFQX-3299216-1-0089; RFQX-3299216-1-0101; RFQX-3299216-1-0105; RFQX-3299216-1-0110; RFQX-3299216-1-0111; RFQX-3299216-1-0112; RFQX-3299216-1-0113; RFQX-3299216-1-0114; RFQX-3299216-1-0115; RFQX-3299216-1-0116; RFQX-3299216-1-0119; RFQX-3299216-1-0120; RFQX-3299216-1-0121; RFQX-3299216-1-0122; RFQX-3299216-1-0123; RFQX-3299216-1-0124; RFQX-3299216-1-0125; RFQX-3299216-1-0136; RFQX-3299216-1-0138; RFQX-3299216-1-0143; RFQX-3299216-1-0144; RFQX-3299216-1-0146; RFQX-3299216-1-0154; RFQX-3299216-1-0198; RFQX-3299216-1-0199; RFQX-3299216-1-0207; RFQX-3299216-1-0208; RFQX-3299216-1-0213; RFQX-3299216-1-0228; RFQX-3299216-1-0245. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-SYS-002 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0070. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-SYS-003 | System Function — System FunctionThe ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0075; RFQX-3299216-1-0139; RFQX-3299216-1-0214; RFQX-3299216-1-0218; RFQX-3299216-1-0285. | System Function | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Test + table/diagram context review |
| SSR-TOOL-001 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Tooling domain; allocated to Engineering Toolchain).From this PDF: RFQX-3299216-1-0035. | Tooling / IT / Evidence Storage | None | None | Supplier-Owned | Candidate | Review + Test |
| SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence StorageThe supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0039; RFQX-3299216-1-0040; RFQX-3299216-1-0043; RFQX-3299216-1-0049; RFQX-3299216-1-0052; RFQX-3299216-1-0055; RFQX-3299216-1-0058; RFQX-3299216-1-0181; RFQX-3299216-1-0201. | Tooling / IT / Evidence Storage | None | OEM/Customer Review Interface | Shared | Blocked by Customer Clarification | Review + Test + table/diagram context review |
| SSR-VV-001 | Security evidence and traceability — Verification and ValidationThe supplier shall verify and validate Security evidence and traceability per the agreed cybersecurity verification and validation plan (System domain; allocated to System Core; interface: OEM/Customer Review Interface).From this PDF: RFQX-3299216-1-0134. | Security evidence and traceability | None | OEM/Customer Review Interface | Supplier-Owned | Candidate | Review + Test + table/diagram context review |
System / Security Design Impact
| Impact Area | Evidence From This PDF |
|---|---|
| Impacted system features | Secure software update and flash readiness; Security evidence and traceability |
| Impacted interfaces | External Interfaces; External Interfaces; OEM/Customer Review Interface; OEM/Customer Review Interface |
| Impacted security capabilities | 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; Engineering Toolchain; External Interfaces; External Interfaces; OEM/Customer Review Interface; Hardware Platform; Security Services; System Core; System Core; OEM/Customer Review Interface |
| Impacted work products | Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design |
| Tools / IT / hardware / test | Low/High/High; 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 | Confirm with customer whether this is a binding requirement and assign a customer ID. |
Estimation / Resource / Tooling Impact
| Impact | Status |
|---|---|
| Estimation impact | yes |
| Resource/tool/IT/HW/test impact | Low/High/High; 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["Diagnostic security"]
doc --> d0
f0["Feature: Secure software update and flash readiness"]
doc --> f0
f1["Feature: Security evidence and traceability"]
doc --> f1
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-004"]
doc --> s0
s1["SSR: SSR-COM-005"]
doc --> s1
s2["SSR: SSR-COM-006"]
doc --> s2
o0["Open point: OP-001"]
doc --> o0
o1["Open point: OP-004"]
doc --> o1
o2["Open point: OP-008"]
doc --> o2
Mermaid source
flowchart LR
doc["3299216_1.pdf"]
d0["Diagnostic security"]
doc --> d0
f0["Feature: Secure software update and flash readiness"]
doc --> f0
f1["Feature: Security evidence and traceability"]
doc --> f1
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-004"]
doc --> s0
s1["SSR: SSR-COM-005"]
doc --> s1
s2["SSR: SSR-COM-006"]
doc --> s2
o0["Open point: OP-001"]
doc --> o0
o1["Open point: OP-004"]
doc --> o1
o2["Open point: OP-008"]
doc --> o2
Source Traceability
Source document
3299216_1.pdf
Document type
Product Requirement
Domain
System Function
Generated records
98 requirements, 82 information, 17 SSRs
Linked artifacts
0 tables, 25 diagrams
Evidence basis
Markdown-derived requirements and registers; OCR disabled; no downstream PDF analysis
Requirement to SSR Traceability
This table is horizontally scrollable. Use the bottom scrollbar to view all columns.
| Customer Requirement | SSR | Disposition | Confidence | Reason |
|---|---|---|---|---|
| RFQX-3299216-1-0001 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0002 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0003 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0004 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0005 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0006 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0007 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0008 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0009 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0010 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0011 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0012 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0013 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0014 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0015 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0016 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0017 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0018 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0019 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0020 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0021 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0022 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0023 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0024 | SSR-COM-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0025 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0026 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0027 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0028 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0029 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0030 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0031 | SSR-DAI-002 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0032 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0033 | SSR-COM-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0034 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0035 | SSR-TOOL-001 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0036 | SSR-DAI-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0037 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0038 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0039 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0040 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0041 | SSR-COM-005 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0042 | SSR-COM-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0043 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0044 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0045 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0046 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0047 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0048 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0049 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0050 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0051 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0052 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0053 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0054 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0055 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0056 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0057 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0058 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0059 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0060 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0061 | SSR-COM-006 | Derive Supplier System Requirement | Low | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0062 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0063 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0064 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0065 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0066 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0067 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0068 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0069 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0070 | SSR-SYS-002 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0071 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0072 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0073 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0074 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0075 | SSR-SYS-003 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0076 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0077 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0078 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0079 | SSR-DAI-003 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0080 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0081 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0082 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0083 | SSR-COM-005 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0084 | SSR-COM-007 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0085 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0086 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0087 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0088 | SSR-COM-004 | Shared Responsibility / CIA Needed | Low | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0089 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0090 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0091 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0092 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0093 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0094 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0095 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0096 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0097 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0098 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0099 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0100 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0101 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0102 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0103 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0104 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0105 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0106 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0107 | SSR-RBAC-001 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0108 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0109 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0110 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0111 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0112 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0113 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0114 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0115 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0116 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0117 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0118 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0119 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0120 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0121 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0122 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0123 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0124 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0125 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0126 | SSR-RBAC-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0127 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0128 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0129 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0130 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0131 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0132 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0134 | SSR-VV-001 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0135 | SSR-DIAG-001 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0136 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0137 | SSR-COM-008 | Derive Supplier System Requirement | Medium | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0138 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0139 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0140 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0141 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0142 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0143 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0144 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0145 | SSR-HW-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0146 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0147 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0148 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0149 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0150 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0151 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0152 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0153 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0154 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0155 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0156 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0157 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0158 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0159 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0160 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0161 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0162 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0163 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0164 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0165 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0166 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0167 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0168 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0169 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0170 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0171 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0172 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0173 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0174 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0175 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0176 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0177 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0178 | SSR-COM-007 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0179 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0180 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0181 | SSR-TOOL-002 | Shared Responsibility / CIA Needed | Medium | Partially accepted; ECU portion mapped, OEM portion needs CIA/RASIC. |
| RFQX-3299216-1-0182 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0183 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0184 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0185 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0186 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0187 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0188 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0189 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0190 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0191 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0192 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0193 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0194 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0195 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0196 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0197 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0198 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0199 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0200 | SSR-LIFE-002 | Derive Supplier System Requirement | High | Accepted requirement; seed of its SSR cluster. |
| RFQX-3299216-1-0201 | SSR-TOOL-002 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0202 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0203 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0204 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0205 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0206 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0207 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0208 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0209 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0210 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0211 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0212 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0213 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0214 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0215 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0216 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0217 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0218 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0219 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0220 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0221 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0222 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0223 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0224 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0225 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0226 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0227 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0228 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0229 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0230 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0231 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0232 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0233 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0234 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0235 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0236 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0237 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0238 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0239 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0240 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0241 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0242 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0243 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0244 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0245 | SSR-SYS-001 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0246 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0247 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0248 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0249 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0250 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0251 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0252 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0253 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0254 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0255 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0256 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0257 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0258 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0259 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0260 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0261 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0262 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0263 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0264 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0265 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0266 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0267 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0268 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0269 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0270 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0271 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0272 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0273 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0274 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0275 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0276 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0277 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0278 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0279 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0280 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0281 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0282 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0283 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0284 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0285 | SSR-SYS-003 | Covered by Existing Supplier System Requirement | Medium | Accepted requirement; covered by a clustered SSR. |
| RFQX-3299216-1-0286 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0287 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0288 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0289 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0290 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0291 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0292 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0293 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0294 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0295 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0296 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0297 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0298 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0299 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0300 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0301 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0302 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0303 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0304 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0305 | None | Needs Internal Review | n/a | Low confidence / human review before derivation. |
| RFQX-3299216-1-0306 | None | Blocked by Customer Clarification | n/a | Needs customer clarification before derivation. |
| RFQX-3299216-1-0307 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0308 | None | Informational Only | n/a | Non-binding; not derived. |
| RFQX-3299216-1-0309 | None | Informational Only | n/a | Non-binding; not derived. |
Next Actions
Detailed Evidence
Document intelligence markdown
3299216_1
- Source PDF:
3299216_1.pdf - Converted Markdown:
converted/markdown/source document - Document type: Product Requirement
- Domain: System Function
- Confidence: High
- Evidence basis: Markdown-derived requirements and generated RFQX registers; no downstream PDF analysis.
Executive Summary
Scope: this product requirement specifies system architecture design, covering 1 Document overview; 2 General; 4 Mechanical interface; 5 Clutch engage and disengage; 6 SW functionality; 7 Electrical. System boundary and interfaces: the document constrains 2 interface(s) - OEM/Customer Review Interface; External Interfaces; OEM/Customer Review Interface; principal functions in scope are Security evidence and traceability; Secure software update and flash readiness.
Engineering obligations: 98 confirmed customer requirement(s) carry an explicit ID and normative wording and must be implemented and verified; 114 further requirement-like statement(s) have no customer ID and must be clarified before they can be baselined; 82 informational and 14 reference item(s) were separated out as non-binding. Design and security impact: affects Security evidence and traceability; Secure software update and flash readiness; security capabilities touched: Diagnostic security; 17 supplier system requirement(s) were derived from this document.
Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). (sample: 3 of 5) - plus 114 unidentified requirement-like statement(s). Do not baseline these until the customer confirms. Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used.
Document Abstract
| Field | Interpretation |
|---|---|
| Document Purpose | Scope: this product requirement specifies system architecture design, covering 1 Document overview; 2 General; 4 Mechanical interface; 5 Clutch engage and disengage; 6 SW functionality; 7 Electrical. |
| Engineering Interpretation | System boundary and interfaces: the document constrains 2 interface(s) - OEM/Customer Review Interface; External Interfaces; OEM/Customer Review Interface; principal functions in scope are Security evidence and traceability; Secure software update and flash readiness. |
| Supplier Proposal Impact | Engineering obligations: 98 confirmed customer requirement(s) carry an explicit ID and normative wording and must be implemented and verified; 114 further requirement-like statement(s) have no customer ID and must be clarified before they can be baselined; 82 informational and 14 reference item(s) were separated out as non-binding. |
| System / Security Impact | Design and security impact: affects Security evidence and traceability; Secure software update and flash readiness; security capabilities touched: Diagnostic security; 17 supplier system requirement(s) were derived from this document. |
| Customer Clarification Impact | Open for the customer: 5 document-linked open point(s) - mainly Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA).; Confirm the update chain ownership (backend/campaign vs. ECU programming) and the authenticity/integrity scheme to be applied.; Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). (sample: 3 of 5) - plus 114 unidentified requirement-like statement(s). Do not baseline these until the customer confirms. |
| Confidence and Limits | Confidence and limits: High confidence. Categorisation is derived from the converted Markdown (customer IDs, normative wording, and section context); no OCR or downstream PDF analysis is used. |
Main Requirement Themes
| Theme | Summary | Requirement Count | Representative Requirements |
|---|---|---|---|
| System architecture design | Groups related document requirements into a single engineering theme. | 276 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| System | Groups related document requirements into a single engineering theme. | 218 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| Core ECA system behavior | Defines actuator ECU behavior, drivetrain integration, electrical/mechanical constraints, and verification scope. | 166 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0003 |
| System core | Groups related document requirements into a single engineering theme. | 145 | RFQX-3299216-1-0001; RFQX-3299216-1-0002; RFQX-3299216-1-0007 |
| Needs clarification | Groups related document requirements into a single engineering theme. | 114 | RFQX-3299216-1-0001; RFQX-3299216-1-0008; RFQX-3299216-1-0009 |
| Requirement | Groups related document requirements into a single engineering theme. | 98 | RFQX-3299216-1-0002; RFQX-3299216-1-0004; RFQX-3299216-1-0007 |
| Information | Groups related document requirements into a single engineering theme. | 82 | RFQX-3299216-1-0003; RFQX-3299216-1-0005; RFQX-3299216-1-0006 |
| Responsibility and customer approval model | Creates supplier/OEM allocation decisions for work products, backend infrastructure, approvals, and residual risk. | 62 | RFQX-3299216-1-0012; RFQX-3299216-1-0017; RFQX-3299216-1-0018 |
Document Content Structure
| Section | Requirements | Information | Unknown | Excluded | Total Items | Critical | Open Points | SSR Links |
|---|---|---|---|---|---|---|---|---|
| 1 Document overview | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 0 |
| 2 General | 6 | 3 | 0 | 0 | 17 | 8 | 3 | 2 |
| 3 Position definition | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 |
| 4 Mechanical interface | 21 | 4 | 0 | 0 | 32 | 13 | 2 | 7 |
| 5 Clutch engage and disengage | 13 | 1 | 0 | 0 | 27 | 13 | 1 | 6 |
| 6 SW functionality | 34 | 9 | 0 | 0 | 63 | 22 | 2 | 10 |
| 7 Electrical | 11 | 9 | 0 | 0 | 54 | 35 | 2 | 4 |
| 8 Reliability | 4 | 1 | 0 | 0 | 10 | 5 | 1 | 3 |
| 9 Environmental impact | 2 | 0 | 0 | 0 | 6 | 4 | 1 | 1 |
| 10 Environmental and electrical testing | 5 | 54 | 0 | 0 | 66 | 7 | 1 | 2 |
| 11 Functional safety | 0 | 0 | 0 | 0 | 5 | 5 | 1 | 0 |
| 12 Quality conformance verification | 1 | 1 | 0 | 0 | 12 | 10 | 1 | 1 |
| 13 Sample maturity definition | 0 | 0 | 0 | 0 | 5 | 5 | 1 | 0 |
| 14 References | 1 | 0 | 0 | 0 | 9 | 2 | 2 | 0 |
Tables and Diagrams
| Artifact | Type | Caption | Page | Related Requirements | Impact |
|---|---|---|---|---|---|
| DIAGRAM-32992161-0001 | Diagram | Figure 1 - Position definition | page 6 | None | Diagram source context |
| DIAGRAM-32992161-0002 | Diagram | Figure 2 - Position relations | page 7 | None | Diagram source context |
| DIAGRAM-32992161-0003 | Diagram | Figure 3 - Pushrod positions | page 8 | RFQX-3299216-1-0022 | Diagram source context |
| DIAGRAM-32992161-0004 | Diagram | Figure 4 – ISO view of 3d envelope. (all parts not shown) | page 9 | RFQX-3299216-1-0027 | Diagram source context |
| DIAGRAM-32992161-0005 | Diagram | Figure 5 - Gearbox flange | page 10 | RFQX-3299216-1-0029 | Diagram source context |
| DIAGRAM-32992161-0006 | Diagram | Figure 6 - Snap in tool space | page 11 | RFQX-3299216-1-0040 | Diagram source context |
| DIAGRAM-32992161-0007 | Diagram | Figure 7 – Maximum disengage time | page 13 | RFQX-3299216-1-0053; RFQX-3299216-1-0054; RFQX-3299216-1-0055 | State-machine or transition behavior |
| DIAGRAM-32992161-0008 | Diagram | Figure 8 - Maximum engage time | page 14 | RFQX-3299216-1-0055; RFQX-3299216-1-0056; RFQX-3299216-1-0053 | State-machine or transition behavior |
| DIAGRAM-32992161-0009 | Diagram | Figure 9 - Step response. | page 16 | RFQX-3299216-1-0070; RFQX-3299216-1-0303 | Diagram source context |
| DIAGRAM-32992161-0010 | Diagram | Figure 9 - Step response | page 16 | RFQX-3299216-1-0070; RFQX-3299216-1-0303 | Diagram source context |
| DIAGRAM-32992161-0011 | Diagram | Figure 10 - Step response test cycle | page 17 | RFQX-3299216-1-0071; RFQX-3299216-1-0072 | Diagram source context |
| DIAGRAM-32992161-0012 | Diagram | Figure 11 - Release frequency test | page 18 | RFQX-3299216-1-0074; RFQX-3299216-1-0073 | Diagram source context |
| DIAGRAM-32992161-0013 | Diagram | Figure 12 - Class B exceptions | page 19 | None | State-machine or transition behavior |
| DIAGRAM-32992161-0014 | Diagram | Figure 133 A 3. Up to 100 kHz | page 29 | RFQX-3299216-1-0159 | Diagram source context |
| DIAGRAM-32992161-0015 | Diagram | Figure 13 - Max current | page 30 | None | Diagram source context |
| DIAGRAM-32992161-0016 | Diagram | Figure 13 - Wake up signal hysteresis | page 32 | None | Diagram source context |
| DIAGRAM-32992161-0017 | Diagram | Figure 14 – Dual function block diagram | page 33 | None | Diagram source context |
| DIAGRAM-32992161-0018 | Diagram | Figure 15 - Reference circuit | page 34 | RFQX-3299216-1-0173 | Software update or memory programming context |
| DIAGRAM-32992161-0019 | Diagram | Figure 16 - Temperature histogram | page 37 | None | Diagram source context |
| DIAGRAM-32992161-0020 | Diagram | Figure 17 - Test procedure I | page 41 | RFQX-3299216-1-0218; RFQX-3299216-1-0220 | Diagram source context |
| DIAGRAM-32992161-0021 | Diagram | Figure 18 - Disengage force | page 55 | None | Diagram source context |
| DIAGRAM-32992161-0022 | Diagram | Figure 19 - Engage force | page 56 | None | Diagram source context |
| DIAGRAM-32992161-0023 | Diagram | Figure 20 - Test cycle | page 58 | None | Diagram source context |
| DIAGRAM-32992161-0024 | Diagram | Figure 21 – Release Load vs Strokes | page 60 | None | Diagram source context |
| DIAGRAM-32992161-0025 | Diagram | Figure 22 – Release Load vs Strokes | page 61 | None | Diagram source context |
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 |
|---|---|---|---|---|
| RFQX-3299216-1-0064 | 95 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | 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. |
| RFQX-3299216-1-0132 | 95 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | The filter time shall equal the update frequency . |
| RFQX-3299216-1-0176 | 95 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; High estimation impact; blocks SSR derivation | 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. |
| RFQX-3299216-1-0009 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 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. |
| RFQX-3299216-1-0011 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | The ECA units shall be delivered to the required Traton brand’s production in a position in the pallet where the marking is visible. |
| RFQX-3299216-1-0015 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 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. |
| RFQX-3299216-1-0017 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 2.10 Traton requires extensive testing to be performed by the supplier to verify all demands stated in the requirement specification. |
| RFQX-3299216-1-0018 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 2.12 Traton requires: - Documentation of the product, i.e. |
| RFQX-3299216-1-0038 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | Alternatively it can have a loose fit in the ECA, but it shall be possible to reconnect it by pushing it back by hand. |
| RFQX-3299216-1-0091 | 81 | High risk due to unclear OEM/supplier responsibility | security relevant; architecture relevant; Needs Customer Clarification; linked open point; blocks SSR derivation | 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. |
Open Points
| Open Point | Priority | Question | Impact | Status |
|---|---|---|---|---|
| OP-001 | Confirm the exact ECU designation/variant and the agreed item definition and boundary used for the risk analysis (TARA). | TARA scope and effort stay open; downstream assets, goals and design may rework. | Open | |
| 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-008 | Confirm production/debug hardening expectations (debug lock, secure end-of-line, developer-access policy). | Hardware fusing and EOL process design stay open; risk of an exposed debug/production interface. | Open | |
| OP-009 | Confirm the DIA / responsibility (RASIC/CIA) split for each cybersecurity work product before supplier scope is fixed. | Without an agreed DIA the supplier risks owning customer work products or leaving cybersecurity gaps in the case. | 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-004 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (IT / backend domain; allocated to Backend and IT Systems). | RFQX-3299216-1-0024; RFQX-3299216-1-0033; RFQX-3299216-1-0088 | no | Blocked by Customer Clarification |
| SSR-COM-005 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Hardware domain; allocated to Hardware Platform). | RFQX-3299216-1-0041; RFQX-3299216-1-0042; RFQX-3299216-1-0083 | no | Blocked by Customer Clarification |
| SSR-COM-006 | Secure Communication and Boundary Control — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for Secure Communication and Boundary Control, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software). | RFQX-3299216-1-0061 | no | Ready for Customer Alignment |
| SSR-COM-007 | 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 (Interface domain; allocated to External Interfaces; interface: External Interfaces). | RFQX-3299216-1-0084; RFQX-3299216-1-0102; RFQX-3299216-1-0103; RFQX-3299216-1-0104; RFQX-3299216-1-0153; RFQX-3299216-1-0171; RFQX-3299216-1-0172; RFQX-3299216-1-0177; RFQX-3299216-1-0178 | no | Candidate |
| SSR-COM-008 | OEM/Customer Review Interface — Secure Communication and Boundary Control | The ECU shall restrict and protect communication for OEM/Customer Review Interface, exposing only OEM-agreed services and applying authenticity/integrity/freshness and boundary controls on allocated signals (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0137 | no | Candidate |
| SSR-DAI-002 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (Interface domain; allocated to External Interfaces; interface: External Interfaces). | RFQX-3299216-1-0031 | no | Candidate |
| SSR-DAI-003 | Data Authenticity and Integrity Verification — Data Authenticity and Integrity Verification | The ECU shall verify the authenticity and integrity of Data Authenticity and Integrity Verification data and reject manipulated or unauthenticated data (IT / backend domain; allocated to Backend and IT Systems). | RFQX-3299216-1-0036; RFQX-3299216-1-0079 | no | Ready for Customer Alignment |
| SSR-DIAG-001 | Diagnostic Services — Diagnostic Services | The ECU shall provide the diagnostic services for Diagnostic Services required by the allocated customer requirements, including the specified services, sessions and data identifiers (Interface domain; allocated to External Interfaces; interface: External Interfaces). | RFQX-3299216-1-0135 | no | Candidate |
| SSR-HW-001 | Hardware / HSM / Secure Storage — Hardware / HSM / Secure Storage | The ECU hardware shall provide the platform and secure-storage capabilities required for Hardware / HSM / Secure Storage (Hardware domain; allocated to Hardware Platform; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0004; RFQX-3299216-1-0059; RFQX-3299216-1-0145 | no | Ready for Customer Alignment |
| SSR-LIFE-002 | Lifecycle / Field Return / Decommissioning — Lifecycle / Field Return / Decommissioning | The ECU and supplier process shall handle lifecycle, field return and decommissioning for Lifecycle / Field Return / Decommissioning, including secure data and key handling (System domain; allocated to System Core). | RFQX-3299216-1-0200 | no | Ready for Internal Review |
| SSR-RBAC-001 | Secure Diagnostics / RBAC — Secure Diagnostics / RBAC | The ECU shall enforce authenticated, role-authorised access for Secure Diagnostics / RBAC, restricting security-relevant diagnostic services per the OEM-agreed role model (Cybersecurity domain; allocated to Security Services; security capability: Diagnostic security; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0107; RFQX-3299216-1-0126 | no | Blocked by Customer Clarification |
| SSR-SYS-001 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0002; RFQX-3299216-1-0007; RFQX-3299216-1-0012; RFQX-3299216-1-0013; RFQX-3299216-1-0014; RFQX-3299216-1-0021; RFQX-3299216-1-0022; RFQX-3299216-1-0025; RFQX-3299216-1-0026; RFQX-3299216-1-0027; RFQX-3299216-1-0029; RFQX-3299216-1-0030; RFQX-3299216-1-0032; RFQX-3299216-1-0034; RFQX-3299216-1-0047; RFQX-3299216-1-0057; RFQX-3299216-1-0060; RFQX-3299216-1-0062; RFQX-3299216-1-0071; RFQX-3299216-1-0074; RFQX-3299216-1-0089; RFQX-3299216-1-0101; RFQX-3299216-1-0105; RFQX-3299216-1-0110; RFQX-3299216-1-0111; RFQX-3299216-1-0112; RFQX-3299216-1-0113; RFQX-3299216-1-0114; RFQX-3299216-1-0115; RFQX-3299216-1-0116; RFQX-3299216-1-0119; RFQX-3299216-1-0120; RFQX-3299216-1-0121; RFQX-3299216-1-0122; RFQX-3299216-1-0123; RFQX-3299216-1-0124; RFQX-3299216-1-0125; RFQX-3299216-1-0136; RFQX-3299216-1-0138; RFQX-3299216-1-0143; RFQX-3299216-1-0144; RFQX-3299216-1-0146; RFQX-3299216-1-0154; RFQX-3299216-1-0198; RFQX-3299216-1-0199; RFQX-3299216-1-0207; RFQX-3299216-1-0208; RFQX-3299216-1-0213; RFQX-3299216-1-0228; RFQX-3299216-1-0245 | no | Candidate |
| SSR-SYS-002 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Process / compliance domain; allocated to Compliance Process; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0070 | no | Candidate |
| SSR-SYS-003 | System Function — System Function | The ECU shall implement the System Function behaviour required by its allocated customer requirements, including the specified functions, signals, states and timing (Software domain; allocated to Application Software; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0075; RFQX-3299216-1-0139; RFQX-3299216-1-0214; RFQX-3299216-1-0218; RFQX-3299216-1-0285 | no | Candidate |
| SSR-TOOL-001 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (Tooling domain; allocated to Engineering Toolchain). | RFQX-3299216-1-0035 | no | Candidate |
| SSR-TOOL-002 | Tooling / IT / Evidence Storage — Tooling / IT / Evidence Storage | The supplier shall provide the tooling, IT infrastructure and evidence storage required for Tooling / IT / Evidence Storage (IT / backend domain; allocated to Backend and IT Systems; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0039; RFQX-3299216-1-0040; RFQX-3299216-1-0043; RFQX-3299216-1-0049; RFQX-3299216-1-0052; RFQX-3299216-1-0055; RFQX-3299216-1-0058; RFQX-3299216-1-0181; RFQX-3299216-1-0201 | no | Blocked by Customer Clarification |
| SSR-VV-001 | Security evidence and traceability — Verification and Validation | The supplier shall verify and validate Security evidence and traceability per the agreed cybersecurity verification and validation plan (System domain; allocated to System Core; interface: OEM/Customer Review Interface). | RFQX-3299216-1-0134 | no | Candidate |
Design Impact
- Impacted System Features: Secure software update and flash readiness; Security evidence and traceability
- Impacted Interfaces: External Interfaces; External Interfaces; OEM/Customer Review Interface; OEM/Customer Review Interface
- Impacted Security Capabilities: 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; Engineering Toolchain; External Interfaces; External Interfaces; OEM/Customer Review Interface (sample: 8 of 12)
- Impacted Work Products: Cybersecurity concept; Cybersecurity verification report; DIA / cybersecurity case; Requirement traceability record; System/architecture design
- Impacted Document Artifacts: DIAGRAM-32992161-0003; DIAGRAM-32992161-0004; DIAGRAM-32992161-0005; DIAGRAM-32992161-0006; DIAGRAM-32992161-0007; DIAGRAM-32992161-0008; DIAGRAM-32992161-0009; DIAGRAM-32992161-0010 (sample: 8 of 13)
- Impacted Tools It Hardware Test: Low/High/High; Low/High/Low; Low/High/Medium; Low/Low/High; Low/Low/Low; Low/Low/Medium; Medium/High/Medium; Medium/Low/Low (sample: 8 of 9)
- Impacted Supplier System Requirements: SSR-COM-004; SSR-COM-005; SSR-COM-006; SSR-COM-007; SSR-COM-008; SSR-DAI-002; SSR-DAI-003; SSR-DIAG-001 (sample: 8 of 17)
- Design Assumptions Introduced: Security-relevant requirement the ECU can own once responsibility/method is confirmed.
- Design Decisions Required: Confirm with customer whether this is a binding requirement and assign a customer ID.