Customer Question Pack

Customer Question Pack

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

Additional PDFs are source evidence only; they are not customer answers.

Remaining Questions

CQ-BOUNDARY-01

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-04

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-06

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-16

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-19

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-23

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-24

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-28

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-31

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-38

• Priority: P1
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-02

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-03

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-05

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-07

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-08

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-09

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-10

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-11

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-12

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-13

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-14

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-15

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-17

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-18

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-20

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-21

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-22

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-25

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-26

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-27

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-29

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-30

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-32

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-33

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-34

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-35

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-36

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-37

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-39

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-40

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-41

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-42

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-BOUNDARY-43

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-INTERFACE-01

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-01

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-02

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-03

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-04

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-05

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-06

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-07

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-08

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-09

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-10

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-11

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-12

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-13

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-14

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-15

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-16

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-17

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-18

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-19

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

CQ-DIAG-20

• Priority: P3
• Status: Introduced by Additional PDF
• Source of question: Introduced by additional PDFs
• 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.
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.

Clarification Closure History

Clarification Closure Report

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

• Questions evaluated: 64
• Answered by additional PDF: 0
• Partially answered by additional PDF: 0
• Introduced by additional PDF: 64
• Still open / customer decision needed: 64

Question Statuses

CQ-BOUNDARY-01

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00006
• Source Markdown reference: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 5
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-04

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00146
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 23
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-06

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00175
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 27
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-16

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00317
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 10
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-19

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00338
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 15
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-23

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00480
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 42
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-24

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00488
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-28

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0051
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 26
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-31

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00634
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 52
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-38

• Priority: P1
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00866
• Source Markdown reference: converted/markdown-cleaned/CVS154.md page 9
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-02

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_SEC_0040
• Source Markdown reference: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-03

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_SEC_0041
• Source Markdown reference: converted/markdown-cleaned/1001379436_P10_000_01_RDDM-1140152501-1744.md page 7
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-05

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: Req.ID-Description-6.22.1
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 25
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-07

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00190
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 29
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-08

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00246
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 41
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-09

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00250
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 47
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-10

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00272
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 52
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-11

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00278
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 61
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-12

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00279
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 1
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-13

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00284
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 4
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-14

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00292
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-15

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00294
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-17

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00335
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 14
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-18

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00337
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 14
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-20

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00343
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 19
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-21

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00378
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 24
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-22

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00420
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 32
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-25

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00492
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-26

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0041
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 23
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-27

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0049
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 25
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-29

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00563
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 32
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-30

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00588
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 37
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-32

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00652
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 57
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-33

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0135
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 64
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-34

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00704
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 69
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-35

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00785
• Source Markdown reference: converted/markdown-cleaned/CVS151.md page 1
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-36

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00843
• Source Markdown reference: converted/markdown-cleaned/CVS154.md page 1
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-37

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00859
• Source Markdown reference: converted/markdown-cleaned/CVS154.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-39

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00932
• Source Markdown reference: converted/markdown-cleaned/CVS31.md page 16
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-40

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00947
• Source Markdown reference: converted/markdown-cleaned/CVS31.md page 18
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-41

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-00996
• Source Markdown reference: converted/markdown-cleaned/CVS32.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-42

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-01013
• Source Markdown reference: converted/markdown-cleaned/CVS32.md page 10
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-BOUNDARY-43

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ-AUTO-01056
• Source Markdown reference: converted/markdown-cleaned/CVS32.md page 18
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-INTERFACE-01

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: req-6.3
• Source Markdown reference: converted/markdown-cleaned/3299216_1.md page 22
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-01

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0051
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-02

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0051
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 6
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-03

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0051
• Source Markdown reference: converted/markdown-cleaned/CVS123-2.md page 17
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-04

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0305
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 27
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-05

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0345
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 37
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-06

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0346
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 37
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-07

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0348
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 38
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-08

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0349
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 38
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-09

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0093
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 40
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-10

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0295
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 61
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-11

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0134
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 64
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-12

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0136
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 64
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-13

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0208
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 81
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-14

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0215
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 82
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-15

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0217
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 82
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-16

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0218
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 83
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-17

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0220
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 83
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-18

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0221
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 83
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-19

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0222
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 83
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes

CQ-DIAG-20

• Priority: P3
• Baseline question ID: Not in pre-additional baseline
• Previous status: Not in pre-additional baseline
• Source of question: Introduced by additional PDFs
• Original 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.
• New status: Introduced by Additional PDF
• Evidence from additional PDF: None
• Related requirement IDs: REQ_UDS-0003
• Source Markdown reference: converted/markdown-cleaned/CVS124.md page 90
• Closure decision: Introduced by Additional PDF
• Confidence level: Low
• Residual uncertainty: Customer confirmation still needed for final baseline acceptance.
• Customer confirmation still needed: yes