Customer Review - RFQX Security Architecture Package

Customer Readiness Summary

Readiness classification: Ready for customer clarification workshop

Recommendation

Use this package as the evidence baseline for a customer clarification workshop. It is not yet customer-ready for approval because key product boundary, interface, ownership, and TARA/residual-risk questions remain open.

Current Gate

Traceability gate: WARN - Customer Clarification Needed
OCR status: false
Downstream direct PDF analysis: false
Unsupported architecture placeholders unresolved: 0

Known Limitations

Low-confidence requirements remain visible with RFQX-06 review statuses.
Final TARA and residual-risk approval are not claimed.
Exact deployment topology and ownership must be confirmed by the customer and supplier.

Additional PDF Delta

Clarification questions before additional PDFs: 0
Clarification questions current: 64
Clarification questions evaluated: 64
Questions answered by additional PDFs: 0
Questions partially answered by additional PDFs: 0
Questions introduced by additional PDFs: 64
P1 before: 0
P1 current: 10
P1 still requiring decision: 10
Customer readiness remains a clarification workshop posture until customer decisions are captured.

Customer Clarification Questions

Generated: 2026-06-20T16:56:36+00:00

Total clarification questions: 64

Product/System Boundary

CQ-BOUNDARY-01

Question: Confirm the customer decision needed to baseline this requirement item: Note: The vehicle manufacturer and supplier shall collaboratively define the context of the system or function to enable the supplier performing th.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00006
Source Markdown: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-04

Question: Confirm the customer decision needed to baseline this requirement item: Message contents to be agreed with Traton 6.9 ECA identification number: The ECA shall report a unique ECA individual identification number 6.10 Su.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00146
Source Markdown: converted/markdown-cleaned/3299216_1.md page 23
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-06

Question: Confirm the customer decision needed to baseline this requirement item: Internally stored parameters may be accessible only using supplier defined tools .. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00175
Source Markdown: converted/markdown-cleaned/3299216_1.md page 27
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Classification: Needs Customer Clarification

CQ-BOUNDARY-16

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: It should be possible to reuse the generic bootloader for future currently unknown purposes/applications without a need to create a new part number.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00317
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-19

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 52 Since Link Control is only applicable in production when no application has been programmed by the supplier, the application may retur.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00338
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 15
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Classification: Needs Customer Clarification

CQ-BOUNDARY-23

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 134 The received data to decrypt may only be parts of a software module and it will be based on the range defined.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00480
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 42
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Classification: Needs Customer Clarification

CQ-BOUNDARY-24

Question: Confirm the customer decision needed to baseline this requirement item: 4 Terms, definitions and abbreviations 4.1 Terms Table 1 – Definition of Terms Term Definition Shall This word, or the terms "Required" or "Must",.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00488
Source Markdown: converted/markdown-cleaned/CVS124.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-28

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Internal Page 26 (90) Diagnostics Service Diag Safe state check Application Boot loader TransferData (0x36) M - RequestFileTransfer (0x38) M - C1 =.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_UDS-0051
Source Markdown: converted/markdown-cleaned/CVS124.md page 26
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-31

Question: Confirm the customer decision needed to baseline this requirement item: Internal Page 52 (90) Byte Description Range Resolu tion This byte shall be set to value 2 and is used to identify the response structure variant #.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00634
Source Markdown: converted/markdown-cleaned/CVS124.md page 52
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-38

Question: Confirm the customer decision needed to baseline this requirement item: 3.2 DSC ASN.1 definition DSC_BASE_REQ 41 The structure version for this document release shall be: Major ‘04’ and Minor ‘00’ DSC_BASE_REQ 42 The se.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P1
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Blocks architecture baseline
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00866
Source Markdown: converted/markdown-cleaned/CVS154.md page 9
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Not Applicable
Rationale: Requirement was not low-confidence in the extracted baseline.
Classification: Needs Customer Clarification

CQ-BOUNDARY-02

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: REQ_SEC_0040 The vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_SEC_0040
Source Markdown: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-03

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: REQ_SEC_0041 The vehicle manufacturer reserves the right to request documentation and evidence as well as to perform or order a compliance audit to.... This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_SEC_0041
Source Markdown: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-05

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Req.ID Description 6.22.1 Wrong rotation direction 6.22.2 Short circuit / open load on the phases 6.22.3 Motor rotation feedback, short circuit / o.... This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: Req.ID-Description-6.22.1
Source Markdown: converted/markdown-cleaned/3299216_1.md page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-07

Question: Confirm the customer decision needed to baseline this requirement item: 7.17 Umax: - - 32/36/48 A Specific test relations TBD 7.18 Umin: 16 - - V CVS41 limits may go below this value.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00190
Source Markdown: converted/markdown-cleaned/3299216_1.md page 29
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-08

Question: Confirm the customer decision needed to baseline this requirement item: Reduced versions of test procedure II may be agreed and used during various tests.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00246
Source Markdown: converted/markdown-cleaned/3299216_1.md page 41
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-09

Question: Confirm the customer decision needed to baseline this requirement item: Y 10.7.28 CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y 10.7.29 CVS46 §5.2.1 Vehicle test RE: Protection of receivers.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00250
Source Markdown: converted/markdown-cleaned/3299216_1.md page 47
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-10

Question: Confirm the customer decision needed to baseline this requirement item: Unless otherwise stated, valid version is the latest available as of 1st May 2026.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00272
Source Markdown: converted/markdown-cleaned/3299216_1.md page 52
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-11

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00278
Source Markdown: converted/markdown-cleaned/3299216_1.md page 61
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-12

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: TRATON Software Update Variant 2 (SUV2) sequence Foreword This Commercial Vehicle Standard (“CVS123-2”) contains requirement specifications for TRA.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00279
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-13

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: Clients may prefer to implement programming support using other service parameter values or even another set of programming steps than. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00284
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 4
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-14

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: The value of this variable (and C2, see below) may be used by the boot manager to determine whether to start the application or the boot loader.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00292
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-15

Question: Confirm the customer decision needed to baseline this requirement item: The value of this variable (and C1, see above) may be used by the boot manager to determine whether or not to start the application or the boot loa.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00294
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-17

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 35 As example, the client may read certificate validity time and/or RBAC configuration file to verify if the appropriate entities are sto.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00335
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-18

Question: Confirm the customer decision needed to baseline this requirement item: Alternatively, it may be a client strategy to always update certain entities prior to a software update.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00337
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 14
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-20

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 82 Implementation hint: The integrity information may contain parts of memory not programmed, regardless of this the server verifies the.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00343
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 19
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-21

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 107 In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into anothe.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00378
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 24
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-22

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 113 In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into an.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00420
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-25

Question: Confirm the customer decision needed to baseline this requirement item: May This word, or the adjective “Optional”, means that an item is truly optional.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00492
Source Markdown: converted/markdown-cleaned/CVS124.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-26

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0041 The default diagnostic session is referred to as “defaultSession”.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_UDS-0041
Source Markdown: converted/markdown-cleaned/CVS124.md page 23
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-27

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0049 Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing cert.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_UDS-0049
Source Markdown: converted/markdown-cleaned/CVS124.md page 25
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-29

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00563
Source Markdown: converted/markdown-cleaned/CVS124.md page 32
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-30

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: INFO_UDS 0014 A functionally addressed TesterPresent may arrive at any time during another request.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00588
Source Markdown: converted/markdown-cleaned/CVS124.md page 37
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-32

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: INFO_UDS 0017 In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into anothe.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00652
Source Markdown: converted/markdown-cleaned/CVS124.md page 57
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-33

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.18.2 Request parameter subFunction REQ_UDS 0135 Refer to CVS31 .. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ_UDS-0135
Source Markdown: converted/markdown-cleaned/CVS124.md page 64
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-34

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: INFO_UDS 0020 In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into an.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00704
Source Markdown: converted/markdown-cleaned/CVS124.md page 69
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-35

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: RBAC for diagnostics Foreword This Commercial Vehicle Standard (“CVS151”) contains requirement specifications for TRATON Group and may be referred.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00785
Source Markdown: converted/markdown-cleaned/CVS151.md page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-36

Question: Confirm the customer decision needed to baseline this requirement item: Data Security Container base definition Foreword This Commercial Vehicle Standard (“CVS154”) contains requirement specifications for TRATON Group a.... This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00843
Source Markdown: converted/markdown-cleaned/CVS154.md page 1
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-37

Question: Confirm the customer decision needed to baseline this requirement item: However, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00859
Source Markdown: converted/markdown-cleaned/CVS154.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-39

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: AUTH_INFO 133 If the server is unable to delete the client’s authentication state or cannot retrieve it due to internal errors, the server responds.... This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00932
Source Markdown: converted/markdown-cleaned/CVS31.md page 16
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-40

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: While the ECU-Diagnostic Role extension specifies the roles assigned to a client, the D-RBACC extension may both grant additional permissions and r.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00947
Source Markdown: converted/markdown-cleaned/CVS31.md page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-41

Question: Confirm the customer decision needed to baseline this requirement item: (There may be more than one authentication state).. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-00996
Source Markdown: converted/markdown-cleaned/CVS32.md page 6
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-42

Question: Confirm the customer decision needed to baseline this requirement item: SDT_REQ 19 The client may alter the CipherScheme between SDT requests within the same SDT sequence.. This affects product/system boundary scope, supplier positioning, and traceability status.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-01013
Source Markdown: converted/markdown-cleaned/CVS32.md page 10
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

CQ-BOUNDARY-43

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: The SDT positive response may of course contain an encapsulated negative UDS response.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Product Boundary
Workshop Block: Block 1: Product and Boundary
Why it matters: Product boundary drives every architecture, TARA, traceability, and acceptance decision.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unresolved boundary can invalidate asset allocation, interface scope, and residual-risk agreement.
Related requirement IDs: REQ-AUTO-01056
Source Markdown: converted/markdown-cleaned/CVS32.md page 18
Related architecture/security element: System boundary / item definition
Recommended owner: Joint
Current RFQX status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Classification: Needs Customer Clarification

Network and External Interfaces

CQ-INTERFACE-01

Question: Confirm whether this source item is binding for the ECA ECU baseline or only informative guidance: The signal is valid during Control Modes RPC and TC(see req 6.3).. This affects whether RFQX treats it as supplier scope, assumption, or evidence-only context.
Priority: P3
Decision Type: Interface
Workshop Block: Block 2: Interfaces and Data Flows
Why it matters: Security controls must be allocated at each real boundary, not a generic interface list.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Interface attack surfaces may be missed or over-specified.
Related requirement IDs: req-6.3
Source Markdown: converted/markdown-cleaned/3299216_1.md page 22
Related architecture/security element: External Interfaces / vehicle network boundary
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Diagnostic and Service Access

CQ-DIAG-01

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: More information on CVS124 REQ_UDS 0051 C2 Also referred to as “programming request” flag.. This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0051
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 6
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-02

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: More information on CVS124 REQ_UDS 0051 C3 Also referred to as “reprogrammed” flag.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0051
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 6
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-03

Question: Confirm whether this software-update/bootloader item is binding for the ECA ECU baseline or informative guidance: SUV2_INFO 66 Implementation hint: The server resets the “application valid” flag (C1, see CVS124 REQ_UDS 0051) before the erase process starts, to.... This affects bootloader/update design scope, diagnostic programming behavior, verification evidence, and supplier effort estimation.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0051
Source Markdown: converted/markdown-cleaned/CVS123-2.md page 17
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-04

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: INFO_UDS 0019 Description of the individual transitions as per Figure 2 -State Diagram is explained from REQ_UDS 0305 to REQ_UDS 0337.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0305
Source Markdown: converted/markdown-cleaned/CVS124.md page 27
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-05

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.5.1 Request REQ_UDS 0345 Refer to ISO 14229-1 for request format.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0345
Source Markdown: converted/markdown-cleaned/CVS124.md page 37
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-06

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.5.1.1 Request parameter DTCSettingType REQ_UDS 0346 Refer to ISO 14229-1 for request parameter DTCSettingType.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0346
Source Markdown: converted/markdown-cleaned/CVS124.md page 37
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-07

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.5.2 Positive response REQ_UDS 0348 Refer to ISO 14229-1 for positive response format and parameter.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0348
Source Markdown: converted/markdown-cleaned/CVS124.md page 38
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-08

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.5.3 Negative response REQ_UDS 0349 Refer to ISO 14229-1 for negative response format and codes.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0349
Source Markdown: converted/markdown-cleaned/CVS124.md page 38
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-09

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0093 Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0093
Source Markdown: converted/markdown-cleaned/CVS124.md page 40
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-10

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.15 TransferData (0x36) service 5.5.15.1 Request REQ_UDS 0295. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0295
Source Markdown: converted/markdown-cleaned/CVS124.md page 61
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-11

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.18.1 Request REQ_UDS 0134 Refer to CVS31 .. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0134
Source Markdown: converted/markdown-cleaned/CVS124.md page 64
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-12

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.5.18.3 Positive response REQ_UDS 0136 Refer to CVS31 .. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0136
Source Markdown: converted/markdown-cleaned/CVS124.md page 64
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-13

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0208 The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0208
Source Markdown: converted/markdown-cleaned/CVS124.md page 81
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-14

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.7.4.1 Latest occurrence REQ_UDS 0215 The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3 REQ_UDS 0216 The la.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0215
Source Markdown: converted/markdown-cleaned/CVS124.md page 82
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-15

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.7.4.2 First occurrence REQ_UDS 0217 The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0217
Source Markdown: converted/markdown-cleaned/CVS124.md page 82
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-16

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0218 The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).. This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0218
Source Markdown: converted/markdown-cleaned/CVS124.md page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-17

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.7.5.1 Latest occurrence REQ_UDS 0220 The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmed.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0220
Source Markdown: converted/markdown-cleaned/CVS124.md page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-18

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: REQ_UDS 0221 The latest operational hours value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 a.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0221
Source Markdown: converted/markdown-cleaned/CVS124.md page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-19

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: 5.7.5.2 First occurrence REQ_UDS 0222 The first operational hours value is updated at the first change of DTC status bits 0 (testFailed) and 3 (con.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0222
Source Markdown: converted/markdown-cleaned/CVS124.md page 83
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

CQ-DIAG-20

Question: Confirm the binding diagnostic behavior and service authorization expected for this item: Modified requirements: REQ_UDS 0003: Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL REQ_UDS 0034: Change in the length of Node.... This affects UDS service allocation, security-access roles, safe-state checks, and verification scope.
Priority: P3
Decision Type: Interface
Workshop Block: Block 4: Diagnostics / Update / PKI
Why it matters: Diagnostics can unlock privileged ECU behavior and update paths.
Impact if unresolved: Can remain as tracked assumption
Impact detail: Unauthorized service access may remain untreated or impossible to verify.
Related requirement IDs: REQ_UDS-0003
Source Markdown: converted/markdown-cleaned/CVS124.md page 90
Related architecture/security element: Diagnostic access boundary / Secure Diagnostics
Recommended owner: Joint
Current RFQX status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Classification: Needs Customer Clarification

Additional PDF Closure Overlay

Additional PDF closure analysis generated: 2026-06-20T16:56:49+00:00
Answered by additional PDFs: 0
Partially answered by additional PDFs: 0
Introduced by additional PDFs: 64
Still requiring customer decision: 64
Current P1: 10

Closed questions are not deleted; closure history is in customer_review/clarification_status_updated.md.

Clarification Priority Matrix

Generated: 2026-06-20T16:56:36+00:00

Total questions: 64
P1 count: 10
P2 count: 0
P3 count: 54

Questions by Domain

Diagnostic and Service Access: 20
Network and External Interfaces: 1
Product/System Boundary: 43

Questions by Owner

Joint: 64

Questions by Impacted Architecture Area

Diagnostic access boundary / Secure Diagnostics: 20
External Interfaces / vehicle network boundary: 1
System boundary / item definition: 43

Sequenced Question Register

CQ-BOUNDARY-01

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00006

CQ-BOUNDARY-04

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00146

CQ-BOUNDARY-06

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00175

CQ-BOUNDARY-16

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00317

CQ-BOUNDARY-19

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00338

CQ-BOUNDARY-23

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00480

CQ-BOUNDARY-24

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00488

CQ-BOUNDARY-28

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_UDS-0051

CQ-BOUNDARY-31

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00634

CQ-BOUNDARY-38

Priority: P1
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00866

CQ-BOUNDARY-02

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_SEC_0040

CQ-BOUNDARY-03

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_SEC_0041

CQ-BOUNDARY-05

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: Req.ID-Description-6.22.1

CQ-BOUNDARY-07

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00190

CQ-BOUNDARY-08

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00246

CQ-BOUNDARY-09

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00250

CQ-BOUNDARY-10

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00272

CQ-BOUNDARY-11

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00278

CQ-BOUNDARY-12

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00279

CQ-BOUNDARY-13

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00284

CQ-BOUNDARY-14

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00292

CQ-BOUNDARY-15

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00294

CQ-BOUNDARY-17

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00335

CQ-BOUNDARY-18

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00337

CQ-BOUNDARY-20

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00343

CQ-BOUNDARY-21

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00378

CQ-BOUNDARY-22

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00420

CQ-BOUNDARY-25

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00492

CQ-BOUNDARY-26

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_UDS-0041

CQ-BOUNDARY-27

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_UDS-0049

CQ-BOUNDARY-29

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00563

CQ-BOUNDARY-30

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00588

CQ-BOUNDARY-32

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00652

CQ-BOUNDARY-33

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ_UDS-0135

CQ-BOUNDARY-34

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00704

CQ-BOUNDARY-35

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00785

CQ-BOUNDARY-36

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00843

CQ-BOUNDARY-37

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00859

CQ-BOUNDARY-39

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00932

CQ-BOUNDARY-40

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00947

CQ-BOUNDARY-41

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-00996

CQ-BOUNDARY-42

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-01013

CQ-BOUNDARY-43

Priority: P3
Workshop Block: Block 1: Product and Boundary
Decision Type: Product Boundary
Domain: Product/System Boundary
Recommended owner: Joint
Impacted architecture/security area: System boundary / item definition
Related requirement IDs: REQ-AUTO-01056

CQ-INTERFACE-01

Priority: P3
Workshop Block: Block 2: Interfaces and Data Flows
Decision Type: Interface
Domain: Network and External Interfaces
Recommended owner: Joint
Impacted architecture/security area: External Interfaces / vehicle network boundary
Related requirement IDs: req-6.3

CQ-DIAG-01

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0051

CQ-DIAG-02

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0051

CQ-DIAG-03

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0051

CQ-DIAG-04

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0305

CQ-DIAG-05

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0345

CQ-DIAG-06

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0346

CQ-DIAG-07

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0348

CQ-DIAG-08

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0349

CQ-DIAG-09

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0093

CQ-DIAG-10

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0295

CQ-DIAG-11

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0134

CQ-DIAG-12

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0136

CQ-DIAG-13

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0208

CQ-DIAG-14

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0215

CQ-DIAG-15

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0217

CQ-DIAG-16

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0218

CQ-DIAG-17

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0220

CQ-DIAG-18

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0221

CQ-DIAG-19

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0222

CQ-DIAG-20

Priority: P3
Workshop Block: Block 4: Diagnostics / Update / PKI
Decision Type: Interface
Domain: Diagnostic and Service Access
Recommended owner: Joint
Impacted architecture/security area: Diagnostic access boundary / Secure Diagnostics
Related requirement IDs: REQ_UDS-0003

Additional PDF Closure Overlay

Additional PDF closure analysis generated: 2026-06-20T16:56:49+00:00
Answered by additional PDFs: 0
Partially answered by additional PDFs: 0
Introduced by additional PDFs: 64
Still requiring customer decision: 64
Current P1: 10

Closed questions are not deleted; closure history is in customer_review/clarification_status_updated.md.

Customer Workshop Agenda

Duration: 60-90 minutes

Objective

Confirm the product boundary, interfaces, security responsibilities, and evidence expectations needed to move the RFQX package from expert synthesis to customer-review baseline.

Participants

OEM/customer system owner
OEM/customer cybersecurity architect
Supplier system architect
Supplier cybersecurity architect
Diagnostic/update owner
Backend/SecOps or tooling owner where applicable

Pre-read

site/index.html
product_understanding/product_summary.md
architecture/architecture_overview.md
cybersecurity/security_concept_overview.md
traceability/traceability_gate_rationale.md
requirements/low_confidence_requirement_review.md

Discussion Blocks

1. 10 min: Confirm product/item boundary and customer review objective. 2. 15 min: Review external interfaces, diagnostic access, update/IVD, and PKI/key ownership. 3. 15 min: Review security architecture, assets, trust boundaries, logging, monitoring, backend/SecOps responsibilities. 4. 15 min: Review low-confidence closure and clarify which items are binding, informational, or out of scope. 5. 10 min: Review TARA/residual-risk expectations and approval authority. 6. 5-20 min: Agree actions, owners, and evidence updates.

Decision Points

Accepted item boundary and architecture scope.
Confirmed mandatory security capabilities and optional/reference-only items.
Confirmed owner for each open security and evidence responsibility.
Confirmed next evidence update and review cadence.

Required Outputs

Answered or owner-assigned clarification questions.
Updated architecture assumptions and traceability status.
Customer-approved next-step list for TARA and mechanism allocation.

Follow-up Actions

Update RFQX baseline with customer answers.
Re-run synthesis/site/evidence export.
Move gate from customer-clarification WARN only when decisions are documented.

Low-Confidence Requirement Review

Generated: 2026-06-20T16:56:35+00:00

Low-confidence requirements before review: 113
Active low-confidence requirements after review: 0
Reviewed low-confidence requirements: 113

Status Summary

Needs Manual Markdown Correction: 56
Reclassified as Assumption: 25
Reclassified as Constraint: 3
Reclassified as Informational: 29

Reviewed Items

REQ_SEC_0040

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6
Statement: REQ_SEC_0040 The vehicle manufacturer reserves the right to perform penetration testing on the ECU to identify potential vulnerabilities.

REQ_SEC_0041

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7
Statement: REQ_SEC_0041 The vehicle manufacturer reserves the right to request documentation and evidence as well as to perform or order a compliance audit to determine whether the listed requirements are fulfilled.

req-6.3

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 22
Statement: The signal is valid during Control Modes RPC and TC(see req 6.3).

Req.ID-Description-6.22.1

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 25
Statement: Req.ID Description 6.22.1 Wrong rotation direction 6.22.2 Short circuit / open load on the phases 6.22.3 Motor rotation feedback, short circuit / open load

REQ-AUTO-00171

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/3299216_1.md page 26
Statement: P 1 Page 6.22.4 Positions sensor short circuit / open load (if used) 6.22.5 Watchdog error 6.22.6 Low voltage 30 6.22.7 CAN-timeout (stored and sent when possible) 6.22.8 High temperature/current consumption (system needs to indicate abnormal usage that can damage the device), indicate a self-protective mode (if applicable) 6.22.9 Error on temperature sensor 6.22.10 High friction in mechanical system 6.22.11 Other electrical HW error

REQ-AUTO-00175

Original confidence: Low
Final status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Action taken: Kept active as a reviewed constraint and mapped through architecture/constraints evidence.
Active in baseline: yes
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 27
Statement: Internally stored parameters may be accessible only using supplier defined tools .

REQ-AUTO-00190

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 29
Statement: 7.17 Umax: - - 32/36/48 A Specific test relations TBD 7.18 Umin: 16 - - V CVS41 limits may go below this value.

REQ-AUTO-00246

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 41
Statement: Reduced versions of test procedure II may be agreed and used during various tests.

REQ-AUTO-00249

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/3299216_1.md page 47
Statement: P 1 Page 10.7.14 CVS46 §4.6.6 Test LFM: Low Frequency Magnetic Y 10.7.15 CVS46 §4.7 Test VCB CTE N 10.7.16 CVS46 §4.8 Test VCB AN and VCB CP N 10.7.17 CVS46 §4.9 Test C-VCB-VCA N 10.7.18 CVS46 §4.10 Test TSUP VCB A N 10.7.19 CVS46 §4.11 Test TSUP VCB B N 10.7.20 CVS46 §4.12 Test VCB Surge N 10.7.21 CVS46 §4.13 Test VCB Burst N 10.7.22 CVS46 §4.14 Test VCB Charging mode N 10.7.23 CVS46 §4.15 Test ESD: Immunity to electrostatic discharge (ESD) Y 10.7.24 CVS46 §4.15.1 Test ESDD: Direct Discharge, Powered up Y 10.7.25 CVS46 §4.15.2 Test ESDI: Indirect Discharge (Powered up) Y 10.7.26 CVS46 §4.15.3 Test ESDH: ESD Handling, Component not energised Y 10.7.27 CVS46 §5.1 Vehicle test ESD Traton performs Vehicle test, Traton may need support from supplier with any issues originating from the component.

REQ-AUTO-00250

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 47
Statement: Y 10.7.28 CVS46 §5.2 Vehicle test RE: Emitted interference of the complete vehicle Y 10.7.29 CVS46 §5.2.1 Vehicle test RE: Protection of receivers outside the vehicle Y 10.7.30 CVS46 §5.2.2 Vehicle test RE: Self- interference Y 10.7.31 CVS46 §5.3 Vehicle test charging: Vehicle in the AC charging mode N 10.7.32 CVS46 §5.3.1 Vehicle test: AC charging: Vehicle in AC charging mode N 10.7.33 CVS46 §5.3.2 Vehicle test: DC charging: Vehicle in DC charging mode N 10.7.34 CVS46 §5.4 Vehicle test RI: Immunity of vehicles to radiated fields Traton performs Vehicle test, Traton may need support from supplier with Y 10.7.35 CVS46 §5.4.1 Vehicle test RI: External interference sources Y

REQ-AUTO-00272

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 52
Statement: Unless otherwise stated, valid version is the latest available as of 1st May 2026.

REQ-AUTO-00278

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/3299216_1.md page 61
Statement: This needs to be checked with the first test run and if necessary the test cycle used in profile B needs to be changed.

REQ-AUTO-00279

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 1
Statement: TRATON Software Update Variant 2 (SUV2) sequence Foreword This Commercial Vehicle Standard (“CVS123-2”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.

REQ-AUTO-00284

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 4
Statement: Clients may prefer to implement programming support using other service parameter values or even another set of programming steps than

REQ-AUTO-00292

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 6
Statement: The value of this variable (and C2, see below) may be used by the boot manager to determine whether to start the application or the boot loader.

REQ_UDS-0051

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 6
Statement: More information on CVS124 REQ_UDS 0051 C2 Also referred to as “programming request” flag.

REQ-AUTO-00294

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 6
Statement: The value of this variable (and C1, see above) may be used by the boot manager to determine whether or not to start the application or the boot loader.

REQ_UDS-0051

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 6
Statement: More information on CVS124 REQ_UDS 0051 C3 Also referred to as “reprogrammed” flag.

REQ-AUTO-00298

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS123-2.md page 7
Statement: Tester System that controls functions such as test, inspection, monitoring, or diagnosis of an on-vehicle electronic control unit and may be dedicated to a specific type of operator (e.g., an off-board scan tool dedicated to garage mechanics, an off-board test tool dedicated to assembly plants, or an on-board tester) see (1) 3.2 Abbreviated terms Table 2: Abbreviated terms Abbreviation Description NRC Negative Response Code NR Negative Response APP Application software BLF Boot Loader Flash CDTCS Clear DTC Setting CF Consecutive Frame Def Default diagnostic session DIAG Changeable over diagnostics interface DID Data identifier DSC Data Security Container EMP Entity Management Protocol Ext Extended diagnostic session FF First Frame FLASH BOOT Boot loader module stored in flash memory FLASH DATA Data set module stored in flash memory

REQ-AUTO-00335

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 14
Statement: SUV2_INFO 35 As example, the client may read certificate validity time and/or RBAC configuration file to verify if the appropriate entities are stored in the server.

REQ-AUTO-00337

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 14
Statement: Alternatively, it may be a client strategy to always update certain entities prior to a software update.

REQ-AUTO-00338

Original confidence: Low
Final status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Action taken: Kept active as a reviewed constraint and mapped through architecture/constraints evidence.
Active in baseline: yes
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 15
Statement: SUV2_INFO 52 Since Link Control is only applicable in production when no application has been programmed by the supplier, the application may return NRC 0x7F (serviceNotSupportedInActiveSession) to this service request and expect the client to proceed to the next step.

REQ_UDS-0051

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 17
Statement: SUV2_INFO 66 Implementation hint: The server resets the “application valid” flag (C1, see CVS124 REQ_UDS 0051) before the erase process starts, to ensure that the server will start in boot loader mode if the programming gets interrupted or if the programming is faulty.

REQ-AUTO-00343

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 19
Statement: SUV2_INFO 82 Implementation hint: The integrity information may contain parts of memory not programmed, regardless of this the server verifies the integrity according to the supplied information on SDSC, see 9.

REQ-AUTO-00378

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 24
Statement: SUV2_INFO 107 In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint.

REQ-AUTO-00420

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 32
Statement: SUV2_INFO 113 In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint.

REQ-AUTO-00480

Original confidence: Low
Final status: Reclassified as Constraint
Rationale: The source text is weakly extracted but carries design or operational constraint value.
Action taken: Kept active as a reviewed constraint and mapped through architecture/constraints evidence.
Active in baseline: yes
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS123-2.md page 42
Statement: SUV2_INFO 134 The received data to decrypt may only be parts of a software module and it will be based on the range defined.

REQ-AUTO-00485

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 2
Statement: Internal Page 2 (90) Foreword This CVS124 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

REQ-AUTO-00492

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 6
Statement: May This word, or the adjective “Optional”, means that an item is truly optional.

REQ_UDS-0003

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 8
Statement: 5.2 ECU Identification Requirements 5.2.1 Used data identifier in order to identify an ECU REQ_UDS 0003 Table 5 -Data identifiers used at ECU identification DID Description/ Name Application Boot loader Changing Def Non- Def Def Ext Prg Ext 0xF180 bootSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF181 applicationSoftwareIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF182 applicationDataIdentificationDataIdentifier ● ● ● ● ● SUPPLIER 0xF186 ActiveDiagnosticSessionDataIdentifier ● ● ● ● ● INTERNAL 0xF187 vehicleManufacturerSparePartNumberDataIdentifier ● ○ ● ○ ○ SUPPLIER 0xF188 vehicleManufacturerECUSoftwareNumberDataIdent ifier ● ● ● ● ● SUPPLIER 0xF189 vehicleManufacturerECUSoftwareVersionNumberD ataIdentifier ● ● ● ● ● SUPPLIER 0xF18A systemSupplierIdentifierDataIdentifier ● ● - - - SUPPLIER 0xF18B ECUManufacturingDateDataIdentifier ● ● ● ● ● SUPPLIER 0xF18C ECUSerialNumberDataIdentifier ● ● ● ● ● SUPPLIER 0xF190 VINDataIdentifier ● ○ ● ● ● DIAG 0xF191 vehicleManufacturerECUHardwareNumberDataIde ntifier ● ● ● ● ● SUPPLIER 0xF192 systemSupplierECUHardwareNumberDataIdentifier ● ● - - - SUPPLIER 0xF193 systemSupplierECUHardwareVersionNumberDataI dentifier ● ● - - - SUPPLIER 0xF194 systemSupplierECUSoftwareNumberDataIdentifier ● ● - - - SUPPLIER

REQ_UDS-0004

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 10
Statement: Internal Page 10 (90) 5.2.1.1 DID 0xF180 bootSoftwareIdentificationDataIdentifier REQ_UDS 0004 Table 6 – Description of DID 0xF180 bootSoftwareIdentificationDataIdentifier 0xF180 Name : bootSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x01 #2 : #14 Boot software identifier #1: : M : M 0x7E .

REQ_UDS-0006

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 10
Statement: 5.2.1.2 DID 0xF181 applicationSoftwareIdentificationDataIdentifier REQ_UDS 0006 Table 7 – Description of DID 0xF181 applicationSoftwareIdentificationDataIdentifier 0xF181 Name : applicationSoftwareIdentificationDataIdentifier Byte Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application software identifier #1: : M 0x7E 0x7E 0x20 : : : #n – 12 : #n Application software identifier #m: : C 0x7E 0x7E 0x20

REQ_UDS-0007

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 11
Statement: Internal Page 11 (90) REQ_UDS 0231 5.2.1.3 DID 0xF182 applicationDataIdentificationDataIdentifier REQ_UDS 0007 Table 8 – Description of DID 0xF182 applicationDataIdentificationDataIdentifier 0xF182 Name: applicationDataIdentificationDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 numberOfModules 1-Byte-A_UINT32 M 0x01 0x02 – 0xFF 0x01 #2 : #14 Application data module part number #1: : 13 Bytes- M : M 0x7E .

REQ_UDS-0008

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 11
Statement: 5.2.1.4 DID 0xF186 ActiveDiagnosticSessionDataIdentifier REQ_UDS 0008 Table 9 – Description of DID 0xF186 ActiveDiagnosticSessionDataIdentifier 0xF186 Name: ActiveDiagnosticSessionDataIdentifier Byte No Description Format Cvt Byte Value Default Data #1 Diagnostic session type 1-Byte-A_UINT32 M 0x00 – 0xFF 0x01

REQ_UDS-0010

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 12
Statement: 5.2.1.6 DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier REQ_UDS 0010 Table 11 – Description of DID 0xF188 vehicleManufacturerECUSoftwareNumberDataIdentifier 0xF188 Name: vehicleManufacturerECUSoftwareNumberDataIdentifier Byte Data #1 : #13 Vehicle manufacturer ECU (server) software number : M : M : 0x20 REQ_UDS 0234 5.2.1.7 DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier REQ_UDS 0011 Table 12 – Description of DID 0xF189 vehicleManufacturerECUSoftwareVersionNumberDataIdentifier 0xF189 Name: vehicleManufacturerECUSoftwareVersionNumberDataIdentifier Byte Data

REQ_UDS-0014

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 14
Statement: Internal Page 14 (90) byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 0x20, 0x30 – 0x39 5.2.1.10 DID 0xF18C ECUSerialNumberDataIdentifier REQ_UDS 0014 Table 15 – Description of DID 0xF18C ECUSerialNumberDataIdentifier 0xF18C Name: ECUSerialNumberDataIdentifier Byte Data To be specified by the supplier.

REQ_UDS-0015

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 14
Statement: 5.2.1.11 DID 0xF190 VINDataIdentifier REQ_UDS 0015 Table 16 – Description of DID 0xF190 VINDataIdentifier 0xF190 Name: VINDataIdentifier Byte Data #1 : #17 VIN number : Byte #17 17-Bytes- M : M : 0x30 .

REQ_UDS-0016

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 14
Statement: 5.2.1.12 DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier REQ_UDS 0016 Table 17 – Description of DID 0xF191 vehicleManufacturerECUHardwareNumberDataIdentifier 0xF191 Name: vehicleManufacturerECUHardwareNumberDataIdentifier Byte Data

REQ_UDS-0017

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 15
Statement: 5.2.1.13 DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier REQ_UDS 0017 Table 18 – Description of DID 0xF192 systemSupplierECUHardwareNumberDataIdentifier 0xF192 Name: systemSupplierECUHardwareNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.14 DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier REQ_UDS 0018 Table 19 – Description of DID 0xF193 systemSupplierECUHardwareVersionNumberDataIdentifier 0xF193 Name: systemSupplierECUHardwareVersionNumberDataIdentifier Byte Data To be specified by the External Supplier 5.2.1.15 DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier REQ_UDS 0019 Table 20 – Description of DID 0xF194 systemSupplierECUSoftwareNumberDataIdentifier 0xF194 Name: systemSupplierECUSoftwareNumberDataIdentifier Byte No Description Format Cvt Byte Value Data To be specified by the External Supplier

REQ_UDS-0020

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 16
Statement: Internal Page 16 (90) 5.2.1.16 DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier REQ_UDS 0020 Table 21 – Description of DID 0xF195 systemSupplierECUSoftwareVersionNumberDataIdentifier 0xF195 Name: systemSupplierECUSoftwareVersionNumberDataIdentifier Byte Data To be specified by the External supplier 5.2.1.17 DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier REQ_UDS 0021 Table 22 – Description of DID 0xF196 exhaustRegulationOrTypeApprovalNumberDataIdentifier 0xF196 Name: exhaustRegulationOrTypeApprovalNumberDataIdentifier Cvt: E Byte Data #1 : #10 Exhaust regulation or type approval 10-Bytes- M : M : 0000000 000 5.2.1.18 DID 0xF197 systemNameOrEngineTypeDataIdentifier REQ_UDS 0022 Table 23 – Description of DID 0xF197 systemNameOrEngineTypeDataIdentifier 0xF197 Name: systemNameOrEngineTypeDataIdentifier Byte Data #1 : #22 System name or engine type 6-to-22-Bytes- G, M : C : 0x20 .

REQ_UDS-0339

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 17
Statement: Internal Page 17 (90) 5.2.1.19 DID 0xF198 SoftwareItemSemanticDataIdentifiers REQ_UDS 0339 Table 24 – Description of DID 0xF198 SoftwareItemSemanticDataIdentifiers 0xF198 Name: SoftwareItemSemanticDataIdentifiers Byte Data #1 : #3 numberOfModules (m) 3-Byte- A_UINT32 M 0x000000 – 0xFFFFFF 00 #4 : #n+3 Data Identifier #1: : byte #n* C1 0x00, 0x20 – 0x7E : : : : : : : Data Identifier #m: : byte #q* C1 0x00, 0x20 – 0x7E *depends on the SoftwareItemSemanticDataIdentifiers length.

REQ_UDS-0340

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 17
Statement: 5.2.1.20 DID 0xF199 SoftwareAssemblySemanticDataIdentifiers REQ_UDS 0340 Table 25 – Description of DID 0xF199 SoftwareAssemblySemanticDataIdentifier s 0xF199 Name: SoftwareAssemblySemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01

REQ_UDS-0341

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 18
Statement: 5.2.1.21 DID 0xF19A HardwareSemanticDataIdentifiers REQ_UDS 0341 Table 26 – Description of DID 0xF19A HardwareSemanticDataIdentifiers 0xF19A Name: HardwareSemanticDataIdentifiers Byte Data #1 : #3 numberOfModules(m) 3-Byte- A_UINT32 M 0x000001 – 0xFFFFFF 01 #4 : #n+3 HardwareSemantic Data Identifier #1: : byte #n* A_ASCIISTR ING, zero M 0x00, 0x20 – 0x7E : : : : : : : HardwareSemantic Data Identifier #m: : byte #q* A_ASCIISTR ING, zero C 0x00, 0x20 – 0x7E *depends on the SoftwareItemSemanticDataIdentifiers length.

REQ_UDS-0023

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 19
Statement: Internal Page 19 (90) 5.2.1.22 DID 0xF19D ECUInstallationDateDataIdentifier REQ_UDS 0023 Table 27 – Description of DID 0xF19D ECUInstallationDateDataIdentifier 0xF19D Name: ECUInstallationDateDataIdentifier Byte Data #1 .

REQ_UDS-0025

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 19
Statement: #8 Format: “YYYYMMDD” byte #1 YY (most significant) byte #2 YY byte #3 YY byte #4 YY byte #5 MM byte #6 MM byte #7 DD byte #8 DD 8-Bytes- RING M : M : 0x2020 20202 020 5.2.1.23 DID 0xF1A5 vehicleManufacturerECUHardwareWithoutBootNumber REQ_UDS 0025 Table 28 – Description of DID 0xF1A5 vehicleMannufacturerECUHardwareWithoutBootNumber 0xF1A5 Name: vehicleManufacturerECUHardwareWithoutBootNumber Byte No: Description Format Cvt Byte Value Default Data #1 : #13 vehicleManufactur er ECU Hardware Number Byte #2 : 13-Byte- M : M : Project 5.2.1.24 DID 0xF1A6 engineNumber REQ_UDS 0026 Table 29 – Description of DID 0xF1A6 engineNumber 0xF1A6 Name: engineNumber Byte Data #1 : #14 Engine number 14-Bytes- A_ASCIISTRING MM : 0x20 C = Applicable only for TRATON standalone engine solutions

REQ_UDS-0030

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 20
Statement: REQ_UDS 0030 Table 31 – Description of DID 0xF1AA Mileage at software update stamp ID Description 0xF1AA Name: mileageAtSoftwareUpdateStamp Byte No Description Format Cvt Byte Value Default Data #1 : #4 Mileage at software update stamp Unit: km Formula: 0,005*X 4-Bytes- A_UINT32 M : M : 0xFFFFFFFF C = Mandatory for ECUs that store Operational data and have access to Vehicle milage information.

REQ_UDS-0032

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 21
Statement: Internal Page 21 (90) REQ_UDS 0032 Table 32 – Description of DID 0xF1AB Date at software update stamp 0xF1AB Name: dateAtSoftwareUpdateStamp Byte Data #1 .

REQ_UDS-0033

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 21
Statement: 5.2.1.28 DID 0xF1AD activeECUSoftwareDataIdentifier REQ_UDS 0033 Table 33 – Description of DID 0xF1AD activeECUSoftwareDataIdentifier 0xF1AD Name: activeECUSoftwareDataIdentifier Byte Data #1 : #2 Active ECU Software 2-Bytes- A_BYTEFIEL D M : M Boot loader: 0x0000 Application Software: 0x0002 No information: 0xFFFF Not applicabl e 5.2.1.29 DID 0xF1AF NodeUID REQ_UDS 0034 Table 34 – Description of DID 0xF1AF NodeUID 0xF1AF Name: NodeUID Byte Data #1 : #8 NodeUID 8-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00

REQ_UDS-0036

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 22
Statement: 5.2.1.30 DID 0xF1B9 RBACCIdentifierNumber REQ_UDS 0036 Table 35 – Description of DID 0xF1B9 RBACCIdentifierNumber 0xF1B9 Name: RBACCIdentifierNumber Byte Data #1 : #16 RBACC Identifier Number 16-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 INFO_UDS 0006 Information on RBACC can be found in CVS151.

REQ_UDS-0037

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 22
Statement: 5.2.1.31 DID 0xF1BA RBACCStructureVersion REQ_UDS 0037 Table 36 – Description of DID 0xF1BA RBACCStructureVersion 0xF1BA Name: RBACCStructureVersion Byte Data #1 : #2 RBACC Structure Version 2-Bytes- A_BYTEFIELD M : M : 0x00 : 0x00 INFO_UDS 0007 Information on RBACC can be found in CVS151.

REQ_UDS-0038

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 22
Statement: 5.2.1.32 DID 0xF1D1 RootCertificateIdentifier REQ_UDS 0038 Table 37 – Description of DID 0xF1D1 RootCertificateIdentifier 0xF1D1 Name: RootCertificateIdentifier Byte Data

REQ_UDS-0041

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 23
Statement: REQ_UDS 0041 The default diagnostic session is referred to as “defaultSession”.

REQ_UDS-0045

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 24
Statement: Internal Page 24 (90) REQ_UDS 0045 Table 39 – Diagnostic service support Service according to ISO 14229-1 Addressin g mode Application Boot loader Def Def Extd Prg Extd DiagnosticSessionControl (0x10) F, P M M M M M ECUReset (0x11) F, P M M M M M SecurityAccess (0x27) - - - - - CommunicationControl (0x28) F, P - M - - M TesterPresent (0x3E) F, P M M M M M AccessTimingParameter (0x83) - - - - - Authentication (0x29) F, P M M M M M SecuredDataTransmission (0x84) P M M M M M ControlDTCSetting (0x85) F, P - M - - M LinkControl (0x87) - C - C C ReadDataByIdentifier (0x22) F, P M M M M M ReadMemoryByAddress (0x23) - - - - - ReadScalingDataByIdentifier (0x24) - - - - - ReadDataByPeriodicIdentifier (0x2A) - - - - - DynamicallyDefineDataIdentifier (0x2C) P U U - - - WriteDataByIdentifier (0x2E) P - M - M C WriteMemoryByAddress (0x3D) - - - - - ClearDiagnosticInformation (0x14) F, P M M - - - ReadDTCInformation (0x19) F, P M M - - - InputOutputControlByIdentifier (0x2F) P - C - - - RoutineControl (0x31) P M M - M M RequestDownload (0x34) P - C - C1 C1 RequestUpload (0x35) P - C - - - TransferData (0x36) P - C - M C RequestTransferExit (0x37) P - C - M C RequestFileTransfer (0x38) P - C - C1 C1 C1 = Either 0x34 or 0x38 is mandatory depending on file based or memory based ECU system.

REQ_UDS-0049

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 25
Statement: REQ_UDS 0049 Diagnostics safe state is the following conditions that needs be satisfied to ensure vehicle is not in operation while performing certain diagnostics services.

REQ_UDS-0305

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 27
Statement: INFO_UDS 0019 Description of the individual transitions as per Figure 2 -State Diagram is explained from REQ_UDS 0305 to REQ_UDS 0337.

REQ_UDS-0306

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 28
Statement: Internal Page 28 (90) REQ_UDS 0306 2.

REQ_UDS-0316

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 29
Statement: Internal Page 29 (90) REQ_UDS 0316 12.

REQ_UDS-0328

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 30
Statement: Internal Page 30 (90) REQ_UDS 0328 24.

REQ-AUTO-00563

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 32
Statement: Its upto the ECU to include the conditions that are relevant for that particular ECU, but needs to be agreed with Vehicle Manufacturer.

REQ_UDS-0073

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 34
Statement: 5.5.2.2 Positive response REQ_UDS 0073 Table 45 – Service 0x11 positive response parameter description 1 ECUReset Response SID M 2 resetType M

REQ_UDS-0074

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 35
Statement: 5.5.2.3 Negative response REQ_UDS 0246 5.5.2.3.1 Supported negative response codes REQ_UDS 0074 Table 46 – Service 0x11 negative response codes NRC Description and scenario 0x12 sub-functionNotSupported Refer to ISO 14229-1 for scenario.

REQ_UDS-0078

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 36
Statement: 5.5.3.1 Request REQ_UDS 0078 Table 47 – Service 0x28 request parameter description 1 CommunicationControl Request SID M 2 controlType M 3 communicationType M 5.5.3.1.1 Request parameter controlType REQ_UDS 0079 Table 48 – Service 0x28 request parameter controlType description Hex (bit 6-0) Description Cvt 0x00 enableRxAndTx M 0x01 enableRxAndDisableTx M 0x40 – 0x5F vehicleManufacturerSpecific U 5.5.3.1.2 Request parameter communicationType REQ_UDS 0080 Table 49 – Service 0x28 request parameter communicationType description Bits Value (Hex) Description Cvt 0 -1 1 normalCommunicationMessages M 4 – 7 0 Disable / Enable specified communicationType M 5.5.3.2 Positive response REQ_UDS 0247 5.5.3.3 Negative response REQ_UDS 0248

REQ-AUTO-00588

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 37
Statement: INFO_UDS 0014 A functionally addressed TesterPresent may arrive at any time during another request.

REQ_UDS-0345

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 37
Statement: 5.5.5.1 Request REQ_UDS 0345 Refer to ISO 14229-1 for request format.

REQ_UDS-0346

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 37
Statement: 5.5.5.1.1 Request parameter DTCSettingType REQ_UDS 0346 Refer to ISO 14229-1 for request parameter DTCSettingType.

REQ_UDS-0347

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 38
Statement: Internal Page 38 (90) 5.5.5.1.2 Request parameter DTCSettingControlOptionRecord REQ_UDS 0347 Refer to ISO 14229-1 for request parameter DTCSettingControlOptionRecord.

REQ_UDS-0348

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 38
Statement: 5.5.5.2 Positive response REQ_UDS 0348 Refer to ISO 14229-1 for positive response format and parameter.

REQ_UDS-0349

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 38
Statement: 5.5.5.3 Negative response REQ_UDS 0349 Refer to ISO 14229-1 for negative response format and codes.

REQ_UDS-0093

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 40
Statement: REQ_UDS 0093 Additional client requests which start copying RAM buffer data into non-volatile memory are not allowed.

REQ_UDS-0259

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 40
Statement: 5.5.8.2 Positive response REQ_UDS 0259

REQ_UDS-0094

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 41
Statement: 5.5.9.2 Positive response REQ_UDS 0263 5.5.9.3 Negative response REQ_UDS 0264 5.5.10 ReadDTCInformation (0x19) service 5.5.10.1 Request REQ_UDS 0265 5.5.10.1.1 Request parameter reportType REQ_UDS 0094 Table 52 – Service 0x19 request parameter reportType description 0x01 reportNumberOfDTCByStatusMask M 0x02 reportDTCByStatusMask M 0x03 reportDTCSnapshotIdentification M 0x04 reportDTCSnapshotRecordByDTCNumber M 0x06 reportDTCExtendedDataRecordByDTCNumber M 0x0F reportMirrorMemoryDTCByStatusMask U

REQ_UDS-0095

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 42
Statement: Internal Page 42 (90) 0x10 reportMirrorMemoryDTCExtendedDataRecordByDTCNumber U 0x11 reportNumberOfMirrorMemoryDTCByStatusMask U 0x12 reportNumberOfEmissionsRelatedOBDDTCByStatusMask E 0x13 reportEmissionsRelatedOBDDTCByStatusMask E 0x42 reportWWHOBDDTCByMaskRecord E 0x55 reportWWHOBDDTCWithPermanentStatus E REQ_UDS 0095 Legislated OBD relevant ECUs have to support legislated OBD standards.

REQ-AUTO-00629

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 49
Statement: Internal Page 49 (90) Range tion #54 ECU start-up and alive reasons Bits 0-3 (start-up reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6-0xE: Reserved 0xF: Not available Bits 4-7 (alive reason): 0x0: Reserved 0x1: Primary wake-up (terminal 15 ON) 0x2: Secondary wake-up 0x3: Sub wake-up 1 0x4: Sub wake-up 2 0x5: Sub wake-up 3 0x6: Stay alive 0x7-0xE: Reserved 0xF: Not available Note 1: While the reason for keeping the ECU alive may change during execution startup reason and alive reason are always identical at ECU startup.

REQ_UDS-0103

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 54
Statement: 5.5.11.1.2 Request parameter controlOptionRecord REQ_UDS 0103 Table 58 – Service 0x2F request parameter controlOptionRecord description 1 inputOutputControlParameter M 2 ..

REQ_UDS-0104

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 54
Statement: 2 + (m-1) controlState byte 1 : controlState byte m C : C 5.5.11.1.3 Request parameter inputOutputControlParameter REQ_UDS 0104 Table 59 – Service 0x2F request parameter inputOutputControlParameter description 0x00 returnControlToECU Refer to ISO 14229-1 for parameter description.

REQ_UDS-0105

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 55
Statement: 5.5.11.2 Positive response REQ_UDS 0285 5.5.11.3 Negative response REQ_UDS 0286 5.5.12 RoutineControl (0x31) service 5.5.12.1 Request REQ_UDS 0287 5.5.12.1.1 Request parameter RoutineControlType REQ_UDS 0105 Table 60 – Service 0x31 request parameter RoutineControlType description 0x01 startRoutine M 0x02 stopRoutine C 0x03 requestRoutineResults C C = Mandatory for routines implemented according to Method “A”.

REQ_UDS-0107

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 56
Statement: Internal Page 56 (90) REQ_UDS 0107 Table 61 – Service 0x31 request parameter RoutineIdentifier description 0x02B2 0x02B3 0x02B4 ReadStatusOfDiagnosticEventCodes ReadDiagnosticEventCodesByStatus ReadEventCodeData These routine IDs are used to handle diagnostic event codes and only mandatory when these type of data are used.

REQ-AUTO-00652

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 57
Statement: INFO_UDS 0017 In order to satisfy stability requirements, the erasing of the boot loader may require that the old boot loader is copied into another memory area before the boot loader memory is erased, see Annex A for an implementation hint.

REQ_UDS-0113

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 58
Statement: M 5.5.13.2 Request parameter dataFormatIdentifier REQ_UDS 0113 Table 63 – Service 0x34 request parameter dataFormatIdentifier description compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF

REQ_UDS-0114

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 59
Statement: Internal Page 59 (90) encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1 5.5.13.3 Request parameter addressAndLengthFormatIdentifier REQ_UDS 0114 Table 64 – Service 0x34 request parameter addressAndLengthFormatIdentifier description 7 - 4 Length (number of bytes) of the memorySize parameter M 3,4 3 - 0 Length (number of bytes) of the memoryAddress parameter M 3, 4 5.5.13.4 Positive response REQ_UDS 0115 Table 65 – Positive response parameter description #1 RequestDownload Response SID M 0x74 #2 lengthFormatIdentifier M 0x20 #3..

REQ_UDS-0116

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 59
Statement: #4 maxNumberOfBlockLength[] = [ byte #1 (MSB) byte #2 ] M M 0xFF 0xFF 5.5.13.5 Response parameter lengthFormatIdentifier REQ_UDS 0116 Table 66 – Service 0x34 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.

REQ_UDS-0117

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 60
Statement: Internal Page 60 (90) 5.5.14 RequestUpload (0x35) 5.5.14.1 Request REQ_UDS 0117 Table 67 – Service 0x35 request parameter description 1 RequestDownload Request SID M 2 dataFormatIdentifier M 3 addressAndLengthFormatIdentifier M 4 ..

REQ_UDS-0118

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 60
Statement: M 5.5.14.1.1 Request parameter dataFormatIdentifier REQ_UDS 0118 Table 68 – Service 0x35 request parameter dataFormatIdentifier description Bytes Description Cvt Values compressionMethod: 0x0: no compression 0x1 – 0x9: reserved for the supplier 0xA: vehicle manufacturer standard compression algorithm LZSS 0xB – 0xF: reserved for vehicle manufacturer M 0x0 – 0xF encryptingMethod: 0x0: no encryption 0x1: encryption on DSC 0x2 -0x7 : reserved for vehicle manufacturer M 0x0 – 0x1

REQ_UDS-0120

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 61
Statement: 5.5.14.2 Positive response REQ_UDS 0293 5.5.14.2.1 Response parameter lengthFormatIdentifier REQ_UDS 0120 Table 70 – Service 0x35 response parameter lengthFormatIdentifier description 7 - 4 Length (number of bytes) of the maxNumberOfBlockLength parameter M 0x2 3 - 0 ISO reserved.

REQ_UDS-0295

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 61
Statement: 5.5.15 TransferData (0x36) service 5.5.15.1 Request REQ_UDS 0295

REQ_UDS-0123

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 62
Statement: 5.5.16.2 Positive response REQ_UDS 0123 Table 72 – Service 0x37 positive response parameter description 1 RequestTransferExit Response SID M

REQ_UDS-0134

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 64
Statement: 5.5.18.1 Request REQ_UDS 0134 Refer to CVS31 .

REQ_UDS-0135

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 64
Statement: 5.5.18.2 Request parameter subFunction REQ_UDS 0135 Refer to CVS31 .

REQ_UDS-0136

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 64
Statement: 5.5.18.3 Positive response REQ_UDS 0136 Refer to CVS31 .

REQ-AUTO-00704

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 69
Statement: INFO_UDS 0020 In order to satisfy stability requirements, the erasing of the boot loader may require that the current boot loader be copied into another non-volatile memory area before the boot loader memory is erased, see Annex A for an implementation hint.

REQ_UDS-0163

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 70
Statement: 5.6.2.1 Request REQ_UDS 0163 Table 78 – RoutineIdentifier 0xFF00 description #1 RoutineControl Request SID M 0x31 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) M 0xFF #4 routineIdentifier (LSB) M 0x00 #5 addressAndLengthFormatIdentifier (XXXXYYYYb) XXXXb = number of bytes of memorySize parameter YYYYb = number of bytes of memoryStartAddress parameter.

REQ_UDS-0167

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 71
Statement: 255 – System specific 5.6.2.3 Positive response REQ_UDS 0167 Table 80 – RoutineControl (EraseMemory) positive response format #1 RoutineControl Response SID M 0x71 #2 routineControlType (StartRoutine) M 0x01 #3 routineIdentifier (MSB) eraseMemory [byte#1] M 0xFF #4 routineIdentifier (LSB) eraseMemory [byte#2] M 0x00 #5 routineStatus routineResult M 0x00-0xFF

REQ_UDS-0169

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 74
Statement: Internal Page 74 (90) #2 routineControlType (StartRoutine) 0x01 #3 routineIdentifier (MSB) 0xFF #4 routineIdentifier (LSB) 0x00 Example #2: Negative response: server → client Table 87 – Example #2: Negative response: server → client #1 Negative Response 0x7F #2 RoutineControl Response SID 0x31 #3 conditionsNotCorrect 0x22 5.6.3 Routine 0x2401 – Software Installation REQ_UDS 0169 The RoutineIdentifier may verify the authenticity of the received file package.

REQ_UDS-0208

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 81
Statement: REQ_UDS 0208 The timestamp is presented in SAE J1939-71 format without local hour/minute offsets.

REQ_UDS-0209

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 81
Statement: REQ_UDS 0209 In SAE J1939-71 section “PGN 65254 Time/Date”, the following format is specified: Table 98 – J1939-71 timestamp format Byte No Length Name Resolutio n Offset Note 1 1 byte Seconds 0.25 s/bit 0 2 1 byte Minutes 1 min/bit 0 3 1 byte Hours 1 hr/bit 0 4 1 byte Month 1 month/bit 0 Value 1 identifies January, value 2 identifies February and so on 5 1 byte Day 0.25 days/bit 0 Values 1,2,3 and 4 identifes first day of month, value 5,6,7,8 identifies second day of month and so on 6 1 byte Year 1 year/bit 1985 Value of 0 identifies year 1985, value of 1 identifes year 1986 and so on 7 1 byte Local minute offset 1 min/bit -125 Not used in DTC timestamps 8 1 byte Local hour offset 1 hr/bit -125 Not used in DTC timestamps

REQ_UDS-0215

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 82
Statement: 5.7.4.1 Latest occurrence REQ_UDS 0215 The latest distance value is updated at a change of DTC status bits 0 (testFailed) and 3 REQ_UDS 0216 The latest distance value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already.

REQ_UDS-0217

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 82
Statement: 5.7.4.2 First occurrence REQ_UDS 0217 The first distance value is updated at the first change of DTC status bits 0 (testFailed) and 3

REQ_UDS-0218

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 83
Statement: REQ_UDS 0218 The operational hours are presented by a four byte integer, big endian, with , half second per bit (0,5s/bit).

REQ_UDS-0220

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 83
Statement: 5.7.5.1 Latest occurrence REQ_UDS 0220 The latest operational hours value is updated at a change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.

REQ_UDS-0221

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 83
Statement: REQ_UDS 0221 The latest operational hours value is updated at a change of DTC status bit 0 (testFailed) from 0 to 1, if bit 3 (confirmedDTC) is 1 already.

REQ_UDS-0222

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 83
Statement: 5.7.5.2 First occurrence REQ_UDS 0222 The first operational hours value is updated at the first change of DTC status bits 0 (testFailed) and 3 (confirmedDTC) both from 0 to 1.

REQ_UDS-0339

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS124.md page 90
Statement: Internal Page 90 (90) Annex C (informative) Change history Release date Changes 2025-12 New requirements and infos: INFO_UDS 0039: F197 structure added REQ_UDS 0339: F198 Request and response format REQ_UDS 0340: F199 Request and response format REQ_UDS 0341: F19A Request and response format REQ_UDS 0342: NRC for RBACC check failures REQ_UDS 0343, REQ_UDS 0344, REQ_UDS 0345, REQ_UDS 0346, REQ_UDS 0347, REQ_UDS 0348, REQ_UDS 0349: Requirements, Request and response formats for the ControlDTCSetting(0x85) added.

REQ_UDS-0003

Original confidence: Low
Final status: Reclassified as Informational
Rationale: The source wording is informational or grants/references a right rather than imposing a supplier SHALL requirement.
Action taken: Kept visible as context; removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS124.md page 90
Statement: Modified requirements: REQ_UDS 0003: Added semantic Identifier DIDs, changed the NodeUID DID to INTERNAL REQ_UDS 0034: Change in the length of NodeUID(0xF1AF) INFO_UDS 0040: Change in the retrieval method for NodeUID(0xF1AF) REQ_UDS 0036: 0xF1B9 RBACCIdentifierNumber is changed to Mandatory REQ_UDS 0037: 0xF1BA RBACCStructureVersion,bit-length changed REQ_UDS 0045: Changes for service (0x84) and (0x31) REQ_UDS 0048: Updated the document references REQ_UDS 0107: 0XCAFE and 0xFF02 are updated to Mandatory REQ_UDS 0180: Modifcations on the bit values and new bit added REQ_UDS 0193: 0x05 is changed to Mandatory 6 Normative references: Updated the referenced documents and versions Removed Requirements and infos: REQ_UDS 0045: (0x86) service removed REQ_UDS 0053, REQ_UDS 0054: Removed the reserved DID ranges and 0xF1C1 REQ_UDS 0024: 0xF19E ODXFileDataIdentifier is removed 2024-10 First issue

REQ-AUTO-00785

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS151.md page 1
Statement: RBAC for diagnostics Foreword This Commercial Vehicle Standard (“CVS151”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.

REQ-AUTO-00843

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS154.md page 1
Statement: Data Security Container base definition Foreword This Commercial Vehicle Standard (“CVS154”) contains requirement specifications for TRATON Group and may be referred to by any of its commercial vehicle Affiliates.

REQ-AUTO-00859

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS154.md page 6
Statement: However, the instance specification may state specialized actions: • Server processes each VerificationEntry one by one.

REQ-AUTO-00880

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS31.md page 3
Statement: Internal Page 3 (31) Foreword This CVS31 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

REQ-AUTO-00932

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS31.md page 16
Statement: AUTH_INFO 133 If the server is unable to delete the client’s authentication state or cannot retrieve it due to internal errors, the server responds NRC 0x94.This informs the client that the authentication state may still exist on the server.

REQ-AUTO-00947

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS31.md page 18
Statement: While the ECU-Diagnostic Role extension specifies the roles assigned to a client, the D-RBACC extension may both grant additional permissions and restrict permissions beyond those derived from the client’s roles.

REQ-AUTO-00988

Original confidence: Low
Final status: Needs Manual Markdown Correction
Rationale: The extracted statement is table-like, concatenated, or flagged with high noise risk.
Action taken: Kept visible, deactivated from the evidence baseline, and queued for manual Markdown correction.
Active in baseline: no
Customer clarification needed: no
Source: converted/markdown-cleaned/CVS32.md page 2
Statement: Internal Page 2 (29) Foreword This CVS32 contains requirement specification for TRATON GROUP and may be used by all within TRATON Group, if applicable.

REQ-AUTO-00996

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS32.md page 6
Statement: (There may be more than one authentication state).

REQ-AUTO-01013

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS32.md page 10
Statement: SDT_REQ 19 The client may alter the CipherScheme between SDT requests within the same SDT sequence.

REQ-AUTO-01056

Original confidence: Low
Final status: Reclassified as Assumption
Rationale: The source uses permissive language or weak extraction, so it is not treated as a confirmed requirement.
Action taken: Kept visible as an assumption candidate and removed from mandatory baseline counts.
Active in baseline: no
Customer clarification needed: yes
Source: converted/markdown-cleaned/CVS32.md page 18
Statement: The SDT positive response may of course contain an encapsulated negative UDS response.

Customer Readiness Summary

Recommendation

Current Gate

Top 5 Customer Clarification Questions

Known Limitations

Additional PDF Delta

Customer Clarification Questions

Product/System Boundary

CQ-BOUNDARY-01

CQ-BOUNDARY-04

CQ-BOUNDARY-06

CQ-BOUNDARY-16

CQ-BOUNDARY-19

CQ-BOUNDARY-23

CQ-BOUNDARY-24

CQ-BOUNDARY-28

CQ-BOUNDARY-31

CQ-BOUNDARY-38

CQ-BOUNDARY-02

CQ-BOUNDARY-03

CQ-BOUNDARY-05

CQ-BOUNDARY-07

CQ-BOUNDARY-08

CQ-BOUNDARY-09

CQ-BOUNDARY-10

CQ-BOUNDARY-11

CQ-BOUNDARY-12

CQ-BOUNDARY-13

CQ-BOUNDARY-14

CQ-BOUNDARY-15

CQ-BOUNDARY-17

CQ-BOUNDARY-18

CQ-BOUNDARY-20

CQ-BOUNDARY-21

CQ-BOUNDARY-22

CQ-BOUNDARY-25

CQ-BOUNDARY-26

CQ-BOUNDARY-27

CQ-BOUNDARY-29

CQ-BOUNDARY-30

CQ-BOUNDARY-32

CQ-BOUNDARY-33

CQ-BOUNDARY-34

CQ-BOUNDARY-35

CQ-BOUNDARY-36

CQ-BOUNDARY-37

CQ-BOUNDARY-39

CQ-BOUNDARY-40

CQ-BOUNDARY-41

CQ-BOUNDARY-42

CQ-BOUNDARY-43

Network and External Interfaces

CQ-INTERFACE-01

Diagnostic and Service Access

CQ-DIAG-01

CQ-DIAG-02

CQ-DIAG-03

CQ-DIAG-04

CQ-DIAG-05

CQ-DIAG-06

CQ-DIAG-07

CQ-DIAG-08

CQ-DIAG-09

CQ-DIAG-10

CQ-DIAG-11

CQ-DIAG-12

CQ-DIAG-13

CQ-DIAG-14

CQ-DIAG-15

CQ-DIAG-16

CQ-DIAG-17

CQ-DIAG-18

CQ-DIAG-19

CQ-DIAG-20

Additional PDF Closure Overlay

Clarification Priority Matrix

Questions by Domain

Questions by Owner

Questions by Impacted Architecture Area

Sequenced Question Register